Advanced Search

Rod I mentioned it via email what needs to be done.

This is an excerpt from the patch for arch/Kconfig
Without this small edit, you don't get all 4 selections when you select which preempt model you need.

@fully_defined
Deleted the twin thread. Having multiple threads about the same topic will invariably cause confusion.
If you want to make the results of the discussion more visible you can edit the first post.

Thanks

The patch adds this function:

The best thing would be for LinuxCNC to remove its dependency on /sys/kernel/realtime and check some other way. That's the only thing keeping LinuxCNC from at least starting up on an unmodified 6.12 kernel (caveat: I haven't cut anything with it yet).

That is the problem. I now notice my designer works because I too have an installed version of linuxcnc. I'll fix this soon.

The tool changer system doesn't matter. I have several lathes with different tool change systems. They all work fine. But for a lathe I don't want to use the command T1M6G43H1, but only T1. Machines with Ladder ATC can do it.More complex machines, such as Sauter, it is better to make a carousel component. And here it does not work like that.

Or just incorporate their better planner into linuxcnc, if someone does have the source.
The planner would be GPL. We have no interest in stealing their product, just some of the underlying code. In fact the updated planner we have came from them.

Tommy,

Maybe you were good luck, but I got it working.  It may have been a syntax error.  Or maybe I didnt make the python file executable.  But what matters is that the feedrate will reverse now.  Thank god. I can even control it with the arduino.  Tomorrow I will do a test cut. 

Best,
-Dylan

For AMD64, these instructions apply
To get PREEMPT_RT at compile time, we need to enable "Fully Preemptible Kernel (Real-Time)" in the "Preemption Model" menu (of "General Setup", in make menuconfig), but "Fully Preemptible" is not an option visible by default, for that we need to enable the "Configure standard kernel features (expert users) (NEW)" option of "General Setup".

So its a bit different in the pi

I think the issue might be there is copyright on the GUI so it would not be wise to share it. The ethical solution is to buy their source code. Or use one of our GUI's. QTdragon is a pretty good substitute these days.

Great work! thanks fo finding that thread for me
@cornholio, I think some of the enabling settings in menuconfig are ARM specific but they were there before 6.12 arrived.

We should be able to apply the required changes without a patch by changing the defconfig.
github.com/rodw-au/rpi-img-builder-lcnc/...onfig_defconfig#L112
That is probably cleaner
Can somebody let me know exactly what should be put in this file? (eg what is the result of the patch?0

Hi, BigJohnT,

Thank you for the information about axis modification.

I have a question regarding 'Changing the size of the file open dialog.' I followed the instructions and successfully resized it.

However, is it possible to also change the size of the 'Open' and 'Cancel' buttons? How can I adjust their size?

Cant do this anymore bye all wrote:

As far as I have been able to see there has been no major hardware updates to the RPi5. Or are you referring to the ability to boot from NVME ?
 

I think there has been a lot of improvement under the hood including making the 6.12 kernel available.But yeh, not something you can really see.

log:

libnml/cms/tcp_srv.cc 694: received_serial_number (1212501068) does not equal expected serial number.(0)
(time=1736393516.203628,pid=13259): TCPSVR request received: fd = 6, serial_number=1212501069, request_type=1327514957, buffer_number=1124928083
libnml/cms/tcp_srv.cc 1501: Unrecognized request type received.(1327514957)
 

Hi PCW,

Thanks for your reply, I was told they were working when I bought the machine but haven't been in a position to start fault finding yet or check that this is true. (The guy I bought it from didn't know what the problem actually was though, so everything needs to be checked).

I'll report back after a month or two and I'll look into those boards you mentioned.

Thanks again for replying and any other help you can think of

Pat

The first P1 encoder is  encoder 1 so the position would be:

hm2_7i96s.0.encoder.01.position

and the most important parameter for that encoder would be:

hm2_7i96s.0.encoder.01.scale