Advanced Search

Hello everyone,

I'm trying to use the NVEM V5 board with LinuxCNC, running the Remora RT1052 firmware.


---

✅ What has already been done:

1. The Remora RT1052 source code was downloaded directly from the official GitHub repository.


2. Inside the remora-rt1052/source/ folder, a new folder named default was created.


3. Inside the default folder, two files were created and configured:



defaultConfig.c

defaultConfig.h


4. These files were manually edited to define fixed pins for the NVEM V5, with the following configuration:



4 axes (X, Y, Z, A)

2 encoders

The remaining I/O as digital inputs and outputs


5. The project was successfully compiled using MCUXpresso IDE, generating a .bin file.


6. The .bin file was flashed correctly to the NVEM V5 using pyOCD, with no errors.


7. On the computer, the network interface was configured with a static IP, and the board responds to ping.




---

⚠️ What has not been done:

❌ The upload_config.py script was not used (the NVEM V5 does not support it).
❌ No remora.conf file was used.
❌ The HAL pins have not yet been defined in the .ini and .hal files, since the pins are fixed in the .bin.


---

❓ Current issue:

Even after all the steps above, LinuxCNC does not enable the machine (emergency state remains active). The NVEM board does not seem to start communication with the host, even though the IP is correctly configured and it responds to ping.


---

❓ Questions:

1. Is there any minimum requirement in the .hal or .ini files for LinuxCNC to properly initiate communication with fixed firmware?


2. What else could prevent the machine from exiting emergency, even with the correct fixed .bin?


3. Has anyone successfully used the NVEM V5 with fixed pins in the firmware, without using remora.conf?

Jogging  a joint is not allowed (because it will rack the gantry)

You can jog the Y axis but only after homing is complete.
So if you don't have dual homing switches you need to setup immediate homing

Also unless you have a rotary A axis, there should be no mention of A anywhere
It would be a lot less confusing to refer to the Y Axis as Y and Y1

 

www.linuxcnc.org/iso/linuxcnc_2.9.4-amd64.hybrid.iso
 

Thanks very much Finnengineering.

That's good to hear. I'll have another play with it in Halshow and see if I can set that pin.

Found it...looks like i have the wrong version?

therman@Debian-LinuxCNC:~$ linuxcnc -v
Verbose mode on
RUN_IN_PLACE=no
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/usr/bin
LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/usr/lib/linuxcnc/modules
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/usr/lib/tcltk/linuxcnc/msgs
INIVAR=inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.6
LINUXCNC - 2.9.0~pre1+git20230208.f1270d6ed7


Where can i download the correct version?

Where can i see the Linux Version?


therman@Debian-LinuxCNC:~$ mesaflash --device ethernet --addr 10.10.10.10

ETH device 7I76EU at ip=10.10.10.10

That's very odd

I am assuming this is LinuxCNC 2.9.4?

I just tested 2.9.4 and a 7I76EU an the pin names are all prefixed with hm2_7i76e
as expected

What does

mesaflash --device ethernet --addr 10.10.10.10 

report?