Re: [Emc-users] Need help with X200 VFD modbus

[Mark]

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 afternoon, and it's all assembled
> up and ready to use.  Very handy little instruments, these hand held
> ESR meters.
>
> Mark
> Yes, they do an excellent job of measuring the most common electrolytic
> capacitor failure, detecting problems 2 years before a loss of
> capacitance will be measured by the common DVM in capacitance mode. They
> don't have a range to check the psu stuff, so generally speaking, that
> mode is similar in usefullness to those appendages on the belly of a
> boar hog.
>
> That $179 Wizard probably saved the station 500k USD in keeping about 15
> DVC-PRO broadcast VCR's going in years of their heyday. Capacitors and
> headwheels still cost us at least $100k though. Pinch rollers and other
> rubber parts were peanuts in comparison. Panasonic usually asked about
> $1500-$2500 a board for a new one, with 11 to 14 boards in a machine,
> and a minimum of a thou & parts at MSRP to repair one sent in.  That
> sort of outgo resulted in permission to buy the wizard in about 30
> seconds. Wasn't hard at all. :)  We still have, kept them like trophy
> deer horns, 3 ea, 2 lb coffee cans 2/3rds full of those capacitors that
> failed.  Thats a boatload because most were smaller than the eraser on a
> #2 lead pencil, so there are thousands in those coffee cans.  All
> surface mounted too.  And yours truly changed about 75% of them, with my
> assistant doing the last 25% after I gave him my office keys & a badly
> worn red office chair at a retirement party, on June 30th 2002.  But by
> 2004 much of that video gear had been replaced with servers with banks
> of hard drives.  Even the news cameras were insertable HD storage by
> then, still are today but replaced with full hidef stuff now.
>
> Cheers, Gene Heskett

As you know, I like to futz around with older Tek equipment.  I usually 
snatch up the "for parts or not working" units on the Bay of E.  Usually 
the problem(s) is centered in the power supply.  First thing I look at 
after dragging the schematics out are the caps. Visual, then an ESR 
search.  A lot of the units that were made in the era I like to fix have 
bad electrolytic caps, and a good many have those bad caps that were 
installed in a lot of other hardware like computers and such.  I forget 
if it was the Chinese or Koreans that tried to make caps based on stolen 
tech, but a lot of those caps found their way into our electronics.  Tek 
was no different. At any rate, the ESR meter makes troubleshooting power 
supplies bunches easier.

Mark

--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785111=/4140
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[Gene Heskett]

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 iron to hold can
> >> assemble this guy. This meter has gotten excellent reviews from all
> >> over.
> >>
> >> 
> >
> > I hadn't been aware of that one yet. Its 100mv voltage may turn on
> > any schotkey diodes a wee bit, something the 85 mv of the wizard is
> > far less likely to do.
> >
> > Bookmarked, thanks a bunch.  I will order me one when the 2mm wide
> > clips are back in stock.  The wizard, FWIW, gold plates all the
> > probe stuffs to negate any resistance buildup due to oxidation,
> > where I note in the pix that these appear to be chromed and will
> > need more care to prevent chipping the chrome off which also has a
> > higher bulk resistance than the gold.
> >
> > But I like, and at less than half the wizard, will get one.
> >
> >>> Cheers, Gene Heskett
>
> 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 afternoon, and it's all assembled
> up and ready to use.  Very handy little instruments, these hand held
> ESR meters.
>
> Mark

Yes, they do an excellent job of measuring the most common electrolytic 
capacitor failure, detecting problems 2 years before a loss of 
capacitance will be measured by the common DVM in capacitance mode. They 
don't have a range to check the psu stuff, so generally speaking, that 
mode is similar in usefullness to those appendages on the belly of a 
boar hog.

That $179 Wizard probably saved the station 500k USD in keeping about 15 
DVC-PRO broadcast VCR's going in years of their heyday. Capacitors and 
headwheels still cost us at least $100k though. Pinch rollers and other 
rubber parts were peanuts in comparison. Panasonic usually asked about 
$1500-$2500 a board for a new one, with 11 to 14 boards in a machine, 
and a minimum of a thou & parts at MSRP to repair one sent in.  That 
sort of outgo resulted in permission to buy the wizard in about 30 
seconds. Wasn't hard at all. :)  We still have, kept them like trophy 
deer horns, 3 ea, 2 lb coffee cans 2/3rds full of those capacitors that 
failed.  Thats a boatload because most were smaller than the eraser on a 
#2 lead pencil, so there are thousands in those coffee cans.  All 
surface mounted too.  And yours truly changed about 75% of them, with my 
assistant doing the last 25% after I gave him my office keys & a badly 
worn red office chair at a retirement party, on June 30th 2002.  But by 
2004 much of that video gear had been replaced with servers with banks 
of hard drives.  Even the news cameras were insertable HD storage by 
then, still are today but replaced with full hidef stuff now.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://makebettercode.com/inteldaal-eval
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[Mark]

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 gotten excellent reviews from all over.
>>
>> 
> I hadn't been aware of that one yet. Its 100mv voltage may turn on any
> schotkey diodes a wee bit, something the 85 mv of the wizard is far less
> likely to do.
>
> Bookmarked, thanks a bunch.  I will order me one when the 2mm wide clips
> are back in stock.  The wizard, FWIW, gold plates all the probe stuffs
> to negate any resistance buildup due to oxidation, where I note in the
> pix that these appear to be chromed and will need more care to prevent
> chipping the chrome off which also has a higher bulk resistance than the
> gold.
>
> But I like, and at less than half the wizard, will get one.
>>> Cheers, Gene Heskett

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 afternoon, and it's all assembled up and 
ready to use.  Very handy little instruments, these hand held ESR meters.

Mark

--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://makebettercode.com/inteldaal-eval
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[Gene Heskett]

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
> > surrounding semiconductors even if they are Schotkey types.
>
> 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 gotten excellent reviews from all over.
>
> 

I hadn't been aware of that one yet. Its 100mv voltage may turn on any 
schotkey diodes a wee bit, something the 85 mv of the wizard is far less 
likely to do.

Bookmarked, thanks a bunch.  I will order me one when the 2mm wide clips 
are back in stock.  The wizard, FWIW, gold plates all the probe stuffs 
to negate any resistance buildup due to oxidation, where I note in the 
pix that these appear to be chromed and will need more care to prevent 
chipping the chrome off which also has a higher bulk resistance than the 
gold.

But I like, and at less than half the wizard, will get one.
>
> > Cheers, Gene Heskett
>
> Cheers,
> Mark
>
>
> --
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://makebettercode.com/inteldaal-eval
> ___
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://makebettercode.com/inteldaal-eval
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[Mark]

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 Schotkey types.

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 gotten excellent reviews from all over.



>
> Cheers, Gene Heskett

Cheers,
Mark


--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://makebettercode.com/inteldaal-eval
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[Gene Heskett]

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
> I even took apart the VFD, found the internal interface IC, located
> its ground, and tried to find continuity to one of the input pins- no
> dice, as I recall.
>
> The X200/WJ200, I know they have a target freq and a "target freq
> locked" bit.  But the live actual freq during spin-up, no, I don't
> know of that being available from a reg.
>
> Danny
[...]

Thanks Danny.

Speaking as a C.E.T., which I am:

In that event, it could be advantagious to know the rail voltages 
expected of that interface chip, place a 1/1 divider R to develop a bias 
voltage that would be applied downstream of some coupling capacitors 
thru resistors to cause them to sag toward a balanced condition when at 
rest.  That would be best described as a Rube Goldberg setup, but it 
might work. Dependent on the noise levels.

However, I would think that someplace on this devices interface, there 
has to be a common point. From your previous descriptions its apparent 
that it sits at stopped with all its h-bridges or whatever they call 
them, on but sitting at an exact 50% duty cycle so the net torque is 
zero.

I think I would scope every interface terminal, in or out, to confirm 
that this is the source of the noise. And if it has some time on it 
already, there may be internal bypassing capacitors that have failed 
with age.  I'd automatically suspect ANYTHING with a label rating under 
150 volts, inspecting all of them in a power off for a long time 
condition, with a meter that measures ESR.

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 Schotkey types.

For what it does, this meter is amazing, and while I have investigated 
other dvm's that purport to measure this characteristic of a capacitor, 
all that I have looked at so far in the nearly 20 years since I bought 
the Wizard for the tv station where I was the CE in a former life, all 
failed in some way that reduced their ultimate ability to make a 
meaningfull measurement.

Condem and replace with top quality replacements, any capacitor over a 
microfarad that measures at more than 2 ohms, and you will have found & 
replaced even near term future problems. You might, in the process, 
inadvertantly fix the noise problem if all the capacitors are subjected 
to the ESR test.

I might also comment that the sheckles might be better spent by retiring 
it, and picking up a suitably rated replacement from ebay that Just 
Works(TM).  You are driving a 3 phase motor which has only 2 ways to be 
built internally, as an induction motor with very large driving currants 
at low speeds, or as a stepper motor with a hard magnetized armature 
that actually runs synchronous to the driving frequency. My bet is on 
the induction motor, which will not generate a huge voltage across its 
coils when scoped and turned by hand. A volt or so from any residual 
armature magnetism remaining, in my experiance usually a few milivolts.

