Visualization of Carloop Telemetry

[jnbankston]

Hello,

We have been using Carloop for the last several months and its been an excellent framework to jumpstart car projects. Thanks to the Carloop team! Since then, we have been developing a platform which leverages the Carloop 3G device to visualize its telemetry data in a mobile app.

Features include trip detection, dtc code notifications and acknowledgement, anomaly detection and service / maintenance history to start. Below are some screenshots from the mobile app. We are in the early stages of development and would like to hear from interested enthusiasts. Thanks in advance looking to share more as we progress.

[cyclin_al1]

Very interesting work! Is this a project that you will be sharing? It would be a great example of how to do a mobile app linked with Carloop!

[jnbankston]

Thanks! We are actually building a Fleet Management platform on top of the Carloop device. There are i some functionality we would be interested in open sourcing.

[cyclin_al1]

Cool!

I could see some of the functionality reused for race car telemetry...

[jnbankston]

Yeah. Any use cases on how you could use it for race car telemetry? Thanks.

[cyclin_al1]

In a race car, once the safety cage is installed and other changes are made, the stock dashboard no longer works.
How about a custom dashboard, where the mobile app is used to configure what parameters are shown on the dash.

Another application would be getting data over to the mobile app so the team chief could what makes for the best lap times on a track.

Yet another is for a navigation rally (not really racing) to keep track of the co-drivers instructions, along with speeds, averages and timing for the driver.

[jnbankston]

I really like the last two use cases and could easily integrate them into the application. Are these challenges you are facing? It would be helpful to do a deeper dive to with someone to flesh out the idea. Thanks!

[cyclin_al1]

Let me elaborate on the navigation rally first.

At its heart, navigation rally is not a race, but precision driving. The goal is to be on time, all the time.
Instructions are in the form of average speeds or leaving a waypoint at a specific time. For example, drive section 1 at 54.3 km/h. Take 3 minutes to drive section 2 (used for sections going through towns or at railway crossings), so you wait at the end of section 2 until the 3 minutes has passed.

The navigation part is by distance. For example, turn left at 0.54 km, then calibrate your odometer with the bridge at 5.1 km (except you will have to calibrate as it may scaled differently than a real odometer). You would want to keep a history of how the car entered and exited a waypoint (ie. direction and location on the way into an intersection, and the same information on the way out). This history would allow to return and make corrections in case of navigation error. The difference between bear (slight) left, turn (90 deg) left and acute (sharper) left may be important. Also, instructions may be in the form of a puzzle (ie. 6:00 on a clock face means straight ahead.).

This is very basic. As you can tell, it gets very interesting (complicated) quickly, but there are teams that can be off by only 0.1 minutes (6 seconds) after 7 or 8 hours of rallying.....

If you are interested, I can search up some links about more detail on the navigation.

[Louisianimal]

Is the project still in development? Really curious to see if you decided on open source and what parts need contribution/work.

[jnbankston]

@Louisianimal yes it is. Send me a pm and we can discuss. There would need to be some clean up before it could be release. Thanks.

[Louisianimal]

@jnbankston PM'd you; my inbox was filtering email from these forums. Better late than never I suppose though.