EzioDash Pro

Advanced dashboard for Gran Turismo 7

Use your iOS device to get telemetry data and more from Gran Turismo 7 – don't miss out on vital information!

Get Started Go to App Store

Scroll for more information.

About EzioDash Pro

EzioDash Pro is an extended version of EzioDash, but where the free version has basic functionality, EzioDash Pro has a lot more features that can give you the edge over your competitors. All the functionality of the free version is available in the pro version, in that it connects to your PlayStation and GT7 to capture and display telemetry data. As such, your iOS device is required to be on the same local network as your PlayStation console. Naturally, your iOS device most likely connects via a wireless connection (WiFi), but your console may connect either by wired connection or wifi.

EzioDash Pro is a paid app.

EzioDash Pro requires iOS 16 or higher (iPhone 8 or higher recommended).
For reference, the free version still works on iOS 15.

Disclaimer

First and foremost, there is no guarantee that this app will work forever. The telemetry from Gran Turismo 7 is an undocumented feature, reverse engineered by brighter people to enable the rest of us to enjoy this. That said, there is no guarantee that this feature of the game will remain accessible to the public forever, and if it should be removed, changed or otherwise locked, this app will cease to work.

Also, please note that the app you download may differ in visuals slightly.

The app consists of up to 4 different dashboards*

* The number of dashboards varies depending on what you choose to activate in the app. If you're not using it, you can toggle it off.
Please also note that the screens shown here may differ slightly from the currently available version, but as a whole it should be similar enough.

To navigate the app, you simply swipe left and right between the screens. When starting the app you will begin on the "third" screen; the connection screen. From left to right in the app, the screens are**; about, settings, connection, full dashboard, simple dashboard, hybrid dashboard and trace graphs screens.
** When all screens are enabled.

  • This screen is simply an "About" screen, with info on the app version (top right), a donation link if you wish to contribute further, contact info, some info on the app and the game, a bit of credits to various people somehow involved in the birth of the app, beta testers and so on.

  • This screen shows the settings that are available to change, divided into multiple sections to break it up into more manageable chunks. For example changing between metric units and imperial units, what data traces to show, pit crew audio settings, tire temperatures and so on.

  • 03 The connection screen

    This is where you arrive when the app starts. This is where you either let the app discover your Gran Turismo 7 game on your network or enter the IP address of your PlayStation to connect to the game. You will of course also find a small image of Ezio, our italian greyhound, who gave name to the app.

    From here you can swipe right to the settings and about screens, or swipe left to the dashboard screens.

  • This will for many be the main screen of the app. This is where you can see the telemetry in a dashboard-like fashion. For players using PSVR2, this will of course not be visible, which is where the pit crew commentary can come in handy. More on that later.

  • This is a simplified version of the dashboard, focused only on the tyre status and fuel information. There is also information on top speed, average/median lap times and time of day on track. Other than that, it's basically the same as the full dashboard.

  • The hybrid dashboard mixes the simple dashboard with a limited version of the traces graph. Here you will find your throttle and brake traces, along with tyre temperatures, fuel information, lap times and a toggle between position, lap and gear.

  • This screen will show data traces in a graphical format, for things like throttle and brake input, selected gear, rpm, speed and so on. This can sometimes provide very useful information for how you perform on track.

 

Telemetry & Pit Crew

Of course the telemetry in itself does not necessarily make you a faster driver, but it can provide you with more information about your driving. And whether or not you are using PSVR2 when you race, your race engineer may well be the difference between running out of fuel before reaching the finish line or not!

Top speed

Compare top speeds of various cars when it suits you, without having to watch the in-game speedometer.

Fuel usage

Keep better check on how much fuel you are using, and how far you can go on the fuel you have left.

Tyre temperatures

Managing your tyres is a very important for good results, EzioDash lets you know current and average tyre temperatures.

Lap comparisons

EzioDash lets you keep track of your average lap times for comparison, only counting your flying lap times.

PSVR2

The Pit Crew feature can be highly valuable for players who drive using PSVR2.

Early warnings

Stay ahead of running out of fuel, with helpful reports from the pit crew regarding fuel status.

Maintain pace

Keeping your tires in the proper window is more important than ever. Your race engineer will tell you if you cook them!

Laps to go

Your race engineer will also try to calculate how many laps you have left, for those endurance races!

A note about predictions

It goes without saying that this app will never give you perfect predictions with regard to how long you can go on a given amount of fuel, or match up pit stops with tyre wear and compounds and so on. This app is a tool, a tool that you can use to give you more information to base your own decisions on. The app may say that you CAN go to this or that lap, but if you suspect that your tyres will wear out well before that – pit at your convenience and let the app pick up again afterwards, it will try to adapt. At the end of the day, race strategy is 99% determined by how you use the inside of your head and how you perform on track.

Download from the App Store

EzioDash Pro is available to download from the iOS App Store, giving you the best user experience and easy updates.

Requires iOS 16 or higher, and should also work on iPad in landscape orientation.

Get EzioDash Pro from
the App Store

How to use EzioDash Pro

Using EzioDash Pro should be pretty straightforward, although there are a few things that you may want to read up on. Here is a short "how-to" (note that the app you download may differ slightly visually):

Connection screen

The connection screen is the first screen when you start the app:

Please note: screens may differ slightly from the current version.

Making a long story short; this is where you connect to Gran Turismo 7, either by using the auto-discover feature or by manually entering the IP of the PlayStation console running Gran Turismo 7 that you want to connect to. Take care to enter the address exactly as shown in the network settings of your PlayStation console. If the address is valid, the "CONNECT" button will activate. Tap "CONNECT" and the app will start trying to connect to your game. When connection is established, ip address of your console will show up in the input box, the text beneath the address field will change to "CONNECTED", and the thin bar will be colored green (green denotes a good connection). You can now click the right arrow or swipe from right to left to change to the dashboard screen.

Read more

Settings screen

The settings screen is where you will change settings:

Please note: screens may differ slightly from the current version.

Here you will find the various settings that enable you to for example choose metric or imperial units (separate toggles for speed/distance and tyre temperatures), enable the trace graphs, turn on the pit crew audio commentary and so on.

