* make sure grounds are connected

* Save config

* disable output channels (good idea until the harness/app is known, and driven loads are verified, at least with simple Ohm measurement; eg between EC36/pin7 and EC36/23)

What would be the target application ?

How many IGBT ?

* measure voltage between EC36/29 (or any other +5V potential above GND) and ignoutput after powerup (output not active)

* 5 .. 5.5V measured => logiclevel output

* 0V measured => power IGBT output

** (if uncertain, use a 1k..10k "pullup" resistor, parallel with the DVM; the DVM otherwise has a very high input resistance, 1M .. 10M usually).

** 1k Ohm resistor in series with LED (anode connected to +5V) makes a very good bench setup.

** If uncertain, that is very good time saving to see in action: PC soundcard => trigger, eg with "m231" aka 24-1 signal (disable sectrig first), and test all outputs in question (or those planned to be used) 1 by 1.

** IGBT outputs are off by default, only light up during dwell time (or if configured as other, eg. misc2 function, and turned on by parameters or by inverting).

** Logiclevel ignouts pull to GND by default, so appear ON if tested between output and +5V (appear OFF if tested between output and GND)

----

VR or HALL trigger ?

Measure DC voltage, while connecting a 1k resistor between GND and

* EC36/27 primary trigger

* EC36/13 sectrig

DC voltage

* 0.5 .. 2V means strong (eg. 2k7 .. 4k7) pullup (1.35V is usual) => HALL input

* 0.1 .. 0.3V means weak (eg. 18k .. 27k) pullup (0.18 .. 0.25V is most usual) => VR input

** 0 .. 0.1V is also possible for sectrig VR

----

Injector type?

must assume 30V voltage flyback, High-Z injector only

* unless you know for sure that it has active flyback at this time.

** Even if it had active flyback 4 or 8 ch originally, perhaps it was removed if the history is untracked

Will look more by orderID. What city and country is it currently in ?