Found it !

github.com/LinuxCNC/linuxcnc/blob/v2.9.1..._auto_probe_tool.ngc

I don't think mesaflash has changed but rather your PC or BIOS

Did you just update to LinuxCNC 2.9 or did you change other hardware at the same time?

Thats what is exactly happening. So my options are get a new motherboard or put the 5i25 back in the old pc, and update the firmware in it. Also need to update the 7i77 firmware.

Will the 2.9 linuxcnc pc able to update the latest firmwares or is that verson of mesaflash too old?

rodw wrote:

LinuxCNC will run on VirtualBox and so on and this is handy to do basic testing and configuration. There is a limit on what can be done on a sim without real hardware.

 

That works. I run several versions of LinuxCNC as virtual machines at once in virsh during development/testing efforts. Virtualbox is great, too, but I got to fighting it all the time on my headless server. Virsh played nicer for me in configuring virtual machines on the headless server over ssh, then I connect with those VMs using Remmina remote desktop.

What does

lspci -v

report?

Is this a new motherboard?

I have seen this issue before where PCI devices are found but not enabled
(LinuxCNC enables disabled PCI devices but mesaflash does not)

The motherboard is using pcie to pci bridge. I am wondering if this is the issue. Mesaflash doesnt like i but linuxcnc doesnt mind. Just a thought.

Hi guys,

I have updated from 2.9 to the latest linuxcnc. It is running but two main issues one is the onboard 7i77 enc0 does not exist when it did before and mesaflash does not see the 5i25.

I assume the enc is related to the 5i25 and the 7i77 has old firmware message.

My question is Is it possible that the new mesaflash not see an old 5i25 card? and if not how to we get it updated?

Linuxcnc runs and see the 5i25 and everything seems to work except no enc0.

Thanks,
Bob

Bob
 

This repo is where probe basic et. al. live and it's been added as a convenience for users but its up to the qtpyvcp devs keep their repo current. I suspect its a transient issue from your message as I have not noticed issues here.

If you are not using any qtpyvcp stuff, you could delete the relevant qtpyvcp sources file in /etc/apt/sources.list.d
and do a sudo apt update

Hi RodW, yeah, sure. I am aware of that. The idea is just to get comfortable and experiment withe the Linuxcnc functionalities, configs etc.... of course later when I get all the stuff set up then will be a dedicated computer with real hardware.

qplasmac is a complicated GUI. Normally, it is set up assuming a mesa card using pncconf. 
I think I  would try running up pncconf and build a rough config for a 7i96s. You just need a template for all of the plasma specific pins so pick a mesa pin to use for each. don't worry about scaling the axes etc
Then I would copy the pin layout to your hal file and make sure any plasma  specific stuff in the ini file is copied to your ini file, then replace the Mesa pins with your lcec pins. 

With linuxcnc running open another window and type halcmcd show pin lcec should list all your Ethercat pins and you could probably filter out just the inputs or outputs

Also reviewing recent plasmac configs on the forum may help
I have one but its a very complex one with lots of custom stuff so would not recommend following it  github.com/rodw-au/showstopper/tree/master  

In the qtplasmac GUI, there is a couple of fields for THCAD parameters. Set the offset to 0 and scale to 1 and use the actual torch volts. You may need to use mult2 to calculate the full scale voltage. Alternatively, use the scaling field which might be better.

Good luck
 

Yeh, come along and we'll find out together. Dated ot not, adoption by Mazac, Siemens, Fanuc et al does give a platform for industry. BUt collection of data for statistical evaluation is saving some plants a lot of money by preventing unscheduled failures when for example an increase in motor torque is reported. In one case downtime was $1.7m per hour if the plant had a shut down.  

LinuxCNC will run on VirtualBox and so on and this is handy to do basic testing and configuration. There is a limit on what can be done on a sim without real hardware.

The Pi4b was marginal, sometimes requiring a slower servo thread but one guy I know says the Pi5 is flawless on real machines
I'd probably pair it with a mesa ethernet card. A Mesa 7i76eU has 5 axes, 16 outputs and 32 inputs but is extensible beyond that.
Linuxcnc supports 9 axes and 32 motors
Arduino is not useful for linuxcnc
There are several GUIs that support lathes but its always best to start with axis until you get everything functional.
Of course we are friendly!
You can mess with everything!
Check the docs as they list the GUI's available but you can write your own. Some support portrait mode.
I checked the other day, there's is over 1800 pages of docs but I always refer to the online docs.
There are no limits to motor size and it will control Ethercat and analog servo motors not just step and direction.
Linuxcnc is far more flexible than Centroid and is complete as opposed to Centroid where additional upgrades are required.
But it may require more effort from you  because there are probably more decisions you need to make becsause of LinuxCNC's flexibility

Re Youtube not sure on Lathe specific videos but I have a channel which is trying to produce tutorial type material.
This one is designed to be a general introduction describing the various pathways through Linuxcnc 

I'm currently working through a series of videos building a control panel from scratch using a parallel port (3rd one to be released tonight) with a couple more planned. Once fully functional, my plan was to replace the parallel port with other controller options. Sounds like I need to include a lathe walkthrough too!



 

easisest way would be to create seperate configs for each option

What is "the auto tool probe remap"? I mean I know what remap is in general, but it sounds like it is a name of something specific. Is it something one can download from somewhere? A quick googling didn't come back with anything specific.

In the meantime I studied the documentation and the source code a little bit, and I think I now have a clue what's what, and there are multiple ways to achieve tool offsets (G10 L2 vs. G10 L20 for instance). What I was looking for was a simple way and a sequence of click here, enter there kind of set of instructions.

I eventually managed to make the standard tool touchup work. The one where you enter the the tool height in the settings tab, enter the workpiece height in the offsets panel on the main screen, and you just click on the tool sensor button, which will calculate the Z value for the current WCS and sets it with G10 L20 (after touching the sensor with the loaded tool).