Hello,
We have several TRB141 with firmware TRB1_R_00.07.14.3. We want the data-to-server to send the custom analogue value every 5 minutes (300 seconds) via REST API. I tryed to set up data-to-server, but it seems that data type “analogue” is missing, which is a little disappointing for a device that is advertised for its input capabilities…
Please help!
Good afternoon,
The TRB141 with firmware version TRB1_R_00.07.14.3 supports the “Data to Server” feature, which allows sending collected data periodically to remote servers via protocols like HTTP(S), MQTT, and Azure MQTT. I do need to note that “Analogue” is not a selectable data type for “Data to server”.
The TRB141 hardware does support analogue inputs, including 4-20 mA current loop inputs and analog voltage inputs (0-30 V range), which are used for measuring sensor signals. The analogue input capability is well-documented, and the device can accurately read and measure these signals, as demonstrated in practical tests with 4-20 mA inputs.
For this, you may need a custom script or application on the device to read the analogue input and format it for sending via HTTP REST API.
Regards,
Arturas
Hello,
Thanks for your reply. The problem with your suggestion is that it does not implement a FIFO queue pattern, like with the Data-to-Server and Modbus Serial Client combination. If I write a simple “read the analogue input’ LUA script, and that is easy to write, it will always read the current analogue input value; if the REST API POST call initiated by Data-to-Server fails for whatever reason, the analogue input value for that certain point in time will be lost.
Regards,
Hi there,
The “Data to Server” feature is designed to collect and send data from sources like Modbus Serial Client, digital inputs, and system parameters, but analogue input is not exposed as a direct data source in this module.
This means you cannot configure the Data to Server module to queue and send analogue input values with built-in FIFO/buffering and retry logic, as you can with Modbus data.
As you mentioned, it is possible to use a custom script (in Lua or shell) to read the analogue input periodically and POST the value to your REST endpoint. However, this approach lacks the built-in queue/buffer mechanism of the Data to Server feature, so if a POST fails, that specific reading is lost.
The Data to Server module’s FIFO queue and retry logic (which ensures no data is lost if a connection fails temporarily) is only available for supported data types, such as Modbus Serial Client data. This is a key difference and a real limitation for applications requiring reliable, lossless analogue data transmission.
Regards,
Arturas
Hello Arturas,
Yes, you are rigtht, this feature is missing, so I am going to write something similar to what I have done with this problem:
TRB145, Modbus Serial Client problem
Regards,