That's what qModMaster could be good for, then. Bye, Philipp
On 06.03.2016 09:50, Danny Miller wrote: > I don't see a reason to view the traffic itself. I need to go though > the manual and read back register values and try writing some regs. > It's tedious to do with the panel, and I'd have to unmount the VFD and > disable to Modbus to do any panel reads. > > So, reading via modbus would be much more desirable. Like I need to > know what's in the C077 register, and the Intelligent Input Terminal > control registers. And read which IIT reg is activating E12 (which > can't be done with modbus disconnected, as it's causing the error somehow). > > Danny > > On 3/6/2016 2:13 AM, Philipp Burch wrote: >> Hi Danny, >> >> I used qModMaster (https://sourceforge.net/projects/qmodmaster/) for >> low-level Modbus access while I was developing some Modbus hardware. >> Maybe you can use it to figure out under which circumstances the error >> occurs. >> Another option would be to log the traffic (I suppose you are using the >> serial Modbus connection, not Ethernet) using a Y-cable. You could then >> compare the commands sent from the Mach3 controller vs. the x200_vfd output. >> >> Bye, >> Philipp >> >> On 06.03.2016 09:04, dan...@austin.rr.com wrote: >>> OK, I think I got it- by just copying x200_vfd from the build dir into >>> usr/bin. I think it was build wrongly the first time I tried that... but >>> the code does "go" now. Which is GREAT! But it doesn't run the X200. >>> >>> Correct me if I'm wrong but it appears that wj200_vfd's modbus bit >>> read/writes use addresses offset by -1. That's the way the code runs and >>> it seems to give the correct results in hal monitor. M3 sets "running" to >>> TRUE. I have all the output bits corrected for the X200- the input bits >>> (fwd, reset, trip) are identical in the X200. >>> >>> Problem is, as soon as I start, is-alarm bit sets. The VFD panel says >>> "E12", which is "A signal on an intelligent input terminal configured as >>> EXT has occurred. The inverter trips and turns OFF the output to the motor" >>> >>> I pulled the RJ45 Modbus cable off the VFD and hit Reset, it read >>> 0.0="Ready". Plugged in Rj45 with LinuxCNC running... "E12". >>> >>> I can't use the panel to explore the registers. Once you set the "Modbus >>> controls on" DIP switch, the panel input is disabled. >>> >>> This is weird. I was using this VFD under Mach3 and just wrote freq, dir, >>> and run. No "E12" hardware error for that- or with the ModBus unplugged, >>> or plugged in but without LinuxCNC running. >>> >>> Any ideas? I'm wondering if I have the Modbus watchdog set (C077) on the >>> VFD- I don't think that would cause the Alarm bit to set- that's explicitly >>> an EXT error, which should be the physical terminal. I'd normally say >>> "well, then, that error's from the unconnected pin and needs to be >>> disabled", but there's no error like that under Mach3. >>> >>> Is there a good way to read/write the Modbus coils or regs manually to >>> investigate the problem? Like I say I don't have panel access right now >>> because of the physical Modbus switch. >>> >>> >>> Danny
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------
_______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
