Where to start with Mesa 7i92 + 7i85S

If you need 6 PWM generators, that is not the correct firmware
what is the motion interface to the prototrack hardware?

Edit, read back and see these are those funny 50% PWM = 0 drives
This is going to take 7I92_7I85spx2 firmware and a quite customized HAL file
to do the PWM offset. Pretty sure pncconf will not be any help at all here.
probably better to start with the hm2-servo example file

Yes, the drives need a 15.5 kHz differential PWM signal, so 2 PWM signals per drive.

Where can I find the 7I92_7I85spx2 firmware? I can't find it in the the support software zip on the Mesa website.
I'll start reading through the hm2-servo.hal example and see if I can get an idea of it.

Edit: Is this the correct firmware PCW? git.linuxcnc.org/gitweb?p=hostmot2-firmw...97adc0d8ccbd;hb=HEAD

That's the correct pinout source file, but the firmware needs to be compiled,
using that file to define the pinout and included modules.

Note that that pinout file will work with 5I25 and the 7I92 but the firmware files
are card specific

The firmware files always end in .bit and mostly start with the card name

Jrjones wrote: Yes, the drives need a 15.5 kHz differential PWM signal, so 2 PWM signals per drive.

Just to clarify where the confusion is, you have two PWM outputs per PWM module. So only 3 PWMs. Standard PWM has 2 pins per module two, PWM and direction. If you look at git.linuxcnc.org/gitweb?p=hostmot2-firmw...fe5a983ab494e0a49b49 you will see the subtle difference.

Going back a posting or two, you don't really need the config wizard to know about your daughter card in detail as firmware sets what pins exist in the sense of whether you see stepgens or pwms and encoders etc, but the HAL pins remain the same regardless of the physical pinouts on the cards. So, hm2_7i92.0.pwm.00.value will drive pins 2 and 15 in the DB25 on the 7i92 with the .bit file you are looking at, but might drive completely different physical pins with different bit file.

git.linuxcnc.org/gitweb?p=hostmot2-firmw...a263cff8d9c8;hb=HEAD

Defines the bitfiles that are created as part of the hostmot2-firmware package, which doesn't seem to include any 7i92 card definitions.
However, the 7i92.vhd etc do appear to exist in the hotmot2.zip file from Mesa. (which you will find inside 7i92,zip inside the Hostmot2/source folder)

I did have a Virtual Machine set up to create bitfiles, but I think I lost it to a HD failure, otherwise I would have offered to build you the bitfile.

The simplest solution is to ask PCW to build the bitfile for you, but it also seems that the LinuxCNC Hostmot2 repository needs updating to add the 7i92 and start autobuilding firmwares.

heres the 7i92_7i85spx2 bit file
i dont yet have a 7i92 to test so it's just as built .

I would recommend a bit of caution with the 7I92 and untested bitfiles as its easy to brick a 7I92 with a
physically correct (correct CRC correct chip etc) but non functional bit file

I would do this with an unknown bitfile:

mesaflash --device 7i92 --write newbitfile.bit --fallback
mesaflash --device 7i92 --reload --fallback

This will write the new bit file to the fallback area of the flash memory and then load the FPGA from that area
if the 7I92 fails to communicate after this, a power cycle will reload the user configuration