Engine EEC-IV Problems

I'm not sure on that one, but since the strategies are different, and I think that means different scalars and tables altogether, I wouldn't expect a BIN from a CBAZA tune to work on a GUFB tune.

Also, and again I don't know, but if I were in your shoes, I'd load BE and just open one program while working with any computer. I don't believe that would be a problem. But, you could image your computer before, if you really wanna play things safe. Then, you could return it to the way it works now. And, since the EEC doesn't actually store anything, flashing the BE or a J3 chip themselves can't leave them in a non-functional state. You'd just have to reflash 'em.

I'm aware that the Binary Editor and TunerPro RT file extensions are different making them not cross compatible.
Also, usually not (within a method) compatible across strategies.
As far as TunerProRT/decipha method, the bin/defintion files are paired up. I'm using CRAI8 based bin variation with a CRAI8 xdf (definition) file in the
1999 Crown Vic pcm with my 5.0 with 2020 F250 7.3 ignition coils. They seem to like the 23 (17) to 26 (21) year old EEC-V pcms.

Check the caps in your processor
Get the snap on scanner to power up
The car is the fault, not the brick
Check every wire in the self test connector
Buy a NGS scanner that does everything, not just some of it