Subscribing is a smart move!
You can subscribe to this forum after you log in or create your free account.
Connect Netbotz to Struxureware via Modbus TCP
EcoStruxure IT forum
A support forum for Data Center Operation, Data Center Expert, and EcoStruxure IT product users to share knowledge on installation, configuration, and general product use.
Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we?ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
Solved
Go to Solution
This question was originally posted on DCIM Support by Gabriel Correa on 2019-10-15
Hello.
I am trying to use a NetBotz rack monitor NBRK0570 as Modbus slave and share temperature and humidity data to a Struxureware AS-P server via Modbus TCP for BMS applications.
I have enabled TCP/IP communication and generated Slave ID for rack and pods.
.png)
However, when I use a Modbus Scanner for to read the Modbus Map than NetBotz Advanced View gave me, all values I get are 57005 (0xDEAD).
%20-%20copia.png)
Anyone know why I can´t get the correct values? Should I change another configuration, or something else? Or NetBotz is not useful for Modbus TCP communications if is not used with Data Expert?
Thank you!
Accepted Solutions
This answer was originally posted on DCIM Support by Steven Marchetti on 2019-10-15
Hi Gabriel,
I've enabled modbus over TCP on my 450. It's similar to the 570 but I didn't have anything connected to it for a quick test:
Then I set up the internal sensor pod as slave 1 and gave the few sensors registers:
Here are my settings using modbuspoll:
I'm getting responses. 0/1 are zero and 2/3 are zero because those are valid values for no smoke and off. 4/5 are 0 (less than 35565 on a 2x 16bit register) and 237 because 74.7 degrees in F is equal to 23.7 C.
The rest are -8531 (0xDEAD) because that is the output the bot gives if that register is invalid or disabled.
Perhaps you don't have the output enabled?
What version of firmware are you running? I'm at 4.6.4.
The rest is pretty simple, you appear to have the slave and register map configured...I can't speak about the BMS.
Steve
This answer was originally posted on DCIM Support by Steven Marchetti on 2019-10-15
Hi Gabriel,
I've enabled modbus over TCP on my 450. It's similar to the 570 but I didn't have anything connected to it for a quick test:
Then I set up the internal sensor pod as slave 1 and gave the few sensors registers:
Here are my settings using modbuspoll:
I'm getting responses. 0/1 are zero and 2/3 are zero because those are valid values for no smoke and off. 4/5 are 0 (less than 35565 on a 2x 16bit register) and 237 because 74.7 degrees in F is equal to 23.7 C.
The rest are -8531 (0xDEAD) because that is the output the bot gives if that register is invalid or disabled.
Perhaps you don't have the output enabled?
What version of firmware are you running? I'm at 4.6.4.
The rest is pretty simple, you appear to have the slave and register map configured...I can't speak about the BMS.
Steve
This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.
Create your free account or log in to subscribe to the forum - and gain access to more than 10,000+ support articles along with insights from experts and peers.