Hi Piecuch,
This is Max from Milesight Iot support,
Regarding this issue, the UC300 does not include timestamps in its regular reports.
If you want to read the time in Modbus, you can add a LoRaObject to achieve this.
1. Add a custom decoder and create a “time” object.
2. Add an object mapping for the “time” object.
3. After apply it on your UC300. You can verify whether this change has taken effect by checking the data reported by the device and the Modbus objects.
For more information, please kindly refer to the article at the link below to further customize your decoder and object mappings.
How to Use Payload Codec on Milesight Gateway : IoT Support
For more information about LoRaObject, please refer to the links below.
SensorDecoders/LoRaObject.md at main · Milesight-IoT/SensorDecoders · GitHub
Have a nice day.
Best Regards,
Max Cai | Technical Specialist
Hi,
I followed the instructions above, but the time tag does not appear in the packets or as an option in the Modbus server. Could this be related to the "id is already defined" errors? And if so, how can I fix it?
Hi Piecuch,
Please note that you may need to manually apply this custom codec in Network Server > Device, as shown below.
Have a nice day.
Best Regards,
Max Cai | Technical Specialist
Piecuch Jarosław
Hi,
I have a UG67 configured with a UC300, and data transmission to SCADA works for me via the Modbus Server. I want to ask how I can add an object with a timestamp — I would like to have, next to the sensor data, the time the data was received. After adding a “Modbus Object,” the timestamp is empty, because as far as I checked, the UC300 does not transmit it. So how can this be achieved?