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.
Released for: Schneider Electric UK
Need help?
Product Selector
Quickly and easily find the right products and accessories for your applications.
Get a Quote
Start your sales inquiry online and an expert will connect with you.
Where to buy?
Easily find the nearest Schneider Electric distributor in your location.
Help Centre
Find support resources for all your needs, in one place.