Adaptronic owners thread

[gslender]

Nice work and very impressed.... did it take you long? Was this a "learn Android" project or did you have a flying start?

G

[Lokiel]

Nice work and very impressed.... did it take you long? Was this a "learn Android" project or did you have a flying start?

G

I'm a software engineer by trade so coding isn't an issue - learning how Android does things was the biggest hassle but there's plenty of information on the internet to help with that. I really HATE Java though (Java enumerations are useless IMO, Ada had REAL enumeration types and even C++'s enumerations that are in reality "glorified constants" were more useful; also, WHY the hell doesn't Java define a byte type with range 0..255?)

I've created a few really small "home-brew" Android Apps before just to learn how to create Android Apps, including one that just logged Adaptronic data using the MODBUS protocol and Bluetooth but when I overlayed the data onto video, if you were critical, the gauges looked jumpy and laggy so I decided to use Adaptronic's new streaming protocol and USB interface to increase the data rate.

The App took me a while, mostly because it's been done in my spare time, there were weeks when I didn't even look at it and coding all the preferences was a real grind. I've spent a lot of time over the last 4 weekends tidying up the App, adding the "Peak" values functionality and writing the User's Guide for it. If this were something I did full time, I'd estimate it would take me at least 6 weeks from scratch.

The ECU input stream is handled in a class so it's not difficult to adapt this App to accommodate other ECUs, I just need need to know their data formal/protocol (unfortunately Haltech's appears closed-source - if anyone has this, please let me know).

I plan to add a few more features, such as Playback, where you can replay/analyse a logged session. This may actually be better as a separate App.

[gslender]

I really HATE Java though (Java enumerations are useless IMO, Ada had REAL enumeration types and even C++'s enumerations that are in reality "glorified constants" were more useful; also, WHY the hell doesn't Java define a byte type with range 0..255?)

Java has its place. enum types are really a class with built in methods to save you time, so unless that's important, I rarely use them unless forced.

Not sure if you know, but all number types in Java (int, short, byte) are all managed as 32 bit signed numbers by the JVM. So easier to work with any packed data as being an array of int and just be careful about the >> and other bit operators (most work as expected, but some edge cases don't).

The ECU input stream is handled in a class so it's not difficult to adapt this App to accommodate other ECUs, I just need need to know their data formal/protocol (unfortunately Haltech's appears closed-source - if anyone has this, please let me know).

Well, I can help with MegaSquirt if you're keen to support that... you may need to change the name of the app if you intend on expanding into other spaces ??!!

I'd be keen to see you support 10Hz GPS and have done some work on that before with Android and/or some embedded systems.

G

[Lokiel]

:
Well, I can help with MegaSquirt if you're keen to support that... you may need to change the name of the app if you intend on expanding into other spaces ??!!

I'd be keen to see you support 10Hz GPS and have done some work on that before with Android and/or some embedded systems.

G

I've investigated the use of a USB OTG hub so that an external USB GPS can be used instead of the phone's GPS and I can plug in the Adaptronic ECU too. It's feasible so now I'm on the lookout for a cheap 10Hz USB GPS (I have a Columbus V800+ GPS that can do 5Hz, it was about $50, and a G-Star GPS than can do 2Hz).

A MS version is something I could do, shouldn't impact the existing design since I have a class that does all the Adaptronic parsing so could swap that for a MS parser. There's an existing ShadowDash Android App for the MS though so there may not be much interest in a MS version of AdapTrackit.

