Advanced Search

Hello all,

I have my milling machine running and following commands well. However, with a small endmill operating in tight quarters, I have some issues with the tool not following the toolpath exactly, I think there is some overtravel. I did the PID tuning months ago and was able to fine tune it after the machine is safely bolted down.

I rewatched some of RotarySMPs videos on the Schaublin conversion and he mentioned that the analog output voltage has to accurately reflect the speed resolution on the motor. Otherwise the initial voltage signal is not correct and the control has to compensate.

It just occured to me that I never adressed that. I have Linuxcnc configured to limit my travel speed to 5000 mm/min. However, the maximum speed the machine could run from the factory is triple that at 15000mm/min.
So this means the Servos only ever run at up to 1/3 of their full speed.

The way I understand it, when I command a rapid move, the Mesacard wants to give it the full 10V, leading to a really rapid move on the motor, way to fast for what linuxcnc anticipated, and that will cause some issues.

Can I change this in my Hal oder Ini files? I think there is a line with maximum output??
I can´t easily change the parameters in my drives, so I prefer changing this in the config.

No worries at all, it has just become increasingly bad info all over the web, so at least here trying to keep info correct.

Just checked some 15 of my old and new configs, luckily i found one where search is positive and latch is negative (on Z), all others are same direction.

2000N i should have just let you convert it sorry i was going off of memory and should have added the extra 0 thanks for the catch on that.

Excellent to see stuff moving!
The torch voltage seems low but that is just a calibration issue.

Is there a reason why you are not using the qtplasmac config? 
linuxcnc.org/docs/stable/html/plasma/qtplasmac.html
Or did this project start so long ago it didn't exist?

Thank you so much! I figured it out with your comment.

It turns out that for whatever reason, when I set up my .ini file, I had commented out the .var file. I just uncommented it and now everything appears to be working normally. The offsets table is updating as I expect when changing work offset locations.

The littlest issues can be so frustrating when you don't know where to look, yet so easy to fix once you realize how the system works. Thank you again!