TunerStudio on Android?

[LT401Vette]

Still in the early stages, much to be done. I don't expect to have anything ready for early testing until spring. That won't start out as a full TS on Android, but at least will data log and give some info. Then I will grow the capabilities from there.

[AutoXinVR6]

I volunteer for BetaTesting haha.

By spring I should have an E30 running on MS2/e and my upgrade is in spring so I should have an extra Droid1 doing nothing. And I live in VA...

[scudderfish]

FYI, I'm developing some logging & display software for the Nokia N900. It does simple display of RPM/MAP/AFR and binary logging wich can be converted by TS into something useful. It won't work on Android or iPhone though.

[20B3rdgen]

I have a EVO 4G running Android 2.2 and am willing the beta test it.

[dglatz]

Yup! I need this too. Much more convenient than packing the old laptop around.

[Quan-Time]

I stumbled across this by accident !

Ive been throwing around the idea of getting a serial->bluetooth dongle, plugging that on the MS unit, and having my phone (android) connect to it that way. Did a quick bit of research on it, and all the library files are there for it. Even if its just logging or a basic RTD (real time display) much in the way that palmlog worked.

I could throw some code together fairly quickly for it, i just dont have a dongle to test with. If i get my butt into gear i could get one and see how i go with it. Shouldnt be too hard.

[MS2tester]

don,t know if you are aware of this thread but they seem to have more luck with a wifi adapter
http://www.msextra.com/forums/viewtopic ... ne#p264326

[y8s]

I stumbled across this by accident !

Ive been throwing around the idea of getting a serial->bluetooth dongle, plugging that on the MS unit, and having my phone (android) connect to it that way. Did a quick bit of research on it, and all the library files are there for it. Even if its just logging or a basic RTD (real time display) much in the way that palmlog worked.

I could throw some code together fairly quickly for it, i just dont have a dongle to test with. If i get my butt into gear i could get one and see how i go with it. Shouldnt be too hard.

The apps aDyno, Torque and OBDroid I believe can all interface over serial to bluetooth adapters. I've used a couple of them and they seem pretty solid once connected. Torque has a nice interface that you can change to your liking similar to the TS dash, but it's limited to OBDII data. I use it with a bluesmirf bluetooth-serial and ScanTool.net OBDLink S.

I don't see why that same setup can't be implemented even if it means limiting the transfer rate for realtime displays.

Here is some linkage to help your butt get in to gear:
http://www.amazon.com/Adapter-Bluetooth ... B000CPMBO6
http://www.sparkfun.com/commerce/produc ... ts_id=8495

Development thread for OBDroid:
http://www.mp3car.com/vbulletin/engine- ... -tool.html

[Quan-Time]

http://developer.android.com/guide/topi ... tooth.html

Have a read.. Its fairly straight forward. Once a connection can be established, then its just normal serial crap. My honest opinion (approach) would be to send (i THINK) Q down the line, get a version response. Could be something other than Q,, i cant remember.. Have to read the doc's.. no biggie.

Point is, once you got it, can get a response via BT->serial, just tell it to spit out data, log that bitch.. Once you have a sample file, make a nice GUI for it. Have say... 5 RTD going, each one is a drop down menu. So ANY reading which is avail (basically anything in the log file) a dropdown box can select that data.. RPM, PW, WBO2, TPS, etc.. 5 can be "displayed" at any time in text format, but all is directly logged. Saved to your SD / microSD card, bingo.. new logging device.
Once BT is working, i cant see it being overly hard to expand on it. Just have to get myself a BT dongle.

If i did this, would anyone be hugely interested / want it ? Please note that you would 100% NEED a BT dongle too.. So it would cost a few coins on your end. If this is needed / wanted by others, ill grab a dongle and start hackin some code / dev work.

I have a HTC Desire, FroYo 2.2, "locked" all legit, etc.. I could put the app to market, but id prolly start with just the .apk file for others to install and beta test. A variety of different brands would be nice, else a "everyone get this brand / model only" would be the go.. To ensure 100% compatibility.
Worth having a shot at ?

PS: any code i do would be 100% free, no cost, no add.. Free as in "freedom", source code provided too for others to mess with / make me a decent GUI.. my graphics skills REALLY suck. As does my creativity.

[y8s]

I'm happy to beta with my BT dongle. Just have to install my MS3X first.

[Quan-Time]

For me, the main priority is getting a simple SMALL logging device. Ive 'squirted my motorbike, so having a laptop is not really practical while riding around. Im sure it could be expanded in the future to being a tuning device but thats a bit beyond my ability, BUT im sure its possible to do.
Once i get some communication, ill throw the whole lot on git-hub for others to build and expand on.

With MS3X, you have a built in logging device already. Thats my intended purpose at this point. With that said, you can get access to a RTD which may be of use to you.

