Advanced Search

Hallo,

ich versuche einen Novusun NVEM mit STM32F207 CPU an LinuxCNC das auf einem kleinem PC (kein Raspberry PI) anzubinden.

Was ich bisher gemacht habe:

1. Installation LinuxCNC auf dem PC
2. Flash der Remora Firmware für NVEM
3. LinuxCNC Ethernet eingerichtet auf 10.10.10.100/24
>> Ping zu dem NVEM läuft
4. Gemäß Quelle DOC folgendes durchgeführt um eben Remora von GitHub auf den PC zu bekommen:
>> Mir ist hier aufgefallen das einiges fehlt unter anderem die Basic-Config "remora-nvem-basic" und unter den Components "Remora-nv"
Ich habe diese dann extra zum PC rüberkopiert in die entsprechenden Ordner.
5. Installieren der Componenten mit halcompile
>> Dabei ist aufgefallen das hier "Remora-nv" fehlt also nochmal nachinstalliert:
6. Die Beispiele der Configs in den Linuxcnc Ordner kopiert - dazu zusätzlich die "remora-nvem-basic"
7. Upload der Config zu dem NVEM - dazu musste ich tftp nachinstallieren 
>> Bei ausführen des uploads scripts dann bin ich im selben Ordner wie die einfache Config.txt von "remora-nvem-basic":
>> das scheint auch soweit zu klappen.
8. Start von LinuxCNC und auswählen der NVEM Basic die ja zur Config.txt passen soll. Alles Startet ohne Fehlermeldung.
>> ab hier kann ich zwar bei LinuxCNC den eStop aufheben und auch die Maschine einschalten. Aber sobald ich eine Achse X verfahren will kommt "Joint 0 following Error"
Ich denke der macht keine Pulse zumindest kommt bei den Treibern nichts an. 

Wie hast du die zum laufen bekommen?

To give you more technical background: this controller is the result of over 10 years of experience in industrial machine retrofits.

The project was accelerated by the massive Mesa card shortage in 2022. Instead of waiting for hardware that wasn't available, we decided to develop our own high-performance industrial-grade solution tailored specifically for complex retrofits. This isn't just a prototype—these units are already integrated and running 24/7 in machining centers, proving their reliability in real production environments.

Key Hardware Specifications:

Core: Custom FPGA running HostMot2 firmware for rock-solid real-time performance.

Fully Isolated Analog Servo Control: Precise ±10V analog outputs with a 7V/μs slew rate. The analog outputs are fully galvanically isolated from the logic to prevent noise and ground loops.

High-Speed Feedback: Isolated encoder inputs supporting up to 10MHz—ready for any high-resolution industrial encoder.

Industrial Isolation & Protection: Complete galvanic isolation between logic and I/O. The 24V field power is protected, and the logic power is fully isolated.

Onboard Processing: Integrated Raspberry Pi Compute Module 5 (CM5), providing a massive performance boost for LinuxCNC and NativeCAM.

Thermal Design: Fanless industrial enclosure. No moving parts, no dust intake—designed to last in woodworking shops.

The goal was to create a controller that is fast, precise, and, most importantly, available for professional retrofits when the industry needs it most.

Hello,

I'm trying to connect a Novusun NVEM with an STM32F207 CPU to LinuxCNC on a small PC (not a Raspberry Pi) for a mini lathe – just the X and Z axes, no limit switches, etc. Very simple.
I'm using just two TB6600 stepper drivers with 1.8 degree and 1.8A stepper motors, connected according to the many wiring diagrams I've found online.
So, Pulse+ and Dir+ are connected together to COM+ on the NVEM, and then Pulse- and Dir- are connected to the corresponding NVEM pins.
Everything is powered with 24V, including the stepper drivers and the NVEM.
All the LEDs are lit, so everything is receiving power.
What I've done so far:

1. Installed LinuxCNC on the PC
2. Flashed the Remora firmware for the NVEM
>> Source DOC: remora-docs.readthedocs.io/en/latest/har...ml#controller-boards
>> Firmware for STM32F207:
Either this one: github.com/scottalford75/Remora-NVEM/tree/main/Firmware
or this one: github.com/scottalford75/Remora-NVEM/tre...-NVEM-STM32/Firmware
I flashed the latter onto the NVEM.

3. LinuxCNC Ethernet configured on 10.10.10.100/24
>> Ping to the NVEM is running

4. As per the source DOC, the following steps were performed to get Remora from GitHub onto the PC:>> I noticed that some things were missing, including the basic configuration file "remora-nvem-basic" and the component file "Remora-nv".
I then copied these files to the appropriate folders on my PC.

5. Installing the components with halcompile:>> It was noticed that "Remora-nv" was missing, so I installed it again:6. I copied the example configurations into the LinuxCNC folder, along with "remora-nvem-basic".
>> After starting LinuxCNC, I can select various Remora configurations to start.

