Data upload feature discussion

[Paulo Pires]

Hi guys,

Given that several users have requested data upload support, I'm hereby asking for input on how you'd like to see it implemented/working.

Please, detail your ideas so that we can agree on a first drawing and get it done.

Cheers,

PP

[Patrick]

Hi Paulo,

thank you for starting this discussion. It would be great if the upload support comes back ... I think there are a lot of interesting applications and scenarios for using this functionallity. Now some basic ideas/input for the implementation:

1) Menu Options/Settings ("OBD Preferences")
If it's right, the User Menu Options/Settings related to the upload function (until 1.2) were the following:
- "Enable Data Upload" (checkbox)
- "Upload URL" (text/string)
- "Vehicle ID" (number/integer)
Additional, I think it would be nice if there were a field to define a username or e-mail-adress. This could be used on server-side for example to identify/login a user. In Addition if the option "Vehicle ID" is set it can be used to match a group/fleet of cars to a specific user/account.

2) Time to Upload ("real-time upload vs. upload at the right time")
If it's right, the default upload mode is in real-time. This means, that the data will send directly (requiring an internet connection) to the server and will not (at any time) be stored on the device. In my opinion it would be great if there were generally the possibility to store the (raw) data-log on the device. If there is no internet connection during the data record, the user has the choice to transfer the data on a later moment. Of course a function that determinates this case (send on internet connection availability) automatically would be useful (but I think this could be difficult...).
Perhaps it would be nice if there were and option to determine that the app will start the record/upload process (dependent on the settings) directly after the start (of the app).

3) Some more suggestions...
In note form some other suggestions, but I think they are not implict nessesary for now:
- Adding a selection in the user menu to pick the OBD-PIDs for the upload. (as determination to the selection of OBD-PIDs for real-time display)
- Adding a password field to the data upload for server-side usage. (no really requirement)
- A bit crazy idea at the end: whats about an rudimentary formula editor to calculate additional values for the upload (directly on the device) by using the OBD-PIDs as variables. (I think this is a pretty big plan...)

Some Questions
- Question 1: Is the fuel consumption (calculation by using serveral sensors/PIDs if available) already part of the upload data?
- Question 2: Relating to the upload/record process: what happens if a sensor/PID could not requested in the stated time (set request interval)? Will the last known value be written in the record/upload or is the corresponding value such as NULL?


So far as, this is my input for the moment - I hope it could help a bit. Now I hope for a lively discussion - there could be other point of views!

Cheers,
Patrick

[B Mutia]

Hi Paulo, 

Are you planning to put this tool at Google Play  to make it easier to download and install for other OBD2 users and enthusiasts?  If not, would you allow third party to put it there?

Thanks

Bern

--
You received this message because you are subscribed to the Google Groups "Android OBD Reader users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-obd-reader...@googlegroups.com.
To post to this group, send email to android-obd-...@googlegroups.com.
Visit this group at http://groups.google.com/group/android-obd-reader-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--

---------
Minimize Our Carbon Footprint!
http://www.greenfuelbooster.com

[Paulo Pires]

@Bern, I'm planning a 2.0 release with updated code and more features, such as the one that's being discuss in this thread.

I'll put it in Play Store whenever I reach that milestone, which I hope to achieve somewhere around July.

Cheers,

PP

Paulo Pires

[Paulo Pires]

See my answers inline.

On Fri, May 17, 2013 at 12:19 AM, Patrick <vol...@uni-potsdam.de> wrote:

Hi Paulo,

thank you for starting this discussion. It would be great if the upload support comes back ... I think there are a lot of interesting applications and scenarios for using this functionallity. Now some basic ideas/input for the implementation:

1) Menu Options/Settings ("OBD Preferences")
If it's right, the User Menu Options/Settings related to the upload function (until 1.2) were the following:
- "Enable Data Upload" (checkbox)
- "Upload URL" (text/string)
- "Vehicle ID" (number/integer)
Additional, I think it would be nice if there were a field to define a username or e-mail-adress. This could be used on server-side for example to identify/login a user. In Addition if the option "Vehicle ID" is set it can be used to match a group/fleet of cars to a specific user/account.

Vehicle ID shouldn't be needed if the app retrieves the VIN.

Username and password? That could prove a little bit tricky. Let's skip that one, for now.

 

