CodeShooter Data Logs: What to Set Up and How to Send One

A data log records what your engine is actually doing while the problem happens. It is the fastest way for our tech team to find a fault that doesn't show up as a trouble code, and it regularly finds causes that swapping parts misses.

Before you start

1. Create a support ticket with your CodeShooter's serial number to have data logging turned on for your device.
2. Use the original EVP CodeShooter app.
3. If the app offers a firmware update, connect the CodeShooter to an external power source, such as a phone charger, and let it update before you go to the vehicle.

Record the log

1. Connect the CodeShooter to the vehicle's diagnostic port, start the vehicle, and connect the app.
2. Get within Wi-Fi range before you start the log.
3. Start the log, then drive the vehicle and reproduce the symptom you're chasing.
4. Return to Wi-Fi range and save the log. It uploads to our servers automatically.
5. Create a support ticket to have the log reviewed. Describe the symptom and when it happens.

For the app's screens step by step, see CodeShooter Data Logging.

What a log can find

Logs routinely settle questions that guesswork can't. In one case a vehicle running rough had already had its map sensors replaced, with no change. The log showed high load with every other reading in spec, which pointed at fuelling, and the customer found a partially plugged injector.

That's the value of a log: it tells you which parts not to buy.

If you need help

If the log won't save or upload, or data logging isn't available in your app, create a support ticket with your CodeShooter's serial number and what the app shows.