We are trying to program Mach4 and fix bugs at this time. Doing tech support for modbus is to much of a distraction at this point. Let us get more core issues solved then we can see what we need to do to get your modbus working.
You should start by telling us what you are connecting too for hardware.
Thanks
Brian
You can't train somebody in Modbus on this forum. And that is not the focus. I get that.
However, I did not ask for tech support on Modbus per se. I have had Modbus working with MACH3 for a couple of years now. I am familiar with Modbus and since Modbus is '100% working' in MACH4 Demo, I am willing to spend some time on MACH4 Modbus and report back my findings.
What I need is just a brief explanation of how Modus is implemented specifically in MACH4. Really I don't think it would take more than 15 minutes for describe what data the config screens are looking for. 'Name' can be interpreted a million ways.
All I need (I think) are the following answers and I *should* be off and running
1) What data are the config screens looking for? 'Name' of what?
2) How do you read a register in MACH4
3) How do you write a register in MACH4
That's it, I think. MACH3 had brains and they are gone. What replaces them. Scripts I would imagine. Fine, so how do you read and write the registers with a script? I have the hardware talking to MACH4. I just have no idea how to move the data. These are all MACH4 specific questions.