Advanced Search

Hallo, woher genau bist Du denn? Könnte man auch mal vorbeikommen? Oder telefonieren? 0171 4152421 Gruß Markus Scheck

It was the probe height setting. Increasing the probe height setting a lot made it work with one touch. 

Looks ok now.
 

Agreed; so much good code goes to waste; at least it's open source!

Dead proprietary programs just go to waste.

But why is there a double sense always? 
It should be enough with one, the first contact.
The plots are from a web csv plot tool, output from the sampler component to record longer sequences.
 

The following settings have been used.

 
 
 

Hi Shemj
I am currently having the same issue as you when I press ref (X/Y/Z) in probe basic the machine moves to its 0 position on that axis uncontrollability ignoring the maximum velocity.

Please let me know if you have found a way to home to machine and retain the encoder values when the machine is powered off ?
cheers will

That should not be a distro issue, but a config issue, so do start a new topic and upload both configs so we can have a look.

f355 wrote:

I'm happy to be helpful to the community even if it is just planting ideas into smart people's minds

That is quite a habit to have, so use it as much as possible.

Saw that, but was too lazy to setup the spare RPi. In fact that was what led me to pi-gen. Tho I haven't completely ruled it out.
Tho I do seem to like with pi-gen you can stop the process at certain stages.
Luckily or maybe not so I'm in a position where time is something I have plenty of. Also a couple of PC's I can use to build different configs. Sadly only one spare RPi400 and one spare RPi5, with the RPi5 being part of a very generous gift on Father's Day from my son.

first of all, thanks for the kind(-ish, lol) words, I'm happy to be helpful to the community even if it is just planting ideas into smart people's minds

have you seen github.com/raspberrypi/rpi-image-gen? to me it looks like a better fit for the purpose - all we need is to install some packages and configure some things, right? building the entire distro from scratch seems excessive.

The buildbot doesn't seem to be working properly at the moment.

I have build a test .deb manually instead.

www.linuxcnc.org/temp/linuxcnc-uspace_2.9.7pre_amd64.deb

You should be able to download the file and install with
Note that this will overwrite your current linuxcnc installation (or will install linuxcnc if it is not installed on the machine). It will not alter the Linux OS and your current machine configurations should be unaffected.

Hi,
i wrote a hal component in python to control some I2C devices

*  pcf8574 : Digital IO's
#  ads1115 : Analog input
#  lm75  : temperature sensor
#  hd44780 : LCD display

It is actually part of the RIO project, but can also run independently.
Maybe someone can use it.
It's also no problem to install additional devices. Just let me know what you need; I have almost everything here


Cheers Olli

Link: github.com/multigcs/riocore/blob/dev/rio...ins/rpii2c/rpii2c.py

After a bit of a discussion with forum member f355 it came to my attention that an image based on the "Raspiberry Pi Way" maybe possible. Whilst a little "terse" at first he did raise some valid point and gave me time to reconsider some things. And eat some humble pie. I would like to give thanks for this...sometimes it's needed to find a new direction.

One reason for this idea is to make using the image more familiar to those used to the RPi ecosystem. Being able to use the RPi imager and setup some defaults may be beneficial as well.

At the moment I'm experimenting with pi-gen ( github.com/RPi-Distro/pi-gen/tree/bookworm-arm64 ) target a bookworm based image, as I feel as time moves on and more familiarity is gained using the tool a working image with a RT kernel and Linuxcnc will be produced and can be compared to the existing image. Wifi seemed to be a bit of a issue from time to time.

Hopefully from this in the readme "Tool used to create Raspberry Pi OS images, and custom images based on Raspberry Pi OS, which was in turn derived from the Raspbian project." distribution should not be an issue.

So the first task is to create a basic image to get a feel for the tool.

All input whether positive or negative ( remember coming from Australia I'm somewhat hard to offend ) is welcomed and encouraged. Rather than the way it has happened in the past I would like this to be more of a community effort with regards to packages. Please remember the object is not to create a daily driver OS but one that makes the entry easier to running Linuxcnc on a Pi. Whilst it may be beneficial to include CAD\CAM I feel leaving this out will create a smaller image to download, and as there are many packages available half will be happy, half wont be and the other half may not have a preference.

As a final note the final decision will have to be made by the Linuxcnc hierarchy as I dont want to go against their wishes, but for the moment I think at least a discussion is good idea, and see what the community thinks.

Yes,yes I know some our esteemed members aren't exactly keen (not recommend) on the RPi due to cost factor.

Cheers
Rob

So i disabled
#net machine-is-on halui.machine.is-on
in my machine.hal

and did this in my custom_postgui.hal
net MachineLED <= halui.machine.is-on => gladevcp.led_Startstopp

unknown wrote:

Would this be a situation where you would like to give a little more input. 
 

Oh certainly and with pleasure! Feel free to create the new thread and shoot me a link.

1. All of this is my method. I'm not implying it is better or worse than yours, it's just mine.
2. There still is/was a patch that exposed /sys/kernel/realtime that linuxcnc required before 2.9.5, and the kernel is still built from source and baked into the image, as opposed to being installed from an apt repo. That makes the kernel update path unclear to me.
3. I could have asked, but I didn't. I never implied that "those that manage Linuxcnc allow randoms to upload untested content to their server", I'm sure the images are well tested and vetted. All I said is that it is completely non-obvious where the image builder sources are - I've just spent 10 minutes to find them again and I couldn't - and the official github has obsolete sources. That doesn't inspire much confidence in how well those images would be maintained in the future, don't you think?
5. I understand there are differences, it is obvious, I just don't want those differences. I gain nothing by learning how yet another distro is organized, it is wasted brain cycles. Now, your copyrighted branding point makes a lot of sense - I honestly did not think about that, and yes, it certainly adds a huge deal of motivation for not using RPi OS for pre-built images, but as I said even before your point, I totally get why your images exist. You've done a great job, I'm just not in the target audience for your work.