Megasquirt Support Forum (MSEXTRA)

Hey Trev,

It's been 3 or 4 months since you've engaged on the changes you were implementing for MSDroid.

Have you finished your house?

Are you still working on MSDroid?
MS3 Basic + FW1.5 + CAN device is broken and I'm really missing using it for quick tune mods.

If you need more information, please let me know.

Tony

Hi Tony,

I'm still very active on it, but unfortunately work and life pressures are getting in the way again. I'll do my best to try to catch up with support as soon as I can.

Sorry for this.

Trev

Hi Trevor,

It's now been a full year since the last functional update to MSDroid.

And, I have not been able to use MSDroid for tuning for almost the full year since it is not compatible with MS3 FW 1.5 and CAN AFR/EGO.
I can only use MSDroid for monitoring at which point I just prefer using ShadowDash instead.

Whenever I connect to the ECU a difference is detected and I need to select "Update Project Settings" to continue.
If I make a change and update the ECU, my CAN based O2 sensor stops working and I need to use TunerStudio to restore functionality.

From reading other threads it appears this is likely due to MS now using parameterized lists in its configuration.

Is there any plan to have MSDroid updated to support parameterized lists?
If so, is there any timeline?

I hate having to carry my laptop around for minor tuning and this is the main reason I purchased MSDroid in the first place.

For example (this is not exhaustive):
1) General Settings page:
Voltage Input Port shows $PIN_ADCS instead of Mainboard
2nd MAP Port shows $PIN_ADCS_OFF instead of off
2) Shift Light page:
Shift Light Output shows $PIN_DIGOUT_CANOUT_OFF instead of off
3) Torque Convertor Lockup page:
Output Pin shows $PIN_DIGOUT_CANOUT_OFF instead of off
4) Alternator Control
Current Monitor Input shows $PIN_DIGIN_OFF instead of off
5)AFR/EGO Control
AFR /EGO Sensor Mapping - Uses Sensor shows $EGOMAP instead of "EGO1"
6) CAN Receiving page:
Local variable / channel shows $CAN_RCV_VARS instead of off
7) Check Engine Light page:
Light output shows $PIN_DIG_OUT_CANOUT_OFF instead of off
Long Term Trim Settings page:
LED output shows $PIN_DIGOUT_CANOUT_OFF instead of off
9) SD Card Datalogging
LED Indicator shows $PIN_DIGOUT_CANOUT_OFF instead of off

I'm also very interested in this, recently got my ms3 tuned and running. Even more recent is the lenovo tab I bought and the apps I downloaded in hopes of running and Android dash.

Haven't been able to find ANY recent info for any of the apps (MSdroid, ShadowDash, RealDash), my rs232>micro USB and an rs232>bluetooth should be here soon.
I'm really hoping I didn't invest in a fossilized concept.

Aks.

Still very active; I'm actually spending several hours a day on average on MSDroid in between work and other commitments. However, I'm still struggling to keep up with a lot of support requests and fixes at the moment. I will get there eventually. I appreciate that me coming out with lots of words yet not having anything visible to show for it is hardly convincing, but I feel it's better than saying nothing at all.

Trev16v wrote:Still very active;

It seems that it doesn't support the current release of MS3 firmware though, this needs to be called out before customers buy it. I checked the Google Play download page and it says that there is full support for MS1/2/3.

James

You're right. It's bad and I take it on board. My problem is not so much lack of work on MSDroid, but more so poorly prioritising essential support and fixes against working away on shiny new stuff.

As mentioned in the other thread, I have now done the .ini preprocessor support to address the main issue reported above by VcrMiata, so I shall provide this fix (plus further MS3 1.5.1 fixes that I work on) in a beta release via Google Play at the weekend.

Cool, thanks Trevor!

Looking forward to the beta this weekend and being able to tune again.

Tony

I have now pushed beta release 2.6b1 to Play, which has two fixes: (1) fix for MS3 1.5.1 support as discussed above, and (2) a fix for the new table editor crashing on Android 4.x.

You'll need to be registered to receive releases on the beta channel. If you're not already registered, the details are in a thread in this section. But let me know if you get stuck.

Hi Trevor,

Thanks for posting the 2.6b1 beta.

What is the expected status of this beta?
I'm finding quite a few issues.

