Another plasma component...

Phill

I am trying this on a clone of your github/phillc54/linuxcnc-plasmac branch. This is still on my desk machine so there is no other linuxcnc installation.

I enter
jd@deskmonsterll:~$ . plasmac/scripts/rip-environment
jd@deskmonsterll:~$ linuxcnc
The first time in a session then just
jd@deskmonsterll:~$ linuxcnc

John

John,

OK, looks like you will need to get the configobj module, there may be more modules required as you progress...

Cheers, Phill.

P.S.
Yes, I would be interested in being able to provide ohmic probing as well.

John,

Did you do linuxcnc.org/docs/devel/html/code/buildi...g-Build-Dependencies
If you did then I would have thought that all dependencies would have been loaded.

Cheers, Phill.

phillc54 wrote: P.S.
Yes, I would be interested in being able to provide ohmic probing as well.

From a system perspective, this is pretty easy. Just provide one more pin that is ORed with the float switch and use the output for probing.

The other thing I had trouble with was the probe becoming enabled while cutting. So becasue I used a gcode touch off routine, I set a digital output from the gcode before the probing sequence and reset it at the end of the routine. I then ANDed that with the probe input so it would only trigger when we were in the probing sequence. I Was thinking I could then sense when the probe/ohmic sensing was triggered while cutting (digital output not asserted) and wondered if I made an immediate offset that was equivalent to the cut height. I've had the gear to add Ohmic sensing here for a month and have not had time to modify the machine to implement it. (I need to fit a bigger drag chain as part of this).

Dunno if my ramblings help...

Rod

I OR2 the ohmic probe signal and the float switch signal and feed the output to the probe input on my current system. Out of an abundance of caution my ohmic sensing circuit is only connected to the work and the torch shield through a relay (well actually 2 because I only have SPST relays on my chinacom relay board) when actually doing the probing. I do have a GUI button so I can do a test connection for trouble shooting a shorted torch tip (happens more often than you think with the Finecut consumables I use). I did this even though the opto isolator I use is good to 2Kv or so isolation. I know this means that I can't use it for plate contact sensing when I am actually cutting but I don't need that because of my torch break away sensing switch (sensitive enough that the torch mount usually doesn't come all the way off the Z). Your A120 when used with the automation torch doesn't need this because the built in firmware will throw an error and shut off the torch if this happens, on US machines the 85psi led will light indicating this error. I believe we discussed my ohmic sensing setup in some detail in the recent past.

Phill

I didn't notice any problems during my installation. I was actually quite surprised by the lack of them. Thanks to Rod I didn't even have to look into the problem, straight to Synaptic to find the the required library wasn't installed and install it.

Today's adventure is find out why I have lost my hal widgets out of my Glade setup. I went through a bunch screwing around to get them installed a few months ago and now they are gone.

John

All

I don't know why this happens. When I try to open any of the plasmac glade files by right clicking on it in the file browser and selecting Glade to open it I don't get all the hal widgets in the left pane and I get error messages where they should be on the preview screen. Now if I start Glade from start menu or from the desktop short cut it starts with all the widgets loaded and if I open a plasmac Glade file from the file menu it opens correctly. Oh well I don't have time to fight this.

A bigger problem is that some of the files won't open in Glade... I opened some of those files with a text editor and found some names to contain special characters. So for instance the file plasmac_buttons.glade works when you run linuxcnc and select a configuration that uses it but if you try and open it with Glade you get nothing, not even a warning. I think this may have something to do with the problem: All of the files that won't open in Glade have a similar problem with special characters in the file names.

John