Advanced Search

Hello, I am testing LinuxCNC 2.9.7 (official Raspberry Pi 4/5 image, Debian Trixie, uspace) on a Raspberry Pi Compute Module 5 (CM5) with a Mesa 7i95 Ethernet card.
The same LinuxCNC version, Mesa card, cable, and network configuration work on another Raspberry Pi platform, but on CM5: • eth0 stays NO-CARRIER • ethtool eth0 shows Link detected: no • Forcing speed/duplex has no effect • RP1 PCIe device is detected in kernel logs Network: • eth0: 10.10.10.1/24 • Mesa: 10.10.10.10
Is CM5 fully supported by the current LinuxCNC Raspberry Pi 4/5 image, or is newer kernel / device-tree support required for RP1 Ethernet on CM5? Thank you.

    Good morning, I am new to this community and joined in hopes you could help me step into the world of CNC’ing. Couple of years back I purchased this multi-cam CNC that had been sitting for a while. It had been used to machine deep pockets into Ovation guitar bodies. After cleaning out all the fiber material I found all the slide bearings in almost new condition. I took a bunch of picts and proceeded to completely disassemble the unit for restore. All the wiring too! I thought I would I’ll just look up what information I need to put it back together… bad plan! Not only can I not find how to wire these components I’m not even sure where to begin, what to keep and what to ditch.I will replace the spindle but would like to keep using the x,y,z motors. These are Allen-Bradley N-3412 B series brushless servo motors powered by Electro-Craft DDM-009 drives. All the rest I want to have new. I figure to use LinuxCNC on a Raspberry 5 with Unbuntu to control these x,y,z axis and (maybe) control the spindle (whatever that will be) separately. What add-on board and how to finally connect the motors escapes me.I have looked and looked but don’t know where to start. I need help.I would greatly appreciate any advise or direction. 

Es ist gar nicht so einfach Bilder hier hochzuladen, ich habe es jedenfalls nicht geschafft (waren auh nicht zu gross).
Ich habe die Bilder unter github.com/freylax/riocfg/img eingestellt. Es ist ein alter selbstbau Plotter aus DDR Zeiten den ich als CNC Testobjekt verwenden moechte bevor ich mich an die richtige Maschine bei meinem Freund ranwage.

Raspberry PI5, Olimex ICE40 EVB, Adapter und CNC Breakout Board, Stepper Driver.

Ich kann die Mikrosteps einstellen, allerdings scheint das nicht ganz zum Erfolg zu fuehren. In der rio-test app kann ich den 
Motor schrittweise steuern, das klappt. Aber wenn ich in der axis app Manuell zb 5mm anfahre und auch eine geringe Geschwindigkeit einstelle, dann vibriert der Motor nur und es werden  keine richtigen Schritte daraus. Was mach rio-test anders?
Ich studiere auch den Code um das zu verstehen.

liebe Gruesse,
Robert 

I did a similar thing a few years back, I used Clough42's Electronic lead screw project and made a few changes to the program to make this work for my needs. all I needed to do was mount an encoder and put a motor on one of my dividing heads. I have since taken apart the electronics as I needed them for other projects but I am now using the DR-DRO Raspberry Pi-based rotary controller for stuff like this. The DR-DRO is much more flexible to do crazy stuff on manual machines. I am thinking about doing the same setup on my mh800e that is retrofitted to linuxcnc

Oh no, something else not quite right with my build. The halrun binary seems to be missing. I will try to find out how that dropped out. I will need it for the project where I plan to use this pi3.

Another latency test. The previous one I shared was run a couple minutes with nothing else running. This time I gave it the works. How about 10mS latency.

Here are the error reports I get trying to wake QtDragon. seems to be a complaint about the ngc path. I'm using run-in-place. I've got to look at this again. Just writing it up gave me more ideas.

Wow, I can hardly believe I did this to a pi 3. The simulation is running. Next I want to check if gpio and a couple other basics work. The latency numbers look a bit sad.
Still no luck starting QtDragon.

