Connect Netbotz to Struxureware via Modbus TCP

[DCIM_Support]

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.

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).

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!

(CID:149785217)

[DCIM_Support · Accepted solution]

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

(CID:149785244)

[DCIM_Support]

This comment was originally posted on DCIM Support by Law TJ on 2019-10-16

---

Hi, 

Try to read holding register 04 then address 31030? The modbus address should be 331030. 

Best Regards, 

TJ

(CID:149785387)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.