Shadow Dash. What does this mean?

[walterclark1]

Right hand column second gauge down of the dashboard. Lambda has a red circle with a slash. This a gauge plus an "indicator" placed behind it. running SD 1.43 on a Nexus 10 with 5.1.1

Screenshot_2015-12-07-15-55-56.png

Same exact file on my Galaxy S4...gauge works fine.

Screenshot_2015-12-07-15-55-56.png

Part of the .dash file is attached. I cant include the whole file because of forum size limit. Hopefully this is the important stuff. The Lambda is from EGO Port 1 and its source is CAN EGO.

I dont know how to fix this.

[LT401Vette]

The red circle and cross indicates it is assigned to an invalid output channel.

What firmware are you running? Has the 10" tablet had internet access to pick up the correct ini?

[walterclark1]

Thanks, I suspected it meant something like that. Funny how the Nexus10 has an issue but the S4 doesnt. They use the same mainController.ini (I did a file compare using Windows command FC) that is located in the MS3 folder of the Shadow Dash MS folder on both devices. These files have for their first line of text: $Id: core.ini,v 1.269.2.39 2015/01/20 15:47:41 jsmcortina Exp $

The MS3 is running 1.3.4 I assume that is the firmware you are referring to. It gets Lambda digitally from the CAN thru a tinyIOX, sourced over I2C from a 14point7 SLC OEM wideband controller. As I wrote all this works well on the S4 via Bluetooth and with TS on a windows laptop connected via USB with the same dashboard. I have a second less elaborate dashboard, which I normally used with the S4, that has a digital number readout "Lambda gauge". I copied that .dash to the Nexus10 as a test and the Lambda gauge on that is not usable either.

The Nexus10 seems to be network connected anytime I am booted up. I have wi-fi everywhere here.

[walterclark1]

I have been comparing Shadow Dash files on the working S4 with those on the Nexus10. When I compared the file called project.properties in the S4 with the one on the Nexus10 there were some differences.

From the Nexus10:

#Project Attributes.
#ShadowDash by EFI Analytics, Inc
#Last Saved on: Mon Dec 07 14:01:31 EST 2015
#Mon Dec 07 14:01:31 EST 2015
projectName=MS3
canId=0
TriggersActiveTriggers=
ecuConfigFile=mainController.ini
ecuSettings=MPH|USE_CRC_DATA_CHECK|

From the S4:

#Project Attributes.
#ShadowDash by EFI Analytics, Inc
#Last Saved on: Sun Dec 08 15:18:14 EST 2013
#Sun Dec 08 15:18:14 EST 2013
projectName=MS3
canId=0
TriggersActiveTriggers=
ecuConfigFile=mainController.ini
ecuSettings=CAN_COMMANDS_OFF|CYL_12_16_SUPPORT_OFF|EXPANDED_CLT_TEMP_OFF|FAHRENHEIT|INTERNAL_LOG_FIELDS_OFF|LAMBDA|METRES|MPH|PORT_STATUS|PW_4X_OFF|

That last line...ecuSettings...had a number of differences with the S4 version having a bunch of statements, including a CAN statement - CAN_COMMANDS_OFF. Hmmm. Seems opposite of what I would expect, but...

I copied the S4 file to the Nexus10 to try it and the Lambda gauge works!

Both of these are WAY smaller than the same file used by my PC with TS however that file also has the CAN_COMMANDS_OFF statement along with a bunch of stuff related to thetinyIOX that the ones on the Androids do not.

Am I on the right path? What did I do to SD by swapping the files?

[LT401Vette]

That points more to it might not have the right ini.
Has that tablet had internet access when connecting to the MS3?

Check what ini file is in:
/Shadow Dash MS/MS3/projectCfg/mainController.ini

[walterclark1]

As I wrote previously, yes it does have internet access while connected to the MS3. And as I wrote before, the .ini that is on the Nexus10 (and was installed by SD, not me) is the same one as on the S4. I cant post it here because it is larger (908KB reported) than the forum permits (715KB). The first text line in the .ini file describes it as: $Id: core.ini,v 1.269.2.39 2015/01/20 15:47:41 jsmcortina Exp $. Same as on the S4 and my PC.

[LT401Vette]

Have you tried copying the project from the S4 over?

If you just delete the whole project, is all working fine again with the default dashboards?

I tried to load the dash above, but it looks like after editing it is no longer valid. Can you send the original dash via drop box or email?
Emailing support <at> efianalytics.com

[walterclark1]

Have you tried copying the project from the S4 over?

When I first setup the Nexus10 and installed SD I copied the custom dashboards (same files as on the S4) from the TS files on my PC to the dashboards directory on the Nexus10. I renamed the original dashboard_0_landscape and dashboard_1_landscape set up on the Nexus by SD before doing that so I could preserve them. they are still there. So not I didnt copy them from the S4 to the Nexus but both devices got the custom .dash files from the same source.

If you just delete the whole project, is all working fine again with the default dashboards?

So, try unistalling SD, deleting the dashboard and projectcfg directories and installing them again from the .apk and see if they behave right? I seem to recall that the "AFR" on the 0 and 1 originals were also broken but I could be mistaken. If what I just wrote is what you mean, I will give it a try and report back.

I tried to load the dash above, but it looks like after editing it is no longer valid. Can you send the original dash via drop box or email?
Emailing support <at> efianalytics.com

Yes, I cut everything but the lines I suspect relate to my Lambda gauge so there is probably a lot lost that is needed to work. On the way...

[walterclark1]

Remembering that I never touched the original dashboard 0 and 1 portrait (I only use landscape mode on my tablet) I re-named the original project.properties back and restarted SD. My dashboards' Lambdas again came up broken (once the connection to the MS3 is made) but the original AFR gauges on the dashboard 0 and 1 portrait files work fine.

[walterclark1]

A bit more.

I found that if the file project.properties contains the LAMBDA statement on the last line, then my Lambda gauge works. If it is not there the gauge does not work and the red circle with a slash appears once the app connects to the MS3.

I believe the statements like MPH and LAMBDA are supposed to be written to this file by SD at some point when I have selected them from the user preferences under the SD Preferences menu. I know that Lambda is currently showing as selected within these menus as my preferred unit of display, but the file did not contain the statement until I added it manually. What set of conditions and series of user actions is required before a selection is supposed to be written and saved to the file?

Currently, when I have SD connected to the MS3 and cycle through the preferences menu (meaning opening a window and tapping on the unit I prefer) for the Temperature, Speed and EGO unit preferences, then exit the menus and SD and then open the project.properties file, only the MPH term has been added to the file.

[LT401Vette]

On the menu in SD select Project Properties, then you can set LAMBDA on.

[walterclark1]

On the menu in SD select Project Properties, then you can set LAMBDA on.

Ah-HA! That seems to be the key. Thanks!