Remora - Rpi Software Stepping Using External Microcontroller via SPI

well, maybe you dont need to use the preassigned index, you will find out i guess

i dont think you are connecting your spindle pins correctly thought. its waiting for the index enable probably
compare to this one
github.com/cakeslob/RRW_LAB/blob/inc/Lin.../remora-xyz.hal#L128

cakeslob wrote:

{
"Thread": "Servo",
"Type": "Digital Pin",
"Comment": "Index",
"Pin": "1.28",
"Mode": "Input",
"Invert": "True",
"Data Bit": 6
},
{
"Thread": "Servo",
"Type": "QEI",
"Comment": "spindle-encoder",
"Modifier": "Pull Up",
"PV[i]": 0,
"Data Bit": 2,
"Enable Index": "True"
},
well, maybe you dont need to use the preassigned index, you will find out i guess

[code]# Spindle QEI encoder

setp encoder.0.position-scale 800.000000
net encoder-count <= remora.PV.0 => encoder.0.raw_count
net encoder-phaseZ <= remora.input.6 => encoder.0.phase-Z
# setp encoder.0.index-enable true

i dont think you are connecting your spindle pins correctly thought. its waiting for the index enable probably
compare to this one
https://github.com/cakeslob/RRW_LAB/blob/inc/LinuxCNC/ConfigSamples/remora-RRW_LAB_latheng/remora-xyz.hal#L128

[/i][/code]
 

Awesome, yeah my hal was a mess. I ended up just grabbing that example and tweaking what I need to to have things make sense for my machine and I'm happy to say, everything is working now. Exactly how it should, and we have threads! Thanks again!


https://imgur.com/a/dP7VYhM

Hello! My team and I have been setting up a cnc using a raspberry pi 5 running remora to an octopus pro with spi, this then uses 4 Ext motor v1.1 to generate the steps using stepgen in the octopus config to generate movement with some DM556 drivers these are wired directly to the steppers. We have been having issues, when we boot LinuxCNC an error appears, raspberry pi 5 using rp1 driver. We belive this to be a warning to tell show that the rasp5 got recognized.

We haven't been able to enable the stepper drivers, the e-stop is working. We can enable but the moment we try to jog we get a joint following error this, caused by  the drivers not getting enabled and not getting any movement. 

Any ideas on what we could do?

Hi, it may be helpful to share your config.txt, hal and ini files so that we may see your setup.

The following error is generated internally, not by the driver not being enabled. Hence maybe a config issue.

      True, let me post the files. 

 

Hi Gusugs,

Thanks for sharing your setup. In your ini file your accelerations are extremely high, way higher than I use in 3D printing.

Also, your FERROR of 0.025 and MIN_FERROR of 0.25 are the most likely causes. These are way way to small. You need enough allowable following error for the control loop to do it's thing.

Have a look at some of the example configs to get a feel for what is needed.

github.com/scottalford75/Remora/tree/mai...nuxCNC/ConfigSamples

We have used this settings before, and the machine worked fantastic, the only change we've made is the change from raspberry pi 3 to 5 and the Remora version change. Well attempt config changes. Thankyou Scotta!

forgot to add, we don't use this for 3d printing but as a router, it has the dm556s connected to NEMA 23 motors.

Hi again and thanks for all the help up until now!

I wan't to give more context and explain myself better, we have been using this cnc router since 2023, originally setup with a raspberry pi 3b and octopus pro combo, it has worked wonders and is amazing the only real issue is that the raspberry pi 3b was slow. Recently we made the change to a raspberry pi 5, we took the original .ini and .hal files which we then update to be compatible with the new remora version, we kept the same config.txt file. We installed the linuxcnc-raspberrypi5 image and installed the remora components as instructed in the documentation.

The issues we've seen: when we first loaded linuxcnc and ran the .ini file by double clicking on it and choosing linuxcnc as the app to run the ini file we then saw the raspberry pi 5 using rp1 driver alert, we initially thought this was error but figured this was just an alert and so continued. We then started testing leaving e stop we could but just for a moment, no more than 3s, we could even get to enable but non of the drivers actually enable. We then tested if this was the E-stop's fault but we assumed it wasn't since if we disconnected the estop we could exit estop at all, wehn it was properly setup we could but can't enable the steppers fisically. This isn't a stepper issue or driver issue since they get enabled with the raspberry pi 3.

Thanks in advance and thank you for all of the help until now! Oh and sorry for any grammar or spelling mistakes, english isn't our first tounge.