A stepper style will generate a coil voltage well above 5 volts in the 
scenarios I can imagine. But because of its instant stall if pushed 
beyond its torque ratings, which fade at higher revs, I would never 
consider using it for a spindle motor. The stall would break the tool, 
and that gets expen$ive. The induction motors speed will sag, drawing 
ever more currant from the controller, until the controller sees the 
overload and sends out the stop signal to the machine as it shuts down 
the motor, so everything ideally stops in its tracks with no broken 
tools(mirrors) & none of the "smoke" gets out.

And we all know this stuff runs on smoke and mirrors and if the smoke 
escapes, or a mirror gets broken, it doesn't work anymore.  ;-)
Sorry, Just Had to throw that in. :)

One old farts $0.02, but you may want to adjust that for inflation in the 
last 81 years.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://makebettercode.com/inteldaal-eval
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[Danny Miller]

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, located its 
ground, and tried to find continuity to one of the input pins- no dice, 
as I recall.

The X200/WJ200, I know they have a target freq and a "target freq 
locked" bit.  But the live actual freq during spin-up, no, I don't know 
of that being available from a reg.

Danny

On 3/7/2016 4:14 AM, Gene Heskett wrote:
> 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 frequency" by
>> multiplying the freq by 100x.  But neither the x200 nor wj200 do that.
>> They go by 10x (e.g. 100Hz is 100.0Hz and formatted as "1000" on both
>> read and write).  So it was trying to send impossible frequencies to
>> the VFD.
>>
>> Now when I first hooked up this system under Mach3, the Modbus didn't
>> read or write and it turned out to be a problem with massive
>> common-mode noise on the VFD, even with no motor output. RS485 is
>> differential, but unless it has opto isolating input stages, its input
>> IC can't read a signal outside its common-mode range even if the
>> differential is fine.
> Ouch.  The speed of the opto's may restrict performance at the higher
> baud rates by causing errors. I'd certainly look at it with a o-scope.
>
>> I fixed that with an RS232-RS485 isolating converter.  At least I
>> thought I did.
>>
>> There's a problem that the X200 has no ground reference to tie the
>> converter's RS485 ground to- not that I could find.  But it worked
>> fine.
>>
>> The thing is, now that I have fprintf reporting, I DO see that the
>> readbits() task fails a LOT when the VFD is decelerating- and to a
>> much lesser extent on acceleration.
> That I'd suspect would be a direct artifact of the lack of a common mode
> reference ground.
>
>> I suspect there's additional excessive ground noise going on during
>> deceleration.  Doesn't seem like it's gonna break anything, though.
>>
>> Danny
> I expect that I had better test this vfd & motor I've purchased by
> setting it up and driving with with a function generator. I have been
> assured by the seller that its quite common to drive its 0-5 volt input
> with a high frequency PWM logic signal, its well filtered and will
> integrate the pwm just fine.  Something the Mesa 5i25 is very good at.
> It has a well marked common ground input that should work well.
>
> But it worries me that I'll lose rigid tapping unless I use it as a
> replacement motor so my encoder still functions, so I may wind up
> putting it on in place of the slow 1hp, fitting the gear from that
> motor, or a replacement of it, to this motor in place of its ER16 chuck.
> That will obviously require replacements of all the spindle and back
> gear bearings with top quality stuff in order to deal with that whole
> gearbox being turned at 6x the speed the existing motor can muster.
> Something in the 6x territory if the nameplate speeds are used. That
> would give about 13,500 revs for wood carving, a huge improvement over
> the 2500 or a bit more that I can get now, using the Pico pwm-servo
> driver.  Bearing life is a huge ? though.
>
> That is unless someone can tell me if the speed tally this vfd returns is
> actual motor speed, and not just the driving frequency, a question thats
> been asked of the vendor and danced around for a reply.  So my question
> to this list is, has anyone attempted to do rigid tapping by using that
> signal as feedback into an a/b/z encoder? Its not available as
> quadrature, its a single pin which I believe is a copy of the driving
> frequency.
>
> And I don't believe in magic.  Not even when David Copperfield does
> it. :)
>
>> On 3/6/2016 6:01 PM, andy pugh wrote:
>>> 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.
> Cheers, Gene Heskett


--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://makebettercode.com/inteldaal-eval
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[Gene Heskett]

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 frequency" by
> multiplying the freq by 100x.  But neither the x200 nor wj200 do that.
> They go by 10x (e.g. 100Hz is 100.0Hz and formatted as "1000" on both
> read and write).  So it was trying to send impossible frequencies to
> the VFD.
>
> Now when I first hooked up this system under Mach3, the Modbus didn't
> read or write and it turned out to be a problem with massive
> common-mode noise on the VFD, even with no motor output. RS485 is
> differential, but unless it has opto isolating input stages, its input
> IC can't read a signal outside its common-mode range even if the
> differential is fine.

Ouch.  The speed of the opto's may restrict performance at the higher 
baud rates by causing errors. I'd certainly look at it with a o-scope.

> I fixed that with an RS232-RS485 isolating converter.  At least I
> thought I did.
>
> There's a problem that the X200 has no ground reference to tie the
> converter's RS485 ground to- not that I could find.  But it worked
> fine.
>
> The thing is, now that I have fprintf reporting, I DO see that the
> readbits() task fails a LOT when the VFD is decelerating- and to a
> much lesser extent on acceleration.

That I'd suspect would be a direct artifact of the lack of a common mode 
reference ground.

> I suspect there's additional excessive ground noise going on during
> deceleration.  Doesn't seem like it's gonna break anything, though.
>
> Danny

I expect that I had better test this vfd & motor I've purchased by 
setting it up and driving with with a function generator. I have been 
assured by the seller that its quite common to drive its 0-5 volt input 
with a high frequency PWM logic signal, its well filtered and will 
integrate the pwm just fine.  Something the Mesa 5i25 is very good at.  
It has a well marked common ground input that should work well.

But it worries me that I'll lose rigid tapping unless I use it as a 
replacement motor so my encoder still functions, so I may wind up 
putting it on in place of the slow 1hp, fitting the gear from that 
motor, or a replacement of it, to this motor in place of its ER16 chuck.  
That will obviously require replacements of all the spindle and back 
gear bearings with top quality stuff in order to deal with that whole 
gearbox being turned at 6x the speed the existing motor can muster. 
Something in the 6x territory if the nameplate speeds are used. That 
would give about 13,500 revs for wood carving, a huge improvement over 
the 2500 or a bit more that I can get now, using the Pico pwm-servo 
driver.  Bearing life is a huge ? though.

That is unless someone can tell me if the speed tally this vfd returns is 
actual motor speed, and not just the driving frequency, a question thats 
been asked of the vendor and danced around for a reply.  So my question 
to this list is, has anyone attempted to do rigid tapping by using that 
signal as feedback into an a/b/z encoder? Its not available as 
quadrature, its a single pin which I believe is a copy of the driving 
frequency.

And I don't believe in magic.  Not even when David Copperfield does 
it. :)

> On 3/6/2016 6:01 PM, andy pugh wrote:
> > 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.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://makebettercode.com/inteldaal-eval
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[andy pugh]

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. The
"setp" in the HAL file was just meant to be a very quick and
definitive test.

I _think_ you probably want to connect the VFD enable to
iocontrol.0.user-enable-out
http://linuxcnc.org/docs/2.7/html/man/man1/iocontrol.1.html
But there are many other options:
http://linuxcnc.org/docs/2.7/html/man/man9/motion.9.html

I suggest poking about with Halmeter to see which pin toggles true at
the right point.

-- 
atp
If you can't fix it, you don't own it.
http://www.ifixit.com/Manifesto

--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://makebettercode.com/inteldaal-eval
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[Danny Miller]

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 x200 nor wj200 do that.  
They go by 10x (e.g. 100Hz is 100.0Hz and formatted as "1000" on both 
read and write).  So it was trying to send impossible frequencies to the 
VFD.

Now when I first hooked up this system under Mach3, the Modbus didn't 
read or write and it turned out to be a problem with massive common-mode 
noise on the VFD, even with no motor output. RS485 is differential, but 
unless it has opto isolating input stages, its input IC can't read a 
signal outside its common-mode range even if the differential is fine.

I fixed that with an RS232-RS485 isolating converter.  At least I 
thought I did.

There's a problem that the X200 has no ground reference to tie the 
converter's RS485 ground to- not that I could find.  But it worked fine.

The thing is, now that I have fprintf reporting, I DO see that the 
readbits() task fails a LOT when the VFD is decelerating- and to a much 
lesser extent on acceleration.

I suspect there's additional excessive ground noise going on during 
deceleration.  Doesn't seem like it's gonna break anything, though.

Danny



On 3/6/2016 6:01 PM, andy pugh wrote:
> 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.
>
>


