Advanced Search

I am currently working on a machine with two X axes 1500x3000mm, what should I do so that with the incremental encoder it can align the bridge if it moves a little in reset mode.
mesa 7i95t
Greetings

  Good afternoon, I think I managed to do what you asked me, but without results, still with the same error. Could it be my pyocd installation? I've tried with other versions of Debian, but always the same problem.

Best thing to do is think of an RPi running Linuxcnc as the ECU in an early 2000's car or bike, as long as it works there's no real need to upgrade.
I'd like to be able to count the amount of times I upgraded the ECU on my 1999 Toyota Echo on one hand, but I have all the fingers on each hand

On a normal daily driver or even server kernel upgrades are fine.
The issue in this instance is that the kernel used in the image is particular to the RPi and is custom built.
From playing around with various Arm devices the boards aren't as "generic" as the PC platform. Each Arm processor or SOC has it's own quirks as such. The device tree is a way to let the Linux kernel know which devices are available, device tree overlays are used to further customise the setup.
Then there are custom patches that are used to further "tune" a particular board.
I have 3 main machines at home running Linux, one desktop and laptop running Mint and a server running Ubuntu, kernel upgrades are not an issue on any of these 3.
Obviously I have an RPi5 & 4 for testing Linuxcnc images, so these don't see kernel upgrades unless testing new images.
The Orangepi PC that running my hacked together reflow oven doesn't get upgrades, it works and is left alone, but it does have a custom device tree has I needed some status LEDs and an off button on the front panel from the GPIO header. Now if I was to upgrade this kernel I would also have to rebuild the device tree file to suit.
Whilst the Arm platform is good, it's come along way in 20 years, it's not as generic as the PC platform, it's kinda like pre PC days.......but without the OS software issues.

Try been in the directory where the file is located. Before you run pyocd. Are you able to ping the board. 10.10.10.10 ??

Aaah I see; thoughtless mistake then. Kernel 6.1.0-35-arm64 was the linuxcnc one, which apt erroneously removed in favor of 6.12.11-1 and 6.12.12+bpo-rt-arm64, since those (recently) emerged as the logical successor. Note to future self: do NOT accidentally do dist-upgrade on LinuxCNC!

I was hopeful though, that the original version could be reinstalled without having to redo the whole install. This is because when removed, apt did note that it could not remove the 6.1.0 folders as they had custom files in them. But alas, I accidentally removed linux-image-bcm2712-rpi since that was now linked to the 6.12.12 kernel. That package has no installation candidate, so I'm borked. Reinstalling...

Thanks! That first paragraph was gold. My understanding of how the whole thing works just went *way* up!

Hello,

I am currently trying to get the toolchanger working with probe basic. It works however the subroutine (m13) is made for a continuous motor. This machine uses a stepper motor, with a custom stepper driver. If I enable one relay it moves the carousel one pocket. The relay needs to deactivate before it can be repeated. There is another relay to change the direction. I was wondering for the homing of the carrousel, is there a good way of doing this?
Like a while loop which activates the relay, waits a little bit and deactivates it until the home sensor is activated?