Diablosport Forums

I recently updated my inTune i2 which hadn't been updated in about a year.

I had done some data logging on Friday, copied the data logs off, ran the updater from a Windows PC, everything installed and ignition was copied to the i2. Because I am actually a Mac user I switched over to my Mac, ran the ignition installer, everything seemed to go well, then it hung on "Please Wait" instead of rebooting. I moved it back to the windows machine, it reinstalled and updated, then it updated another time, now it says it is up to date on both machines. SWEET! or not...

I tried to do some data logging: I select Scan Tool, Data Logging, and then I get "Please Wait" infinitely (I let it sit for about an hour)
Then I tried to apply one of the tunes from my tuner and it does nothing after I select the tune. It literally does nothing, I can select any tune and it just goes right back to the selection screen.

I tried connecting to the pc again and it shows up to date. I deleted the old logging files off of it, same thing.

Help?

Here's a screenshot from the ignition app "more info", unfortunately I don't have the xml file right now

info file attached

Also, I noticed the files in "Runtime" are timestamped in the future (12 hours ahead of the time I connected it to my Mac - which does have the correct time from NTP)

jhb-mbp:~ oba$ ls -lt /Volumes/i2/runtime/
total 8912
drwxrwxrwx 1 oba staff 4096 Sep 19 2015 .
drwxrwxrwx@ 1 oba staff 16384 Aug 28 23:16 ..
-rwxrwxrwx 1 oba staff 113379 Aug 29 2017 runtime_01.dbg
-rwxrwxrwx 1 oba staff 114284 Aug 29 2017 runtime_00.dbg
-rwxrwxrwx 1 oba staff 109943 Aug 29 2017 runtime_04.dbg
-rwxrwxrwx 1 oba staff 113048 Aug 29 2017 runtime_03.dbg
-rwxrwxrwx 1 oba staff 113291 Aug 29 2017 runtime_02.dbg
-rwxrwxrwx 1 oba staff 108881 Aug 29 2017 runtime_07.dbg
-rwxrwxrwx 1 oba staff 109392 Aug 29 2017 runtime_06.dbg
-rwxrwxrwx 1 oba staff 109263 Aug 29 2017 runtime_05.dbg
-rwxrwxrwx 1 oba staff 672590 Aug 29 2017 runtime_08.dbg
-rwxrwxrwx 1 oba staff 506874 Aug 29 2017 runtime_09.dbg
-rwxrwxrwx 1 oba staff 12420 Aug 29 2017 runtime_13.dbg
-rwxrwxrwx 1 oba staff 12213 Aug 29 2017 runtime_12.dbg
-rwxrwxrwx 1 oba staff 12413 Aug 29 2017 runtime_11.dbg
-rwxrwxrwx 1 oba staff 12448 Aug 29 2017 runtime_10.dbg
-rwxrwxrwx 1 oba staff 558306 Aug 29 2017 runtime_15.dbg
-rwxrwxrwx 1 oba staff 504497 Aug 29 2017 runtime_16.dbg
-rwxrwxrwx 1 oba staff 503624 Aug 29 2017 runtime_17.dbg
-rwxrwxrwx 1 oba staff 77520 Aug 29 2017 runtime_23.dbg
-rwxrwxrwx 1 oba staff 18858 Aug 29 2017 runtime_22.dbg
-rwxrwxrwx 1 oba staff 19472 Aug 29 2017 runtime_21.dbg
-rwxrwxrwx 1 oba staff 19819 Aug 29 2017 runtime_20.dbg
-rwxrwxrwx 1 oba staff 508242 Aug 29 2017 runtime_18.dbg
-rwxrwxrwx 1 oba staff 8288 Aug 29 2017 runtime_29.dbg
-rwxrwxrwx 1 oba staff 8327 Aug 29 2017 runtime_28.dbg
-rwxrwxrwx 1 oba staff 164040 Aug 29 2017 runtime_24.dbg

what vehicle is this?

mikel wrote:what vehicle is this?

Hi Mike - this is a 2015 Jeep Wrangler with a DiabloSport PCM and an Edelbrock supercharger

I am not sure but I think its related to software update issue

I just purchased new device my dealer have updated for me I notice same issue after more digging I found after update data logger not working after try new device without update work to make sure we update device then data logging stop work

I open support case and waiting for a fix

My car dodge challenger 2012 v6