MSLogger 4.1 preview ** SCREENSHOTS **

[93white3400z]

Hi everyone,

Last week, I've forked MSLogger from Dave on github. I've been pretty actively working on it and improved a few things. From the solid work Dave have made, I fixed MS3 implementation (still have trouble loading constants page, need info on that), fixed a bunch of crashs, some code cleanup/commenting, made the gauges a bit more pretty and fixed a text scaling issue with them, added a super basic log viewer (to be improved), added menu icons, etc.

I still have to talk to Dave about officially releasing a new version but I guess I can send apk file if anybody want to try it.

Code is available at https://github.com/scudderfish/MSLoggerBase for Phil... erm I mean anybody to look at . Feel free to fork it and help us make it better!

Feedback welcome!

[gslender]

Cool. Send me the APK if you will.... Got a link I can get it from?

G

[93white3400z]

Hi Grant,

I've uploaded an apk on github https://github.com/sebgiroux/MSLoggerBase/MSLogger4.1.apk/qr_code. I've just added support for your firmware (MS2Extra SerialGS26) because I suppose that's what you want to use. I have no MS2 so I cannot test, let me know if it doesn't work.

[AdamR]

It isn't working for me. I am still using MS2/E ver 3.2.1. I will be upgrading soon, though. I will let you know then.

[gslender]

Didnt work for me too

[93white3400z]

You can download a new file here: https://github.com/sebgiroux/MSLoggerBa ... pk/qr_code Lots of improvements in the last week.

But guys, I will need more info then that to be able to help you. AdamR, I've just added 3.2.1 support (which is included in the file above). If you were getting an error about unsupported firmware, you can try again. If not, I've also modified the code to consolidate the app log into a single file so it's easy for you guys to send us the file to debug. Again, more info about whats going on is always welcome. If it's a crash, the debug log is where the stack trace would be and that would help a lot.

Me and Dave don't have an MS2 (he have an MS1 and I have an MS3) so more MS2 feedback would be welcome. I'm pretty sure it was working at some point so if we broke something, I guess we will be able to fix it pretty quick, with your help

Any person that is serious about wanting this app, we will try to do what we can to make it work for you. It already should work for any MS (once we had the support for your specific firmware, which take about 2 mins to do). If I could get a bunch of firmware ini, I could add support for all of them pretty quick actually.

[gslender]

Any person that is serious about wanting this app, we will try to do what we can to make it work for you. It already should work for any MS (once we had the support for your specific firmware, which take about 2 mins to do). If I could get a bunch of firmware ini, I could add support for all of them pretty quick actually.

Can you make it fall back to generic support of the nearest release it relates to (ie match the string based on the first N characters of the signature) - for me it just didn't provide much feedback anyway, it just tried to connect, and failed... I can't remember but it wasn't very informative as to what went wrong.

I'm a fairly good Java developer and if you send me build/environment setup instructions I have a MS2 & JimStim setup always connected to my Mac that I can use to report bugs etc >> gslender @ gmail dot com

G

[93white3400z]

I have thought about that and I think it would a great idea. For a readonly app like that, I think it's good enough. Worst case scenario, you won't get access to the latest gauge added in your newest release and that's about it. We can add a message that say something like: "We don't currently support your firmware MS2extra X.X.X, we will inform the developers about it and for now you can choose the closest firmware to yours in the list below: ...". I think I will indeed have to do that. I will email you the information about getting your development environment setup shortly!

[piledriver]

Just gave the latest apk a run, it d*** near worked on my piddly little HeroC running cyanogenmod.

