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.
Does Mango has modbus tcp master function?
-
I see it can set modbus IP slave function, but how to set localhost to be modbus IP master?
-
Hi timkk880,
Mango has Modbus Serial and TCP/IP data sources that enable it to behave as a Modbus master (initiating requests to other devices). These can be found on the /data_sources.shtm page.
Mango can also act as a Modbus TCP/IP slave device, accepting requests from other devices. Mango cannot currently act as a Modbus Serial slave device. This is created through the Modbus publisher on the /publishers.shtm page. The publisher configuration binds data points into register locations and determines if they will accept write commands.
I hope that helps!
-
I've used Mango as a MODBUS over IP master for years, it works fantastically.
Regards
Dan -
But how to set Master? I see there is a input form need fill in IP, that should be remote PLC IP adress, so this make localhost computer to be slave, for my understanding, Modbus IP Master should not set any IP address, am I right? I am a beginner and try to learn how to use Mango.
-
The master initiates requests. You put in the PLC's IP address because you need to know where to request something. I think you may have the terms swapped.
-
The Modbus DataSource act as a master. Configure that to get data from a PLC or Modbus capable RTU.
The Modbus Publisher act as a slave. You would need to use virtual Datasource/datapoint in this case for each value you want to transfer, unless those datapoint that you want to transfer come from another source.
It is a bit more effort to work through the publisher (as a slave) because you need to anticipate or figure out what the Master (maybe another SCADA software) want from Mango (publisher) In our case after much debugging we found the modbus master poll register 1-30 from Mango publisher. if those are not configured, Mango do not respond, and the modbus master gives up and never get to the real registers above 4000 that we were actually interested. So we had to create 30 dummy virtual points to make the master happy.
-
sorry, I swapped Master ans slave, thanks for proposals, I will try modbus publish function.
