Page 1 of 1

No Comms after testing

Posted: Sun Feb 28, 2010 7:02 am
by JT squirt
Hi to everyone, I'm a newbie here and need advise.

I'm currently trying to microsquirt a 250cc single cylinder four stroke.
I had no problems communicating with my M/squirt until trying to set up my VR sensor with a 34-1 flywheel in Megatune, the rpm kept dropping between zero and 250 whilst cranking, I also had my ignition coil connected, when I started getting a stable rpm reading a put my spark plug back in to make sure it would still read ok.

The battery was only just coping turning the engine over and not getting resets, then it lost communication with M/squirt, now it won't communicate at all with my M/squirt.

I'v tried connecting in boot loader mode as another test and can't do that anymore either.

Do you think having the coil connected could have caused some damage? not sure if was suitable, it has a 12v feed and the ground switched by M/squirt, my M/squirt was a bit warm! when it stopped working.

Have I killed it? can I get it repaired?

Thanks Jason.

Re: No Comms after testing

Posted: Sun Feb 28, 2010 7:12 am
by Peter Florance
Did you have it jumpered to use the internal ignitor? If not, you may have hit the processor with +12V
Having said that, I've found one MicroSquirt that seems to have survived that insult.

Try reloading the firmware via Downloader

Re: No Comms after testing

Posted: Sun Feb 28, 2010 8:02 am
by JT squirt
I pretty sure the jumpers are in the write place but I'll double check tomorrow and I already tried reloading the firmware but can't connect anymore ( I have in the past playing with the Tackref/Tooth analyzer program)

Anymore ideas?

Re: No Comms after testing

Posted: Sun Feb 28, 2010 5:46 pm
by Peter Florance
JT squirt wrote:I pretty sure the jumpers are in the write place but I'll double check tomorrow and I already tried reloading the firmware but can't connect anymore ( I have in the past playing with the Tackref/Tooth analyzer program)

Anymore ideas?
If the boot loader jumper is in place, you won't be able to talk to the module with tuning programs. If the firmware is corrupted, you also might not be able to communicate with it until you reload firmware.