Advanced Search

PCW wrote:

Mesa firmware includes a specific PWMgen for RC servos: RCPWMGen.

This can be added to any Mesa FPGA card. Standard PWMgens tend
to have low resolution when used for RC servos as the full scale
duty cycle of RC servos is quite low ( a few %)
 

In my case even low res motion is better than stop to stop action. Out of curiosity what physical pins on a 7i96 would drive the RC servo. 

Mesa firmware includes a specific PWMgen for RC servos: RCPWMGen.

This can be added to any Mesa FPGA card. Standard PWMgens tend
to have low resolution when used for RC servos as the full scale
duty cycle of RC servos is quite low ( a few %)

PCW wrote:

A 7I92TH/TF and a couple Mach 5 Axis BOBs could do this
(or even without the BOBs if you are careful...)
 

Crazy idea, what is the frequency of the spindle PWM signal on a 7i96 card?  Can I co-op that to drive a RC servo.  Or use a spare output and pulse at 50 Hz? Can the I/O handle that kind of duty cycle toggling?

Yes, pulling the SD card, should also work for me.
Thanks

www.makeuseof.com/tag/enable-spi-i2c-raspberry-pi/
 

Probably not very elegant, but what I have done is:

install Raspbian on a SD Card
use the imager to install LCNC image from the LCNC.org downloads page
leave the boot order to boot from the SDcard preferentially
remove the SDCard
system boots from NVME into LCNC

So far, this has enabled me to keep the Raspbian SDCard handy to reinsert and reinstall LCNC quickly as I experiment with different things and muck up the LCNC install...

This strategy inspired by my innate lazy nature will probably come back to bite me eventually...

Randale

That was just to prove a point, keep chugging along, the experience you get from it is priceless.

When I google change boot order of RPi5, all links say use rpi-eeprom-config --edit and put the 6 at the RH end of the BOOT_ORDER line.
No other option is offered.
Why shouldn't it work, the update page I was pointed at says its for Pi5 ?

Who has said it won't work?

Been reading this silently long enough, so why are you trying to shove rpi4 stuff into rpi5? It most probably not work, hell even stuff for rpi5 does not work on rpi 5 as it has 6 or 7 variants by now, version 3 had a long period where a lot of things did not work. They mostly got fixed by now.
You had a very good reply at the start of this topic, install raspios and see if it works, then just add RT kernel and LinuxCNC.
This is comming from someone who just spent 2 days trying to shove ardupilot with autonomous flight into an ESP32!
One part of me wants to say: take the advice and be done with it, the other part is screaming : keep going, make it work no matter how many tell you it wont work!

But... the update of rpi-eeprom-config to version 2712 doesn't actually change the boot order. No longer messages about PI4, so happy its really installed.

Goes through the motions, confirms on screen that the new boot order will be applied at the next reboot. Machine reboots and rpi-eeprom-config shows that the boot order is the same as it was before.
Sigh.

There is an install in the test folder of the clone.
This runs and installs this later version...

Thanks

sudo python3 -m pip install --break-system-packages pycryptodomex
success.

./rpi-eeprom-config -e run from inside the rpi-eeprom clone directory appears to work, but still fails with RPi4 error.
I can now see on the processing message that it is running an eeprom..2023.bin from outside the clone directory.
To me its odd that there is no install script in the clone and without it, I am stumped.
Thanks again.

They might have made a typo

This may work
sudo python3 -m pip install pycryptodomex

Last try was
sudo python3 -m pip install --break-system-packages cryptodomex

error is could not find distribution.

A 7I92TH/TF and a couple Mach 5 Axis BOBs could do this
(or even without the BOBs if you are careful...)