Got LinuxCNC built. Running latency test. Tried running Axis and QtDragon, gui just crashes, need to spend a little more time on it, maybe tomorrow. I think I got some missing dependencies going on.

This is catching my interest. I think I will try it. I have at my fingertips a Pi 3 Model B+ but it is not working, not sure why. Maybe I dropped it a while back. I also have a Pi 3 Model B V1.2, I have it running a fresh install of Debian 12 Bookworm.

Now it is installing LXDE.
Next up is realtime kernel, I'm looking at linux-image-6.1.0-41-rt-arm64
And then LinuxCNC....
Fingers crossed...

There are no premade RPi3 images available for download.

You have a couple of options.
1: Someone maybe able to make one, but it would require that person having access to a Rpi3.
2: Find someone with Linux knowledge who can also speak english and is willing to help.
3: Have a go following someone's instructions, all is not lost if you make a mistake.
4: Look into using grbl.

A bit of a warning regarding the RPi3, you may have latency issues, which there may not be a solution for fixing it. Increasing thread period may not give smooth operation.

Saying that you don't understand all the time wont help. I'm sorry I really wish it was different.

Yeah std breakout board, a lot of the generic Chinese one have a 0-10v converter. Mesa also sells something called spinx1 store.mesanet.com/index.php?route=produc...oduct&product_id=205 which could be connected to the 2nd port on the 7i92T.
Glass sensor would require a buffer circuit of sorts I guess, PCW would have the best advice regarding that.

I've been using an original 7i92 for years (the change was to a different FPGA for the T) and had no issues........plus a number of other cards as things grew


This how good the support from Mesa is. Some users have bought clones from AliExpress (I'd recommend the genuine thing) and he's been happy to help those users out. TBH PCW has helped me out when I got bored and tried to build a clone of a 7c81 based on a Spartan6 FPGA dev board. Which does work either via SPI to Raspberry Pi 4/5 or a PC with a parallel port using the EPP protocol.

You may find some forum users very biased towards Mesa, some build machines professionally and only use Mesa, other have converted a mill or a lathe....or many other machines that I have probably missed. But they all swear by Mesa products.
Not that there aren't other options, but it's the best way if you "just wanna make chips".

what is kernel and what is compiler, how use or how install and use. what is repos and scratch. not understand code nerd super engineer language. (translator not help this)

It appears to work fine. Any further suggestions would be appreciated.

Full HAL file attached.
 

And here is the Snippet:
# --- SPINDLE PWM CONFIGURATION ---

# Load and Add Functions
# (Ensure loadrt pwmgen and loadrt scale are at the top of your file)
addf pwmgen.make-pulses base-thread
addf pwmgen.update servo-thread

# 3. Connect Spindle Enable
# This turns the PWM generator on only when the spindle is active and needs to be eliminated.
# (removed) net spindle-on spindle.0.on => pwmgen.0.enable

#Inverted Voltage Corrections
# First you need to add the next two lines above
# loadrt not count=1
# addf not.0 servo-thread

# set the Frequency
# first we need to set a frequency for the PWM in order for it to smooth the output
setp pwmgen.0.pwm-freq 100.0

# Calibration
# When using a 0-10v output signal, you may need to invert the PWM output
# so that the 5 axis breakout board will output 0V at spindle off,and
# 10v when the spindle is full on. The Negative sign before the 60000 usually does this.
# unfortunately the resting (spindle off) voltage is 10.0V - bad -very bad!
# rather we leave everything alone and creat a not.0 variable that reverses the values
setp pwmgen.0.scale 60000
setp pwmgen.0.offset 0.0
setp pwmgen.0.enable 1

# Connect Spindle Speed Command
# This signal carries the RPM requested by G-code (S command)
net spindle-speed-cmd spindle.0.speed-out => pwmgen.0.value

# Prepare to invert it
net spindle-pwm-raw pwmgen.0.pwm => not.0.in

# Connect and invert the PWM Output to Physical GPIO
# This is the "Writer" for GPIO18
net spindle-pwm-final not.0.out => hal_gpio.GPIO18-out

#End Spindle Code