gmoccapy plasma struggle bus

More
18 Sep 2018 21:08 #117731 by jimmyrig
i've setup a few machines before in axis but gmoccapy plasma is kicking my butt. I've looked over the getting started documentation here wiki.linuxcnc.org/cgi-bin/wiki.pl?Gmoccapy_Plasma and here linuxcnc.org/docs/devel/html/gui/gmoccapy.html
but cannot seem to find how to convert a axis hal and ini file to gmoccapy plasma

i copied the gmoccapy sim file, made an hal+ini file with step config (2 parallel ports), then proceded to delete the "sim" files out of the gmoccapy ini file and linked my axis hal file instead (along with the signal and plasma hal files). i then coppied the MOTOR values over so everything was lined up

the error i get is cant find "gmoccapy2.glade"...

Print file information:
RUN_IN_PLACE=no
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/usr/bin
LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/usr/realtime-3.4-9-rtai-686-pae/modules/linuxcnc
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/usr/share/linuxcnc/tcl/msgs
INIVAR=inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.5
LINUXCNC - 2.7.14
Machine configuration directory is '/home/jimmy/linuxcnc/configs/5x10Plasma'
Machine configuration file is '5x10Plasma.ini'
INIFILE=/home/jimmy/linuxcnc/configs/5x10Plasma/5x10Plasma.ini
PARAMETER_FILE=sim.var
TASK=milltask
HALUI=halui
DISPLAY=gmoccapy
Starting LinuxCNC...
Starting LinuxCNC server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting LinuxCNC IO program: io
Starting HAL User Interface program: halui
Found file(REL): ./table.hal
Found file(REL): ./plasma.hal
Found file(REL): ./signals.hal
Starting TASK program: milltask
Starting DISPLAY program: gmoccapy
task: main loop took 0.104681 seconds
task: main loop took 0.015092 seconds
**** GMOCCAPY GETINIINFO ****
Preference file path: gmoccapy_preferences
[]
**** GMOCCAPY INFO ****
**** No gmoccapy2.glade file present ****

**** GMOCCAPY INFO ****
**** audio available! ****
**** GMOCCAPY INFO ****
**** No virtual keyboard installed, we checked for <onboard> and <matchbox-keyboard>.
**** GMOCCAPY INFO ****
**** no valid probe config in INI File ****
**** disabled tool measurement ****
**** GMOCCAPY INFO: Gcode.lang found ****
**** GMOCCAPY INFO : inifile = /home/jimmy/linuxcnc/configs/5x10Plasma/5x10Plasma.ini ****:
**** GMOCCAPY INFO : postgui halfile = gmoccapy_postgui.hal ****:
**** GMOCCAPY GETINIINFO ****
Preference file path: gmoccapy_preferences
Xlib.protocol.request.QueryExtension
**** GMOCCAPY GETINIINFO ****
Preference file path: gmoccapy_preferences
Xlib.protocol.request.QueryExtension
Shutting down and cleaning up LinuxCNC...
Killing task linuxcncsvr, PID=25976
Killing task milltask, PID=26043
task: 3157 cycles, min=0.000020, max=0.104681, avg=0.001163, 2 latency excursions (> 10x expected cycle time of 0.001000s)
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments



the error i get is cant find "gmoccapy2.glade"...which appears to be the coolant file, so i went to a normal gmoccapy setup and copied the file over to the plasma and this was what i got...not sure what the issue is here..

Print file information:
RUN_IN_PLACE=no
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/usr/bin
LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/usr/realtime-3.4-9-rtai-686-pae/modules/linuxcnc
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/usr/share/linuxcnc/tcl/msgs
INIVAR=inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.5
LINUXCNC - 2.7.14
Machine configuration directory is '/home/jimmy/linuxcnc/configs/5x10Plasma'
Machine configuration file is '5x10Plasma.ini'
INIFILE=/home/jimmy/linuxcnc/configs/5x10Plasma/5x10Plasma.ini
PARAMETER_FILE=sim.var
TASK=milltask
HALUI=halui
DISPLAY=gmoccapy
Starting LinuxCNC...
Starting LinuxCNC server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting LinuxCNC IO program: io
Starting HAL User Interface program: halui
Found file(REL): ./table.hal
Found file(REL): ./plasma.hal
Found file(REL): ./signals.hal
Starting TASK program: milltask
Starting DISPLAY program: gmoccapy
task: main loop took 0.027556 seconds
task: main loop took 0.013195 seconds
**** GMOCCAPY GETINIINFO ****
Preference file path: gmoccapy_preferences
[]
**** GMOCCAPY INFO ****
**** gmoccapy screen 2 found ****