--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://makebettercode.com/inteldaal-eval
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[andy pugh]

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

--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://makebettercode.com/inteldaal-eval
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[dannym]

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.
> 
> -- 
> atp
> If you can't fix it, you don't own it.
> http://www.ifixit.com/Manifesto


--
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[andy pugh]

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

--
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[dannym]

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 not getting set to anything.

Danny

 andy pugh  wrote: 
> 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 error?
> 
> -- 
> atp
> If you can't fix it, you don't own it.
> http://www.ifixit.com/Manifesto
> 
> --
> ___
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users


--
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[andy pugh]

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 error?

-- 
atp
If you can't fix it, you don't own it.
http://www.ifixit.com/Manifesto

--
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[dannym]

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 0.  The third one is programmed as active-low to be 
the estop, but its function is disabled (255).  E-stop function would be 64- 
but that won't create E12, that's only from an IIT being programmed to 12 and 
the pin's level working that way.

There's a problem in that EXT/Alarm/E12 latches.  I don't see anything on the 
current IIT input status that indicate which one would be the source.  If it 
strobed and went idle, it'll latch with no way to determine which IIT caused 
it. 

I added code for "if Alarm bit is set, printf coils 1h-4h and IIT coils, write 
coil 0003h (EXT Trip event) = 0, then write coil 0004h (Trip Reset) = 1 (that 
auto-clears when reset completes)".

The Alarm bit itself is read-only.

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.

Danny


 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
> > 
> > 
> >  Sebastian Kuzminsky  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 

Re: [Emc-users] Need help with X200 VFD modbus

[Dave Cole]

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.
I learned machine code, assembler, ladder, and then C etc in that order 
so I'm simply abnormal.  ;-)
Dave

On 3/6/2016 12:23 PM, Danny Miller wrote:
> 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 all dressed up with a GUI for non-programmers- I'd
> rather just write code.
>
> Danny
>
> On 3/6/2016 10:13 AM, Dave Cole wrote:
>> 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 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 axis
>>> -rwxr-xr-x  1 atxhacker atxhacker3204 Mar  2 00:11 axis-remote
>>> -rwxr-xr-x  1 atxhacker atxhacker  595611 Mar  5 22:47 classicladder
>>> -rwxr-xr-x  1 atxhacker atxhacker2659 Mar  2 00:11 debuglevel
>>> -rwxr-xr-x  1 atxhacker atxhacker5770 Mar  1 23:58 elbpcom
>>> -rwxr-xr-x  1 atxhacker atxhacker   34595 Mar  5 22:54 genserkins
>>> -rwxr-xr-x  1 atxhacker atxhacker   11674 Mar  2 00:11 gladevcp
>>> -rwxr-xr-x  1 atxhacker atxhacker  202787 Mar  2 00:12 gmoccapy
>>> -rwxr-xr-x  1 atxhacker atxhacker1332 Mar  2 00:12 gremlin
>>> -rwxr-xr-x  1 atxhacker atxhacker  77 Mar  2 00:11 gremlin_view
>>> -rwxr-xr-x  1 atxhacker atxhacker   31695 Mar  3 21:18 gs2_vfd
>>> -rwxr-xr-x  1 atxhacker atxhacker  161755 Mar  2 00:12 gscreen
>>> -rwxr-xr-x  1 atxhacker atxhacker  170370 Mar  5 22:48 halcmd
>>> -rwxr-xr-x  1 atxhacker atxhacker   54059 Mar  1 23:58 halcompile
>>> -rwxr-xr-x  1 atxhacker atxhacker7730 Mar  2 00:11 hal_input
>>> -rwxr-xr-x  1 atxhacker atxhacker2465 Mar  2 00:11 hal_manualtoolchange
>>> -rwxr-xr-x  1 atxhacker atxhacker   74196 Mar  5 22:48 halmeter
>>> -rwxr-xr-x  1 atxhacker atxhacker  108772 Mar  5 22:48 halrmt
>>> -rwxr-xr-x  1 atxhacker atxhacker   16451 Mar  3 21:18 halsampler
>>> -rwxr-xr-x  1 atxhacker atxhacker  313352 Mar  5 22:48 halscope
>>> -rwxr-xr-x  1 atxhacker atxhacker  78 Mar  2 00:11 halshow
>>> -rwxr-xr-x  1 atxhacker atxhacker   16662 Mar  3 21:18 halstreamer
>>> -rwxr-xr-x  1 atxhacker atxhacker  211041 Mar  5 22:48 halui
>>> -rwxr-xr-x  1 atxhacker atxhacker   13174 Mar  2 00:11 hbmgui
>>> -rwxr-xr-x  1 atxhacker atxhacker6313 Mar  2 00:11 hexagui
>>> -rwxr-xr-x  1 atxhacker atxhacker   47686 Mar  3 21:18 hy_vfd
>>> -rwxr-xr-x  1 atxhacker atxhacker   26836 Mar  2 00:11 image-to-gcode
>>> -rwxr-xr-x  1 atxhacker atxhacker   15265 Mar  5 22:47 inivar
>>> -rwxr-xr-x  1 atxhacker atxhacker  182713 Mar  5 22:54 io
>>> -rwxr-xr-x  1 atxhacker atxhacker  189240 Mar  5 22:54 iov2
>>> -rwxr-xr-x  1 atxhacker atxhacker  200501 Mar  5 22:48 keystick
>>> -rwxr-xr-x  1 atxhacker atxhacker2729 Mar  2 00:11 lintini
>>> -rwxr-xr-x  1 atxhacker atxhacker  259421 Mar  5 22:48 linuxcnclcd
>>> -rwxr-xr-x  1 atxhacker atxhacker   14654 Mar  5 22:54 
>>> linuxcnc_module_helper
>>> -rwxr-xr-x  1 atxhacker atxhacker  273576 Mar  5 22:48 linuxcncrsh
>>> -rwxr-xr-x  1 atxhacker atxhacker  137167 Mar  5 22:48 linuxcncsvr
>>> -rwxr-xr-x  1 atxhacker atxhacker7535 Mar  2 00:11 linuxcnctop
>>> -rwxr-xr-x  1 atxhacker atxhacker4437 Mar  2 00:11 maho600gui
>>> -rwxr-xr-x  1 atxhacker atxhacker5032 Mar  2 00:11 max5gui
>>> -rwxr-xr-x  1 atxhacker atxhacker   62501 Mar  5 22:47 mb2hal
>>> -rwxr-xr-x  1 atxhacker atxhacker1596 Mar  2 00:11 mdi
>>> -rwxr-xr-x  1 atxhacker atxhacker 3780992 Mar  5 22:54 milltask
>>> -rwxr-xr-x  1 atxhacker atxhacker   35254 Mar  5 22:54 motion-logger
>>> -rwxr-xr-x  1 atxhacker atxhacker 101 Mar  2 00:11 ngcgui
>>> -rwsr-x---  1 root  atxhacker   34014 Mar  1 23:58 pci_read
>>> -rwsr-x---  1 root  atxhacker   33978 Mar  1 23:58 pci_write
>>> -rwxr-xr-x  1 atxhacker atxhacker  297892 Mar  2 00:11 pncconf
>>> -rwxr-xr-x  1 atxhacker atxhacker 187 Oct 24 07:52 profile_axis
>>> -rwxr-xr-x  1 atxhacker atxhacker5281 Mar  2 00:11 puma560gui
>>> -rwxr-xr-x  1 atxhacker atxhacker4606 Mar  2 00:11 pumagui
>>> -rwxr-xr-x  1 atxhacker atxhacker  65 Mar  2 00:11 pyngcgui
>>> -rwxr-xr-x  1 atxhacker atxhacker3148 Mar  2 00:11 pyvcp
>>> -rwxr-xr-x  1 atxhacker atxhacker 3311487 Mar  5 

Re: [Emc-users] Need help with X200 VFD modbus

[Danny Miller]

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 all dressed up with a GUI for non-programmers- I'd 
rather just write code.

Danny

