Advanced Search

HOME_FINAL_VELOCITY = 10
For metric that would be 600mm/m
Set also SEARCH and LATCH values acordingly, in the ini file.

The SPI driver has nothing to do with Armbian, it's in the kernel, it seems to be a known issue with the default (example) driver. Unless their is a proper SPI driver for the rk3399 it won't be different on that sbc. AFAIK there's only made a realtime driver for the RPI.
Unfortunately I don't have a spi board to test with, perhaps it helps to pin the irq of spi to an isolated core?

I've seen that there has been a rt patch for one board for a quite old kernel, I can try to find that one and if I'm able to apply that on the newer kernel.

Hi,
Thanks for your feedback! Based on what I am seeing this appears as if its an issue with the G43 and G49 entries in the gcode.
Which is why I included a copy of my gcode in one of the posts in this thread. There are both G43 and G49 code changes in the qt_auto_probe_tool.ngc script.
I suspect that there may be some quirks that might be disabling/enabling these two codes.

Strange enough is the value of #5070 probe fail/succeed passes each time with a one(1) succeed.

I have not even tried(recently) to do a tool change in mid code(other than the initial beginning tool change) for fear of crashing, etc...

Its also worth noting that the post processor for Fusion 360, EMC2 in my case doesn't inhibit the call to G43 despite having the following two lines in my PP script:
outputToolLengthCompensation: false,
outputToolLengthOffset: false

To further complicate things, I've also noted that using tool number zero as my probe doesn't seem to work very well. I've moved my probe to tool number 99 as of now.

It would be nice to hear from some of the seniors as to their take on this issue.

1.
2. ....
I see PCW beat me to it.

Spindle.n.on
That should be the hal pin controlling the spindle (on phone can not check).
If using later versikn of LinuxCNC, the spindle on gcode is
M3 S24000 $0
S24000 is the RPM
$0 is spindle 0 of the first installed spindle as there can be several spindles.
One thing to keep in mind, if you set just the spindle on pin, it should just turn the spindle on, but if you do have a spindle pwm pin, then the spindle will not trun on from gcode without the speed value included.
! Means active low in 3d printers
Active low is whatever signal sign or name with the dash above.
What GUI are you using?

I can answer some of the hardware questions:

2: 600 PPR is fine (LinuxCNC is not counting the pulses, the 7I96S hardware is)
3: Yes Z is the 1 PPR signal (assuming the encoder is geared 1:1 with the spindle)
4. The 7I96S has 4 MPG encoders available on its isolated inputs so if you have enough
    free inputs for limit/home/probe/etc you should not need a 7I73 (each MPG uses 2 pins)

how should i attain the maximum possible rotational speed on my spindle?

my current settings are:
[SPINDLE_0]
SCALE = 6400
MAX_VELOCITY = 20000.0
MAX_ACCELERATION = 40000
STEPGEN_MAXVEL = 25000.00
STEPGEN_MAXACCEL = 40000
DIRSETUP = 10000
DIRHOLD = 10000
STEPLEN = 5000
STEPSPACE = 5000
STEP_SCALE = 6400

the spindle motor is set to 800 Pulses/rev

when i configure the motor as the axis, the fastest possible speed is apparently a bit higher than i can achieve when configured as a spindle

#*** AXIS_A *******************************
[AXIS_A]
MAX_VELOCITY = 971.590909090909
MAX_ACCELERATION = 36000.0
MIN_LIMIT = -99999999999999.0
MAX_LIMIT = 99999999999999.0

[JOINT_3]
TYPE = LINEAR
HOME = 0.0
MIN_LIMIT = -99999999999999.0
MAX_LIMIT = 99999999999999.0
MAX_VELOCITY = 971.590909090909
MAX_ACCELERATION = 36000.0
STEPGEN_MAXACCEL = 45000.0
SCALE = 17.77777777777778
FERROR = 1
MIN_FERROR = .25
HOME_OFFSET = 0.0
#******************************************

Thankyou in advance. looking forward

Thanks to all
Final working version attached including debounce mods suggested because I hate googling for a fix that ends 'thank you' but keeps the fix secret.
Quite what is different I'm not sure but it works before you home stuff which is what I wanted.
Now I can get on with making the Pendant actually move things rather than move and then jump back to the start position
but that would be another thread I guess.
 

Yes - with that encoder & index signal LCNC will adjust feed while threading to compensate for spindle speed variations.

Tutorial 21



JT

It’s a gear driven lathe and I just don’t want to deal with variable speed , and frying the motor controller etc . Already destroyed a mini lathe motor control board lol. I had made an encoder for the mini with two wheels and two optical sensors. One had like 60 slits and the other had 1 so I under stand that .

For me just turning the spindle on manual and hitting cycle start Is fine for the needs.

I wasn’t sure if I would be able todo threading and Linux CNC would just adjust the feed to compensate for the spindle load etc .

Running "sudo apt update && sudo apt install linuxcnc" gives an error.

I blacklisted the Ethernet port.

Debian has no internet connection.

BTW, the system is a dual boot of Ubuntu 24.04 (my preferred OS) and Debian (for LinuxCNC)

I also unplugged the front audio and USB ports that I do not use.

(The back of the PC has a plethora of ports)

However, now the BIOS complains every boot

Whatever, I'll just press f1 every time I boot up to clear the error.

I'm Japanese and I'm posting using Google Translate. Please forgive me if the text is difficult to read.

In the past, I consulted with LinuxCNC2.8.2 about the phenomenon where the HOME_OFFSET operation starts at full speed for a short time when the homing operation starts. The servo amplifier is torque controlled and uses PID control. The servo amplifier is connected to the servo amplifier using an analog output module via EtherCAT. At that time, I was only connecting the JOINT and Encoder Index-enable in the HAL file, but I was advised to connect it to the PID Index-enable, and the problem was solved.

This time, I am using LinuxCNC2.9,3 to create a machine with a similar configuration, and the homing operation starts at full speed for a short time when the HOME_OFFSET operation starts. In the HAL file, Index-enable is connected to JOINT, PID, and Endoder. And the PID module of this version of LinuxCNC has a pin like the AT-PID version used in between. And there is no AT-PID. I remember that Index-enable didn't work well with the previous version of AT-PID. At the time I thought it couldn't be helped since it was for servo adjustment. Is it possible to fix the behavior when entering this HOME-OFFSET? I've looked through various manuals, but I haven't found anything. Is there some information I don't know? Please let me know.

Thank you.

I managed to lower the latency to about 14000ns max jitter by disabling hardware.

I also set the CPU governor to performance.

I will try to disable more hardware to further reduce latency.

Unfortunately, I am unable to modify and BIOS settings because this is an old scrap computer from my high school.
I tried to get the IT person to change the password, but the BIOS login window is broken