For the last three days I have had no trouble logging with CANscan. Today I got home from work and was planning on doing a few more runs to flatten out a trouble area in my AFR graph around 5600 6200 (dips into mids 12's)

For the last two hours I have seen one message after starting CANscan and connecting on COM4. "Waiting for ECU"

I have rebooted the laptop.
Reinstalled the software
Used the USB port to connect up to the CZ Unit.
Triple checked all my wiring
Crawled up underneath the dash to make sure the car's wiring was tight
Turned off the CZ unit
Deleted and reinstalled the Com port

My thoughts to reolve this are...

Get another RX-8 later in the week to connect up to.
Make sure my USB/Serial converter works by connecting up to a CISCO switch or something.
Finding a laptop with a serial port.
And at last resort asking Mr Harrison of I need to replace the CAN bus converter.

Anyone else have any ideas? or experienced a similiar problem?

 

Email Dan Harrison about this. Same thing happened to me last November and it turns out the CAN chip inside the unit burnt out. Dan had no idea how that could have happened.

Dan gave me this troubleshooting tip first before I sent it back for repair:

"Has it worked before on the RX-8? Were you still using it on the RX-8? You
can try running Hyperterm, it is found at
Programs/Accessories/Communication/Hyperterminal. Configure Hyperterm to
connect on the COM port you are using with the following settings: 19200
baud, No parity, 8 data bits, 1 stop bit, No Handshaking. With Hyperterm
running, connect to scan tool to the car and turn the ignition switch to ON.
You should see some characters appearing on the Hyperterm window, either
PIPIP... or SSSSSSS."

Hope this helps!

 

Well I just removed the CZ unit. No luck
I ran a dump of the serial data i just c this ....

RX -> 50 (that is recieve right)

It tries that alot.

Thanks for the tip on hyperterminal. This is ignition to ON position but engine not turned over? U say "connect scan tool to car" do u mean the wiring and not the app just hyperterm, or do u mean start the app and use hyper term to watch the traffic ?

 

Well of course HEX for P is 50 as I should darn well know. And yes other terminal applications show me that as well. So this means I blew the chip, or this means I am working as expected ?

 

It could show PPPPPPPPPPPPP and that means it's PC - > Canscan is working but Canscan -> Car isnt. PIPIPIPIP or SSSSSS should be what you get.

And yes, power on but ignition off. I think there might be a power surge coming from the OBDII/CAN port that causest this burnout. If it was causing this, you wouldn't even get to connect to the Canscan anyway. Email Dan Harrison if PPPPPP is all you're getting, he's very responsive and helpfull.

 

damnit you brunt out our canscan no cookie for you.....

 

i met dan @ lunch and he swapped out my CAN converter. it works just fine now.