Quick sanity-check

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!

With linuxcnc mapping and io mistakes I can't tell cause it's machine dependent. A quick glance didn't pop up anything crazy.

The middle two bullet points usually work or don't. I wouldnt run the estop that way but if it works.....run it.

In this world if it works reliability and it's fast enough just let it rip.


The only thing I would recommend is to do a latency-histogram and see what your latency is. This allows for days running without issues vs hours (or min) (Applications-linuxcnc-latency histogram) If it's below 100 let it ride, below 150 prob fine might tweak a few settings, above that would tune things to make it more reliable..... Otherwise it'll studder/glitch which can cause the UI to drop out.

Let's use know and I can help tune

Thanks a lot for your reply. I ran the latency test at the beginning of this project. At first I had some issues because of the drivers (realtek 8168), and sometimes it would stop with a “Finished reading” error. After a bit of trial and error I changed the drivers as suggested in some threads, and now it runs fine: no packet loss, and both average and maximum latency stay below 70 µs, so I think I’m good.

Should be good! Run it!