1) Opening almost all screens with tables causes the application to crash.
for example, the following non-exhaustive list all cause the application to immediately crash:
Basic/Load Settings
Rev Limiter
Alternator Control
Barometric Correction
Map Sample Settings
MAT Air Density Table
MAT/CLT Correction
Fuel Settings
Injector Dead-Time/PWM
Injector Small Pulsewidths
Ignition Settings
Dwell Battery Correction
Cold Advance
MAT Based Timing Retard
---> and many, many more

2) Parameterised lists not using default overrides.
For example:
Note: my TunerStudio .msq file shows mapport configured as "Mainboard"
<constant name="egoport1">"CAN EGO"</constant>

Page: General Settings->mapport (Voltage Input Port) is showing "JS5 (ADC6)" instead of "Mainboard".
mapport has the following definitions:
mapport = bits, U08, 242, [0:5], $PIN_ADCS, 0="Mainboard"
this should override the $PIN_ADCS list which is defined as:
#define PIN_ADCS1 = "JS5 (ADC6)", "JS4 (ADC7)", "EXT_MAP (ADC11)", "EGO2 (ADC12)", "Spare ADC (ADC13)", "MAP", "INVALID", "CAN ADC01", "CAN ADC02", "CAN ADC03", "CAN ADC04", "CAN ADC05", "CAN ADC06", "CAN ADC07", "CAN ADC08", "CAN ADC09", "CAN ADC10", "CAN ADC11", "CAN ADC12", "CAN ADC13", "CAN ADC14", "CAN ADC15", "CAN ADC16", "CAN ADC17", "CAN ADC18", "CAN ADC19", "CAN ADC20", "CAN ADC21", "CAN ADC22", "CAN ADC23", "CAN ADC24", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "EGO", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID"
#define PIN_ADCS = "INVALID", $PIN_ADCS1

$PIN_ADCS needs to be translated to show "Mainboard", not "JS5 (ADC6)".

Another example:
Note: my Tunerstudio .msq shows egoport1 as "CAN EGO"
<constant name="mapport">"Mainboard"</constant>

Page: Fuel Settings->AFR/EGO Control->egoport1 (EGO 1 Port) is showing "EGO" instead of "CAN EGO"
egoport1 has the following definition:
egoport1 = bits, U08, 40, [0:5], $PIN_ADCS_EGO, 7="CAN EGO", 38="INVALID"

#define PIN_ADCS_EGO = "EGO", $PIN_ADCS1

This is not right at all and suggests something wrong with the .apk I built, because it doesn't appear to have incorporated my fixes. This is what happens when you rush out a build just before going to sleep in a hotel room!

Sorry for this - I'll investigate this evening.

VcrMiata, what is the device and Android version you're using, please? When 2.6b1 has crashed on various tuning pages, could you please ensure that a crash report is submitted to Google if you're given the opportunity? I have a separate issue in that our own separate crash reporting system isn't currently reporting from the beta, so I don't yet have any crash reports from your device. I speculated that you're using Android 4.x on which the table editor was known to crash, but that's fixed in 2.6b1.

The other fix is in progress but I'm still trying to understand the above issue.

Wait! Ignore that. I was being retarded. I've found the bunch of crash reports from the beta from the curve editor crashing on a Galaxy running Android 7.0 which must be you. Cool.

Hi Trevor,

Yes, it's android 7.0, on a Samsung Tab S2.

Do you need a crash report?

Tony

Hi Tony,

Many thanks, and I have what I needed after all -- I found the crash reports your device had already sent. I've now pushed 2.6b2. It has fixes for the above issues. Work continues.

Regards
Trev

Thanks Trevor!

Looks like some pretty good progress here.
==> Crashes no longer occur
==> Most parameter lists fields were displaying properly (except for 1 that I found so far)

I'm working my way through the screens as I have time and will add more later.

These tests just check the field values / table cells against TunerStudio.
I have not done any tuning write tests yet - probably won't until the values match with TunerStudio
Note: I think the KPH vs MPH difference is not significant for write tests as the values appear to be adjusted correctly).
Here are my results so far:

Basic/Load Setting
. Engine and Squential Settings : Good
. General Setting : Good
. Rev Limiter : Good
. Shift Light : Good (although I have this off)
. Engine State Settings : Discrepancy Noted
.. VSS Threshold : TunerStudio shows (KPH) and values : MSDroid shows (MPH) and values
. Tacho Output : Good
. Fan Control : Discrepancy Noted
.. VSS Shutoff : TunerStudio shows (KPH) with kph value / MSDroid shows (MPH) with mph value
.. VSS Hyst : TunerStudio shows (KPH) with kph value / MSDroid shows (MPH) with mph value
. Torque Converter : Good (although I have this off)
. Alternator Control: Good (graph enabled/disabled is also good)
. Barometric Correction : Good
. MAP Sample Settings: Good (although I have this off)
. ITB Load Settings : Not used (disabled)
. MAF Settings : Good (although I have this off)
. MAF Flow Curve : Not used (disabled)
. MAF/MAT Correction Table : Not Used (disabled)
. MAT Air Density Table : Good
. MAT/CLT Correction : Good
. Real Time Display : TunerStudio shows real time dialog : MSDroid shows MAT/CLT Correction settings
. Feature List Showing I/O pins: Discrepancy Noted
.. page 2: Gen PWMA Output: TunerStudio shows CANPWM1 : MSDroid shows $PIN_DIGOUT_CANPWM
. I/O Pins list: Good
. Expansion I/O pins List/Usage: inconclusive : Only tested when offline
. Gauge and Settings Limits: Good

Fuel Settings
. Injector Dead-Time/PWM : Discrepancy Noted
.. Inj Parameters selection (same/individual) field is missing in MSDROID (also missing title on page 1)
.. Ordering of curve 2 and 3 are reversed (i.e. curve 3 is shown before curve 2)
. Injector Small Pulse widths : Discrepancy Noted
.. Ordering of curve 2 and 3 are reversed (i.e. curve 3 is shown before curve 2)
. AFR/EGO Control : Good
. Injector Timing : Good
. Staged Injection : Good
. Fuel Sensor Settings : Good
. Overrun Fuel Cut : Good
. AFR Table 1 : Good
. EGO Authority Table: Good
. EGO Delay Table : Good
. AFR Safety System : Good
. Fuel VE Table 1 : Good
. Fuel Pump and Pressure Control: Good

Advanced Engine
. Speed and Gear Sensors : Discrepancy Noted
.. page 2 : Preferred Speed Units : TunerStudio shows KPH : MSDroid shows MPH
. Shaft Speed Sensors : Good
. EGT / Thermocouple Inputs : Good
. Generic Sensor Inputs : Good'ish - Field Name is not provided in MSDroid
. Accelerometer Parameters : Good
. Traction Control Settings : Good (although I have this off)
. Launch Control/2-Step/3-Step/T-Brake : Good (although I have these off)
. Speed based Launch Control : Discrepancy Noted
.. RE-arm Below Speed : TunerStudio shows (KPH) and values : MSDroid shows (MPH) and values
. Sequential Shift Cut : Good
. Nitrous System : Good
. Water Injection : Discrepancy Noted
.. Can view table but cannot get to the field settings
. High Power Time Enrichment : Good - however graph is not disabled out when enrichment is off
. Oil Pressure : Good - however graph is not disabled when oil pressure sensor is off
. Pit Lane Limiter : Discrepancy Noted
.. Speed : TunerStudio shows (KPH) and values : MSDroid shows (MPH) and values
.. Speed Control Range: TunerStudio shows (KPH) and values : MSDroid shows (MPH) and values

Hi Trevor,

Is there a timeline estimate for the next incremental release?

Thanks,
Tony

Hi Trevor,

Any update or feedback on my test input for you?
It's been over a week with no response.

Perhaps I can synchronize with your development availability.
I am more than happy to help do some extended testing but I need to know that my efforts are helping to improve your application, are appreciated, and especially; not falling into a bit bucket.

Let me know when you have some extended time set aside where you can promote changes/fixes and I'll see what I can do to help with fast turn-around on testing.

[Edit update: the beta does not seem to support your extended table functionality - I can't do anything to help testing those areas.]

Thanks,
Tony

Hello Trevor,

Any update available?

2 months since last beta and last engagement.
I am hoping you are well.

Any chance of fixing outstanding issues and releasing a production version?
I still want to help in any way I can but I'm getting close to cutting my losses.

Note: you have a unique product in the MS domain, a portable tuning app. But it has not worked for over a year now when using MS version 1.5.1, and that's a real shame.

Tony