Advanced Search

did you update all of the config files? that is why i wanted to see your var file. if it was out dated it means all the subroutines are also outdated which would be a possible contribution to your issue.

once you have verified all of your config files have been correctly updated for the latest probe basic release requirements, if you still are getting the error then come back and we will have a further look at it. in the interim it is always best to run a comparison on config folders when you do an update. in many cases if there are substantial changes to probe basic that include configuration changes such as subroutine file edit and or adds/deletions, if you do not have those things will not work as expected. a quick test is to try probing in the sim, if it does not fail in 0.5mm, then you know its a config issue.

royka wrote:

If you build LinuxCNC now from Master you don't have to patch the kernel anymore from 6.12+.
To be clear, of course you still need a PREEMPT_RT built kernel.
 

Do you know if this has filtered down to 2.9.4 yet ?

KrisJ wrote:

I'm trying to follow Deje63's step by step to build the RT Kernel but I end up with an error:
"reversed (or previously applied patch detected) assume -R?" when trying to run command
"patch -p1 < ../patch-$RT_PATCH_VERSION.patch".
I'm not sure what it meant so I tried to patch anyway but end upp with make throwing "Error 2" at me,.on makefile:1921. Any idea what this might be and/or how to rectify it?

OR even better if anyone might be able to share an .img with LinuxCNC working with Rpi5 and built on RaspberryOS Lite.
I can't get the GPIO pins to work with the distro on the downloads page and it looks like in the man pages that a build on RpiOS is necessary for this to work...

Edit: attached Deje's txt-file for convenience. 

 

I can't get the GPIO pins to work this doesn't help.
and it looks like in the man pages that a build on RpiOS is necessary for this to work... This is not true

Output from a halrun session loading the driver

halcmd: loadrt hal_gpio inputs=GPIO5,GPIO6,GPIO12,GPIO13,GPIO16,GPIO17,GPIO18,GPIO19 \
halcmd+:                                 outputs=GPIO20,GPIO21,GPIO22,GPIO23,GPIO24,GPIO25,GPIO26,GPIO27 \
halcmd+:                                 invert=GPIO20,GPIO27 \
halcmd+:                                 reset=GPIO21,GPIO22
Note: Using POSIX realtime
halcmd: show pin
Component Pins:
Owner   Type  Dir         Value  Name
     4  bit   OUT         FALSE  hal_gpio.GPIO12-in
     4  bit   OUT         FALSE  hal_gpio.GPIO12-in-not
     4  bit   OUT         FALSE  hal_gpio.GPIO13-in
     4  bit   OUT         FALSE  hal_gpio.GPIO13-in-not
     4  bit   OUT         FALSE  hal_gpio.GPIO16-in
     4  bit   OUT         FALSE  hal_gpio.GPIO16-in-not
     4  bit   OUT         FALSE  hal_gpio.GPIO17-in
     4  bit   OUT         FALSE  hal_gpio.GPIO17-in-not
     4  bit   OUT         FALSE  hal_gpio.GPIO18-in
     4  bit   OUT         FALSE  hal_gpio.GPIO18-in-not
     4  bit   OUT         FALSE  hal_gpio.GPIO19-in
     4  bit   OUT         FALSE  hal_gpio.GPIO19-in-not
     4  bit   IN          FALSE  hal_gpio.GPIO20-out
     4  bit   IN          FALSE  hal_gpio.GPIO21-out
     4  bit   IN          FALSE  hal_gpio.GPIO22-out
     4  bit   IN          FALSE  hal_gpio.GPIO23-out
     4  bit   IN          FALSE  hal_gpio.GPIO24-out
     4  bit   IN          FALSE  hal_gpio.GPIO25-out
     4  bit   IN          FALSE  hal_gpio.GPIO26-out
     4  bit   IN          FALSE  hal_gpio.GPIO27-out
     4  bit   OUT         FALSE  hal_gpio.GPIO5-in
     4  bit   OUT         FALSE  hal_gpio.GPIO5-in-not
     4  bit   OUT         FALSE  hal_gpio.GPIO6-in
     4  bit   OUT         FALSE  hal_gpio.GPIO6-in-not
     4  s32   OUT             0  hal_gpio.read.time
     4  s32   OUT             0  hal_gpio.reset.time
     4  s32   OUT             0  hal_gpio.write.time

This is from the latest image. Now if something doesn't work, please please go into detail. How are we supposed to fix an issue when you don't elaborate on what happens ? I can't tell you how frustrating this is.

This driver wont work on the RPi5 hal_pi_gpio has it depend on the bcm2835 headers, which is applicable for the Rpi4 & Rpi3.

 

Just a stab but have you tried ./macros instead of just macros?

It's an output pin of the cia402 component so the cia402 component writes the control word to lcec

I have been bitten by the 3D printing bug as well and because of recent Bambu Lab events I am in the process of
building a Voron 2.4. To the vets who have done this before have you done the can bus print head conversion
and if so did it make things better, faster, ect?

I have just copied over the latest probe_basic.var file from github and same results.

I have tested my probe in hal and I have two entries. Probe in and probe input. Only probe input is turning yellow when triggered.

No tommy not study at 1800 ... only study element table as explain here in old continent with scientific Latin world .... All nation use a derived name, based on Modern Latin (silicium = modern latin .... silex = old latin) .... at end your explanation is right, But if you buy a table of element in Italy Silicium is the world ... or Silicio in italian ... Silicium is for most part of european people if they buy an original element table (not in local language).

Any how Tommy when study zilog80 and NE555 texas instruments (25 year ago) all manuals talk about Silicon. American manual obviusly ... Have you never noticed that the division between Christianity and Protestants here in Europe has also divided scientific studies? This is what happened.... we separated 300 years ago and even today we struggle to find the thread of union.

The dumification is an old history ... and history tends to be really boring!!! .... need to change it every one a little pieces .... THAT'S THE WAY !  (that I prefer to "may the force be with you").

Post your var file

unknown wrote:

Aussie:

 but can chain an otto bin lid behind the bike

 

Dear Friend ... snow and drunk can be a good couple if after can go to sleep ..... my english I know is terrible .... after these I'm curious about your upper worlds ... seems like a figure to speech .... and honestly I know only "brass monkeys", no other unfortunately my flights is only for work, so is difficult to discover people culture. Here for me is a better place.

Ok you take a pause from work (chat gtp explain to me these is a typical australian slang) .... but where does these phrase came from? (I refer to ..... can chain an otto bin lid behind the bike ...) .

bye .... uknowwn member ....

For your actual machine I wouldn't bother with step/dir and go straight to another servo ethercat. Sell yours and with 150 difference you are already setup.

For your second machine take a look at FlexiHAL, you can directly slap a raspi5 in it. also they are designing a new board with Rj45 for step/dir and another guy is designing a board to swap A6 step/dir to Rj45. Join the printNC discord the board creator is there

My servos just need a boolean input, guess yours need the same

Just fresh installed PB and probing works like a charm. Check probe behavior in halshow?

Thanks for the reply. I updated about a month ago.

So the behaviour is. No matter what i change the probe will only search down 0.5mm

Then I get a message saying G38.2 move finished without making contact.

Thanks Chris