You did not program the flash, just the FPGA.
Now you should have Ethernet access so you can run:

mesaflash --device 7i95t --addr 192.168.1.121 --write  7i95t_16m_fallback.bin --fallback
mesaflash --device 7i95t --addr 192.168.1.121 --write  7i95t_d.bin 
 

hhscott wrote:

Edit: Modbus (TCP) may not be the most "modern" approach that is available but I would say that it is the most universal, well understood, and common Industrial protocol. When it comes to system support it would be hard to argue against Modbus just because so many industrial control techs know it and use it. Simple system architecture typically translates to reliability. In an industrial application, reliability is king.

good point

I have been suspicious my bad experiences with modbus was mostly related to some inexpensive hardware I used.

Probe Basic has had a NEW Stable Release made as of today February 5th, 2026

In order to update to the latest stable release it will require updating your sources.list.d/kcjengr.list file to point to the updated repository. the same goes for updating to the latest develop version, please see the link below in order to see all of the update notes!

kcjengr.github.io/probe_basic/update_notes.html

I installed Linux cnc / Efinity in a Virtual machine, I was able to use your command.
I just needed to activate python Virtual environment.

Could you please provide one .bit file? I am afraid that I might flash the wrong .bit file again.

It seems like I manage to flash the board?
What do I do next?



efx_run.py seveni95t.xml --flow program --pgm_opts mode=jtag
Programming using Board Profile: Generic Board Profile Using FT4232
jtag programming started!
JTAG Programming on ftdi://0x0403:0x6011:1:2/2
Programming 'outflow/seveni95t.bit' via JTAG at freq 3.0 MHz
Device ID read from JTAG: 0x00210A79
... finished with JTAG programming

Yes, I think that command needs the IDE or al least the xml project file with paths setup properly

Do you have a 7I95T  .bit file? (if not I can post one)

 

Hey Guys, I’m pretty new here.
 I have a little Problem with configuring my Stepper online A6 Servo Drive. I want to use torque homing but I can not Figure Out wich Parameters I need to set in the Drive. 

And I also Think that my Linux CNC Config is wrong. Can maybe someone with more experience then me help me

Liebe Grüße

Thanks Rod, I managed to build a deb in a bookworm chroot but it won't install on trixie because linuxcnc requires python3.11 and trixie uses python3.13. I also tried installing the deb from buildbot2 but same result. Looks like I have no option but to reinstall bookworm. Major PITA.
On that note, I recall you posted the 6.3.0-rt11-linuxcnc kernel somewhere, but I can no longer find it. Could you tell me where that is? Thanks again.
Jim
 

OK those settings should result is a +1.0V output
(as they do here)

Possible reasons for a very different output voltage:

1. Measuring wrong pins ( analog output 0 would be measured from TB3 pin 4 to TB3 pin 3)

2. Marginal 5V supply to 7I97T

3. Problem with the voltmeter

4. Damaged 7I97T analog output driver

5. 7I97T analog output connected to shorted  load

Okay first of all thank you for all your help with this, I am very new to this and have watched countless hours of youtube on ethercat and a having a hard time finding solutions to errors. I have another error 
Failed to register PDO entry: No such file or directory
LCEC: master 0 PDO entry registration failed

I want to thank everyone again for the help, I had lost hope on my project until now.

I consider having to restart LinuxCNC unacceptable. If I don't find a better solution, I will not use this pendant.

The rotary knob sounds more like a configuration issue(?). Have you checked if you see the position switch changes by running "xhc-whb04b-6 -a" from a terminal?

Greetings Mark!
First of all, excellent work on the retrofit - this thread will end up being a literal goldmine for me. 
Last week I also purchased a 1986 MH400E and the goal is to convert the machine to LinuxCNC in the coming few months. 

Somewhere in this thread I saw that you have a 'collection of notes' for your conversion - is there any way to get these from you? I can't seem to find an email-adress available on your YT Channel as previously stated. 

I haven't quite had the time to work through all 180 pages, but I do have a quick question: 
How is the gear-changing generally handled? Do you have to command an exact speed value, or will LinuxCNC pick the correct gear for whatever arbitrary speed you command? 
Also, will the gear-change happen automatically whenever a speed is commanded, or is there specific codes that need to be ran (I would love to use the F360 CAM and I wonder if linuxcnc will handle selecting the speed automatically, or if I need to fiddle around with the post-processor?) 

Thanks and very best regards from Germany
Daniel

 

Hakan wrote:

If the drive is reducing the speed by itself you will get following errors.
Otherwise it's the settings in the ini file that are throttling the speed.

Yeh, that's what I have been playing with to determine where to set max velocity. I remembered from when I set up my plasma on a Mesa card to see how much of its 10 Mhz bandwidth I could use that there was a physical limit to how fast you could step in the real world. That's why I cut back the settings here. The design target was 10240mm/min so it fell a bit short, But the RPM is still quite respectable. I've had enough for one night.

I also might try increasing the amps a bit too

If the drive is reducing the speed by itself you will get following errors.
Otherwise it's the settings in the ini file that are throttling the speed.

So I had this theory that at default 10000 steps/rev it was running out of bandwidth when it got to 2000 mm/min (400 rpm). S0 I changed the steps to 1000 steps/rev which I assumed might get me to 10 x 2000 = 20000 mm/min
This let me get up to 8500 mm/min maximum velocity. But It did not get me to the expected 20000 mm/min (10 x 2000)
So definitely reduce the steps/rev if top end speed is important to you. I think you'll need to tweak the steps/rev to suit your design parameters.