This company has been selling ARINC429 test equipment - as well as a load of other avionics and milspec "bus" products.
No reply on any phone # (voice mail only) or to any emails, for some months now.
The cellphone # of one of their engineers is also dead.
https://www.maxt.com/maxt/home.htmlI have one of their 4 figure priced PCI cards and their software, and one PCMCIA card, both running, and a new PCI card which I want to get running. But the software needs codes which are PC configuration dependent. Yeah, "that system" where if you change the motherboard you need new codes
They use keylib32.dll which generates some sort of hash from the current machine config, and you give this to MAXT, and they give you codes you enter and this enables the functionality. They offer a free (zero cost) mode where you get just 1xTX and 1xRX but they still need to issue codes for that.
Their software was written over the last 25+ years (there is stuff online where one of their devs was asking questions on forums c. 2002, when developing a PCMCIA version

) in Delphi. And Delphi supports this module by generating a large number of calls to it so it cannot be patched practically.
Their main guy in Europe lists on LinkedIn as having left the company last month
Manel Pouget
MAX Technologies
12 yrs 3 mos
Director at MAX Technologies Europe
Jan 2020 - Apr 2026 · 6 yrs 4 mos
Toulouse, Occitanie, France
and from yesterday lists a new job
Key Account Manager
SPHEREA · Permanent
Apr 2026 - Present · 2 mos
Toulouse, Occitanie, France
Better leave those two PCs powered 24/7 because that produces the best reliability in electronics

It's a lesson - as if one was needed - to avoid software which is locked to the hardware of the PC or laptop. Basically everything MAXT made will end up in the bin within not many years, due to this ridiculous copy protection. Especially in companies which have a self imposed requirement to run only the latest OS. They won't know how the keylib32.dll copy protection system works so they will chuck out the old PC, move the card to a new one, and then discover it...
Someone suggested using just the card and doing own software. I would expect the API to be immensely complex. This is the sort of card

and there is a huge FPGA on it. Their older cards (I have one of them too) is 2x the length and with more huge FPGAs. These cards are a tour de force of hardware design. Their old PCMCIA card must be absolutely packed, since it does 16xTX and 16xRX, IIRC (I have one, enabled for just 1xTX and 1xRX which is all I need.
They also spent a lot of time on the software. They have packet definitions for every imaginable ARINC429 packet, and these vary according to grouping so e.g. (just an illustration) label 250 might be altitude if from the INS or ground speed if from the GPS. Plus some of the packet definitions vary anyway according to which avionics document you read; the Honeywell GPWS 400 page tome is a common reference, with great detail, but not universally followed. This software does actually run without the codes so you can use it as a packet reference manual

The way to get this working is to attack keylib32.dll. This googles to a lot of people playing around with it. It decrypts its executable data and loads it into RAM for execution, to resist disassembly.