Advanced Search

Yes.

That was it! I tried 8" for max travel instead of my 16" and it probed down......I should have done that last night, but it was time to stop for the evening. So, I added 60 thousandths to my previous measurement, as you mentioned, and it measured and inputed the tool length.

Thanks for the link....that is what I was already following, along with the directions on the various PB screens.

I also saw info on the various offsets in your directions, so that should answer one of my previous questions in this thread. I'll make my way through all the directions on your page and I need to check out your videos to see what else I can learn.

Hi Friends, 

The goal is a tangential knife setup with a pizza type cutter blade. To achieve this i have a servo driving a pulley that drives an output shaft with the  blade on it. my goal right now is to get it to jog without errors. 

In Axis, when i jog the A axis its slow and jittery. I increased the speed to about 500 deg/min and it moves faster but just as jittery. Anything over 600 i get a following error, I also get random following errors throughout normal jogging. I checked all the connections and they seem fine. Which leaves makes me think it might be the servo tuning. 

I tried to follow this guide to tune it (gnipsel.com/linuxcnc-old/tuning/servo.html) however, i cannot find the signal in hal scope. The tutorial calls out 'axis.x.f-error' i can only find 'joint.x.f-error' and get no change when i trigger it with a movement. what is the difference between these two and am I on the right track?

Any advice is greatly appreciated. 






 

LinuxCNC will only come out of eStop when the SPI comms works, ie the remora-spi component receives a valid response from the board.

This is where using the serial output from the board is handy to ensure the board boots all the way to idle state where it will wait for SPI commands.

OK  thinking about this, it's probably just a difference between a RIP installation and
a binary installation, where the normal user does not have write access to LinuxCNC's
system files.

Still does not explain the issue, and why it works as expected using  2.9.4 built from source.
Maybe a problem with the binary image.