THC plasma configs, with HOW TO.

More
8 years 2 months ago - 8 years 2 months ago #115439 by Grotius
Hi,

Okey i have got it working without probe function. I mentioned that autostart enable must be on.

I added a mux2 component after studying the visual hal file yesterday.

I think we add a user macro for the probe function. This is also compatible with the future probe distance component.
In the Gmoccapy plasma panel, the switch travel height input can be deleted if we use a probe macro.





File Attachment:

File Name: tomathcwit....ngc.zip
File Size:29.66 KB
Last edit: 8 years 2 months ago by Grotius.

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

More
8 years 2 months ago - 8 years 2 months ago #115440 by tommylight
I personally do not like using macros and subroutines and remaps, so i would try to avoid using them. The best thing about the toma.thc. config was that it does not need any of that, it does everything in hal, so even when the machine is stopped mid work it can continue with absolutely no user intervention, just an F9 and "run from here".
When using any of above mentioned methods, that can not be done without user intervention and that consists of switching to MDI, calling the macro or subroutine etc, or continue somewhere where there is a call for that macro or subroutine, meaning going back and cutting again through the same cut where the machine was cutting before it stopped.
Battery .....
Back,
well that was it mostly, i can not recall other quirks of using macros so i will quietly leave. Thank you.
Last edit: 8 years 2 months ago by tommylight. Reason: added more info

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

More
8 years 2 months ago - 8 years 2 months ago #115442 by Grotius
It is kind of difficult to make a on/off switch in the Toma hal code for the probe.

orginal and deactivated :
#net PosSelectC mux2.6.out => mux2.4.in1

added to disable probe and look for ack_ok signal :
net Grotius_in mux2.6.out mux2.7.in1
#this mux function is conneced to arc_on signal
net Grotius_out mux2.4.in1 mux2.7.out

If we now add a button to do this : mux2.6.out => mux2.4.in1
problem is solved.
Last edit: 8 years 2 months ago by Grotius.

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

More
8 years 2 months ago #115451 by tommylight
That was quick, you are getting pretty good at this.
Respect.

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

More
8 years 2 months ago #115460 by Grotius
Hi Tom,

Problem is not solved.
The muxers are not working my way. :woohoo:
Code:
net grotius_button mux4.0.sel1 #mux4.0.out #mux4.0.in0 #mux4.0.in1 #mux4.0.in2 #mux4.0.in3 net Grotius_in0 mux2.4.in1 mux4.0.in0 net Grotius_in2 mux2.4.in1 mux4.0.in2 net Grotius_in3 mux2.4.in1 mux4.0.in3 net Grotius_out mux2.6.out mux4.0.out

The mux2 would connect the same signal over 2 imputs. The mux4 will not do this. So 5 hours trying to do this brings no luck...

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

More
8 years 2 months ago - 8 years 2 months ago #115470 by Grotius
Okey,

Hmm.... It looks like we got some progress... It's almost like the Titanic. Jack, never give up.




Following my schematic's i must avoid mux4 eingang 1.
Last edit: 8 years 2 months ago by Grotius.

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

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