On 3/6/2016 10:13 AM, Dave Cole wrote:
> 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 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 axis
>> -rwxr-xr-x  1 atxhacker atxhacker3204 Mar  2 00:11 axis-remote
>> -rwxr-xr-x  1 atxhacker atxhacker  595611 Mar  5 22:47 classicladder
>> -rwxr-xr-x  1 atxhacker atxhacker2659 Mar  2 00:11 debuglevel
>> -rwxr-xr-x  1 atxhacker atxhacker5770 Mar  1 23:58 elbpcom
>> -rwxr-xr-x  1 atxhacker atxhacker   34595 Mar  5 22:54 genserkins
>> -rwxr-xr-x  1 atxhacker atxhacker   11674 Mar  2 00:11 gladevcp
>> -rwxr-xr-x  1 atxhacker atxhacker  202787 Mar  2 00:12 gmoccapy
>> -rwxr-xr-x  1 atxhacker atxhacker1332 Mar  2 00:12 gremlin
>> -rwxr-xr-x  1 atxhacker atxhacker  77 Mar  2 00:11 gremlin_view
>> -rwxr-xr-x  1 atxhacker atxhacker   31695 Mar  3 21:18 gs2_vfd
>> -rwxr-xr-x  1 atxhacker atxhacker  161755 Mar  2 00:12 gscreen
>> -rwxr-xr-x  1 atxhacker atxhacker  170370 Mar  5 22:48 halcmd
>> -rwxr-xr-x  1 atxhacker atxhacker   54059 Mar  1 23:58 halcompile
>> -rwxr-xr-x  1 atxhacker atxhacker7730 Mar  2 00:11 hal_input
>> -rwxr-xr-x  1 atxhacker atxhacker2465 Mar  2 00:11 hal_manualtoolchange
>> -rwxr-xr-x  1 atxhacker atxhacker   74196 Mar  5 22:48 halmeter
>> -rwxr-xr-x  1 atxhacker atxhacker  108772 Mar  5 22:48 halrmt
>> -rwxr-xr-x  1 atxhacker atxhacker   16451 Mar  3 21:18 halsampler
>> -rwxr-xr-x  1 atxhacker atxhacker  313352 Mar  5 22:48 halscope
>> -rwxr-xr-x  1 atxhacker atxhacker  78 Mar  2 00:11 halshow
>> -rwxr-xr-x  1 atxhacker atxhacker   16662 Mar  3 21:18 halstreamer
>> -rwxr-xr-x  1 atxhacker atxhacker  211041 Mar  5 22:48 halui
>> -rwxr-xr-x  1 atxhacker atxhacker   13174 Mar  2 00:11 hbmgui
>> -rwxr-xr-x  1 atxhacker atxhacker6313 Mar  2 00:11 hexagui
>> -rwxr-xr-x  1 atxhacker atxhacker   47686 Mar  3 21:18 hy_vfd
>> -rwxr-xr-x  1 atxhacker atxhacker   26836 Mar  2 00:11 image-to-gcode
>> -rwxr-xr-x  1 atxhacker atxhacker   15265 Mar  5 22:47 inivar
>> -rwxr-xr-x  1 atxhacker atxhacker  182713 Mar  5 22:54 io
>> -rwxr-xr-x  1 atxhacker atxhacker  189240 Mar  5 22:54 iov2
>> -rwxr-xr-x  1 atxhacker atxhacker  200501 Mar  5 22:48 keystick
>> -rwxr-xr-x  1 atxhacker atxhacker2729 Mar  2 00:11 lintini
>> -rwxr-xr-x  1 atxhacker atxhacker  259421 Mar  5 22:48 linuxcnclcd
>> -rwxr-xr-x  1 atxhacker atxhacker   14654 Mar  5 22:54 linuxcnc_module_helper
>> -rwxr-xr-x  1 atxhacker atxhacker  273576 Mar  5 22:48 linuxcncrsh
>> -rwxr-xr-x  1 atxhacker atxhacker  137167 Mar  5 22:48 linuxcncsvr
>> -rwxr-xr-x  1 atxhacker atxhacker7535 Mar  2 00:11 linuxcnctop
>> -rwxr-xr-x  1 atxhacker atxhacker4437 Mar  2 00:11 maho600gui
>> -rwxr-xr-x  1 atxhacker atxhacker5032 Mar  2 00:11 max5gui
>> -rwxr-xr-x  1 atxhacker atxhacker   62501 Mar  5 22:47 mb2hal
>> -rwxr-xr-x  1 atxhacker atxhacker1596 Mar  2 00:11 mdi
>> -rwxr-xr-x  1 atxhacker atxhacker 3780992 Mar  5 22:54 milltask
>> -rwxr-xr-x  1 atxhacker atxhacker   35254 Mar  5 22:54 motion-logger
>> -rwxr-xr-x  1 atxhacker atxhacker 101 Mar  2 00:11 ngcgui
>> -rwsr-x---  1 root  atxhacker   34014 Mar  1 23:58 pci_read
>> -rwsr-x---  1 root  atxhacker   33978 Mar  1 23:58 pci_write
>> -rwxr-xr-x  1 atxhacker atxhacker  297892 Mar  2 00:11 pncconf
>> -rwxr-xr-x  1 atxhacker atxhacker 187 Oct 24 07:52 profile_axis
>> -rwxr-xr-x  1 atxhacker atxhacker5281 Mar  2 00:11 puma560gui
>> -rwxr-xr-x  1 atxhacker atxhacker4606 Mar  2 00:11 pumagui
>> -rwxr-xr-x  1 atxhacker atxhacker  65 Mar  2 00:11 pyngcgui
>> -rwxr-xr-x  1 atxhacker atxhacker3148 Mar  2 00:11 pyvcp
>> -rwxr-xr-x  1 atxhacker atxhacker 3311487 Mar  5 22:54 rs274
>> -rwsr-x---  1 root  atxhacker  460391 Mar  5 22:47 rtapi_app
>> -rwxr-xr-x  1 atxhacker atxhacker5697 Mar  2 00:11 scaragui
>> -rwxr-xr-x  1 atxhacker atxhacker  337341 Mar  5 22:48 schedrmt
>> -rwxr-xr-x  1 atxhacker atxhacker   19225 Mar  3 21:18 shuttlexpress
>> -rwxr-xr-x  1 atxhacker atxhacker   64769 Mar  2 00:11 stepconf
>> -rwxr-xr-x  1 atxhacker atxhacker2485 Mar  2 00:11 teach-in
>> -rwxr-xr-x  1 atxhacker atxhacker   22296 Mar  1 23:57 test_rtapi_vsnprintf
>> -rwxr-xr-x  1 atxhacker atxhacker  95 

Re: [Emc-users] Need help with X200 VFD modbus

[Danny Miller]

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 debugger.  
Could I just have it do printf()?  Is there any way to call subroutines 
or anything from HAL monitor so I can send commands?

Is qModMaster going to compose read/write packets used by the X200?  
That is, just give it an address to read and it composes the read packet 
and interprets the response packet automatically?



Danny

On 3/6/2016 2:54 AM, Philipp Burch wrote:
> 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
>
>
> --
>
>
> ___
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users

