QtPlasmaC release.
11 Apr 2022 21:36 #239979
by snowgoer540
Yep, I see that behavior too (nothing to do with your Debian release). It's actually moving the origin over by the appropriate offset, each loop (if you let it run you can see the origin move). It doesn't go back to "normal" because that is the last line of the g-code before the M2, and it was cancelled before it got there
:
When this all got implemented, a function was added to set the rotation back to what it was before the program was run, if the user cancelled.
It looks like possibly the same may need to be done for X and Y.
Thanks for pointing it out!
Replied by snowgoer540 on topic QtPlasmaC release.
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.
Yep, I see that behavior too (nothing to do with your Debian release). It's actually moving the origin over by the appropriate offset, each loop (if you let it run you can see the origin move). It doesn't go back to "normal" because that is the last line of the g-code before the M2, and it was cancelled before it got there
:G10 L2 P0 X[#<ucs_x_offset> * 1] Y[#<ucs_y_offset> * 1] R#<ucs_r_offset>When this all got implemented, a function was added to set the rotation back to what it was before the program was run, if the user cancelled.
It looks like possibly the same may need to be done for X and Y.
Thanks for pointing it out!
Please Log in or Create an account to join the conversation.
14 Apr 2022 23:32 #240275
by tommylight
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.
Replied by tommylight on topic QtPlasmaC release.
[/quote]Agreed but if afix is pushed to master branch, Tommy will need to build the source to get it!
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.
Please Log in or Create an account to join the conversation.
17 Apr 2022 15:45 #240475
by tommylight
Replied by tommylight on topic QtPlasmaC release.
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.
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. Please Log in or Create an account to join the conversation.
09 May 2022 16:02 #242391
by tommylight
Replied by tommylight on topic QtPlasmaC release.
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.
-
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.
Please Log in or Create an account to join the conversation.
10 May 2022 07:55 #242469
by tommylight
Replied by tommylight on topic QtPlasmaC release.
Later, i will be out today chasing gremlins!
Please Log in or Create an account to join the conversation.
Moderators: snowgoer540
Time to create page: 0.110 seconds