1) What config? Modbus or Mach?
Modbus . . increase regs count, enter data ; type, name, descriptions, exit. Close MACH4, Reopen MACH4, go to Modbus Config for the function you kust edited and all types have defaulted to input. Change them to registers again, exit, and this time they stick.
2) Use the PLC script and scr.* API
OK, will do. Note I said no CONVINIENET way. Would be nice to have a third data rounting check box to stream data to a Modbus reg. . . . . I'm just being lazy
3) I'm not getting [selected single register ] this one. Can you explain what you are wanting to do?
Want to Write a single register OTHER than #1. No way to do it. You mentioned earlier about putting addresses into the config correctly (i.e. 1 and not 40001), but I have not found any place to enter addresses at all.
4) Can you provide and example? With say the Mod_RSSim modbus simulator? I can set up connections to the simulator, not run the simulator (like the PLC is off) and it works fine.
MACH4 appears to test the Modbus before startup (before screen loading anyway). I can see the polling MACH4 is doing. If the Modbus is healthy, the test takes a few seconds and MACH4 starts. If the Modbus is OFF (as in your example) MACH4 logically would not be able to test, so it just starts. However, if Modbus is Active but is sick or if the user just configures it incorrectly, MACH hangs trying to get a good response from Modbus. The only way to recover (that I found) was to revert to an earlier backup .ini
My suggestion is that if Modbus is active, have MACH4 start and then test the Modbus. If there is a problem, MACH4 should provide and error message to theuser and ignore Modbus so that the user aq) knows what the problem is and B) can re-configure to correct an error without knowing how to retrieve backup .ini and so on.
I think it would be beneficial to both myself and Artsoft from a SUPPORT standpoint. People will be calling in sayng MACH4 won't start and there will be no indication why.
5) I have never seen this! I will try and find it.
I suspect there are not a lot of folks working with the Modbus at this point . . or ever for that matter.
#3 is a problem. The rest are minor inconveniences and #5 is a potential support problem so those are just FYI.
Note that these issues are happening on my development system which MACH4 may not be happy with for some reason, so some of this stuff may be local to my desk . I'm just recording it via post when I encounter it.
BTW, some of the bug stuff needs to be posted in the bugs thread. That way we can track it.
No problem. In fact, I just echoed some stuff to the 'new features' thread from here. I'm just not sure what is a bug and what is operator error at this point. If it turns out the problem is not my own ignorance, then certainly I'll repost in the bug section so that it will get collected.
Thanks very much for this response.. I have all Modbus functions working now via TCP (except item #3 here (single reg write), which works, but is stuck at reg1).
Steve
[/quote]