The settings are divided into several categories, and will remember where you left off previously. Whether you want to change the granularity for en older iOS device, change the tyre temperature window or disable certain pit crew audio comments, this is where you will find the setting for it.

Read more

Full dashboard screen

The full dashboard screen is the main screen when using the app:

Please note: screens may differ slightly from the current version.

A quick run through of the elements; top left is the connection status bar (same as on the connection screen), followed by the RPM indicator bar. Top right is the on-track time-of-day (changes according to time progression). Left hand side contains position, along with current and top speeds. To the right of this are the throttle and brake indicator bars, with the current gear and RPM readouts in between. Beneath this is the fuel bar, with the fuel consumption info underneath. To the right of this are the tyre temperatures, indicating the average and current temperatures. Far right you find the current lap, last, best and average lap times.

Read more

Simple dashboard screen

The simplified dashboard screen can also be used as your main screen:

Please note: screens may differ slightly from the current version.

The simplified dash focuses mostly on tyres and fuel, but at the top you will find the same connection status, rpm bar and time of day readouts as on the full dash. The front tyres are on top, the rear tyres at the bottom, with the fuel information in the space between. Additionally, on the right hand side you can find the current top speed, current lap/gear/position as well as the average (or median) lap time (plus possibly the cutoff lap time).

Read more

Hybrid dashboard screen

The hybrid dashboard combines the simple dash with traces for brake and throttle:

Please note: screens may differ slightly from the current version.

This screen shows your brake and throttle traces (you can toggle between 3 layouts) together with tyre temps, fuel info, lap times and more.

Read more

Trace graphs screen

The trace graphs screen shows graphical data of your telemetry:

Please note: screens may differ slightly from the current version.

This screen will show data traces for your throttle and brake input, tyre temperatures and so on. What is displayed here is selectable in the settings, to remove unnecessary clutter depending on what info you are interested in.

Read more

About screen

The about screen contains some further info and credits:

Please note: screens may differ slightly from the current version.

Here you can find the donation link, a link to this page, a short informational blurb and legal information with regards to the Gran Turismo and PlayStation trademarks. Here is also a list of people that have been instrumental in one way or another in getting this app to where it is.

Frequently Asked Questions

