Advanced Search

To be honest, it doesn't really matter where Z home is. You can't rely on limits to avoid mashing the tool into the chuck anyway. (consider long boring bars....)
However, if you fitted a hard-stop for the tailstock, perhaps that would help with repeatability on occasions when you leave work in the machine with it powered down.

Maybe:
"If this message annoys you, add --nocheck to the loadrt hal_parport line"

TMC2209 Drivers with jumpers in SPI mode

try doing it without the drivers configured in SPI, but they should also probably be configured with UART instead if they are 2209. The Remora Octopus firmware doesnt support SPI drivers anyway. If you are planning to use TMC2209 drivers, they need to be configured in the config.txt file.

how long is the cable that connects the octopus to the rpi? Also what RPi? I dont think you need to have SPI enabled in the RPi software either. Your serial output looks perfect though, but you will need to configure the TMC drives.

It's in a library file. qt_action.py

github.com/LinuxCNC/linuxcnc/blob/2.9/li...cp/qt_action.py#L754

Does this help?
linuxcnc.org/docs/devel/html/gui/qtvcp.h...qtvcp:designer-slots

Yes, the missing power supply was the issue. I was being too careful in my attempt not to blow up the Heidehain cards, but now it works.

I have hooked up all three encoders and for the first time I can see some movement in the LinuxCNC UI.

Thanks for your help again.

Hi .
I have the same problem , with message Slave did not sync after 5000 ms.

With the same hardware , with debian 10 and ethercat 1.5.2 and lcnc 2.9.0-pre run ok , without problem.

Because with Debian 12 and Ethercat 1.6 stable and 2.10.0 , on the same hardware, have problem ?

I have install Corbett procedure, step-by step . Some step not is ok ?

Hi,
I have a configuration where X axis is the drill axis. 
When I run 
G19 
G0 X0.35 
G81 X-0.35 R0.1 F1 

it is accepted and runs but in reverse direction than what is needed.  
G19 
G0 X-0.35 
G81 X0.35 R-0.1 F1
It throws an error that r cannot be less than X.  In my case R-0.1 is above workpiece and x-0.35 is the start of drill, X0.35 is the end.  
Is this not supported or am I missing something. 
Best,
Rick

 

Wasn't expect that:/ Any practical use for ENCODER_RATIO then? I believe this is the point related to is in documentation:
"
encoder-ratio.sample

Read all input pins. Must be called at twice the maximum desired count rate."

Why can't we use encoder.0.position? Or it is just the way this component is coded? Anyway why would it be a problem? Is it because of the encoder-ratio.sample call frequency required?

ZIP download was ok. Trying to wrap my head around it.