Advanced Search

Thanks a ton, Greg. How soon will this hit Buildbot2, you figure?

QtPlasmaC updates - Master (v2.10):

• fix cut recovery bug
• fix user button removal
• fix some button interlocking templates
• fix user manual URL

Just pushed a commit that should fix this (and a few other issues).  This is entirely my fault, caused by a refactor of the way we were doing button interlocking (enable/disable).  As it turns out I trimmed too much fat and completely broke cut recovery.  I am honestly not sure how I missed this, but I appreciate you pointing it out nonetheless.  It's been broken since the beginning of Feb 2026.  Which either means not many people use QtPlasmaC on the master branch, or not many have cut issues requiring cut recovery, or both... 

I apologize for the inconvenience I caused.  

Please let me know if you run into any other issues!

Happy cutting.

-Greg

  Is it unrealistic to try and run this on 7.2.15 ?

Earlier this year i got hit by the idea, to build an airplane windspinner. The model is based on Nieuport N28. The body is made of oak, some other parts are made of screen-printed plywood panel

Just checking you know, home switches need to stay triggered to end of travel.
Also be sure to add a home-offset to move off the home switch trigger
 

I would try typing: lcec-configgen
and see how much of your configuration is done for you

If I had a Trademark on fusion360 and found someone with a product in the same trademark class called CNC fusion, I would be sending a Cease and Desist letter real quick. I recommend you change the name of your product. There are lawyers out there whose business model looks for opportunities to bill their client for trademark protection.. That would be an instant winner.

Johnsinski wrote:

rodw, oh I saw you on youtube! The new motion.interp.heading pin looks to give you the tangent angle of the current point on a path? That seems helpful.

oh well, tried to attach gifs of the two motion strategies, but didn't work.

Yes the heading gives you an arc tangent to a G2/G3 move which is the direction the wheels should be pointing to drive it. When you revert to a G0 or G1 move, the heading is simply the direction of travel which should also be where both wheels are pointing

Now in the case of  the inside wheel needing to travel  a shorter arc radius than the outer wheels, you should be able to calculate that from the outer arc.

Hi Sascha,

i wanted to thank you, you made my day with your hint, that's what it needed to get the smooth Handwheelfeeling i wanted!

Greets, Tom

Hi All. 

I am using SCARAKINS for my scara robot with (2 angular axis + 1 linear axis). The joint mode is working fine but when in cartesian mode the X axis does not move. Please help!  
Attached is the config. I am using MESA 7c81 with a regular BOB.
 

Hi Keith,
I had the same or similar problem yesterday, when I tested my new 7i96s. The estop remained activatet. The cause was: I had configured one input as estop, but left it unconnected during the test.

Sounds like either an electrical noise issue or maybe contact bounce.

What type of switches are used and what are they connected to?

I couldnt figure out what was interfering with the non-flash 'checked' state, but I figured out a workaround:  set the flashState="false" to the same color as "true" and the indicator appears solid when on.

Time to merge in to my live machine HAL and see if the hang problem I reported on GH have been resolved.

Greetings everyone, I call for help on a new issue with my plasma table. So basically when I go to press home all the homing sequence begins. The z axis homes successfully 90% of the time, the x axis homes successfully half the time, and the y axis gantry does not successfully home. I get these errors with the x and y axis.