• Recent
    • Tags
    • Popular
    • Register
    • Login

    Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

    Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website Mango 5 Documentation Website

    Too many alert messages

    Mango feedback
    3
    7
    3.9k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      ray
      last edited by

      Mango is installed to monitor meters with Modbus serial connection. It is running on the Linux platform. Mango generates a lot of messages as follows.

      7568 04:52:19
      'Modbus_/dev/ttyUSB0': Exception from modbus master: Function code: 0x14 04:52:47 - Returned to normal
      7567 00:18:17
      'Modbus_/dev/ttyUSB0': com.serotonin.modbus4j.exception.ModbusTransportException: com.serotonin.messaging.TimeoutException: request=com.serotonin.modbus4j.serial.rtu.RtuMessageRequest@14d9723 00:18:47 - Returned to normal
      7566 00:03:17
      'Modbus_/dev/ttyUSB0': com.serotonin.modbus4j.exception.ModbusTransportException: com.serotonin.messaging.TimeoutException: request=com.serotonin.modbus4j.serial.rtu.RtuMessageRequest@1dfe402 00:04:17 - Returned to normal
      7565 00:01:17
      'Modbus_/dev/ttyUSB0': com.serotonin.modbus4j.exception.ModbusTransportException: com.serotonin.messaging.TimeoutException: request=com.serotonin.modbus4j.serial.rtu.RtuMessageRequest@104d667 00:01:47 - Returned to normal
      7564 Jul 29 23:59
      'Modbus_/dev/ttyUSB0': com.serotonin.modbus4j.exception.ModbusTransportException: com.serotonin.messaging.TimeoutException: request=com.serotonin.modbus4j.serial.rtu.RtuMessageRequest@1da0d5b Jul 29 23:59 - Returned to normal
      7563 Jul 29 23:53
      'Modbus_/dev/ttyUSB0': com.serotonin.modbus4j.exception.ModbusTransportException: com.serotonin.messaging.TimeoutException: request=com.serotonin.modbus4j.serial.rtu.RtuMessageRequest@1fc3519 Jul 29 23:54 - Returned to normal
      7562 Jul 29 23:47
      'Modbus_/dev/ttyUSB0': com.serotonin.modbus4j.exception.ModbusTransportException: com.serotonin.messaging.TimeoutException: request=com.serotonin.modbus4j.serial.rtu.RtuMessageRequest@dbdcef Jul 29 23:47 - Returned to normal
      7561 Jul 29 23:29
      'Modbus_/dev/ttyUSB0': com.serotonin.modbus4j.exception.ModbusTransportException: com.serotonin.messaging.TimeoutException: request=com.serotonin.modbus4j.serial.rtu.RtuMessageRequest@d10aa Jul 29 23:31 - Returned to normal
      7560 Jul 29 23:23
      'Modbus_/dev/ttyUSB0': com.serotonin.modbus4j.exception.ModbusTransportException: com.serotonin.messaging.TimeoutException: request=com.serotonin.modbus4j.serial.rtu.RtuMessageRequest@410205 Jul 29 23:25 - Returned to normal
      7559 Jul 29 23:20
      'Modbus_/dev/ttyUSB0': com.serotonin.modbus4j.exception.ModbusTransportException: com.serotonin.messaging.TimeoutException: request=com.serotonin.modbus4j.serial.rtu.RtuMessageRequest@17e1207 Jul 29 23:21 - Returned to normal
      7558 Jul 29 23:19
      'Modbus_/dev/ttyUSB0': com.serotonin.modbus4j.exception.ModbusTransportException: com.serotonin.messaging.TimeoutException: request=com.serotonin.modbus4j.serial.rtu.RtuMessageRequest@153be14 Jul 29 23:20 - Returned to normal
      7557 Jul 29 23:18
      'Modbus_/dev/ttyUSB0': com.serotonin.modbus4j.exception.ModbusTransportException: com.serotonin.messaging.TimeoutException: request=com.serotonin.modbus4j.serial.rtu.RtuMessageRequest@a0c65c Jul 29 23:18 - Returned to normal
      7556 Jul 29 23:16
      'Modbus_/dev/ttyUSB0': com.serotonin.modbus4j.exception.ModbusTransportException: com.serotonin.messaging.TimeoutException: request=com.serotonin.modbus4j.serial.rtu.RtuMessageRequest@1a9e065 Jul 29 23:17 - Returned to normal
      7555 Jul 29 23:12
      'Modbus_/dev/ttyUSB0': com.serotonin.modbus4j.exception.ModbusTransportException: com.serotonin.messaging.TimeoutException: request=com.serotonin.modbus4j.serial.rtu.RtuMessageRequest@c5ac6d Jul 29 23:12 - Returned to normal
      7554 Jul 29 23:11
      'Modbus_/dev/ttyUSB0': com.serotonin.modbus4j.exception.ModbusTransportException: com.serotonin.messaging.TimeoutException: request=com.serotonin.modbus4j.serial.rtu.RtuMessageRequest@d0c8a Jul 29 23:11 - Returned to normal
      7553 Jul 29 23:08
      'Modbus_/dev/ttyUSB0': com.serotonin.modbus4j.exception.ModbusTransportException: com.serotonin.messaging.TimeoutException: request=com.serotonin.modbus4j.serial.rtu.RtuMessageRequest@86d793 Jul 29 23:09 - Returned to normal
      7552 Jul 29 23:07
      'Modbus_/dev/ttyUSB0': com.serotonin.modbus4j.exception.ModbusTransportException: com.serotonin.messaging.TimeoutException: request=com.serotonin.modbus4j.serial.rtu.RtuMessageRequest@1609b2f Jul 29 23:07 - Returned to normal
      7551 Jul 29 23:04
      'Modbus_/dev/ttyUSB0': com.serotonin.modbus4j.exception.ModbusTransportException: com.serotonin.messaging.TimeoutException: request=com.serotonin.modbus4j.serial.rtu.RtuMessageRequest@1ae74dc Jul 29 23:05 - Returned to normal
      7550 Jul 29 23:02
      'Modbus_/dev/ttyUSB0': com.serotonin.modbus4j.exception.ModbusTransportException: com.serotonin.messaging.TimeoutException: request=com.serotonin.modbus4j.serial.rtu.RtuMessageRequest@1a0b09d Jul 29 23:03 - Returned to normal
      7549 Jul 29 22:54
      'Modbus_/dev/ttyUSB0': com.serotonin.modbus4j.exception.ModbusTransportException: com.serotonin.messaging.TimeoutException: request=com.serotonin.modbus4j.serial.rtu.RtuMessageRequest@1ecfbed Jul 29 22:55 - Returned to normal
      7548 Jul 29 22:48
      'Modbus_/dev/ttyUSB0': com.serotonin.modbus4j.exception.ModbusTransportException: com.serotonin.messaging.TimeoutException: request=com.serotonin.modbus4j.serial.rtu.RtuMessageRequest@18322a4 Jul 29 22:50 - Returned to normal
      7547 Jul 29 22:42
      'Modbus_/dev/ttyUSB0': com.serotonin.modbus4j.exception.ModbusTransportException: com.serotonin.messaging.TimeoutException: request=com.serotonin.modbus4j.serial.rtu.RtuMessageRequest@12e3fa3 Jul 29 22:43 - Returned to normal
      7546 Jul 29 22:39
      'Modbus_/dev/ttyUSB0': com.serotonin.modbus4j.exception.ModbusTransportException: com.serotonin.messaging.TimeoutException: request=com.serotonin.modbus4j.serial.rtu.RtuMessageRequest@457317 Jul 29 22:41 - Returned to normal
      7545 Jul 29 22:33
      'Modbus_/dev/ttyUSB0': com.serotonin.modbus4j.exception.ModbusTransportException: com.serotonin.messaging.TimeoutException: request=com.serotonin.modbus4j.serial.rtu.RtuMessageRequest@186ef65 Jul 29 22:35 - Returned to normal
      7544 Jul 29 22:29
      'Modbus_/dev/ttyUSB0': com.serotonin.modbus4j.exception.ModbusTransportException: com.serotonin.messaging.TimeoutException: request=com.serotonin.modbus4j.serial.rtu.RtuMessageRequest@1d681e Jul 29 22:29 - Returned to normal
      7543 Jul 29 22:26
      'Modbus_/dev/ttyUSB0': com.serotonin.modbus4j.exception.ModbusTransportException: com.serotonin.messaging.TimeoutException: request=com.serotonin.modbus4j.serial.rtu.RtuMessageRequest@17adcd4 Jul 29 22:27 - Returned to normal
      7542 Jul 29 22:22
      'Modbus_/dev/ttyUSB0': com.serotonin.modbus4j.exception.ModbusTransportException: com.serotonin.messaging.TimeoutException: request=com.serotonin.modbus4j.serial.rtu.RtuMessageRequest@135650e Jul 29 22:24 - Returned to normal
      7541 Jul 29 22:02
      'Modbus_/dev/ttyUSB0': com.serotonin.modbus4j.exception.ModbusTransportException: com.serotonin.messaging.TimeoutException: request=com.serotonin.modbus4j.serial.rtu.RtuMessageRequest@10d517c Jul 29 22:02 - Returned to normal
      7540 Jul 29 17:23
      'Modbus_/dev/ttyUSB0': com.serotonin.modbus4j.exception.ModbusTransportException: com.serotonin.messaging.TimeoutException: request=com.serotonin.modbus4j.serial.rtu.RtuMessageRequest@1b0fd23 Jul 29 17:23 - Returned to normal
      7539 Jul 29 17:02
      'Modbus_/dev/ttyUSB0': com.serotonin.modbus4j.exception.ModbusTransportException: com.serotonin.messaging.TimeoutException: request=com.serotonin.modbus4j.serial.rtu.RtuMessageRequest@1dce9f Jul 29 17:02 - Returned to normal
      7538 Jul 29 16:58
      'Modbus_/dev/ttyUSB0': com.serotonin.modbus4j.exception.ModbusTransportException: com.serotonin.messaging.TimeoutException: request=com.serotonin.modbus4j.serial.rtu.RtuMessageRequest@bfefae Jul 29 16:58 - Returned to normal

      Could you inform how to stop it or resolve this problem.

      Thanks in advance !

      1 Reply Last reply Reply Quote 0
      • JoelHaggarJ
        JoelHaggar
        last edited by

        What is your update period and time out settings. Have you tried setting your timeout higher?

        Joel.

        1 Reply Last reply Reply Quote 0
        • R
          ray
          last edited by

          The update period is set to 30 seconds.
          when try to change it and get the message in the attachment.

          Where it says Port- there’s nothing in the drop down and it is a required value.
          Timeout is set to 2000 and there is 1 retry.

          Attachment: download link

          1 Reply Last reply Reply Quote 0
          • JoelHaggarJ
            JoelHaggar
            last edited by

            Yes, port is where you have your rs-485 converter installed. You also need to install the RXTX files as discribed on the download page. Is this windows or linux? I see it looks like you've put the port path in the name field so I'm assuming this is Linux.

            1 Reply Last reply Reply Quote 0
            • M
              mlohbihler
              last edited by

              Note that sometimes when your data source is running the port that it is using will not be displayed in the drop down. You can try disabling the data source and refreshing the page to see if the port shows up.

              Other than that, it looks like your timeout needs to be longer. You can also try upgrading to a more recent version that has I/O logging to log the comm traffic for later analysis. Later versions also have better tools for testing your settings; this will help you determine what timeout value you should use.

              Best regards,
              Matthew

              1 Reply Last reply Reply Quote 0
              • R
                ray
                last edited by

                I tried to export the "point hierarchy" and import right away. The port show up again. When the interval is extended to 3 minutes, number of the alert messages becomes less.

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post