Search Results (Searched for: )
- PCW
28 Dec 2025 15:18
Replied by PCW on topic Bitfile for Mesa 7i96s + 7i85 (+Modbus (PKT-Pin))
Yes, you may need to use pkluart (RX and TX) version 2 if not running the latest LinuxCNC
- manny
28 Dec 2025 13:54
LinuxCNC + Mesa 7i43 – Axis A stepper (stepgen), error was created by manny
Hello,
I am using LinuxCNC with a Mesa 7i43 card.
Axes X, Y and Z are working correctly.
I need help with configuring Axis A (4th axis),
which I use as an auxiliary axis and want to control
with a stepper motor using STEP/DIR signals.
Hardware:
- LinuxCNC
- Mesa 7i43
- Stepper driver – blue digital stepper driver, Leadshine DM542 / DM556 type
(or compatible clone) with PUL+, PUL-, DIR+, DIR-, ENA+, ENA- inputs
- 2-phase stepper motor
Stepper driver wiring:
- PUL+ -> Mesa P3 pin 25
- PUL- -> Mesa P3 pin 26
- DIR+ -> Mesa P3 pin 27
- DIR- -> Mesa P3 pin 28
- ENA+ -> Mesa P3 pin 29
- ENA- -> Mesa P3 pin 30
The driver is configured by DIP switches for microstepping
(e.g. 3200 pulses per revolution).
Axis A is configured in the HAL file as a stepper axis
using hm2 stepgen (stepgen.00).
I need advice on how to correctly modify the HAL file
so that Axis A works properly as a stepper axis
with the Mesa 7i43.
I am attaching my complete HAL file.
Thank you.
#*******************
# AXIS A
#*******************
setp pid.a.Pgain [AXIS_3]P
setp pid.a.Igain [AXIS_3]I
setp pid.a.Dgain [AXIS_3]D
setp pid.a.bias [AXIS_3]BIAS
setp pid.a.FF0 [AXIS_3]FF0
setp pid.a.FF1 [AXIS_3]FF1
setp pid.a.FF2 [AXIS_3]FF2
setp pid.a.deadband [AXIS_3]DEADBAND
setp pid.a.maxoutput [AXIS_3]MAX_OUTPUT
setp pid.a.error-previous-target true
setp pid.a.maxerror .0005
net a-index-enable <=> pid.a.index-enable
net a-enable => pid.a.enable
net a-pos-cmd => pid.a.command
net a-vel-cmd => pid.a.command-deriv
net a-pos-fb => pid.a.feedback
net a-output => pid.a.output
# Step Gen signals/setup
setp hm2_7i43.0.stepgen.00.dirsetup [AXIS_3]DIRSETUP
setp hm2_7i43.0.stepgen.00.dirhold [AXIS_3]DIRHOLD
setp hm2_7i43.0.stepgen.00.steplen [AXIS_3]STEPLEN
setp hm2_7i43.0.stepgen.00.stepspace [AXIS_3]STEPSPACE
setp hm2_7i43.0.stepgen.00.position-scale [AXIS_3]STEP_SCALE
setp hm2_7i43.0.stepgen.00.step_type 0
setp hm2_7i43.0.stepgen.00.control-type 1
setp hm2_7i43.0.stepgen.00.maxaccel [AXIS_3]STEPGEN_MAXACCEL
setp hm2_7i43.0.stepgen.00.maxvel [AXIS_3]STEPGEN_MAXVEL
# ---closedloop stepper signals---
net a-pos-cmd <= axis.3.motor-pos-cmd
net a-vel-cmd <= axis.3.joint-vel-cmd
net a-output => hm2_7i43.0.stepgen.00.velocity-cmd
net a-pos-fb <= hm2_7i43.0.stepgen.00.position-fb
net a-pos-fb => axis.3.motor-pos-fb
net a-enable <= axis.3.amp-enable-out
net a-enable => hm2_7i43.0.stepgen.00.enable
# ---setup home / limit switch signals---
net a-home-sw => axis.3.home-sw-in
net a-neg-limit => axis.3.neg-lim-sw-in
net a-pos-limit => axis.3.pos-lim-sw-in
I am using LinuxCNC with a Mesa 7i43 card.
Axes X, Y and Z are working correctly.
I need help with configuring Axis A (4th axis),
which I use as an auxiliary axis and want to control
with a stepper motor using STEP/DIR signals.
Hardware:
- LinuxCNC
- Mesa 7i43
- Stepper driver – blue digital stepper driver, Leadshine DM542 / DM556 type
(or compatible clone) with PUL+, PUL-, DIR+, DIR-, ENA+, ENA- inputs
- 2-phase stepper motor
Stepper driver wiring:
- PUL+ -> Mesa P3 pin 25
- PUL- -> Mesa P3 pin 26
- DIR+ -> Mesa P3 pin 27
- DIR- -> Mesa P3 pin 28
- ENA+ -> Mesa P3 pin 29
- ENA- -> Mesa P3 pin 30
The driver is configured by DIP switches for microstepping
(e.g. 3200 pulses per revolution).
Axis A is configured in the HAL file as a stepper axis
using hm2 stepgen (stepgen.00).
I need advice on how to correctly modify the HAL file
so that Axis A works properly as a stepper axis
with the Mesa 7i43.
I am attaching my complete HAL file.
Thank you.
#*******************
# AXIS A
#*******************
setp pid.a.Pgain [AXIS_3]P
setp pid.a.Igain [AXIS_3]I
setp pid.a.Dgain [AXIS_3]D
setp pid.a.bias [AXIS_3]BIAS
setp pid.a.FF0 [AXIS_3]FF0
setp pid.a.FF1 [AXIS_3]FF1
setp pid.a.FF2 [AXIS_3]FF2
setp pid.a.deadband [AXIS_3]DEADBAND
setp pid.a.maxoutput [AXIS_3]MAX_OUTPUT
setp pid.a.error-previous-target true
setp pid.a.maxerror .0005
net a-index-enable <=> pid.a.index-enable
net a-enable => pid.a.enable
net a-pos-cmd => pid.a.command
net a-vel-cmd => pid.a.command-deriv
net a-pos-fb => pid.a.feedback
net a-output => pid.a.output
# Step Gen signals/setup
setp hm2_7i43.0.stepgen.00.dirsetup [AXIS_3]DIRSETUP
setp hm2_7i43.0.stepgen.00.dirhold [AXIS_3]DIRHOLD
setp hm2_7i43.0.stepgen.00.steplen [AXIS_3]STEPLEN
setp hm2_7i43.0.stepgen.00.stepspace [AXIS_3]STEPSPACE
setp hm2_7i43.0.stepgen.00.position-scale [AXIS_3]STEP_SCALE
setp hm2_7i43.0.stepgen.00.step_type 0
setp hm2_7i43.0.stepgen.00.control-type 1
setp hm2_7i43.0.stepgen.00.maxaccel [AXIS_3]STEPGEN_MAXACCEL
setp hm2_7i43.0.stepgen.00.maxvel [AXIS_3]STEPGEN_MAXVEL
# ---closedloop stepper signals---
net a-pos-cmd <= axis.3.motor-pos-cmd
net a-vel-cmd <= axis.3.joint-vel-cmd
net a-output => hm2_7i43.0.stepgen.00.velocity-cmd
net a-pos-fb <= hm2_7i43.0.stepgen.00.position-fb
net a-pos-fb => axis.3.motor-pos-fb
net a-enable <= axis.3.amp-enable-out
net a-enable => hm2_7i43.0.stepgen.00.enable
# ---setup home / limit switch signals---
net a-home-sw => axis.3.home-sw-in
net a-neg-limit => axis.3.neg-lim-sw-in
net a-pos-limit => axis.3.pos-lim-sw-in
- tommylight
-

