QtPlasmaC release.

snowgoer540 wrote:

Yep, I see that behavior too (nothing to do with your Debian release).

Agreed but if afix is pushed to master branch, Tommy will need to build the source to get it!

rodw wrote:

Agreed but if afix is pushed to master branch, Tommy will need to build the source to get it!

[/quote]
Seems i do not have to, went to update/upgrade one of the PC today and the new version got installed ! Maybe, as i did not check.
-
Also on a good note, the updater worked perfectly when converting from PlasmaC to QtPlasmaC.
-
What was not good was when cutting 10 wizard pieces of 50x25 squares, on the 5th piece, the torch fired, arcok went on, machine started moving, arc was lost but the arcok remained on, machine kept moving, voltage was 0, THC was active, up/down were off, piece 6 and subsequent pieces continued cutting without issues. No errors were reported.
I did try to repeat this but could not for the limited time i had.
BTW, the arcok is derived from voltage/THCAD.

tommylight wrote:

Latest QtPlasmaC on Debian "Unstable", here is a strange one:
-home all
-wizard, 50x25mm box, inside leadin 4mm, 5mm radii on all corners
-wizard multiply at 5 columns 2 rows with 55 and 30 offsets
-send
-run
-stop using esc or cancel
-run again = it moves the start point to the second box
-stop again
-run again = it moves to start point to the third box
-rinse and repeat
-
-if left to continue, it will do all boxes, but they will not be where they should.

This should be good to go in version 1.223.184!

Sorry, did not check as i had to replace the HDD to revert back to PlasmaC for training, but i do still have the drive in case you might need that info.
Also doing a howto for the above setup, it is painless although it downloads over 1GB of packages, but works always without braking anything.
I have it on 6 HDD/SSD by now, not sure why (OCD ) as i am not using QtPlasmaC for running machines, only for testing.

Here i go again on my own .... Whitesnake !
-
Keep in mind this is on Unstable Debian, so needs more testing.
Debian Bookworm, QtPlasmaC v1.223-181 i think, same version on two different PC's, both lock GUI solid at random, today on one, a few days back on the other. On both cases everything else runs normally, even milltask and Python3 are all good. Forgot to try to start a config again, it normally asks if it should close the running instance, just to check if it finds it as i could not find it in TOP or HTOP.

-
Something that does not need testing, why QtPlasmaC does not use the "machine-is-enabled" pin?
This is a PncConf generated config, not edited, it would not turn on the drives, while in Axis it does.
X-enable works.

tommylight wrote:

Something that does not need testing, why QtPlasmaC does not use the "machine-is-enabled" pin?
This is a PncConf generated config, not edited, it would not turn on the drives, while in Axis it does.
X-enable works.

That is interesting, QtPlasmaC makes no changes to the machine in PnCconf that I am aware of with the exception of adding the QtPlasmaC requirements.
Can you post the PnCconf file.