407 Radio Beeping

This section is for General Enquiries or for Systems not Covered Above

Moderator: GiveMeABreak

User avatar
GiveMeABreak
Forum Admin Team
Posts: 26603
Joined: 15 Sep 2015, 19:38
x 3109

Re: 407 Radio Beeping

Post by GiveMeABreak »

Beeping almost certainly means the Head Unit needs VIN coding to the vehicle if it has been replaced. It may also mean some other configuration to match any vehicle options if it has been sourced from another vehicle.

At the end of the list is a link to a Google Map, showing the members' geographic locations and details. Just use the Private Message or Email links on the member's profile to contact anyone suitable.

List of Lexia / Diagbox Owners with Kits Offering Help

Bear in mind, although we update the list as often as we can, not all members are active on the Forum all the time, so it may take a while for a reply.
User avatar
Paul-R
(Donor 2020)
Posts: 5489
Joined: 07 May 2009, 16:24
x 818

Re: 407 Radio Beeping

Post by Paul-R »

I once met a different Lewis Collins at a wedding reception in Wallasey some 30 years ago. I know it was a different Lewis Collins because it was the Lewis Collins from The Professionals and he sadly died some 8 years go.

Anyway, I digress.

Hopefully this is just a problem with a headend unit (HU - radio to you and me) from another car that needs the correct VIN inputting. I'm available most times although obviously I'm in and out as required. PM me.
User avatar
Paul-R
(Donor 2020)
Posts: 5489
Joined: 07 May 2009, 16:24
x 818

Re: 407 Radio Beeping

Post by Paul-R »

Managed to cure the beeping on Lewis's car but, boy, what a grueler it was. My first problem was that I couldn't find the cloverleaf power lead that the Diagbox laptop power supply needed. So that wrote off yesterday! Lewis found a spare no-longer-needed lead and came back today.

We got the VIN from the stamping visible through the windscreen no problem and fired up the laptop, started Diagbox and, after I'd inputted the VIN, offered the choice of Lexia or Scantool. Obviously too old for Diagbox itself then!

Then Lexia asked for the RP number. This was next problem - no label on the car. After faffing around we decided to leave the box blank and just click the Next button and see what happens. Surprisingly the program accepted this then offered the usual options of Diagnose, etc. I ran the Global scan and this threw up a few errors. I then made the mistake of clicking on the error log. Why an error? Because it locked the machine up - obviously too many errors.

I wasn't able to step back in the process and ended up having to terminate the program and then restarting. This time I couldn't get past the Input RP number stage. It kept either giving me an error message or dropping back to Diagbox with the same demand for the RP number and a complete refusal to get past this stage without it. I made numerous attempts with slight variations, exiting and restarting Diagbox and even restarting the laptop. Lew suggested just making up an RP number so I put a random number in - I think 3406. This was obviously too low as when I did a Global scan Lexia couldn't communicate with any of the ECUs. Lew looked on the internet and one place suggested using 12345 in such a case and this then worked. A Global scan produced the same result as our first scan and this time I didn't make the mistake of looking at the log.

Problem solved? Not a bit of it. No matter how many times I tried inputting the VIN the beeping didn't stop. We went through all the variations of stopping, restarting and rebooting we could think of and still no success. Then I did the thing I should have done much earlier and checked what VIN was stored in the BSI. And, of course, it was different. The BSI must have been changed for one off a scrapper at some time. Finally I was able to cure the beeping by putting this VIN into the radio ECU.

Phew! I was very close to giving up at several points. Possibly if I had done recoding a radio before I might have realised earlier what the problem was but we got there in the end.
User avatar
GiveMeABreak
Forum Admin Team
Posts: 26603
Joined: 15 Sep 2015, 19:38
x 3109

Re: 407 Radio Beeping

Post by GiveMeABreak »

Well done for persevering with it. If I'd had the VIN I could of provided the RPO for you quite quickly, as this is needed to determine the correct build date to ensure the correct operation, but for the task at hand it was sufficient with the guess!
User avatar
Paul-R
(Donor 2020)
Posts: 5489
Joined: 07 May 2009, 16:24
x 818

Re: 407 Radio Beeping

Post by Paul-R »

I did consider making a post asking for the VIN but didn't think I would get an answer quickly enough. I was wary of putting a spurious RPO in but reasoned that the item I was looking at wouldn't be affected greatly. I was partially right and as soon as I had put this 3406 in I thought to myself that it was way too early a number.

Out of interest what dates do 3406 and 12345 equate to?
User avatar
GiveMeABreak
Forum Admin Team
Posts: 26603
Joined: 15 Sep 2015, 19:38
x 3109

Re: 407 Radio Beeping

Post by GiveMeABreak »

07/03/1986 and 27/08/2010 respectively.
Dormouse
Donor 2021
Posts: 1220
Joined: 15 Apr 2021, 14:32
x 265

Re: 407 Radio Beeping

Post by Dormouse »

Learning more all the time.
User avatar
Paul-R
(Donor 2020)
Posts: 5489
Joined: 07 May 2009, 16:24
x 818

Re: 407 Radio Beeping

Post by Paul-R »

GiveMeABreak wrote:
08 Oct 2021, 13:34
07/03/1986 and 27/08/2010 respectively.
Haha. Well the first was definitely too early. No wonder the program couldn't find any ECUs - they weren't invented back then.

The second was only a couple of years out, soooo - close enough!