Here is a collection of answers to questions you may have:

  • Why won't the app connect to my PlayStation console?

    Follow these points to try to resolve the problem:

    • First and foremost; check that the IP address that is shown (or that you have entered manually) is the correct one – compare with what your console is showing in the network settings.
    • Make sure that your iOS device allows "Local Network Access" (or the equivalent in your language). The app will ask for permission to access the local network on first launch, and if you don't allow it access, it will not work. If so, this is a setting in iOS that you need to change, you should find EzioDash Pro listed there. For more info, visit Apple's support page here: support.apple.com/en-us/102229
    • Make sure that the iOS device and the PlayStation console is on the same local network. You need to be on a wifi network with the same IP address range as the console (preferably the same local wifi network, i.e. same SSID and frequency, if the console is also on wifi).
    • If both devices are on the same wifi, prioritize 5GHz above 2,4GHz unless either device is far from the router or access point.
    • Other possible network issues may of course occur, but issues with your physical local network is beyond this FAQ and most likely something you need to fix with your network or router.
    • Make sure that Gran Turismo 7 has loaded, it must have reached at least the initial news screen where you select "World Map" before it can actually connect.
    • Sometimes the ports used for the telemetry can be blocked for an indefinite amount of time. Seemingly, there is no need to restart the game, you just have to wait it out.

  • No, unfortunately that's not what happens. Everyone I've discussed this with have claimed it to be near impossible to achieve, and likely not worth the money invested to make it happen either. So for us PSVR2 users, we will have to make do with the excellent race engineer from the Pit Crew feature in the app. Personally I have a thing for Fiona from Scotland, especially in her enhanced voice version!

  • Yes, personally I can recommend both the Sony PlayStation Pulse Explore Wireless Earbuds as well as their Sony PlayStation Pulse Elite Wireless Over-ear Headset. Both of these plugs into the PlayStation console using a small dongle, by which the sound from the console is transmitted. Along with that, you can pair them via Bluetooth to you iOS device, and they will work with both sound inputs pretty nicely. I know there are other brands that does more or less the same, but these are the ones that I have personal experience with.

  • This app is primarily not intended to be run in the background, and even if the setting to allow it to run in the background is on, some features will not work while the app is in the background. The app will try maintain the connection, but no audio will be played unless the app is active.

  • The dashboard will only show actual telemetry data while you are either on track, having entered a race in a lobby or watching a replay. And, you do need to be connected to the game, of course.

  • There are a number of network-related issues that can influence the connection between the app and the game running on the PlayStation console. This is beyond the scope of this page, but it can be a good idea to test the app and the connection quality in a situation where you are certain that no other devices on the same local network are congesting the network traffic in any way. Also, for slower devices and/or networks, you can try to set a higher granularity and see if that solves the problem for you.

    That said, it is still possible that older iOS devices are unable to keep up with decrypting the telemetry, which may indicate a lower quality connection. This does not mean that the app won't work, but it may in time lag behind from what you experience in-game. Your mileage may vary, and you will have to evaluate if it "works" or not, for you.

  • Due to the nature of the app where it needs to decrypt the telemetry data and update the dashboard at up to 60 times per second, the energy consumption will naturally increase, and with that comes extra heat. There is not much that can be done about this, but we recommend that you keep the iOS device connected to wired power to keep the heat from a discharging battery to further add to the build up of heat. Increasing the granularity may also help with this problem.

  • This is something you would have to ask Polyphony Digital about. The telemetry from replays is NOT 100% the same as what the live data was. This is most obvious if you look at the fuel gauge during a replay; you will most likely see that the amount of fuel left "jumps" up and down a bit.

  • This app was never developed to be a customizable dashboard, and it is highly unlikely that the app in its current form will ever allow for any customization.

  • There are a few instances where the dash will reset. This is on purpose. For example, while you are in a lobby and have entered the race (i.e. you have clicked the green checkmark or you have entered the track) the dash will not reset. But as soon as you are considered to be "in the menus" so to speak, the dash will reset. For example, in a lobby, while you are entered, the dash will not reset. However, if you click the red cross button to exit the race (not the lobby), the dash will reset. The reasoning is that you may want to reset the dash at some points, and this is a simple way to do it.

    You may also experience this due to network issues, where the connection is dropped for some reason that is out of the control of the app. If or when this happens, the app will try to restart the telemetry, which will also reset the data up to that point.

  • This usually only happens if you coast a lot at the beginning of your run, or apply the brake while on the throttle respectively. Since the app has no previous data to work with, the percentage of these two readouts go up very quickly. However, it may then take some time to get them down to "normal" levels again, so you can give the gear indicator a quick tap to reset these two readouts (although the same logic will then apply again).

  • Naturally there is a certain difficulty in predicting the future, and even with dozens of laps of data available, there may be small margins that can cause big effects at the end of the race. The app tries to err on the safe side, so if you're really on the edge with fuel, the app may try to tell you to stop another time – this is when you as a driver have to use the inside of your head. Within a certain margin, the pit crew feature will tell you to save fuel, but there is a gray area where you're in between and have to make the call to save fuel (or pit again) all by your lonesome. Of course if you are using the various fuel map settings in the game, that will throw these calculations off, and you will get incorrect values and predictions.

    Note: For races based on duration rather than laps, the app will use your median lap time to give you an estimate of how many laps are left. If you know that you will have good pace for example at the very end of a race, or vice versa, you may have to compensate for that. The same also applies if you want to push harder during a final stint, in which case you will likely need to put more fuel in the car, or you will have to save fuel on the last few laps. If your current pace differs from your median lap time, the estimation may be off, but it should gradually adjust itself. Use your common sense in addition to what the app tells you.

  • The most likely culprit here is that some tracks have pit lanes that aren't at the start/finish line. One example is the Tokyo Expressway South layouts, where the pit lane is in a parking garage some 1/3 of the total track distance (depending on what direction it is) from the start/finish line. For obvious reasons this messes up the fuel per lap percentage, but it will gradually correct itself as you lap around the track. Of course if you are using the various fuel map settings in the game, that will throw these calculations off, and you will get incorrect values and predictions.

  • The reason here is that it is the easiest way to calculate how much fuel you consume per lap. The app will try to learn how much fuel you had at the start of the lap, and compare that with what you had when passing the finish line, starting the next lap. This will gradually give you an average fuel amount consumed per lap, which is then used to calculate pit stops and how far you can go on the fuel you have. Of course if you are using the various fuel map settings in the game, that will throw these calculations off, and you will get incorrect values and predictions.

  • No, this app has no such functionality available publicly at the moment. Even if the telemetry is less than 350 bytes per packet, it sends a new packet 60 times per second. To add to that, a human usable data file, for example a CSV text file, needs more space. And even unpacked, that amounts to 60 megabytes per hour. Maybe not a lot in today's day and age, but it would also involve functionality for the app to manage those recorded sessions. In the future, this may be implemented, but no guarantees on that front.

  • No, there is no way to get the game to send another player’s telemetry.

  • Primarily, we can only use what data we can access. For example, there is no way for the app to know what tyres you have on the car, or how much wear there is. It's simply not data that is available in the telemetry. It may be in the game, but it's not publicly available, as far as we know. For some things, we can try to guesstimate, for example we can make educated guesses as to which track we're currently on, whereas the current car (when on track) is available in the telemetry.

    So basically, if it's relevant to display or convey during a race and is in the telemetry, the app will try to provide that information to you. If there is data that could be useful, and it's not shown, chances are that it's not available in the telemetry. Simple as that. There is more data, but actually displaying the X, Y and Z coordinates for example, seems meaningless.

  • This is related to the speech synthesizer having to run on the main thread of the app, and the freeze occurs immediately after a spoken sentence is finished (no data is lost, as far as I can tell). I have tried to remedy the situation, but since both the user interface, which is the obvious thing that freezes momentarily, and the speech feature needs to fight for the same CPU cycles, there's a limit to what can be done.

  • No, it's not broken as such, but the app is not, and likely will not, be built to handle navigating around in the replay, and you may experience that the commentary is queued up for quite a while if you fast forward lap by lap. It may also take a flying lap or two for the app to calculate any trustworthy data, so if you want to use the app for analysis, I recommend that you let the replay run its course – if anything, I recommend that you record using the built-in screen recording of both the PlayStation and your iOS device to review the data afterwards.

  • No, there is no portrait mode. The app is only available in landscape mode.

  • Ezio is our italian greyhound, born in the year of the pandemic, 2021. Italian greyhounds may not the most common breed of dog, for sure, but they are one of the most charming beings you can find. My family have had iggys (from the acronym IG) since 1984.

Connecting EzioDash to Gran Turismo 7

This section describes how to setup EzioDash together with your PlayStation console running Gran Turismo 7

When you first launch EzioDash (as in the very first time), you should get an iOS dialog screen that asks you for permission for "Local Network Access" – You need to allow this, or the app will NEVER connect to anything, anywhere. You can find a setting for this in you iOS settings later, if you do tap the wrong choice here.

There are several elements on the connection screen, but the main one is the blue "CONNECT" button. As default, the app will try to auto-discover your Gran Turismo 7 game when it is running on your PlayStation console, meaning that you should be able to just tap "CONNECT" and be done.

However, if this fails, you should go into the settings by either swiping right or tapping the gear icon in the lower left corner. There you can toggle the auto-discover feature off, which enables you to manually enter the IP address of your PlayStation console. Tap the input box and enter your IP address, for example you can enter "192.168.0.128" (without the quotes) if that is the IP address of your console. Once entered, the app will remember the last used IP until you change it. Once you have entered a valid IP address (the app allows a variety of formats including valid IPV6) the "CONNECT" button will activate, meaning you can tap it to try to connect to the game's telemetry ports.

Note: To find the IP address of your console, you need to go into the network settings of your PlayStation where you can select a menu option to view your network connection. Note the IP address, which is likely an IPV4 address with 4 numbers separated by period characters, for example 192.168.1.87 or similar looking. Do note that your address may vary from the examples here, and that it CAN change from time to time, depending on how your local network is setup.

