- Posts: 5711
- Thank you received: 2100
Another plasma component...
- phillc54
- Offline
- Platinum Member
-
So I have tested Axis and Gmoccapy in metric and imperial with Z zero at bottom and Z zero near top and all were successful with the current version of the branch.
Cheers, Phill.
Please Log in or Create an account to join the conversation.
- phillc54
- Offline
- Platinum Member
-
- Posts: 5711
- Thank you received: 2100
I think I am going to go with this unless there are valid reasons not to as it means keeping track of the Z axis is much neater.
Cheers, Phill.
Please Log in or Create an account to join the conversation.
- tommylight
- Offline
- Moderator
-
- Posts: 22011
- Thank you received: 7491
Please Log in or Create an account to join the conversation.
- islander261
- Offline
- Platinum Member
-
- Posts: 757
- Thank you received: 216
Thank you, I did successful line testing today. As usual nice cut quality from Plasmac, no surprises. The weather is supposed to be dry tomorrow so I will need to do yard work, no cutting. Hopefully Monday or Tuesday I will do a few production sheets when the weather is wet again.
My Gmoccapy using my complex PP and Gcode files resets the offsets at the end of every file so you always start in a known state when loading the next file without having to re initialize the machine.
John
Please Log in or Create an account to join the conversation.
- phillc54
- Offline
- Platinum Member
-
- Posts: 5711
- Thank you received: 2100
- remove duplicated ini file entry - doesn't really affect anything, just a tidy up
- change resolution for arc voltage input scaling and offset
GUI files changed are:
configs/sim/axis/plasmac/native/plasmac_axis.py
configs/sim/axis/plasmac/gladevcp/plasmac_panel.py
configs/sim/gmoccapy/plasmac/plasmac_config.py
configs/sim/gmoccapy/plasmac/plasmac_panel.py
I have fixed the upper and lower limits, hopefully by enough to cover everything.rodw wrote:
The on screen scaling does not work because of enforced upper and lower limits in the config screen as I can't enter an offset of 3659.375 (0-100 enforced)
Also the maths in my earlier post says the frequency counts per volt is 83.73 and you have to input the reciprocal of this which is 0.011943151 which is not logical. So I would recommend that the maths be changed to do the reciprocal stuff internally and also remove the enforced range on the scale. If that was the case I think it would work well with some explanation in the docs.
I don't want to change too much as I don't want the component itself to be dependent on any particular hardware.
I rigged up a 7i76e with a TCAD connected to the encoder input and two batteries for testing:
- run LinuxCNC
- open halshow and watch plasmac.arc-voltage-in and plasmac.arc-voltage-out
- set arc-voltage-scale to 1
- set arc-voltage-offset to the value read from plasmac.arc-voltage-in
- measure battery voltage
- connect battery to THCAD input
- set arc-voltage-scale to battery-voltage / plasmac.arc-voltage-out
could probably fine tune further but it was good enough for the purpose of the exercise.
My values were:
arc-voltage-offset = -3805
arc-voltage-scale = -0.000406
Cheers, Phill.
Please Log in or Create an account to join the conversation.
- rodw
- Offline
- Platinum Member
-
- Posts: 12170
- Thank you received: 4153
At 0 volts, with zero as an offset, I was getting 44 volts and 3659/83.73 = 43.7 volts so the logic was correct.
I'll update and give it a go when I'm next up in the shed.
Please Log in or Create an account to join the conversation.