QtPlasmaC release.

More
11 May 2022 00:15 #242544 by tommylight
Replied by tommylight on topic QtPlasmaC release.
Also, i think i mentioned this several times, but i will mention it again:
Mode 0 or synthesized ARC-OK signal works perfectly well with a 50A Cebora, works OK 90% of the time with a Thermal Dynamics PAC9 90A, Works 99.99% with a 120A Cebora @70A, works 99% with a 100A Oerlikon @70A.
I would consider that very good as that same Thermal Dynamics with it's own factory ARC-OK misses about 5%.
The default values in QtPlasmC set at 60/250V work very well and rarely need adjusting.
Pierce time set at 0.1 or 0.2 sec helps with some of the plasma sources.
-
Not important as this is specific to that Thermal Dynamic, at 30A it will show around 180V, at 70 and 90 it shows the normal 120V or thereabouts while cutting, due to a big resistor that is used to limit the current at 30A.
Just in case anyone bumps into one.
The following user(s) said Thank You: phillc54

Please Log in or Create an account to join the conversation.

More
12 May 2022 00:35 #242695 by phillc54
Replied by phillc54 on topic QtPlasmaC release.

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.

Thanks for the report Tommy, I have pushed a fix to master.
The following user(s) said Thank You: tommylight

Please Log in or Create an account to join the conversation.

More
12 May 2022 00:50 #242697 by tommylight
Replied by tommylight on topic QtPlasmaC release.

Thanks for the report Tommy, I have pushed a fix to master.


Oh good, i was waiting to be told that i shoot myself in the foot, again ! :)
As a side note and and a very big thank you to Chris Morley, PncConf does everything every time, and my stuff is not standard by any stretch of imagination. Lately it got to the point that i rather make a new config than looking through USB drives to find the ready made one.
Thank you, CMorley.
Also as a side note, a very big I am sorry goes to BigJT as i did not have time to use his wizards more.
Sorry, BigJT.

Please Log in or Create an account to join the conversation.

More
12 May 2022 00:52 #242698 by phillc54
Replied by phillc54 on topic QtPlasmaC release.

Oh good, i was waiting to be told that i shoot myself in the foot, again ! :)

Nah, it was just another one of my mistakes... :)
The following user(s) said Thank You: tommylight

Please Log in or Create an account to join the conversation.

More
14 May 2022 00:08 #242924 by phillc54
Replied by phillc54 on topic QtPlasmaC release.

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.

Unstable is the correct word, I have issues running Debian Unstable as a VM, until that works reliably I won't be looking at this issue.
The following user(s) said Thank You: tommylight

Please Log in or Create an account to join the conversation.

Moderators: snowgoer540
Time to create page: 0.088 seconds
Powered by Kunena Forum