28 Dec 2025 12:07
Replied by tommylight on topic No speed control on xhc-wb04b-6 pendant on 3 axis router
Usually due to naming errors, like spindle.enable should be spindle.0.enable, axis should be joints, etc.
- unknown
28 Dec 2025 10:54 - 28 Dec 2025 11:01
Replied by unknown on topic How to install simplescreenrecorder on old version of Debian?
Dependencies will be a nightmare, libqt5 will be a problem as it would appear it wasn't packaged for Wheezy, if in fact Wheezy is the Debian version Old Mate is running.
- TripleM
28 Dec 2025 09:31
Replied by TripleM on topic Bitfile for Mesa 7i96s + 7i85 (+Modbus (PKT-Pin))
I tested the bit file...
The good news: nothing is damaged. But I got this error
Should I use version 2?
I change the Version by editing x"03"--> x"02"?:
The good news: nothing is damaged. But I got this error
Code:
Debug file information:
Note: Using POSIX realtime
hm2/hm2_7i96s.0: Unsupported or inconsistent PktUART TX module (version 3)not loading driver
hm2/hm2_7i96s.0: failed to parse Module Descriptor 12
hm2_eth: rtapi_app_main: Invalid argument (-22)
Should I use version 2?
I change the Version by editing x"03"--> x"02"?:
Code:
(PktUARTTTag, x"03", ClockLowTag, x"01", PktUARTTDataAddr&PadT, PktUARTTNumRegs, x"00", PktUARTTMPBitMask),
(PktUARTRTag, x"03", ClockLowTag, x"01", PktUARTRDataAddr&PadT, PktUARTRNumRegs, x"00", PktUARTRMPBitMask),
Code:
Configuration Name: HOSTMOT2
General configuration information:
BoardName : MESA7I96
FPGA Size: 20 KGates
FPGA Pins: 256
Number of IO Ports: 3
Width of one I/O port: 17
Clock Low frequency: 100.0000 MHz
Clock High frequency: 160.0000 MHz
IDROM Type: 3
Instance Stride 0: 4
Instance Stride 1: 64
Register Stride 0: 256
Register Stride 1: 256
Modules in configuration:
Module: DPLL
There are 1 of DPLL in configuration
Version: 0
Registers: 7
BaseAddress: 7000
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Module: WatchDog
There are 1 of WatchDog in configuration
Version: 0
Registers: 3
BaseAddress: 0C00
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Module: IOPort
There are 3 of IOPort in configuration
Version: 0
Registers: 5
BaseAddress: 1000
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Module: OutM
There are 1 of OutM in configuration
Version: 0
Registers: 1
BaseAddress: B000
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Module: PWM
There are 1 of PWM in configuration
Version: 0
Registers: 5
BaseAddress: 4100
ClockFrequency: 160.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Module: StepGen
There are 5 of StepGen in configuration
Version: 2
Registers: 10
BaseAddress: 2000
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Module: MuxedQCount
There are 6 of MuxedQCount in configuration
Version: 4
Registers: 5
BaseAddress: 3600
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Module: MuxedQCountSel
There are 1 of MuxedQCountSel in configuration
Version: 0
Registers: 0
BaseAddress: 0000
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Module: SSerial
There are 1 of SSerial in configuration
Version: 0
Registers: 6
BaseAddress: 5B00
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 64 bytes
Module: SSR
There are 1 of SSR in configuration
Version: 0
Registers: 2
BaseAddress: 7D00
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Module: InM
There are 1 of InM in configuration
Version: 0
Registers: 5
BaseAddress: 8500
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Module: LED
There are 1 of LED in configuration
Version: 0
Registers: 1
BaseAddress: 0200
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Module: PktUARTTX
There are 1 of PktUARTTX in configuration
Version: 3
Registers: 4
BaseAddress: 6100
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Module: PktUARTRX
There are 1 of PktUARTRX in configuration
Version: 3
Registers: 4
BaseAddress: 6500
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Configuration pin-out:
IO Connections for TB3 -> 7I96_0
Pin# I/O Pri. func Sec. func Chan Sec. Pin func Sec. Pin Dir
TB3-1 0 IOPort InM 0 Input0_EncA0 (In)
TB3-2 1 IOPort InM 0 Input1_EncB0 (In)
TB3-3 2 IOPort InM 0 Input2_EncA1 (In)
TB3-4 3 IOPort InM 0 Input3_EncB1 (In)
TB3-5 4 IOPort InM 0 Input4_EncA2 (In)
TB3-6 5 IOPort InM 0 Input5_EncB2 (In)
TB3-7 6 IOPort InM 0 Input6_EncA3 (In)
TB3-8 7 IOPort InM 0 Input7_EncB3 (In)
TB3-9 8 IOPort InM 0 Input8 (In)
TB3-10 9 IOPort InM 0 Input9 (In)
TB3-11 10 IOPort InM 0 Input10 (In)
TB3-13,14 11 IOPort SSR 0 Out-00 (Out)
TB3-15,16 12 IOPort SSR 0 Out-01 (Out)
TB3-17,18 13 IOPort SSR 0 Out-02 (Out)
TB3-19,20 14 IOPort SSR 0 Out-03 (Out)
TB3-21,22 15 IOPort OutM 0 Output4 (Out)
TB3-23,24 16 IOPort OutM 0 Output5 (Out)
IO Connections for TB1/TB2 -> 7I96_1
Pin# I/O Pri. func Sec. func Chan Sec. Pin func Sec. Pin Dir
TB1-2,3 17 IOPort StepGen 0 Step/Table1 (Out)
TB1-4,5 18 IOPort StepGen 0 Dir/Table2 (Out)
TB1-8,9 19 IOPort StepGen 1 Step/Table1 (Out)
TB1-10,11 20 IOPort StepGen 1 Dir/Table2 (Out)
TB1-14,15 21 IOPort StepGen 2 Step/Table1 (Out)
TB1-16,17 22 IOPort StepGen 2 Dir/Table2 (Out)
TB1-20,21 23 IOPort StepGen 3 Step/Table1 (Out)
TB1-22,23 24 IOPort StepGen 3 Dir/Table2 (Out)
TB2-2,3 25 IOPort StepGen 4 Step/Table1 (Out)
TB2-4,5 26 IOPort StepGen 4 Dir/Table2 (Out)
TB2-7,8 27 IOPort MuxedQCount 2 MuxQ-A (In)
TB2-10,11 28 IOPort MuxedQCount 2 MuxQ-B (In)
TB2-13,14 29 IOPort MuxedQCount 2 MuxQ-IDX (In)
TB2-16,17 30 IOPort PktUARTRX 0 RXData (In)
TB2-18,19 31 IOPort PktUARTTX 0 TXData (Out)
Internal-TXEn 32 IOPort PktUARTTX 0 TXEna (Out)
Internal 33 IOPort SSR 0 AC Ref (Out)
IO Connections for P1 -> 7I96_2
Pin# I/O Pri. func Sec. func Chan Sec. Pin func Sec. Pin Dir
P1-01/DB25-01 34 IOPort SSerial 0 RXData4 (In)
P1-02/DB25-14 35 IOPort SSerial 0 TXData4 (Out)
P1-03/DB25-02 36 IOPort SSerial 0 RXData3 (In)
P1-04/DB25-15 37 IOPort SSerial 0 TXData3 (Out)
P1-05/DB25-03 38 IOPort SSerial 0 RXData2 (In)
P1-06/DB25-16 39 IOPort SSerial 0 TXData2 (Out)
P1-07/DB25-04 40 IOPort SSerial 0 RXData1 (In)
P1-08/DB25-17 41 IOPort SSerial 0 TXData1 (Out)
P1-09/DB25-05 42 IOPort SSerial 0 RXData0 (In)
P1-11/DB25-06 43 IOPort SSerial 0 TXData0 (Out)
P1-13/DB25-07 44 IOPort MuxedQCountSel 0 MuxSel0 (Out)
P1-15/DB25-08 45 IOPort MuxedQCount 0 MuxQ-A (In)
P1-17/DB25-09 46 IOPort MuxedQCount 0 MuxQ-B (In)
P1-19/DB25-10 47 IOPort MuxedQCount 0 MuxQ-IDX (In)
P1-21/DB25-11 48 IOPort MuxedQCount 1 MuxQ-A (In)
P1-23/DB25-12 49 IOPort MuxedQCount 1 MuxQ-B (In)
P1-25/DB25-13 50 IOPort MuxedQCount 1 MuxQ-IDX (In)
- timo
28 Dec 2025 08:51 - 28 Dec 2025 09:01
Replied by timo on topic CNC camshaft grinder DIY project
I am super curious about that.
You might consider a more narrow grinding wheel. Then you can traverse the x-Axis. I think this might improve surface finish.
I also would add a tailstock support on the end of the cam shaft. It will improve things, worth the effort.
Edit: I would first try to get x-y-z and rotation running. Then try some simple cylindrical grinding to get a feel for the machine and surface finishes.
Please keep reporting how things go.
You might consider a more narrow grinding wheel. Then you can traverse the x-Axis. I think this might improve surface finish.
I also would add a tailstock support on the end of the cam shaft. It will improve things, worth the effort.
Edit: I would first try to get x-y-z and rotation running. Then try some simple cylindrical grinding to get a feel for the machine and surface finishes.
Please keep reporting how things go.
- jameslc15
28 Dec 2025 06:36 - 28 Dec 2025 06:37
Replied by jameslc15 on topic No speed control on xhc-wb04b-6 pendant on 3 axis router
Hi Tommy
Thank you for the heads up, I did some reading prior to get the vfd signal going and did hear to other peoples warnings on this forum so I've got an abs component running successfully. The issue is the pendant won't send rpm signal to analogue output 5 were as axis will ?
Thank you for the heads up, I did some reading prior to get the vfd signal going and did hear to other peoples warnings on this forum so I've got an abs component running successfully. The issue is the pendant won't send rpm signal to analogue output 5 were as axis will ?
- grandixximo
-

