Advanced Search

I installed a 1A FF miniature fuse for the Mesa.

I am unable to reproduce the error on the sim because I needed to trigger the probe while it was going to home or the starting location to start probing. This would cause a G38.2 error then the lockout would start. I ran a debug and returned a [Error] from a specific routine. I should have grabbed a screenshot.. I noticed a difference in the sim subroutines folder vs the subroutines folder I got from the github. I replaced all the files and lockout is no longer accruing

What Mesa fuse? There are PTCs to protect the 5V encoder wiring, if these trip, you have a wiring error.

All correct, see attached screenshots

Thanks for the clarification spumco. I had thought for sure Fusion 360 had said something as to not working 
on windows 10 machines as of 1-1-2026, but since it is still for the moment working on my Win10 stuff.
I must have been mistaken. I will have to look back to see how to do Win11 LTSC. And yes for me
I am still stuck having to use windows for certain things at work. UGH

I moved them

sim
axis
axis_mm_scurve

instead of the main folder.

andypugh just sent me the Tormach 9 axis code, I will be looking at that closely...

After further investigating, it seems when queue buster, M66 E0 L0  or G38.n is used, makes the preview disappear and sub call level is 1
Most of my routines are used for years, and when there were problems with LOG, and DO / WHILE loop and others, queue buster always helped.

I modified a probing routine for diameter inside, just moving with G1. #<queue_bust> can be set to 0 or 1 , to see the problem

the file example.ngc is used to call example_sub.ngc


 

 

I haven't wired them up yet, but the fuse issue also happened when the power amplifiers were connected.

I would venture a guess at wrong wiring, so first check if analog grounds are wired correctly, from your explanation this seems to be the reason.

forum.linuxcnc.org/10-advanced-configura...to-example-mesa-7i77

The lower LED is slightly dim. I adjusted the voltage; it was 4.6V, now it's 5.1V. When I move the axis, the fuse trips immediately, but the wire only deforms slightly more. Is 1A too low, or is the Mesa fuse defective?

If I remember correctly, I've checked this back then and the the column R showed 0.0000 for G54 and other offsets. Clearing and saving the offsets did not help. Only G10 L2 P1 R0 resolved the issue. But since then, everything works fine. I will let you know, in case it happens again.

Here is a version, which creates a surfacemap.yml so the parameters persist throughout sessions. The variables like probe fast feed rate are still independent from the standard PB probing parameters. Maybe this can be aligned in a future version of this interface.

Hello everyone!

I am struggling with the implementation of my servo drives. I set up the pncconf wizard and did some adjustments, checked the Output Offset and scaled the Encoder. Now I want to start the machine an make some PID tuning, but if i toggle the Machine Power Button the Servos directly starts to turn. After a few secs i got an following error (make sens) and the Servos stops.

What is wrong in my config? Is this an Servo Controller Problem or an Mesa Setup Problem? What should i do next?

I am using the Linux CNC (2.9.4), a MESA 7I92TM connected via Ethernet and a 7i77 at Port P2 for the Servo Drive Control. My Servo Drives (Yaskawa SGDV-7R6A01A) run with +-10V and Encoder Signal to the Linux CNC.

Attached you can find some pictures and files of my config.
Thanks a lot and all the best wishes from Germany
JanCNC

active setup is faar miles in front of everything... it is very interesting stuff 

please reupdate repo /configs with scurve_example.hal and .ini files config for easy setup for other users as it was 1.1.2026 for testing ...