So whats different about Linux for CNC?

[Rodw]

I thought now there is a new section, I better add some content. I'll add a few topics from time to time that hopefully make a case for using Linuxcnc. I might add, that I don't really care what OS I use, but do like to choose the right one for the given application. In fact, I even have a Windows based NC control on a press brake which is pretty awesome. I have to say I have never used Mach, so I might get some details wrong, and this might become more of a history lesson but here goes.

Believe it or not Mach and Linuxcnc came out of the same US government department called NIST. They came up with NML,
"The Real-Time Control System (RCS) library is a C++ class library intended for multi-platform real-time distributed applications."

You eyes may glaze over, but you can read the nitty gritty here https://www.nist.gov/el/intelligent-sys ... rs-guide-c

NIST passed on their work to industry and Mach picked it up and ran with it (it did say multi-platform right?). Then the Linux EMC project (Enhanced Machine Controller - now Linuxcnc) became an open source project under the GPL2 license.

The key here is that NML is a real time system which is what CNC requires. Things must happen on time every time without fail. Linuxcnc chose a more complex path and worked with a Linux real time operating system kernel called RTAI. This real time OS kernel meant that Linuxcnc could be THE_MOTION _CONTROLLER

But then Mach ran into problems with Windows becasue as Windows matured into a multi tasking OS, it was impossible to guarantee real time performance as another task could interrupt a time critical process (like CNC). So to solve this problem, Mach moved their motion controller to an external board so the Smooth Stepper et al became THE_MOTION_CONTROLLER. The capability of these microprocessor controlled boards is fairly limited and they cannot offer anywhere near the power available from a modern PC CPU. (Thats why they call them a microprocessor right?)

Linuxcnc on the other hand did not have these problems as all the core activity remained on the PC. But there is a cost. That cost is that to use Linuxcnc, you needed to install a Real time OS kernel (Like RTAI). Few people other than CNC integrators and the music industry so RTAI languished.

Then a funny thing happened. Industry required a real time kernel and an alternative to RTAI emerged called PREEMPT_RT. Suddenly big players with money put their development team on the project and paid their wages. BMW and other automotive manufacturers became involved becasue they needed a real time OS. When you need an airbag to be deployed, you don't want it to go off late right?

Then with the slow demise of parallel ports, a company called Mesa developed a series of ethernet boards that Linuxcnc (THE_MOTION_CONTROLLER) could command. Ethernet is not exactly a real time environment so using these boards required the PREEMPT_RT kernel.

Back when I first became involved with CNC about 1995 or so, I ended up having to patch the Kernel source code with the PREEMPT_RT patch and then compile the Linux kernel which took 5-8 hours. I did not know about this when I bought my Mesa 7i76e so I did what I had to do to use my new hardware.

PREEMPT_RT has gathered a head of steam and from all accounts, it will eventually become the default Linux kernel so eventually, every Linuxcnc distro will be running this kernel by default. As a result, the Debian software repositories now include a PREEMPT_RT upgrade that can be applied to any Debian system and its derivatives like (Linux Mint) by typing a single line at the terminal n about 10 minutes.

Phew, thats enough history. In my next post I'll try and summarise some of the great benefits available by using Linuxcnc as your motion controller.

[Rodw]

This post reserved for Linuxcnc features.

[Buckmaster1967]

Fantastic info. In the progress of switching form Masso controller to Linuxcnc. Thanks you for the write up.

[RDA]

I thought now there is a new section, I better add some content. I'll add a few topics from time to time that hopefully make a case for using Linuxcnc. I might add, that I don't really care what OS I use, but do like to choose the right one for the given application. In fact, I even have a Windows based NC control on a press brake which is pretty awesome. I have to say I have never used Mach, so I might get some details wrong, and this might become more of a history lesson but here goes.

Believe it or not Mach and Linuxcnc came out of the same US government department called NIST. They came up with NML,
"The Real-Time Control System (RCS) library is a C++ class library intended for multi-platform real-time distributed applications."