--
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[Dave Cole]

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 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 axis
> -rwxr-xr-x  1 atxhacker atxhacker3204 Mar  2 00:11 axis-remote
> -rwxr-xr-x  1 atxhacker atxhacker  595611 Mar  5 22:47 classicladder
> -rwxr-xr-x  1 atxhacker atxhacker2659 Mar  2 00:11 debuglevel
> -rwxr-xr-x  1 atxhacker atxhacker5770 Mar  1 23:58 elbpcom
> -rwxr-xr-x  1 atxhacker atxhacker   34595 Mar  5 22:54 genserkins
> -rwxr-xr-x  1 atxhacker atxhacker   11674 Mar  2 00:11 gladevcp
> -rwxr-xr-x  1 atxhacker atxhacker  202787 Mar  2 00:12 gmoccapy
> -rwxr-xr-x  1 atxhacker atxhacker1332 Mar  2 00:12 gremlin
> -rwxr-xr-x  1 atxhacker atxhacker  77 Mar  2 00:11 gremlin_view
> -rwxr-xr-x  1 atxhacker atxhacker   31695 Mar  3 21:18 gs2_vfd
> -rwxr-xr-x  1 atxhacker atxhacker  161755 Mar  2 00:12 gscreen
> -rwxr-xr-x  1 atxhacker atxhacker  170370 Mar  5 22:48 halcmd
> -rwxr-xr-x  1 atxhacker atxhacker   54059 Mar  1 23:58 halcompile
> -rwxr-xr-x  1 atxhacker atxhacker7730 Mar  2 00:11 hal_input
> -rwxr-xr-x  1 atxhacker atxhacker2465 Mar  2 00:11 hal_manualtoolchange
> -rwxr-xr-x  1 atxhacker atxhacker   74196 Mar  5 22:48 halmeter
> -rwxr-xr-x  1 atxhacker atxhacker  108772 Mar  5 22:48 halrmt
> -rwxr-xr-x  1 atxhacker atxhacker   16451 Mar  3 21:18 halsampler
> -rwxr-xr-x  1 atxhacker atxhacker  313352 Mar  5 22:48 halscope
> -rwxr-xr-x  1 atxhacker atxhacker  78 Mar  2 00:11 halshow
> -rwxr-xr-x  1 atxhacker atxhacker   16662 Mar  3 21:18 halstreamer
> -rwxr-xr-x  1 atxhacker atxhacker  211041 Mar  5 22:48 halui
> -rwxr-xr-x  1 atxhacker atxhacker   13174 Mar  2 00:11 hbmgui
> -rwxr-xr-x  1 atxhacker atxhacker6313 Mar  2 00:11 hexagui
> -rwxr-xr-x  1 atxhacker atxhacker   47686 Mar  3 21:18 hy_vfd
> -rwxr-xr-x  1 atxhacker atxhacker   26836 Mar  2 00:11 image-to-gcode
> -rwxr-xr-x  1 atxhacker atxhacker   15265 Mar  5 22:47 inivar
> -rwxr-xr-x  1 atxhacker atxhacker  182713 Mar  5 22:54 io
> -rwxr-xr-x  1 atxhacker atxhacker  189240 Mar  5 22:54 iov2
> -rwxr-xr-x  1 atxhacker atxhacker  200501 Mar  5 22:48 keystick
> -rwxr-xr-x  1 atxhacker atxhacker2729 Mar  2 00:11 lintini
> -rwxr-xr-x  1 atxhacker atxhacker  259421 Mar  5 22:48 linuxcnclcd
> -rwxr-xr-x  1 atxhacker atxhacker   14654 Mar  5 22:54 linuxcnc_module_helper
> -rwxr-xr-x  1 atxhacker atxhacker  273576 Mar  5 22:48 linuxcncrsh
> -rwxr-xr-x  1 atxhacker atxhacker  137167 Mar  5 22:48 linuxcncsvr
> -rwxr-xr-x  1 atxhacker atxhacker7535 Mar  2 00:11 linuxcnctop
> -rwxr-xr-x  1 atxhacker atxhacker4437 Mar  2 00:11 maho600gui
> -rwxr-xr-x  1 atxhacker atxhacker5032 Mar  2 00:11 max5gui
> -rwxr-xr-x  1 atxhacker atxhacker   62501 Mar  5 22:47 mb2hal
> -rwxr-xr-x  1 atxhacker atxhacker1596 Mar  2 00:11 mdi
> -rwxr-xr-x  1 atxhacker atxhacker 3780992 Mar  5 22:54 milltask
> -rwxr-xr-x  1 atxhacker atxhacker   35254 Mar  5 22:54 motion-logger
> -rwxr-xr-x  1 atxhacker atxhacker 101 Mar  2 00:11 ngcgui
> -rwsr-x---  1 root  atxhacker   34014 Mar  1 23:58 pci_read
> -rwsr-x---  1 root  atxhacker   33978 Mar  1 23:58 pci_write
> -rwxr-xr-x  1 atxhacker atxhacker  297892 Mar  2 00:11 pncconf
> -rwxr-xr-x  1 atxhacker atxhacker 187 Oct 24 07:52 profile_axis
> -rwxr-xr-x  1 atxhacker atxhacker5281 Mar  2 00:11 puma560gui
> -rwxr-xr-x  1 atxhacker atxhacker4606 Mar  2 00:11 pumagui
> -rwxr-xr-x  1 atxhacker atxhacker  65 Mar  2 00:11 pyngcgui
> -rwxr-xr-x  1 atxhacker atxhacker3148 Mar  2 00:11 pyvcp
> -rwxr-xr-x  1 atxhacker atxhacker 3311487 Mar  5 22:54 rs274
> -rwsr-x---  1 root  atxhacker  460391 Mar  5 22:47 rtapi_app
> -rwxr-xr-x  1 atxhacker atxhacker5697 Mar  2 00:11 scaragui
> -rwxr-xr-x  1 atxhacker atxhacker  337341 Mar  5 22:48 schedrmt
> -rwxr-xr-x  1 atxhacker atxhacker   19225 Mar  3 21:18 shuttlexpress
> -rwxr-xr-x  1 atxhacker atxhacker   64769 Mar  2 00:11 stepconf
> -rwxr-xr-x  1 atxhacker atxhacker2485 Mar  2 00:11 teach-in
> -rwxr-xr-x  1 atxhacker atxhacker   22296 Mar  1 23:57 test_rtapi_vsnprintf
> -rwxr-xr-x  1 atxhacker atxhacker  95 Mar  2 00:11 tooledit
> -rwxr-xr-x  1 atxhacker atxhacker   38457 Mar  2 00:11 touchy
> -rwxr-xr-x  1 atxhacker atxhacker2042 Mar  2 00:11 tracking-test
> -rwxr-xr-x  1 atxhacker atxhacker   30852 Mar  5 22:48 vfdb_vfd
> -rwxr-xr-x  1 atxhacker atxhacker   35495 Mar  5 22:47 vfs11_vfd
> -rwxr-xr-x  1 atxhacker atxhacker   21570 Mar  5 22:48 wj200_vfd
> -rwxr-xr-x  1 atxhacker atxhacker   21603 Mar  5 22:48 x200_vfd
> -rwxr-xr-x  1 atxhacker atxhacker   47619 Mar  5 22:47 xhc-hb04
> 

Re: [Emc-users] Need help with X200 VFD modbus

[Philipp Burch]

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

Re: [Emc-users] Need help with X200 VFD modbus

[Danny Miller]

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
>>
>>
>>  Sebastian Kuzminsky  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: 

Re: [Emc-users] Need help with X200 VFD modbus

[Philipp Burch]

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  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

Re: [Emc-users] Need help with X200 VFD modbus

[dannym]

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  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

Re: [Emc-users] Need help with X200 VFD modbus

[dannym]

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 axis
-rwxr-xr-x  1 atxhacker atxhacker3204 Mar  2 00:11 axis-remote
-rwxr-xr-x  1 atxhacker atxhacker  595611 Mar  5 22:47 classicladder
-rwxr-xr-x  1 atxhacker atxhacker2659 Mar  2 00:11 debuglevel
-rwxr-xr-x  1 atxhacker atxhacker5770 Mar  1 23:58 elbpcom
-rwxr-xr-x  1 atxhacker atxhacker   34595 Mar  5 22:54 genserkins
-rwxr-xr-x  1 atxhacker atxhacker   11674 Mar  2 00:11 gladevcp
-rwxr-xr-x  1 atxhacker atxhacker  202787 Mar  2 00:12 gmoccapy
-rwxr-xr-x  1 atxhacker atxhacker1332 Mar  2 00:12 gremlin
-rwxr-xr-x  1 atxhacker atxhacker  77 Mar  2 00:11 gremlin_view
-rwxr-xr-x  1 atxhacker atxhacker   31695 Mar  3 21:18 gs2_vfd
-rwxr-xr-x  1 atxhacker atxhacker  161755 Mar  2 00:12 gscreen
-rwxr-xr-x  1 atxhacker atxhacker  170370 Mar  5 22:48 halcmd
-rwxr-xr-x  1 atxhacker atxhacker   54059 Mar  1 23:58 halcompile
-rwxr-xr-x  1 atxhacker atxhacker7730 Mar  2 00:11 hal_input
-rwxr-xr-x  1 atxhacker atxhacker2465 Mar  2 00:11 hal_manualtoolchange
-rwxr-xr-x  1 atxhacker atxhacker   74196 Mar  5 22:48 halmeter
-rwxr-xr-x  1 atxhacker atxhacker  108772 Mar  5 22:48 halrmt
-rwxr-xr-x  1 atxhacker atxhacker   16451 Mar  3 21:18 halsampler
-rwxr-xr-x  1 atxhacker atxhacker  313352 Mar  5 22:48 halscope
-rwxr-xr-x  1 atxhacker atxhacker  78 Mar  2 00:11 halshow
-rwxr-xr-x  1 atxhacker atxhacker   16662 Mar  3 21:18 halstreamer
-rwxr-xr-x  1 atxhacker atxhacker  211041 Mar  5 22:48 halui
-rwxr-xr-x  1 atxhacker atxhacker   13174 Mar  2 00:11 hbmgui
-rwxr-xr-x  1 atxhacker atxhacker6313 Mar  2 00:11 hexagui
-rwxr-xr-x  1 atxhacker atxhacker   47686 Mar  3 21:18 hy_vfd
-rwxr-xr-x  1 atxhacker atxhacker   26836 Mar  2 00:11 image-to-gcode
-rwxr-xr-x  1 atxhacker atxhacker   15265 Mar  5 22:47 inivar
-rwxr-xr-x  1 atxhacker atxhacker  182713 Mar  5 22:54 io
-rwxr-xr-x  1 atxhacker atxhacker  189240 Mar  5 22:54 iov2
-rwxr-xr-x  1 atxhacker atxhacker  200501 Mar  5 22:48 keystick
-rwxr-xr-x  1 atxhacker atxhacker2729 Mar  2 00:11 lintini
-rwxr-xr-x  1 atxhacker atxhacker  259421 Mar  5 22:48 linuxcnclcd
-rwxr-xr-x  1 atxhacker atxhacker   14654 Mar  5 22:54 linuxcnc_module_helper
-rwxr-xr-x  1 atxhacker atxhacker  273576 Mar  5 22:48 linuxcncrsh
-rwxr-xr-x  1 atxhacker atxhacker  137167 Mar  5 22:48 linuxcncsvr
-rwxr-xr-x  1 atxhacker atxhacker7535 Mar  2 00:11 linuxcnctop
-rwxr-xr-x  1 atxhacker atxhacker4437 Mar  2 00:11 maho600gui
-rwxr-xr-x  1 atxhacker atxhacker5032 Mar  2 00:11 max5gui
-rwxr-xr-x  1 atxhacker atxhacker   62501 Mar  5 22:47 mb2hal
-rwxr-xr-x  1 atxhacker atxhacker1596 Mar  2 00:11 mdi
-rwxr-xr-x  1 atxhacker atxhacker 3780992 Mar  5 22:54 milltask
-rwxr-xr-x  1 atxhacker atxhacker   35254 Mar  5 22:54 motion-logger
-rwxr-xr-x  1 atxhacker atxhacker 101 Mar  2 00:11 ngcgui
-rwsr-x---  1 root  atxhacker   34014 Mar  1 23:58 pci_read
-rwsr-x---  1 root  atxhacker   33978 Mar  1 23:58 pci_write
-rwxr-xr-x  1 atxhacker atxhacker  297892 Mar  2 00:11 pncconf
-rwxr-xr-x  1 atxhacker atxhacker 187 Oct 24 07:52 profile_axis
-rwxr-xr-x  1 atxhacker atxhacker5281 Mar  2 00:11 puma560gui
-rwxr-xr-x  1 atxhacker atxhacker4606 Mar  2 00:11 pumagui
-rwxr-xr-x  1 atxhacker atxhacker  65 Mar  2 00:11 pyngcgui
-rwxr-xr-x  1 atxhacker atxhacker3148 Mar  2 00:11 pyvcp
-rwxr-xr-x  1 atxhacker atxhacker 3311487 Mar  5 22:54 rs274
-rwsr-x---  1 root  atxhacker  460391 Mar  5 22:47 rtapi_app
-rwxr-xr-x  1 atxhacker atxhacker5697 Mar  2 00:11 scaragui
-rwxr-xr-x  1 atxhacker atxhacker  337341 Mar  5 22:48 schedrmt
-rwxr-xr-x  1 atxhacker atxhacker   19225 Mar  3 21:18 shuttlexpress
-rwxr-xr-x  1 atxhacker atxhacker   64769 Mar  2 00:11 stepconf
-rwxr-xr-x  1 atxhacker atxhacker2485 Mar  2 00:11 teach-in
-rwxr-xr-x  1 atxhacker atxhacker   22296 Mar  1 23:57 test_rtapi_vsnprintf
-rwxr-xr-x  1 atxhacker atxhacker  95 Mar  2 00:11 tooledit
-rwxr-xr-x  1 atxhacker atxhacker   38457 Mar  2 00:11 touchy
-rwxr-xr-x  1 atxhacker atxhacker2042 Mar  2 00:11 tracking-test
-rwxr-xr-x  1 atxhacker atxhacker   30852 Mar  5 22:48 vfdb_vfd
-rwxr-xr-x  1 atxhacker atxhacker   35495 Mar  5 22:47 vfs11_vfd
-rwxr-xr-x  1 atxhacker atxhacker   21570 Mar  5 22:48 wj200_vfd
-rwxr-xr-x  1 atxhacker atxhacker   21603 Mar  5 22:48 x200_vfd
-rwxr-xr-x  1 atxhacker atxhacker   47619 Mar  5 22:47 xhc-hb04
-rwxr-xr-x  1 atxhacker atxhacker  282573 Mar  5 22:48 xlinuxcnc
-rwxr-xr-x  1 atxhacker atxhacker4263 Mar  1 23:29 yapps


