Beno
January 29, 2021, 4:48pm
5
A few comments that I hope are helpful.
Let me start by saying what I said in this post over here;
Marys post here is still very valid;
The Modbus “standard” can be a somewhat non-standard sometimes (you’ll see various: interpretations of the standard, options and their names, word-order/Endianness, etc). Also, not all Modbus device manuals are as detailed or helpful as one might like.
So… to help you connect any Modbus devices you’d like to monitor/control with groov, we’ve compiled a list of popular Modbus devices and their corresponding settings in groov…
especially what we call the Access Config. settings (defaults picture…
You might be using this tech note already, if not, take a review.https://www.opto22.com/support/resources-tools/documents/2011-using-modbus-devices-with-opto-22-products
I think the main thing you will find helpful is the PAC Manager Modbus Calculator;
I would like to setup the Groov Epic as a Modbus Slave in order for a 3rd party HMI to access and control the unit. What is the easiest way to accomplish this? I recently download the Modbus Integration Kit from Opto 22 not sure if this would be the best way to proceed or not. Any examples that can be provided would be very helpful.
It is also built into groov Manage.
Its under I/O - I/O Tools.
Bottom line, I am pretty sure the PAC Sim Modbus registers are different from EPIC that’s why you are getting the error. (You will need to change more than just the IP address).