When you've tapped "CONNECT" the app will start trying to connect, and the status indicator below the IP address will change from "DISCONNECTED" to "CONNECTING". If everything works like it should, the status indicator should change to "CONNECTED" and the bar below should begin to fill up to indicate the connection quality. The status indicator bar should fill up green when the app connects, and if it remains at a steady green color you can assume you have a good connection. A red, orange or yellow bar means that the connection is bad and the app is missing a lot of telemetry packets from the game.

To proceed to the dashboard once connected, you can either swipe left on the screen or tap the large circled arrow pointing to the right to take you to the dashboard screen.

If/when you want to disconnect, you can go back to this screen and tap the "DISCONNECT" button on the connection screen. The app does NOT disconnect by itself, not even if the game or PlayStation console is shut down. However, if the app goes into the background or the device goes into standby (by itself or manually) it will disconnect, unless you have set the app to remain active* in the background (defaults to off).

* Note: The app will only maintain the connection, it will not play pit crew messages, and iOS may force quit the connection at times.

The connection screen is the first screen when you start the app:

Please note: screens may differ slightly from the current version.

The connection status indicator bar

The connection status indicator bar is present on both the connection screen and the dashboard screens. On the connection screen it is front and center, accompanied by a status text indicating the connection status of the app. On the dashboard screens you will find it in the top left corner.

The connection quality is displayed as a bar that fills up and is colored green for a good connection. If your connection quality is low, the telemetry reported by the dashboard may be wrong, or lagging behind. It is therefore important to make sure that your local network connection is as good as it can be.

Telemetry from the game is sent 60 times per second (with minor variations), and there is no guarantee that a telemetry packet is received, or that it arrives in the correct order. Due to this, the app discards packets that are sent out of sequence, as well as counting the number of missed packets. This is the basis for the connection quality indicator. The more missed or lost packets, the lower the quality is considered.

The full dashboard readouts

This section describes the various parts of the full dashboard

