- Posts: 116
- Thank you received: 33
I removed the PyVCP from the INI and still get the errors.I didn't see a reference to a PyVCP panel in your ini file
I have my hal commands spread between that file and my original hal file. Should I combine it to one single hal file?I just noticed in your ini file that you have:
HALFILE = ./imperial_plasmac_cmds.hal
Please Log in or Create an account to join the conversation.
Looks Good.This is actually using custom component that divides the table into 2 zones, but you can use the Lincurve component to create the zones along the Y axis position and trigger a switch accordingly.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
It seems you didn't use the configurator to create your config, you have multiple commands doing the same thing.I didn't see a reference to a PyVCP panel in your ini file
I removed the PyVCP from the INI and still get the errors.
I just noticed in your ini file that you have:
HALFILE = ./imperial_plasmac_cmds.hal
I have my hal commands spread between that file and my original hal file. Should I combine it to one single hal file?
Do I have all the commands I need, or which commands don't I need with Plasmac? Do I need the PID Commands on all the axis with a stepper system?
Please Log in or Create an account to join the conversation.
I would recommend that you create a new base machine . In your case you would use Stepconf
Then make sure everything works correctly.
When you have a working base machine then use configurator to get PlasmaC working
Please Log in or Create an account to join the conversation.