toplessFC3Sman

iTrader: (1)

Hello again, It's been a very long time since I've posted in this subforum... some of that is because my MS2 has been working very well, some of that is because the engine it was controlling lost a coolant seal and life got in the way of fixing it for a while (new house, baby boy, etc...). Anyway, I've rebuilt the engine and got it back in the car, and it starts up and runs very nicely on the old tune from a number of years ago (as it should). I can connect to the MS and adjust the tune using TunerStudio on my laptop with a USB to serial adapter, but when trying to use MSDroid on my phone with the serial to Bluetooth adapter (the one that EFIanalytics sells), I can connect to the adapter but MSDroid says that the MS2 firmware signature is not recognized, and that it cannot connect.

The back-story is that in the 2 years the car was parked, my old phone (a Samsung Galaxy S - before they started numbering them) was at the end of its life and got replaced by a Motorola Moto G3, so I had to reinstall MSDroid on the new phone. Before parking the car, the old phone and the same bluetooth adapter worked flawlessly for connecting to the ECU, adjusting the tune, etc. The MSDroid installation on the new phone refuses to connect because of the signature recognition problem. I have an MS2 with the V3 board, running MS2extra alpha 303w (dated 2010-10-23; I think I got it from muythaixbr on this board a while ago). Sure, this version of the firmware is pretty old (actually, a bit older than i realized before looking it up... sigh...), but is there any reason that MSDroid wouldn't be able to work with it? Are there any files that I could salvage off of my old phone that would work to allow MSDroid to recognize the signature?

Thank you very much,
Pete

toplessFC3Sman

iTrader: (1)

After playing with it a bit more, I was able to get it working. What seemed to do it was putting the mainconfiguration.ini file that I had on the Tunerstudio laptop for the version of the MS2extra firmware onto my phone in the MSDroid folder, then restarting MSDroid, the car, and creating a new project when it connected. Now it seems to work fine, so I wanted to post up the solution here in case anyone else ran into issues.

Thanks

Aaron Cake

iTrader: (1)

Glad you got it going. Is there any reason you are running very old non-production firmware?

toplessFC3Sman

iTrader: (1)

There's no specific reason that I'm still running it - it was something that muythaibxr had been working on at the time to fix some rotary-specific issues, and he sent me his alpha. It fixed the issues I was seeing, so I just kept it. More recently, I've had the engine apart to rebuild it over the past year, and didn't want to change too much at once in case I needed to trouble-shoot things. After the rebuild, the car started almost immediately on the old tune, but since both the old phone and old laptop I had been using for tuning prior to the rebuild had died, I was a bit limited in tuning & flashing capacity.

The biggest thing that I had wanted that wasn't in the firmware that I am using was sequential injection control, but since it seemed (at least a few years ago) that the rotary settings and additional counter usage for the trailing spark prevented it on the MS2, I hadn't really been keeping up with the new firmware releases.