Plasma component in Gmoccapy

More
9 years 9 months ago #85901 by rodw
Replied by rodw on topic Plasma component in Gmoccapy

rodw wrote: Guys,

so I assumed all I needed to do was change it to

Code:
net curvolt thc.volts => plasma.hal_lbl_cur_volt


Well, I'm glad we are all back online :)

I'm still having trouble with this. I've got all the THC component working in my main hal file but this line breaks the plasma display section in gmoccapy.

Can plasma.hal access components in the main hal file?

I've had a couple of distractions but my next step was to move all of the THC stuff into plasma.hal. Is that necessary?

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

More
9 years 9 months ago #85949 by islander261
Replied by islander261 on topic Plasma component in Gmoccapy
rodw

The short answer is yes you can spread the hal instructions around, just be careful with naming. No you do not have to consolidate all of the THC related stuff in one hal file. All of my THC setup and main connections are in my main HAL file and then the voltage display connections are in another as you are doing. The easiest way I found to sort these problems out (and believe me I have had plenty) is to start Linuxcnc from a terminal and look at the error messages. Post your HAL and .ini files and we'll have a look. It really took me a while to get the hang of multiple tabs, .py files and hal files. Mine still doesn't work perfect but is close, a recurring problem on reloading persistent variables that I don't know how to trouble shoot..

John
The following user(s) said Thank You: rodw

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

More
9 years 9 months ago #86139 by rodw
Replied by rodw on topic Plasma component in Gmoccapy - BUG REPORT
Well, I've resolved this error. Its a bug in Gmocappy plasma sim and Islander spotted it earlier, so thanks John! Also thanks to the tip to run from the command line

This line was generated when I created a brand new sim from the LInuxcnc chooser.
Code:
# plasma.hal_lbl_cur_volt (float)

A gmocappy plasma sim generates this plasma.hal file that uses underscores (_) where it should be using hyphens. (-)
Code:
############### plasma hal pins #################### # out pin # plasma.CHL-Threshold (float) # plasma.enable-HeightLock (bool) # plasma.enable-HeightLock-not (bool) # plasma.hal-btn-torch-not (bool) # plasma.hal-btn-torch (bool) # plasma.Target-Voltage (float) # plasma.THC-Speed (float) # plasma.Piercing-autostart-not (bool) # plasma.Piercing-autostart (bool) # plasma.Pierce-Gap (float) # plasma.Pierce-Delay (float) # plasma.G0-Gap (float) # plasma.Cut-Gap (float) # in pin # plasma.led-pos-limit (bool) # plasma.led-neg-limit (bool) # plasma.hal-lbl-corr (float) # plasma.hal_lbl_cur_volt (float) # Hook up plasma pins using the net command # for simulation mode we connect them directly net torch plasma.hal-btn-torch => signals.led-torch-on => signals.led-arc-ok net curvolt plasma.Target-Voltage => plasma.hal-lbl-cur-volt

Now if I had chosen any other signal, the bug would not have bitten.

So to wrap this up, can somebody confirm that building my config in plasma.hal is best practice?

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

More
9 years 9 months ago #86198 by rodw
Replied by rodw on topic Plasma component in Gmoccapy
Hmm, there is also a problem in signals.hal. Pin names do not agree with what is used in signals.glade so the tab does not load

I've only had time to attach one signal. Once complete I will post all errors as a bug report.

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

More
9 years 9 months ago #86495 by newbynobi
Replied by newbynobi on topic Plasma component in Gmoccapy
Hallo rodw,

sorry for the mistakes, I corrected the hal pin names and pushed that to master.

Norbert
The following user(s) said Thank You: rodw

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

Moderators: newbynobi, HansU
Time to create page: 0.388 seconds
Powered by Kunena Forum