MSDroid - Android dash, tuning, and log viewer!

[Trev16v]

You guys need a "donate" button on the Play store so we can buy y`all a beer occasionally.

What we've done is set up an MSDroid page on JustGiving to raise for cancer research:

http://www.justgiving.com/MSDroid

[gslender]

Will investigate MS3 issues tonight.

I'm still getting a failed connection - during the "reading signature" phase in the status page I see these 3 strings...

1) The correct signature for the MS3 Pro 1.2.1 firmware - MS3 release 1.2.1 20130316 16:55GMT (c) JSM/KC ********

2) Then the correct revisions string for the ini - MS3 Format 0262.07P

3) Then some garbage characters... only about 4-5 of them... but just wierd...!?@

It repeats this about 3-4 times then gives up.

As mentioned before, the two other Droid apps work fine and have no problems connecting first time.

G

[Trev16v]

Haven't had a chance to look yet but I wonder if it's screwing up when it should actually be politely telling you that it doesn't have the required definition file. Did you add the .ini? As it doesn't ship with that .ini yet and we haven't yet put it on the server so you'd need to add it.

[Trev16v]

BTW - SD card msdroid/ini/ directory.

[gslender]

Ahh, that would be it!

So does the fact that the firmware sig is the same but the ini revision is different cause problems? Eg. The ms3pro ecu signature is the same as the std ms3 sig, but they require different ini files I think....?

I will try and copy the ini into the SD card on the phone in the next few days when I get back home.

Thanks
G

[jsmcortina]

Ahh, that would be it!

So does the fact that the firmware sig is the same but the ini revision is different cause problems? Eg. The ms3pro ecu signature is the same as the std ms3 sig, but they require different ini files I think....?

The signatures are different and match the ini files.

James

[gslender]

Ahh, that would be it!

So does the fact that the firmware sig is the same but the ini revision is different cause problems? Eg. The ms3pro ecu signature is the same as the std ms3 sig, but they require different ini files I think....?

The signatures are different and match the ini files.

James

Mmmm curious, what part of the sig above in point 1) changes to show it is from a ms3 pro?

G

[jsmcortina]

Mmmm curious, what part of the sig above in point 1) changes to show it is from a ms3 pro?
G

That's the version string, not the serial signature.

James

[gslender]

Mmmm curious, what part of the sig above in point 1) changes to show it is from a ms3 pro?
G

That's the version string, not the serial signature.

James

Yes, terms are confusing!?

I was trying to explain, the version string, called signature S cmd in the protocol, is the same between both the ms3 and ms3pro, but they use a different serial Revison R cmd signature. that's not common or typical that a ecu firmware can have two different ini files right?

I'm wondering if that is upsetting MSDroid?

G

[Trev16v]

No, it's the ini being missing that's upsetting it. It's supposed to inform you properly. Will fix properly after work. Yep, for MS3 and pro you have two ini files to cover both. Pro has extra P in signature IIRC.

MSDroid also being misleading in showing you the version sometimes in place of signature. More to fix.

[jsmcortina]

The long text version string with the copyrights is for display to the user only.

The shorter serial signature string is for ini file and protocol matching and should not be shown to the user.

The origin of the S/Q commands might be vague, but that's how the two strings should be used, this has worked this way with all MSEXTRA firmwares for a good 9 years now.

James

[racingmini_mtl]

I wanted to let people know that MSDroid now can read the signature of the IOx and the CAN-EGT. There is still a small bug where the different ini switches are not correctly set as per the user selection but Seb is aware of it. So I needed to do a small change in the ini and this is what the DIYAutotune CAN-EGT output looks like on my Nexus 7 connected the USB port of both devices (on-board FTDI chip):

CANEGT_MSDroid_Nexus7_small.png

Please not that this is half the real resolution so that it's not to big for the post. You can also see in the lower left corner that the frame rate is more than 35 which is more than fast enough. And no, those are not actual measurements but simply the maximum that can be read (in degrees F).

Jean

[93white3400z]

Awesomeness Jean! And yes I'm aware of the issue... but even better, it is already fixed for the next version.

[gslender]

I will try and copy the ini into the SD card on the phone in the next few days when I get back home.

After placing the ms3pro.ini in the correct /msdroid/ini location, the app now connects and works. Great!

Note: I found that using Dropbox as an easy way to copy/export the files to the right place on the SDcard... really easy and avoids needing the usb cable to manage the SDcard.

G

[piledriver]

I just email it to myself via gmail...
same for exporting logs.

[neverlift19]

what am I doing wrong? Is this up to date on 3.2.4 ms2?

[Trev16v]

Help me out here - I need full information about what your problem is!

It ships with the definition for 3.2.4.

[neverlift19]

Not sure what the issue is. I plug the phone into my serial to usb converter then into an otg cable(phone is an old galaxys on 4.2.2jellybro/cyanogenmod10) with the phone on msdroid but my ecu is never recognized?

Am I missing a step please help me out I'd love to log via phone

[turtana]

where can i download this other than google play ? my tablet dot support google play, the browser wont make secure connection.
eny help regarding a download source would be apriciated dearly.

[Trev16v]

I've put the latest APK on the website for you:

http://www.msdroid.com/builds/MSDroid_0_3a4.apk