Advanced Search

I see, what do i need to do to get it configured for the RP1? Might be a very obvious answer but im a newbie and dont really yet know exactly what im doing.

Do i have to do anything other than redoing the hal file? This issue seems to be a bit deeper than just the hal file (or atleast thats what makes ĺ
sense to me)

I managed to send the remora firmware to the card but I'm stuck on the config txt file I have an error message ?


attached the videos

youtube.com/shorts/RS7OnZ3ts2o?si=CMQ5Cg7p2Btm-zWb
youtube.com/shorts/JX6X--eaXos
 

Got a strange one with a Pi5...   Network seems fine when I am just pinging my Mesa card (a 7i76e) but when I run Linux CNC, things kick on but then the network crashes and I get a bazillion (technical term) hm2/hm2_7i76e.0: error queuing read iter=xxxx) and everything turns back off.. 

Once it dies I can't even ping the Mesa card (10.10.10.10) until I unplug and plug back in the ethernet cord... Then its happy as a clam pinging.. but once I start up Linux CNC again same crash right as the UI inits. 

(Linux CNC 2.9.3, PI5 8Gb, NVMe Boot)

PCW wrote:

its a bit involved, you can look here for the basic hal setup

linuxcnc.org/docs/html/examples/mpg.html

(that happens to use a software encoder counter but the basics are the same)

Note that there are jog enable,count and scale pins for both axis and joints
The joint pins are active before homing and the axis pins are active after homing.

You could also search the forum for "MPG" as there may be a MPG setup using similar
hardware as yours.
 

Well thanks for that.

I now have the MPG working for the X axis and it was super simple (the example above gave me what I needed, and I only needed 4 lines to get it working

#MPG 

---

setp axis.x.jog-scale 0.001
setp axis.x.jog-enable true
net encoder-counts  <= hm2_7i96s.0.inm.00.enc1-count
net encoder-counts => axis.x.jog-counts
#MPG ENDS

---

I have switches to manually jog, so I will use those to move significant distances, and then use the MPG to home in on the desired position, should make for a user friendly experience.

I will likely upgrade to ball-screws to fix the backlash, however at least now when I change direction the backlash is automatically dealt with.

I 3D printed a belt cover and mounted the X-MPG where the old manual cross slide hand wheel was.

Thanks for all your help, a Mesa board and HAL make customization really easy.
 


 

The menu will automatically expand as you add additional values ​​in the machine configuration file.

INCREMENTS = 5mm 1mm .5mm .1mm .05mm .01mm .005mm
ANGULAR_INCREMENTS = 0.1, 1, 5, 10, 15, 30, 45, 90, 180, 360, 3600, 36000

I think your confusing this with the earlier DAPlink firmware that allowed drag and drop upload.

The CMSIS-DAP-STLINK21.hex firmware converts the STLink into a CMSIS-DAP probe that can be used the MCUxpresso or pyOCD.

Looking at the source for hal_pi_gpio it's setup for the BCM2835 (RPi 4). The RPi 5 uses the new RP1 southbridge chip for IO.

GeckoWorks wrote:

slowpoke wrote:

I had the link for that one. Perhaps I wandered off this thread when I found it. It was a compilation of I think all of the macros showing the actual operation on a lathe much like the video you referenced, just for all the different operations quite a good video, no idea where I found it and can't seem to find it.

Thanks
I think this video does a good job of going through the macros but I don't know if it's the one you had in mind:

 

That is a different video, however somewhat similar. For a small lathe he sure is getting good results.

I'm a bit clueless regarding the available lathe type GUI's (I'm starting with axis), what version is this fellow using?

Are those the "lathe macros" he is using?



 

Hello everyone, ive been trying to set up linuxcnc to work with my Raspberrypi 5 for a week or two now, ive gotten to a point where i can load the hal_pi_gpio driver with no errors showing up, i have a config running in linuxcnc and i can see in halshow that the pins are activating and deactivating, the issue i have is that the pins only activate and deactivate in the software and not physically, i cannot measure any difference on the physical pin itself, i can use gpioset command to set the pins to high or low manually and that works well, but as soon as i try setting it to high/low using halcmd it just doesnt change state, i would greatly appreciate some assistance in setting this up correctly.

The hal file below was given as an example somewhere online, dont remember exactly where i got it but it is as mentioned supposed to work considering that halshow shows the pins and the fact that they should be changing state.