Ill have a hunt thru some code examples of data logging and BT communication and see what i can come up with. Plus ill have to get a BT dongle. Theres a few cheap ones on ebay which may do the job. Ive also found a nice cheap one on sparkfun which is a dev board. Id be able to hide that inside the case, even on a microsquirt, and power it internally, leaving full 100% use of the normal RS232 connector. Im a hardware guy, not a software guy. So you will have to allow me a bit of time to smash some crap code together.
Once i get the gear and start "properly" working on it, ill make a new thread and go from there. Watch this space ;)

[Quan-Time]

ugh.. after doing some research on BT stack's on android, it explicitly NEEDS "pairing". Not all BT devices support it. So will have to find one which does. Either way ive got a BT keyboard here which is a pairing enabled device, which is basically a "secure" connection method. Helps prevent sniffing, multi or ghost hosting, etc..

Have to do some homework on this.. *sigh*

[djandruczyk]

After searching extensively, I ordered an Aircable Serial 5 RS232 bluetooth adapter. Can be powered by RS232 pin 9, via a wall brick, or via a usb adapter cable (included), and is the only one I found that you can disable the flow controls lines (3 wire serial) which is what MS uses. It's also programmable and seems to be OSS friendly, with docs, toolkit, api info. the 5X model includes a battery and stubby antenna for longer range, but its more pricey at $129, though the battery feature is a nice bonus, which saves from having to mod the MS board, or hack in a power connection

$79.00 from http://www.aircable.net/products/serial5.php

Too bad I don't have any android hardware yet, and Apple has screwed the (open/OSS) dev community with regards to bluetooth, though my planned iphone apps wil be for jailbroken phones only (via the cydia store) at least to start, since my apps would never be approved in the apple store anyways due to using "private" (bluetooth serial) api's)...

[JustinHoMi]

This summer I wrote an Android app that just does logging and shows some values. Right now everything is hardcoded to MS-I hr10g... but I'll try to make it more generic and post something as soon as I get a chance.

[Quan-Time]

ohhhh interesting. How did you connect to the MS ? With a BT dongle and the BT stack API, could prove to be a bit of a weapon for data logging.

As for changing it to be "universal", it wouldnt be too hard. Got a screen pic of the app ? Ive also been looking into drawing a gauge or 2 on screen, which are user selectable.. IE: 2 gauges, which can be most anything from a pre-select group. RPM, TPS, CLT, WB02, etc...

[JustinHoMi]

Yeah, I used a bluetooth dongle with the standard bt api. It logs at about 9hz with MS-I. I haven't taken a screenshot. No gauges yet... just text. I need to make them user-selectable. It's quite handy, especially when racing or working under the hood. I'll take a screenshot as soon as I can.

Actually, I think I did make it so that it would work with any version of MS-I.... I'll plug in the MS-II sometime and get that working.

[Quan-Time]

oh wow.. so you basically did what i was planning to do. One thing i want to do is make it display firmware version, and have it auto log on start up, with date-time.log style. Id have 2 "tabs" at the top.. One tab for RTD, 2nd tab for "options".. such as what gauge to actually show, and current firmware version, program version, and a few settings which may (or may not) be required. Wouldnt be hard to make at all. Even easier now that you have done the hard yards.

[LT401Vette]

Nothing new here, shooting for spring 2011

[sshamuss]

Don't let this die. I'd be willing to pay good money. Most apps go for .99-5.99, I'd be willing to pay up to 30.00 for this app. Surely the free market system will prevail!

[Quan-Time]

ive halted my code stuff until i see what JustinHoMi has done. If nothing is posted up soon, ill just finish what i started.

AS for price, as with most things i do, it will be FOSS (free, open source software). Full code will be provided to those who ask in case they want to tweak it / bug fix it, etc..

Point is, i KNOW now its possible to do. And i honestly suspect anythnig with a 2.0+ BT chipset will do it, 2.1+ would be nicer as it has a better paired key exchange. No huge deal, but something to look out for on the compatibility side of things. Theres not many 2.1+ dongles around, so id probably be aiming at 2.0+EDR.
With that theres also 2 options..



These are both linked from sparkfun, so credit to them for the pics. The top one would require some hacking to get it into your MS unit. Its a 1.8v - 3.3v power, and more of a dev thing. The beauty of this solution is total integration, its ALWAYS there / powered on if the MS unit is on, and you can still use your normal RS232 cable + laptop / whatever if you wish.. So you could technically log with BOTH devices (android phone + laptop) at the same time.
With just a dongle, you would have to leave it on, and you would need to power it some how. One way ive thought of is getting a 3.5mm stereo jack, and making a short break out wire to power the sucker. So this still requires some level of modding your MS unit, BUT if you were able to assemble it, im sure you can do this.