Why real time kernel is needed with board like MESA?

tommylight wrote:

tommylight wrote: --proposing stuff here is very welcomed and it triggers involvement of others to finish it in record time, as proven here:
forum.linuxcnc.org/qtpyvcp/40082-monokro...for-plasmac-and-mill
from proposal to a working proof of concept it took 8 days

Thanks to the community for awesome support and collective work, we have made an example.

This has gave me confidence to start many projects.
Now I know, you people will help me out in any problem.

@stivemaster13
Believe me, I am only one month old user here, these people have solved so many problems of mine.
Now I will try to give back in any way I can

Cheers
Pinder

Thank you tommylight I was also very enthusiastic when, we made our own THC controller. The work lasted more than 2 years, so the result is quite good. Of course I will not compare with what you have achieved today in PlasmaC, but obviously you have not done anything more. The good thing is that it is in one place!
I also managed to add a stop when working through a kerf or a small hole. We are currently working on the automatic adjustment of the PID of the Z motor during installation.Thus, the controller will work optimally with each motor - slow stepper or fast servo.
Our goal is for the customer not to be interested in height control at all, after the initial installation and adjustment of the controller. Regardless of the thickness and type of cut material. It only matters what drilling height, drilling time and cutting height we set from the G code. The setting is done with RS485 and is submitted as tool number T.
Well, we are far from Burny Inova - there are some very nice things. Special brush servo motor of Ametek (for faster change of direction at maximum current) very powerful controller, specially designed for them servo driver. They have interesting features - such as a function for anti-collision - torch collision detection. The controller controls a closed servo circuit and uses a "motion completed" output and a Probe input. So if the IHS procedure starts before "motion completed" is obtained, Probe must come, otherwise we obviously don't reach the material and the torch has collided with something. This happens very quickly and leads to an error message!

And one more thing to praise the developers of LinuxCNC - for the end of IHS to take the end of the touch of the torso to the material when moving up! Something I achieved soon but only with UCCNC. I hope to succeed with LinuxCNC as well.
I will be happy to discuss interesting things when I have the necessary hardware.

stivemaster13 wrote: Thank you tommylight I was also very enthusiastic when, we made our own THC controller. The work lasted more than 2 years, so the result is quite good. Of .......

Yeah my friend, now you are talking real things.

Best wishes for you build with linuxcnc. I guarantee, you will be happy with the result.

In PlasmaC, you can set best working IHS and cut height once for a material and save it.

You only need to select material you are about to cut. Your customers will be more than happy.

Best wishes.

Wait till you become part of community.

Cheers
Pinder

Maybe you didn't understand me - in Plasma, as far as I understand by reading, you can do the same thing I do. In my opinion, after the settings during the installation - on the PID motor of the Z axis, there is no need to set the voltage for monitoring from the screen! It is not precise enough (you can check this) to control the height, to be done with a fixed voltage from the screen. It is much better to measure the voltage every time after the start, after IHS, and after the CV has already occurred.
I will give details when I started the settings. I will probably have a lot of questions.

I think you will find we have incorporated everything you talk about in the Plasmac config. Its just we may have gone about it slightly differently.
Probing down and then away has always been supported in Linuxcnc gcode with G38 but In Plasmac its done internally.
Yes, we sample the torch voltage constantly 1000 times per second and auto sample the torch voltage after a timedelay from ArcOK but defer it until we are at or near the desired cut velocity (your CV).. I never set it on the screen and always auto sample.

Linuxcnc has never had a pin that tells you the programmed feedrate (eg the target CV). Plasmac works around this by setting the feedrate from the materials settings on the screen through its materials file.

The current velocity (1000 times a second) is published on the motion.current-vel pin (mm/sec)
Version 2.9 (the development version) adds a motion.feed-upm pin which tells you what the feed rate is at all times(mm.min) This is the target Constant Velocity (CV you mention)
So looking for contant velocity is as simple as seeing if these two pins are equal

Plasmac has a void/kerf crossing hold. I'm told it works but few people need it. I have a morse sophisticated algorithm but its still a work in progress. It uses moving averages and looks at dv/dt (change in volts over time)

If you go to the last few pages of the plasma section on this forum, you will find a few components I wrote for torch auto sampling and other plasma functions you may be interested in.

I used Phills void sensing feature for the first time the other day, and it worked perfectly. I was cutting some left over 25mm plate and I had some large lead ins in the section I was cutting. It cut through the large lead ins without the torch diving. Before I would always have to restart the machine as the float switch was activated.

I thinks its foolish to say that the people working on LinuxCNC are not continuing to improve. They are not constantly redeveloping how the basic program functions, rather continuing to improve the features it has. And I for one think that is the most productive thing to do.