Advanced Search

Cool, that looks painless.Please confirm it works when you test it.

With 6.12 PREEMPT_RT is not enabled by default. It needs to be built. You still need to run menuconfig (which should open in our system unless defconfig is enabled) and under general settings, you still need to select "Fully preemptible Kernel". Sometimes this option is hidden until you enable expert mode in another menu (still under general)

 

   

i was thinking Pneumatic clamping of some sort that could be controlled by Linux CNC. i was wondering if something simple like regulating air pressure between two independently could be a simple solution for calibration of the center line ?

just some more progress on the Z axis

A couple of photos of Joey's setup.
He's running Qtplasmac. The rotary is attached to the gantry. I think he must use another unpowered chuck to hold the other end.
you can see his table is not exactly a hobby one

I am using master on Bookworm in a RIP setup. I am trying to compile and install a custom kinematics module but it seems that things has changed a lot since I last tried this.
halcompile will not compile and install the .c file so I tried the only other method that I can find in the documentation.

I did this:
The output form the compile :-I see it linking all kinds of other modules but not my module. I cannot find output of my module anywhere.
It would seem that I cannot compile and install my own custom file.
What am I doing wrong or don't I understand the process?
 

Just created a Pull Request for the change required. So hopefully that can be ticked off the list.

also add the Longworth chuck to your list
www.carbatec.com.au/article/266/how-to-make-a-longworth-chuck
Not sure if it does square and rectangles

Thanks for chiming in mate. Hope this year is a better one for you.

This appears to be the config.txt file is created using the config_dot_text function

I'm thinking the following maybe all that is required.

Line 137 of rpi-img-builder-lcnc/lib/function/staging
changeto
Just created a PR

Sorry if I'm a bit vague it's been a while since I've looked at the code.

I haven't kept up to date with RT Kernel, as I've been working on other stuff.
I know there was talk about the mainline kernel including the RT code, but it seemed that the std config wasn't for the RT kernel we need, one of the less "aggressive" types. Would have to have a look into it.

Is there any "special sauce" regarding the fixes for the video issues ? I think you said another user created the image that has the 'fixes" to change video resolution...... That was the most recent one you had on your google drive.
One thing I did notice is that when coming back after the screen saver had activated the window to change resolution pops up. I'll power up the 5 tomorrow and have a closer look and report back with a more concise description.

Hi,

just to make sure I understood that correctly.
I have a 7i96s and want to connect a laser module which uses a TTL signal to control it. When I connect it like shown below, the M67 command will control the intensity, right? Or do I need to configure something to make that work?

Thanks!

 

 

If your interest is in kernels and the pi 5, the Linuxcnc builder (for the Pi 5 and 4b)
github.com/LinuxCNC/rpi-img-builder-lcnc
Is a fork of my repo
github.com/rodw-au/rpi-img-builder-lcnc/tree/linuxcnc-2.9.3
Which in turn is a fork of
github.com/pyavitz/rpi-img-builder
with Linuxcnc and the PREEMPT_RT kernel installed

Note the builder cross compiles on a normal PC and builds the official Pi kernel, then wraps Debian around it before installing Linuxcnc and a few other goodies in this script github.com/rodw-au/rpi-img-builder-lcnc/....3/files/userscripts

I got as far as merging the latest upstream code into my  master over Christmas but have not pushed it to my 2.9.3 branch as the default kernel has rolled forward from 6.1 used by Debian Bookwoem to 6.6
It's quite a business finding a Pi kernel commit that agrees with the PREEMPT_RT patch kernel version. 
The latest upstream source now supports the 6.12 kernel so it would be good to build for it as there is no need to patch the kernel anymore
ref: github.com/rodw-au/rpi-img-builder-lcnc/.../patches/userpatches
(but you still need to set the fully preemptible kernel in  menuconfig)
Cornholio has asked in another thread for changes to config.txt to support spi so there is a nice kernel related project here.
 

So I picked up a self-centering 4 jaw chuck. it's not very big but will hold 4 inch square tubing from the inside. i was looking at several ways to make a steady rest for longer tube but the draw back is you have to have around a 6" bore to pass 4" square tube through. bearings beyond 90mm ID's are very expensive. i might have found a work around but i have to test a small design and scale it up if it works. A steady rest for round tube is pretty easy but the square tube gets a lot more involved unfortunately. it would be nice if a cheap self-centering programable clamping system could be don cheaply but that solution is yet to be found
i have an idea for that too but until you build and test it out all it is an idea but if that would work the little chuck would get phased out  

 

Nicht ganz.
Du musst gucken was wo wie verknüpft ist und gebraucht wird.
Beispiel:
handrad.hal:  net maschine.ist-an halui.machine.is-on whb.halui.machine.is-on
gui.hal:  net machine-is-on halui.machine.is-on qtpyvcp.machine.leds.is-on

Wie du siehst wird sowohl für's Handrad als auch eine GUI das "halui.machine.is-on" benötigt.
Daraus muss man dann was einheitliches machen, da zwei Netze genutzt werden. Was aber nicht geht.
Du hast einen "Sender" "halui.machine.is-on", das Signal davon soll an zwei "Empfänger", "whb.halui.machine.is-on" und "qtpyvcp.machine.leds.is-on". Du kannst nur ein Netz und nur einen "Sender" miteinander verknüpfen: "net maschine.is-on halui.machine.is-on", den Namen des Netzes kannst du dabei recht frei selber wählen.
Für die beiden "Empfänger" gilt also:
net maschine.is-on whb.halui.machine.is-on
net maschine.is-on qtpyvcp.machine.leds.is-on
Oder alles zusammen: net maschine.is-on halui.machine.is-on whb.halui.machine.is-on qtpyvcp.machine.leds.is-on
Denn an ein Netz kannst du beliebig viele "Empfänger" verknüpfen.

Du musst also entscheiden, ob das noch gebraucht wird oder nicht.
Ein einfaches "net maschine.is-on halui.machine.is-on" und "maschine.is-on" wird nirgendwo mehr benutzt, kann dann weg.

www.linuxcnc.org/iso/ubuntu-10.04-linuxcnc3-i386.iso

To configure my machine, I've already created several user defined commands. I've always followed the examples in the documentation, where there's always the line “exit 0” at the end.

Today I wanted to set up a custom M code that runs Zenity to display information to the user and wait for him to click on OK. I then wondered how LinuxCNC would behave if the exit code was not equal to zero.
I searched the documentation but found no mention of this apart from the “exit 0” in the examples. So I did a few tests: in Gmoccapy, a macro that uses a custom M code with “exit 1” seems to cancel the execution of the macro. This suits me because I could use Zenity to ask whether or not the probe is correctly positioned. Clicking on “no” cancels the probe macro.

It's a pity that exit codes are not documented.
Is my way of doing things correct?
Will the documentation of user defined commands be completed?

yes thank you for your help my question was stupid. I have two servo drive systems one that I kept from the original Deckel and the other a new generation leadshine both driven in analog. they are operational when powered up which a priori will have to change. they must be requested by linuxcnc t so my hal file must be modified which will be done initially I will come back to you after the result. in the meantime thank you for your help

BSOD wrote:

Please share your config, HAL and ini. (can't find them, if you did earlier.)

For the HAL and INI files, I’m using the default LinuxCNC/remora-rt1052-basic configuration. I haven’t made any changes or tweaks to it.

For the config file uploaded to the NVEM V5 board, I used LinuxCNC/nvem-rt1052.txt .

Let me know if you need any more details!