CEL P1305 P1310 = stranded on highway. Unichip problem?

[Herb]

Well this was great way to spend a day. This afternoon I started to drive back to Calgary from Edmonton, and suddenly I noticed that I was losing response from the throttle. The tach was fluctuating around 700-1300RPM, even when the engine sounded it was still running close to 2500RPM at times.I noticed the CEL was lit and I decided to pull over and shut down, probably was a good idea as I was on an incline and left hand lane when this originally happened as I probably wouldn't have made it to the shoulder on the right if I tried to push the issue.After I shut down I scanned the codes with my ScanGuageII and it showed I had a P1305 and P1310. Not knowing what they were, I just made a note of them and cleared them from the ECU, hoping that I would be able to re-start the engine.Well no go on that. I tried several times to start the engine, but to no avail. I managed to google the codes on my Blackberry and it indicated some kind of ignition issue, but it was hard to read all the stuff that was formatted oddly on my BB so I resigned to the fact I probably couldn't fix the problem with nothing on hand and nowhere to go.Since clearing the CELs didn't work I tried to cut power to the ECU through the manual cut off from the Unichip, but that didn't even work. Desperate to try anything I decided to disconnect the Unichip. Lo and behold the engine started up fine. I drove the remaining distance home without issue so I'm assuming the problem was with my UnichipNow that I'm home I searched the codes and this is what I came up with:P1305 Ignition Coil 2 Primary Feedback CircuitP1310 Ignition Coil 3 Primary Feedback CircuitI think the Unichip plays around with ignition timing so if something went south on it, I'm assuming that it would throw CELs at me.Thoughts?

[BlueCrush]

Makes sense that it was the Unichip since it worked fine once it was disconnected. Something probably went bad on the chip. I would also pull the plugs to make sure they are still good. Then re-install the Unichip to see if it comes back again (if you dare). Keep us posted.

[Herb]

Quote, originally posted by BlueCrush »Makes sense that it was the Unichip since it worked fine once it was disconnected. Something probably went bad on the chip. I would also pull the plugs to make sure they are still good. Then re-install the Unichip to see if it comes back again (if you dare). Keep us posted.Well I've written NEA and surprisingly enough I got a response from Brad on a Sunday evening no less. He told me to contact Unichip, so I've sent them a message.In the meantime, I'll be running without the Unichip until I hear back from them to see what I should do next to diagnose it.I wasn't about to reconnect the Unichip after the engine started as I was still 2.5 hours away from home at that point. Not to mention it was scorching hot today, definitely not a pleasant way to spend the afternoon on the side of a busy highway.