Search Results (Searched for: )
- juergen-home
- juergen-home
12 Aug 2025 07:52
Replied by juergen-home on topic "pwm/dir" (Out1) switches for spindle CCW
"pwm/dir" (Out1) switches for spindle CCW
Category: Basic Configuration
Thanks Peter for coming by. I put your 3 lines in my .hal file but there is an error message:
...
Debug file information:
Note: Using POSIX realtime
./ttm_a.hal:298: parameter or pin 'hm2_6i25.0.gpio.007.is_output' not found
2077
Stopping realtime threads
...
Perhaps this is because gpio.007 is "hm2/hm2_6i25.0: IO Pin 007 (P3-17): PWMGen #0, pin Out1 (Dir or Down) (Output)"
Seems this gpio.007 is bound to "pwm/dir" (Out1) for signaling CCW, what I want to do is to use it as a signal to enable my VFD while CW rotation.
Because I'm low on outputs I want to use this gpio.007 with the relay.
Juergen
...
Debug file information:
Note: Using POSIX realtime
./ttm_a.hal:298: parameter or pin 'hm2_6i25.0.gpio.007.is_output' not found
2077
Stopping realtime threads
...
Perhaps this is because gpio.007 is "hm2/hm2_6i25.0: IO Pin 007 (P3-17): PWMGen #0, pin Out1 (Dir or Down) (Output)"
Seems this gpio.007 is bound to "pwm/dir" (Out1) for signaling CCW, what I want to do is to use it as a signal to enable my VFD while CW rotation.
Because I'm low on outputs I want to use this gpio.007 with the relay.
Juergen
Error report created by /usr/lib/tcltk/linuxcnc/show_errors.tcl:
Print file information:
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.8.4-1-gb7824717b
Machine configuration directory is '/home/cnc/linuxcnc/configs/ttm_a'
Machine configuration file is 'ttm_a.ini'
INIFILE=/home/cnc/linuxcnc/configs/ttm_a/ttm_a.ini
VERSION=1.1
PARAMETER_FILE=linuxcnc.var
TASK=milltask
HALUI=halui
DISPLAY=axis
COORDINATES=XYZ
KINEMATICS=trivkins coordinates=XYZ
Starting LinuxCNC...
Starting LinuxCNC server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting LinuxCNC IO program: io
Starting HAL User Interface program: halui
Found file(REL): ./ttm_a.hal
Shutting down and cleaning up LinuxCNC...
Running HAL shutdown script
hm2: loading Mesa HostMot2 driver version 0.15
hm2_pci: loading Mesa AnyIO HostMot2 driver version 0.7
hm2_pci: discovered 6i25 at 0000:06:00.0
hm2/hm2_6i25.0: Low Level init 0.15
hm2/hm2_6i25.0: Smart Serial Firmware Version 43
hm2/hm2_6i25.0: 34 I/O Pins used:
hm2/hm2_6i25.0: IO Pin 000 (P3-01): PWMGen #0, pin Out0 (PWM or Up) (Output)
hm2/hm2_6i25.0: IO Pin 001 (P3-14): IOPort
hm2/hm2_6i25.0: IO Pin 002 (P3-02): StepGen #0, pin Step (Output)
hm2/hm2_6i25.0: IO Pin 003 (P3-15): IOPort
hm2/hm2_6i25.0: IO Pin 004 (P3-03): StepGen #0, pin Direction (Output)
hm2/hm2_6i25.0: IO Pin 005 (P3-16): IOPort
hm2/hm2_6i25.0: IO Pin 006 (P3-04): StepGen #1, pin Step (Output)
hm2/hm2_6i25.0: IO Pin 007 (P3-17): PWMGen #0, pin Out1 (Dir or Down) (Output)
hm2/hm2_6i25.0: IO Pin 008 (P3-05): StepGen #1, pin Direction (Output)
hm2/hm2_6i25.0: IO Pin 009 (P3-06): StepGen #2, pin Step (Output)
hm2/hm2_6i25.0: IO Pin 010 (P3-07): StepGen #2, pin Direction (Output)
hm2/hm2_6i25.0: IO Pin 011 (P3-08): StepGen #3, pin Step (Output)
hm2/hm2_6i25.0: IO Pin 012 (P3-09): StepGen #3, pin Direction (Output)
hm2/hm2_6i25.0: IO Pin 013 (P3-10): IOPort
hm2/hm2_6i25.0: IO Pin 014 (P3-11): IOPort
hm2/hm2_6i25.0: IO Pin 015 (P3-12): IOPort
hm2/hm2_6i25.0: IO Pin 016 (P3-13): IOPort
hm2/hm2_6i25.0: IO Pin 017 (P2-01): Encoder #0, pin A (Input)
hm2/hm2_6i25.0: IO Pin 018 (P2-14): Encoder #4, pin B (Input)
hm2/hm2_6i25.0: IO Pin 019 (P2-02): Encoder #0, pin B (Input)
hm2/hm2_6i25.0: IO Pin 020 (P2-15): Encoder #4, pin Index (Input)
hm2/hm2_6i25.0: IO Pin 021 (P2-03): Encoder #0, pin Index (Input)
hm2/hm2_6i25.0: IO Pin 022 (P2-16): IOPort
hm2/hm2_6i25.0: IO Pin 023 (P2-04): Encoder #1, pin A (Input)
hm2/hm2_6i25.0: IO Pin 024 (P2-17): IOPort
hm2/hm2_6i25.0: IO Pin 025 (P2-05): Encoder #1, pin B (Input)
hm2/hm2_6i25.0: IO Pin 026 (P2-06): Encoder #1, pin Index (Input)
hm2/hm2_6i25.0: IO Pin 027 (P2-07): Encoder #2, pin A (Input)
hm2/hm2_6i25.0: IO Pin 028 (P2-08): Encoder #2, pin B (Input)
hm2/hm2_6i25.0: IO Pin 029 (P2-09): Encoder #2, pin Index (Input)
hm2/hm2_6i25.0: IO Pin 030 (P2-10): Encoder #3, pin A (Input)
hm2/hm2_6i25.0: IO Pin 031 (P2-11): Encoder #3, pin B (Input)
hm2/hm2_6i25.0: IO Pin 032 (P2-12): Encoder #3, pin Index (Input)
hm2/hm2_6i25.0: IO Pin 033 (P2-13): Encoder #4, pin A (Input)
hm2/hm2_6i25.0: registered
hm2_6i25.0: initialized AnyIO board at 0000:06:00.0
hm2_6i25.0: dropping AnyIO board at 0000:06:00.0
hm2/hm2_6i25.0: unregistered
hm2_pci: driver unloaded
hm2: unloading
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments
Debug file information:
Note: Using POSIX realtime
./ttm_a.hal:298: parameter or pin 'hm2_6i25.0.gpio.007.is_output' not found
2077
Stopping realtime threads
Unloading hal components
RTAPI_PCI: Unmapped 65536 bytes at 0x7f0222141000
Note: Using POSIX realtime
-----------------------------------------------------------------------
Info report created by linuxcnc_info:
The file: /tmp/linuxcnc_info.txt
can be posted to a forum or a web site like:
http://pastebin.com
in order to provide information about the linuxcnc
system and configuration.
Date: Di 12. Aug 09:22:22 CEST 2025
UTC Date: Di 12. Aug 07:22:22 UTC 2025
this program: /usr/bin/linuxcnc_info
uptime: 09:22:22 up 10 min, 1 user, load average: 1,09, 0,87, 0,52
lsb_release -sa: Debian Debian GNU/Linux 10 (buster) 10 buster
which linuxcnc: /usr/bin/linuxcnc
pwd: /home/cnc/linuxcnc/configs/ttm_a
USER: cnc
LOGNAME: cnc
HOME: /home/cnc
EDITOR:
VISUAL:
LANGUAGE:
TERM: dumb
COLORTERM:
DISPLAY: :0.0
DESKTOP: lightdm-xsession
display size: 1920x1080 pixels (508x285 millimeters)
PATH: /usr/bin:/home/cnc/linuxcnc/configs/ttm_a/bin:/usr/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
uname items:
nodename -n: debian
kernel-name -s: Linux
kernel-vers -v: #1 SMP PREEMPT RT Debian 4.19.316-1 (2024-06-25)
machine -m: x86_64
processor -p: unknown
platform -i: unknown
oper system -o: GNU/Linux
/proc items:
cmdline: BOOT_IMAGE=/boot/vmlinuz-4.19.0-27-rt-amd64 root=UUID=9c449597-d44a-4504-9fed-3d2541ad317f ro initrd=/install/initrd.gz quiet
model name: Intel(R) Core(TM) i5-4440 CPU @ 3.10GHz
cores: 4
cpu MHz: 1935.655
parport: 0000-0000 : parport0
serial: 0000-0000 : serial
Versions:
gcc: gcc (Debian 8.3.0-6) 8.3.0
python: Python 2.7.16
git: not_in_PATH
git commit: NA
tcl: 8.6
tk: 8.6
glade: not_in_PATH
glade-gtk2: not_in_PATH
linuxcnc_var all:
LINUXCNCVERSION: 2.8.4-1-gb7824717b
LINUXCNC_AUX_GLADEVCP: /usr/share/linuxcnc/aux_gladevcp
LINUXCNC_AUX_EXAMPLES: /usr/share/linuxcnc/aux_examples
REALTIME: /etc/init.d/realtime
RTS: uspace
HALLIB_DIR: /usr/share/linuxcnc/hallib
dpkg -l '*linuxcnc*':
Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten
| Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/
Halb installiert/Trigger erWartet/Trigger anhängig
|/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht)
||/ Name Version Architektur Beschreibung
+++-===================-====================-============-=====================================================================
un linuxcnc <keine> <keine> (keine Beschreibung vorhanden)
un linuxcnc-dev <keine> <keine> (keine Beschreibung vorhanden)
un linuxcnc-doc <keine> <keine> (keine Beschreibung vorhanden)
ii linuxcnc-doc-en 1:2.8.4.1.gb7824717b all motion controller for CNC machines and robots (English documentation)
ii linuxcnc-doc-es 1:2.8.4.1.gb7824717b all controlador de movimiento para máquinas CNC y robots (Español).
ii linuxcnc-doc-fr 1:2.8.4.1.gb7824717b all motion controller for CNC machines and robots (French documentation)
un linuxcnc-sim <keine> <keine> (keine Beschreibung vorhanden)
un linuxcnc-sim-dev <keine> <keine> (keine Beschreibung vorhanden)
ii linuxcnc-uspace 1:2.8.4.1.gb7824717b amd64 motion controller for CNC machines and robots
ii linuxcnc-uspace-dev 1:2.8.4.1.gb7824717b amd64 PC based motion controller for real-time Linux- jimmyrig
- jimmyrig
12 Aug 2025 07:46 - 12 Aug 2025 07:47
Replied by jimmyrig on topic Mesa 7i76eu gpio pins not working
Mesa 7i76eu gpio pins not working
Category: General LinuxCNC Questions
Had the same issue, need to wire the "orange block" so that your inputs and outputs have power. You should see a yellow light only with only Ethernet or 5v power..... and a red or green light with field power.
I think it's just the bottom one on that orange block that needs 24v and the top one needs ground but that's from memory.... please check the manual
I think it's just the bottom one on that orange block that needs 24v and the top one needs ground but that's from memory.... please check the manual
- LeonDolnicar
- LeonDolnicar
12 Aug 2025 07:41
Mesa 7i76eu gpio pins not working was created by LeonDolnicar
Mesa 7i76eu gpio pins not working
Category: General LinuxCNC Questions
Hello,
I am using Mesa 7i76eu card to operate my 3 axis CNC mill. I connected the stepper motors and they work, I can move them with linuxCNC. Now I tried to connect PNP proximity sensors to use as homing switches, but they are not working. At first I was also getting an error when starting linuxCNC, but i noticed that is because W1 jumper fell out while wiring. I set the W1 jumper back to its original left position but the pins are still not working. I also noticed that i have a CR11 LED light turned on indicating field i/o fault. Does anyone have an idea what could be the problem.
I am using Mesa 7i76eu card to operate my 3 axis CNC mill. I connected the stepper motors and they work, I can move them with linuxCNC. Now I tried to connect PNP proximity sensors to use as homing switches, but they are not working. At first I was also getting an error when starting linuxCNC, but i noticed that is because W1 jumper fell out while wiring. I set the W1 jumper back to its original left position but the pins are still not working. I also noticed that i have a CR11 LED light turned on indicating field i/o fault. Does anyone have an idea what could be the problem.
- Hakan
- Hakan
12 Aug 2025 07:18
Replied by Hakan on topic Debian Trixie upgrade/install to 2.9.4
Debian Trixie upgrade/install to 2.9.4
Category: Installing LinuxCNC
Ended up reinstalling ethercat_dkms and ethercat_master, before that I got errors
of not being able to read PDO at 0x0000 or something. After reinstall that's gone.
Yes, I'm trying to float over the certificate thing without really understanding.
I did some reading on the subject and the lines you have in the sticky file should make secure boot and ethercat modules work together. I'll point to that next time.
of not being able to read PDO at 0x0000 or something. After reinstall that's gone.
Yes, I'm trying to float over the certificate thing without really understanding.
I did some reading on the subject and the lines you have in the sticky file should make secure boot and ethercat modules work together. I'll point to that next time.
- Hakan
- Hakan
12 Aug 2025 06:59
Replied by Hakan on topic Amplifier Fault ECT60 Closed Loop
Amplifier Fault ECT60 Closed Loop
Category: EtherCAT
Sorry, I don't do consulting.
But I'm often here on the forum and, as I do for everyone, I try to help.
Ethercat has its fair share of startup issues and that's what many people need help with. But after the devices are configured and working, it's just regular LinuxCNC, with HAL files, INI files and all that. Now you know something about ethercat, Tommy and can jump in.
But I'm often here on the forum and, as I do for everyone, I try to help.
Ethercat has its fair share of startup issues and that's what many people need help with. But after the devices are configured and working, it's just regular LinuxCNC, with HAL files, INI files and all that. Now you know something about ethercat, Tommy and can jump in.
- Aciera

12 Aug 2025 06:54
Replied by Aciera on topic best practice Benutzervariablen anzeigen und speichern
best practice Benutzervariablen anzeigen und speichern
Category: Deutsch
Mir ist kein Weg bekannt um ausserhalb des Interpreters direkt auf gcode
Parameter zuzugreifen. Ein Auslesen von Paramterwerten ist somit (meines Wissens) nur von innerhalb des GCode Programms möglich.
1. Parameterwert in einen Analog Hal pin schreiben (zB M68 E0 Q#31)
2. Parameterwert mit Gcode logging in eine Datei schreiben
linuxcnc.org/docs/html/gcode/overview.html#gcode:logging
Parameter zuzugreifen. Ein Auslesen von Paramterwerten ist somit (meines Wissens) nur von innerhalb des GCode Programms möglich.
1. Parameterwert in einen Analog Hal pin schreiben (zB M68 E0 Q#31)
2. Parameterwert mit Gcode logging in eine Datei schreiben
(logopen,myparams.txt)
(log,#31, #32, #33)
#31 = 1.23
(log,#31, #32, #33)
#32 = 4.23
(log,#31, #32, #33)
(logclose)linuxcnc.org/docs/html/gcode/overview.html#gcode:logging
Time to create page: 0.376 seconds