Page 1 of 1

Not the usual comms problem

Posted: Fri Sep 28, 2012 10:29 am
by tsoldrin
Hi Guys

I have got an interesting comms problem which is that I had ms tuner working fine and connected to my bike without any problems and I then tried to change my laptop as my old one was a bit slow. I have been unable to connect to the new laptop and whilst troubleshooting the problem I reconnected the old laptop and discovered that it couldn't connect either and with further investigation i found some damage to the serial cable, it was slightly cut with some copper showing. I have replaced it with a new one but still cannot connect, I have tried portchecker and it can't see the MS but I know that the MS is still working as the bike still start and runs. Could the damaged cable have done something to the MS? what should i be checking next?

Cheers

John

Re: Not the usual comms problem

Posted: Mon Oct 01, 2012 5:21 am
by Matt Cramer
It could have damaged the serial circuit or sent corrupted data. Try reloading the firmware - this can often be done even if the data is corrupted.

Re: Not the usual comms problem

Posted: Sun Oct 07, 2012 12:54 pm
by tsoldrin
Thanks for the suggestions Matt, I tried reloading the firmware and am still getting no connection to the MS.
Could you point me in the right direction for fault finding on the circuit board?

Cheers

John

Re: Not the usual comms problem

Posted: Tue Oct 09, 2012 4:59 am
by Matt Cramer
About the only way to check is with an oscilloscope. What board version do you have?

Re: Not the usual comms problem

Posted: Tue Oct 09, 2012 8:20 am
by tsoldrin
Hi Matt

Its the V2.0 black pcb. I Have an electronics friend who has oscilloscope and all required facilities (his business designs and builds electronic audio equipment inc pcb's and writing software) for circuit board repair but he is usually very busy so it would be good if I can show him what and where need to be checked and what the results should be. I have downloaded the pdf circuit diagram and can see the the section with RX and TX connections but I am a little stuck as to what I do next!

Thanks for all the help so far.

John

Re: Not the usual comms problem

Posted: Wed Oct 10, 2012 4:33 am
by Matt Cramer
I would put the scope on the serial connection and see if the signal is making it from the cable to the RS232 chip to the CPU pins.

Re: Not the usual comms problem

Posted: Wed Oct 10, 2012 11:37 am
by tsoldrin
Thanks for all your help Matt!

I will be dropping it off with my Electronics Dave tomorrow for him to look at.

Cheers

John

Re: Not the usual comms problem

Posted: Wed Feb 20, 2013 9:36 am
by tsoldrin
After a brief pause for winter I am back at this continuing comms problem.

My friend inspected the MS and couldn't find and problem with the RS232 chip.

I have refitted it to the bike and the MS works well and the bike even starts and runs reasonably considering I had only put a basic map onto it to before the connection problems started. There is just no connection to computer at all.

The problem started when I discovered that I had left the serial cable attached to the bike and it had got damaged and had probably shorted out (I seem to remember that the ignition had been left on too)

list of what I have checked so far

replaced the serial cable

checked the settings on the laptop/s (I have 3 that can run tuner studio on)

belled out the MS loom from jack plug to ampseal and checked the jackplug too

tried to reload the MS but just get a " no connection" error message

removed the MS for inspection.

Have you got any more suggestions as to what to try?

Are there any UK specialists that can test/ repair MS?

cheers

John

Re: Not the usual comms problem

Posted: Sat May 14, 2016 2:35 pm
by hecmac
Hi mate,

I have the very same problem, almost identical in circumstances. Did you ever find a solution?

Cheers,

Hec