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 > > > ---- Sebastian Kuzminsky <s...@highlab.com> wrote: >> On 03/03/2016 09:21 PM, dan...@austin.rr.com wrote: >>> No joy. I have the RT-preempt (have a 7i92 ethernet control card, >>> does not handle the modbus though). >>> >>> uname -a Linux localhost 3.2.0-4-rt-686-pae #1 SMP PREEMPT RT Debian >>> 3.2.73-2+deb7u2 i686 GNU/Linux >> >> Great, this helps illuminate your situation. >> >> >>> Sudo was required for some of these. Made errors without. >>> >>> cd src ./configure --with-realtime=uspace ./configure: line 2025: >>> config.log: Permission denied ./configure: line 2035: config.log: >>> Permission denied >> >> config.log is produced by the configure script. I bet you ran configure >> as root earlier and it created config.log owned by root, and now when >> you try to run configure as you (non-root) it won't let you overwrite >> root's config.log. >> >> Your options are to either chown all the incorrectly root-owned files to >> be owned by you (this would be my preference), or live as root in this >> directory from now on. The chown could be done like this (in the root >> directory of the git checkout, the one with .git/ in it): >> >> sudo chown -R $(id -u).$(id -g) . >> >> >>> ok.... well then... sudo ./configure --with-realtime=uspace >>> >>> sudo make >>> sudo make setuid >>> source ../scripts/rip-environment >>> which x200_vfd >>> /home/atxhacker/linuxcnc-2.7.4/bin/x200_vfd >> >> Yay, this is good! >> >> >>> Applications Menu-> Linuxcnc -> select HAL file: >>> ./7i92_spid.hal:313: execv(x200_vfd): No such file or directory >> >> Ok, this won't work because the GUI menu runs in a different context >> that hasn't seen your "source ../scripts/rip-environment", so it doesn't >> know to look in /home/atxhacker/linuxcnc-2.7.4/bin. >> >> You then tried this, which is the right way to go: >> >> >>> cd ~/linuxcnc-2.7.4/bin >>> linuxcnc -> select HAL file: >>> ./7i92_spid.hal:31: execv(/home/atxhacker/linuxcnc-2.7.4/bin/rtapi_app): >>> Permission denied >>> ./7i92_spid.hal:31: waitpid failed >>> /home/atxhacker/linuxcnc-2.7.4/bin/rtapi_app gantrykins >> >> You're super close. I bet this is probably fallout from running the >> build as root up above. If you do the chown i suggested, then this >> should start working. >> >> If it doesn't, run "ls -la >> /home/atxhacker/linuxcnc-2.7.4/bin/" and paste the output into an email >> and we'll figure it out. >> >> >>> I did try "sudo linuxcnc", but then my HAL file isn't there, only >>> "Sample Configurations". The whole "My Configurations" tab is gone? >> >> Right, because linuxcnc looks for My Configurations in your home >> directory, and root has a different home directory than you do. Run as >> you, not as root. Linuxcnc has setuid helpers that become root >> automatically in the few places where it's needed. >> >> >> -- >> Sebastian Kuzminsky > > > ------------------------------------------------------------------------------ > _______________________________________________ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users >
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------
_______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