It connects, properly IDs gslenders 2.6 firmware, loads 7 pages... then drops the connection.(but doesn't seem to realize it, still says connected)

That's further than it made it before with the original versions, I could never get a connect IIRC..

[93white3400z]

piledriver, I guess this is progress If you could make sure you're logging in debug (go into the app preferences and scroll to the bottom, click on logging level and make sure debug is checked), then you can send me that log and I should be able to help

[93white3400z]

New version available at the same URL: https://github.com/sebgiroux/MSLoggerBase/MSLogger4.1.apk/qr_code

gslender's firmware should work now, thanks to piledriver for the help! We still get some feedback about clunky Bluetooth connect/reconnect/etc. We will work on this soon

[93white3400z]

And I've just updated the apk again (same URL). The Bluetooth connect/reconnect should work much better. I had no problem with connect myself, but disconnect/reconnect was hit and miss (up to 1min reconnect). Now, it seems to be 100%. It might even help for initial connect for some people, who knows.

[piledriver]

Once I turned the log level back to errors only, I'm getting 13.5-14.5 FPS~, which is same>better than SL with no gauges and ~as fast as my laptop with BT--- BT is the speed limit here.

Still had to run msdroid or SL first to init BT or it stalls loading page1, and it still thinks it's connected and fights being reset, but rock solid once running.

Will play again in AM, just about usable.

[93white3400z]

So sounds like we are making progress I don't see why running SL or msDroid before MSLogger would have any effect on BT tho. If you get to loading page 1, that mean the BT is already initialize and the signature from MS was received properly. If you reply here with an attached debug log (switch back to logging level verbose) of a connect attempt that get stuck to page 1, that would help a lot

[piledriver]

Will do, as that's the "default" behavior..
All the logs I have sent previously should show that.
Now just takes a bit of playing silly buggers to get it going, but once it does it seems to work very well.

Took a nice long log (~45 min driving to work) and it seems to have issues loading it in mslogger to view 9MB logs, but MLV seems to like it just fine, just had to turn off "fill time gaps" it sees every few seconds.

The .frd that also seems to get generated converts and views just fine as well.
(not really needed ?)

The .frd seems to have the units right, the .msl seems to have the temps in C.
Time intervals in the .frd also seems to be MUCH more consistent, solid 13.5+ FPS.

[93white3400z]

Thanks for the logs man, they are once again very helpful. I see a few issues just looking at them. You're also right about the .msl, I do see gaps sometime too, I will look into that. We should be able to resolve all those issues pretty soon, I will let you know once it's done

[93white3400z]

New version available at the same URL: https://github.com/sebgiroux/MSLoggerBa ... pk/qr_code

Here is the changelog:
- Try longer activation page delay to see if it help for some users
- Don't swallow exception in ECUFingerprint (would have been useful to have that exception in the log )
- logException now have same format as log in DebugLogManager
- Add a progressbar and time remaining to datalog viewer when loading a datalog
- Don't display first calculated RPS as .0

The first one is the main one to hopefully fix your page loading issue. I'm really not sure it will fix it but it's worth a try. Connection was waiting 50ms to get page response for your specific firmware, now it's at minimum 200ms for any firmware. I had that problem with getting the MS signature before... at 100ms timeout it was too fast (but only at reconnect, first connect was fine.... go figure ) and at 200ms its working every time now. Just have to figure out the fudging factors like Dave would say

About the datalog temp units, I'm not 100% sure either but I think TS use the project configuration to rescale the temp. Is it possible that your MSLogger and TS are not configured with the same temp units ?

I've also added a progress bar and time remaining when loading a datalog so you have an idea of it will end before Christmas

And about the msl having random gap, I haven't figured that one out yet.

Again, thank you for taking the time testing this, it does help a lot!

[AdamR]

I have gotten a connection a few times, but the gauges are static and it stays on the "loading page 1" dialog. I'm currently using 4.1 and MS2 3.2.1

[93white3400z]

Seems like same MS2 issue. When did you download your copy ? Make sure you're using the latest version I uploaded last night.

[piledriver]

For giggles, run msdroid first, close it, then try mslogger.

That's the only way I've been able to get it going properly, and it appears to work GREAT as long as you don't shut it down.