Danny

 dan...@austin.rr.com wrote: 
> 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 

Re: [Emc-users] Need help with X200 VFD modbus

[dannym]

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/lib 
-Wl,-rpath,/home/atxhacker/linuxcnc-2.7.4/lib -shared -o ../lib/python/gcode.so 
objects/emc/rs274ngc/gcodemodule.o ../lib/librs274.so.0 -lstdc++
Linking ../rtlib/abs.so
ld: no input files
make: *** [../rtlib/abs.so] Error 1

then I did "sudo make setuid"
hal/user_comps/vfdb_vfd/Submakefile:11: warning: overriding commands for target 
`../bin/vfdb_vfd'
hal/user_comps/vfdb_vfd/Submakefile:11: warning: ignoring old commands for 
target `../bin/vfdb_vfd'
chown root ../bin/rtapi_app
chmod 4750 ../bin/rtapi_app


source ../scripts/rip-environment
This script only needs to be run once per shell session.

type "linuxcnc" , loads, lets me select a HAL file, then:
LINUXCNC - 2.7.4
Machine configuration directory is '/home/atxhacker/linuxcnc/configs'
Machine configuration file is '7i92_spid.ini'
Starting LinuxCNC...
inifile: warning: File contains DOS-style line endings.
emc/iotask/ioControl.cc 768: can't load tool table.
Found file(REL): ./7i92_spid.hal
hal_lib: dlopen: /home/atxhacker/linuxcnc-2.7.4/rtlib/hal_lib.so: cannot open 
shared object file: No such file or directory
Note: Using POSIX realtime
gantrykins: dlopen: /home/atxhacker/linuxcnc-2.7.4/rtlib/gantrykins.so: cannot 
open shared object file: No such file or directory
./7i92_spid.hal:31: waitpid failed /home/atxhacker/linuxcnc-2.7.4/bin/rtapi_app 
gantrykins
./7i92_spid.hal:31: /home/atxhacker/linuxcnc-2.7.4/bin/rtapi_app exited without 
becoming ready
./7i92_spid.hal:31: insmod for gantrykins failed, returned -1
Shutting down and cleaning up LinuxCNC...
hal_lib: dlopen: /home/atxhacker/linuxcnc-2.7.4/rtlib/hal_lib.so: cannot open 
shared object file: No such file or directory
Note: Using POSIX realtime
LinuxCNC terminated with an error.  You can find more information in the log:
/home/atxhacker/linuxcnc_debug.txt
and
/home/atxhacker/linuxcnc_print.txt
as well as in the output of the shell command 'dmesg' and in the terminal


Danny

 Sebastian Kuzminsky  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 

Re: [Emc-users] Need help with X200 VFD modbus

[Sebastian Kuzminsky]

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

--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[dannym]

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-realtime=uspace
./configure: line 2025: config.log: Permission denied
./configure: line 2035: config.log: Permission denied

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

Applications Menu-> Linuxcnc -> select HAL file:
 ./7i92_spid.hal:313: execv(x200_vfd): No such file or directory

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
./7i92_spid.hal:31: /home/atxhacker/linuxcnc-2.7.4/bin/rtapi_app exited without 
becoming ready
./7i92_spid.hal:31: insmod for gantrykins failed, returned -1
Shutting down and cleaning up LinuxCNC...

cd ~/linuxcnc-2.7.4/scripts
 ... same thing
cd ~/linuxcnc-2.7.4/
 ... same thing

I note that in running from linuxcnc-2.7.4, the execv-can't-find-x200_vfd isn't 
the error anymore.

I did try "sudo linuxcnc", but then my HAL file isn't there, only "Sample 
Configurations".  The whole "My Configurations" tab is gone?


Danny

 Sebastian Kuzminsky  wrote: 
> 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 error info 
> > it shows says "execv x200_vfd: no such file or directory".
> 
> If i correctly understand the changes you've made then after a 
> successful compile you should have both bin/x200_vfd and bin/wj200_vfd 
> in your linuxcnc checkout directory.
> 
> You're building linuxcnc from source, what we call a "run in place" 
> configuration (as opposed to building linuxcnc into a debian package, 
> installing the deb, and running it from the system install path).  This 
> means you need to run "source ./scripts/rip-environment" in order to 
> find the x200_vfd executable (in the terminal you're staring linuxcnc 
> from).  So something like this:
> 
> cd src
> ./configure
> make
> sudo make setuid
> source ../scripts/rip-environment
> 
> At that point, "which x200_vfd" should find it in the bin dir of your 
> linuxcnc source tree, and starting linuxcnc (from that terminal) should 
> let it start.
> 
> 
> Ah, one other thing to check.  Are you running on rtai or rt-preempt? 
> You can check with "uname -a".  If you're on rt-preempt your configure 
> line needs to be "./configure --with-realtime=uspace".  I think it 
> detects RTAI automatically, so no special configure argument is needed 
> for that (though I always provide one anyway, 
> "--with-realtime=/usr/realtime-*").
> 
> 
> -- 
> Sebastian Kuzminsky


--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[Sebastian Kuzminsky]

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 error info 
> it shows says "execv x200_vfd: no such file or directory".

If i correctly understand the changes you've made then after a 
successful compile you should have both bin/x200_vfd and bin/wj200_vfd 
in your linuxcnc checkout directory.

You're building linuxcnc from source, what we call a "run in place" 
configuration (as opposed to building linuxcnc into a debian package, 
installing the deb, and running it from the system install path).  This 
means you need to run "source ./scripts/rip-environment" in order to 
find the x200_vfd executable (in the terminal you're staring linuxcnc 
from).  So something like this:

cd src
./configure
make
sudo make setuid
source ../scripts/rip-environment

At that point, "which x200_vfd" should find it in the bin dir of your 
linuxcnc source tree, and starting linuxcnc (from that terminal) should 
let it start.


