Datalogging error with working Xenocron USB cable

[cyanide]

Hi. Finally got a chance to connect everything and turn on my car today. I've done a DIY ITB setup with CBR954 TBs. Using ectune, Ostrich, Xenocron USB datalogging cable and Innovate's LC-1 with USB <> Serial converter (PL2303). I get a solid CEL at ignition and as soon as I turn on the car. I've tried 2 different COM ports, 4 and 10. Set latency to 1 and 16 and baud rate to 38400 and 9600 in all combinations possible. On doing auto-scan, it detected the correct COM port a few times. In the debug menu, it showed that it was selecting COM4 as the datalogging port. However, ectune gave an error that it couldn't connect to the ECU. Tried other COM ports and latency/baud settings to no avail. Now, the debug function just keeps retrying with timeout error. Increased timeout and retries values without any difference. I have used this cable on the same ECU with Freelog before, so I guess the hardware shouldn't be a problem. Further, ectune did detect it a couple of times too. J12 is cut btw. I need to know why I'm getting a solid CEL and the \"cannot connect to ecu\" error. Any help will be appreciated. Thanks! One small note I'd like to include. The car is OBD2B (no VTEC pressure switch) and has been converted to an OBD1 with the proper wiring harness and a 2-wire iacv. Since I was using CROME which didn't have a proper VTPS disable function, I had connected A4 and D6 in the wiring harness to fix the VTPS error. Don't think that bit of wiring should make a difference, but including it just in case. Also, the car won't idle without the butterfly opened just a bit. This is with a 2wire IACV connected and wired using the FF-Squad 3 > 2 wire iacv fix.

[cyanide]

Problem fixed by using a ZIF socket for Ostrich ribbon cable. I am an idiot