28 Dec 2025 06:23
Replied by grandixximo on topic How to fix "Queue is not empty after probing"
could you run
latency-histogram
instead of latency-test?
I think you might be onto something, I use a custom version with probe tripped during non-probe move disabled, and I never see queue error...
latency-histogram
instead of latency-test?
I think you might be onto something, I use a custom version with probe tripped during non-probe move disabled, and I never see queue error...
- rodw
-

28 Dec 2025 05:45
Replied by rodw on topic Freelancer wanted to get tool sensor working (software)
My email address is on my YouTube channel
www.youtube.com/@MrRodW
Qtdragon and probebasic assume you have repeatable tooling. If you don't, I would recommend investing in Tormach TTS collets, their marble plate and a manual tool height measurer. Measure your 3D probe and your tools and record the settings in the tool table. Probe the material height with the 3D probe and the tool changing routine will do what you want to do. (ask you to insert a premeasured tool) This is far the best way. Works perfectly with QT dragon
Qtdragon and probebasic assume you have repeatable tooling. If you don't, I would recommend investing in Tormach TTS collets, their marble plate and a manual tool height measurer. Measure your 3D probe and your tools and record the settings in the tool table. Probe the material height with the 3D probe and the tool changing routine will do what you want to do. (ask you to insert a premeasured tool) This is far the best way. Works perfectly with QT dragon
- rodw
-

