Advanced Search

In particular, that update is looking for 'nc_files/plasmac/m_files' in your USER_M_PATH, to be able to see the Mxxx files. It’s not seeing it so it’s trying to update the ini file to fix it.

Perfect that's where they're supposed to be:

I installed the latest package on buildbot2 for bookworm a few minutes ago, it opened the qtplasmac_l_metric simulation without issue, no update messages, etc.

This was fixed on Sept 6, 2024. Commit notes:

Did you think it referred to QtDragonHD, or Axis?

I suppose it could say something to the effect of "QtPlasmaC configuration changes mandated at V2.10-001.017 were applied". As a developer it's not always easy to know how the end user will interpret a message. Since January 23, 2024 you are the very first to complain.

There must be something going on with your OS/Installation. Simulations work fine on version V2.10-008.056 for a Package install and V2.10-008.061 for RIP. No update messages.

Click the Statistics tab, there's a MACHINE LOG frame, it'll be there. machine_log_{date/time}.txt in the config folder also reflects the log on the Statistics tab. It's also in the "update_log.txt" file in the config folder.

rodw wrote:

More feedback here. Customer has an IT savvy brother. His brother told him to lift the torch to clear the stall after reviewing the code and it worked!
It goes without saying, I have asked for a line number reference.

I think this implies the bug lurks in the plasmac.comp state machine somewhere.

I've already found my plasmac bug for the day. Maybe someone elses turn!

setp plasmac.debug-print 1

tommylight wrote:

I think i should do a summary of the Sunix PCI-E card as the info got scattered in pieces, so:
I had one, it works perfectly but:
In a Lenovo PC it show the warning when LinuxCNC starts, but it works fine
In another PC with Asus Prime Z270 board, it shows no warning and no ................................
IT JUST dawned on me:
It will show the warning on older kernels, it will not show on new-er kernels!!!
Lenovo has Mint 19.3, the Asus has Mint 21.3, the friend with the same model cards has LMDE 6
Ok just checked the original post and it is Debian 12 so most probably 6.1.nn kernel, should be the same as in LMDE 6, so there goes my joy, oh hell, back to more testing!

rodw wrote:

Thanks Greg, I've beem away for years and find a bug in 5 minutes 

The m_files folder was in ~/linuxcnc/nc_files/examples/plasmac

The files in the m_files folder under examples were owned by root and the user did not have permissions to the M codes

The INI M_CODE variable in the ini file was not updated in qtplasmac_metric_ini.inc. I suspect this was because its not the top level ini file (I'm not sure if you actually write to that folder)

qtplasmac: fix m_code pathing
Fixes the m_code path for a package install sim.
Allows update 001-017 to be applied correctly for configs that were build prior to then.

The error message should refer to plasmac so the user knows its specific to Plasmac. I had to deduce that by checking other configs

The version number reported does not reconcile with the version details displayed on startup 2.10.0-pre-4165-xxxxxxxxxxxxxxxx

Let me introduce you to Python try/except error handling www.w3schools.com/python/python_try_except.asp This would ensure the user is less bewildered when it  fails. There is nothing displayed on the screen when it fails

Perhaps the message could be a little more specific eg "updating qtplasmac mcode folder"

Perhaps the upgrade message could also be printed on the console. Displaying Top right when console is in bottom left meant I did not even see the error the first couple of times!

I might add Joco is also in trouble over this for adding these gcodes!