Advanced Search

Hi,

Could really use some pointers:

Short version, PCNC 1100-3 PC with PCIe mesa card died, new PC can't fit PCIe mesa card, only card that seems compatible is the Mesa 7i92T (in my case the 7i92TM, yah wrong DB 25 gender, but a gender bender fixed that.)  Issue is when  restore from my tormach supplied PP 2.0.0 thumb drive, that version does not support the T version of mesa cards, but to update to the latest version I need to get to the PP GIU (Or is there 1) a way to upgrade without PP GIU or 2) create a PP full install thumb drive that has a newer version of PP?)  I tried some .ini and .bashrc edits I found to force it into simulation mode, but they are not working.  Granted I had to guess at where the files were located and they did not match the lite description of where to edit so I may have been doing it wrong.  the files I edited with in the ~ directory the .bashrc where i added the PATHPILOT_SIM_MODE=1 (pretty sure this one is right, made it the first line) and the other edits were in the ~/tmc/configs folder in files that were for the 1100-3 with Ethernet - but these I am suspecting have changes or I really did not get what the ask was on what I had to change as none of the lines matched the instructions, so I took my best guess as to what I had to do, regardless it does not let the GIU start.   Any help is greatly appreciated.  PS:  I don't believe the PC is the issue and the card is setup to use 10.10.10.10 and is communicating, there are no other devices on the Ethernet, its a direct link.  thanks, Happy new year

Thanks for these instructions, have made them but PP 2.0.0 does not boot without giving the "No ethernet link detected. check cabling between controller and machine." My original PC for my PCNC 1100-3 died, it used the PCIe mesa card, have switched to a small form factor Intel based PC and imaged the drive with my install/upgrade thumb drive but when I got it Tormach was on PP 2.0.0. With the new Ethernet based MESA 7i92T card I need to update PP before it can work with the newer card, but I can't get it to the PP GUI to do the update. Any ideas how to force it past the above error, note plugging in the card to the Ethernet port (direct) changes the behavior to display a indication that the card FW has been updated then reboots, this keeps happening with no sign of the PP UI. Not sure I am in the right files/folders for the above changes the files I tried modifying are in ~/tmc/configs/ with my selected mill type. the .bashrc file is in ~ directory.

testing in full stream ... its runs at 2ms cycle with profibus master without significant problems ... hardware beckhoff C6930-0060 with native driver at 3.4ghz 


video - 

That issue had been raised before and had been marked as closed as it was an issue with Linuxcnc itself, not with the image. The readme also addressed the issue. Please check the readme, as well as checking both the open and closed issues on GitHub.
As I'm in the process of looking for a new place to live it may be some time before a new image is built.

Was also mentioned here:
github.com/ozzyrob/linuxcnc-rpi-2.9.7-im...ase-12-december-2025

New image releases will also be announced via github. The latest announcement will have links to the latest release.

Possibly missing a first linein the hal file.
Anyway, you must attach your ini and hal file for any meaningful diagnose to the problem.

I've been really curious about EtherCAT and decided to take a deep dive and a bit of risk in ordering a Lichuan CL57E-2A. It's a 2 axis, closed-loop stepper driver: en.xlichuan.com/product-xq/200.html

It took a little while looking through the forum, but once I found the information in this thread , particularly from Robbbbbb (thank you!), I got the drive into an OP state and 1 axis working in LinuxCNC fairly easily. So it was with a lot of expectation that I added the configuration for the 2nd axis, but then got nowhere for days.

Has anyone had success with a drive that has 2 axes?

I run `ethercat pdos` and have created the config .xml file attached. As I said, the first axis works, but the second doesn't get set up correctly, and it isn't controllable from LinuxCNC. Using the show HAL configuration tool, I can see the statusword in LCEC HAL pin shows `0x0000` for the second axis. Reading the value via `ethercat upload -p 0 0x6841 0 -t uint16`, I can see that it's not `0x0000`. So I'm thinking something is wrong with my config file or with the lece driver? Is it normal to have two PDOs in one sync manager?

Many thanks,
David.

 

I have attached the probe settings screenshot, however I found the issue. The .ini file had [VERSA_TOOLSETTER] Z=-2.49, changed it to 0 and it works! 

Thanks for the help! I have two questions though

1. What is the difference between the tool sensor commands (in the offset section) compared to this auto tool length change? Wouldnt have been the same? 

2. The other screenshot "Zoffset" shows a massive Z offset. Not a concern though the tool able takes the correct number 

I guess the answer is here: www.forum.linuxcnc.org/29-forum-announce...nuxcnc-2-9-8-release

Hi All:
Using the RPI 2.9.7 image from the download page
www.linuxcnc.org/iso/image_2025-11-10-ra...7-6-trixie-arm64.zip

With RPI5 using a parallel hat
byte2bot.com/blogs/instructions/setting-...35144898857#comments

I get the following error when launching linuxcnc for my configuration:
hal_gpio.so does not exist on that install. Is it a file I can download or is it compiled for each system by the image?

