Jiji
Well-Known Member
- First Name
- Rick
- Joined
- Jul 26, 2021
- Threads
- 19
- Messages
- 398
- Reaction score
- 507
- Location
- Finger Lakes
- Vehicles
- 2022 Mustang Mach-E GT 2023 Rivian R1S
- Thread starter
- #1
4/12/2023 Update: OBD Record 0.50.11 supports DCFC!
Build 0.50.11 has been posted, see the OBD Record GitHub discussion for the link and the release notes. Also a write up of the updates to the Trip and DCFC displays can be found here.
4/3/2023 Update: OBD Record 0.50.7 is now available for download
Build 0.50.7 has been posted, see the OBD Record GitHub discussion for the link and the release notes.
3/28/2023 Update: OBD Record 0.50.6 is now available for download
Build 0.50.6 has been posted, see the OBD Record GitHub discussion for the link and the release notes.
3/26/2023 Update: OBD Record 0.50.5 is now available for download
A new build has been posted with improvements based on the 0.50.3 release. Please download a copy and try it out if you have an OBDLink MX+ scan tool.
3/23/2023 Update: OBD Record is now available for download
The first preview is now live and to keep things sane we will start with 10 testers. To get the most out the first preview I ask that you only download a copy if you have the following:
TL;DR
This is the companion to the previously showcased OBD Play app, it records the details of your trips and charges so you can view them in OBD Play. To get this done it requires a Mustang Mach-E, an OBDLink MX+ OBDII scan tool, and somewhere to store your data (which I can help). If you are interested in checking it out, the code and discussions are found here.
Overview
My work of love for the past couple of months it replaces my gen1 Raspberry Pi solution (link) which got me started into pulling CAN bus data from the OBDII connector for viewing. It has now been repurposed as a simulator, playing back trips and charges into the gen2 solution using he OBDLink MX+ as it can be tough to debug OBD Record while tooling around on the open roads.
Let's Take a Trip
Unlike OBD Play which displays a wealth of detailed information about your trips and charges, OBD Record really doesn't need much of a user interface. It has just two tab views, Record which is a display of the current vehicle state, and Settings which allows you to configure OBD Record to your liking:
So what happens when you jump in your MME you will connect your phone to the OBDLinkMX+ using the iPhone Settings (if it didn't connect automatically) and the Record state changes from Disconnected to Connected and things start to happen:
Doesn't seem like much but now we are talking to the OBDLink MX+ and pulling the charge plug and ignition status and waiting patiently for something to happen. When you hit the Run/Start button, the vehicle state will change to Ignition On where we start polling the gear shift selector (which should be in Park):
Now we wait for a trip to begin which occurs when the gear selector is moved out of Park. Once detected we collect a variety of start details such as the odometer, vehicle location, SoC, and much more) and the state transitions to Trip:
Now that we are moving there is more interesting data to show but this just debugging fluff so I know OBD Record is still working and not locked up. As you might imagine there is a lot of real-time communications going on between the phone and the OBDLink MX+ (over Bluetooth) and then pushing all the collected data to the cloud (using your phones WiFi or cellular data) where OBD Play can later access it.
Our trip ends when the gear selector is returned to Park. This causes the end point odometer, vehicle location, SoC, and other end point data to be read and the trip recorded in the cloud.
Let's Charge our MME
Very similar to a trip but the state just follows the charge path (Plugged In, AC Charge Starting, AC Charge, AC Charge Ending) and when the charge completes the data is again pushed to the cloud. Here is what the AC Charge view looks like:
Wrap Up
And that is OBD Record in a nutshell. A reminder you need a Mustang Mach-E and an OBDLink MX+ to use OBD Record and it will be available for all via the Apple TestFlight app (where OBD Read has been hanging out).
I hope you find these useful tools in exploring your Mach-E but a final comment. This beta software is strictly for your amusement and there are no warranties or claims that it is fit for any particular purpose. I can't be responsible for bug fixes or updates but the source code will be available should you wish to do so yourself. That said, I have been using variants of OBD Record/OBD Play for early a year now and will likely do so as long as there is a Mustang Mach-E in the garage.
Enjoy!
Build 0.50.11 has been posted, see the OBD Record GitHub discussion for the link and the release notes. Also a write up of the updates to the Trip and DCFC displays can be found here.
4/3/2023 Update: OBD Record 0.50.7 is now available for download
Build 0.50.7 has been posted, see the OBD Record GitHub discussion for the link and the release notes.
3/28/2023 Update: OBD Record 0.50.6 is now available for download
Build 0.50.6 has been posted, see the OBD Record GitHub discussion for the link and the release notes.
3/26/2023 Update: OBD Record 0.50.5 is now available for download
A new build has been posted with improvements based on the 0.50.3 release. Please download a copy and try it out if you have an OBDLink MX+ scan tool.
3/23/2023 Update: OBD Record is now available for download
The first preview is now live and to keep things sane we will start with 10 testers. To get the most out the first preview I ask that you only download a copy if you have the following:
- Mustang Mach-E
- OBDLink MX+ scan tool
- a working InfluxDB Cloud or OSS instance to store the trips/charges
TL;DR
This is the companion to the previously showcased OBD Play app, it records the details of your trips and charges so you can view them in OBD Play. To get this done it requires a Mustang Mach-E, an OBDLink MX+ OBDII scan tool, and somewhere to store your data (which I can help). If you are interested in checking it out, the code and discussions are found here.
Overview
My work of love for the past couple of months it replaces my gen1 Raspberry Pi solution (link) which got me started into pulling CAN bus data from the OBDII connector for viewing. It has now been repurposed as a simulator, playing back trips and charges into the gen2 solution using he OBDLink MX+ as it can be tough to debug OBD Record while tooling around on the open roads.
Let's Take a Trip
Unlike OBD Play which displays a wealth of detailed information about your trips and charges, OBD Record really doesn't need much of a user interface. It has just two tab views, Record which is a display of the current vehicle state, and Settings which allows you to configure OBD Record to your liking:
So what happens when you jump in your MME you will connect your phone to the OBDLinkMX+ using the iPhone Settings (if it didn't connect automatically) and the Record state changes from Disconnected to Connected and things start to happen:
Doesn't seem like much but now we are talking to the OBDLink MX+ and pulling the charge plug and ignition status and waiting patiently for something to happen. When you hit the Run/Start button, the vehicle state will change to Ignition On where we start polling the gear shift selector (which should be in Park):
Now we wait for a trip to begin which occurs when the gear selector is moved out of Park. Once detected we collect a variety of start details such as the odometer, vehicle location, SoC, and much more) and the state transitions to Trip:
Now that we are moving there is more interesting data to show but this just debugging fluff so I know OBD Record is still working and not locked up. As you might imagine there is a lot of real-time communications going on between the phone and the OBDLink MX+ (over Bluetooth) and then pushing all the collected data to the cloud (using your phones WiFi or cellular data) where OBD Play can later access it.
Our trip ends when the gear selector is returned to Park. This causes the end point odometer, vehicle location, SoC, and other end point data to be read and the trip recorded in the cloud.
Let's Charge our MME
Very similar to a trip but the state just follows the charge path (Plugged In, AC Charge Starting, AC Charge, AC Charge Ending) and when the charge completes the data is again pushed to the cloud. Here is what the AC Charge view looks like:
Wrap Up
And that is OBD Record in a nutshell. A reminder you need a Mustang Mach-E and an OBDLink MX+ to use OBD Record and it will be available for all via the Apple TestFlight app (where OBD Read has been hanging out).
I hope you find these useful tools in exploring your Mach-E but a final comment. This beta software is strictly for your amusement and there are no warranties or claims that it is fit for any particular purpose. I can't be responsible for bug fixes or updates but the source code will be available should you wish to do so yourself. That said, I have been using variants of OBD Record/OBD Play for early a year now and will likely do so as long as there is a Mustang Mach-E in the garage.
Enjoy!
Last edited: