Schaublin 125-CNC retrofit.

I had a quick look at the config files in the first thread. However, I do think it would be good with the latest files, as well as the classicladder part.

In addition to what I mentioned in the last post, I would also say you should have a look at these signals when you issue an M3 command:
If the physical buttons are not connected to (only) LinuxCNC, then I guess it could very well be something on the hardware side as well. In that case some kind of schematic would also be needed for "remote" troubleshooting.

Thanks. I fixed it. I think it was a combination of sometimes doing M3 without an Sxx first on start up, then pressing the button (which defaults to S200) and then trying S100 M3 in the MDI.
Turns out I got the Analog 0-10V and GND wires reversed when I rewired the VFD.

The weird thing was with those wire reversed, it would not start the spindle below S175, but would only run the VFD at the max frequency with any S speed above that. So switch on, type M3 nothing, push button (= S200 worked but always at 70 Hz),  then I had been typing S100 M3, and it would not start. 

Switched the polarity, and now it is all back to normal.

I'll upload the latest HAL and Ini to the first posts a bit later, as it is good to have a back up here.

That is quite interesting behavior by the VFD. If you have a "single ended" output (say 0...10V -> 0...70Hz), you would think that with the wires reversed, it would go to minimum allowed frequency or just refuse to start.

Anyway, glad you got it working.

Yeah, that behaviour threw me.

Made a start on getting the Schaublin tool changer running. I will use Andy's carousel.comp to control it.


 

Nice video and good work! It's interesting to see the internals of the tool changer. And it will be interesting to see how it works once you have it all back together.

By the way, regarding the earlier video. Are you aware that you can use named parameters in g-code?
linuxcnc.org/docs/stable/html/gcode/over...ode:named-parameters
I think it improves readability quite much if you use variable names like #<partnum> instead of something like #50. Especially if you have many parameters, and might still need to understand the code the following day 

Good input, I have used names before, but had forgotten it.
Cheers,
Mark

I have now gotten the tool changer working mechanically and electrically tied in with LinuxCNC. 


Next step is to set up the carousel comp. Since my lathe is still running 2.8.2, and I never updated it, the version of Carausel.comp will still be the one with the bugs identified here...
www.forum.linuxcnc.org/10-advanced-confi...carousel-toolchanger

I see three options.
1/ patch the carousel I have and recompile it
2/ download the current carousel.comp from github and compile it.
3/ upgrade my full installation from 2.8.2 to 2.9.8, and then the current carousel will already be covered.

linuxcnc.org/docs/html/getting-started/updating-linuxcnc.html
I read the wiki that it is recommended to do a clean install, but I am hestitant to do that with a working system. Wish me luck.
Cheers,
Mark
 

So I checked and my lathe is running Lcnc 2.8.2 on Debian Buster, with RT 4.19.

Since Buster is still okay per the updating instructions, I thought Id try an update.

 
I added the repository.
 

but get errors

 

...

 

 I attached the full error log.
Does this mean Buster can no longer be updated?
Cheers,
Mark