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.
Exception from modbus master: No recipient was found waiting for response
-
Hello everyone, have a nice week, first of all
I must say that I tried extending the timeout time and selecting the Contiguous batches only option as a solution when similar problems were encountered before.I am sharing the current alarm list photo of my 2 modbus datasource sources. The timeout times at the interfaces of my slave devices belonging to the relevant modbus data sources are 3000ms and 10000ms, and 5000ms and 5000ms on the mango.os side. My modbus data sources produce a lot of errors, although the points return correct values. Could this be due to the baudrate settings on the field related to the problem? Or does anyone have a suggestion on the mango side that I can interfere with?
-
@usi
have you tried with mod scan just to prove that you have got a healthy modbus trunk? -
@cwangv
Yes, when I query it with the modbus tool, I can get the values properly. Since my master device is in a remote location, I couldn't change the baudrate rate, I'll try this. Other than that, I can't think of any other suggestions. Now my data points are still reading correctly, but I keep getting errors at the same time. -
@usi
From the message, it seems you are trying to access a modbus/ip device, so the baud rate should have nothing
to do with Mango.Can you try mapping only one point in Mango and see how you go?
-
@cwangv For example, I am sharing the average graph of a current point with an error in 1 week and 2 hour periods.
-
@usi
with modscan, did you see any error messages in the traffics console? Modscan can show you or maintain a correct value even when it encounters errors in next cycle of comms.
Are there more than 1 modbus master polling this device apart from Mango?
Have you tried using the modbus tool in Mango? (shown on the far right of the tabs) -
This is exactly the reason why I cannot understand the cause of the error. There is also no problem when I use the Modbus tool or a secondary modscan tool. Values come regularly, errors come regularly, although there is no communication problem. Here I share the results I got when scanning with the device's modbus tool and secondary modscan scanner. And of course the device receives queries from a single source.
In addition, the slave monitor points in the loop indicate that the communication was successful.
