2012 Dodge Challenger 3.6 Intune Problem?

[SuaveRT]

Plug in different USB port. Wait a while, it will create two drives. One that has the tunes folder and others and shortly after that another drive will create which will have the intune.exe file. It should error and then still load. You just have to wait for second drive to show up in my computer.

[zeropilot]

Mike said it went up @ 1pm on Fri and I tried it at 4pm, no dice.

[ltwhite]

There are a lot of inaccurate posts on various forums (often from people who don't seem to actually have a DCX unit and a 11-12 3.6L vehicle) saying that the problem has been solved but as of this evening it still hasn't.

[Oconer]

There are a lot of inaccurate posts on various forums (often from people who don't seem to actually have a DCX unit and a 11-12 3.6L vehicle) saying that the problem has been solved but as of this evening it still hasn't.

I seen that out of the 30+ people that I've seen have still have problems and funny how the one or two people have theirs working

[Warmanr]

Sorry to gloat but it is worth it huge difference in performance

[Oconer]

Sorry to gloat but it is worth it huge difference in performance

Is your intune working?

[Warmanr]

Sorry to gloat but it is worth it huge difference in performance

Is your intune working?

Yes I am one of the lucky ones been working since friday

[Oconer]

Sorry to gloat but it is worth it huge difference in performance

Is your intune working?

Yes I am one of the lucky ones been working since friday

Could you post pics of your intune software so we can see what the differences are in our intune

[ltwhite]

Here is an info.xml file from a working tune on a 2012 vehicle with 8-speed tranny:

<?xml version="1.0"?>
-<tool_info> <main svn="6219" sw_rev="1r03i" full_version="InTune-1r03i 05/06/2013 01:43:25 PM"/> <registration status="1" sn="CIKA863-1"/> <cal_id CM1="68046526AH" PCM="68084713AH"/> <restore bc="1" vin="2C3CDXHG1CH125931" id="0"/> <system_db vin="1r01c" dtc="1r01a" info="1r01b"/> <db pid="1r01a" tune="1r01e" mfr="DCX"/> <db pid="1r01a" mfr="FORD"/> <db pid="1r01a" mfr="GM"/> <license tuned="1" avail="1"/> <updates count="2"/> <oem tool_oem="DIABLODCX"/> </tool_info>
Thanks very much. This is interesting. I have the same serv num, same software rev, same full version dated 5/6/2013 1:43pm. Three items are different, I have: sn="J23QCFA-4"/> <cal_id CM1="68065111AGkc3a0" PCM="68060761AG"/>

My error message is saying that my pcm calibration of 68060761AG is unsupported. I wonder if the AG at the end of my calibration means 2011 year or 5-speed and the AH at the end of the working tune calibration means 2012 or 8-speed.

I am developing a working theory that the tune works on 2012 8-speeds but not 2011s and/or not 5-speeds.

Warmanr: can you tell us your vehicle year and tranny type?

[Oconer]

Not a bad start to state what you have

2012 challenger sxt 5 speed automatic 3.6

Having the same problem no matter what I drag and drop,
PCM error this, vehicle not supported that.. Everything I do it a problem

[ltwhite]

it is saying PCM calibration for 23CDYAG7CH206593 might need an update. check for a calibration update? and i click the green check and does absolutely nothing

please post a copy of the info.xmlfile from the intune drive.

Most of you have already tried tuning your car before the release, which is why everyones tools are asking for an update.
After a moment of confusion with Wramanr's issue, I realized his calid was now supported, despite the leftover update request, which is why all he had to do was go to the car and load the tune. Anyone that is getgting the calibration failure on the PC side, please try just loading the tune to your car. If it still asks you for an update, and it is not downloading fromthe web, please post up a copy of your info.xml file from the intune drive.

Thanks

Here another for

info.xml

Griffin 26, I see you have a 2012 vehicle. Can I ask, is it 5-speed or 8-speed?

[Oconer]

I really do hope they come through tomorrow.

[Oconer]

The farthest I get is the vehicle not supported

[ltwhite]

Same here. The post by Suave in this thread about plugging on to a different USB port gets you nowhere. The post theorizing that people tried to tune before tune was released and got calibration error on the PC side just need to go to vehicle and tune is wrong as well. My very first attempt was 5/13, well after the 5/6 tune release and the rumored Friday update.

I know transmission type should not matter on our vehicles (which have a separate TCM), but as best I can tell this calibration error seems to be more prevalent with 5-speeds. I base this on the fact that the only one or two guys who got the tune to work both had 8-speeds.

What is odd about that is the first 3.6L application was Jeep (which obviously was not an 8-speed) so if anything you would think they should have had the 5-speed Charger/Challenger sorted first.

[Warmanr]

Same here. The post by Suave in this thread about plugging on to a different USB port gets you nowhere. The post theorizing that people tried to tune before tune was released and got calibration error on the PC side just need to go to vehicle and tune is wrong as well. My very first attempt was 5/13, well after the 5/6 tune release and the rumored Friday update.

I know transmission type should not matter on our vehicles (which have a separate TCM), but as best I can tell this calibration error seems to be more prevalent with 5-speeds. I base this on the fact that the only one or two guys who got the tune to work both had 8-speeds.

What is odd about that is the first 3.6L application was Jeep (which obviously was not an 8-speed) so if anything you would think they should have had the 5-speed Charger/Challenger sorted first.

Mine is 5 speed 12 challenger and I have mine working