Skip to main content

When are the engine status uploaded for "StatusData" API

KUeha-1540
Original Poster

I'm trying to get time series engine status from StatusData API below for building a data analysis software, and looking for a spec of when the Geotab system get the data from the GO device.

https://geotab.github.io/sdk/software/api/reference/#T:Geotab.Checkmate.ObjectModel.Engine.StatusData

 

My question is:

  1. How it's determined by the system to upload each engine status record to Geotab cloud?
  2. Is there a way to configure the data upload strategy? By interval based, value delta based, whatever it's appreciated.

 

I tried to get EV battery status, and figured out the data resolution is much different on each day for battery charge status.

 

[one day]

6.5 hour driving

190 battery data

=> 2.0 minutes/data

 

[another day]

2.5 hour driving

260 battery data

=> 0.6 minutes/data

 

[+ another day]

5.0 hour driving

0 battery data

=> infinite minutes/data

 

I referred the below document to get battery data.

https://docs.google.com/document/d/1f5aUkK9t3JiEqg6oL9dep5UDps_ymuC2refw7pEZ0VU/edit#bookmark=kix.486lj0orwea5

 

Thank you!

Join the conversation

You need to be logged in to reply to this post and participate in the Geotab Community discussions.

Top Answers

Hi @KUeha-1540​ 

 

These three diagnostics types all function differently:

 

  • State of Charge (DiagnosticStateOfChargeId): recorded each 1% change
  • Energy in & out while driving (DiagnosticElectricEnergyInId, DiagnosticElectricEnergyOutId): recorded at each ignition On and Off, and when speed hits 0, and when the vehicle starts moving again (in and out of idling).
  • Battery Power (DiagnosticElectricVehicleBatteryPowerId): curve logged

 

For more detail about how curve logging works, see this blog post

EishiFUN
Geotabber

Hey @KUeha-1540​ sorry for the delay with getting back to you on this. I wanted to help answer your questions here.

 

(1) It can vary based on each diagnostic, and we don't have document that summarizes all diagnostic thresholds public.

 

(2) No there is not

 

Feel free to reach out with any other questions or concerns we are happy to help.

 

Have a great day!

Eishi FUN

6 Replies

EishiFUN
Geotabber

Hello @KUeha-1540​  great question thank you for asking them here. I did reach out to our SMEs about this and this is what they told me.

 

By EV 'battery status', are you looking at state of charge? (DiagnosticStateOfChargeId)? If yes, it should be recorded by each 1% increment, every other diagnostic will be subject to curve logging. I believe that may be dependent on the make / model / year, but you can compare your vehicle to our list of supported EV's Electric Vehicle Make/Model Support Reference [PUBLIC].

 

The actual driving of the vehicle (speed, accessories being used, temperature outside, etc) will have an effect on the rate of change for state of charge. Aggressive driving vs non aggressive, etc. Which will effect how often that value gets recorded.

 

For the day 3 part we are curious what DiagnosticId you are querying and we will follow up with you.

 

Please reach out if you have any questions or follow ups to this we are happy to help.

 

Have a great day!

Eishi FUN

KUeha-1540
Original Poster

Hello @EishiFUN​ ​ thank you so much for the reply, much helpful!

 

Yes, state of charge is one of what in my mind.

 

Your explanation sounds like the system determines to record data on detecting certain amount of delta since last record (like 1% delta for state of charge).

 

If above is true, does the system works under the same logic (delta based record) for the following items as well?

  • energy in&out (DiagnosticElectricEnergyInId, DiagnosticElectricEnergyOutId)
  • power (DiagnosticElectricVehicleBatteryPowerId)

 

And how can I know the delta for each items? e.g. How large amount of energy input (XX kWh) triggers to record DiagnosticElectricEnergyInId?

Hi @KUeha-1540​ 

 

These three diagnostics types all function differently:

 

  • State of Charge (DiagnosticStateOfChargeId): recorded each 1% change
  • Energy in & out while driving (DiagnosticElectricEnergyInId, DiagnosticElectricEnergyOutId): recorded at each ignition On and Off, and when speed hits 0, and when the vehicle starts moving again (in and out of idling).
  • Battery Power (DiagnosticElectricVehicleBatteryPowerId): curve logged

 

For more detail about how curve logging works, see this blog post

KUeha-1540
Original Poster

Hi @CMidd-10803​ thanks for the update. The logic looks slightly different for each engine status.

 

So going back to my original two questions.

 

1. How it's determined by the system to upload each engine status record to Geotab cloud? Or how can I know the logic for each engine status listed in below.

https://docs.google.com/spreadsheets/d/1sy7IOhWmFoo40_I-ruOJO8bVTMLXqHa11d0oJtaoIcE/edit#gid=1405610761

 

2. Is there a way to configure the data upload strategy? By interval based, value delta based, whatever it's appreciated.

 

Thank you!

EishiFUN
Geotabber

Hey @KUeha-1540​ sorry for the delay with getting back to you on this. I wanted to help answer your questions here.

 

(1) It can vary based on each diagnostic, and we don't have document that summarizes all diagnostic thresholds public.

 

(2) No there is not

 

Feel free to reach out with any other questions or concerns we are happy to help.

 

Have a great day!

Eishi FUN

KUeha-1540
Original Poster

Hi @EishiFUN​ , much appreciate on your description.

 

It's so good to know. Let me ask for each diagnostic in different thread if needed. Thank you!

Still have questions?