I have an X200 VFD (a predecessor to the WJ200) I commanded with Modbus
under Mach3, but am moving this to LinuxCNC. Same PC. So the
hardware's fine. It's starting from a motherboard RS232 port that we've
used for other things under Linux (and has an RS485 converter). VFD is
programmed to r
Hi Danny!
On 29.02.2016 08:15, Danny Miller wrote:
> [...]
>
> loadusr -W wj200_vfd baud 19200
> #default slave address is 1
> setp wj200-vfd.0.mbslaveaddr 1
> setp wj200-vfd.0.commanded-frequency 60
> # connect to wj200-vfd pins
> net spindle-on wj200-vfd.0.run
> net spindle-cw wj200-vfd.0.rever
Not a stupid question at all- I literally didn't do more than I said.
I will try this ASAP.
Do you know how to handle a "watchdog" that continuously checks whether the VFD
is running?
Danny
Philipp Burch wrote:
> Hi Danny!
>
> On 29.02.2016 08:15, Danny Miller wrote:
> > [...]
> >
>
Hi,
according to
http://linuxcnc.org/docs/2.7/html/man/man9/wj200_vfd.9.html
the wj200-wfd component already has a toggle output for use by a
watchdog. Then, there's a "watchdog" component:
http://linuxcnc.org/docs/2.7/html/man/man9/watchdog.9.html
So, your HAL will basically need something like
Wait, aren't these ALREADY connected at:
> > net spindle-on wj200-vfd.0.run
> > net spindle-cw wj200-vfd.0.reverse
> > net spindle-at-speed wj200-vfd.0.is-at-speed
Does "net spindle-on motion.spindle-on" do something additional, or just try to
connect "spindle-on" to an unstated "motion" compone
On 02/29/2016 08:01 PM, dan...@austin.rr.com wrote:
> Wait, aren't these ALREADY connected at:
>
>>> net spindle-on wj200-vfd.0.run
>>> net spindle-cw wj200-vfd.0.reverse
>>> net spindle-at-speed wj200-vfd.0.is-at-speed
>
> Does "net spindle-on motion.spindle-on" do something additional, or just
OK, I am unclear on how baud rate gets set. I see the .c code has "void
userinit()", but I don't know how that gets called.
I had tried "loadusr -W wj200_vfd baud 19200" (kind of random stab) and
thought I was setting the baud, but I changed "baud" to gibberish here
("bxyzz") and no error is
Well I spent several hours on this now. I do see the format is wrong, I
changed to:
loadusr -W wj200_vfd baud=19200
But I've got it on a scope and it's still 9600 baud. And if I change it to
"baud=hahahhaha", there's no error for it being a non-number either.
Could the wj200_vfd code have
On 02/29/2016 10:26 PM, dan...@austin.rr.com wrote:
> Well I spent several hours on this now. I do see the format is wrong, I
> changed to:
>
> loadusr -W wj200_vfd baud=19200
>
> But I've got it on a scope and it's still 9600 baud. And if I change it to
> "baud=hahahhaha", there's no error
On 3/1/2016 10:05 AM, Sebastian Kuzminsky wrote:
> On 02/29/2016 10:26 PM, dan...@austin.rr.com wrote:
>> Well I spent several hours on this now. I do see the format is wrong, I
>> changed to:
>>
>> loadusr -W wj200_vfd baud=19200
>>
>> But I've got it on a scope and it's still 9600 baud. And i
So it is! It's "--baud=".
Well, it didn't make the VFD run. And looking at the Hal monitor, the
vfd "Ready" was False.
I looked through the code, I see where it reads the coils, and compared
with wj200 manual and x200 manual... the x200 does have all the same
coils, but for some reason the w
On 2 March 2016 at 06:24, Danny Miller wrote:
> So, the wj200 driver needs to be modified into an x200 and recompiled.
> We're working through how to do all that right now. The code
> modification seems trivial, the compile stage is a lot more.
The component is written in the "comp" format, so th
On 03/02/2016 02:59 AM, andy pugh wrote:
> On 2 March 2016 at 06:24, Danny Miller wrote:
>> So, the wj200 driver needs to be modified into an x200 and recompiled.
>> We're working through how to do all that right now. The code
>> modification seems trivial, the compile stage is a lot more.
>
> Th
OK, modified the .comp file with the new reg numbers and blanket replaced
"wj200" to "x200".
first tried:
cd /home/atxhacker/linuxcnc-2.7.4/src
sudo ./configure
sudo make
sudo make setuid
That compiled ok, but running linuxcnc got "execv x200_vfd no such file or
directory".
Tried your halcom
On 03/02/2016 09:22 PM, dan...@austin.rr.com wrote:
> OK, modified the .comp file with the new reg numbers and blanket replaced
> "wj200" to "x200".
>
> first tried:
> cd /home/atxhacker/linuxcnc-2.7.4/src
> sudo ./configure
> sudo make
> sudo make setuid
That looks nearly right, but you shouldn'
Forgot to mention- yes there was a "Submakefile" in the wj200_vfd directory.
We moved that to the x200_vfd directory and blanket-replaced wj200 to x200 in
that as well.
It compiles ok. Like I say, starting Linuxcnc, it exits and the error info it
shows says "execv x200_vfd: no such file or di
On 03/03/2016 10:04 AM, dan...@austin.rr.com wrote:
> Forgot to mention- yes there was a "Submakefile" in the wj200_vfd directory.
> We moved that to the x200_vfd directory and blanket-replaced wj200 to x200 in
> that as well.
>
> It compiles ok. Like I say, starting Linuxcnc, it exits and the
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
Sudo was required for some of these. Made errors without.
cd src
./configure --with-realti
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 y
I tried the sudo chown. Not sure what you meant by "the one with .git in it",
I did it from the directory above the src.
I got some errors and redid ./configure --with-realtime=uspace
"make" did a lot of stuff, but ended with:
Linking python module gcode.so
g++ -L/home/atxhacker/linuxcnc-2.7.4/
Oh yeah:
ls -la /home/atxhacker/linuxcnc-2.7.4/bin/
total 12384
drwxr-xr-x 2 atxhacker atxhacker4096 Mar 5 22:54 .
drwxr-xr-x 17 atxhacker atxhacker4096 Feb 8 06:13 ..
-rwxr-xr-x 1 atxhacker atxhacker3358 Mar 2 00:11 5axisgui
-rwxr-xr-x 1 atxhacker atxhacker 128301 Mar 2 00:11
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
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
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 de
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
FYI - You do know that Classic Ladder can write and read from your drive
in a manner similar to the way that Mach3 did, right ?
Dave
On 3/6/2016 12:04 AM, dan...@austin.rr.com wrote:
> Oh yeah:
>
> ls -la /home/atxhacker/linuxcnc-2.7.4/bin/
>
> total 12384
> drwxr-xr-x 2 atxhacker atxhacker
Well can I use the wj200_vfd.comp code to read it, to stay within what
I'm already doing?
Obviously, with the .comp file, I can add whatever read and writes I
need. But it looks like the HAL monitor can only display things tied to
a net, I can't just view elements of the struct, it's not a deb
I saw it mentioned on
http://wiki.linuxcnc.org/cgi-bin/wiki.pl?VFD_Modbus
Which just said "I know nothing about Classic Ladder"- basically I don't
know anything either. The wj200_vfd.comp path looked shorter.
I was not impressed with the way Mach3 ran "brains". That was
super-simplistic and
Mach3 "Brains" was never really completed and was bug ridden. Art
admitted that long ago.
Classic Ladder actually works with the Modbus TCP and RTU interface!
The "Ladder" part scares a lot of people, but being interpretive and
interactive speeds the development process for a one-off application
Well, I'm seeing Coil 0003h: External Trip (EXT) = 1, which would be the Alarm
source. And the VFD display = E12.
E12 is only supposed to be set via IITx=12 (pin triggers EXT/Alarm). But reg
C001-C005, IIT function, are 0, 01, 255, 18, and 255. None are set to 12.
Coil 0007h-000Bh= 0 0 1 0
On 6 March 2016 at 22:22, wrote:
> All I get is a loop- as soon as it comes out of reset, the Alarm bit sets
> itself, even though the EXT coil is 0. I just can't find any possible cause
> for this! I do know the VFD did reset- I hear a relay click.
Is it possibly some checksum or parity e
Nope! I see more clearly- the HAL input net "Enable" in is FALSE. That's not
set inside x200_vfd.comp, but if it ISN'T true, it'll do a write which forces
the EXT bit which forces the ALARM.
What's up with the ENABLE bit? I don't have anything connecting that net in
the HAL file, and it's no
On 6 March 2016 at 23:29, wrote:
> I don't have anything connecting that net in the HAL file, and it's not
> getting set to anything.
It might well default to false if not connected.
--
atp
If you can't fix it, you don't own it.
http://www.ifixit.com/Manifesto
---
I'm sure it will- how do I connect it?? Or just get rid of it?
Danny
andy pugh wrote:
> On 6 March 2016 at 23:29, wrote:
> > I don't have anything connecting that net in the HAL file, and it's not
> > getting set to anything.
>
> It might well default to false if not connected.
>
>
On 6 March 2016 at 23:46, wrote:
> I'm sure it will- how do I connect it?? Or just get rid of it?
Simplest is to "setp pin-name.enable 1" in the HAL file.
--
atp
If you can't fix it, you don't own it.
http://www.ifixit.com/Manifesto
--
And that did it! Well, is there any reason to hook that enable up
to anything? Won't it issue a stop via Modbus if we do Toggle Machine
Power? (I should have checked that).
I found the code has a bug, it's making a "calculated frequency" by
multiplying the freq by 100x. But neither the
On 7 March 2016 at 07:21, Danny Miller wrote:
> And that did it! Well, is there any reason to hook that enable up to
> anything? Won't it issue a stop via Modbus if we do Toggle Machine Power?
> (I should have checked that).
Yes, you would normally expect to connect that to a useful pin. Th
On Monday 07 March 2016 02:21:53 Danny Miller wrote:
> And that did it! Well, is there any reason to hook that enable up
> to anything? Won't it issue a stop via Modbus if we do Toggle Machine
> Power? (I should have checked that).
>
> I found the code has a bug, it's making a "calculated f
I used an Advantech ADAM as an isolated RS232/RS485 converter. It's
rated for high baud rates.
Like I say, I couldn't find a ground on the X200 that I was supposed to
use, not by the manual. The VFD's input does NOT use optos. IIRC I
even took apart the VFD, found the internal interface IC,
On Monday 07 March 2016 10:04:35 Danny Miller wrote:
> I used an Advantech ADAM as an isolated RS232/RS485 converter. It's
> rated for high baud rates.
>
> Like I say, I couldn't find a ground on the X200 that I was supposed
> to use, not by the manual. The VFD's input does NOT use optos. IIRC
On 03/07/2016 12:50 PM, Gene Heskett wrote:
>
> The best of that type of device is (google for it) the "Capacitor
> Wizard", a single function device that costs about $200, which can do it
> incircuit because its signal is too low to turn on any surrounding
> semiconductors even if they are Schotke
On Tuesday 08 March 2016 07:39:25 Mark wrote:
> On 03/07/2016 12:50 PM, Gene Heskett wrote:
> > The best of that type of device is (google for it) the "Capacitor
> > Wizard", a single function device that costs about $200, which can
> > do it incircuit because its signal is too low to turn on any
On 03/08/2016 12:42 PM, Gene Heskett wrote:
>>
>> Gene,
>>
>> Check out the Blue ESR meter. Does the same as the Cap Wizard, and is
>> only $84. It is a kit, but I built mine a few years ago, and anyone
>> that knows which end of a soldering iron to hold can assemble this
>> guy. This meter has g
On Tuesday 08 March 2016 12:56:41 Mark wrote:
> On 03/08/2016 12:42 PM, Gene Heskett wrote:
> >> Gene,
> >>
> >> Check out the Blue ESR meter. Does the same as the Cap Wizard, and
> >> is only $84. It is a kit, but I built mine a few years ago, and
> >> anyone that knows which end of a soldering
On 03/08/2016 06:33 PM, Gene Heskett wrote:
> Never had any issues with it turning on unwanted components. Works
> fine in circuit too. A lot of folks, on both the Tek and HP/Agilent
> groups are using the instrument, and I kinda went with the flow and
> bought a kit. An hour or two in the after
45 matches
Mail list logo