The full dashboard consists of multiple elements, which is explained below:

  1. Connection quality indicator. This bar goes from red to orange to yellow to green to indicate the quality of the connection. Normally this should be a full green bar if you have a good local network environment.
  2. Gear shift indicator. This bar is directly connected to the RPM of the car, and corresponds more or less to the in-game gear shift indicator. It fills up from the left towards the right, starting from green through yellow, orange and red and can optionally start flashing between blue and white when it reaches what in the game is the flashing shift indicator.
  3. In-game time of day. This is a 24h clock corresponding to the time of day on the current track. If the game has time progression enabled, this will show the correct on-track time. Note: For tracks that don't have a full 24 hour cycle, this time of day may seem to be stuck, until it switches over to the first morning time of day. This is only applicable in races where the time progression is either high enough to cause a full day cycle to pass, or is long enough to pass from one day to another.
  4. Current speed or Position. This is the car's current speed (in kph or mph). You can tap this readout to toggle (4, 5 and 6) between two modes; SPEED, TOP SPEED and DISTANCE – or POSITION, SPEED and TOP SPEED.
  5. Top speed* or Current speed. This is the top recorded speed (in kph or mph). Can be reset by tapping the digits.
  6. Distance travelled* or Top speed.* This is an estimate of the distance travelled (km or mi), accuracy is not 100%. Can be reset by tapping the digits.
  7. Fuel indicator. A simple bar and percentage of fuel left. When the app can calculate pit stop predictions*, it will display the predicted number of stops on the left hand side, and the next predicted pit window on the right hand side – these are predictions, remember that. Note: In races without fuel consumption, this will always remain at 100%.
  8. Fuel used per lap.* This shows the percentage of fuel used per lap (only when you've passed the starting line) if fuel consumption is enabled.
  9. Laps remaining.* This shows an estimate of how many laps you can finish based on your past consumption and fuel remaining.
  10. Time remaining.* This shows an estimate of how many minutes and seconds of fuel you have left, based on an average lap time (which can be reset) and your fuel consumption.
  11. Brake indicator. This indicator bar shows how much brake input the game is getting. Note that this may not correspond exactly to the input of your pedals or controller.
  12. Throttle indicator. This indicator bar shows how much throttle input the game is getting. Note that this may not correspond exactly to the input of your pedals or controller.
  13. Gear indicator. This shows the current gear (if enabled, the internal app state shows above). Tapping this resets the "lift and coast" and "braking on throttle" meters.
  14. Braking on throttle.* This small indicator increases/decreases depending on how much you brake while simultaneously being on throttle.
  15. Lift and coast.* This small indicator increases/decreases depending on how much time you spend off both throttle and brake.
  16. RPM. This indicates the current RPM of the engine.
  17. Tyre temperatures; front left, front right, rear left and rear right. These 4 indicators shows the tyre temperatures. The top temperature digits* shows the average temperature* for that tyre over the past 30 seconds or so. The bottom temperature digits show the current, actual temperature as reported by the game. The background of the tyre is filled with a gradient ranging from blue (cold) to green (working temp) to red (overheating). The color at the top of the tyre follows the average tyre temperature, and the bottom color follows the current tyre temperature. *You can tap on any of the tyre readouts to toggle between both temps, or showing only the average or current temperature in larger font size for better readability.
  18. Current lap. This indicates the current lap as reported by the game.
  19. Last lap time. This indicates your last lap time as reported by the game.
  20. Best lap time. This indicates your best lap time as reported by the game.
  21. Average/Median lap time.* This indicates your average (or median, if you enabled that in the settings) lap time. This is based only on your flying laps. Can be reset by tapping the digits. Note: If you have enabled a cutoff lap time in the settings, it will be shown below this readout, and any laps exceeding the cutoff time will not be counted towards the average/median lap time.

* denotes a readout that is NOT straight from the game telemetry, also meaning that it may not be 100% accurate at all times. Some data is based on qualified guesswork, but should be usable and "good enough" in most cases.

There is also a toggle in the settings to display the app's internal state tracking, which when enabled shows as a text above the gear indicator. It has the following possible states; MENUS, ENTERED, PITENTRY, PITLANE, PITSTOP, OUTLAP and FLYING.

The dashboard screen is the main screen of EzioDash:

Please note: screens may differ slightly from the current version.

Why are some readouts zero or empty?

For obvious reasons some readouts shows zero or no information when starting (or after a reset), but there are a few readouts that have special conditions.

Beneath the fuel bar, there are three readouts. The first readout shows percentage of fuel per lap, and shows only if fuel consumption is active and only after the first lap has completed. The second readout shows laps remaining, and uses the same conditions as fuel per lap. The last readout is time left for the remaining fuel. This third readout only shows if/when you have an average lap time value.

The average lap time is only available when the app can determine that you've completed a flying lap. For this reason, if you go straight into the pits after an outlap or the first flying lap, you will not get an average lap time.

Lift and coast

The app tries to keep track of how much lifting and coasting you do. This basically means how much you let the car just "roll" through corners and such. For this, the app counts how many packets pass by where you are off both throttle and brake. Of course, this would give a false picture if those were the only conditions; this is only measured when the game is not paused, the car is on track (outlap or flying lap) and in gear. Also, the speed must exceed 20 kph (about 12-13 mph) and it stops counting after 3 seconds of continued lack of throttle and brake input.

This meter can be reset by tapping the gear indicator (also resets "braking on throttle").

Braking on throttle

EzioDash also tries to keep track of how much of the time you apply brake at the same time as you are on throttle. For some cars and driving styles, this is a common practice, but if you know that you are touching the brake pedal while you shouldn't, this is a good indicator to see how much of this you are actually doing. Knowing enables you to try to change a potentially bad habit. As with the lift and coast, this is only measured under certain conditions; not paused, on track (outlap or flying) and above 20 kph.

This meter can be reset by tapping the gear indicator (also resets "lift and coast").

The simplified dashboard readouts

This section describes the various parts of the simplified dashboard

The simplified dashboard consists of a select number elements:

  1. Connection quality indicator. This bar goes from red to orange to yellow to green to indicate the quality of the connection. Normally this should be a full green bar if you have a good local network environment.
  2. Gear shift indicator. This bar is directly connected to the RPM of the car, and corresponds more or less to the in-game gear shift indicator. It fills up from the left towards the right, starting from green through yellow, orange and red and can optionally start flashing between blue and white when it reaches what in the game is the flashing shift indicator.
  3. In-game time of day. This is a 24h clock corresponding to the time of day on the current track. If the game has time progression enabled, this will show the correct on-track time. Note: For tracks that don't have a full 24 hour cycle, this time of day may seem to be stuck, until it switches over to the first morning time of day. This is only applicable in races where the time progression is either high enough to cause a full day cycle to pass, or is long enough to pass from one day to another.
  4. Tyre temperatures; front left, front right, rear left and rear right. These 4 indicators shows the tyre temperatures. The top temperature digits* shows the average temperature* for that tyre over the past 30 seconds or so. The bottom temperature digits show the current, actual temperature as reported by the game. The background of the tyre is filled with a gradient ranging from blue (cold) to green (working temp) to red (overheating). The color at the top of the tyre follows the average tyre temperature, and the bottom color follows the current tyre temperature. *You can tap on any of the tyre readouts to toggle between both temps, or showing only the average or current temperature in larger font size for better readability.
  5. Fuel indicator. A simple bar and percentage of fuel left. When the app can calculate pit stop predictions*, it will display the predicted number of stops on the left hand side, and the next predicted pit window on the right hand side – these are predictions, remember that. Note: In races without fuel consumption, this will always remain at 100%.
  6. Fuel used per lap.* This shows the percentage of fuel used per lap (only when you've passed the starting line) if fuel consumption is enabled.
  7. Laps remaining.* This shows an estimate of how many laps you can finish based on your past consumption and fuel remaining.
  8. Time remaining.* This shows an estimate of how many minutes and seconds of fuel you have left, based on an average lap time (which can be reset) and your fuel consumption.
  9. Current speed. This is the car's current speed (in kph or mph). This can be toggled between CURRENT SPEED and TOP SPEED* by tapping on readout (10), see below.
  10. Current lap. This shows the current lap of the race, but you can also tap this readout to toggle between CURRENT LAP, CURRENT GEAR and CURRENT POSITION (if applicable). When you tap through all three options, the readout above (9) will toggle between CURRENT SPEED and TOP SPEED*.
  11. Average/Median lap time.* This indicates your average (or median, if you enabled that in the settings) lap time. This is based only on your flying laps. Can be reset by tapping the digits. Note: If you have enabled a cutoff lap time in the settings, it will be shown below this readout, and any laps exceeding the cutoff time will not be counted towards the average/median lap time.

* denotes a readout that is NOT straight from the game telemetry, also meaning that it may not be 100% accurate at all times. Some data is based on qualified guesswork, but should be usable and "good enough" in most cases.

The simple dashboard screen is one of the dashboards in EzioDash:

Please note: screens may differ slightly from the current version.

The hybrid dashboard readouts

This section describes the various parts of the hybrid dashboard

The hybrid dashboard consists of a select number elements, most are the same as the standard and simple dashes:

  • Connection quality indicator. This bar goes from red to orange to yellow to green to indicate the quality of the connection. Normally this should be a full green bar if you have a good local network environment.
  • Gear shift indicator. This bar is directly connected to the RPM of the car, and corresponds more or less to the in-game gear shift indicator. It fills up from the left towards the right, starting from green through yellow, orange and red and can optionally start flashing between blue and white when it reaches what in the game is the flashing shift indicator.
  • In-game time of day. This is a 24h clock corresponding to the time of day on the current track. If the game has time progression enabled, this will show the correct on-track time. Note: For tracks that don't have a full 24 hour cycle, this time of day may seem to be stuck, until it switches over to the first morning time of day. This is only applicable in races where the time progression is either high enough to cause a full day cycle to pass, or is long enough to pass from one day to another.
  • Brake and throttle traces. These two lines represent the throttle (green) and brake (red) traces over time (see the traces graphs for more information). As with the trace graphs, you can tap the display and use the slider to change the displayed duration.
  • Tyre temperatures; front left, front right, rear left and rear right. These 4 indicators shows the tyre temperatures. The top temperature digits* shows the average temperature* for that tyre over the past 30 seconds or so. The bottom temperature digits show the current, actual temperature as reported by the game. The background of the tyre is filled with a gradient ranging from blue (cold) to green (working temp) to red (overheating). The color at the top of the tyre follows the average tyre temperature, and the bottom color follows the current tyre temperature. *You can tap on any of the tyre readouts to toggle between both temps, or showing only the average or current temperature in larger font size for better readability.
  • Fuel indicator. A simple bar and percentage of fuel left. When the app can calculate pit stop predictions*, it will display the predicted number of stops on the left hand side, and the next predicted pit window on the right hand side – these are predictions, remember that. Note: In races without fuel consumption, this will always remain at 100%.
  • Fuel used per lap.* This shows the percentage of fuel used per lap (only when you've passed the starting line) if fuel consumption is enabled.
  • Laps remaining.* This shows an estimate of how many laps you can finish based on your past consumption and fuel remaining.
  • Time remaining.* This shows an estimate of how many minutes and seconds of fuel you have left, based on an average lap time (which can be reset) and your fuel consumption.
  • Last lap time. This indicates your last lap time as reported by the game.
  • Best lap time. This indicates your best lap time as reported by the game.
  • Average/Median lap time.* This indicates your average (or median, if you enabled that in the settings) lap time. This is based only on your flying laps. Can be reset by tapping the digits.
  • Current lap. This shows the current lap of the race, but you can also tap this readout to toggle between CURRENT LAP, CURRENT GEAR and CURRENT POSITION (if applicable).

* denotes a readout that is NOT straight from the game telemetry, also meaning that it may not be 100% accurate at all times. Some data is based on qualified guesswork, but should be usable and "good enough" in most cases.

The hybrid dashboard screen is one of the dashboards in EzioDash:

Please note: screens may differ slightly from the current version.

Trace Graphs

This section explains the trace graph display

If you have enabled the trace graphs in the settings, you will find this screen either by swiping left past the full and simple dashboards, or by tapping the small icon in the bottom right corner of the Traces tab in the settings.

Note: This feature does not record all data since you started the app. I want to be perfectly clear that you can not scroll sideways to see data from 10 laps ago. At least not in this iteration of the app. Whether this is something to expand upon in the future – we shall see.

What it does do is to store approximately 120 seconds of the most recent telemetry data points collected. The data points that you can see as a graph line on the screen are as follows:

  • Throttle trace shows how much throttle input the telemetry have recorded. Good way to see if you are giving smooth throttle input or not.
  • Brake trace shows how much brake input the telemetry have recorded. This is useful to see whether you are trail braking or not.
  • Gear shifts shows you if you are consistent in your up- and downshifts, or if you need to work on gear selection.
  • Speed trace shows your speed at various parts along the track.
  • RPM trace lets you see how your revs are maintained during the lap.
  • Elevation trace can tell you if you are losing speed in uphill sections by being in the wrong gear, for example.
  • Tyre temperature traces shows you the tyre temperatures, so you can find sections of the track where you may need to nurse the tyres a bit to keep them in the window.

Do note that you can merge, or rather average out the temperatures across all four tyres in the Traces settings tab. This gives you a more general idea of where the tyres take a beating rather than individual tyres (which aren't labelled on the graph).

You can tap the trace graph screen to change the resolution of the display. You can select between 0.25x, 0.5x, 1x, 1.5x, 2x, 2.5x, 3x, 4x or 6x "magnification". Higher magnification shows less time/resolution, but can show you more detailed data from your inputs, if you so require.

Please note: screens may differ slightly from the current version.

Giving you a lot of options

This section describes the various settings available in EzioDash

Within the settings screen you will find several separate settings each on their own tab, which you select from the button row at the very top of the screen. The settings are divided into:

At the bottom of the settings page is a simple link to this page. Please note that depending on your settings, the app may disconnect when clicking any link in the app, since the app goes inactive.

  • App settings – these are the main settings for how the app will behave with regards to connecting, staying awake, working in the background and so on.
  • General settings – here you can find some more generic settings that will apply to the app in general. Whether to use average or median lap times, for example.
  • Dashes settings – here you can turn the various dashboard screens on and off as you like. You may also find specific settings for dashboards here.
  • Traces settings – on this tab you can activate and select what kind of trace data you are interested in.
  • Pit Crew settings – if you are looking for audio assistance while you race, this is where you will find it.
  • Tyres settings – on this tab you can set your own tyre window temperature range, enabling you to get the most out of your tyres.

Demo mode

The app has a demo mode that simply replays a recorded session. To enable the demo mode you need to go into the settings screen to enable the option “Display demo mode”. Then from the connection screen you must disconnect (if connected) before you can tap the “START DEMO” text. To view the demo, proceed to the dashboard screen by swiping or tapping the large circled right arrow. You can also go back to the connection screen and tap "STOP DEMO" at any time.

App settings:

  • Auto-discover Gran Turismo 7: (defaults to on) This toggle allows you to turn off the auto-discover feature if you for some reason need to manually enter the IP address of a specific console/game.
  • Keep app awake: (defaults to on) This toggle lets you decide if the app always stays on, keeping the screen from dimming and the iOS device from sleeping. Please note that this app draws quite a lot of power, and will drain your battery at a pretty rapid pace. Consider keeping the iOS device on wired power (or equivalent) to prevent excessively rapid discharge and heat.
  • Stay connected in background: (defaults to off) This setting allows you to have the app maintain the connection to GT7 even if you send the app to the background. This will however prevent the audio from playing, if you're using the Pit Crew feature for example.
  • Enable demo mode: (defaults to off) This toggle lets you activate a demo mode from the connection screen. The demo mode is simply a pre-recorded session that is replayed in the dashboard screen. To activate it, you will find a "START DEMO" button on the connect screen.
  • Packet granularity: (defaults to 3) This slider lets you choose the resolution of the telemetry by telling the app if it should decode every packet, or every 2nd, 3rd, 4th, 5th or 6th packet. This essentially means that you toggle between 60Hz, 30Hz, 20Hz, 15Hz, 12Hz and 10Hz updates. This is aimed at enabling older iOS devices to try to keep up with the telemetry without lagging behind as the race goes on.

Please note: screens may differ slightly from the current version.

General settings:

  • Metric speed/distance (kph/km): (defaults to on) This toggle lets you toggle between metric units (kilometers per hour, kph) and imperial units (miles per hour, mph).
  • Metric temperatures (°C): (defaults to on) This toggle lets you toggle between metric units (degrees Celsius, °C) and imperial units (degrees Fahrenheit, °F).
  • Endurance race duration: (defaults to 60m) This slider allows you to set a race duration before a race, to enable the app to make pit stop predictions for races with a duration rather than laps, give you predictions on how many laps the race is likely to be, and so on.
  • Display median lap time: (defaults to off) This toggle allows you to switch from an averaged lap time (based on flying laps) to a median lap time. I will not go into the difference in depth, you can read more about the difference on Wikipedia.
  • Display internal app state: (defaults to off) This toggle lets you display the app's internal state tracking, which shows what the app thinks is going on in-game. This displays as a text above the gear indicator.
  • Enable RPM bar flash: (defaults to off) This toggle lets you turn on a flashing bar when the car reaches its rev limiter (provided by the game).
  • Enable track identification: (experimental, defaults to off) This toggle lets you turn on a feature that tries to identify which track you are currently driving on. For some tracks/layouts the app needs you to pass certain points to identify it fully. Currently this feature is not used for anything tangible. The identified track is displayed overlaid on the RPM bar at the top when applicable.
  • Filter out slow laps from your average/median: (defaults to None) This slider lets you choose if you want slow laps (up to 110% of your fastest lap) to be ignored for the display of average/median lap time.

Please note: screens may differ slightly from the current version.

Dashes settings:

  • Standard dashboard: (defaults to on) This toggle enables the standard dashboard.
  • Simple dashboard: (defaults to on) This toggle enables the simple dashboard.
  • Hybrid dashboard: (defaults to on) This toggle enables the hybrid dashboard.
  • Trace dashboard: (defaults to off) This toggle enables the trace graph screen (same as the toggle in the Traces settings).
  • Select throttle/brake trace layout: (defaults to Overlay) This enables you to choose whether:
    • Overlay: the brake and throttle are overlaid over one another (more or less).
    • Brk/Thr: the brake trace is displayed above the throttle trace.
    • Thr/Brk: the throttle trace is displayed above the brake trace.

Please note: screens may differ slightly from the current version.

Traces settings:

  • Enable trace graphs: (defaults to off) This toggle enables the trace graph screen (either swipe all the way beyond the simple dashboard, or tap the icon in the lower right corner), where you can see your throttle and brake input, and more.
  • Show throttle trace: (defaults to on) This enables the throttle input trace.
  • Show brake trace: (defaults to on) This enables the brake input trace.
  • Show gear shifts: (defaults to on) This enables the display of gear shifts.
  • Show speed trace: (defaults to on) This enables the speed input trace.
  • Show RPM trace: (defaults to off) This enables the rpm trace.
  • Show elevation trace: (defaults to off) This enables the display of the track elevation trace.
  • Show tyre temperature traces: (defaults to off) This enables the display of tyre temperatures (separated).
  • Average all tyre temperatures: (defaults to off) This tells the app to average all tyres into a single trace rather than four separate traces.

Please note: screens may differ slightly from the current version.

Pit Crew settings:

  • Enable pit crew: (defaults to off) This toggle turns the pit crew audio commentary on or off. This feature will have the app speak information to you at pertinent occasions. Normally this takes place around 5 seconds after you have passed the finish line, since there is no data gathered right from the start of a race. On longer races, you may also get one or two occasions at other points along the track, if there is useful information to be shared.
  • Select pit crew voice: (defaults to default voice) This control allows you to select which voice you want to use for your "race engineer". Since all the spoken lines are in English, only English-speaking voices will be listed here. There may be a number of voices available on your iOS already, and there are a few enhanced or premium versions as well. To hear what it sounds like, you can tap the little round play button on the right of this control. To find out more about how you install other voices, visit Apple's website here: support.apple.com/en-us/111798
  • Enable radio bleep sounds: (defaults to off) This toggle adds a radio "bleep in" and "bleep out" before and after the spoken lines, for added realism. Some like to have this enabled to focus their hearing before the race engineer speaks.
  • Pit crew information: (defaults to on) This is a set of six toggles that allow you to control what aspects of the race engineer's spoken lines you wish to hear.
    • POS: This tells you your position in the race, if and when it is applicable.
    • LAPS: This tells you what lap number you are on in the race or practice.
    • TIME: This tells you about your last lap time. The spoken format varies depending on the circumstances.
    • TYRES: This tells you some information on whether your tyres are in a good temperature window or not.
    • PIT: This tells you information about your current fuel situation and if/when you need to pit. No info if fuel is not consumed.
  • Crew communication detail: (defaults to 6) This slider allows you to basically tune the amount of information the pit crew gives you. The lower the number, the less info you get. The app will try to give you the most important info as applicable, but really low settings may tune out important info – you will have to find the setting that suits you best. And yes, it goes to 11.

Please note: screens may differ slightly from the current version.

Tyres settings:

  • Base: (defaults to 75°C) This slider sets the "centerpoint" of your preferred tyre temperature window. This can be considered the "ideal" temperature, but varies depending on your driving style as well as which kind of tyre you have mounted on your car.
  • Spread: (defaults to 10°C) This slider sets the "window spread" for what the app considers reasonable. With a base of 75°C and a 10°C spread, the window is 70-80°C. Below this window, temperature-wise, is another spread where the app considers the tyres low temperature, or cold. Same goes for the other end of the temperature, with high to hot temperatures.
  • Dashboard temperature display: (defaults to Both) This selection picker allows you to swap between showing both average and current temperatures in each respective tyre readout (in a smaller font size), or either of average or current tyre temperatures instead (in a bigger font size). Note: This can be changed on the fly by tapping on any tyre readout.

Note: The base and spread temperatures set here reflects on all aspects of tyre temperatures throughout the app. That means both for the tyre readouts and for the pit crew information you get.

Another note: With regard to terminology, the app will try to convey an understandable meaning, but it may of course always be open to interpretation. With this in mind, "Warm" would in the app's terminology be the same as "in the window" (see the base and spread settings above), but "Hot" and "Overheating" would be outside the window or well outside the window.

Please note: screens may differ slightly from the current version.

Known issues

Here is a list of known issues:

  • If you experience that the app "lags behind" and gear shifts and such shows with a noticeable delay from within the game, try to increase the granularity to 3 or more. In my experience, even my old iPad Air (2nd gen) on iOS 15.7 is able to keep up on granularity 4 or higher.
  • The app may lose connection or freeze for a short time. This is likely due to a bad connection, or an interruption on the network. This may cause the ports used for the telemetry to block for a time (which is an operating system issue, more or less). EzioDash Pro will keep trying to reconnect, but you may have to manually disconnect and reconnect, or even force quit the app and wait a few minutes before it will reconnect again.
  • It is possible that the app fails to detect pit stops. There is no built-in data about this in the telemetry, so the app uses homegrown logic to determine if/when a car enters the pit. If this fails, it mostly affects the calculation of the average lap time, and by extension the time remaining for the fuel. There are two ways for the app to detect a pit entry; either by careful examination of the telemetry data, or “brute-force” looking at the pit lane entry coordinates. Both of these approaches CAN fail, especially for new tracks. So if you encounter a track where the app fails to detect a pit stop (and you can reproduce it reliably), or get stuck in either of PITENTRY, PITLANE or PITSTOP states, feel free to notify me about it.
  • There is a small chance that the app may crash when quitting the game while the app is still running.
  • Dirt tracks doesn't seem to have neither fuel consumption nor tyre wear, and going into the pit lane just sees the car trundle through. This means that there is no way to detect if/when a car enters the pit lane on dirt tracks.
  • Some cars in the game can exhibit strange behavior (telemetry-wise) which will prevent the app from working properly, either in some isolated aspect or completely. One example is the Chaparral VGT car, which always have the clutch engaged. I may look into this in the future, and since the actual car id is included in the telemetry, it may be possible to somehow get around this.

Bug reports

You are very welcome to contact me if you find anything that isn’t working as intended. I do however request that you try to recreate the problem before you contact me. A bug that can be reproduced is a lot easier to find. Also, please include the build version of the app (top right on the about screen), where in the game you were (lobby, arcade, time trial), what car you were driving at the time, and on what track. The more information you can provide, the easier it will be to find and hopefully fix.

If you can include a replay or video of when and/or how the bug occurred, it can be very helpful.

There is a changelog available for the app here.

You will find contact info on the bottom of this page.

Why a paid app?

Due to the reason mentioned in the disclaimer, I decided to at first release a free version as EzioDash. Since this relies on the goodwill of a third party (i.e Gran Turismo 7), I felt it would be unreasonable to charge even a small sum for the basic app. And EzioDash still remains a free, separate app.

However, as time passed and so many people were asking for this and that, I knew that the time spent on the app would be measured in weeks and months rather than hours and days. Then a completely unforeseen variable entered the equation, and that was PSVR2. Having tried GT Sport with the original PSVR, I knew that I had to try to get my hands on a PSVR2 headset. And that was it, I was hooked. It did have this one caveat though, I could no longer see the dashboard of EzioDash when I was racing in GT7... I'd had requests for audio before, and I had even started experimenting with it a bit. But it wasn't until I got my eyes (ears?) opened by earbuds that could connect to sound output from both the console as well as to iOS simultaneously that I knew I had to take the next step. Instead of trying to figure out a way to mix audio through cables (which is a nightmare if you are in VR), it was just wireless. And just worked.

So, many hours, days, weeks and months later, I had something working that I believed could be helpful not only for me, but for others, and especially those with their head in a VR headset. No, of course you can't see the actual dashboard in VR, but having the pit crew commenting on your lap times, how much fuel you have left, and so on... That brought a whole new level to playing in VR. At least for me.

I don't usually pay for apps myself. Maybe it's because I never really find apps that lives up to my expectations. Maybe it's because so many wants me to pay a subscription, or buy parts of the app piecemeal. I don't know. But I do know that I would have paid for an app such as this. And for that reason, coupled with the hard work put into it, this app will be a paid app. Mind you, it will not be an expensive app.

With that said, you are always welcome to further support and donate to the development of the free version, as well as a possible iPad version if this endeavour brings in any money. You can donate by buying a coffee or a chew bone for Ezio by visiting my Ko-fi page here: https://ko-fi.com/bornhall

Thank you, for taking the time to read this.

Credits

This app would not have been possible without the work of Nenkai and the combined efforts of people on GTPlanet like poumpoum, tarnheld, Stoobert, gu64, MGR, Hyurt, snimat, ddm, vthinsel, Lukejuryous, DJShadesUK, Evis and anyone else I might have forgotten.

Also a very big thanks to my beta testers.

You can find more information about how this all came to be here:
https://www.gtplanet.net/forum/threads/gt7-is-compatible-with-motion-rig.410728

This is in parts based on information gathered by Nenkai (and others). Learn more from his Github:
https://github.com/Nenkai/PDTools

Contact

If you have any questions about EzioDash, you can contact me by e-mail: bornhall@gmail.com

You will also find me on the forums on GTPlanet with the nickname "Bornhall".

Note: I can’t possibly answer all e-mails or messages, but I will read them. Please include “EzioDash” somewhere in the subject line for better visibility though.

Privacy policy

You can read the privacy policy here. However, the app does not collect any personal data at all (apart from the telemetry), so it's basically a formality.

Promote EzioDash Pro in the game

If you want to promote the app in-game, you can download either (or both) of the logos below – they are in SVG format and should work in the game. Right click and save the image locally, and upload it to the game using the decal uploader at gran-turismo.com.