Advanced Search

If you do not need the 0-10V analog output for VFD, there are in stock Mesa 7i96 without the S, they do have an encoder input:
store.mesanet.com/index.php?route=produc...oduct&product_id=311

No need for a bit file, only if you need non standard firmware.
That is from old Mesa boards that needed the firmware at startup, all new ones have that on board, many of them twice, just in case a bad flash messes up switch to the backup and flash again, correctly if possible.

Thanks Peter — one additional note: I also see that 7i96S and 7I84U are currently showing as out of stock on the Mesa store.

My preference is to stay fully within the Mesa ecosystem (rather than using generic BOBs), so if there are any expected restock timelines for 7i96S and 7I84U, or recommended current-production alternatives that keep a similar architecture, that would be very helpful for planning.

I can wait a bit if needed, but I’d like to avoid purchasing from Europe if these boards are expected to be restocked or revised in the near term.

Thanks Peter — that’s very helpful.

That aligns well with my use case. Since the IL-1000 is only ~10 Hz bandwidth and Y motion is intentionally slow, trading loop bandwidth for higher effective resolution via low-pass filtering sounds ideal for stable stand-off control.

Given that, THCAD-2 looks like the right solution for the current phase, especially with it coming back in stock shortly.

For any future higher-speed sensor upgrades, I’ll revisit true ADC options like the 7i87 if needed — but for now THCAD-2 + filtering seems well matched to the application.

In addition, I will need extra isolated digital I/O for valves, interlocks, and machine signals. I was looking at the 7I84U isolated remote field I/O card (sourcing/sinking outputs), but it currently shows as out of stock. My preference is to stay within the Mesa ecosystem rather than using generic BOBs, to keep things robust and well-supported in an electrically noisy environment.

If you have any guidance on availability of the 7I84U, or alternative Mesa smart-serial I/O options that integrate well with 7i96S for isolated field I/O, I’d really appreciate your recommendation.

Thanks again for the detailed clarification.

The THCAD2 should be back in stock in the US by the end of the week.

Our other analog input card (the 7I87 6 channel +- 10V card) will still be about 4 weeks
but you don't need 6 channels...

For the THCAD2, the update rate is the servo thread rate (giving a loop bandwidth
of about 300 Hz at ~10 bit resolution) You can get better resolution by low pass
filtering (in hal) the frequency signal at the expense of loop bandwidth of course.

 If your height sensor only has 10 Hz bandwidth, you could easily increase the resolution
(to 12 bits or so) by this filtering since it will not affect system loop bandwidth significantly.

Again THANKS a lot
My issue isn’t with Linux itself, but with the documentation.

I guarantee you that I am starting on a very small scale. My gantry weighs 600 kg without the spindle.

I will start tomorrow with mesa ct but just a small question:
When I look through the files immediately after the installation i see no bitfile I can relate to 7i97 card. Is that how it is supposed to be? Does the bitfile exist at all as a separate file and is it generated automatically when the config file is written by mesaCT?

Thanks for the feedback — appreciated.

To clarify, my primary focus right now is using the Keyence IL-1000 for slow stand-off correction. Based on the discussion, I agree that THCAD-2 into a 7i96S encoder input should be sufficient in terms of raw speed and isolation for this use case.

My main concern is less about servo-thread rate and more about effective sensor update rate, frequency-to-velocity measurement noise, and required filtering/deadband for stable Y correction in a noisy industrial environment.

I’ve contacted Mesa support regarding isolated analog input options to complement a 7i96S-based system, but haven’t received a response yet. At the moment, many Mesa ADC-related boards appear to be out of stock in the US, and I’m considering purchasing from Europe. However, I’m a bit concerned about committing to hardware if Mesa is planning to release newer or replacement analog/ADC solutions in the near future.

If you (or others) have practical recommendations for current Mesa ADC hardware that works well with 7i96S, or insight into Mesa’s roadmap for analog input, I’d really appreciate hearing them.

LK-G3000 is only a possible future upgrade — the current design focus is on making IL-1000 work robustly and predictably.

Yeah, that is very old info, for some reason google insists on finding docs and info for version 2.4 but not for 2.8 or 2.9, and that is aggravating, extremely, but is beyond our reach to fix it.
We do remove outdated info from the forum whenever we bump into it.
-
Ping OK is the only thing you need, make a config and start wiring stuff.
-
You might need mesaflash ONLY if you need firmware for:
-you want to use a Mesa 7i74 or 7i85 or add a 7i76 or similar
-you request special firmware that is not standard
-
One major tip for wiring, do NOT wire everything and power the machine ON.
Follow the link i posted, wire stuff one by one as mentioned there, check and recheck, and only when making sure all is good, move on to wiring and testing the next thing on that list.

I would just try either MesaCT  or the sample configuration.

As others have mentioned, you don't need mesaflash, unless you need
a configuration with a parallel expansion port connected daughter card,
or perhaps want MODBUS support.

Unfortunately the mesaflash version included with 2.9.4 is quite ancient
and does not recognize the 7I97T.

As long as:

mesaflash --device ethernet --addr 10.10.10.10

replies with the card name (whether it recognizes it or not) you have a connection.

The ping  test also works, except if you set the host IP address to the FPGA cards address
(a common mistake) but if mesaflash finds a card, unsupported or not, you have connectivity.

Thanks. That was the issue. I did the script SrL had above, and lost the customized grub notes. thanks

I will post some updates when i finished the next steps

Always nice to hear that someone likes the work, Thanks

Thanks a lot for helping
So… my question is: when do I need to change my firmware?
In all the resources I have been through I have been informed that I needed to secure that the connection between LinuxCNC and the mesa card (hostmot, hm2_eth and bitfile) all were in place and functioning correctly.
The ping OK was not enough.
Do I still need to do this or can I carry on?

edimas93 wrote:

Is there any hal to configure this 2-mode configuration!

 

Yes.  This post has a configuration using a step/dir spindle drive to manage spindle, orient, and c-axis modes:

github.com/LinuxCNC/linuxcnc/issues/3556

A few posts down the author attached a configuration zip file.

It's not extremely complicated, but neither is it simple.

And the issue reported in the post is still present.  I'm almost done with my attempt at a configuration based on the posted one, and I'll be testing if the joint.N.index-enable signal is what causes motion errors.

OT-CNC wrote:

Good info.

What are the compression fittings you are using on the trucks? That is usually the more difficult part to source due to the odd pitch of 0.75 on some LM blocks.

For a lathe I would need 10 remote ports if direct fed like on your setup. That might be okay.
Equal length tubing may be a solution to avoid metering units if running it off a manifold. Any experience with that? 


 

A search for "M6 x .75 grease fitting adapter" resulted in a bunch of hits on Scamazon for 4mm tube compression fittings (both elbows and straights).

They aren't as cheap as the push to connect, but if you're worried about it you should be able to fully plumb up the lathe for appx $100 (20ftgs and tube)

Since mine are individual, I wasn't concerned with metering.  A pump or two and watch for some grease to ooze out of the truck or ballscrew before a long, slow warmup cycle to spread things out.  A manifold, metering components, or similar was just going to be a complication.  Once they are easy to access it's not a burden to lubricate.  And grease generally stays put for quite a while - no need to grease every day like an oil system.

unknown wrote:

So this is just another USB to serial implementation ?

Yes,
it's the usual USB/serial converter that anyone can make themselves.
Can you give me some working and usable examples?
I haven't found any, and I've probably wasted six months of my life trying to figure this out. 

ciao
Roberto