Void Lock Kerf Crossing suggestion

Thanks but it would have been nice is if as I said before I had some testing and feedback done on what I have obviously wasted my time on.

phillc54 wrote:

......................... on what I have obviously wasted my time on.

As i said to a client after scraping 2 useless tables for robot welding, and thinking how to do the third:
This was not a waste of time and money, we learned something, we learned what does NOT work !

tommylight wrote:

phillc54 wrote:

......................... on what I have obviously wasted my time on.

As i said to a client after scraping 2 useless tables for robot welding, and thinking how to do the third:
This was not a waste of time and money, we learned something, we learned what does NOT work !

Ha Ha, thanks Tom but I don't even know if it doesn't work.

But I know a lot of that foundation work by others and myself found its way into Plasmac.

Most of how PlasmaC works is from the Toma config, just all wrapped up in one component.

I did say at the time that I did not think you were following a workable kerf crossing algorithm... and did share my methodology and early code very early in the piece...

Yes, you were quite negative about it. I also recall you saying the same about my THC.

phillc54 wrote:

But I know a lot of that foundation work by others and myself found its way into Plasmac.

Most of how PlasmaC works is from the Toma config, just all wrapped up in one component.

That was not easy, for sure. That config has everything automated in hal, and just following what is going on there is a mess. I do not remember much of the work i have done at the beginning several years back, but i do remember when i made it work with Mesa and servo systems, i still have 3 or 4 pages of scribbles trying to follow joint command and joint feedback through it.
-

phillc54 wrote:

But I know a lot of that foundation work by others and myself found its way into Plasmac.

Most of how PlasmaC works is from the Toma config, just all wrapped up in one component.

I did say at the time that I did not think you were following a workable kerf crossing algorithm... and did share my methodology and early code very early in the piece...

Yes, you were quite negative about it. I also recall you saying the same about my THC.

Since you two are bickering about it, i do recall writing here that the only way to do that properly is DV/DT. Or did i ?
As i see it, both of you ( and others ) did a magnificent job of making all this work properly and having features that most of the industrial plasma machines lack.
Again, i will point out that looking at a plasma machine while cutting it all seems very simple, but nothing related to plasma cutting is simple. Cutting metal like butter is no easy feat, and being able to build such a machine in a shed and have it work all day every day without a hiccup is only made possible by such persons as we have here, putting endless hours of work without expecting any reward for it. But it sure as hell is fun !

That was not easy, for sure. That config has everything automated in hal, and just following what is going on there is a mess. I do not remember much of the work i have done at the beginning several years back, but i do remember when i made it work with Mesa and servo systems, i still have 3 or 4 pages of scribbles trying to follow joint command and joint feedback through it.

That is a great piece of HAL work Tom. I think it took me about a week to draw it out into a format I could understand.