Mark Booth, aka '95MSM on mazda-speed.com, has suggested the following additions/mods:
1. Display "High Threshold Hit" indicators on the minor gauges, these should remain active when the high threshold is hit (implemented)
2. Add shift light indicator (this weekend's task)
3. Lower rev-range tick marks should be "tighter", upper range ticks further apart (will make this configurable, on the track this is useful, when DD having them evenly spaced is preferable)
4. Implement a "hockey stick" RPM, where the "blade" has the lower revs and the shaft runs across the top of the screen (will make this configurable, "hockey-stick" or "semi-circle")

[Lokiel]

Android AdapTrackIt V1.1 Updates (2 and 3 were suggested by mazda-speed.com's '95MSM, aka Mark Booth - still have a couple of his ideas to implement):

1. Fixed default value for Boost minor Gauge.

2. Added Shift Light Indicators and associated configuration.
"Settings -> Shift Light Preferences" added to configure the Shift Light functionality:
* Enable/Disable Shift Lights
* RPM Warning Threshold
Shift Lights start when the current RPM is within this number of RPM's away from the Gear's "RPM shift point"
Defaults to 1000 RPM - there are 4 Shift Light indicators so each light corresponds to 250 RPM closer to the Gear's Shift Point with this default value
* Warning Colour
When within 75.001-100% (eg. 800 ) of the RPM Warning Threshold, one Shift light is displayed in this colour
When within 50.001-75% (eg. 600) of the RPM Warning Threshold, two Shift lights displayed in this colour
* Shift Colour
When within 25.001-50% (eg. 300) of the RPM Warning Threshold, three Shift lights displayed in this colour
When within 0.001-25% (eg. 5) of the RPM Warning Threshold, four Shift lights displayed in this colour (see attached .png file)
When the Gear's "RPM shift point" has been hit, the shift lights flash
* RPM Shift Points for each gear added
* "Settings -> Demo Mode" updated to include a "Gear (used for Shift Lights)" option
When in Demo Mode, this gear's RPM Shift Point is used to control the Shift Light behaviour.

3. Added High Threshold "hit" Indicators to minor gauges.
When a minor gauge's High Threshold is "hit", a circle is displayed inside the gauge to indicate this.
The High Threshold "hit" indicators remain displayed until reset by the "Show Peaks -> Clear Peaks" button.
The screenshot below shows an example of the High Threshold "hit" Indicator in the "Water Temp" minor gauge.
This allows the user to see if a High Threshold has been hit at any time.

Will update the User's Guide on weekend.

Installation Instructions:
1. Uninstall the previous version, if installed
2. Get the latest version from http://www.adaptronic.com.au/forum/index.php?topic=6235.0
3. Delete the ".zip" suffix from the attached .apk file
4. Copy .apk file to your device
4. Run the .apk file to install the App.

[Okibi]

Thanks, installed will play with the settings later.

ImageUploadedByTapatalk1446734085.150696.jpg

[Lokiel]

Thanks, installed will play with the settings later.

ImageUploadedByTapatalk1446734085.150696.jpg

There's a LOT of settings for maximum configurability but let me know if there's something else you'd like to add.

I added the Demo Mode largely to test the configurations without needing to connect the ECU so you can play around with them at any time.

This App has grown a LOT bigger than I expected, the more I used it the more features I wanted and I've had a few other requests too.

[beavis]

Really impressive. I await megasquirt compatibility. saves me having to make my own

[Lokiel]

Updated the AdapTrackIt User's Guide on http://lokiel.weebly.com/android-adaptrackit-app.html and added a couple of videos which I'll link here too:

The following YouTube videos demonstrate the App running in Landscape mode and Portrait mode.
In the videos, "Demo mode" is enabled, then Shift Lights are enabled and disabled again to demonstrate their function.
Refer to the User's Guide below for details.




I also added "Ethanol Concentration" as a selectable minor gauge and added it as a "Loggable" option (only useful if you have a Flex Fuel sensor).

[Lokiel]

Raining here in Brisbane so I updated the AdapTrackIt App to support multiple resolutions - now tested on 1920x1080 and 1280x800 displays, others should be OK, if not, please let me know.

See http://www.adaptronic.com.au/forum/index.php?topic=6235.0 and download adapTrackIt_v1_3.apk .

[Roadrunner]

Hey that's awesome. So much more usable and readable than the gauges tab on adaptive tuner.

Well done!

[cookie]

Stupid question alert.

I'd like to have a few physical guages in the car. I.e. wideband, oil pressure/temp, water temp. I'd also like to have the ecu keep track of these values and trigger alarms/limp modes- essentially piggy backing off the sensors themselves. Anyone done this successfully with innovate by linking them together with the serial cables then into the current via wideband input?

[Okibi]

I think TimK has.

[Lokiel]

Stupid question alert.

I'd like to have a few physical guages in the car. I.e. wideband, oil pressure/temp, water temp. I'd also like to have the ecu keep track of these values and trigger alarms/limp modes- essentially piggy backing off the sensors themselves. Anyone done this successfully with innovate by linking them together with the serial cables then into the current via wideband input?

That's what the Innovate SSI4 unit is for, your sensors connect to it and you can daisy-chain it with your Innovate Wideband O2 sensor's Serial Input into the Adaptronic ECU.

See http://www.innovatemotorsports.com/support/manual/SSI4_manual.pdf

The Adaptronic Select's serial stream even outputs the SSI4 data so it can be logged.

The Innovate MTX-L includes a gauge so you have a physical gauge.
Note: Adaptronic recommends the Innovate Wideband O2 sensor over most because it provides digital information to the ECU that indicates whether or not the sensor is actually ready (ie. warmed up and reporting valid data) - prior to this, any data is garbage so if the ECU cannot determine this, the car can Idle roughly.

[timk]

I think TimK has.

Yep, I have the sender for my oil pressure gauge also going into an SSI-4 input. For this to work your gauge needs to use a 10bar 0.5-4.5v transducer, not sure if they are common or I just got lucky.

If you have a different transducer (7 bar for example) but it still outputs the same 0.5-4.5v range, you can do the math and put the adjusted values into the Adaptronic to use the engine protection features, but the values being datalogged would be meaningless without conversion first also.