28 Dec 2025 05:35
@unknown, Sid or more correctly unstable branch of Debian has the latest version of 2.9 (eg 2.9.7) while the release version is a couple of versions behind due to Debian's lockdown policy. Using APT pinning allows you to get linuxcnc (and possibly simplescreenrecorder) from Sid/unstable as I outline in this video
IN fact a variant of this could be used by the OP to get simplescreenrecorder from unstable (or Trixie)
Replied by rodw on topic How to install simplescreenrecorder on old version of Debian?
Becasue you are using an old and unsupported version of Debian.Why it is so hard to install a simple program on Linux, which I have installed easily on two other flavours of linux.?
@unknown, Sid or more correctly unstable branch of Debian has the latest version of 2.9 (eg 2.9.7) while the release version is a couple of versions behind due to Debian's lockdown policy. Using APT pinning allows you to get linuxcnc (and possibly simplescreenrecorder) from Sid/unstable as I outline in this video
IN fact a variant of this could be used by the OP to get simplescreenrecorder from unstable (or Trixie)
- Thllll
28 Dec 2025 02:07
Freelancer wanted to get tool sensor working (software) was created by Thllll
I am looking for a freelancer to remote into my system and help me get tool sensor working in either probe basic or dragon QT.
The mill works right now with Dragon QT, able to home, jog, run g-code, even 3d probe. I am giving up though on trying to get this tool sensor to work, spent way to much time trying to get the right ini setting or something. Unable to find any manauls, guides, or anything to set this up in software. The tool sensor is a that standard orange button one from amazon. Its wired in, it works, the software just doesnt want to work.
What happens is when I attempt to use the dragon qt tool sensor it goes to the postion, probes, then sets the tool offset to 9999999. The other "buttons" for setting the tool length just dont work at all, does not press or allow me to press.
The objective is when a tool changed (manually for now) it will move to the tool sensor location, probe, set the tool length, then back to work.
Name your price, I just want it to work.
The mill works right now with Dragon QT, able to home, jog, run g-code, even 3d probe. I am giving up though on trying to get this tool sensor to work, spent way to much time trying to get the right ini setting or something. Unable to find any manauls, guides, or anything to set this up in software. The tool sensor is a that standard orange button one from amazon. Its wired in, it works, the software just doesnt want to work.
What happens is when I attempt to use the dragon qt tool sensor it goes to the postion, probes, then sets the tool offset to 9999999. The other "buttons" for setting the tool length just dont work at all, does not press or allow me to press.
The objective is when a tool changed (manually for now) it will move to the tool sensor location, probe, set the tool length, then back to work.
Name your price, I just want it to work.
- rhscdn
28 Dec 2025 01:35
Replied by rhscdn on topic WHB04B-6 - Change display units and step sizes
Just wondering if there are any other alternatives for swapping the pendant units when a G20/G21 command is given? I frequently run jobs in metric/imperial units and keeping separate machine definitions seems like an inelegant solution. As described by the OP, the display units are correctly updated but not the pendant.
- Thllll
28 Dec 2025 00:54 - 28 Dec 2025 01:51
QT Dragon Unable to Set Tool Height was created by Thllll
The buttons on the probing page for setting the tool height, I am unable to click on those. Ever other button works. Bottom two buttons
- unknown
28 Dec 2025 00:05
Replied by unknown on topic CNC camshaft grinder DIY project
Change the couplers between the lead screw and stepper motor. They can wind under load and tear themselves apart.
Looks good so far.
Looks good so far.
- unknown
27 Dec 2025 23:03
Replied by unknown on topic How to install simplescreenrecorder on old version of Debian?
What exact version of Debian are you using ?
When you do an apt update it will list the repos and the version, wheezy or bullseye or whatever.
If it's bullseye or up it's available in the repos, if not you may have to install from source, which brings along a whole manner of other issues. And to make whatters worse there does appear to be some issues with wheezy.
From my understanding Sid is the "unstable"branch, so I doubt that anything from Sid would help.
When you do an apt update it will list the repos and the version, wheezy or bullseye or whatever.
If it's bullseye or up it's available in the repos, if not you may have to install from source, which brings along a whole manner of other issues. And to make whatters worse there does appear to be some issues with wheezy.
From my understanding Sid is the "unstable"branch, so I doubt that anything from Sid would help.
Time to create page: 0.548 seconds