I screwed up bad and need help!

[javi]

I ordered a Mac 10T upgrade kit from EM3ev with 9FET controller and Cycle Analyst V3 and I spent the last day or so putting it all together. I took it out for a test drive and it was fun.

Then I started reading about the Cycle Analyst and how I should capture the set up menu as it came configured (presumably by EM3ev). I downloaded software and brought laptop outside. I now realize that I picked up the EB3 controller programming cable and found a 5-pin connector on the CA, clicked it together and then plugged in the USB to the computer. The CA immediately lost power and when I pulled out the USB, it was quite hot.

So to recap, I hooked the (5) pin connector on CA to my computer with the controller programming cable and now nothing works. How do I figure out what happened and what I broke? I don't even know where to start and feel so frustrated with myself! UGGH!

 

[Jason27]

Its probably just a bad connection. Can you post some pics? Have you contacted 3mev?

 

[John in CR]

I'd talk to GrinTech at Ebikes.ca . Hot connect and now CA doesn't come on tells me something is fried, since you connect the CA3 to a computer via the CA3's serial port using the TTL/USB cable for the CA. The 5pin connector I think is the PAS connector, and you definitely do not use the controller programming cable to connect to a CA.

I would consider the programming cable to now be suspect too, so I'd start a thread about how to test the cable before connecting it to the controller.

In the meantime, if the CA won't power up, you will have to connect the throttle directly to the controller to be running in the meantime. Go easy on it if the CA was limiting current before.

 

[javi]

OK - thanks for replies.

I feel like everything electrical is suspect at this point. I opened up the CA - didn't see anything black or burnt in there.

I guess the first step is to hook everything up to the controller and see if the bike works. If that works, it would seem that my issue is with the CA. If not, then probably a lot of troubleshooting...