Downlink does not always reach end-device (UC100 + 8-channel Modbus Relay)

Viewed 53
troubleshooting devices chirpstack

Hello everyone, I am having an issue with downlink:

  • I have a UG65 Gateway and a UC100 IoT Controller.I have added them to ChirpStack.
  • On the UC100, I have connected an 8-channel Modbus Relay device to the RS485 port. However, when I send hex code via equeue on ChirpStack to turn the Relay ports on or off, the response is inconsistent: sometimes it executes the relay on/off command immediately, sometimes it takes 5-6 seconds to execute, and other times it does not execute the command at all.
1 Answers

UC100_device

Device UC100 is use class C. I'm have build a web to design a control interface to switch 8 relay ports on/off using the downlink protocol is gRPC.
I tried changing the 'RX2 Frequency' on the UC100 from 'DR2 SF10' to 'DR3 SF9' and adjusted the uplink to shorten the transmission time in the 'Spread Factor' section to 'SF9-DR3', while also turning off ADR on both the device and in the server configuration, but I still couldn't optimize that part; the command was still being missed.
In my prediction, because 8 ports are enabled simultaneously, it sends 8 commands at once, which causes the Chirpstack queue to be full, right? Can you give me a way to fix this issue?

Đức Thuận1
Related
Class-B devices stays at deviceClassEnabled: CLASS_A
2 answers
RX1 window timeout when using RAK MQTT Forwarder for ChirpStack v4
1 answers
Gateway rak 7391 offline after 24h while using cellular and UDP packet forwarder
1 answers
Gateway milesight UG63 LoRaWAN Packet Forward Connected but on chirpstack stays as never seen
1 answers
One IN865 Channel(Freq: 866155000) Not Receiving Uplinks
2 answers
DeviceTimeAns with time 0
1 answers