1. Forum
  3. Search

Advanced Search

Search Results (Searched for: )

  • freylax
  • freylax
05 Jan 2026 13:11
Replied by freylax on topic LinuxCNC-RIO - RealtimeIO for LinuxCNC based on FPGA (ICE40 / ECP5)

LinuxCNC-RIO - RealtimeIO for LinuxCNC based on FPGA (ICE40 / ECP5)

Category: Computers and Hardware

Es ist gar nicht so einfach Bilder hier hochzuladen, ich habe es jedenfalls nicht geschafft (waren auh nicht zu gross).
Ich habe die Bilder unter github.com/freylax/riocfg/img eingestellt. Es ist ein alter selbstbau Plotter aus DDR Zeiten den ich als CNC Testobjekt verwenden moechte bevor ich mich an die richtige Maschine bei meinem Freund ranwage.

Raspberry PI5, Olimex ICE40 EVB, Adapter und CNC Breakout Board, Stepper Driver.

Ich kann die Mikrosteps einstellen, allerdings scheint das nicht ganz zum Erfolg zu fuehren. In der rio-test app kann ich den 
Motor schrittweise steuern, das klappt. Aber wenn ich in der axis app Manuell zb 5mm anfahre und auch eine geringe Geschwindigkeit einstelle, dann vibriert der Motor nur und es werden  keine richtigen Schritte daraus. Was mach rio-test anders?
Ich studiere auch den Code um das zu verstehen.

liebe Gruesse,
Robert 
  • grandixximo
  • grandixximo's Avatar
05 Jan 2026 12:46 - 05 Jan 2026 14:12
Replied by grandixximo on topic LinuxCNC S-Curve Accelerations

LinuxCNC S-Curve Accelerations

Category: General LinuxCNC Questions

HOME with index should be available, nothing about homing should have changed other than the homing movements being now jerk controlled, but I'll double check on my end, you still have to enable

HOME_USE_INDEX = YES

In the ini file for each joint you want to home using index

Edit:

Yeah, triple checked, homing index should work as expected, just has to be set proper, mind that machine movements will be effected by the s-curve even while homing, if you do not want that, you can link all joint.N.homing pins with or2, then to a mux2, and then to the ini.traj_planner_type pin in hal, so when you home you can have planner 0, otherwise planner 1, I originally had an INI flag to disable s-curve while homing, if you guys think is necessary I'll add it back, but I ended up not liking the machine shaking up only when homing, I want it always to be smooth now, I'd rather readjust the homing vel to compensate for the longer but smoother movements.
  • endian
  • endian's Avatar
05 Jan 2026 12:29
Replied by endian on topic LinuxCNC S-Curve Accelerations

LinuxCNC S-Curve Accelerations

Category: General LinuxCNC Questions

is homing at joint.0.index_enable avaible?

I can not home my profibus sstuff it looks like index_enable is still down .. 

I have had to uuse the NO_FORCE_HOMING = 1

thanks
  • Bendandsend
  • Bendandsend
05 Jan 2026 10:11
Replied by Bendandsend on topic MESA 7i76eu Firmware

MESA 7i76eu Firmware

Category: Driver Boards

Hey Tommylight — thanks for the reply just to close the loop on that earlier issue

I did get past the firmware/install side in the end. After a few messy attempts, I wiped everything and went with a fresh Debian 12 install, then installed LinuxCNC separately (rather than relying on bundled firmware paths). That got the 7i76EU fully detected, firmware loaded cleanly, and all stepgens running perfectly.

Where I’m stuck now is further downstream: the limit/prox inputs. The board, smart-serial, and motion side are all behaving exactly as expected, but the GPIO inputs appear frozen and don’t update in HAL even when shorted directly to GND.

So the original “missing firmware” problem is solved — this is a new issue on the input side, which is what I’m trying to chase down now.

I created a fresh topic on it to try and nail it down as its hopefully my final port of call for a while.
  • Bendandsend
  • Bendandsend
05 Jan 2026 10:00 - 05 Jan 2026 10:05
7i76EU GPIO inputs completely frozen - not updating in real-time was created by Bendandsend

7i76EU GPIO inputs completely frozen - not updating in real-time

Category: Driver Boards

Summary (TL;DR)I have a Mesa 7i76EU on LinuxCNC where everything works except the GPIO inputs.
The board is fully detected, stepgens and smart-serial work perfectly, but all 32 inputs are frozen and never change state — even when shorted directly to GND.System
  • Mesa 7i76EU (Ethernet, 192.168.1.121)
  • Debian 12 (Bookworm)
  • LinuxCNC 2.9.8
  • RT kernel:
    6.12.57+deb13-rt-amd64
  • WECON VD2 servos (X/Y/Z)
  • NPN 3-wire proximity switches (brown +24V, blue GND, black signal)
What Works (100% solid)
  • Mesa discovered every startup
    hm2_eth: discovered 7I76EU
  • Board pings reliably
  • Smart-serial working (FW v43)
  • All stepgens work flawlessly (axes move correctly)
  • E-stop and brake control functional
  • No timing issues (
    SERVO_PERIOD = 1000000
    )
  • halcmd
    shows all inputs
    input-00
    through
    input-31
  • No errors in logs, dmesg, or startup
The Actual ProblemALL GPIO inputs are frozen.Input values never change in HAL, even when:
  • Triggering physical limit switches (LEDs light correctly)
  • Shorting input pins directly to GND
  • Switching between
    input-XX
    and
    input-XX-not
  • Power cycling the Mesa
  • Restarting LinuxCNC
This applies to all 32 inputs, not just the ones in use.What I’ve Already Ruled Out
  • Wiring verified multiple times
  • Bypassed switches entirely (direct GND test)
  • Tested raw vs inverted inputs
  • Verified HAL nets (no duplicates or syntax issues)
  • Confirmed good network latency
  • Smart-serial confirmed via
    mesaflash --sserial
  • Inputs monitored live with
    watch halcmd show pin
    — completely static