7. Uploading the configuration to the NVEM - for this, I had to install TFTP:- via a workaround involving the installation of pip3, etc., since some things are not installed by default in LinuxCNC.
>> When I run the upload script, I'm in the same folder as the simple config.txt file from "remora-nvem-basic":>> This seems to be working so far.

8. Starting LinuxCNC and selecting NVEM Basic, which should match the Config.txt file. Everything starts without an error message.
>> From here, I can cancel the eStop in LinuxCNC and also turn on the machine. But as soon as I try to move an X axis, I get "Joint 0 following Error."


I think it's not sending any pulses; at least nothing is reaching the drivers.
Although I assume it's only controlling stepper motors in the config without encoders—how does it know the following errors? It must be a configuration problem, right?

Does anyone know where I can check this?

Regards,

Hi Forum; 

I went to use my CNC Router the other day and the cobbled together controller has give up.. Won't even boot after a few kicks and wiggles...

So I've put together a Raspberry Pi LinuxCNC controller with a mesa board to squeeze into the old PC location.

I've gotten  the Pi5/LinuxCNC all running off the boot image but just yesterday received and added the Mesa 7C81 I/O board. 

It's assembled and powers on, now I just need to figure how to connect the Mesa I/O to the outputs from LinuxCNC.   I guess it's time to read.

If anyone has a good 7C81 configuration page they can refer me to I'd appriciate it.  Ive just started and am not stuck yet but love a good example to follow. 

Adventure Awaits!

My second machine build log, If you want a good laugh and have time to waste that you will never get back
www.cnczone.com/forums/cnc-wood-router-p...t-log/35355-cnc.html
 

Es werden doch verschiedene 7i98 angeboten. Welche genau?

Das 7i98 Bitfile von Baidu funktioniert nur mit der "v1.1", lässt sich aber auch auf eine 7i92 flashen, weil es in Wirklichkeit ein 7i92 Bitfile mit 3 Kanälen ist, statt 2. Die 7i92 zeigt dann 50 Pins an, brickt aber nicht. Trotzdem nicht nachmachen!
Wenn man dieses Bitfile auf eine 7i98 flasht, die dem Original entspricht, brickt die Karte und sollte sich nur per JTAG wieder richten lassen.
Die Pinbelegung ist auf meiner großen 7i98 nicht angeschrieben, ist aber mit gleichen Pins des FPGA verbunden, wie die 7i92 oben in meinem Bild. 3.3V Pin ist der quadratische.

Sowohl die 7i92 oben im Bild, als auch die 7i98 in voller Größe funktionieren mit originalen Bitfiles von Mesa. Die 7i98 "V1.1" funktioniert nicht mit originalen 7i98 Bitfiles, es lassen sich aber, neben den Bitfiles von Baidu 7i92 Bitfiles von Mesa flashen, ohne dass sie brickt. Die funktioniert dann aber in EMC nicht, das dann eine Hostmot2 Fehlermeldung ausspuckt. Die "V1.1" funktioniert also wirklich nur mit chinesischen Bitfiles. Eventuell kann man selbst ein Bitfile machen, ich habe es aber noch nicht probiert, da ich noch keinen PC dafür habe und die AMD Software auf meinem Raspberry nicht laufen wird.

Beim Flashen sollte man bei allen Karten wie folgt vorgehen:

sudo mesaflash --device ethernet --addr 10.10.10.10 --write bitfile.bit --fix --fallback
sudo mesaflash --device ethernet --addr 10.10.10.10 --write bitfile.bit --fallback
sudo mesaflash --device ethernet --addr 10.10.10.10 --reload --fallback 

sudo mesaflash --device ethernet --addr 10.10.10.10 --readhmid  sollte dann die neue Pinbelegung ausspucken. Falls die Karte nicht gefunden wird, funktioniert die Firmware nicht und wird die Karte bricken, wenn man sie in den normalen Bereich flasht. Falls die Firmware nicht funktioniert, trennt man die Karte von der Stromversorgung und verbindet sie wieder, dann läuft sie wieder. Das Bitfile sollte man dann nicht mehr nehmen.

Falls das Flashen funktioniert hat und die korrekte Pinbelegung angezeigt wird, geht man dann weiter wie folgt vor:

sudo mesaflash --device ethernet --addr 10.10.10.10 --write bitfile.bit --fix 
sudo mesaflash --device ethernet --addr 10.10.10.10 --write bitfile.bit 
sudo mesaflash --device ethernet --addr 10.10.10.10 --reload 

Das Bitfile ist dann dauerhaft geschrieben und ist auch nach dem Trennen der Stromversorgung im Flash gespeichert wird also immer automatisch geladen.

