I know this is a lot to ask. Is there a way you can use Delta's VDTools to read the parameters from your VFD and send me the file for comparison.
It's not a problem. I'll do that on Saturday or Sunday. Can you post a link where I can download the application ? In the meanwhile, here's the list of params I've changed (IIRC) from default to custom (mostly unrelated):
00.03=3, 00.05=60 (all unrelated)
01.00=400, 01.01=200, 01.09=1, 01.10=1 (all unrelated/not applicable)
02.00=0, 02.01=0, 02.04=1 (not applicable/related to digital keypad)
03.08=2 (unrelated)
09.01=3, 09.02=?, 09.04=6 (modbus settings)
As you can see, there's not much here...I wanted to change a lot more, but I could not get detailed info on params I was interested in.
I am using a Delta VFD-E. I have manual controls for VFD on/off, Fwd/Off/Rev, Emergency stop. There are two switches set to ACI and PNP.
I thought that you're using digital keypad accessory like I am. I do not have any auxiliary inputs / external terminals connected (just RJ connector) and I have no experience with that wiring method or related params.
If you're using ext terminals for manual operation, then the values for p02.01 should be 1 or 2 for manual operation and 4 for RS485 control (0=digital keypad), check the manual for p02.00 settings too.
Once I close the comm port, I noticed the VFD sets to 0
How did you noticed that without digital keypad display ? By running vdtools app ?
I then got another laptop running 32 bit and downloaded and installed Mach3 and setup the comm port to 4 and matched your settings for the baud rate. I set the VFD on p2.00 and p2.01 to 4 and 3. The VFD keeps the settings and once "Run Modbus" or "Modbus Input/Output Support" is checked the VFD goes to 0.
Notice that params go to 0, not to 1, which is the default value for those params, and which you should use since you're not using digital keypad. This means that something is setting those params to that value, and that it is not a fallback in case of error (actually, in case of error param value should not be changed).
It may be that we've missed some simple step in configuring mach for modbus since you experienced the same behavior with fresh install, or it can be related to the usage of external inputs and related VFD params (have you tried disconnecting them, backup/reset the vfd params and start from scratch ?). Have you also tried toggling RTS after changing the modbus address from 1 to 0 ? I'm using rs232 to rs485 converter
http://www.ebay.com/itm/RS232-RS485-RS-232-to-RS-485-Converter-Port-Powered-/231331240225?hash=item35dc6a9921 (price went up x2.5 since I bought it) which does not need that option, but since you've mentioned port number 4, I presume you're using USB to rs485 converter, and I've read that people had issues with RTS and those converters.