Ah, one other thing to check.  Are you running on rtai or rt-preempt? 
You can check with "uname -a".  If you're on rt-preempt your configure 
line needs to be "./configure --with-realtime=uspace".  I think it 
detects RTAI automatically, so no special configure argument is needed 
for that (though I always provide one anyway, 
"--with-realtime=/usr/realtime-*").


-- 
Sebastian Kuzminsky

--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[dannym]

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 directory".

Yeah moving the executable to a new directory manually was pretty crude.  I 
deleted it from the new destination immediately. Didn't work, anyhow, just 
generated that new RTAPI error.

Danny


 Sebastian Kuzminsky  wrote: 
> 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't run most of the build as 
> root.  ./configure and make should be run as your regular user, only the 
> last "sudo make setuid" step should be run with sudo.
> 
> 
> > That compiled ok, but running linuxcnc got "execv x200_vfd no such file or 
> > directory".
> >
> > Tried your halcompile link.  Build, but still the same exev error.  
> > x200_vfd executable was in ~/linuxcnc-2.7.4/bin.
> 
> Did you modify the code in src/hal/user_comps/wj200_vfd while leaving 
> the directory name unchanged, or did you copy 
> src/hal/user_comps/wj200_vfd to src/hal/user_comps/x200_vfd?
> 
> If you did the latter like i suggested, then you'd have to also edit 
> src/Makefile to add your new driver.  Search for wj200 in that file and 
> add your new x200 right next to it, run "make" again, and it should 
> build and install.
> 
> If you can push a branch with your changes to github I'll have an easier 
> time seeing what you're doing and offering useful help.
> 
> 
> > So just stabbing, we moved x200_vfd into /usr/bin, and now it gives:
> > RTAPI: ERROR: could not open shared memory (No such file or directory)
> > HAL: ERROR: could not initialize RTAPI
> > ./7i92_spid.hal:313: waitpid failed x200_vfd x200_vfd
> > ./7i92_spid.hal:313: x200_vfd exited without becoming ready
> 
> You shouldn't copy files outside of your home directory by hand.  I 
> understand you're experimenting, trying to get things to work, this is 
> just and FYI/PSA from an old unix geek  ;-)
> 
> 
> -- 
> Sebastian Kuzminsky


--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[Sebastian Kuzminsky]

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't run most of the build as 
root.  ./configure and make should be run as your regular user, only the 
last "sudo make setuid" step should be run with sudo.


> That compiled ok, but running linuxcnc got "execv x200_vfd no such file or 
> directory".
>
> Tried your halcompile link.  Build, but still the same exev error.  x200_vfd 
> executable was in ~/linuxcnc-2.7.4/bin.

Did you modify the code in src/hal/user_comps/wj200_vfd while leaving 
the directory name unchanged, or did you copy 
src/hal/user_comps/wj200_vfd to src/hal/user_comps/x200_vfd?

If you did the latter like i suggested, then you'd have to also edit 
src/Makefile to add your new driver.  Search for wj200 in that file and 
add your new x200 right next to it, run "make" again, and it should 
build and install.

If you can push a branch with your changes to github I'll have an easier 
time seeing what you're doing and offering useful help.


> So just stabbing, we moved x200_vfd into /usr/bin, and now it gives:
> RTAPI: ERROR: could not open shared memory (No such file or directory)
> HAL: ERROR: could not initialize RTAPI
> ./7i92_spid.hal:313: waitpid failed x200_vfd x200_vfd
> ./7i92_spid.hal:313: x200_vfd exited without becoming ready

You shouldn't copy files outside of your home directory by hand.  I 
understand you're experimenting, trying to get things to work, this is 
just and FYI/PSA from an old unix geek  ;-)


-- 
Sebastian Kuzminsky

--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[dannym]

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 halcompile link.  Build, but still the same exev error.  x200_vfd 
executable was in ~/linuxcnc-2.7.4/bin.

So just stabbing, we moved x200_vfd into /usr/bin, and now it gives:
RTAPI: ERROR: could not open shared memory (No such file or directory)
HAL: ERROR: could not initialize RTAPI
./7i92_spid.hal:313: waitpid failed x200_vfd x200_vfd
./7i92_spid.hal:313: x200_vfd exited without becoming ready

??


Danny

 Sebastian Kuzminsky  wrote: 
