Torch Breakaway and Torch Pulse

rodw wrote:

I think the lead developer is lucky bugs are reported here on on the issues register. I'm sure the official view is that the LD is a gun programmer cos there is never any issues reported on his code ......

rodw wrote:

I think the lead developer is lucky bugs are reported here on on the issues register. I'm sure the official view is that the LD is a gun programmer cos there is never any issues reported on his code ......

NOTE: PlasmaC now uses the motion.motion-type HAL pin. If your configuration already uses this you will need to do some HAL editing.

unlinkp motion.motion-type
net ohmic:type => or2.1.in0
net plasmac:motion-type => or2.1.in1
net or2.1.out => motion.motion-type

twopass: Error in file ./plasma_connections.hal:
    Signal 'plasmac:motion-type' of type 's32' cannot add pin 'or2.1.in1' of type 'bit'

phillc54 wrote:

I did look at what I could find on the ohmic component but didn't see that pin being used, I didn't realise there were two models.

You shouldn't need to or it, just net the plasmac:motion-type signal to the ohmic.motion-type pin

net ohmic:type => plasmac:motion-type

I noticed the folder structure changed. I was a bit confused because my table was named "plasmac" (a stupid idea in retrospect). Are there any ill effects of having the machine name match the new naming convention? One thing that is confusing is I now have 2 plasmac folders (one in linuxcnc\configs and one in linuxcnc\configs\plasmac). Another thing is that within the second plasmac folder, there is a plasmac.hal which appears to be a dummy .hal file for dummies like me . Maybe it might be prudent to put a note in the user guide to advise naming it ANYTHING but "plasmac" Sometimes I cant get out of my own way haha. It's like these things just find me lol

rodw wrote:

Yes, ohmic2.comp was a work in progress to fix some of the issues with ohmic.comp on water tables but its not final as I had some issues afterwards and I need my table back together to test it works properly...

Once that is done, I 'll be leaning on the LD to add some adjustment capability in the Plasmac GUI .....
Its the kinda thing that may change from job to job. eg Ally might be different from steel.

snowgoer540 wrote:

phillc54 wrote:

I did look at what I could find on the ohmic component but didn't see that pin being used, I didn't realise there were two models.

You shouldn't need to or it, just net the plasmac:motion-type signal to the ohmic.motion-type pin

Yea, it's a bit messy at the moment, Rod started a ohmic2.comp when we were having the water in the torch issues. He uses the aforementioned pin to turn the ohmic relay on and stay on the entire time a program is executing.

So just?:

net ohmic:type => plasmac:motion-type

net plasmac:motion-type => ohmic.motion-type

1. Should there be an error associated with trying to pulse the torch and either the float switch or the breakaway (or both) is tripped? It might alleviate some inquiries here at a later date?

2. I noticed the folder structure changed. I was a bit confused because my table was named "plasmac" (a stupid idea in retrospect). Are there any ill effects of having the machine name match the new naming convention? One thing that is confusing is I now have 2 plasmac folders (one in linuxcnc\configs and one in linuxcnc\configs\plasmac). Another thing is that within the second plasmac folder, there is a plasmac.hal which appears to be a dummy .hal file for dummies like me . Maybe it might be prudent to put a note in the user guide to advise naming it ANYTHING but "plasmac" Sometimes I cant get out of my own way haha. It's like these things just find me lol

3. It looks like in the user guide that some "<machine_name>" references are missing the ">" (they read "<machine_name" currently in the manual).

4. Last one, I think. I noticed that pictures are back in the devel (master) version of the user guide. How did you fix that?!

phillc54 wrote:

snowgoer540 wrote:

1. Should there be an error associated with trying to pulse the torch and either the float switch or the breakaway (or both) is tripped? It might alleviate some inquiries here at a later date?

Dunno, see what others think.

phillc54 wrote:

comment out your existing motion-type stuffs then:

net plasmac:motion-type => ohmic.motion-type

Thanks, my editing and proof reading is getting worse, want another job?