Another plasma component...

I wondered why I couldn't see kerfcross-is-locked.
What is your height-per-volt setting?
Could you try kerfcross override at 200%.
It would also be nice to trigger from kerfcross-is-locked and see what is happening when it switches.

Cheers, Phill.

I have pushed an update, it is a configurator that will (or should) create a complete plasmac configuration.
It doesn't affect plasmac so if you have a working config then there is no need to update.
I have attached a copy if you would like to try it without updating.

Before running this application you need to have:
1. a working machine config.
2. a local clone of the plasmac repo.

Double click on configurator.py in the configs/sim/gmoccapy/plasmac directory and follow the prompts.
The configurator.py MUST remain in the configs/sim/gmoccapy/plasmac directory so it knows where to copy the plasmac files from.
It creates a sub directory in ~/linuxcnc/configs named {machine_name} and writes a {machine_name}.ini and {machine_name}.hal file in that directory.
I makes a backup copy of the original HAL and INI files in the above folder.
It creates a {machine_name}_connections.hal file for the connections between plasmac and the original config. This moves the connections/comments from plasmac.hal to allow it to be overwritten by an upgrade.It copies all the plasmac application files to the new directory.
It also leaves the original HAL and INI files untouched so they could be changed and the configurator could be run to rebuild the config.
It shows only the relevant HAL connections for the selected mode.

It can also be used to upgrade an existing config, although it probably shouldn't be used to update a config that wasn't built by the configurator.

Cheers, Phill.

Mode0


Upgrade

I pushed another update, just some enhancements and code cleaning for the configurator.
To aid the configurator I have changed the layout of plasmac.hal. There are no code changes, just layout and comment changes plus additional comments in the ini files.

Cheers, Phill.

I did a bit of searching and it seems that angles for corrugated are around 33^o to 37^o which gives a worst case gradient of 1.327.
For each 1000mm/min of X velocity it would require 754mm/min of Z velocity so for your 4500mm/min X velocity you would require 3392mm/min of Z velocity.
Say if you decide 40^o to give a margin the gradient would be 1.192.
So you would then require 3775mm/min of Z velocity.

The theory is that plasmac calculates the maximum offset counts that the Z axis is able to handle in each period, then while in THC active mode if it senses that a correction is required it sends that calculated maximum count (tempered by the THC Speed (P) parameter in the run tab) to the axis.z.eoffset-counts pin every period until the number of correction counts required is exhausted. For fastest response, wind that parameter up to the maximum (I think it is 1000).

Acceleration is determined by your ini file settings and should not be affected by plasmac.

You also need to ensure that the side of your nozzle/torch has enough clearance for that angle and cut height.

Cheers, Phill.

I have pushed an update that allows the configurator to upgrade and old manually setup version.

Cheers, Phill.

rodw wrote:

Looks like the Plasmac speed setting is able to go to the maximum but is set to 80% of that right now.

No, THC is ALWAYS allowed 100% of available velocity.
The setup speed spinbox is for the height changes for moving to cut-height, probe-height, pierce-height etc.

If you hover over the spinbox, the tooltip will show you that.

Cheers, Phill