Unable to Datalog
Moderator: sohfast94
Unable to Datalog
I'm trying to data log to work with Johan on my email tune. Using the i2010 in my 2015 Challenger I open the data log menu, click record. It goes to a screen with blank tables but no info. If I hit the back button it asks if I want to save the file and I choose yes. After connecting the i2010 to my computer there is no data listed in the logs folder.
I'm also having trouble selecting PIDs. I've gone through the list and selected items but the selection doesn't change. There is no indication if the value is selected or not. Am I missing something? Is there a list of the PID matrix and their sub items?
I'm also having trouble selecting PIDs. I've gone through the list and selected items but the selection doesn't change. There is no indication if the value is selected or not. Am I missing something? Is there a list of the PID matrix and their sub items?
You do not have the required permissions to view the files attached to this post.
Re: Unable to Datalog
https://forum.diablosport.com/viewtopic ... 60&t=53549
I have the same problem. Waiting for the fix for weeks.......
I have the same problem. Waiting for the fix for weeks.......
Re: Unable to Datalog
Thanks for the info. I hope to hear from Diablo soon since I've already paid for a custom tune.Cherche wrote:https://forum.diablosport.com/viewtopic ... 60&t=53549
I have the same problem. Waiting for the fix for weeks.......
- mikel
- Posts: 58698
- Joined: Tue Jan 16, 2007 1:17 pm
- Location: DiabloSport World Headquarters
- Contact:
Re: Unable to Datalog
we're working to address this bug.
Mike Litsch
DiabloSport Brand Manager
Diablo Tech support by phone:
561-908-0040
M-F 8:00 AM to 5:00 PM EST
[email protected]
DiabloSport Brand Manager
Diablo Tech support by phone:
561-908-0040
M-F 8:00 AM to 5:00 PM EST
[email protected]
Re: Unable to Datalog
Any updates on this issue? I'm in the same boat.mikel wrote:we're working to address this bug.
Re: Unable to Datalog
I'd also appreciate any updates or ETA. It would have been beneficial to know before I ordered the PCM and tuner that this was a known issue. I probably still would have bought the setup, but wouldn't have paid for a custom tune.aw148751 wrote:Any updates on this issue? I'm in the same boat.mikel wrote:we're working to address this bug.
Does this affect the Trinity as well? What is the root cause?
- mikel
- Posts: 58698
- Joined: Tue Jan 16, 2007 1:17 pm
- Location: DiabloSport World Headquarters
- Contact:
Re: Unable to Datalog
update the tool then choose restore default pids in the logging menu and try again please.
Mike Litsch
DiabloSport Brand Manager
Diablo Tech support by phone:
561-908-0040
M-F 8:00 AM to 5:00 PM EST
[email protected]
DiabloSport Brand Manager
Diablo Tech support by phone:
561-908-0040
M-F 8:00 AM to 5:00 PM EST
[email protected]
Re: Unable to Datalog
I attached the tool and ran the updater. It reported that there were no updates at this time. I connected it to the car and reset the PIDs and it DID record.mikel wrote:update the tool then choose restore default pids in the logging menu and try again please.
I'm still having trouble selecting PIDs. I've gone through the list and selected items but the selection doesn't change. There is no indication if the value is selected or not. Am I missing something? Is there a list of the PID matrix and their sub items?
Re: Unable to Datalog
I'm still having trouble selecting PIDs. I've gone through the list and selected items but the selection doesn't change. There is no indication if the value is selected or not. Am I missing something? Is there a list of the PID matrix and their sub items?Heckcat wrote:I'm still having trouble selecting PIDs. I've gone through the list and selected items but the selection doesn't change. There is no indication if the value is selected or not. Am I missing something? Is there a list of the PID matrix and their sub items?
Re: Unable to Datalog
You cannot select PIDs. You can only log the default PIDs. That is an issue many people have here......
Re: Unable to Datalog
After what update will it make sense to check this issue again?