Advanced Search

This machine has a Contour 3 controller.
At first i want to move all axis. Then the spindle and at last the toolchanger.
I want to keep the old simens servos with the bosch servocontrolls. I also want to keep the linear Heidenhein encorder. They are still in a good shape and still work. 

A list of all the components on the machine i want to keep to move the table:

Heidenhein LS904
 
Bosch tr15-xa-140-230V
Simens 1HU3071-0AC01-Z
 

Well i guess I should ask is the program prefix (~/home/cnc/linuxcnc/nc_files) a valid path too.

ok.
I see there two entries for:
PROGRAM_PREFIX = /home/cnc/linuxcnc/nc_files

should only be one entry and they are both wrong. should be:
PROGRAM_PREFIX = ~/home/cnc/linuxcnc/nc_files

I don't think this is the problem bit please fix it anyways,
Then can you run linuxcnc from a terminal, do a MDI tool change and post the terminal output.

Hello!
I currently bought a used Deckel FP4ATC. Now the want to retrofit it. I am going to document my journy and hopefully is going to be successful. It would be nice if someone could help me a bit. Thank you!
 

I started working on the layout of the new control cabinet using plain old cardboard, which actually works surprisingly well.

Given the space constraints, I currently think it makes sense to place the components related to the three axes on one of the side walls, and put the remaining components on the back wall. I’m not done with the puzzle yet, but it’s starting to come together.

I’d be interested in any feedback or suggestions you might have.

If a 1A fuse blows with no encoders connected and analog outputs open (or at least not shorted).
the 7I97T is damaged...

I don't use cia402 homing so someone else has to come with advice on that.
If you just want something that works you can use standard linuxcnc homing.
linuxcnc.org/docs/html/config/ini-homing.html

You can always revisit cia402 homing later on.
 

Hello,

I have now checked my entire configuration again.
I have also tried different homing methods.
Unfortunately, the error persists.
After homing is complete, the axes jump back and the servo shows Er87.1.
The axis is then referenced.
The error occurs on all axes.

Does anyone have any advice?

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