Diese Prozedur ist auch in der chinesischen Anleitung so zu finden.

Die kleine 7i98 "V1.1" würde ich nicht noch mal kaufen, da die original Bitfiles von Mesa mit der nicht funktionieren (es sollte aber möglich sein selber welche zu schreiben). Die oben gezeigte 7i92 und die 7i98 in voller Größe entsprechen aber dem Original und funktionieren mit den originalen Bitfiles von Mesa. 



 

bladekel wrote:

I am using a Raspberry Pi 5 with the LinuxCNC Debian Bookworm image.
I have configured the system to communicate over SPI.
I can move all axes, but when I run a G-code file, I experience a drift in all axes.

To troubleshoot the issue, I wrote a simple G-code program that only moves the X-axis: it moves 10 cm in the positive direction and then 10 cm in the negative direction.
I set this program to run continuously in a loop. In every cycle, a small shift occurs in the positive direction.
After 20 repetitions, I observed that this drift reached approximately 5 mm.
The start and end points of the program shift slightly in the positive direction with each iteration.
I have also tested it at very low speeds, but the result remains the same.

I am certain there is no mechanical backlash or electrical interference/noise.

I am attaching my configuration files. What do you think could be causing this?
 

For those who might encounter this problem, just like me;

This problem is caused by the dir_delay. 
Solved by increasing the dir_delay value.

I am using a Raspberry Pi 5 with the LinuxCNC Debian Bookworm image.
I have configured the system to communicate over SPI.
I can move all axes, but when I run a G-code file, I experience a drift in all axes.

To troubleshoot the issue, I wrote a simple G-code program that only moves the X-axis: it moves 10 cm in the positive direction and then 10 cm in the negative direction.
I set this program to run continuously in a loop. In every cycle, a small shift occurs in the positive direction.
After 20 repetitions, I observed that this drift reached approximately 5 mm.
The start and end points of the program shift slightly in the positive direction with each iteration.
I have also tested it at very low speeds, but the result remains the same.

I am certain there is no mechanical backlash or electrical interference/noise.

I am attaching my configuration files. What do you think could be causing this?

I tried on a Raspberry Pi 4 with image "image_2026-01-21-raspios-lcnc-2.9.8-trixie-arm64"
and on a Laptop with image "linuxcnc_2.9.8-amd64.hybrid"
and unfortunately i get the same results on both, with the simplest configs i can do, even in the test/tune tab in pnc wizard it acts the same way, Sorry guys i may be missing something really basic here, do you think it might be the firmware?

config name "GG" made on the laptop

Files attached

Yeah that’s the one

I was trying to load gcode file for small engraving of size 200x150mm, gcode file size is 243MB. I tried qtdragon_HD and Axis GUI both crashes while loading the file. Even I tried disbling preview by adding (AXIS,hide) at start of GCODE. But didnt helped. Using Raspberry PI 5, 4GB RAM version.

Untested

 

 

i think NOT need this HAT, i think can build own "hat" mean connect to gpio pins shift level converter tx108 chip module, input is 3,3V and this module convert output to 5V and this 5V signal can wired to stepper driver board DM556 etc, step pin and dir pin and enable pin. but problem have how i setting rpi4 linuxcnc all gpio pins ? rpi4 and has installed linuxcnc but if looking have only config wisard and this can only setting paraller port pins, and pnconfig tool has only how setting mesa card pins, i not understand how can setting rpi4 gpio pins all step, dir, enable and all input pins home, e-stop, limits, probe, etc pendant encoder, rotary SW, axis select, scale select. i have installled linuxcnc to rpi4 and software/image working ok, but how setting gpio pins ?

Might be worth asking in the Remora thread.

Hello forum,
I have 6 x 1KW Lichuan LC20 drives and have been trying to get them to work with Raspberry Pi 4B 4GB and LinuxCNC for about 9 months.  I realised I don't have the technical knowhow to make this work.  Using this forum, youtube and Grok, I was able to get close, getting the Raspberry Pi to work as a master and I even got all 6 drives to work as slaves, but trying to get them in to OP mode proved impossible.  On one occasion, when I unplugged 5 of the 6 drives, I managed to get it to go into OP mode but have not been able to replicate it since.  And I have never been able to understand how to get them to turn using LinuxCNC, that baffles me a bit so I have never actually seen the motors work ever.
I am open to buying hardware that kinda works out of the box but I have no idea what that is.  
Can anybody on this forum work with me over time to help me to get these things to work with LinuxCNC, or even Mach???  I can't return them, and after spending $2K on them, I can't afford to buy something a little more 'out of the box'.
Any assistance would be greatly appreciated.
Andrew.
 

Is it this?  github.com/cakeslob/RRW_LAB
google does not find it but duckduckgo shows it first