Another plasma component...

More
7 years 5 months ago - 7 years 5 months ago #133433 by phillc54
I have pushed another update.

Specifying a time after probe-test in the ini file will hold the probe test on for that time, allows for better hands free probe testing.
Affected files:
Code:
configs/sim/gmoccapy/plasmac/metric_plasmac.ini configs/sim/gmoccapy/plasmac/imperial_plasmac.ini configs/sim/gmoccapy/plasmac/plasmac_buttons.py
The only changes in the ini files are additional comments for probe-test.

Cheers, Phill.
Last edit: 7 years 5 months ago by phillc54.

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

More
7 years 5 months ago #133612 by rodw
Replied by rodw on topic Another plasma component...
[quote="phillc54" post=133423
Rod,
I cannot find any problems with the button colors.

Cheers, Phill.[/quote]

This is quite strange. I just updated again. I dug through the glade file and python handler and there is no reason why its not working. My machine has forgotten how to change the background. The handler is definitely is being called as the text changes. I'll ask in another forum section.

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

More
7 years 5 months ago #133613 by phillc54
Rod,
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.

More
7 years 5 months ago #133614 by rodw
Replied by rodw on topic Another plasma component...
Yeh, I dunno either. It used to work unless I broke it playing with the task modules. But went nowhere outside of the ./EMC folder. I might reinstall plasmac from scratch

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?
Code:
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.

More
7 years 5 months ago #133615 by phillc54

Also on a live cut, I don't have an M190. Is there something I need to set up?

If you don't already have a USER_M_PATH in your ini file [RS274NGC] section you will need:
Code:
# required for our material change USER_M_PATH = ./
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.


Also can you confirm this is only needed once in a gcode file if you are only running one tool in the job?

Yes, that is correct.

Cheers, Phill.

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

More
7 years 5 months ago #133616 by phillc54
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:
Code:
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
Or whatever logic you have for your requirements.
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.

Moderators: snowgoer540
Time to create page: 0.580 seconds
Powered by Kunena Forum