Another plasma component...
That is strange, it works on my development machine which is a VMware Fusion virtual machine running 'Stretch' RT_PREEMPT and on my test machine which is a real machine running 'Wheezy' RTAI.
Cheers, Phill.
Please Log in or Create an account to join the conversation.
Also on a live cut, I don't have an M190. Is there something I need to set up?
Also can you confirm this is only needed once in a gcode file if you are only running one tool in the job?
M190 P2
M66 P3 L3 Q1n
Just thinking about what a post processor looks like
Please Log in or Create an account to join the conversation.
If you don't already have a USER_M_PATH in your ini file [RS274NGC] section you will need:Also on a live cut, I don't have an M190. Is there something I need to set up?
# required for our material change
USER_M_PATH = ./
Yes, that is correct.
Also can you confirm this is only needed once in a gcode file if you are only running one tool in the job?
Cheers, Phill.
Please Log in or Create an account to join the conversation.
I have done a bit of work on your external thc-enable pin request and the best I can do is:
The plasmac component has an input pin named plasmac.thc-enable
The userspace run panel has an output pin named plasmac_thc.enable-out
These are netted together in plasmac_run.hal to a signal named plasmac:thc-enable
You could have a postgui halfile with something like:
unlinkp plasmac_thc.enable-out
loadrt or2 names=thc_or
addf thc_or servo-thread
net thc-in0 thc_or.in0 => plasmac_thc.enable-out
net thc-in1 thc_or.in1 => my.hal-pin
net plasmac:thc-enable thc_or.out
This doesn't break anything else so if it is good enough for what you want to do then I can push it later today.
Cheers, Phill
Please Log in or Create an account to join the conversation.
If you don't already have a USER_M_PATH in your ini file [RS274NGC] section you will need:
And you need the M190 file in the config directory, unless you already have a USER_M_PATH in which case put the M190 file there.# required for our material change USER_M_PATH = ./
Fixed. Very cool thank Phil
Please Log in or Create an account to join the conversation.
Rod,
I have done a bit of work on your external thc-enable pin request and the best I can do is:
The plasmac component has an input pin named plasmac.thc-enable
The userspace run panel has an output pin named plasmac_thc.enable-out
These are netted together in plasmac_run.hal to a signal named plasmac:thc-enable
You could have a postgui halfile with something like:Or whatever logic you have for your requirements.unlinkp plasmac_thc.enable-out loadrt or2 names=thc_or addf thc_or servo-thread net thc-in0 thc_or.in0 => plasmac_thc.enable-out net thc-in1 thc_or.in1 => my.hal-pin net plasmac:thc-enable thc_or.out
This doesn't break anything else so if it is good enough for what you want to do then I can push it later today.
Cheers, Phill
Phill, that would formalise what John is doing now by the sound of it. So that is OK by me.
I was just looking for a THC delay but I found it.
I was going to modify my Sheetcam postprocessor and see if I could get a gcode file generating without errors this afternoon
Then I'll be onto Les to make a post file for plasmac.
All my Sheetcam tool entries imported fantastically into plasmac. Thanks for that.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
I am happy to make the pins available for use but what you guys do with them is up to you.
Cheers, Phill.
Please Log in or Create an account to join the conversation.
Affected files are:
configs/sim/gmoccapy/plasmac/plasmac_run.glade
configs/sim/gmoccapy/plasmac/plasmac_run.hal
configs/sim/gmoccapy/plasmac/plasmac_run.py
Cheers, Phill.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.