**** GMOCCAPY INFO ****
**** audio available! ****
**** GMOCCAPY INFO ****
**** No virtual keyboard installed, we checked for <onboard> and <matchbox-keyboard>.
**** GMOCCAPY INFO ****
**** no valid probe config in INI File ****
**** disabled tool measurement ****
**** GMOCCAPY INFO: Gcode.lang found ****
**** GMOCCAPY INFO : inifile = /home/jimmy/linuxcnc/configs/5x10Plasma/5x10Plasma.ini ****:
**** GMOCCAPY INFO : postgui halfile = gmoccapy_postgui.hal ****:
**** GMOCCAPY GETINIINFO ****
Preference file path: gmoccapy_preferences
Xlib.protocol.request.QueryExtension
**** GMOCCAPY GETINIINFO ****
Preference file path: gmoccapy_preferences
Xlib.protocol.request.QueryExtension
Shutting down and cleaning up LinuxCNC...
Killing task linuxcncsvr, PID=26660
Killing task milltask, PID=26707
task: 3248 cycles, min=0.000019, max=0.027556, avg=0.001147, 2 latency excursions (> 10x expected cycle time of 0.001000s)
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments

finally if i copy the plasma.glade and rename it gmoccapy2.glade i actually boot gmoccapy and everything appears normal but a popup window with this message

Found an error!
The following information may be useful in troubleshooting:

Traceback (most recent call last):
File "/usr/bin/gmoccapy", line 4238, in <module>
app = gmoccapy()
File "/usr/bin/gmoccapy", line 249, in __init__
self._init_hide_cursor()
File "/usr/bin/gmoccapy", line 1143, in _init_hide_cursor
self.widgets.window1.window.set_cursor( None )
AttributeError: 'NoneType' object has no attribute 'set_cursor'



clicking ok gives me this errror...not sure what the issue is



Print file information:
RUN_IN_PLACE=no
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/usr/bin
LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/usr/realtime-3.4-9-rtai-686-pae/modules/linuxcnc
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/usr/share/linuxcnc/tcl/msgs
INIVAR=inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.5
LINUXCNC - 2.7.14
Machine configuration directory is '/home/jimmy/linuxcnc/configs/5x10Plasma'
Machine configuration file is '5x10Plasma.ini'
INIFILE=/home/jimmy/linuxcnc/configs/5x10Plasma/5x10Plasma.ini
PARAMETER_FILE=sim.var
TASK=milltask
HALUI=halui
DISPLAY=gmoccapy
Starting LinuxCNC...
Starting LinuxCNC server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting LinuxCNC IO program: io
Starting HAL User Interface program: halui
Found file(REL): ./table.hal
Found file(REL): ./plasma.hal
Found file(REL): ./signals.hal
Starting TASK program: milltask
Starting DISPLAY program: gmoccapy
task: main loop took 0.045948 seconds
task: main loop took 0.010584 seconds
task: main loop took 0.017576 seconds
task: main loop took 0.010684 seconds
task: main loop took 0.017156 seconds
task: main loop took 0.010299 seconds
task: main loop took 0.013882 seconds
**** GMOCCAPY GETINIINFO ****
Preference file path: gmoccapy_preferences
Xlib.protocol.request.QueryExtension
task: main loop took 0.024240 seconds
**** GMOCCAPY GETINIINFO ****
Preference file path: gmoccapy_preferences
Xlib.protocol.request.QueryExtension
**** GMOCCAPY GETINIINFO ****
Preference file path: gmoccapy_preferences
[]
**** GMOCCAPY INFO ****
**** gmoccapy screen 2 found ****

**** GMOCCAPY INFO ****
**** audio available! ****
Shutting down and cleaning up LinuxCNC...
task: main loop took 0.014214 seconds
Killing task linuxcncsvr, PID=27087
Killing task milltask, PID=27145
task: 48885 cycles, min=0.000019, max=0.045948, avg=0.001193, 9 latency excursions (> 10x expected cycle time of 0.001000s)
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments



i am using linuxcnc 2.7.14 (latest version as i understand it).....it seems to be a bug that the coolant window isnt disabled to it crashes when loading....but it wouldnt surprise me if im missing something

hal files and ini are included

thanks for the help
Jimmy

File Attachment:

File Name: 5x10Plasma.ini
File Size:6 KB

File Attachment:

File Name: table.hal
File Size:4 KB
Attachments:

Please Log in or Create an account to join the conversation.

More
19 Sep 2018 21:48 - 19 Sep 2018 21:56 #117767 by Grotius
Hi Jimmyrig,

