Advanced Search

Try to change both the joint and the axis to the same sign:

net jog.0.cont-minus vc-p1as.jog.0.minus => halui.axis.x.plus halui.joint.0.plus 
net jog.0.cont-plus vc-p1as.jog.0.plus => halui.axis.x.minus halui.joint.0.minus

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?

 

So I found a 7i77 on ebay. Put it in and all is good. I then tried qtplasmac and converted the old file to qtplasmac but no luck enabling the machine ! I did set the estop button to mode 2 but estop does not move and power button does not move. Same ini file settings work fine in linuxcnc axis mode. I have a physical estop by the way.

I did a complete uninstall and reinstall of LinuxCNC. After I went through the wizard and selected 7i76e, I ran LinuxCNC again and i got this error message;

./PM833TV.hal:10: parameter or pin 'hm2_7i76e.0.watchdog.timeout_ns' not found
Shutting down and cleaning up LinuxCNC...

The only way to get rid of this error is to change 7i76e back to 7i76 in the Hal and Ini files.  It doesn't like any references to 7i76e.

Is this the source of the issues?

Attaching my current Hal and Ini files.

My Router has a motor on each side of the Y axis running a 16mm ball screw fixed to each side of the gantry (Motors Y and A). The motors will always be required to jog and home together in synchronicity. If I try to home or jog either of them, the gantry will rack. When I get an error for trying to jog either axis it says : " Cannot jog joint because home sequence is synchronized". Is there a way to jog Synchronized? Is that a setting in my step config I have overlooked? Should I be doing an XYZA type of step config vs, the XYZ step config choice? Thanks again for your help and support. I am going to dig into the documentation further.

 

OK that's not going to work as most of the pin names are wrong.

I would suggest using pncconf (choosing 7I76e) and starting over making a new configuration.
(7I76E hal/ini configurations are identical to 7I76EU hal/ini configuration)

pncconfs default values are correct for most things 

Do not use AI for this as its just a huge time sink

 

I understand the personal choice of RJ45 over the M23 connector. That's also why my design had a RJ45 connector included as a secondary input from the very beginning. My PCB supports a standard 2.54 mm 2x5 pin header or a sensor input via RJ45. The pin header is meant to be used with the M23 connectors shown in my last post.
You can get these M23 connectors really cheap on AliExpress - i got mine here for 7 $ each: de.aliexpress.com/item/1005006649703485.html)

I'm writing one more exam next week, after that's done I'll order the first batch of PCBs. My primary goal was to be able to use any kind of encoder signal with future glas scales. At the moment i could use either a glas scale via 1V, 11µA or TTL, with the latter i wouldn't need the interpolator/converter board. I'll keep you posted

current Hal and Ini files attached.  i attempted to replace 7i76 with 7i76e or 7i76eu but it didn't like that either so i've kept everything as is.
Thanks
 

 I bought and received the same type of pendant just a couple of days ago. And I saw the same issue. It appears that the machine-is-on pin needs to be true for XHC-WHB04B-6 to change the counts. And you also need to press the Step button first, as opposed to "Continuous".

I don't remember the exact pin name right now, maybe just whb.machine-is-on, or whb.halui.machine-is-on. You need to set that to true for the counts to actually count (based on my very limited troubleshooting).