You eyes may glaze over, but you can read the nitty gritty here https://www.nist.gov/el/intelligent-sys ... rs-guide-c

NIST passed on their work to industry and Mach picked it up and ran with it (it did say multi-platform right?). Then the Linux EMC project (Enhanced Machine Controller - now Linuxcnc) became an open source project under the GPL2 license.

The key here is that NML is a real time system which is what CNC requires. Things must happen on time every time without fail. Linuxcnc chose a more complex path and worked with a Linux real time operating system kernel called RTAI. This real time OS kernel meant that Linuxcnc could be THE_MOTION _CONTROLLER

But then Mach ran into problems with Windows becasue as Windows matured into a multi tasking OS, it was impossible to guarantee real time performance as another task could interrupt a time critical process (like CNC). So to solve this problem, Mach moved their motion controller to an external board so the Smooth Stepper et al became THE_MOTION_CONTROLLER. The capability of these microprocessor controlled boards is fairly limited and they cannot offer anywhere near the power available from a modern PC CPU. (Thats why they call them a microprocessor right?)

Linuxcnc on the other hand did not have these problems as all the core activity remained on the PC. But there is a cost. That cost is that to use Linuxcnc, you needed to install a Real time OS kernel (Like RTAI). Few people other than CNC integrators and the music industry so RTAI languished.

Then a funny thing happened. Industry required a real time kernel and an alternative to RTAI emerged called PREEMPT_RT. Suddenly big players with money put their development team on the project and paid their wages. BMW and other automotive manufacturers became involved becasue they needed a real time OS. When you need an airbag to be deployed, you don't want it to go off late right?

Then with the slow demise of parallel ports, a company called Mesa developed a series of ethernet boards that Linuxcnc (THE_MOTION_CONTROLLER) could command. Ethernet is not exactly a real time environment so using these boards required the PREEMPT_RT kernel.

Back when I first became involved with CNC about 1995 or so, I ended up having to patch the Kernel source code with the PREEMPT_RT patch and then compile the Linux kernel which took 5-8 hours. I did not know about this when I bought my Mesa 7i76e so I did what I had to do to use my new hardware.

PREEMPT_RT has gathered a head of steam and from all accounts, it will eventually become the default Linux kernel so eventually, every Linuxcnc distro will be running this kernel by default. As a result, the Debian software repositories now include a PREEMPT_RT upgrade that can be applied to any Debian system and its derivatives like (Linux Mint) by typing a single line at the terminal n about 10 minutes.

Phew, thats enough history. In my next post I'll try and summarise some of the great benefits available by using Linuxcnc as your motion controller.

Hello Rod,

I would be interested in maybe contributing to the project in some way. Would you please PM me somesort of contact as I am unable to PM you in here and the linuxcnc forum doesnt have PM option at all? Im a bit sceptic in putting my email here in public.

[acourtjester]

You can PM any member by going to the right side where their icon is click on the contact bubble icon as shown in this attachment it will take you to the PM section. you can remove the info in the PM page as it will be a copy of the post you have been in to get the members PM connection. enter your message and hit send. I will stay in your outbox until the member picks it up, some never do
You can enter you email or ask for theirs this PM is not show to anybody then the member you PM to. You can attach files that have been ZIPed to the PM for the member to download from the PM. :

pm icon.jpg (7.56 KiB) Viewed 8218 times

pm icon.jpg (7.56 KiB) Viewed 8218 times

[Rodw]

Hello Rod,

I would be interested in maybe contributing to the project in some way. Would you please PM me somesort of contact as I am unable to PM you in here and the linuxcnc forum doesnt have PM option at all? Im a bit sceptic in putting my email here in public.

PM sent on this forum

[BTA Plasma]

There is a ton of back story to Mach and Linux. A LinuxCNC interface was developed by Apple computer for Brother industries in their new Speedio CNC. LinuxCNC was also implemented by Mazak, Haas and others. Linux was recently used by SpaceX in its last 5 launches and os systems. Its biggest advantage is its real time control. For Haas it allowed them to monitor more encoder counts per unit time and adjustment algorhithms for trajectory planning and real time positional values. This allows Haas to go from analog to fully digital in 2013. We have several Linux CNCs in our facility.

