Another plasma component...

Pushed a fix for probe error handling

Cheers, Phill.

Pushed user configurable buttons for axis native, axis gladevcp and gmoccapy.

To make it easier (for me) to support multi GUI's I have renamed the buttons and ALL buttons are now configurable.

Sorry, but this will make it necessary to edit any existing configs that have user configurable buttons.

Cheers, Phill.

Still no luck adding to the materials list, not a big problem as I will most likely edit it to the materials and conditions I use

John, the materials list is not editable (is that a word) from within LinuxCNC, it has to be done with an external editor. It may be edited while LinuxCNC is running then if you reload from the config tab then it will show in the materials.

Cheers, Phill

phillc54 wrote:

This has been fixed, the GUI's set it correctly. You can leave the setp plasmac.mode 2 in your HAL file if you wish.

Thank you for this fix I will update and try it out.

I'm not sure what is going on here, islander261 is also having this problem. I have tried many times here and cannot get it fail.
I will keep trying.

Let me know if there is anything I can do on my side to help diagnose this problem. The only thing I can think of that may cause an issue is I changed the name of the machine in the INI file. This caused a new "machine-name.cfg" and "machine-name.mat" file to be generated. linuxcnc does seem to load changes made directly to the file but sving doesn't happen.

I have tried touchoff at 1mm in a metric config and 0.1" in a imperial config without any problems. In the sims I just leave touchoff at Z0 and don't touchoff for any tests. The component itself does not use the touchoff height at all.

This morning I managed to figure out why these errors were occuring (it was my fault). My machine table only uses a single motor for the y-axis (joint_1) but also has a rotary 4th axis (joint_3). When I converted the config over from sim I missed this line in plasmac.hal:

Code:

net p_comp:axis-position joint.3.pos-fb => plasmac.axis-z-position

which was reading my rotary position as the z-position and causing confusing errors. To fis the issue I simply changed it to read:

Code:

net p_comp:axis-position joint.2.pos-fb => plasmac.axis-z-position

but I was wondering if it would not be better if the line was:

Code:

net p_comp:axis-position axis.z.pos-cmd => plasmac.axis-z-position

my brief check in hal config told me that these should be equivalent but I dont have enough Linuxcnc experience to be sure...

Do you still want to see my config I should be able to upload it later today (machine computer doesn't have internet)?

Thanks for your help
Glenn

Zultan wrote: but I was wondering if it would not be better if the line was:

Code:

net p_comp:axis-position axis.z.pos-cmd => plasmac.axis-z-position

my brief check in hal config told me that these should be equivalent but I dont have enough Linuxcnc experience to be sure...
Glenn

I kinda think that is more correct for the 2.8 master branch Plasmac is based on. The reason for this is that one significant change from V 2.7 to V 2.8 was separating the dependence between axes and joints. In the case of an axis with 2 motors, the axis don't really exist until the machine is homed. I wondered if external offsets might make the joint vs axis be different but I don't think so.

You can't assume a given joint represents a specific axis anymore

Zultan wrote:
but I was wondering if it would not be better if the line was:
net p_comp:axis-position axis.z.pos-cmd => plasmac.axis-z-position

rodw wrote:
I kinda think that is more correct for the 2.8 master branch Plasmac is based on

Thanks guys, I will have a look at this.

Zultan wrote:
Do you still want to see my config I should be able to upload it later today (machine computer doesn't have internet)?

I don't think I have actually tried with a machine rename, I will give that a try and let you know.


Cheers, Phill.