Advanced Search

I managed to test it just now and every time I try to move an axis, a new warning like the one in the image appears.
 No engine moved...

I just looked at this file on my host and noted that it appeared to be edited in DOS (ouch):  /usr/bin/z_level_compensation

There was a ^M on every line ending.

Cure and fix if you have this problem:  sudo  perl -pi -e 's/\r//g' /usr/bin/z_level_compensation

Trying to get the router to run. I have tried everything there is in the config settings. The controller is Unity from Probotix and it says pin 14. Or I may be doing something wrong else where.
Spindle ON
Spindle PWM
Spindle CCW
Spindle CW
Spindle Brake
 

Thank you Don Bozarth! You saved me a lot of hassle I would undergo with velocity mode!!

Curious to hear if you got the turret working by now.

Best regards

The realtime command yes. But the calculated error is downstream of the command and is calculated using the Tx PDO returned by the drive. The round trip time is what the original question was about.

But, like I said LCNC is not closing the loop, that is isolated to the drive in ECAT under LCNC. Hence the document from Etherlabs telling you that position mode is all that is really supported although the v and t modes are available.

The error in LCNC is really just showing the comm delay and not real error. Which if you compare the actual in the drive to LCNC you would see that LCNC has exponentially larger error. Which based on the 2-3ms tick cycle that lcec is capable of managing. The doc is available at Etherlabs.

Actually I would expect the drive to be behind LinuxCNCs command.
This can be determined by the sign of the velocity and sign of the
following error.

PeterSi wrote:

Sadly not
To be honest I have no idea where to even look at this point.
For now I have gone back to manual tool changing which works without any problems.
But I really want to get the ATC working again since it worked perfectly fine with the old setup with the only drawback being that I had to manually change the pocket numbers when I changed out a tool in the ATC which wasn't very often since I had 24 pockets. But I assume that going back to an older Linuxcnc and probebasic version will be somewhat difficult as well since I don't know what exact version I was using.

 

Pommen makes a good point, this sounds like it could be your hal for the tool change type.  have a look and maybe try comparing the configs from the ATC sim hal?

I managed to recover a big cn lathe, I'm on cable and make the DC drivers work but impossible to make them work (I don't have any schematics and I don't know if they're still operational but the 2 don't work so the probability that it's me the problem is high). has anyone been confronted with NUM GEC MK2S drivers?

when retrofitting i took care not to disconnect the control cables (motor, tachy, enable, etc...) after wiring with my 7i97 board, i try to enable the axes but no noise and no movement possible.

diagrams below:



the enable contactor I drive with driver enable because on the old cn it was the only output coming from the drivers so I assume it's the enable.


if unfortunately I can't get the drivers to work, can I replace my current drivers with these?

old driver - NUM GEC MK2S S.57.27.001.B 24V3800-20 Variateur 27A

www.cnc-shopping.com/num-gec-mk2s-s-57-2...0283649b-p-3233.html

new driver - Sprint 3200i 32A 1Q 230V/400V AC to DC Isolated Signals


 

I have 2 CNC lathes with linuxcnc AXIS.
One of them does not display the loaded tool at the bottom of the screen and does not load the offset in the tool table.
So every time i use the lathe i have to set each tool offset again.
regards Wilfried

That would be the combined lag for all users of that stream of data. Yes. But this does not actually matter.

LCNC is just 73ms behind the truth. But the truth is still happening at the part. Kinda like a time continuum. But the accuracy is not impacted because LCNC is not closing the loop. The drive is. LCNC is just a postman and a UI that also happens to pass out positions on an EtherCat stream.

Unless your round parts are not so round after all, there should be no real concern at all. The time it takes to make a round trip is not effecting the accuracy or overall outcome. The position displayed on the DRO will match the position that is in the drive. The error is only a concern of the actual loop controller which in this case is the drive. If it is within a desired tolerance on the drive then it is good.

Hope that helps.

I'm curious whether you got any further with the machine?

I was reading your posts, and can relate extensively. Every time I come to use mine it is some new problem

Mine had a blown spindle drive when I got it. It's Z axis was also retrofitted at some point in the past. That blew up during the time I owned it and had to be rebuilt with new IGBTs.

Last (recent) was a failed TNC355. I "think" I repaired it on the bench ok (it was a failed RAM chip), but when I reinstalled it to the machine I couldn't get past the interlock chain

I hope you actually got to make some chips with the machine... I think you can set the gear train manually if the DC motors aren't working. The PLC in the Heidenhain control might throw you error codes if it doesn't see the feedback it wants for the active gear though.

nsk is now with jaeger as one company btw.

The appropriate size ATC spindles form them cost $15000+. So a non starter even if I could legally use them on this machine (which I'm not sure of).

My ATC spindle is 1.5kw @ 60000rpm for reference and is only about $1000. The entire machine loaded with goodies will be in the $20k usd area. Walking that line between cheap, good, and FAST. haha.

Sorry to necro post, but I have this same machine. I'm based in St. Neots near Cambridge. (Machine is in a shed in Lincolnshire though).

Feel free to contact me if you wanted to chat about the machine. Did you get it working ok?

Mine is still running Heidenhain TNC355 (assuming my recent control repair gets it going again!)

I have 2 nakanishi electric spindles for my micro mill, 3000 series. does 60-80k rpm. you might want the 4000 series thought. they have their own NSK driver to handle the speed