> 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.
> > 
> > The component is written in the "comp" format, so there is a chance
> > that halcompile will work.
> > http://linuxcnc.org/docs/2.7/html/hal/comp.html
> > 
> > There is also a fair chance that it won't work due to the includes,
> > but it is probably worth a try.
> > 
> > If you change the name of the file you need to also change the name of
> > the component (in the "component" line of the source file)
> 
> It's a little hairier than that, the wj200_vfd is written as a .comp
> file but it needs to link against libmodbus, so the normal halcompile
> work flow does not work.
> 
> Danny, check out the linuxcnc git repo (instructions here:
> http://linuxcnc.org/docs/html/code/contributing-to-linuxcnc.html#_the_git_revision_control_system).
> 
> Make sure you can build the code before you make any changes.  See
> instructions in the top-level README file for details on how to build.
> 
> In src/hal/user_comps there's a subdirectory named wj200_vfd, you're
> probably best off copying that whole directory, renaming all the files
> and variables from wj200 to x200, and making your modifications in the
> renamed files.
> 
> Let me know if you get stuck in this process, I'll be happy to help.
> 
> 
> -- 
> Sebastian Kuzminsky
> 
> --
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
> ___
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users


--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[Sebastian Kuzminsky]

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.
> 
> The component is written in the "comp" format, so there is a chance
> that halcompile will work.
> http://linuxcnc.org/docs/2.7/html/hal/comp.html
> 
> There is also a fair chance that it won't work due to the includes,
> but it is probably worth a try.
> 
> If you change the name of the file you need to also change the name of
> the component (in the "component" line of the source file)

It's a little hairier than that, the wj200_vfd is written as a .comp
file but it needs to link against libmodbus, so the normal halcompile
work flow does not work.

Danny, check out the linuxcnc git repo (instructions here:
http://linuxcnc.org/docs/html/code/contributing-to-linuxcnc.html#_the_git_revision_control_system).

Make sure you can build the code before you make any changes.  See
instructions in the top-level README file for details on how to build.

In src/hal/user_comps there's a subdirectory named wj200_vfd, you're
probably best off copying that whole directory, renaming all the files
and variables from wj200 to x200, and making your modifications in the
renamed files.

Let me know if you get stuck in this process, I'll be happy to help.


-- 
Sebastian Kuzminsky

--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[andy pugh]

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 there is a chance
that halcompile will work.
http://linuxcnc.org/docs/2.7/html/hal/comp.html

There is also a fair chance that it won't work due to the includes,
but it is probably worth a try.

If you change the name of the file you need to also change the name of
the component (in the "component" line of the source file)

-- 
atp
If you can't fix it, you don't own it.
http://www.ifixit.com/Manifesto

--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[Danny Miller]

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 wj200 put them at different coil numbers.

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.

Danny

On 3/1/2016 9: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 if I change it to 
>> "baud=hahahhaha", there's no error for it being a non-number either.
>>
>> Could the wj200_vfd code have a bug in accepting arguments?
> It's certainly possible that there's a bug in the WJ200 driver, but at
> this time I don't know of any.
>
> Looking at the code, i see that it expects arguments to have two leading
> dashes, for example "--baud=12345".
>
> I also see that it does not attempt to validate the --baud=NUMBER
> argument, so it makes sense that giving the argument "--baud=huehuehue"
> leaves the baud rate at 9600 and does not complain.  (I'm not saying it
> *should* be that way, just saying that's what the code currently does.)
>
>


--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[Dave Cole]

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 if I change it to 
>> "baud=hahahhaha", there's no error for it being a non-number either.
>>
>> Could the wj200_vfd code have a bug in accepting arguments?
> It's certainly possible that there's a bug in the WJ200 driver, but at
> this time I don't know of any.
>
> Looking at the code, i see that it expects arguments to have two leading
> dashes, for example "--baud=12345".
>
> I also see that it does not attempt to validate the --baud=NUMBER
> argument, so it makes sense that giving the argument "--baud=huehuehue"
> leaves the baud rate at 9600 and does not complain.  (I'm not saying it
> *should* be that way, just saying that's what the code currently does.)
>

Can you set the drive to 9600 baud and see if you can establish a comm 
link?

Dave

--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[Sebastian Kuzminsky]

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 for it being a non-number either.
> 
> Could the wj200_vfd code have a bug in accepting arguments?

It's certainly possible that there's a bug in the WJ200 driver, but at
this time I don't know of any.

Looking at the code, i see that it expects arguments to have two leading
dashes, for example "--baud=12345".

I also see that it does not attempt to validate the --baud=NUMBER
argument, so it makes sense that giving the argument "--baud=huehuehue"
leaves the baud rate at 9600 and does not complain.  (I'm not saying it
*should* be that way, just saying that's what the code currently does.)


-- 
Sebastian Kuzminsky

--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[dannym]

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 a bug in accepting arguments?

Danny

 dan...@austin.rr.com wrote: 
> 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 generated.  
> 
> So, chances are I'm not setting the baud rate- how do I do that?
> 
> 
> Danny
> 
>  dan...@austin.rr.com wrote: 
> > 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:
> > > > [...]
> > > > 
> > > > 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.reverse
> > > > net spindle-at-speed wj200-vfd.0.is-at-speed
> > > > 
> > > 
> > > Maybe it's a stupid question, but: Have you also connected the nets
> > > spindle-on, spindle-cw and spindle-at-speed to the motion component?
> > > 
> > > I.e. something like
> > > 
> > > net spindle-on motion.spindle-on
> > > net spindle-cw motion.spindle-forward
> > > net spindle-at-speed motion.spindle-at-speed
> > > 
> > > See: http://linuxcnc.org/docs/2.7/html/man/man9/motion.9.html
> > > 
> > > Then, wj200-vfd.0.commanded-frequency is actually a pin, which you
> > > can/should set dynamically as well:
> > > 
> > > net spindle-rps motion.spindle-speed-out-rps-abs
> > > net spindle-rps wj200-vfd.0.commanded-frequency
> > > 
> > > Good luck!
> > > 
> > > Bye,
> > > Philipp
> > > 
> > 
> > 
> > --
> > Site24x7 APM Insight: Get Deep Visibility into Application Performance
> > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> > Monitor end-to-end web transactions and take corrective actions now
> > Troubleshoot faster and improve end-user experience. Signup Now!
> > http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
> > ___
> > Emc-users mailing list
> > Emc-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/emc-users
> 
> 
> --
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
> ___
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users


--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[dannym]

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 generated.  

So, chances are I'm not setting the baud rate- how do I do that?


Danny

 dan...@austin.rr.com wrote: 
> 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:
> > > [...]
> > > 
> > > 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.reverse
> > > net spindle-at-speed wj200-vfd.0.is-at-speed
> > > 
> > 
> > Maybe it's a stupid question, but: Have you also connected the nets
> > spindle-on, spindle-cw and spindle-at-speed to the motion component?
> > 
> > I.e. something like
> > 
> > net spindle-on motion.spindle-on
> > net spindle-cw motion.spindle-forward
> > net spindle-at-speed motion.spindle-at-speed
> > 
> > See: http://linuxcnc.org/docs/2.7/html/man/man9/motion.9.html
> > 
> > Then, wj200-vfd.0.commanded-frequency is actually a pin, which you
> > can/should set dynamically as well:
> > 
> > net spindle-rps motion.spindle-speed-out-rps-abs
> > net spindle-rps wj200-vfd.0.commanded-frequency
> > 
> > Good luck!
> > 
> > Bye,
> > Philipp
> > 
> 
> 
> --
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
> ___
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users


--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[Sebastian Kuzminsky]

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 try 
> to connect "spindle-on" to an unstated "motion" component?

Nothing unstated happens.

"net spindle-on motion.spindle-on" simply connects the "spindle-on" net
to the "motion.spindle-on" pin.  If you want that net to relay the
information to some other pin, you need to explicitly connect that other
pin to the net.

If you say:

net spindle-on motion.spindle-on
net spindle-on wj200-vfd.0.run

Then the spindle-on net will connect the motion.spindle-on pin to the
wj200-vfd.0.run pin, which is probably what you want.


-- 
Sebastian Kuzminsky

--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[dannym]

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" component?

Danny


 Philipp Burch  wrote: 
> 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.reverse
> > net spindle-at-speed wj200-vfd.0.is-at-speed
> > 
> 
> Maybe it's a stupid question, but: Have you also connected the nets
> spindle-on, spindle-cw and spindle-at-speed to the motion component?
> 
> I.e. something like
> 
> net spindle-on motion.spindle-on
> net spindle-cw motion.spindle-forward
> net spindle-at-speed motion.spindle-at-speed
> 
> See: http://linuxcnc.org/docs/2.7/html/man/man9/motion.9.html
> 
> Then, wj200-vfd.0.commanded-frequency is actually a pin, which you
> can/should set dynamically as well:
> 
> net spindle-rps motion.spindle-speed-out-rps-abs
> net spindle-rps wj200-vfd.0.commanded-frequency
> 
> Good luck!
> 
> Bye,
> Philipp
> 


--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[Philipp Burch]

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

loadrt watchdog num_inputs=1
addf watchdog.0.process base-thread
addf watchdog.0.set-timeouts servo-thread

setp watchdog.0.timeout-0 0.1

net vfd-wdt wj200-vfd.0.watchdog-out => watchdog.0.input-0
net machine-en motion.enable-out => watchdog.0.enable-in
net vfd-ok watchdog.0.ok-out

HAL syntax and naming without warranty, as I'm just writing this from
memory and the quoted manpages.

Then you can connect vfd-ok to whatever you want (or whatever should
know if the VFD is responding). The watchdog timeout will need to be set
in accordance with the VFD update rate. For a userspace component, I'd
not go much below 100ms to avoid false-positives if a response takes a
moment longer to be processed.

Bye,
Philipp

On 29.02.2016 19:59, dan...@austin.rr.com wrote:
> 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:
>>> [...]
>>>
>>> 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.reverse
>>> net spindle-at-speed wj200-vfd.0.is-at-speed
>>>
>>
>> Maybe it's a stupid question, but: Have you also connected the nets
>> spindle-on, spindle-cw and spindle-at-speed to the motion component?
>>
>> I.e. something like
>>
>> net spindle-on motion.spindle-on
>> net spindle-cw motion.spindle-forward
>> net spindle-at-speed motion.spindle-at-speed
>>
>> See: http://linuxcnc.org/docs/2.7/html/man/man9/motion.9.html
>>
>> Then, wj200-vfd.0.commanded-frequency is actually a pin, which you
>> can/should set dynamically as well:
>>
>> net spindle-rps motion.spindle-speed-out-rps-abs
>> net spindle-rps wj200-vfd.0.commanded-frequency
>>
>> Good luck!
>>
>> Bye,
>> Philipp
>>
> 



signature.asc
Description: OpenPGP digital signature
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[dannym]

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:
> > [...]
> > 
> > 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.reverse
> > net spindle-at-speed wj200-vfd.0.is-at-speed
> > 
> 
> Maybe it's a stupid question, but: Have you also connected the nets
> spindle-on, spindle-cw and spindle-at-speed to the motion component?
> 
> I.e. something like
> 
> net spindle-on motion.spindle-on
> net spindle-cw motion.spindle-forward
> net spindle-at-speed motion.spindle-at-speed
> 
> See: http://linuxcnc.org/docs/2.7/html/man/man9/motion.9.html
> 
> Then, wj200-vfd.0.commanded-frequency is actually a pin, which you
> can/should set dynamically as well:
> 
> net spindle-rps motion.spindle-speed-out-rps-abs
> net spindle-rps wj200-vfd.0.commanded-frequency
> 
> Good luck!
> 
> Bye,
> Philipp
> 


--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Need help with X200 VFD modbus

[Philipp Burch]

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.reverse
> net spindle-at-speed wj200-vfd.0.is-at-speed
> 

Maybe it's a stupid question, but: Have you also connected the nets
spindle-on, spindle-cw and spindle-at-speed to the motion component?

I.e. something like

net spindle-on motion.spindle-on
net spindle-cw motion.spindle-forward
net spindle-at-speed motion.spindle-at-speed

See: http://linuxcnc.org/docs/2.7/html/man/man9/motion.9.html

Then, wj200-vfd.0.commanded-frequency is actually a pin, which you
can/should set dynamically as well:

net spindle-rps motion.spindle-speed-out-rps-abs
net spindle-rps wj200-vfd.0.commanded-frequency

Good luck!

Bye,
Philipp



signature.asc
Description: OpenPGP digital signature
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

[Emc-users] Need help with X200 VFD modbus

[Danny Miller]

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 respond to Modbus and has the proper number of motor poles 
and all that.

I found the WJ200 VFD code, and they're both Hitachi, and use the same 
Modbus commands.  Same basic control regs.  AFAIK the code should work.

I don't know what all I need to do here.  I just need to have Sxxx set 
the RPM, M3 makes it go, M0 makes it stop initially, but I will need 
some feedback (under the Mach3 setup, if the VFD overloaded and shut 
down or even if its breaker was off, nothing told Mach3).  I'd like to 
have a display show actual RPM (as it ramps up/down) and VFD current but 
that's very far from "essential".

I found the WJ200 man page, but I don't know what all I need to do. 
Google found me snippets of .hal code I put into my .hal.  I added 
something that I think should change the baud rate, my VFD is set to 19200.

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.reverse
net spindle-at-speed wj200-vfd.0.is-at-speed

No error messages, but M3 has no effect.  Well, I would expect more 
needs to be done, that's the extent of what I know to do.  I don't know 
what else to look up.  Surely needs something on the .ini  file but I 
can't just randomly mash the keyboard, I'll get the script for Hamlet 
before a working LinuxCNC config.  Could I get a little help here?

Danny







--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users