New AL Priority 2 Sensor, Wont Update Firmware?

[RedRocket]

RedRocket, i understand, and i've done that. ive tried 14 USB drives in the past 3 days, different mfgs, models, sizes, USB specs, and so forth.- There you go, wrongly assuming what/how I was going to suggest you & I try to walk thru your issues.

in the end, the unit was swapped out and the one i have installed now works fine.- (HALLELUJAH !) i see that you and everyone else is saying i needed to try different usb drives,- (nooo, another incorrect assumption on your part) and see what steps, and i figured you all would assume i'm an idiot,- (that's a rather broad indictment...speaking for myself,I DIDN'T) which is why i posted a video. unfortunately, no one was really helpful despite me stating facts and what my process for fault isolation was. documentation is sparse for these units unfortunately. BRD represents these products for the USA and is therefore responsible for their support, which he told me in the end he was willing to take care of the issue via a phone call.

It appears your problems began w/ the Installer, then compounded by neither of you Registering the Control Box as required, which beget the missteps afterwards.
I'll go out on a limb w/ an assumption...I'll bet you never read any of the Stickies for "install,how-to,problem resolution" Threads which contain a wealth of info to avoid self-inflicted problems.

[spitcool]

actually, the control box WAS registered. and the mis steps afterwards were lack of information for troubleshooting, for which i was giving very clear information and symptoms as well as a video.

and i did read all the stickies, and the manuals.
There you go, wrongly assuming...

[RedRocket]

actually, the control box WAS registered- (at what point in time ?). and the mis steps afterwards were lack of information for troubleshooting, for which i was giving very clear information and symptoms as well as a video.

and i did read all the stickies, and the manuals.
There you go, wrongly assuming...- hahaha, egg on my face, but I can take it out on the limb I climbed.

Then obviously the Installer was the root cause & you having read all Stickies being now fully familiar w/ process, should have been able to easily correct their error in giving a non-working unit in the first place.

[BestRadarDetectors]

actually, the control box WAS registered. and the mis steps afterwards were lack of information for troubleshooting, for which i was giving very clear information and symptoms as well as a video.

and i did read all the stickies, and the manuals.
There you go, wrongly assuming...

Then obviously the Installer was the root cause & you having read all Stickies being now fully familiar w/ process, should have been able to easily correct their error in giving a non-working unit in the first place.

No need to continue the back and forth arguing. The customer has a working unit and the dealer did what he needed to do to take care of the issue which is how it should have been handled anyway. I have not spoken with the dealer and they did not ask for an RMA but if the unit comes back we can test it and see what the issue was.

[RedRocket]

The customer has a working unit and the dealer did what he needed to do to take care of the issue which is how it should have been handled anyway.

Ditto the Hallelujah & Amen.

[Salty]

OP, glad your unit is working properly. Have a safe and ticket free trip, and please let us know if you run into any encounters!

Closing thread.

[BestRadarDetectors]

Needed to post a followup on this thread for anyone that reads it in the future and wants to know what happened. The CPU that was installed was not defective in any way. The shop that installed the system had a few different CPU's on hand and installed one but gave the customer the serial number of a different unit he had ordered on the same order. Since the serial numbers were not valid the customer could not update the firmware. The original returned CPU was installed in another vehicle with the correct serial number and is working just fine. As a rule of thumb if you have a new install always verify the serial number on the bottom of the unit if you are having any issues updating.

[radargeek]

Maybe there needs to be a distinct error code/beep/voice alert (on HiFi) when there is a serial number mismatch between the CPU and the firmware on the USB. It would make this sort of mistake a lot easier/quicker to troubleshoot anyway.

[RedRocket]

Needed to post a followup on this thread for anyone that reads it in the future and wants to know what happened. The CPU that was installed was not defective in any way. The shop that installed the system had a few different CPU's on hand and installed one but gave the customer the serial number of a different unit he had ordered on the same order. Since the serial numbers were not valid the customer could not update the firmware. The original returned CPU was installed in another vehicle with the correct serial number and is working just fine. As a rule of thumb if you have a new install always verify the serial number on the bottom of the unit if you are having any issues updating.

Tks for the follow-up, I was still wondering about this & remained firm in believing it was ser. # related,somehow.