Pankuzu (Breadcrumbs): trip & charging data recording app for your F-150 Lightning

[Jiji]

Is the veepeak module not an option? Does it only work with the MX+?

Sorry but no. But I hope the source code will be on github this week so someone can add it for you.

Sponsored

 

[Jiji]

I’d like to point out using an app in TestFlight can be risky if you don’t know or trust the developer

Yes, save my precious time and don’t download it. Thank you for looking out for everyone’s safety and well being.

 

[SFsparkie]

try it out, except the recording aspects, and let someone else confirms it works. As I am the only one that has used this let others that already have an OBDLink MX+ and help iron out the kinks in 6he onboarding process.

I ordered the MX+ because I want to support your efforts to perfect the App. I have driven my Lightning San Francisco to New York and San Diego, CA to Moscow, Idaho. I would have liked to automatically record those trip details to plan future trips. I’m looking forward to using Pankuzu to enhance the driving experience. (Breadcrumbs-great metaphor)

 

[Jiji]

I ordered the MX+ because I want to support your efforts to perfect the App. I have driven my Lightning San Francisco to New York and San Diego, CA to Moscow, Idaho. I would have liked to automatically record those trip details to plan future trips. I’m looking forward to using Pankuzu to enhance the driving experience. (Breadcrumbs-great metaphor)

There is hope for your trips:, first successful report on the Mach-E forum.

i am a little less apprehensive now given there aren’t any real instructions at this point.

 

[SFsparkie]

i am a little less apprehensive now given there aren’t any real instructions at this point.

You did good. Your two posts and the seeded examples are sufficient. TestFlight is not for the impatient tap & run user. We will navigate the learning curve. For us Lightning buyers we were all sort of test pilots enduring lemons, buy backs, bricks, uninformed dealers & deceased architecture. Still love the ride & thankful for all the knowledge this Forum has provided.

 

[Jiji]

You did good. Your two posts and the seeded examples are sufficient. TestFlight is not for the impatient tap & run user. We will navigate the learning curve. For us Lightning buyers we were all sort of test pilots enduring lemons, buy backs, bricks, uninformed dealers & deceased architecture. Still love the ride & thankful for all the knowledge this Forum has provided.

I just updated the OP with links to the GitHub repo and discussions, everything will be there eventually. Writing user docs hasn't been a priority when designing features for a user base of one but about a week ago I added Claude to the team and now I can focus on the big picture and let Claude do the boring stuff.

 

[Antimater]

I love the app! I have a similar project but using a OBDLink CX instead. I fired Panzuku up with my OBDLink MX and it found my MY 2023 Lightning pretty quickly. I haven't gone anywhere to get trip (breadcrumb) data yet but will later today.

 

[Jiji]

I love the app! I have a similar project but using a OBDLink CX instead. I fired Panzuku up with my OBDLink MX and it found my MY 2023 Lightning pretty quickly. I haven't gone anywhere to get trip (breadcrumb) data yet but will later today.

The simplest trip is shift out of Park, wait a few seconds, shift back into Park. You should see a trip in the Trips list and swipe on it to delete it.

The CX is interesting, less expensive but BLE and not Bluetooth. But they also have an LX which is Bluetooth and doesn't have the secondary CAN bus access that the MX+ has (don't currently use any modules on the MSCAN bus).

If anyone out there has an OBDLink LX, it might just work.

 

[Antimater]

The simplest trip is shift out of Park, wait a few seconds, shift back into Park. You should see a trip in the Trips list and swipe on it to delete it.

The CX is interesting, less expensive but BLE and not Bluetooth. But they also have an LX which is Bluetooth and doesn't have the secondary CAN bus access that the MX+ has (don't currently use any modules on the MSCAN bus).

If anyone out there has an OBDLink LX, it might just work.

I did move about a 1/10th of a mile from my carport to the charger. It connected to the truck but did not register the trip or gather data for the cards. In settings-vehicles , it shows the same as the screenshot, 2023 ford unknown, but does have the correct vin. I can confirm it does not attch to the CX. I can DM this stuff to not clog the thread if you want

 

[Jiji]

I can DM this stuff to not clog the thread if you want

The VIN lookup failed to recognize what model you have.

Send me a DM with the interesting part of the VIN (last 5 digits don’t matter) and what type of Lightning Should be displayed and I will add support.

And for those following along, you can go to Settings.Debugger and copy the log history to the clipboard when something bad happens.

 

[02Reaper]

I did move about a 1/10th of a mile from my carport to the charger. It connected to the truck but did not register the trip or gather data for the cards. In settings-vehicles , it shows the same as the screenshot, 2023 ford unknown, but does have the correct vin. I can confirm it does not attch to the CX. I can DM this stuff to not clog the thread if you want

Same thing with my 22 xlt. I took about a 14 mile trip. Connected to the mx+ but no logging

 

[Jiji]

Same thing with my 22 xlt. I took about a 14 mile trip. Connected to the mx+ but no logging

The log says you are not connected, you would see activity there is connected, like this:

23:22.641 .reset(
.nextState(protocolCheck(DokoTypes.CanbusProtocol.iso15765_11bit))
.reset(ATZELM327 v1.4b)
)
23:21.598 .connect(ObdLinkManager.inputStream(opened))
23:21.598 .connect(ObdLinkManager.outputStream(opened))
23:21.586 .info(SE.vehicleStateObservation(.reset)))
23:21.585 .info(SE.connectedVehicleObservation: connected vehicle changed to UndeterminedVehicle)
23:21.582 .info(SE.startStateEngine)
23:21.582 .info(SE.vehicleStateObservation)
23:21.581 .info(SE.connectedVehicleObservation)
23:21.566 .info(PM.startResponseStream)
23:21.565 .info(PM.startCommandStream)
23:21.565 .connect(OBDLink MX+)
==== connected here =====
22:56.552 .error(No protocol 'com.obdlink')
22:56.551 .info(SE.accessoryNameObservation)
22:56.477 .info(DVM: UndeterminedVehicle)

 

[Jim Lewis]

For me, the irony is that I have both an OBDLink MX+ and the CX. But A Better Route Planner only works with iOS BLE (the CX), not the classic BT connection of the MX+ (last time I checked). I'm a relative dummy about smartphone app use while driving, but it would be nice to have a statement about other types of apps we won't be able to use effectively when using Pankuzu hooked up to an OBDLink MX+. Great idea! Thanks for sharing it with us all.

 

[Jiji]

For me, the irony is that I have both an OBDLink MX+ and the CX. But A Better Route Planner only works with iOS BLE (the CX), not the classic BT connection of the MX+ (last time I checked). I'm a relative dummy about smartphone app use while driving, but it would be nice to have a statement about other types of apps we won't be able to use effectively when using Pankuzu hooked up to an OBDLink MX+. Great idea! Thanks for sharing it with us all.

As far as I know, ABRP is the only app that can pull data from OBDII connector that isn’t a traditional scan tool app (OBDLink, Car Scanner, etc). Since only one app at a time can connect to the MX+, you have to pick the one that meets your needs.

 

[Lightning Rod]

So, this app is for apple only?

Sponsored