MSDroid 0.3a0 Change Log

[TurboCamaro]

Is anyone else having trouble creating an "Air:Fuel Ratio" gauge?

Everytime I try it I get a gauge titled whatever the previous one I just did except it erases the numbers. All other gauges seem to work fine.

[93white3400z]

Everytime I try it I get a gauge titled whatever the previous one I just did except it erases the numbers.

I'm not sure what you mean by that, can you elaborate a bit more please ?

[TurboCamaro]

Sorry, I was being brief because I was posting from my 7" tablet.
So, if I tried to add in a new gauge or reassign an existing one, the gauge assignment would assume that of a gauge I had just change, or if it was the first gauge attempted it seemed to default to Engine Vacuum. And it would only display a single tick and number on the gauge but the needle would still be present. This occured several times until opening up the program just today and finding all of my assignments were as I had wanted. Now it has since forced a dash reset on me so I may get the chance to see that behavior again.

I was playing around with it today while connected to the Megasquirt (MS-1, MSnS-Extra 029y4, V2.2 PCB) and the program would crash on me quite often. It would happen every time I attempted to view either the VE table or the Spark table. I'd get the messege come up that said "Unfortunately, MSDroid has stopped." with the options being OK or Report. I wonder why it would happen everytime one of those tables was trying to be open. It also occurs when not connected to the megasquirt, The program restarts but will crash right away again if you try to view either table.

Have things like the Realtime Display been set up yet? Nothing comes up for me when I choose it. Also, Engine Constants 1 doesn't come up for me either...the page is just blank. Are these things that have yet to be filled in?

Thanks!

[93white3400z]

No problem. That's a pretty weird one about the gauges, I will see if I can reproduce it. And yeah, the gauges reset is pretty annoying. I think we should try adding the concept of "dead gauge" in case an output channel cannot be found after a firmware upgrade or something. Resetting everything to default when something goes wrong is a bit brutal.

The bug that crash the app when viewing VE/spark table has been fixed (it was happening only on MS1) and will be in the next release (hopefully Thursday).

No realtime display yet, those are part of the hard coded std_* dialog and they are a bit painful to implements. They will find their way in a future release for sure tho

[TurboCamaro]

Thanks for keeping us MS1ers supported!

[hardline]

It will not load on MS2/Extra3.3.0Alpha9. Stuck on reading Page 0

[Trev16v]

Hi hardline,

Sorry you're having issues. Is this the latest version (0.3a1) from Play?

Cheers, Trev

[hardline]

Yes it is

[racingmini_mtl]

Trev,

You are aware that the alpha 9 code uses basically the same serial protocol as the MS3, right? (You have to be careful about the blocking factor though).

Jean

[Trev16v]

Ah, thanks Jean! Wasn't aware, but will be straightfoward to enable MS3 protocol for it. That's a relief!

hardline, fix should be in the next weekly release for you. Planned before the weekend.

[LT401Vette]

Trev, also note the blockingFactor.
I'm not sure if you are supporting that yet or not, but on MS2 with the new Protocol data needs to be written and read in maximum blocks of 256 bytes.

[hardline]

Thanks guys for the assist. Much appreciated.

[Trev16v]

Many thanks Phil. I must admit I hadn't come across it before and just noticed it in the 3.3alpha9 ini (blockingFactor = 256) after Jean mentioned it.

Thanks to both for the heads up - it's much appreciated.

[nismoautoxr]

Hi Trev, I have a huge problem getting apps from google play . I keep getting "error retrieving information from server"

Google play has had several reports of this problem but as of Nov 2012 there has been no more updates on fixing the problem . I got the 02A1 build off or your build page but would like to get the latest version . Any chance of getting the latest off of a build page too?

Its not just your app that does it on google play for me so its nothing to do with your app...just an issue either on my end or GPs end.

[Trev16v]

Ah, of course - no problem, I'll just upload the latest .apk to msdroid.com for you right now! This might sound a silly question, but do you have the date and time set right on your device? I've found that access to Google Play misbehaves if your device's time and date are wildly out.

By the way, we were planning on doing a weekly build release from now, but we're too busy adding lots of stuff so the next one will probably be during the week!

[nismoautoxr]

thanks Trev. I have no idea whats going on with it . Its been a problem from day one with this thing when i got it for christmas, the date and time are good . I have gotten google play to work 3 times and each time was by creating a new google play account but I have run out of email addys to create one with. LOL. Any idea what could be up with that ? i havent found a way to delete an account once its added so Im kindof lost there.

[93white3400z]

Here it is:
http://msdroid.com/builds/msDroid_0_3a1.apk

The next version is coming along really good, I'm happy with the changes so far Hopefully we can release it early next week!

[nismoautoxr]

thanks ...got it on there and works good . You still working on AE tuning and engine constants pages?

[93white3400z]

Engine constants and all the "required fuel" stuff will be in the next release, I spend a lot of time yesterday on this and its done AE will probably have to wait a bit more but hopefully very soon.

[nismoautoxr]

I look forward to it . Nice app man . Keep up the good work!!