Building iOS App for 6th Gen (fuel, average miles, and other data)

[pgrossman]

Following, would be interested in using this app if it would work for SR5 trim

It should work with all Gen 6 vehicles, including Tundras, Tacomas, and Sequoias. Although I can't validate that yet, but I'm going to see if the dealer will let me test it at their location. But all the TNGs should use the same PID code. So it'll work across all forerunners, six gen.

Sponsored

 

[Grumpy2634]

Would this work on my 2027 Land Cruiser?

 

[pgrossman]

Did a bunch of testing/PID Sniffing last night and here is all the data I can currently capture from the ODB2

I will continue to "sniff" out the other items, right now I am working diligently to find the Roll/Pitch info. At minimum I can use the iOS devices accelerometer and pipe that data into the app. I will b using the Altimeter of the iOS device to capture altitude for the overloading page.

Let me know if there is something missing you would like to have added and I will see what I can do.

For those wanting to help beta test, I will be setting this up with Apples Test flight. I will let everyone know when this is ready and

 

[TdoubleT]

That’s impressive to say the least. If you have it running on Testflight and you need some to partake, I’m sure you’ll be able to find plenty to help out (including myself) for testing. Cheers and again, fantastic work!

 

[Nodak]

i was going to suggest a torque app pid scan, but you already have a limited and there isnt much difference in a platinum.

 

[jarvis]

Also following along, great work so far - this generally interests me - for my own knowledge, the data is coming direct from the bluetooth OBD2 that is only displaying through the app and the app isn't actually 'storing' any data? I'm thinking through this from a Cyber perspective and privacy risk here.

 

[pgrossman]

Also following along, great work so far - this generally interests me - for my own knowledge, the data is coming direct from the bluetooth OBD2 that is only displaying through the app and the app isn't actually 'storing' any data? I'm thinking through this from a Cyber perspective and privacy risk here.

Yeah, just displaying the data though I will capture the data for a trip and I’ll have the ability for the user to capture all the data and use it later on. It will be encrypted on the phone and only accessible by that user and exported by that user.

 

[MikeD]

I don't know if I’ll have it in the thousands in the final designs,. , although that is the level of detail that the system does provide. I may make that an option in the settings so, individuals can decide accurate they want it to be.

Also, working on a better true distance to empty based on the actual driving at the time

Really great work. Am dreaming about someone taking your code and creating a version for Android Auto. (And I would opt for as much resolution on the fuel levels as possible)

But on your final point: Is there any way to see EXACTLY the algorithm the vehicle is using to calculate distance to empty? I've attempted unsuccessfully to back into the algorithm based on all the data I can collect from the dash - but none of my candidate equations generate repeatable results. Am curious if you find a way to back into the "Toyota" DTE algorithm with more data - am also curious what algorithm you will use to generate a "better true distance to empty based on the actual driving at the time".
This post from me is old and I have lots more data since then, but have given up trying to figure out how Toyota calculates DTE:

Interesting. My data below is based on recording (photo) the DTE before and after fill up over the last 27 fillups and almost 9K miles. When running with air dam and OEM TRD ORP tires I've seen the DTE value after fillup as high as 366 when tank milage was 24.4; with air dam off and 285/70R18 Load E tires on TRD PRO wheels I've seen as low 294 (when tank milage was 15.1 (which included a long off-road excursion). In table below the "blank rows" are where I swapped between wheels & tires.
I DO NOT know exactly how the 6G4R calculates DTE and am interested if anyone KNOWS. (I've checked all the theories and run the equations so I'm really only interested in accurate knowledge if there is a Toyota engineer out there. Thanks

Refuel Date	Odometer Reading	Adjusted Odometer (+3.4%)	Tank Miles	Adj. Miles	Gallons	Fuel Octane	Dist. to go -Before fill	"Actual" dist to go?	Dist. to go -After fill	MPG Tank	Gallons (total)	MPG Total	Range Est.
	7				(fuel added)					(mileage)
5/24/2025	262		255		15.719	87	?	53.2	?	16.2	15.72	16.7	308.2
6/6/2025	586		324		15.699	89	?	68.1	?	20.6	31.42	18.7	392.1
6/14/2025	854		268		14.1	93	?	93.1	?	19	45.52	18.8	361.1
6/27/2025	1216		362		16.073	93	28	65.9	347	22.5	61.59	19.7	427.9
7/4/2025	1487		271		11.767	93	102	166.6	347	23	73.36	20.3	437.6
7/20/2025	1848		361		16.834	93	6	46.4	351	21.4	90.19	20.5	407.4
8/1/2025	2207		359		16.333	93	6	58.6	351	22	106.53	20.7	417.6
8/7/2025	2519		312		16.211	93	24	53.7	351	19.2	122.74	20.5	365.7
8/17/2025	2907		388		16.505	93	12	58.7	361	23.5	139.24	20.9	446.7
8/30/2025	3286		379		17.127	92.5	-2	41.4	361	22.1	156.37	21	420.4
8/31/2025	3657		371		16.818	93	1	48.1	361	22.1	173.19	21.1	419.1
9/6/2025	4004		347		17.063	93	-3	39.4	355	20.3	190.25	21	386.4
9/13/2025	4366		362		16.954	93	-1	43.7	355	21.4	207.2	21.1	405.7
9/19/2025	4737		371		16.459	93	17	57.3	363	22.5	223.66	21.2	428.3
9/20/2025	4906		169		6.938	93	214	293.8	366	24.4	230.6	21.3	462.8
	285/70 no air dam
9/24/2025	5211	5221.4	305	315.4	16.355	93	10	51	348	19.3	246.96	21.1	356
######	5481	5501	270	279.4	15.547	93	31	62.1	330	18	262.5	21	332.1
9/28/2025	5760	5789.7	279	288.7	15.345	93	35	68.8	324	18.8	277.85	20.8	347.8
######	6065	6105.3	305	315.6	17.277	93	-8	31.5	316	18.3	295.12	20.7	336.5
10/10/2025	6260	6307.1	195	201.8	10.55	93	125	161.6	314	19.1	305.67	20.6	356.6
10/11/2025	6557	6614.5	297	307.3	17.024	93	-9	35.7	306	18.1	322.7	20.5	332.7
10/18/2025	6800	6865.9	243	251.5	14.602	93	46	75.7	302	17.2	337.3	20.4	318.7
######	6920	6990.1	120	124.2	8.234	93	167	162.4	294	15.1	345.53	20.2	282.4
	265/70 & Air Dam
10/31/2025	7307	7377.1	387	387	16.274	93	13	64.8	324	23.8	361.81	20.4	451.8
10/31/2025	7630	7700.1	323	323	16.525	93	7	48.4	324	19.5	378.33	20.4	371.4
11/2/2025	7916	7986.1	286	286	15.041	93	76	101	332	20.4	393.37	20.3	387
11/7/2025	8133	8203.1	217	217	8.509	93	155	267.5	335	25.5	401.88	20.4	484.5
11/8/2025	8443	8513.1	310	310	15.324	93	31	74.4	334	20.2	417.21	20.4	384.4
	285/70 no air dam
11/14/2025	8771	8841.1	328	339.4	16.284	93	10	56.6	335	20.8	433.49	20.4	384.6
11/21/2025	8988	9058.1	217	224.6	11.753	93	106	138.5	329	19.1	445.24	20.3	355.5
11/23/2025	9262	9332.1	274	283.5	16.998	93	-7	33.4	311	16.7	462.24	20.2	307.4

Currently I have the 285/70s on the TRD flat black option wheels (+45 offset). Will be moving back to the OEM 265/70 Michelins on TRD PRO wheels (+20 offset) for long trips - to get the range and avoid stops. I like the all black look of both wheels and this solution avoids some of the rubbing on the 285s which will be on for off-roading and when snow expected where I will be. (Handed down the OEM wheels to my son and now have his 2022 SR5 Premium 17x7 alloy wheels and tires available if anyone interested:>)

 

[pgrossman]

Really great work. Am dreaming about someone taking your code and creating a version for Android Auto. (And I would opt for as much resolution on the fuel levels as possible)

But on your final point: Is there any way to see EXACTLY the algorithm the vehicle is using to calculate distance to empty? I've attempted unsuccessfully to back into the algorithm based on all the data I can collect from the dash - but none of my candidate equations generate repeatable results. Am curious if you find a way to back into the "Toyota" DTE algorithm with more data - am also curious what algorithm you will use to generate a "better true distance to empty based on the actual driving at the time".
This post from me is old and I have lots more data since then, but have given up trying to figure out how Toyota calculates DTE:

I'm not sure how Toyota does it. It's a mystery to me. But what I'm going to be doing is a one-minute running average based on the fuel flow and the total fuel in the tank and then also taking into account the EV portion of it so that over any one minute in time you'll have a fairly accurate distance to empty. Obviously if you accelerate past a truck or something, I didn't want it to shoot up and shoot down, so I'm trying to give a running average over the period of time,

 

[pgrossman]

I’m getting ready to begin real-world beta testing for MobileCommandISR,

I’m looking for Toyota owners willing to help test the app with their vehicles and Bluetooth OBD-II adapters.

A sincere thank-you to everyone who volunteers. Your interest and willingness to help mean a lot.

I won’t be able to include everyone in the initial beta group. Please don’t take it personally if you aren’t selected. I need to build a balanced testing group covering different Toyota models, model years, generations, powertrains, and Bluetooth adapters. Selection will be based on creating the most useful mix—not on who volunteered first or who has the newest vehicle.

I’m Initially focused on 6th Gen (and 5th Gen)

• Tacoma
• 4Runner
• Sequoia
• Land Cruiser
• Tundra
• Other potentially useful Toyota configurations

If you’re interested, please complete the short form below:

Beta Tester Form

Even if you aren’t selected for the first round, I may contact you for a later testing phase as the app expands. Thank you again for helping me make MobileCommandISR accurate, reliable, and useful in the real world.

 

[SC4Runner]

I filled out the form and looking forward to chipping in! The information you are gathering and the layout you are providing shows a lot of potential.

 

[Kurtz48]

Filled out the form. I don't currently have a Bluetooth OBD-II adapter. Is there one anyone is willing to recommend?

 

[pgrossman]

Filled out the form. I don't currently have a Bluetooth OBD-II adapter. Is there one anyone is willing to recommend?

I currently use the Vgate vLinker MC+ in my research, as I started looking at building this app, that one came out as having the most information available. I don't know how much different it is than any of the other ones, but this is a list that I sort of have currently that we're going to be looking at.

Recommended Bluetooth OBD-II adapters for MobileCommandISR, in order:

1. Vgate vLinker MC+ — Our preferred adapter and the only one fully tested with MobileCommandISR on the sixth-generation 4Runner. It reliably supports Toyota-specific enhanced PID requests, firmware updates, automatic sleep/wake, and long diagnostic commands. Limitation: its 2 KB buffer can overflow during unrestricted passive CAN monitoring, although normal MobileCommandISR polling works well.
2. OBDLink CX — Best premium BLE alternative. Excellent connection quality, Bluetooth 5.1 LE, raw-CAN support, firmware updates, and very low sleep power. Limitation: not yet physically validated with MobileCommandISR, and it is more expensive than most generic adapters.
3. Veepeak OBDCheck BLE+ Plus — Excellent value. It uses ELM327 v2.2, supports additional AT commands, works with iPhone/iPad over BLE, and has broad third-party-app support. Limitation: no MS-CAN or SW-CAN support and not yet tested directly with MobileCommandISR.
4. Vgate vLinker FD+ — A capable vLinker-family alternative supporting iOS BLE, ELM and ST commands, raw CAN, and MS-CAN. Limitation: it is primarily optimized for Ford/FORScan applications, so many of its extras provide little benefit on a Toyota. Despite the name, its published specifications do not list CAN FD support.
5. Vgate iCar Pro BLE 4.0 — Good budget choice with iOS BLE, all standard OBD-II protocols, firmware updates, and automatic sleep/wake. Limitation: it is an older, lower-throughput design than the vLinker MC+, making it less desirable for rapid multi-PID telemetry.
6. Carista EVO — Well-built current-generation Bluetooth adapter with Toyota support, good power management, and strong diagnostic capabilities in the Carista ecosystem. Limitation: Carista’s documentation focuses primarily on its own app, so direct MobileCommandISR compatibility still needs verification.
   
   I would not currently recommend app-locked adapters such as BlueDriver. I would also exclude the otherwise excellent OBDLink MX+ because it uses Bluetooth 3.0 rather than BLE

 

[Nodak]

from what i read, you dont want to use a BLE adapter, it has slower tranmits for real time updates.

roughly 30 updates/sec vs 100 for non ble adapters.

 

[pgrossman]

from what i read, you dont want to use a BLE adapter, it has slower tranmits for real time updates.

roughly 30 updates/sec vs 100 for non ble adapters.

That’s a fair concern, but the 30-versus-100 figure isn’t a general BLE limitation. Some inexpensive BLE adapters are slow, but good BLE adapters can transmit much faster. The actual update rate also depends on the vehicle, ECU response time, number of requested PIDs, adapter firmware, and how the app schedules requests.

The Vgate vLinker MC+ is specifically designed for higher-volume diagnostic and dashboard applications. It supports a 500-kbps internal UART, long diagnostic requests, user-defined commands, and firmware updates. More importantly, 1 have tested it extensively with MobileCommandISR on the actual 4Runner, including Toyota-specific enhanced data, and BLE has not been the limiting factor.

MobileCommandISR also does not need 100 complete updates per second. Trip data is recorded at approximately 1 Hz, and the displayed information is divided among several telemetry channels. A reliable 20–30 complete PID responses per second would already provide more than enough data for this type of dashboard.

I did find one real limitation: the MC+ has a 2 KB buffer and can report BUFFER FULL when attempting unrestricted full-bus passive CAN monitoring. That matters for engineering-level CAN sniffing, but it has not been a problem for MobileCommandISR’s normal targeted polling.

So I would agree that adapter speed matters, but I would not rule out BLE categorically. For an iPhone app, BLE provides reliable CoreBluetooth connectivity, automatic reconnection, low power consumption, and continued Wi-Fi/cellular availability. Based on our physical testing, the vLinker MC+ remains our preferred adapter unless another model proves measurably better in the actual app and vehicle.

Sponsored