If using NetBotz rest API, Pod Enclosure Number (podEncNum) may be either 0 or 1 based
Issue:
If using NetBotz rest API, Pod Enclosure Number (podEncNum) may be either 0 or 1 based
Product Line:
NetBotz
Environment:
NBRK0750
NBWL0755
Cause:
There are 2 different numbering systems in the NetBotz code, some are 0 based while others are 1 based.
This is exposed in the podEncNum field that we expose in our REST API, mass config, SNMP, Modbus.
Resolution:
For the 150 and 155 pod’s the podEncNum values will be 0-based
For the 170 anad 175 pod’s the podEncNum values will be 1-based
For the AP9520TH the podEncNum values will be 0-based
NOTE that the numbers allocated are distinct across the three sequences based on enclosure type / pod model.
If using NetBotz rest API, Pod Enclosure Number (podEncNum) may be either 0 or 1 based
Product Line:
NetBotz
Environment:
NBRK0750
NBWL0755
Cause:
There are 2 different numbering systems in the NetBotz code, some are 0 based while others are 1 based.
This is exposed in the podEncNum field that we expose in our REST API, mass config, SNMP, Modbus.
Resolution:
For the 150 and 155 pod’s the podEncNum values will be 0-based
For the 170 anad 175 pod’s the podEncNum values will be 1-based
For the AP9520TH the podEncNum values will be 0-based
NOTE that the numbers allocated are distinct across the three sequences based on enclosure type / pod model.
게시 대상: 슈나이더 일렉트릭 Korea
도움이 필요하신가요?
제품 선택기
애플리케이션에 적합한 제품과 액세서리를 빠르고 쉽게 찾을 수 있습니다.
견적 받기
영업 관련하여 온라인으로 문의하시면 전문가가 연락드립니다.
구매처
해당 지역의 가장 가까운 슈나이더 일렉트릭 대리점을 쉽게 찾을 수 있습니다.
지원 센터
한 곳에서 모든 요구 사항에 대한 지원 리소스를 찾아보십시오.