Another plasma component...

islander261 wrote:
The part about not being able to delete a directory in your home user space is troubling while being logged in as the user.

I think that is because of using sudo when not necessary...

This is what you should see.


Cheers, Phill.

John,

No worries at all, I can always find something to do...

Thank you for all your testing.

Cheers, Phill.

I have pushed a couple of minor updates:
- show thc as locked until target voltage established at start of cut
- change all stop on error to pause on error

Cheers, Phill.

I have pushed another update:
- fix torch pulse and ohmic test while paused

Cheers, Phill.

JTknives, I will try a fresh git clone on my workshop machine and get back to you.

Cheers, Phill.

JTknives wrote:
jtknives@plasma:~$ git clone github.com/phillc54/linuxcnc.git ~/plasmac

This should be:The one you cloned is my fork of linuxcnc so you would have master branch...

I just completed a brand new install and it does work...

Cheers, Phill.

John,
I intend to have another attempt at the m-code override parameters and I am trying to get my head around how it should work so I hope you can help me out with the following:

At the moment I believe you set thc-enable and cut-height from m-code, I can understand thc-enable but wouldn't cut height be better set by the cut parameters from the material selected on the panel.
Do you use a digital out for thc-enable and an analog out for cut-height, or just use analog for both.
If during a job a spin box value is changed should this then override the last m-code or should the last m-code be the value used until a new m-code or the end of the job.
When a job is finished should the original spinbox values then be set as the values for the next job or should they stay at what was last used.

If anyone else would like to chime in you are more than welcome...

Cheers, Phill.