I have left a message with the developer of the image (ozzyrob) at
github.com/ozzyrob/linuxcnc-rpi-2.9.7-image-issues/issues/5

... but haven't yet heard anything. Is there a less experimental version of Linuxcnc I should be using?

 

if you have installed beckhoff package manager ... there install the drive manager 2 and there will be firmware .. you can upgrade firmware over ethercat and then let us know ...


 

and post outcome here
 

Dear members,

my Leinen FM1 is now running with LinuxCNC on all 4 axes.
I have built a small cubicle containing the required components. I have not modified the original setup at all. The CNC cubicle can be activated by a simple changeover of the original plugs coming from the mill (HONDA MR 50 pin and 20 pin plugs and the 4 Heidenhain plugs) from the original control panel to the CNC cubicle.
The relevant hardware I'm using is
- MESA 7i97T
- 1 Heidenhain EXE with 3 channels from a MAHO mill (1 my resolution)
- 1 Heidenhain EXE 610 for the rotary axis (0,001° resolution)
- 2 Mattke two channel Tach DC motor controller MTRG 25/2D
- 1 Mattke MTRM 061/5 Tach DC motor controller for the spindle motor
- 1 cycloidal transfer 60VAC for the spindle
- 1 cycloidal transformer 2 x 22VAC for the axes motors
- 1 5VDC and 1 12VDC power supply
- 1 All-In-One PC
Only the MESA card is new. All the other other equipment is bought second hand and mostly about 40 years old. But it works !
To be sincere, without help I would not have been able to configure LinuxCNC.on my own. A very kind and knowledgeable member of this forum did this work for me. Thanks a lot to him.
If anybody needs the INI and the HAL files, I would be happy to send a copy.
The following functions are implemented::
- x-, y-, z- and rotary-axis control
- end switches for the 3 linear axes
I have and I need no homing function.
The spindle speed is controlled outside LinuxCNC with an old Beckmann 10-turn potentiometer. I know them from the 80th of the last century, using them in the university labs.
Furthermore I have installed an original old style Waldmann machine light
Best regards
Hartwig

In the end I managed to fix it. HALShow was really helpful, and using a small oscilloscope made it easy to see exactly where the signal chain was stopping.
I’ll leave the relevant HAL and INI sections below in case anyone else needs them.

HAL Part
# ---setup spindle control signals---
setp hm2_[MESA](BOARD).0.pwmgen.pwm_frequency [SPINDLE_0](PWM_FREQUENCY)
setp hm2_[MESA](BOARD).0.pwmgen.00.scale [SPINDLE_0](SCALE)

net spindle-enable spindle.0.forward => hm2_[MESA](BOARD).0.pwmgen.00.enable
net spindle-speed-cmd spindle.0.speed-out => hm2_[MESA](BOARD).0.pwmgen.00.value
net spindle-enable => hm2_7i95.0.ssr.00.out-01

INI Part
[SPINDLE_0]
PWM_FREQUENCY = 2000
P = 0.0
I = 0.0
D = 0.0
FF0 = 1.0
FF1 = 0.0
FF2 = 0.0
BIAS = 0.0
DEADBAND = 0.0
SCALE = 24000
MIN_RPM = 3000

Thanks everyone for the help!

Uii, 60 steps, wo hast du denn den her
Mal davpn abgesehen, ich frei mich immer über bilder eurer konstuktionen.

So, hmm, jaaa, deine rechnung passt, allerdings befürschte ich das LinuxCNC, bzw der PID regler da einfach keinen spielraum hat um irgendwas zu regeln.
Ich werde das morgen mal am simulator ausprobieren.

Kannst amber mal versuchen den Min-Ferror auf z.b. 1.0 zu setzen und den P-Wert vom PID auf 25 oder so, um zu sehen ob es besser wird.
Vielleicht auch mal beim PID die deadband auf 1 setzen.

Aber wo bitte bekommt man einen stepper mit 60 steps auflösung her
kannst du nicht am treiber die microsteps höher stellen ?

Hi everyone,
I’m configuring LinuxCNC with a Mesa 7i95T and I’d like to ask for a quick sanity-check of my .hal and .ini files, I'm new to the subject so just to make sure I didn’t do anything stupid before I move forward.Quick context: with the 7i95T there isn’t a full “wizard” configurator. I generated a base config with PnCconf, then had to manually edit a bunch of things (I/O mapping, firmware for PWM, encoder/MPG, etc.). The machine now works, but I’d really like a second pair of eyes on:

• Mesa pin mapping ↔ LinuxCNC signals (inputs/outputs, enables, polarity)
• thread setup / addf order (servo-thread, base-thread if used)
• common HAL mistakes: duplicated nets, non-existing pins, unconnected signals, wrong inversions
• INI mistakes: JOINT/AXIS settings, limits, SCALE, stepgen/encoder params, homing sequence, etc.

I’m attaching the following:

• machine.ini
• machine.hal
• if needed, I can also post all the other HAL files like postgui.hal etc

If someone can spend a couple minutes to point out anything that looks wrong or risky, I’d really appreciate it.Thanks!