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

Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website

  • Hi all,

    Have a new and exciting problem with M2M2 with regards to continuity of data.

    Ive got a 5 devices in a daisy chain. Controller->Power Peter->3x I/O Modules to Rs485/LAN gateway that M2M2 polls from. This should work just fine. The unit beside it doesnt have a problem.

    Now, the problem seems to be data collisions. my sampling intervals are 5 seconds and at the end of every other interval a non-zero value (lets say discharge temperatures) just cuts down to zero and then picks up to the "proper" value after the next 5 seconds.

    The baudrates of the devices are all 19200, everything is setup properly as far as I can tell.

    I dont understand why this is different than the time I did this before...any ideas?



  • Not sure what you mean by data collisions. Do you think this is a problem with Modbus? You're using Modbus, right? If so, you could enable I/O logging and see if that help troubleshoot the problem.

  • This is a pic of what Im experiencing. And its only 2 points (OD outlet and discharge temp). The other 13pts work fine.

    I dunno if this helps or not.


    Attachment: download link

  • How do I enable I/O logging?

    Also, does the "point value may not be reliable" have anything to do with it?


  • You need at least 1.13.0 to do I/O logging with Modbus. Your other possibility is to set a discard low limit on the point that is > 0, but then you'll only be getting 10 second updates.