now we have confirmed that all the radios have same settings they should talk to each other.
If the repeater is installed between sensor and gateway, it should behave like this
Sensor >>> Repeater >>> Gateway
are you still getting data on the serial terminal.
Also by default sensor sends data in broadcast mode. change that to unicast.
node red has an option to set destination address.
are you still getting data on the serial terminal.
I did initially but then it failed.
Also by default sensor sends data in broadcast mode. change that to unicast.
node red has an option to set destination address.
ok I see how to set the full MAC address destination address in node-red.
I now get data through this modem in USB mode!
So if I understand correctly, no settings need to change when I change modem jumpers back to ethernet mode?
that is correctā¦
We successfully got data in USB mode through enabling Destination Address and specifying the full MAC address (unicast mode). If I understand the MAC address is to be just the last 8 characters without colons, eg
422a353c for the address 00:13:a2:00:42:2a:35:3c
is that correct?
After switching jumpers back to ETH mode I have no data. Any ideas?
correct
because local data will be router to ETH not usb but it modem will still act as repeater.
but I donāt get ANY data from that sensor in ETH mode, so how do I resolve this?
i think it will be best to get on a call and take a look.
agreed. what times tomorrow work best for you?
@Bhaskar Regarding the RS485 converter: we have the āstandardā version, but according to the introduction document, this simply passes the 485 packet, wrapped in the Digi API frame, directly out the RS485 serial. This doesnāt seem like it would work well with a ādumbā Modbus device, connected to that RS485, since that device cannot unwrap the RS485 packet from within the Digi API frame. Or am I missing something? Thanks.
can you share a picture of rs485 modem ?
this one is a gen 2 device and has option to change mode of operation on the FLY.
the default mode is auto encoder. you can use is a dumb wireless to rs485 converter.
@Bhaskar thanks for the great session with @jacob last Friday. Unfortunately we are no longer getting data even though the modems are online and settings have not changed. Can we get another troubleshooting session scheduled?
We have modems working now!
To recap, we changed on the modems:
ā¢ Baud rate to 115200
ā¢ TCP to TCP SERVER
On the Sensors:
ā¢ Changed connection from SERIAL to TCP
ā¢ Set each sensor to have the TCP:2101 address of the target modem
ā¢ Set each sensor to have the Destination Address of the target modem
@Bhaskar After getting modems to work as intended, we moved the Gateway to the target location and within range of the RS485 converter, but still no data. Can you advise next steps? This is our last piece of the puzzle before we can scale the system.
did you confirm if the Modbus command we are sending is correct?
if thatās not correct then there will be no response.
I believe we were getting responses back from the flow meter during our last session, and Iāve seen appropriate responses returned since then. It just seems to go away after a while. Almost as if something powers off after a while.
We may try connecting the Modbus device directly to a serial port on the gateway (Edge EG5120), but I have two questions: 1) which device connects to the 3-pin external connector (Iām guessing COM2) and 2) Iāve tried setting COM2 to RS485 mode using the configuration interface for the gateway, but it wonāt accept this change unless I set up TCP parameters. Iām confused because Iām not trying to set up a network serial interface, just RS485 to the external connector. Thanks.
The gateway rs495 port is bit tricky to use. @jacob has used it in past.
The new RS485 firmware sends health msg after user defined interval.
Can you clarify? Iām not sure what youāre asking me to do. I just want to use the rear serial connection as as a direct Modbus (RS-485) connection. Thanks.
