• 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

    Hi.Can anybody give suggestions regarding the Modbus Tcp/Ip

    Modbus4J general discussion
    3
    6
    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.
    • S
      swapnika
      last edited by

      I am using Mango automation-2.0.6 version, Modbus -1.4.2, and Java-6.

      while using the Modbus Tcp/Ip connection i have a problem the devices are not connecting it is showing the error as

      '**modbusIp': com.serotonin.modbus4j.exception.ModbusInitException: java.net.SocketTimeoutException: connect timed out
      **

      Thank you in advance :)

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

        Do you get this error all the time or just now and then. It's normal with modbus communication to get some errors occasionally. If you disable the datasource can you use the point locator tool to successfully communicate with your device?

        I would also recommend trying the TCP with keep alive option as that might help.

        Joel.

        1 Reply Last reply Reply Quote 0
        • S
          swapnika
          last edited by

          I tried with Tcp with alive also that time the Point locator test error is coming.

          Thankyou in advance:)

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

            Something is not configured correctly with your device or the data source. Please share some screen shots so we can see the configurations and the errors.

            Thanks,
            Joel.

            1 Reply Last reply Reply Quote 0
            • N
              nikorun
              last edited by

              Why not trying to poll your slave withj a command line tool like "modpoll" ?

              once you'll be sure that everythning is allright with it, then switch back to Mango.

              Also use the log functionality in Mango (check the Log I/O Box in the modbus Data Source) and make a tail -f on the modbusIO-1.log file

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