Advanced Search

Seems to be very similar to a lathe.
When the a axis gets an encoder and the x axis is "slaved" to this.
Pitch should be adjustable.

Leaves the back and forth movement to be taken care of.

Is it a dedicated winding machine? Or you need to solve it just with G-code for a standard x-y-z a Machine?
Greetings Timo

Hello All, I am at a beginner level in linuxcnc and cnc programming.

I have to build a simple winding machine, as depicted in the attached image. (I wish to perform side by side winding of the mateial without any gaps or overlaps)

the X axis is supposed to control the layup slide back and forth.
the A axis is supposed to rotate at a constant speed in the same direction until multiple layers are wound.

here is a simple working example of the gcode i prepared.
g91
o100 repeat [5]
g1 x80 a3600 f360
g1 a720 f10000
g1 x-80 a3600 f360
g1 a720 f10000
o100 endrepeat
m2

*please note that this is just a representative code, which performs the desired motion for me.*
however, since the feedrate is calucated in a compound manner, giving priority to the x-axis, adjusting the rotational speed so as to have a side-by-side layup of material is difficult.

secondly, since the A axis isnt rotating conitnously, it generates a momentary pause (due to deaccelartion and re-accelartion when a line of code ends)

Q: I am looking to eliminate both of these problems, but i dont know how to make it possible in the gcode.
I wish that A axis would keep rotating indefinietly without any pause at a given certain feed rate. and the X axis to keep moving back and forth independently at a different given feedrate.

i can use a spindle setting instead of A axis, the example gcode for it looks something like this:
s100 m3
o100 repeat [5]
g91 g0 x80 f360
g91 g0 x-80 f360
o100 endrepeat
m2

However, i wish to know if this is possible to with X and A axis, what would the gcode look like.

Any help is much appreciated.

royka wrote:

At least for the rk3588 the dtb version must match with the kernel version so I assume it's the same with yours. In this case it might be easier to create an image with the Armbian build system, just put the rt patch in the right folder, for example patch/kernel/archive/rockchip64-6.9 and start with ./compile and choose that you want to see the kernel config before you'll compile it.

Although they only support Linux 6.6, 6.9 and 6.12 (which don't need a rt patch). But if for some reason you need an older kernel you could just find an image with the same version kernel you've compiled and copy that dtb.

I'm using those kernels just because the official links of orangepi provided them, If any rt-kernel can be installed, that would be great.
when I was using orange pi 5 plus, I used armbian 5.10.160. but I experienced a tough time with its SPI driver. after spending some time on that I thought it may be the armbian which its spi is not real-time and reliable.
That's why this time I was avoiding to installing armbian.
if you think armbian is reliable in SPI, then this time i will try this way.

Here are some more detailed photos.I've also just shared the 3D files of some elements on Thingiverse .

Photos :

Is there a reason that you need specific that kernel version?

At least for the rk3588 the dtb version must match with the kernel version so I assume it's the same with yours. In this case it might be easier to create an image with the Armbian build system, just put the rt patch in the right folder, for example patch/kernel/archive/rockchip64-6.9 and start with ./compile and choose that you want to see the kernel config before you'll compile it.

Although they only support Linux 6.6, 6.9 and 6.12 (which don't need a rt patch). But if for some reason you need an older kernel you could just find an image with the same version kernel you've compiled and copy that dtb.

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/