Page 1 of 1

Comms Issues -with log

Posted: Sun Jun 06, 2010 3:49 am
by hwright
Hi,

I have been having trouble connecting to the microsquirt V1 that I have.
2 years ago I used it on a motorbike (since sold) and it was working fine when I removed it. Stored it in a dry box since then. Now powering it up on the bench I get strange connection issues.

I am using a HP laptop with the USB -serial converter I got through DIY auto tune. I tested it with the MOTEC PLM and also another serial datalogger and it works with both of them no problems

Every time I try to connect the Microsquirt with megaTune I get no response.

I tried using the embedded code update utility in bootloader mode and the first two times it got to 19% then failed. Then The last time it downloaded the 2.890 code and verified and said all was ok. But after power cycling again without bootloader still no connection.

Then I checked again with the bootloader and first it didn't work but after 2-3 times I got the log below.

Any idea's? what the hell is 'a' when I read signiture and why does it work sometimes and not others!

[EDIT - I deleted the massive log this is what you need to know]

Opened comm port 2 at 115200.
Reading signature:
Trying command 's'
á
Signature: "á"
MegaSquirt Download 1.04

<I power cycled without bootloader>

Opened comm port 2 at 115200.
Reading signature:
Trying command 's'
Trying command 'S'
Trying command 't'
Trying command 'T'
Trying command 'q'
Trying command 'Q'
No signature available, possibly could not connect properly.
MegaSquirt Download 1.04

Re: Comms Issues -with log

Posted: Wed Jun 16, 2010 3:25 am
by hwright
Ok after some fiddling and using another desktop computer with a built in serial port I have confirmed that:

- With the bootloader connected I can download and verifiy code no problems, I tried a few different versions, all went in ok.
If with the bootloader connected I ask to read the signiture I just get the wierd <a> symbol

- After reset with no bootloader connected I get absolutely nothing through the microsquirt. Never connects to megaquirt, Nothing in hyperterminal, nothing in port checker, nothing in read signiture.
Also the fuel pump line is just open circuit and does not cycle, same with the accell and warmup LEDS. I do get 5V on my Vref. I double checked the bootloader voltage and it's about 3.4V when not grounded. I also connected it to the Vref but no joy.

I opened the uS and had a look but there is nothing obviouly wrong like water damage or burnt parts, in fact it's clean as a wistle in there.

The only thing is that uS draws about 0.8A from my power supply, which seams high given nothing is connected - what is the normal draw??

I have pretty much given up, I think somehow it has died while in storage. - What are my options for repair / replace?

Re: Comms Issues -with log

Posted: Wed Jun 16, 2010 4:51 am
by Matt Cramer
Can you load code with the bootloader pin *not* grounded? If so, the processor may be damaged.

Re: Comms Issues -with log

Posted: Sun Jul 04, 2010 1:29 pm
by hwright
Hi Matt,

No I can't connect or load anything with the bootloader not grounded

Re: Comms Issues -with log

Posted: Wed Jul 07, 2010 5:32 am
by Matt Cramer
This is a new one. You may need to contact whoever sold you the Microsquirt directly.

Re: Comms Issues -with log

Posted: Thu Jul 08, 2010 7:30 pm
by hwright
Ok, I bought it from DIY Autotune! in April/May 2008

What do you think of the chances / costs of repair or should I be looking at a replacement?

Re: Comms Issues -with log

Posted: Fri Jul 09, 2010 4:54 am
by Matt Cramer
It's not easy for me to say without examining it myself. Email me at websales@diyautotune.com.

Re: Comms Issues -with log

Posted: Tue Aug 24, 2010 10:07 pm
by hwright
To others that might be reading this.

I sent the uS to Matt and he diagnosed it as an internal CPU fault where it was stuck in bootloader mode.

The Board was replaced under warranty with a V2 mainboard. Now I have no problems.

Big thankyou to Matt and the Folks at DIY autotune for excellent customer support.