New Software - US 2.6 Version

[menardrs1]

I, too, experience the same results on intial install. So, if I understand all this thread correctly.

1) Run the fix (in or out of the vehicle) and update heads.
2) Run the 2.6 firmware upgrade and update the heads.

In that order, correct?

[Warz00]

That's what I did and it worked perfectly.

[menardrs1]

Has anyone had any trouble applying this update? I can't get the heads to reprogram after the update. Here is what I did step by step

1. Unplug everything from the CPU unit and connect it to the usb port on my laptop
2. Click on 2.6 USA and click the update CPU button and let it finish.
3. Unplug from laptop and reconnect all the heads, alert, and power.
4. Made sure the switch was in II position and turn the car on.

This is where I'm stuck, the heads don't start updating. After I turn on the car, it seems like it's working normally but the heads did not update. Is this normal and the heads are not suppose to update?

I have also tried flashing to the 2.2 USA Repair first and then flashing to the 2.6 and still doesn't work.

You have to use the Fix flash first. What that does is wipe the heads clean and unlock them for programming. Then download the update and reprogram heads.

----------------------
Eureka!
I tried the sequence as described on my new installation and all is perfect. Now I just need to find a L-Gun to test the system that is not being held by a COP.

1) Power off, Switch to Center position, plug in USB
2) Ran the 2.2 USA Repair on a Brand New installation (in-car)
2) Unplugged the USB
3) Turn on power and flip switch to position II (Jamming)
4) Four long beeping sequences with Green light flashing with a single beep between each head update.
5) Two beeps with Red Light flash to complete the update.
6) Repeat steps 1 - 5 with the 2.6 USA Firmware Update.

Thank you so much for the help!!!!!

[kpatz]

Just a thought, but instead of having to flash the heads with "repair" firmware to allow them to be updated, how about (for a future update) add code where the CPU and heads compare versions, and if the CPU reports it has a newer version than then heads, have it reflash the heads automatically?

It would simplify the update process, cut down on support calls, and avoid people running mismatched firmware on the heads and CPU leading to performance issues.

Just my 0.02...

[menardrs1]

Just a thought, but instead of having to flash the heads with "repair" firmware to allow them to be updated, how about (for a future update) add code where the CPU and heads compare versions, and if the CPU reports it has a newer version than then heads, have it reflash the heads automatically?

It would simplify the update process, cut down on support calls, and avoid people running mismatched firmware on the heads and CPU leading to performance issues.

Just my 0.02...

-----------------------
I would have thought that was the process, and the only reason some of us have had issues in the first place was our new installation had to have basic information before the update could be established. Oh well. Now that I know how the process works...I'm good.

[Tom]

Where is the Mac version of the updater?

I must say, though, the updates went without a hitch using Parallels.

[aa2033]

1) plug in cpu
2) restore to 2.2
3) disconnect
4) reconnect everything
5) turn on car, turn from off to II
6) green light goes nuts and beeps like 10 times, then turns red solid, 1 long beep, then constant green. or something like that.
7) turn to Off
8) disconnect and repeat?

i feel like i shouldn't of had the red

EDIT: So i restored back to 2.2 a second time to try to see if i messed up, but this time, did all of that again, and it just blinked red twice, then solid green like normal startup, so i guess they're already updated?

EDIT 2: Updated to 2.6, re connected, and it blinked green like 10 times fast, then solid, then beeped fast again, repeated, blinked red twice, then solid green.

T_T
done?

[BlinderGuy]

EDIT 2: Updated to 2.6, re connected, and it blinked green like 10 times fast, then solid, then beeped fast again, repeated, blinked red twice, then solid green.

T_T
done?

This means it is ready to rock.

[aa2033]

This means it is ready to rock.

awesome. thanks

actually, after an hour of looking for the freaking CPU, i plugged it in and saw i already had 2.6.. but since i had gone through all that trouble i thought i'd try the flash and update to see how it works..

the installer really hid it well.