This question was originally posted on DCIM Support by Mian Aqeel on 2018-04-12
Hope you all are doing well, I am connecting the Netbotz Sensor Pod 150 Qty:11 with Netbotz 550, but there is a problem, i,e
few of the Sensor pods were existing and others were new , now after cascading, Sensor POD Identification was not in proper sequence, Rack Monitor 550 - 150 IDs were in below sequence
NB550 - ID 6 - ID 11 - ID 5 - ID 2 - ID 10 - ID 9 - ID 4 - ID 12 - ID 3 - ID 7 - ID 8
Please guide that how it can be sorted out without changing the device placement.
Please note that, I had installed the system as per installation manual and put terminator into last sensor POD out-Link, and then powerup the system.
Solved! Go to Solution.
This answer was originally posted on DCIM Support by Steven Marchetti on 2018-04-12
The 150 uses ID #1 by default. If the device sees another pod in the chain has that ID, it gives it #2 and so on. Subsequently that pod will always have ID #2 until it is added to a chain where #2 (or whichever it was last given) is taken and it will get the next available ID. If it's been attached to a chain, it will retain that ID. There is currently no way to manually alter these IDs. It is a suggested enhancement that's already in the system and I will add this post to that enhancement request however I do not know that it is going to be addressed and if so, when it may be. Sorry.
This comment was originally posted on DCIM Support by Mian Aqeel on 2018-04-12
Hi Steven Marchetti,
Thanks for your prompt response, its OK if there is not solution to this problem,
but i have a question here, suppose I reset my Netbotz Rack monitor 550, will this affect any sensor pod Identification # or not?
Is there any way to hard reset my Netbotz sensor pod 150 ?
This comment was originally posted on DCIM Support by Steven Marchetti on 2018-04-12
Sorry Mian but no. Resetting the NetBotz parent device will not reset the IDs shown on the sensor pod 150s. As I tried to infer, it is in the memory of the pod and only changes when there is a conflict with another pod with the same number and it should increment by 1 (or until it reaches a non-conflict number) . If resetting the appliance was an option, I would have suggested that.
Discuss challenges and get support in energy and automation with 30,000+ experts and peers.
Over 10,000+ support articles are available to help you find answers to your product and business challenges.
Find peer based solutions to your questions. Provide answers for fellow community members!