Search results

The blue one is this one: https://www.amazon.com/gp/product/B0BVLZ27TL/ref=ppx_od_dt_b_asin_title_s00?ie=UTF8&th=1&_encoding=UTF8&tag=featherlessde-20&linkCode=ur2&linkId=7a7a9ab9c7ed0a266a95d9efe08a237a&camp=1789&creative=9325 It’s the cheapest one on Amazon and apparently for good reason...

Some quick updates on device performance statistics: # OBDLink CX (v1.4b) - 15.03 seconds to send 21 ATZ commands - 2.07-2.31 seconds to send 21 0902 commands # vLinker MC+ (v2.2) - 20.3 seconds to send 21 ATZ commands - 2.34-2.37 seconds to send 21 0902 commands # VEEPEAK OBDCheck BLE...

Will add in next update! I noticed that the Swift Bluetooth library I was using wasn’t thread safe and would end up getting stuck on itself, so I’m doing a clean rewrite… with a nice view :)

If you're looking for some scanner recommendations (links are affiliate links for Electric Sidecar's business account): - My personal favorite due to form factor / price: Veepeak OBDCheck BLE Bluetooth OBD II Scanner ($31.99)...

Ah also, this scanner works for any vehicle, so if you have a non-Taycan car I'd also love to get any feedback on your experience with it. I've been testing this functionality with our 2012 Nissan Juke which has zero connectivity features, and it's been nice to have a widget on my phone that...

I've got the first alpha build of the new OBD scanner functionality ready for test! You can get access to it by joining this beta group: https://testflight.apple.com/join/qqA3wnAp If you're able to test out the new functionality, please share the following details with me so that I know what...

I've stumbled upon a fun algorithm interview question: build Electric Sidecar's OBD signal scheduling mechanism ? It's a pretty fun algorithm / optimization / timing problem. Given a set of commands X, where each command has: 1. a refresh interval specified in milliseconds and, 2. a 16 bit...

Everything is now fully functional for an MVP release of the OBD scanner functionality :D Just doing a final QA pass on the feature set now to iron out some of the obvious rough edges. Journey statistics can now be much more accurate if you're using a scanner: I've been brain-dumping all of...

Two punctures in ~12,000 miles. One on the rear left, one on the rear right. Noticed both due to a slow leak over a few days, and both got replaced under the tire warranty (~$50 / tire).

The data that comes from your car via the Porsche servers can be pretty delayed (on the order of minutes). This is why the data you see in the Porsche app is fairly consistent with the data currently shown in Electric Sidecar. There isn’t much that can be improved on the app side for this...

Another update, this one less visual but important nonetheless: I've just finished a complete overhaul of the app's underlying signal logging database to a unified architecture that will now support both OBD and OEM-based data. This means a few things: - When you're plugged in to a car scanner...

Been making good progress on the monitor UX. Here's what the community monitors page will look like: Note that monitors can now suggest metrics that they'll power, such as SoC, speed, tire pressure, etc. When a monitor is connected to one of these metrics and you're scanning your car...

Adding an OBD badge to the charge widget to nicely surface when an OBD reader is connected to the vehicle everywhere this widget gets used:

Went for the first drive with live monitors wired up :D :D :D Monitors will be defined in the same community GitHub repos that house the vehicle discussions. So the Taycan's monitors are defined here: https://github.com/ElectricSidecar/Porsche-Taycan/blob/main/signalsets/default.json. The app...

Will never unsee now ?

Quick update: spent the past couple days learning about DBC files before finally realizing that they're optimized for raw, fixed-width CAN bus data parsing, and aren't really designed for working with OBD diagnostics requests coming in via variable-width CAN frames via OBD. I want to make...

haha that’s next! Needed to start with the published standards first :p

First generic value monitor in place: This is setting up the foundations for tracking monitors over time. Electric Sidecar keeps a historical record of all command/response pairs sent over the OBD-II connection, so this data can be turned into charts within the app. Will also make it possible...

Working on expanding the monitor status page with the standard OBD-II features: These features aren't as relevant for the Taycan, but it's part of setting Electric Sidecar up for a general App Store launch as a more general purpose OBD-II scanner while I wait to get official OEM vehicle...

Oooh do you work on the MyPorsche app?