Advanced Search

intermitent problem! try pulling and pushing the card into the pci slot few time to try to get a good contact, the pci copper fingers get oxidised after few years unused.

My understanding is that your computer reboots only when you run Linuxcnc?
You could install the latest Linuxcnc and test your lathe  with your current setup files (ini, hal, ui …)

The apt installation is better if your not doing dev work.

kcjengr.github.io/probe_basic/development_quick_start_apt.html

The hal shouldn't really change much and the ini and other files can be compared to the probe basic sim config files.  Just update the new sections and files.   Should only take a few minutes. 

Open the folder in any file explorer, right click on the ini file, click on "open with" then in the new window click on "use custom command" and type in linuxcnc and press enter.
Although that might not work as there are way to many things changed in Probe Basic.

Remove the lathe power plug, try again.

I have had issues with older 4b's until I updated the firmware but that was done using a setting in rpi-imager

Hello Everyone, 
I finally got Probe Basic on my new computer, it's a Dell OptiPlex 5040 and everything installed nicely. 
My question is can I take my milling machine configuration and use Pncconfig to update it since my original configuration is from version 2.8.0 and make it work with version 2.9.3, I have tried playing around with Pncconfig and it doesn't seem to want to load my original configuration files...

Excellent. Thanks! I just put the Hal meter on inmux.00.enc0-count and see that it is in-fact counting when I move the MPG wheel, albeit backwards. I do have noise issues on the TB4 and TB5 inputs that are occurring when the DMM servo drives are powered up, even with the drives disabled.  This doesn't seem to be affecting the motor encoder inputs, however.  I followed all of DMM's recommendations for shielding and noise filtering - but regarding the signal cable shielding they recommend connecting the shied ground the the connector shell at the drive end vs. the MESA manual which recommends shielding at the Mesa end...

Skylor

-Check if the ram memory is detected correct in the bios.
-Replace ram memory, check cpu temperature (old thermal paste?)
-Another/Newer kernel
-maybe it's just a defect in the mb or cpu

For the RP2040 Andrew implemented the double buffers and methods to get the current buffer.

this->rxData = getCurrentRxBuffer(&rxPingPongBuffer);
this->txData = getCurrentTxBuffer(&txPingPongBuffer);

I'm waiting on stock of the RP2340 to arrive so I can get another new toy. It looks like the RP1 is getting more and more popular and with the version of the RP2340 with more IO would allow for even more functionality.

Might be a good excuse to learn the PIO stuff and port over the other Remora modules. At the time I did the RP2040 it was suitcase project while I was travelling for work.

No, they are always there.

setp near.0.difference 8.33333

In this case means you have to be within 8.33 RPM of the
commanded RPM to make spindle at speed true

man near
 

Well I tried our image first, and got this:
 

That was written with rpi-imager without error.  Note the bootloader date (2022).  So then, long-pressed shift and installed the latest RaspiOS. In that, did a sudo rpi-eeprom-update to see what firmware versions were in use:
 

So looks like there are still firmware updates. So then issued a sudo rpi-update, which after that completed, was verified:
 

So then the SD card was re-burned with our image, and that now boots, woohoo!  Thought I'd share if anyone else experienced this.

Try installing those one by one.