Example output (never changes):
 
hm2_7i76e.0.7i76.0.0.input-08 FALSE hm2_7i76e.0.7i76.0.0.input-08-not TRUE
The TRUE/FALSE pattern looks random and does not correlate to real input state.Why This Feels Strange
  • Stepgens work → Mesa comms are good
  • Smart-serial works → daughter card is talking
  • But GPIO inputs behave as if they’re not being refreshed at all
Almost feels like the input register isn’t being updated or latched.Questions
  • Is there any known 7i76EU case where outputs work but inputs don’t update?
  • Anything firmware-related that can cause frozen inputs?
  • Any HAL / driver parameter that explicitly enables input scanning?
  • Worth reflashing the Mesa firmware?
I have PNP switches on order, but since even direct GND shorting doesn’t change inputs, I don’t think this is a sensor-type issue.Attachments (if needed) 
  • mesa_debug.txt
  • mesa_hal_config.txt
  • mesa_ini_config.txt
  • Hakan
  • Hakan
05 Jan 2026 09:33
Replied by Hakan on topic Network Interface Card Recommendation

Network Interface Card Recommendation

Category: EtherCAT

I wonder if TSN works. At least without modifications.
Do you have any real-world experience with that?

In the  flyer I read that while the master can be unaffected, at some point the slave needs to support TSN either directly or via a TSN switch in front of it.

The i210 is an excellent choice, albeit a bit old now. I have good luck with the i217 and also with the latest dirt-cheap i226-v adapters. Older adapters use the igb driver, newer use the igc driver, with some different options and defaults.
  • Ferra
  • Ferra
05 Jan 2026 09:03
Replied by Ferra on topic Quick sanity-check

Quick sanity-check

Category: PnCConf Wizard

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.
  • rodw
  • rodw's Avatar
05 Jan 2026 07:13
Replied by rodw on topic LinuxCNC 2.9.8 Image with Debian Trixie

LinuxCNC 2.9.8 Image with Debian Trixie

Category: Installing LinuxCNC

Also note that there is no /etc/apt/sources.list.d/debian.sources in my Debian 13 after doing a full upgrade.

JT

yes the old format is retained on a full upgrade from Bookworm but it will nag you on an apt update to run sudo apt modernize-sources if I got the spelling right...

Debian says the old format will be removed in time.
  • rodw
  • rodw's Avatar
05 Jan 2026 07:08
Replied by rodw on topic New member from Germany - CNC retrofit of a Leinen FM1

New member from Germany - CNC retrofit of a Leinen FM1

Category: General LinuxCNC Questions

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

You should be able to use your existing end switches as home switches and limit switches. It is so much easier if set up completely. Just make sure you have a home_offset to move the axis away from the limit switch (even 0.5mm is enough, sometimes less). Otherwise the limit switch will trigger as homing completes.
  • grandixximo
  • grandixximo's Avatar
05 Jan 2026 06:50 - 05 Jan 2026 09:44
Replied by grandixximo on topic LinuxCNC S-Curve Accelerations

LinuxCNC S-Curve Accelerations

Category: General LinuxCNC Questions

I saw it the first time I opened it. Couldn't bother myself to fix the sequence on a Sunday afternoon lol
I will fix it for y'all tonight.

Edit:
Done, pushed to github, the ini configuration is better suited for quick testing, you don't even need to home it ([TASK] NO_FORCE_HOMING = 1), but if you do is just one click, and you got infinite limits to load your wildest g-codes.
  • rodw
  • rodw's Avatar
05 Jan 2026 06:34
Replied by rodw on topic LinuxCNC S-Curve Accelerations

LinuxCNC S-Curve Accelerations

Category: General LinuxCNC Questions

A couple of us played briefly today on Trixie and we built some debs to share with a few friends.
In the sim, I would like to see 
HOME_SEQUENCE=1 for all joints 
This will enable the home all button to save some time when playing. No need to home each joint.

I'm just having trouble with a corrupt APT system on my Linuxcnc PC and I am getting latency errors on my  office PC so I could not see much but I did briefly see some nice curved graphs in halscope.

I think if it was committed, there would be a stream of testers to find any remaining bugs...
 
  • jimmyrig
  • jimmyrig
05 Jan 2026 05:23
Replied by jimmyrig on topic Quick sanity-check

Quick sanity-check

Category: PnCConf Wizard

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
  • Bari
  • Bari's Avatar
05 Jan 2026 04:03
Replied by Bari on topic Bridgeport EZ Trak DX II Conversion to LCNC

Bridgeport EZ Trak DX II Conversion to LCNC

Category: CNC Machines

Thank you. I just saw this after a long illness.
  • Thllll
  • Thllll
05 Jan 2026 02:50 - 05 Jan 2026 02:51
Replied by Thllll on topic Auto Tool Probe - not callable

Auto Tool Probe - not callable

Category: Qtvcp

The docs are good, its just so much information.. and it seems like alot of it can conflict with each other and can be easily setup wrong. I would suggest a better LinuxCNC setup wizard.

Consider this, the pncconfig and the stepper config could be updated. Yes it would be massive amount of work. Basic setup is a breeze currently but if it was updated to have more options like probe, tool sensor, camera, ATC ect. Each new section can have additional details or options with images or explanations. Based on the setup the wizard would automatically change the .ini file, hal file, postgui, add folders, add routines, ect, set paths, ect. This way human error is taken out leading to a faster setup or update
Displaying 121 - 135 out of 20517 results.
  1. Forum
  3. Search
Time to create page: 0.366 seconds
Powered by Kunena Forum