QtPlasmaC release.
There have been a few documentation changes and install program changes to reflect this.
Please Log in or Create an account to join the conversation.
# if no new dbounce then use old debounce component for legacy plasmac conversio
#if {[hal list pin db_float.out] != {}} {
net plasmac:arc-ok db_arc-ok.out => plasmac.arc-
net plasmac:breakaway-switch-out db_breakaway.out => plasmac.brea
net plasmac:float-switch-out db_float.out => plasmac.floa
net plasmac:ohmic-probe-out db_ohmic.out => plasmac.ohmi
#} else {
# puts "using old debounce component"
# puts "it is recommended to convert to the new dbounce component\n"
# net plasmac:breakaway-switch-out debounce.0.1.out => plasmac.bre
# net plasmac:float-switch-out debounce.0.0.out => plasmac.flo
# net plasmac:ohmic-probe-out debounce.0.2.out => plasmac.ohm
#}
twopass:invoked with <> options
twopass:found ./qtplasma.hal
twopass:found ./qtplasma_connections.hal
twopass:found /home/colten/git/linuxcnc/lib/hallib/plasmac.tcl
twopass:found ./pendant.hal
using old debounce component
it is recommended to convert to the new dbounce component
twopass:pass0: loadusr -W xhc-hb04 -I ./xhc-hb04-layout2.cfg -H -x -s 1
xhc-hb04: waiting for XHC-HB04 device
I've determined that the newer debounce is actually being used as halcmd list pin db_* turns up the correct pins. So, no sure what is causing the puts to fire. Only thing I can think of is the two pass is causing the issue. First pass through, it fires the puts, second pass through they don't run.
Please Log in or Create an account to join the conversation.
It made no connections for the probe, thc etc.... So I am at a loss on how to make these connections. I followed the instructions with the docs. did the conversion and the cfgprefs...... from existing working plasmac
Here is what I came out with as config but no thc and no probe.
Please Log in or Create an account to join the conversation.
That is the problem, I keep meaning to take the message out but... I will get there one day.I've determined that the newer debounce is actually being used as halcmd list pin db_* turns up the correct pins. So, no sure what is causing the puts to fire. Only thing I can think of is the two pass is causing the issue. First pass through, it fires the puts, second pass through they don't run.
Please Log in or Create an account to join the conversation.
I tried loading the new QTplasmaC, with new pncconf.
It made no connections for the probe, thc etc.... So I am at a loss on how to make these connections. I followed the instructions with the docs. did the conversion and the cfgprefs...... from existing working plasmac
Here is what I came out with as config but no thc and no probe.
Might need to run the qtplasmac-setup in order to enable those.
Please Log in or Create an account to join the conversation.
I tried loading the new QTplasmaC, with new pncconf.
It made no connections for the probe, thc etc.... So I am at a loss on how to make these connections. I followed the instructions with the docs. did the conversion and the cfgprefs...... from existing working plasmac
Here is what I came out with as config but no thc and no probe.
Did you select a plasmaa float switch or plasma ohmic probe in pncconf?
Did you select a plasma arc voltage encoder in pncconf?
Please Log in or Create an account to join the conversation.
I tried loading the new QTplasmaC, with new pncconf.
It made no connections for the probe, thc etc.... So I am at a loss on how to make these connections. I followed the instructions with the docs. did the conversion and the cfgprefs...... from existing working plasmac
Here is what I came out with as config but no thc and no probe.
Did you select a plasmaa float switch or plasma ohmic probe in pncconf?
Did you select a plasma arc voltage encoder in pncconf?
I selected plasma float and probe and it did add everrything except thc stuff.
I set the thcad freqs and stuff but did not find where to set for arc voltage - encoder.00.velocity
Nevermind, I found it in pncconf. Thanks
Please Log in or Create an account to join the conversation.
Attachments:
Please Log in or Create an account to join the conversation.
I run mint 19.2 with 2.8.1 on several machines but I am missing out on QTplasmaC. I realise I need 2.9 master
Q.1 So do I have to install Buster (that I don't like) or can I still use mint updated to 2.9 ?
Q.2 Is there a different GUI colour other than yellow ?
Sorry if this post is in the wrong place if so can you move it elsewhere. (not to the bin I hope)
Please Log in or Create an account to join the conversation.
AFAIK it should work on Mint.With me getting old and a bit forgetful may a I ask a newbie question?
I run mint 19.2 with 2.8.1 on several machines but I am missing out on QTplasmaC. I realise I need 2.9 master
Q.1 So do I have to install Buster (that I don't like) or can I still use mint updated to 2.9 ?
Colours are user changeable, see the GUI SETTINGS chapter here:Q.2 Is there a different GUI colour other than yellow ?
linuxcnc.org/docs/devel/html/plasma/qtpl...ml#qt_parameters-tab
Haha, I wouldn't do that to you Clive.Sorry if this post is in the wrong place if so can you move it elsewhere. (not to the bin I hope)
Please Log in or Create an account to join the conversation.