IQ-X support in MQL ? Custom scans not placed — IAPI DLL mismatch

[louisfeli...@gmail.com]

Hi all,

I'm trying to run MaxQuant.Live 2.2.2 on a Thermo Orbitrap IQ-X Tribrid and running into an issue where custom scans cannot be placed via the IAPI.

Setup:
- Orbitrap IQ-X 4.2 QF1 (build 4321)
- Xcalibur 4.7 SP1 (4.7.102.25)
- Foundation 3.1 SP10
- FreeStyle 1.8 SP2 QF1 (1.8.65.0)
- API license valid until 09/07/2026
- MaxQuant.Live 2.2.2 with SelectedInstrumentName set to "Eclipse" in Settings.xml (Exploris fails).

Behavior:
MQL connects to the instrument and receives incoming scans successfully (magic scan trigger works, scans arrive as expected). However, when MQL attempts to place custom scans, the log shows:

"NEW CUSTOM SCAN1000 HAS NOT BEEN PLACED, CONNECTION TO SERVICE BROKEN"

The scan protocol is a are two MS OT experiments (Orbitrap, 60000 resolution, positive polarity, profile data, standard AGC) configured as per instruction for magic scans. I have tried with and wo quadrupole isolation.

Investigation:
Looking at the IAPI DLLs in the MQL lib folder, I noticed:
- MQL ships with Fusion.API-1.0.dll, but the IQ-X does not have this DLL in its TNG\OrbitrapIQ-X\4.2\System\Programs\ directory
- The API-2.0.dll in MQL (71.5 KB, from 2022) differs from the IQ-X version (81.5 KB, from 2024)

It appears the IQ-X uses a different IAPI pathway than Eclipse/Fusion instruments, so the Fusion.API DLL can read scans but fails when writing custom scans back.

Any plan/trick to have the Orbitrap IQ-X supported by MaxQuant.Live 2.2.2?

Happy to provide additional logs or screenshots. Any guidance would be greatly appreciated.

Thanks!