Another plasma component...

This development phase is very time consuming so I need to reduce the burden by cutting back on sim configs.
My preference would be to revert to one GUI for the time being and revisit others if needed when when the component development is more complete.
It seems like most users run Gmoccappy, would that be correct?.
Is any one using Axis, if no one is that would be great, I could remove both...
If you use Axis, which one do you use, Native or GladeVCP.
I don't believe any one is using QtVCP as that is one I did for myself using Chris M's development work so I will remove it and get back to that later.

The order of work will be:
Complete the statistics tab, this is half done so I don't want to start something else until it is complete.
Provide some different IHS Skip types of which one will be set in the ini file.
Get the Cut Parameters to load from a gcode tool change.

Current IHS Skip was supposed to follow HT ArcGlide operation:
Skip IHS: This parameter optimizes production by reducing the time between cuts. If the next starting point is within this distance of the end of the previous cut, the THC skips the IHS. When this happens, the torch goes directly to the Pierce Height and skips contact with the workpiece. This setting can improve the overall machine production rate. Set this parameter to disabled to disable this feature. Skip IHS will be ignored if:
- Sample Voltage mode is active and an IHS is needed for arc voltage sampling (six arc voltage samples are required before IHS can be skipped)
- The THC is not in Automatic mode

I read this wrong and made it be in THC enable AND Auto Volts mode, I will fix that...

Plasmac uses three arc samples, would six be better?

[strike]I was thinking of four types:[/strike] I am doing two types:
1. within distance of end of last cut AND THC enabled
[strike]2. within distance of end of last cut AND THC disabled[/strike]
[strike]3. within distance of start of last cut AND THC enabled[/strike]
4. within distance of start of last cut AND THC disabled or enabled

Regarding gcode tool change:
We will need to integrate with the existing tool table to allow for G41 & G42 for the kerf widths.
We will also need a tool number as a setting for each material.
I have a couple of ideas in mind but will know more after a bit of experimenting, also I won't be able to do anything that ties it to any particular software.

John,
Would it be practical to add THC Enable as a setting for each material then do everything from a tool change rather than a digital pin?

Whatever I have forgotten will follow...

Cheers, Phill.

I have struggled to get any time out of work to try Plasmac, I managed to get a couple of hours over the weekend and did a fresh clone, but although the sims work fine, when trying to use it as a live solution I got a screen dump and locked pc.

I have booked 2 days off work next week to dedicate to getting this up and running,

I will be using Gmoccappy

Gmocappy alone is good with me and it aligns with the instructions I've written.

I think 3 arc samples is fine. I've found if it does not work the first go, It won't on subsequent goes without some user intervention. eg. Put the earth clamp back on, lower pierce height are a couple I've had today.

phillc54 wrote: I was thinking of four types:
1. within distance of end of last cut AND THC enabled
2. within distance of end of last cut AND THC disabled
3. within distance of start of last cut AND THC enabled
4. within distance of start of last cut AND THC disabled

Option 2 can't exist, you can't base the skip from the end of a cut if THC is disabled can you?
Does THC need to be tied into this?
Can't it be:
1. within distance of end of last cut (THC enabled is implied, so if not enabled, ignore and probe anyway)
2. within distance of start of last cut (implies it does not matter if THC is disabled or enabled)

phillc54 wrote: Regarding gcode tool change:
We will need to integrate with the existing tool table to allow for G41 & G42 for the kerf widths.
We will also need a tool number as a setting for each material.
I have a couple of ideas in mind but will know more after a bit of experimenting, also I won't be able to do anything that ties it to any particular software.

John,
Would it be practical to add THC Enable as a setting for each material then do everything from a tool change rather than a digital pin?
Cheers, Phill.

Sounds like a good start re the tool changer. Sorry about coming up with the idea. It will be very powerful. Sounds like it needs to be done within a separate tool changer module. Perhaps the GUI can update the displayed material based on a change of the tool number it receives from the tool changer.

phillc54 wrote: John,
Would it be practical to add THC Enable as a setting for each material then do everything from a tool change rather than a digital pin?
Cheers, Phill.

I don't think so. You might wish to rerun a part for testing with THC disabled or something. Keep the material selection strictly as a container for required cut settings (THC has no part in that)

Personally, THC will always be enabled at my end after plasmac walk up a badly warped bit of aluminium today. By the time I was ready to take a photo, the heat had gone and the warp subsided a lot.

I have to say I read your Hypertherm reference document today, I had not seen it before. Hats off to you for the research. Once I got my head around it it makes sense. if the THC is accurate, there is nothing wrong with the end of cut. Thinking about it, it could be inclusive:

eg
This kinda gives you the best of both worlds. Assuming an accurate THC, there are 2 positions we know to be true. The last probe position and the end of the last cut (actually where THC is disabled). If you don't want to skip, then the user set the skip distance 0.1

Sorry about thinking out aloud...

I have just pushed an update for the completed stats tab in Gmoccapy. It may need some refinement but I think it is close...

rodw wrote:
Option 2 can't exist, you can't base the skip from the end of a cut if THC is disabled can you?
Does THC need to be tied into this?
Can't it be:
1. within distance of end of last cut (THC enabled is implied, so if not enabled, ignore and probe anyway)
2. within distance of start of last cut (implies it does not matter if THC is disabled or enabled)

At the moment it is your #1 (when I fix my error) and John would like your #2, I just added the other two to fill in the blanks but I would be happy with just the two you suggest.

Cheers, Phill

is page 1 always updated with the newest version of the component

pl7i92 wrote: is page 1 always updated with the newest version of the component

Yes, thats what git does. When Phill says he's pushed an update, you just need to go to your src directory (~/plasmac/src if you followed my instructions), pull it and recompile with these commands:

If there is only one change, then only that file will get compiled so it will only take a few seconds.