connection -> gmoccapy to THC
19 Aug 2015 19:19 #61548
by BigJohnT
Replied by BigJohnT on topic connection -> gmoccapy to THC
I don't know what a signals and plasma screen is but after some searching I assume your following this wiki page?
wiki.linuxcnc.org/cgi-bin/wiki.pl?Gmoccapy_plasma
Then you need to contact Mariusl about his screen.
JT
wiki.linuxcnc.org/cgi-bin/wiki.pl?Gmoccapy_plasma
Then you need to contact Mariusl about his screen.
JT
Please Log in or Create an account to join the conversation.
- tommylight
- Away
- Moderator
Less
More
- Posts: 19224
- Thank you received: 6441
26 Aug 2015 06:33 #61797
by tommylight
Replied by tommylight on topic connection -> gmoccapy to THC
To late but still,
In the case of using gmocapy with proma elektronika THC, with the config found on their website and on this forum ( namely toma thc), it will not work without some modifications to the gmocapy to add sliders and buttons and LED for the THC.
I can not remember what was with THCUD comp that did not work with simple THC that use simple UP/DOWN/ARCOK signals, but it did not work per se.
As suggested on this thread, first be sure to make that config work with AXIS properly, you have everything explained in a readme file, so read it and it will work properly. Only after you get that working ( it should take 10 to 20 minutes max ), see what and how you need to add the buttons and leds and sliders and other stuff that is located at the right side of the axis screen. Have a look at the gmocapy thread on this forum and i belive you can have it working happily inside of a day !
Regards,
Tom
In the case of using gmocapy with proma elektronika THC, with the config found on their website and on this forum ( namely toma thc), it will not work without some modifications to the gmocapy to add sliders and buttons and LED for the THC.
I can not remember what was with THCUD comp that did not work with simple THC that use simple UP/DOWN/ARCOK signals, but it did not work per se.
As suggested on this thread, first be sure to make that config work with AXIS properly, you have everything explained in a readme file, so read it and it will work properly. Only after you get that working ( it should take 10 to 20 minutes max ), see what and how you need to add the buttons and leds and sliders and other stuff that is located at the right side of the axis screen. Have a look at the gmocapy thread on this forum and i belive you can have it working happily inside of a day !
Regards,
Tom
Please Log in or Create an account to join the conversation.
26 Aug 2015 16:11 - 26 Aug 2015 16:12 #61804
by cncbasher
you need to add your pin connections to the list for each one
net MoveDown hm2_7i43.0.gpio.002.in => signals.led_MoveDown ( example mesa 7i43 )
net MoveDown parport.0.pin-12-in => signals.led_MoveDown ( example parallel port connecting MoveDown to pin 12 of parallel port 0 , change to 1 if your using a second port )
i must admit the example program needs a rewrite to be easier to under stand
if you can give me a list of the port pins your using , and what they are connecting to etc , i'll see what i can do , to get you up and running on axis
Gmocappy may take a little longer , as im working on this blind as i dont have a THC at the moment to test with .
i'll re arrange and bring the example into a working state at the same time . and in line with current examples .
so it's easier to work with ,
Replied by cncbasher on topic connection -> gmoccapy to THC
Ok,
i inserted "addf thcud servo-thread" in my HAL
No error during start up, but my signals and plasma panel is away!
I know that effect.
This is my "Signals.HAL":If i remove one # i have the same effect.# Hook up signal pins connecting # Out pin #net MoveDown => signals.led_MoveDown #net MoveUp => signals.led_MoveUp #net FloatSwitch => signals.led_FloatSwitch #net ArcOK => signals.led_ArcOK #net TorchOn => signals.led_TorchOn #net HeightLock => signals.led_HeightLock
you need to add your pin connections to the list for each one
net MoveDown hm2_7i43.0.gpio.002.in => signals.led_MoveDown ( example mesa 7i43 )
net MoveDown parport.0.pin-12-in => signals.led_MoveDown ( example parallel port connecting MoveDown to pin 12 of parallel port 0 , change to 1 if your using a second port )
i must admit the example program needs a rewrite to be easier to under stand
if you can give me a list of the port pins your using , and what they are connecting to etc , i'll see what i can do , to get you up and running on axis
Gmocappy may take a little longer , as im working on this blind as i dont have a THC at the moment to test with .
i'll re arrange and bring the example into a working state at the same time . and in line with current examples .
so it's easier to work with ,
Last edit: 26 Aug 2015 16:12 by cncbasher.
Please Log in or Create an account to join the conversation.
- ZX-Sinclair
- Offline
- Junior Member
Less
More
- Posts: 31
- Thank you received: 0
27 Aug 2015 01:40 - 27 Aug 2015 15:32 #61817
by ZX-Sinclair
Replied by ZX-Sinclair on topic connection -> gmoccapy to THC
Thanks to all!
But i give up.
gmoccapy is nice but it is to complex or poor documented.
If i insert the suggestion of cncbasher
(net MoveDown parport.0.pin-10-in => signals.led_MoveDown )
The signals LED's disappear from gmoccapy display.
I don't have the time for that. I'm playing since three weeks now.
Now i'm back to axis again.
The actual situation is that i use the version from Proma THCud.
With this version i see the correct LED's light up for up, down, acrOk and float switch.
I can jog around with all three axis. Fine!
But if i try to start a program i get an error: "Joint 2 following error"
I think that this is misleading.
I wrote a program to move only the Y axis for 10 mm very slow and the same happens.
But the z-axis tries to move! In joint and world modus. I played around with different Ferrors, etc. without success.
If i click on spindle start i get the same result (!!!)
But i give up.
gmoccapy is nice but it is to complex or poor documented.
If i insert the suggestion of cncbasher
(net MoveDown parport.0.pin-10-in => signals.led_MoveDown )
The signals LED's disappear from gmoccapy display.
I don't have the time for that. I'm playing since three weeks now.
Now i'm back to axis again.
The actual situation is that i use the version from Proma THCud.
With this version i see the correct LED's light up for up, down, acrOk and float switch.
I can jog around with all three axis. Fine!
But if i try to start a program i get an error: "Joint 2 following error"
I think that this is misleading.
I wrote a program to move only the Y axis for 10 mm very slow and the same happens.
But the z-axis tries to move! In joint and world modus. I played around with different Ferrors, etc. without success.
If i click on spindle start i get the same result (!!!)
Last edit: 27 Aug 2015 15:32 by ZX-Sinclair.
Please Log in or Create an account to join the conversation.
27 Aug 2015 15:56 - 27 Aug 2015 16:00 #61830
by cncbasher
Replied by cncbasher on topic connection -> gmoccapy to THC
if you only start the spindle , and you get follow error , then you have stray electrical surge spikes
make sure all low voltage wiring limits , home switches etc are all sheilded .
follow errors on a stepper driven machine is an indication of incorrect ini settings , perhaps your velocity is too high
or it may be attributable to your thc , and this is what we need to sort out
gmoccapy works well , but with your thc controller modifications are required , if your not a programmer then yes it can be difficult to rectify
but it can be done , however without that specific thc unit for testing then it may take me a while to trouble shoot
if you have axis working correctly , then gmocappy can also , with changes
joint errors are easily sorted , but in this instance it may take a while to debug everything ,
you must remember with Plasma you have high electrical fields that cause problems , interfering to either the pc directly or the cableing
i'm happy to help sort this , but please remember i'm in the UK .
can you either send offlist a picture of the z axis ,
and attach a archive of your working config
you say gmocappy removes the led's this is wrong , and suggests you are configuring something incorrectly
make sure all low voltage wiring limits , home switches etc are all sheilded .
follow errors on a stepper driven machine is an indication of incorrect ini settings , perhaps your velocity is too high
or it may be attributable to your thc , and this is what we need to sort out
gmoccapy works well , but with your thc controller modifications are required , if your not a programmer then yes it can be difficult to rectify
but it can be done , however without that specific thc unit for testing then it may take me a while to trouble shoot
if you have axis working correctly , then gmocappy can also , with changes
joint errors are easily sorted , but in this instance it may take a while to debug everything ,
you must remember with Plasma you have high electrical fields that cause problems , interfering to either the pc directly or the cableing
i'm happy to help sort this , but please remember i'm in the UK .
can you either send offlist a picture of the z axis ,
and attach a archive of your working config
you say gmocappy removes the led's this is wrong , and suggests you are configuring something incorrectly
Last edit: 27 Aug 2015 16:00 by cncbasher.
Please Log in or Create an account to join the conversation.
- ZX-Sinclair
- Offline
- Junior Member
Less
More
- Posts: 31
- Thank you received: 0
27 Aug 2015 18:28 - 27 Aug 2015 18:31 #61834
by ZX-Sinclair
Replied by ZX-Sinclair on topic connection -> gmoccapy to THC
I don't have a spindle.
With gmoccapy it works perfect (but without THC).
With axis i can move all the axes. No Problem.
The "Joint 2 following error" happens if the TripleBeast and all the other stuff is unplugged and i want to start a program or if i start the spindle (?).
I think that this is a software problem.
All three motors (and the parameters in the .ini) are the same and this error happens only with the Z-drive.
I can do what i want. The error is always the same.
With gmoccapy it works perfect (but without THC).
With axis i can move all the axes. No Problem.
The "Joint 2 following error" happens if the TripleBeast and all the other stuff is unplugged and i want to start a program or if i start the spindle (?).
I think that this is a software problem.
All three motors (and the parameters in the .ini) are the same and this error happens only with the Z-drive.
I can do what i want. The error is always the same.
Last edit: 27 Aug 2015 18:31 by ZX-Sinclair.
Please Log in or Create an account to join the conversation.
- tommylight
- Away
- Moderator
Less
More
- Posts: 19224
- Thank you received: 6441
28 Aug 2015 05:19 - 28 Aug 2015 05:22 #61846
by tommylight
Replied by tommylight on topic connection -> gmoccapy to THC
in stepper.hal
line:
#setp stepgen.2.maxvel [AXIS_2]MAX_VELOCITY
remove #
Also edit the acceleration and velocity values in the .ini file to match your machine.
Tom
P.S. do read the readme and/or howto included with the thc config, everything is explained there.
line:
#setp stepgen.2.maxvel [AXIS_2]MAX_VELOCITY
remove #
Also edit the acceleration and velocity values in the .ini file to match your machine.
Tom
P.S. do read the readme and/or howto included with the thc config, everything is explained there.
Last edit: 28 Aug 2015 05:22 by tommylight. Reason: added p.s.
Please Log in or Create an account to join the conversation.
- ZX-Sinclair
- Offline
- Junior Member
Less
More
- Posts: 31
- Thank you received: 0
28 Aug 2015 11:43 #61851
by ZX-Sinclair
Replied by ZX-Sinclair on topic connection -> gmoccapy to THC
#setp stepgen.2.maxvel [AXIS_2]MAX_VELOCITY
remove #
It is removed!
It has nothing to do with acceleration and velocity. I tried that for hours and hours.
I give up...
remove #
It is removed!
It has nothing to do with acceleration and velocity. I tried that for hours and hours.
I give up...
Please Log in or Create an account to join the conversation.
Time to create page: 0.090 seconds