Can I use 7i96s with LCNC 2.8

Can I use 7i96s with LCNC 2.8? I dont need any wizard.

If you are OK with startup complaints and some loss of functionality
2.8 will work, though there is no reason the hm2 driver changes in 2.9
could not be back-ported to 2.8

Me and google translator don't understand your answer. The reason is that the structure of sentences in English and Czech is different. So I'm sorry to ask some things second.

First, I'll start with what I'm about. I made a website where I present my opinion as simply and reliably as possible to start with LCNC.
zz912.webnode.cz/mesa-7i96/
My opinion is LCNC 2.8 + Mesa 7i96 is ideal to start with. The reliability of the LPT port is determined by the luck of the particular hardware and electromagnetic interference at the point of use.

My site is for people who know absolutely nothing about Linux OS or LCNC. Windows is the most widespread OS in the Czech Republic, so Debian is a shock.

Today I am able to solve many problems that I was not able to solve at the beginning with LCNC. However, my main goal is to show the way how to get started with LCNC for complete beginners and keep your website up to date.

When I started with 7i96 LCNC 2.8 was the nostable version. It was hell. You helped me yourself, if you remember. Therefore, I will not recommend beginners to upgrade to version 2.9 at this time. I currently have RIP 2.8, so 2.8.3 will be the first version I'll be happy with. Some of my friends are still using LCNC 2.7.15. I just wanted to take a look at 2.9 and finished before I started. forum.linuxcnc.org/qtvcp/39967-qtvcp-python3-in-master#185536 (I just want a RIP install)

Everything would be great if the Mesa 7i96 didn't go out of production. I originally thought that the 7i96s would be controlled the same as the 7i96, at most a different bit file. However, as I read various messages on the chat, it probably won't be true.

Will the regular 7i96 still be produced?
(When the chips are available)

What additional functionality does the 7i96S have over the 7i96?

Will hostmot2 from LCNC 2.8 handle the 7i96S?
Yes / No

If not, do you plan to update LCNC 2.8 hostmot2 for 7i96S?
Yes / No

Can mesaflash from LCNC 2.8 handle the 7i96S?
Yes / No

If not, do you plan to update LCNC 2.8 mesaflash for 7i96S?
Yes / No

Will PNCconf from LCNC 2.8 handle the 7i96S?
Yes / No

If not, I could help you with that. My friend has already ordered the 7i96s, they have already arrived in the Czech Republic and he will send them to me. I don't know if I could do it, but I would try.

Best bet for the 7I96S currently is to update to LinuxCNC to 2.9

Full support for the 7I96S requires LinuxCNC 2.9 and Mesaflash 3.4.3

pnconfig does not currently support the 7I96S but configurations built for a
7I96 will mostly work (if you change the card name to 7I96S) except for
outputs 4 and 5

JT's MesaCT does support the 7I96S

7I96S additional features are: isolated Spindle analog output and
ESD hardening of Ethernet for Plasma applications. Also the 6 isolated
outputs have been divided into 4 high current (2 A) low isolation outputs
(identical to the 6 7I96 outputs) and 2 low current (100 mA) high isolation outputs.

The FPGAs used on the 7I96 have leads times in the 2 year range currently
so if the 7I96 is ever built again, it will be a long time...

Thank you for response.

Is possible added Mesaflash 3.4.3 to repository for LCNC 2.8 ?
At the moment there is Mesaflash 3.4.0-1

I guess this could happen with a new distribution,
but I expect we will see a 2.9 distribution next, instead of 2.8.3
 

PCW wrote:

I guess this could happen with a new distribution,
but I expect we will see a 2.9 distribution next, instead of 2.8.3

 

I hope no.

tommylight wrote:

zz912 wrote:

PCW wrote:

I guess this could happen with a new distribution,
but I expect we will see a 2.9 distribution next, instead of 2.8.3

 
I hope no.
Ahoj,
Your translation should be passed on, i think, i do not know for sure.
Are you worried about that?
 

I have no problem, just my translation. Branche 2.8 contains at least 2 important FIX for Gmoccapy. These BUGS really annoyed me and I was looking forward to the 2.8.3 version.
Don't you know when the deadline for switching 2.8.2 to 2.9.0 is? I wanted to convince the admins here to make 2.8.3, but I would like to try to add something to it, but I don't know if I will succeed or if I will be able to do it. When PWC told me the information about the transition from 2.8.2 to 2.9.0, I spent half a day breathing it out. Version 2.7 ended at 2.7.15. I thought I had more time. I am a very conservative person. I start using the programs from version X.X.10. I don't have a problem being a tester, but I prefer to catch minor bugs in an advanced stage of a project. I was very happy when I managed to do Pull Requests to branche 2.8. Many of you here have helped me with them.
 

I don't have a physical 7i96s card yet. But I was looking at the 7i96s_d.pin file.
 
I found a bug on line 4.
there is: BoardName : MESA7I96
it should be there: BoardName : MESA7I96S

Then I looked at the Configuration pin-out and I couldn't find anywhere the Pins for the PWM that should drive the SPINDLE.