Advanced Search

royka wrote:

Check with "ls -l /boot" if all links are correct. With Armbian for example the Image file is a link to the used kernel. To relink you can use "sudo ln -sf your-rt-kernel Image" and also check for the uinitrd link and to use the right dtb for that kernel version.

I saw that it's a rk3399 indeed, but here it also worked great for a s912 sbc so it might be a good base for yours too.

 

while a go you've provided a rt kernel for my orange pi 5 plus. can u do the same for this one (orange pi 4 lts) ? i mean a real-time 5.10.43 kernel for rk3399?

Thanks Scott, it's a spindle encoder I'm trying to get working. Its just the first step to get the PV1 counting in Halshow so I know at least the hardware is working. I'll look at my wiring again. Config setup for the encoders. No not using the MPG , just needed to rule out I didn't need that .so installed for the encoders to work. I have everything else working the lathe with this controller, axis ,spindle and tool changer 

royka post=314868 userid=31446Check with "ls -l /boot" if all links are correct. With Armbian for example the Image file is a link to the used kernel. To relink you can use "sudo ln -sf your-rt-kernel Image" and also check for the uinitrd link and to use the right dtb for that kernel version.

I saw that it's a rk3399 indeed, but here it also worked great for a s912 sbc so it might be a good base for yours too.

 

Thanks, I've tried to relink the files in boot directory to my new kernel files, still same problem.
In the source that I compiled from, I noticed that there is no dts and dtsi files and other related files for rk3399 in that source. can it be the problem for not booting after compilation?
if it can be, how can I solve this problem?
is there any other source besides kernel.org?

I tried another thing too, I used another sources like rockchip and orangepi-build. but whenever I wanna patch the real-time patch (got from kernel.org), it fails and says there are conflicts and incompatibility/

Exactly what I was looking for.

Thank you

Hi Forum,

I am trying to get Classic Ladder working with ]LinuxCNC RIO.

I try to get my VFD working with Classic Ladder. This is what works on the same machine with soft stepping.

loadrt classicladder_rt numS32out=100
addf classicladder.0.refresh servo-thread
loadusr classicladder --modmaster vfd.clp

When I start LinuxCNC with the FPGA connected I get the following error:Shared memory conflict or RT component not loaded!

ERROR CLASSICLADDER-   Ladder memory allocation error

I tried to remove the numS32out=100, but no success. I can load the program manually with the ladder editor, but it is still not in modmaster mode and won't work.

Someone an idea what the cause would be and how to fix it?

Hello Tommy 
I am using the following hardware.
qty 1   7I92M ethernet Anything I/O
qty 1    7I77D daughter card
qty 1    Lenovo think center M715q
I am re using the MSI servo drives, SEM servo motors and Heidenhain encoders, I plan on adding a A axis later.

Regards
John

Not sure If I bring anything but :
once you start machine and load tool z offset is present ?
I have problem with G43 on the first time after starting machine. Even my macro for tool change issue G43 after program is executed z offset disappears. Once I manually issue G43 everything is working than fine.

I have no idea how I can track what is causing this problem
my workflow :

Start machine
home all XYZ
load Probe (M6 T99) , during subprog execution z offset is visible for split of the second and than disappears)
G43 manually from MDI - offset now visible 
Probing part and zero G54
M6 T1 -all offsets are correct, if I don't issue manually G43 all the offsets with all the tools are messed up later on.