TRB245 SMS Spam Issue

Hardware:

  • Router: Teltonika TRB245

  • Communication: Modbus TCP between PLC and router

Problem: I’m implementing a motor monitoring system where the TRB245 sends SMS notifications based on motor status (running/failure) received from a PLC via Modbus TCP.

The issue is that since the PLC inputs are latched, the alarm condition remains active continuously, causing the SMS trigger to fire repeatedly and spam the notification recipients.

Current Setup:

  1. PLC reads motor status signals

  2. Router communicates with PLC via Modbus TCP

  3. Router alarm checks memory register (1=run/failure, 0=normal)

  4. Alarm trigger sends SMS when condition is met

  5. Problem: Continuous triggering due to latched PLC inputs

Question: What’s the best approach to prevent SMS spam while maintaining reliable notifications?

Hi,

If you want to only be informed ONCE, in the “Services → Modbus → Modbus TCP Client → (edit) → Alarm Configuration → (edit)” menu, you can set “Action frequency” to “First trigger”:

Alternatively, if you want to be informed periodically (e.g. once an hour), you can enable the “Redundancy protection” and set your own time period how often this alarm could be triggered:

Hello @DavidVargas,

Please let me know if your issue has been resolved or if you still need any assistance.

Best regards,

Hi, I tried using those configurations for the alarm, but the problem is that I don’t want the SMS to be sent only once—I need it to be sent every time the trigger occurs. Since Modbus is continuously reading, the condition is always true and it keeps sending SMS messages over and over.

I think the best solution is to detect the rising edge in the PLC, link it to another memory bit, and then read that bit via Modbus to trigger the alarm. That way, the SMS is sent only on the rising edge.

By the way, is it possible to send a notification through the RMS app instead of an SMS?

Hello @DavidVargas,

Could you please provide screenshots from your Modbus TCP client requests and the alarms configuration (with any sensitive information hidden)?

In your case, I’d recommend enabling the "Store on change only” option in the requests confirmation section:

This way, you should be able to set the action frequency to “Every trigger” so that the notification is sent only when the condition changes rather than continuously.

Let me know how it goes once you try this.

Best regards,

This topic was automatically closed after 60 days. New replies are no longer allowed.