[CarterKraft]

Cool info

[robertspark]

There is a ton of back story to Mach and Linux. A LinuxCNC interface was developed by Apple computer for Brother industries in their new Speedio CNC. LinuxCNC was also implemented by Mazak, Haas and others. Linux was recently used by SpaceX in its last 5 launches and os systems. Its biggest advantage is its real time control. For Haas it allowed them to monitor more encoder counts per unit time and adjustment algorhithms for trajectory planning and real time positional values. This allows Haas to go from analog to fully digital in 2013. We have several Linux CNCs in our facility.

think this is a bit confused between Linux and linuxcnc and Linux using a real time kernel.

I do not believe that Apple used linuxcnc or mazak and has have ever used linuxcnc.

they may have used Linux with a real time kernel and a software application of their own creation to use Linux + the real time kernel in a CNC application but it was not LinuxCNC

if they had.... they would have to make available their source code as that is a condition of using linuxCNC.

one manufacturer that has used linuxcnc is Tormach.... they did do some development work with the planner and that has since been back ported into linuxcnc.

other users of linuxcnc that I am aware of is CandCNC although I believe it is now using a 2.7 version of linuxcnc along with one of the Ubuntu distros that may be past or near end of LTS (long term support).

linuxcnc is presently on stable release 2.8.2, with the current master (development branch) being 2.9 and I believe highly likely to be a full major release (2.9) as it is fairly stable and is being tweaked pending the next stable release from Debian (bookworm) in about August / September next year,

