Timeout error while reading data from power meter

Python
1

I’m trying to establish connection with Rail350 Power Meter using XBee RS-485 Adapter. I had configured my Connect Port X4 as it is described on this page http://www.digi.com/wiki/developer/index.php/Modbus_Bridge_on_CPX4, set up Adapter to work with RS485 (DIP switches 2,3,4 are ON) and configured connection parameters as follows:
Baud Rate (BD): 19200 (Rail 350 default value)
Parity (NB): None,
Flow Control (D7 - in Advanced Settings): 7,
Packetization Timeout (RO): 20

Connections seems to be open properly:

UDP 502 Modbus/TCP Listener 0
192.168.1.111 Modbus/TCP via TCP 0
192.168.1.111 local shell telnet 0
TCP 502 Modbus/TCP Listener 0
00:13:a2:00:40:62:59:6a! Modbus/RTU via Zigbee 0

When I send modbus messages using Modbus Poll (or other software, I’ve also wrote a python script sendig modbus frames to 127.0.0.1 on UDP port 502) I only receive Timeout error (0B if error responses are enabled).

Here is a part of output from Connect Port:

#> set trace state=on mask=ia:i+d+w
#>
#> 107838:ia:INFO:mbtcp:m01 recv req 1
107838:ia:DEBG: 00 00 00 00 00 06 05 03 02 02 00 02
107838:ia:DEBG:rte[0]: return[20]
107843:ia:DEBG:mbrtu:p02 Zigbee slave connect 00:13:a2:00:40:62:59:6a!
107844:ia:INFO:Binding on XBee end-point 232 (0xE8)
107847:ia:INFO:mbrtu:p02 send req 1
107847:ia:DEBG: 05 03 02 02 00 02 65 F7
117839:ia:WARN:mbtcp:m01 message timeout error
117840:ia:DEBG:mbtcp:m01 suppress error resp per config
117847:ia:WARN:mbrtu:p02 slave timeout error
122839:ia:INFO:mbtcp:m01 recv req 2
122840:ia:DEBG: 00 01 00 00 00 06 05 03 02 02 00 02
122840:ia:DEBG:rte[0]: return[20]
122842:ia:INFO:mbrtu:p02 send req 2
122842:ia:DEBG: 05 03 02 02 00 02 65 F7
132840:ia:WARN:mbtcp:m01 message timeout error
132841:ia:DEBG:mbtcp:m01 suppress error resp per config
132843:ia:WARN:mbrtu:p02 slave timeout error
137839:ia:INFO:mbtcp:m01 recv req 3
137840:ia:DEBG: 00 02 00 00 00 06 05 03 02 02 00 02
137840:ia:DEBG:rte[0]: return[20]
137842:ia:INFO:mbrtu:p02 send req 3
137842:ia:DEBG: 05 03 02 02 00 02 65 F7
147841:ia:WARN:mbtcp:m01 message timeout error
147841:ia:DEBG:mbtcp:m01 suppress error resp per config
147843:ia:WARN:mbrtu:p02 slave timeout error
149840:ia:INFO:mbtcp:m01 recv req 4
149841:ia:DEBG: 00 03 00 00 00 06 01 03 02 02 00 02
149841:ia:DEBG:rte[0]: return[0]
149841:ia:WARN:mbtcp:m01(730) no path error
149842:ia:DEBG:mbtcp:m01 suppress error resp per config
165841:ia:INFO:mbtcp:m01 recv req 5
165842:ia:DEBG: 00 04 00 00 00 06 01 03 02 02 00 02
165842:ia:DEBG:rte[0]: return[0]
165842:ia:WARN:mbtcp:m01(730) no path error
165843:ia:DEBG:mbtcp:m01 suppress error resp per config
176842:ia:INFO:mbtcp:m01 recv req 6
176842:ia:DEBG: 00 05 00 00 00 06 05 03 02 02 00 02
176842:ia:DEBG:rte[0]: return[20]
176844:ia:INFO:mbrtu:p02 send req 6
176844:ia:DEBG: 05 03 02 02 00 02 65 F7
186844:ia:WARN:mbtcp:m01 message timeout error
186844:ia:DEBG:mbtcp:m01 suppress error resp per config
186846:ia:WARN:mbrtu:p02 slave timeout error
187843:ia:INFO:mbtcp:m01 recv req 7
187843:ia:DEBG: 00 06 00 00 00 06 05 04 02 02 00 02
187843:ia:DEBG:rte[0]: return[20]
187845:ia:INFO:mbrtu:p02 send req 7
187846:ia:DEBG: 05 04 02 02 00 02 D0 37
197844:ia:WARN:mbtcp:m01 message timeout error
197844:ia:DEBG:mbtcp:m01 suppress error resp per config
197846:ia:WARN:mbrtu:p02 slave timeout error
201843:ia:INFO:mbtcp:m01 recv req 8
201844:ia:DEBG: 00 07 00 00 00 06 05 03 02 02 00 02
201844:ia:DEBG:rte[0]: return[20]
201846:ia:INFO:mbrtu:p02 send req 8
201846:ia:DEBG: 05 03 02 02 00 02 65 F7
211844:ia:WARN:mbtcp:m01 message timeout error
211844:ia:DEBG:mbtcp:m01 suppress error resp per config
211846:ia:WARN:mbrtu:p02 slave timeout error
216844:ia:INFO:mbtcp:m01 recv req 9
216845:ia:DEBG: 00 08 00 00 00 06 05 03 02 02 00 02
216845:ia:DEBG:rte[0]: return[20]
216847:ia:INFO:mbrtu:p02 send req 9
216847:ia:DEBG: 05 03 02 02 00 02 65 F7
226846:ia:WARN:mbtcp:m01 message timeout error
226846:ia:DEBG:mbtcp:m01 suppress error resp per config
226849:ia:WARN:mbrtu:p02 slave timeout error
687876:ia:INFO:mbtcp:m01 recv req 10
687877:ia:DEBG: 01 00 00 00 00 06 05 03 02 01 00 02
687877:ia:DEBG:rte[0]: return[20]
687879:ia:INFO:mbrtu:p02 send req 10
687879:ia:DEBG: 05 03 02 01 00 02 95 F7
697877:ia:WARN:mbtcp:m01 message timeout error
697877:ia:DEBG:mbtcp:m01 suppress error resp per config
697879:ia:WARN:mbrtu:p02 slave timeout error
702793:ia:INFO:mbtcp:m01 recv req 11
702793:ia:DEBG: 02 00 00 00 00 06 05 03 02 01 00 02
702794:ia:DEBG:rte[0]: return[20]
702795:ia:INFO:mbrtu:p02 send req 11
702796:ia:DEBG: 05 03 02 01 00 02 95 F7
712795:ia:WARN:mbtcp:m01 message timeout error
712795:ia:DEBG:mbtcp:m01 suppress error resp per config
712796:ia:WARN:mbrtu:p02 slave timeout error

The Power Meter was checked and is working properly for sure. I’ve also tried changing configuration parameters and response/character timeout but it didn’t help much. Please let me know if there is something I’ve missed or misconfigured.

2

You are sending to Modbus Unit Id #5 - I assume that is what you desire? It appears the ‘use fixed id’ option in a route to change say the source Unit ID of 5 to 1 just for the XBee transaction confuses the IA’s XBee task.

Use the same trace paradigm, but enter as “set trace state=on mask=xbee:i+d+w”, which shows all Xbee traffic. Confirm the message is being sent (you’ll see the Modbus bytes near the end of a perhaps 20+ byte packet.

See if a response is being returned via XBee - the method used to link up the XBee response to the IA engine is rather involved, so perhaps that is where it is being dropped.