Another plasma component...

BigJohnT wrote:

I'm using a database for my plasma cut data on my GUI just for that reason that there are so many different options and kerf width changes with material, thickness and nozzle.

JT

Yes, I shared some example python scripts and SQL tables a long time ago somewhere in this thread but I had not taken into account the LinuxCNC tool table.. I'll see if I can find it.

rodw wrote:

BigJohnT wrote:

Yes, I shared some example python scripts and SQL tables a long time ago somewhere in this thread but I had not taken into account the LinuxCNC tool table.. I'll see if I can find it.

Well, that was quick!. it is on page 2. forum.linuxcnc.org/plasma-laser/35449-an...nent?start=10#119922

I might revisit this work as I did not look at it again.

But we don't wan to to make too much work for Phill.

I personally think unless you moved to a fully relational database, what we need would be met by simply adding a unique ToolID and a kerf width to the existing materials table records.

How would you then relate that to a LinuxCNC tool.

Cheers, Phill.

Would that be done in the CAM software?
If so then I don't see a need for kerf width in the GUI config.

Cheers, Phill.

I thought I understood what was asked for but now I don't think I do and I have no experience to relate to it.

Do you know if there still a 50 odd tool limit in LinuxCNC?
The HT tool table for Sheetcam I was sent had over 100 tools.

Cheers, Phill.

I was looking at that limit too. I do remember Andy or someone saying it had been increased. There is a note on the lathe page that there is a 99999 limit but I think pockets are involved. I think though most users will only have one machine so a smaller subset (but 56 won't go far). I was looking at my SQL stuff and wanted to try and add an auto incrementing tool ID to the cut chart select statement but not having much luck with SQLITE syntax. If I could do that, it would be much easier as the select statement could limit the data set (to 56)

It would be good if JohnT could share his sql and interface. I kinda think there needs to be a separate toolchanger module that shares the plasmac data.

Either way it won't be easy to map it out. Its kinda like a whiteboard problem. I've really only done a cursory look at tool tables so don't know much more than Phil. Plasmac could parse it on start up and create a gcode subrroutine to reset and load the tools thats called somewhere.

If it gets too hard just add the extra fields for Id and kerf to the materials file for now and we can worry about it down the track once Phills had a rest!

Rod,
Can you explain what you want to achieve with this in layman's terms, I think I got a bit lost somewhere.
I don't understand why we need kerf width in a plasmac config as we don't use it anywhere. My understanding is that it would be used in the CAM software.

Cheers, Phill.