THC plasma configs, with HOW TO.

More
31 Jul 2018 19:10 #115251 by tommylight
Your music to mild, i do this mostly

Thank you.

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

More
31 Jul 2018 23:02 #115266 by rodw


If Mesa will not marry me, it will be a stand alone FPGA project for me during the winter periode. But i will be back after that.


I'm really looking forward to photos of you and PCW at the ceremony :woohoo: :woohoo: :woohoo:
Sounds like it will be a showdown for the music though!

Thank you for your kind comments.
The following user(s) said Thank You: tommylight

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

More
01 Aug 2018 20:01 - 01 Aug 2018 20:01 #115340 by Grotius
Okey,

Back to real life.

In this forum threat we have a orginal Toma Proma THC Function working in different Gui's for a machine with stepper motors.

What i mis and want to upgrade is the following :

The probe sensor is touching all the time before starting.

I already added a button for activating (enable) the probe sensor in the Gmoccapy Gui.
But to enable this, i must have a schematic of the Toma THC interface. Who has this schematic? I know 2 years ago
it was on the internet, but it looks dissapeared.

When the button is scripted and working, it is also possible to add the Probe section component. Then
users can probe over the offset distance they want. This one question would make this forum section final.

I am working on my own Gui now in the mean time.

Attachments:
Last edit: 01 Aug 2018 20:01 by Grotius.

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

More
01 Aug 2018 21:54 #115347 by tommylight
Yeah i could not find it either, will have to do a search through my USB sticks, maybe i can find it.

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

More
02 Aug 2018 01:27 - 02 Aug 2018 01:32 #115364 by Grotius
Okey, I have made a Gmoccapy Hal Visualisation of the Toma Plasma Config.
See attached documents how to do it yourself.

It's late now.

To make a cleaner image, we have to delete some hal trash, just for getting a better overview.

In the attached doc you see this line :
python dot.py | dot -Tpng > mymachine.png
It also works with jpg.
python dot.py | dot -Tpng > mymachine.jpg

It's almost impossible to do this shematic within 180 lines of Python code. But it is done !

Rename the python attachement file to : dot.py
Attachments:
Last edit: 02 Aug 2018 01:32 by Grotius.
The following user(s) said Thank You: tommylight

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

More
02 Aug 2018 05:54 #115373 by tommylight
Grotius, you are da man !!!
That is ............a LOT of work, thank you for reminding me, just scrolling through that PDF was very hard on the nerves, never mind having to follow everything around.
Well, it is complicated for sure !
With utmost respect,
Tom.

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

More
02 Aug 2018 20:48 - 02 Aug 2018 20:58 #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:30 KB
Attachments:
Last edit: 02 Aug 2018 20:58 by Grotius.

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

More
02 Aug 2018 21:05 - 02 Aug 2018 21:49 #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: 02 Aug 2018 21:49 by tommylight. Reason: added more info

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

More
02 Aug 2018 21:15 - 02 Aug 2018 21:17 #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: 02 Aug 2018 21:17 by Grotius.

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

More
02 Aug 2018 21:50 #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.

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