2) Time to Upload ("real-time upload vs. upload at the right time")
If it's right, the default upload mode is in real-time. This means, that the data will send directly (requiring an internet connection) to the server and will not (at any time) be stored on the device. In my opinion it would be great if there were generally the possibility to store the (raw) data-log on the device. If there is no internet connection during the data record, the user has the choice to transfer the data on a later moment. Of course a function that determinates this case (send on internet connection availability) automatically would be useful (but I think this could be difficult...).
Perhaps it would be nice if there were and option to determine that the app will start the record/upload process (dependent on the settings) directly after the start (of the app).

This is doable.

 

3) Some more suggestions...
In note form some other suggestions, but I think they are not implict nessesary for now:
- Adding a selection in the user menu to pick the OBD-PIDs for the upload. (as determination to the selection of OBD-PIDs for real-time display)

I'm thinking about adding a configurable list of PID's, so that only those selected are queried repeatedly with intervals.

 

- Adding a password field to the data upload for server-side usage. (no really requirement)

Let's skip this for now.

 

- A bit crazy idea at the end: whats about an rudimentary formula editor to calculate additional values for the upload (directly on the device) by using the OBD-PIDs as variables. (I think this is a pretty big plan...)

Not even sure I follow you, but for sure it's a no go, for now.

 

Some Questions
- Question 1: Is the fuel consumption (calculation by using serveral sensors/PIDs if available) already part of the upload data?

This isn't available as it *NEVER* worked. I don't know any other software that *REALLY* does calculate or retrieve instant fuel consumption without having paid for proprietary ECU documentation.

 

- Question 2: Relating to the upload/record process: what happens if a sensor/PID could not requested in the stated time (set request interval)? Will the last known value be written in the record/upload or is the corresponding value such as NULL?

If a list of PID's is executed, than the result will integrate all of the responses. Whenever the list is executed again, a new result is saved. When uploading, we'll be compiling all the executions. This way, you can do whatever you want with the data! But at least, you 'll have all the data :-)

What do you think?

 

So far as, this is my input for the moment - I hope it could help a bit. Now I hope for a lively discussion - there could be other point of views!

Cheers,
Patrick


Am Donnerstag, 16. Mai 2013 11:54:45 UTC+2 schrieb Paulo Pires:

Hi guys,

Given that several users have requested data upload support, I'm hereby asking for input on how you'd like to see it implemented/working.

Please, detail your ideas so that we can agree on a first drawing and get it done.

Cheers,

PP

--

You received this message because you are subscribed to the Google Groups "Android OBD Reader users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-obd-reader...@googlegroups.com.
To post to this group, send email to android-obd-...@googlegroups.com.
Visit this group at http://groups.google.com/group/android-obd-reader-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Paulo Pires

[B Mutia]

Paulo,  that is great news!  I know quite a few who will be happy to know that.

Thanks,

Bern

[Paulo Pires]

Well, there are better apps that target the end-user. And I think the idea of this project is simply to be an OSS OBD reader/proof-of-concept.

Still, I'll try to have something fancy :-)

Cheers,

PP

[B Mutia]

Paulo,

The interested people I know do not need to be fancy stuff ... as long as it logs core OBD2 parameters into a CSV file.   That is all they need.

Thanks

Bern

[Patrick Voland]

Please don't misunderstand me. I understand that this project has a defined project scope. My achievements covered a few more or less proper considered ideas. Well, not particularly constructive - many things are really not necessary to implement.

But I think it would be great if there were the capability to use/utilize the data from the reader. For me there are two possible ways: the data export (for exp. as CSV, as Bern said) and the data upload (via HTTP for server-side use). I Think it could be possible to brings this things together: Both ways requires (at least temporary) storing of the data log on the device. This enables the data export and in case of the data upload (the local stored data) could be delayed transfered (in dependency of an established internet connection).

It is clear that the use/adaption of the data (in case of data export and data upload) is exercise of other projects/developers. In my current case, the upload function is really interesting so I hope it comes (back). I Think every output capability gives the people the chance to use/Utilize the obd data and increases the group of persons who could participate in the results of this (really magnificent) OSS project.

Cheers,
Patrick

[Paulo Pires]

Well, it's easy to store data and eventually upload it.

Right now, I'm to busy to pick up on this, but as soon as I have time (but no more later than August), I'll pick it up and implement something people can try.

More feedback is always welcome.

Cheers,

PP

--

You received this message because you are subscribed to the Google Groups "Android OBD Reader users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-obd-reader...@googlegroups.com.
To post to this group, send email to android-obd-...@googlegroups.com.
Visit this group at http://groups.google.com/group/android-obd-reader-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Paulo Pires

[Paulo Pires]

OK so I'm back. I've just received a new Android device (Nexus 7, yey!) and will be catching up starting this weekend or so. Let's do it? ;-)

Cheers,

PP

--
Paulo Pires