Advanced Search

hello, I am a new user of linuxcnc, I am creating my first milling machine, in the process I encounter many problems that I am trying to solve.
I can not solve the last problem - after installing probe screeeb 2.9 I can not run the G-code program,

Can anyone help me in setting up remora on btt skr3 board. I have posted my config files on previous posts. 
Now can I can make LinuxCNC to come out of estop. But stepper don't move, not even slightly. Don't feel like stepper is energized. Getting joint following error. LinuxCNC display dev/ttyAMA10 device, I connected through minicom but can't get any output on screen. 
PS. I am not new to remora, earlier I was using on Octopus pro board, now when newer Remora supported TMC5160 on skr3, so I changed the board.

I had a joint following error as well but, it was because my default jog speed was set too high for my set up. Not sure if this is happening to you but, thought I would mention it.

I posted something I thought might be helpful since it seemed to fix my problem but, then it started happening again.  My SPI interface keeps getting reset as well and only when my spindle gets turned on.  I already created a shielded cable between the SPI connections. I thought messing with the base servo speed helped in the ini file at one point but, I just tried again and got the same microcontroller reset.  After that I have to reset the microcontroller before I get a good status signal for the SPI connection and I can toggle machine power once again and communications work as well.  I guess it could be interference on the SPI interface still but, I'm not sure how that is happening. EDIT:  I guess after creating a shielded SPI cable it did work for longer before getting an SPI reset.  I still had issues and I just put a piece of tin foil over no directly onto the raspberry pi4 GPIO pins and it looks like all of my errors are gone so maybe some EMI was getting into the raspberry pi pins and resetting the controller somehow?  I'm still testing to see if my problem is gone for good but, fingers crossed.

I'm happy to say, I was just being dumb and -5  was lowest number in my head except it was negative so it was obviously the highest number.  I also spent a bit of time playing with spreadsheets and the raw RTL file and it was easy make a mistake shuffling data.

So, I wrote a python script to handle the process. (I haven't tested it with an axis going in the positive direction, it should work.) 
  Renishaw_Laser10_with_LinuxCNC

I really hope it helps someone someday.  I've attached my results before and after.

OK it should be possible to debug this step by step:

First what FPGA card and what firmware is being used?

I not remember tuning software on lichuan servo, stepper have utility to connect driver and change parameter - only on chinese

Has anyone been able to connect the drives to their tuning software. Maybe its because im on windows 11.

Ok, hope I understood correctly- I disconnected the X-encoder, set the jumper W4 DOWN to TTL and shorted the pins ENCX0 and GND of the X-encoder.
The status in HAL-Show for the hm2_7i80.0.encoder.00.input-index for X did not change, stayed high (yellow).
(I have set the jumper W4 back to UP before reconnecting the X-encoder)

Interesting, does that work reliably?
What do you do, disable EoE mailbox support and also disable EoE?
Wonder why there is a difference between 1.5 and 1.6, EoE seems to be supported also in 1.5.
 

Thanks Andypugh! Its calming to hear you have done something like this already and is doable using LinuxCNC. I will try to learn and act on next steps.
I have not worked on the 3D model of the machine yet. Would be trying to do it next.
Edit: Its a continuous generating gear grinding machine, threaded griding wheel mimics the geometry of a fear hob.
Also, do you make helical gears?

Thanks for the guidance.

Glad you got it resolved

Yeah debounce looks for a input over a time period before acting. Just be sure to recalibrate after you find the setting that solves your issue

Try the docs for job settings, there was an update on it. It's fully explained in the docs page configuration in ini file instructions

It just starts on the status page, is not an error, just informational.