2.9 has a lot of things within it and available different to 2.8 (qtplasmac for one, as well as a departure from python 2.7 (a major change) with knock on implications for gtk and glade etc etc that had newer versions for python 3

the flexibility of linuxcnc is quite amazing once you get you head into it and what it can do and the availability of the Mesa source code to reconfigure all 26 pin output ports (or 50 pin IDC) to ANY input and output function is really phenomenal!

yes it can be confusing if you are like me and used to plug and play and click desktop icons but STICK with it.

I came from a background of USB smooth stepper with mach3 then in to ethernet smooth stepper and was highly supportive of warp9 and the smooth stepper but wow could those guys drag their heels with getting that board to FULLY work properly and do everything it was capable of ..... I tried to "upgrade" to mach4 + ess .... man was that painfull .... nearly every time a new release of mach4 came out the ess plugin broke..... hence the pluggin was only compatible with a specific version or range of bug fix / development releases of mach4..... kind of like trying to fix a formal 1 car and provide it with upgrades during the race with guys running along side it IN THE RACE!!!!

(I am well aware that the ESS has come on leaps and bounds since I last used it.... this is just my story and perspective at the time, I am aware to the THC integration that has since happened too).... same applies to mach4!

needless to say I got fed up with promises of the next missing features of the ESS that were to be released in 6m.... that went by and were never released.

I looked around for a board.... considered acorn and many others ..... and settled on cncdrive + uccnc ... because it had its own software and their boards had plugins for mach4 and mach3 ... just in case I wanted or needed to go back.

their boards and uccnc were great..... did almost everything I needed up until I wanted to get my lathe sorted using uccnc..... and they at that time had no interest in developing features..... vivid hit and all development stopped ... what was monthly bug fix and development releases went to nothing for 6-9 months and even then it was the minor of changes....

so I again looked at linuxcnc as I had a Mesa board it had been configured for plasma it was ok ... but not brilliant at that time..... then I decided it was either all in or shut up !!! so I've converted everything to linuxcnc
plasma
mill
router
lathe
and it's finally clicked and I'm starting to see how it all works plus the flexibility of Mesa boards to be able to be configured for ANY input or output function on any pin with the freely available source code for their FPGA boards ( very fast .... up to 10 MHZ step and encoder feedback rates! )..... the ability to run closed loop servos or steppers if you have encoders on your stepper drives (I don't)

there has been a lot of development with graphical user interfaces and the eye candy of looking modern.... and whilst I use qtplasmac for plasma (very clean and neat interface) I have switched back to axis for the mill, router and lathe as it JUST works ... and it's SO simple and clean. it CAN be modified and very simply to look and feel differently (I use a 24" touchscreen so have changed the icon buttons to be larger etc).

anyone starting out in CNC should REALLY consider linuxCNC ... but you need to stick it out.... it won't be easy especially if you are either from a click-click + plug and play background of windows but the rewards will be great and the costs won't be that high.

trust me as I bought:
usb smooth stepper
ethernet smooth stepper
mach3
mach4
proma 150thc
CM126 break out board
CM201 break out board X 2
minthc
uc400eth
uc300eth
uccnc X 2 licences as they are hard coded to the hardware
CNC room UB1 break out board for uc300eth
CNC room UD1 breakout board for uc300eth
pokeys 57E for mach4 lathe
CNC room pobob for pokeys to be used on mach4 lathe
neuron lite THC
____________

scrapped the lot^^^^

now running
Mesa 7i76e for mill, router and plasma
Mesa 7i92 + 7i76 for lathe
+ Mesa 7i98 for bench testing and development (3x 17pin input / outputs using 3x 26pin idc connectors... same cost as a 7i92 with 2x 26 pin IDC connectors

using a superpid for the router
mill uses a VFD
lathe uses a servo spindle drive with 1000ppr spindle emcoder
plasma uses a thcad5 for THC via internal linuxcnc+plasmac control.

fully configurable via hal and Mesa firmware.

I also have a creality cr10s 3d printer and an atomstack S7 M50 (10w laser diode cutter / engraver that are not using linuxcnc)

my advice to myself ~2006/8 when I bought the usb smooth stepper and started on my journey to convert a pmx350 to CNC.... ignore everything else try linuxcnc and stick with it the rest you are dependent on others on developing and bug fixing .... with linuxcnc you are the maker of your own destiny and you have way more chance of fixing whatever the bug is and developing whatever the way YOU want. the rest is just full of pipe dreams and missed promises and dates of stringing you a long when you find an issue or have a really good idea of find that it doesn't quite do what you want now you have learnt or heard about something as you learn what CNC is all about and what all the g and m codes do when you get past the basics.

PS >> {shameless plug} I can now offer pre configured pcs all set up for linuxcnc + plasmac or whatever you want in a plug and play box.

to get it truly plug and play I will need info from you as my crystal ball works overtime already..... but I'm happy to work with anyone for a plug and play solution to convert from whatever to linuxcnc in whatever flavour (plasma mill lathe router etc mach3 mach4 printer port whatever!!!!)

yes there will be a lot of questions ..... but then again how plug and play do you want it..... only you know the hardware sat in front of you and can advise me what it is and how it is configured.

you can buy your own cards direct from Mesa and I will provide custom firmware for you to load onto the cards that just works. some cards are proving difficult to obtain due to chip shortages..... no problem I can advise hardware and breakout board options or just an plug and play hardware card.

I am able to offer custom PCBs or breakout boards too... if you have something quirky.... or require something custom.

no I am not a programming expert just the tip of the linuxcnc iceberg..... and beginning to see the picture and it's potential.

no I cannot get linuxcnc to work on some oddball arm SBC, or to get it to run on some poor latency pc or laptop .... but if you want Linuxcnc in a plug and play box, not a problem happy to help with your build or conversion

[Rodw]

I have to say I've watched Robert transition from somebody who resisted Linuxcnc because of the effort that can be involved in getting it going through to a power user. My journey started in about 2015 with a mesa card and a desire to build a plasma machine. Little did I know plasma was not well supported but the efforts of a number of us to use new features set the way forward for the development of Plasmac and the later QTPlasmac.

Linuxcnc today is much easier to get going now then it was when I started. But one of the most exciting thing is that Linuxcnc is now a standard package included in Debian. It started in their unstable branch and is now part of testing branch (also known as Bookworm). This branch will become the next official Debian release in about 12 months.

The other interesting thing is that Linuxcnc also supports Ethercat devices and I've been working with them for a while now. This is a big deal and I'm told its a a AUD $1400 addon to Mach4. But I'm sure Mach4 would not support the 6 axis Ethercat robot that David in the UK got moving with linuxcnc today. It shows as a single ethercat slave device.

I just added 42 wires to 5 x stepper drives in a control box this week. With Ethercat, all I would have had to do is plug in some daisy chained ethernet cables! Plus some Ethercat drives can be homed internally and some even allow homing by stalling! So it may be feasible to build a gantry machine with no home or limit switches at all. This would further reduce the wiring required.

But don't give up hope on SBC's (single board computers) just yet Robert! David is controlling his robot with a Raspberry PI 4 and is just finalising the build process of a raspberry Pi image that can be just burnt to a SD card that contains everything. I've been on the sidelines with this project and its very exciting as it will include ethercat, and the dependencies of both QTPYVCP and QTVCP which are used for various GUI's. The reason we can do this is because the Debian buildbots are building Linuxcnc across a number of platforms including ARM64. So we start with cross compiling the Bookworm kernel for the Pi on a AMD64 PC. And install Linucnc from the Bookworm packages.

So as Robert says, give linuxcnc seroius consideration for your next CNC project!

[robertspark]

not given up on SBC's + linuxcnc or the Rpi4 + linuxcnc. Just in my opinion it's not where a new user of linuxcnc should be aiming to understand how it works. {destination yes, but not the first install}

I'd go so far as to say that you could probably get linuxcnc to run on anything.... subject to a real-time kernel being available to able to be built.... but that is really niche {non amd64 {64bit pc} or rpi4}

I've seen the development of EtherCAT going on and understand the principle (ethernet daisy chain transmission + very high speed)
I looked at EtherCAT drives and baulked at the cost. {don't think I'll be using them soon.... hey but everything get cheaper over time.... like cnc 20 years ago being niche.... now every many + his dog has a cnc machine of some sort)

never done anything with analog drives, or resolvers etc.... but linuxcnc does it ALL when you have a look under the bonnet, and the key is the mesa cards and their sourcecode and firmware.... just buy an ethernet one and you can plug it into many more machines especially if your PC dies, just swap it over and set up your backup

Nope it does not do stuff like plasmacam (designedge) {draw + cut} ..... there are only widgets / conversational scripts of various types (qtplasmac, ngcgui, nativecam, qtpyvcp_conversational) .... but you can draw in something else for FREE (inkscape / librecam / freecad) and in some cases just save as an svg and load them into linuxcnc and cut.... in other cases .... use something like sheetcam to do the post processing (or an inkscape pluging >> gcode )... there is always a way. Sometimes it can be convoluted but there is always the option for you to imoprove your workflow as sourcecode and many other users tips are available.

[Rodw]

not given up on SBC's + linuxcnc or the Rpi4 + linuxcnc. Just in my opinion it's not where a new user of linuxcnc should be aiming to understand how it works. {destination yes, but not the first install}

I agree. while Linuxcnc has a has an image for the RPI4, its been on 32 bit and suffers from latency. The new official PI OS images are 64 bit and based on Debian Bullseye. It gives decent latency but has been missing some key dependencies.

But the Pi is also open source and these can be compiled from source. But compiling VTK containing almost 10000 files (which we got down to 4800) is a 10 hour job on a PI so not everybody's cup of tea. Having it as part of an image athat can be burnt to an SD file to boot the pi, might be a game changer. I might add the Pi has become expensive so you really need to save the space as there are industrial fanless PCs that are cheaper and work well!

[beefy]

I'm a bit like Rob.

With my plasma table I've been through:

• Candcnc all in one package using Mach3
  Cncdrive's controller which is UCCNC, combined with their ethernet motion control cards, an excellent 3rd party breakout board (UB1 mentioned by Rob), and my personally designed THC that communicated with UCCNC plus I also designed a custom screenset to go with it.
  Neuron Lite THC working with UCCNC

Finally ended up with LinuxCNC and Qtplasmac.

Yes Linuxcnc and Mesa cards are what I've finished up with after various frustrations with the above, some of which Rob has already mentioned. But I do have to admit I sometimes find the Linuxcnc documentation lacking for someone coming from Windows. One of the best things you can do is watch a few tutorials on Linux itself, get to understand the file system, how installation is done, etc. Then move on to Linuxcnc.

Plenty help out there on the forums too.

[robertspark]

one of the things that seems to catch new linuxcnc users out is the graphical user interfaces (GUIs) or screensets in other CNC softwares.

given this is a plasma forum, I will not go into the other eye candy, but my advice is always use AXIS which is the basic very old looking screenset. it is ROCK SOLID, it is simple, it is clean and everything is available for mill, router and lathe and available by default. some of the other eye candy GUIs can be a bit tricky to get working requiring a fair bit of tricky typing and occasionally something breaks. AXIS just works.

Plasma however is something different, there is a relatively new GUI that is clean, fully functional and very easy to install. there are a couple of guys who developed it and have put a lot of time into honing it. it is very stable, very easy to install and very clean and simple (functional) to use. it just works!

that's GUI is QTPlasmaC.

under the bonnet is uses a component called PlasmaC.

below are a few screenshots. these are the ones from the very detailed and fully documented documentation on QTPlasmaC. that small group of guys who have dedicated a lot of time to developing this and providing a full package have done an outstanding job. hence it too is ROCK SOLID, simple to use, functional and very clean to use. you can use it with a touchscreen if you want, or keyboard and mouse.

9x16 (landscape) screenset common with a lot of monitors these days (what I use with a 23" touchscreen)

qtplasmac_16x9.png (149.4 KiB) Viewed 8047 times

qtplasmac_16x9.png (149.4 KiB) Viewed 8047 times

4x3 older more square monitor screenset

qtplasmac_4x3.png (221.28 KiB) Viewed 8047 times

qtplasmac_4x3.png (221.28 KiB) Viewed 8047 times

9x16 (portrait / vertical) screenset for those that want a screen maybe at the side of the machine, without a keyboard or mouse.

qtplasmac_9x16.png (136.12 KiB) Viewed 8047 times

qtplasmac_9x16.png (136.12 KiB) Viewed 8047 times

Settings Screen

stats screen

conversational gcode screen for quick and simple profile cutting

one screen that is missing (or I could not find an image of it) is the Materials Handling screen. basically that is the tool table in simple terms, it is where in QTPlasmaC you set and store all of your cut parameters, so it's like the tooltable in sheetcam. but it holds a lot more information.... it is like CandCNC's sheetcam post processor that adds fields to sheetcam tool table. it sort of makes sheetcam sort of redundant in part. because you don't need to populate or use the tooltable in sheetcam. all sheetcam is used for is to create the cutting profile / shape, cut start and end point, plus any changes from one "tool" such as maybe a scribe or a simple marking operation to a plasma cutting operation.

once you have a profile, you just open it in QTPlasmaC and select the material you want to cut it with, 2mm / 4mm/ 20mm / inch / 1/4" whatever and QTPlasmac will automatically set the cut voltage, feedrate, pierce times etc etc from its material setting stored within it.

No you cannot DRAW a shape in QTPlasmaC, and you cannot convert a shape in plasmac to gcode or a cut file in QTPlasmaC, you will still need SheetCAM or (maybe) inkscape to do that. (not tried inkscape to gcode), or you could try to use a grbl gcode tool.... all you need is the profile.... it is better if you can create the gcode in the right format as QTPlasmaC Hass a lot of features that are embedded within modified gcodes to say select the right tool or turn the THC on and off etc so sheetcam would be best and just works with the PlasmaC post processor.

I am aware that linuxcnc will import many file formats such as SVG and I think even png but I don't think this works with qtplasmac as you really want a clean profile to cut.... the use of pngs and other image file types can be a bit fuzzy and are used for things like V-Carve milling and routing where the fuzzyness gives the image cut depth.


And that is IT, clean and simple, you can change the colours from yellow to whatever, I use green as it stands out.

[Rodw]

Back to the discussion around documentation for QTPlasmac,
The documentation is here
http://linuxcnc.org/docs/devel/html/pla ... asmac.html
You can find this page from the main docs page I linked to before under the heading user interfaces

[robertspark]

the basic choice you have to make is how do you want the Torch Height Control (THC) to work.

you have 2 options:

simple up / down input from an external THC (such as a proma 150 or a minithc or a Price AHVC/THC). sure it works... but it's not brilliant as you are not going to be using PlasmaC / QTPlasmaC to its full potential.

or fully integrated arc voltage signal control where the PlasmaC component gets to directly receive the plasma arc and it controls the torch up and down motion directly and the voltage setpoint is set within QTPlasmaC. This is the best option as it gives you full control based on an analog input (voltage) from the plasma cutter.

the next choice you have is how to decide it is ok to start cutting motion. known as the arcOK or transfer signal. Again you have 2 choices.

if you chose to use an external THC to provide THC up and down signals, you have no choice to make, your THC or plasma cutter must provide that transfer signal. as PlasmaC does not see the actual cutting voltage it just gets the signal to move the torch up and down. this is the same as Mach3, Mach4 and Uccnc and others.

if you chose to feed the plasma cutting voltage into the PlasmaC component then you have two choices and both or either will provide you with similar benefits and be on a par with CandCNC's offering, or using something like an external THC with voltage setpoint integration like a Neuron Lite or Pro THC or a Razerdance THC.

your choice is to either use that received analog voltage signal to decide if the arc has transferred OR use the plasma cutters own ArcOK or transfer signal. either will work just the same and just as good and if set correctly will provide the same cut results, given that is what the game is all about.... what the finished part looks like in your hand all things being equal with cut speed, table build quality, servos, steppers and drives and plasma cutters.

the rest is optional and the cherry on the cake if you have things like the hypertherm rs485 machine interface, PlasmaC can interface with it and adjust or read settings same as CandCNC's offering.

All opensource, and FREE and well supported, with a lot of machines now being used in commercial environments (it's just a hobby for me, no financial interest really, I have a totally unrelated day job to CNC plasma or manufacturing or selling anything).

yes if you want to go the recommended route, a Mesa FPGA board will be required, minimum spec similar to the Ethernet Smooth Stepper or CNCDrive un400eth but much better as it is both faster AND the source code is provided should you want to configure any pin to do something else.... $100 USD done! cheaper than the smooth stepper and the UC400eth.

no that won't get you a breakout board.... but you don't get one with a smooth stepper or a uc400th!

you can choose to use a single or pair of cheap chinese breakout boards.... or spend a little more and get the Mesa 7i96 / 7i96S (the chip shortage has affected their product range a bit + boards availability) $119 / $149 USD respectively.

with regards to voltage input, you can roll your own device to convert the voltage signal to a frequency ..... or just buy a Mesa THCAD board (there are 3 variants, just input voltage difference) all cost $69 USD. nothing to compare with.

given linuxcnc and QTPlasmaC is FREE to compare it to any other offering is difficult as anything divided by zero on my calculator gives error!

sure anything divided by your hardware selection cost will provide you with a number to compare against but it's a no-brainer..... hindsight is a funny thing but I wish it had been about when I started on my expensive trek into CNC .

take a hop over to the linuxcnc forum and ask any questions or feel free to ask them here as there are a few of us who frequent both forums, but the guys who do a lot of the under the bonnet stuff reside I've on the linuxcnc forum .... we don't bite (much) but I know I struggle to know what level of CNC / Linux / linuxcnc user we are trying to help with some of the questions that you see posted..... so a bit of a background helps, and you can never have too much information when asking a question.

[acourtjester]

Lots of great info from you guys, I'm about 85% done with a new table using Linux. Got sidetracked but need to get back to it soon, it is all there just some finer details needed. I ran into a mental block with the signal formation for the Ohmic sensor. When I get back to it I will seek out help then.

[cutnweld]

Ha same here, we had my servos running on the bench from Plasmac jog buttons, tested the arc volt signal etc etc, its going slow here because what i have is working (sort of) and I am extremely busy with the repair side, was hoping for a lull this winter but it never came... Just the little fiddling I have done with the interface, my 2 cents are that the conversational side, along with the camera aided sheet alignment, not to mention the realtime thc along with other benefits, make this the new standard in the plasma cutting world. Honestly I cant see why some of the OEMs out there aren't using it, My current running system has about 49 pcbs, all kinds of cables running everywhere, my new one has a total of 3 boards with ohmic sense and thc. Cant be much more simple can it?

[Rodw]

your choice is to either use that received analog voltage signal to decide if the arc has transferred OR use the plasma cutters own ArcOK or transfer signal. either will work just the same and just as good and if set correctly will provide the same cut results,

I might add, if your plasma cutter has an ArcOK (eg transfer) signal I strongly recommend you use it. The QTplasmac docs even show you how to add it to any plasma cutter using a reed relay.

The reason I recommend this is the arc voltage is very chaotic for a few milliseconds after a pierce and QTplasmac depends on a voltage threshold being reached to enable arcOK. Sometimes after this is reached, the voltage can fall below the threshold again and QTplasmac senses a loss of the cutting arc as you start... and cutting stops or won't start.

[Rodw]

Honestly I cant see why some of the OEMs out there aren't using it, My current running system has about 49 pcbs, all kinds of cables running everywhere, my new one has a total of 3 boards with ohmic sense and thc. Cant be much more simple can it?

Tormach use Linuxcnc. They use a variant of the THCAD where a single board provides both ArcOK and Torch voltage. I suspect from the images I've seen its a custom board made by Mesa for them. So 2 boards! simpler again!

[robertspark]

Some screenshots of the QTPlasmaC Conversational Wizards {they have just been changed to use SVG's)

I use a green screenset colour but you can use whatever you set

https://forum.linuxcnc.org/plasmac/4606 ... ent#244400

[N2 Welding]

Ok you guys have peeked my interest. Just read through this whole thread. Not through the history links though :p

You mentioned @ couple times now the benefits of real time with CNC and the need of having a low latency network system.

How would a Dell Optiplex 9010 work for LinuxCNC and QTplamaC

[acourtjester]

Only from my experiences, I have a Dell Optiplex 970 SSF PC I am using. I did have some problems to start with undetermined errors which I though were from the Latency issue. That problem cleared up when I removed the wireless keyboard and mouse, I found a post that stated they were a problem. QTPlasmaC has some very nice features and you can add custom buttons for more. Like test firing the torch, doing a test Ohmic touch off, do a frame move around the G-code perimeter. The GUI has pages you flip through for all the info selection or importing G-code or cut spects or other helpful functions.

[Rodw]

There is a video I did about its features since this thread was raised.

And cut recovery

[N2 Welding]

Only from my experiences, I have a Dell Optiplex 970 SSF PC I am using. I did have some problems to start with undetermined errors which I though were from the Latency issue. That problem cleared up when I removed the wireless keyboard and mouse, I found a post that stated they were a problem. QTPlasmaC has some very nice features and you can add custom buttons for more. Like test firing the torch, doing a test Ohmic touch off, do a frame move around the G-code perimeter. The GUI has pages you flip through for all the info selection or importing G-code or cut spects or other helpful functions.

I won't use wireless keyboard and mouse then lol. Not to start with any way. These systems did not come with an add in wifi/blue tooth card so not sure it would be an issue any way. They are decent PC's I got 5 of them for $100 one of them is the Optiplex 990 that has a slower ram and cpu. ram runs at 1066 and cpu is a i5 2400 95w cpu but the other 4 optiplex 9010 have the i5 3470 73w faster cpu's that run cooler and the ram runs at ddr3 1600mhz so not sure but hoping the Optiplex 9010's are fast enough with no latency issues on the Nic and I think all of them have a built in Intel Nic. Hoping the intel Nic won't be an issue for LinuxCNC