Welcome to the linuxcnc forum. I see you are member sinds yesterday. That is good news !!

1. What kind of torch height controller are you using?
2. What kind of linux version?
3. Port and pin hard wiring setup?
4. What kind of plasma inverter and tables do you have, maybe you can upload picture? I skipp chineze plasma machine's, sorry about that. ( this because of chineze service failure's all around the globe, they sell, but they don't service anything, and i don't wanna be the guy who solve's their mistakes for nothing. ) So if it is chineze, please photoshop the picture to a Dutch machine like Voortman Plasma, hmm, it looks like Voortman is using a Siemens display.

Last edit: 19 Sep 2018 21:56 by Grotius.

Please Log in or Create an account to join the conversation.

More
28 Sep 2018 07:35 #118094 by jimmyrig
for anyone in the future, the way i fixed it was manually editing the stepconf files generated with the wizard to use the gmoccapy plasma parts.

if you download 2.8pre it has gmoccapy as an option in the stepconf wizard making it even easier (still have to move a few things for the plasma)

hope that helps someone
Jimmy

Please Log in or Create an account to join the conversation.

More
28 Sep 2018 07:40 #118095 by jimmyrig
1, i am using my own THC based off of an arduino
2. i went to 2.8 pre after starting with the linuxcnc usb install stick
3. 2 parallel ports, drivers are a gekko g540 that reads in all 4 homing switches separate (XXYZ) and a ebay parallel breakout board to run the plasma pins (arc ok, torch touchoff, ohmic touchoff, and
4. i built the table from scratch.

Please Log in or Create an account to join the conversation.

More
27 Oct 2018 12:05 #119505 by mariusl
Hi Jimmy
Sorry I did not see this thread before. Did you come right with your plasma config?

Just some observation from experience with plasma and usb based devices. I have been building plasma machines for a long time now and have tried many USB based THC systems. I have my own design that was never implemented due to the fact that USB and plasma do not like to live in the same town.
The problem is due to the plasma arc being at between -80to -180V level for most cases and occasionally cause voltage conditions on the USB interface that will cause it to shut down. You cannot revive it unless you unplug.
The most reliable of all is good old analog comparators and some very good filtering on the arc voltage. A window comparator will create UP/DOWN signals that can be used in the THCUD component that comes with Linuxcnc.
There are other issues with using the USB interface that has to do with server loop timing .

Gmoccapy Plasma provides features for the simple UP/DOWN THC and also for a more complex system that no one has used seemingly.

Let me know if you need any help with the setup of Gmoccapy. I did the Plasma section with Norbert but it was a long time ago and I might be rusty.

Regards
Marius


www.bluearccnc.com

Please Log in or Create an account to join the conversation.

More
19 Nov 2018 16:06 #121002 by bevins
Replied by bevins on topic gmoccapy plasma struggle bus
Not quite following this. Does the gmoccapy plasma work and hal connection made if you go through stepconf?

Is anyone using gmoccapy with plasma? If so, can we see configs somewhere?

Thanks,

Bob

Please Log in or Create an account to join the conversation.

More
19 Nov 2018 16:26 #121005 by tommylight
Rodw is using it, and maybe Icelander.
I use Axis strictly.......for now.

Please Log in or Create an account to join the conversation.

More
19 Nov 2018 16:52 - 19 Nov 2018 16:54 #121007 by mariusl
None of the Guis will make the plasma connection through Stepconf. You have to do some work yourself but mostly it is because there are many ways of doing THC. Gmoccapy works very well. What is it that you want to do with it?

Use stepconf to configure the CNC part of your machine and then use the THCUD component and the Gmoccapy Plasma HAL interface to get your plasma working.

As I said, you need to understand plasma and the THC equipment that you want to use. The rest is easy.

P.S. Did you read up on some of the explanation on the wiki / documents?

Regards
Marius


www.bluearccnc.com

Last edit: 19 Nov 2018 16:54 by mariusl.

Please Log in or Create an account to join the conversation.

More
19 Nov 2018 17:07 #121009 by mariusl
Also read the man pages for THCUD it explains very well.

linuxcnc.org/docs/devel/html/man/man9/thcud.9.html

Regards
Marius


www.bluearccnc.com

Please Log in or Create an account to join the conversation.

More
19 Nov 2018 17:25 #121012 by mariusl
I just read you message again an saw that you use an ohmic sensor for THC. Are you sensing through the torch tip or do you have your own sensor?

Regards
Marius


www.bluearccnc.com

Please Log in or Create an account to join the conversation.

Moderators: newbynobiHansU
Time to create page: 0.115 seconds
Powered by Kunena Forum