Android app only reads partial configuration

Discussion on the RaceCapture App - Windows, Android, OSX and Linux.

Moderators: JeffC, stieg

Post Reply
ushgeo
Posts: 19
Joined: Wed Oct 28, 2015 10:07 pm
Location: Fort Worth, TX

Android app only reads partial configuration

Post by ushgeo »

I just received my new RCP2 in the mail today and am eagerly busy with the initial set up (at home; car is at the shop).

I have successfully connected RCP2 to my Mac (Yosemite), loaded the desktop app, updated the firmware to 2.8.5, and connected to RCP via USB. I configured the dashboard, race tracks, and a few other preliminary settings, saved the configuration to my desktop, and loaded the config to RCP2. So far, so good.

I then connected the bluetooth module, downloaded the Android app to my new Amazon Fire, paired RCP2 and Android app via bluetooth, and can read the configuration file from RCP2. All of the tracks come across but the dashboard settings do not appear in the Andorra app.

Am I missing something? Please tell me I don't have to set up the dashboard separately on the Android app and the desktop app.
NASA GTS3 Racing
2000 Porsche 996 Ex Grand Am Series Race Car
****************************************
2005 Porsche 997 C2S - Atlas Grey - R.I.P.
2012 Audi S4 Prestige - Sold
2006 BMW 330i Sport - Sold

momostallion
Posts: 58
Joined: Wed Feb 12, 2014 1:48 pm
Location: dallas, tx

Post by momostallion »

you do. the android's dash settings are a file locally on the android. took me like 3 minutes to setup how i like.

ushgeo
Posts: 19
Joined: Wed Oct 28, 2015 10:07 pm
Location: Fort Worth, TX

Post by ushgeo »

momostallion wrote:you do. the android's dash settings are a file locally on the android. took me like 3 minutes to setup how i like.
This begs the question, what's the point of being able to configure the dashboard on the desktop app if it doesn't get transferred to the mobile app? Moreover, why does the mobile app read the list of tracks but not the dashboard settings?
NASA GTS3 Racing
2000 Porsche 996 Ex Grand Am Series Race Car
****************************************
2005 Porsche 997 C2S - Atlas Grey - R.I.P.
2012 Audi S4 Prestige - Sold
2006 BMW 330i Sport - Sold

stieg
Posts: 100
Joined: Fri Dec 20, 2013 1:37 am
Location: Madison, WI
Contact:

One App to Rule Them All

Post by stieg »

Hi ushgeo,

momostallion is correct, you have to setup the dash on a per-device basis.

This begs the question, what's the point of being able to configure the dashboard on the desktop app if it doesn't get transferred to the mobile app?
The reason you are able to configure a dash on your computer and tablet is because we wrote the new app in a framework that allows us to use the same app across both computers and tablets. Hence you see the dash on both your computer and tablet, but the configuration settings do not transfer over. We have this listed as a future feature request (being able to save/transfer dash configs) but currently I can not provide any estimate as to when it will be done. Our apologies for the confusion.
why does the mobile app read the list of tracks but not the dashboard settings?
The list of tracks comes from the Race Capture Live cloud service. This is why.
Andrew Stiegmann (Stieg)
Principal Engineer
Autosport Labs Inc.

ushgeo
Posts: 19
Joined: Wed Oct 28, 2015 10:07 pm
Location: Fort Worth, TX

Post by ushgeo »

Thank you stieg for the explanation and it makes perfect sense. I thought I was losing my mind because I couldnt figure out what I was doing wrong. It would be great if the mobile app could read the config from RCP2 or from the desktop app, or be able to download it from the cloud, SD card, or even an emailed file. I'm glad to see that's in the list of requested enhancements.

Of course, this makes me think of a couple of other questions. I apologize for asking all of these, especially if they are duplicated somewhere else in the forums, but I cant seem to find much discussion about the mobile app.

1. Is there anything else that can be written using the desktop app that cant be read by the mobile app, and vice versa?

2. Should all scripting be done in the desktop app and will it be readable by the mobile app?
NASA GTS3 Racing
2000 Porsche 996 Ex Grand Am Series Race Car
****************************************
2005 Porsche 997 C2S - Atlas Grey - R.I.P.
2012 Audi S4 Prestige - Sold
2006 BMW 330i Sport - Sold

stieg
Posts: 100
Joined: Fri Dec 20, 2013 1:37 am
Location: Madison, WI
Contact:

Post by stieg »

No worries RE the questions. Answers inline...
Is there anything else that can be written using the desktop app that cant be read by the mobile app, and vice versa?
The desktop app can also do firmware updates while the mobile app can not (possible if the mobile device has a USB host controller and is plugged into the RCP unit, but this is not tested).

All the settings under the "Configuration" section of the app get written to the RCP unit, so as long as they get written, then you can make changes on one app and have them be reflected on the other app.

In other words, configuration settings for the RCP will come across between apps. But app specific settings will not.
Should all scripting be done in the desktop app and will it be readable by the mobile app?
In my experience trying to do LUA scripting on a tablet takes you to a world of pain. I do all my scripting on the desktop app and save it to the RCP. Since the LUA script is part of the RCP configuration, it will go between apps. I think we would have the worst user experience in the world if we forced you all to type LUA script in on a tablet :P

Hope that helps.
Andrew Stiegmann (Stieg)
Principal Engineer
Autosport Labs Inc.

brentp
Site Admin
Posts: 5986
Joined: Wed Jan 24, 2007 6:36 am

Post by brentp »

A bit of clarification.

RCP currently stores information about a sensor channel - like channel name, the number of digits of precision it should report, and it's min / max values. We're looking at adding some additional information, like alert levels - stuff that makes sense to live in RaceCapture.


However, there are things that won't be stored in RCP:

- how your dashboard screens are configured
- what gauges are selected on which screens
- colors of alerts

and other similar user interface configuration. It's a logical separation between user interface view and the thing that supplies data.

Reason: RaceCapture is not inherently aware of the user interface. Also, one app may need to be configured differently than another app. Example, app on desktop vs dashboard in car. In the future, we may offer the ability for multiple tablets to connect to one RaceCapture device, and each will want to keep it's own configuration.

Hope that helps!

Post Reply