did you check the connections are all good?

there's some fuses aswell

 

Hi Jetronic77,

I've checked both the fuses that tie into the Bluetooth. Apart from the blue and me module connection is there some others I should check?

Fuse box diagram Alfa Romeo Giulietta

 

I'm sorry i thought I added the wiring schematics

 

Thanks I'll have a look

 

Most likely, but you can find them used if not in a hurry.

 

The problem with the Blue&Me modules is that they fail so often that most second hand units you'll get from wreckers are faulty as well. You are better off just removing the Blue&Me module & that will allow you to do a full Proxi-Alignment with no errors, thus resolving the flashing odometer.

Then go to your local Auto Sound specialist and get them to install a quality aftermarket bluetooth adapter. Am pretty sure I read on one of the forums that they can even fit ones that allow your steering wheel function buttons to work as well, allowing you to play music from, as well as answer your phone.

 

This has just answered a question I was going to ask soon.

Mine's either blown a fuse or dead after some battery connection issues and rather than replace it, I'd rather just remove it since I can count the times I've used the bluetooth in the last 5 years on one hand.

Knowing that I can just disconnect the module and 'map' it out makes me happy with replacing the headunit later.

 

Well one would of course have to fix the Airbag issue as well.

 

The problem with the airbag is when you go to that node and check it individually it does not show any faults. And on the CAN set up page it shows ok
(Airbag Node (NAB) EOL OK). It's only during the alignment that it shows an error and it is the node after the blue and me module.

 

Where are you located?

Are you using a Bluetooth or USB ELM adapter?

 

Hi bazzbazz,
We were using a cable. I'm in Melbourne.
Cheers

 

Disconnect the battery and give the connections to the body computer a good going over.

Also, disconnect the replacement Blue & Me unit and try doing the Proxi-Alignment again and see if it makes it all the way through. (stranger things have happened)

 

Hi All,
Just wanted to let you know that in the end I purchased a new unit from Alfa. They installed it and everything is working fine now. Unfortunately looks like a new unit is the only fix.
Cheers

 

Hi All,
Just wanted to let you know that in the end I purchased a new unit from Alfa. They installed it and everything is working fine now. Unfortunately looks like a new unit is the only fix.
Cheers

How much that end up setting you back?

 

Was expensive, about $900.

 

Did you ever found the solution to the Proxi fails on aibag node request out of range ?
Writing to module: Airbag Node (NAB/ORC) FAILED! - Request out of range error
[102A] errors: Byte 69: 7C->4C

?

 

Hello everybody. I have the same issue but because of a different reason. I can not finish proxi alignment because MES can not write to Airbag node. Thus I am getting multiple DTCs:
C1213-54 System configuration (missing calibration)
C0074-29 Torque requested on steering wheel from CAN (module DST) - (signal invalid)
C100A-62 DST module unavailable (signal compare failure)
C1214-55 End of line configuration incorrect (not configured)
It acts just like after a battery replacement. However, power steering calibration procedure (lock to lock) does not help. I think it is the case when MES proxi procedure had written to all nodes once and had somehow damaged configuration in these and now it is no longer possible to finish, failing on the airbag node. Airbag ECU fine btw. No trouble codes, NAB EOL OK... I am a little desperate right now

 

No practical experience of this procedure but check the log file for the first error ?
So the CAN status of every module except the Airbag is OK/EOL OK ?
Why were you doing it ? What changed ?

 

I am browsing the logs and the last correct proxi alignment was by this config:
CAN CONFIGURATION DATA:
6F 04 00 25 00 00 00 00 6F 04 00 25 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
6F 04 00 25 00 00 00 00 09 04 00 04 00 00 00 00 6F 04 00 25 00 00 00 00 09 04 00 04 00 00 00 00 09 04 00 04 00 00 00 00
30 34 31 39 31 30 30 31 32 36 35 4F 55 54 50 55 54 2D 4A 49 54 20 10 07 02 6F 04 00 25 00 00 00 00 09 04 00 04 00 00 00 00 87 C8 55 07 8F 10 3C 11 38 10 00 1F 07 07 01 95 06 2D 03 3C 00 00 01 00 3A 51 0A 7C 00 00 00 00 09 00 00 00 00 37 01 61 01 38 00 40
All nodes OK.
Byte69 == 7C;
First proxi with airbag node issue is from action, where I changed engine type from Type 6/0.9 MultiAir to Type 8/1.4 16V MultiAir, because I obviously have a 1.4... This is the first time Airbag node failure occured. These config params:
CAN CONFIGURATION DATA:
6F 04 00 25 00 00 00 00 6F 04 00 25 00 00 00 00 01 04 00 00 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
6F 04 00 25 00 00 00 00 09 04 00 04 00 00 00 00 6F 04 00 25 00 00 00 00 09 04 00 04 00 00 00 00 09 04 00 04 00 00 00 00
30 34 31 39 31 30 30 31 32 36 35 4F 55 54 50 55 54 2D 4A 49 54 20 10 07 02 6F 04 00 25 00 00 00 00 09 04 00 04 00 00 00 00 87 C8 55 07 8F 10 3C 11 38 10 00 1F 07 07 01 95 06 2D 03 3C 00 00 01 00 3A 51 0A 7C 00 00 00 00 09 00 00 00 00 37 01 61 01 38 00 40
Airbag node (NAB/ORC) Error, request out of range:
[102A] errors: Byte 69: 7C->5C

Even if I change back to start stop present or 0.9 Multiair engine type, Airbag node still fails to write 5C. over 7C. (I don´t want it to do so, but it tries)

I assume, there is a parameter in Can setup, proxi alignment in MES that changes this byte. Shame is, I cannot find which one it is. Is it possible to write the config data byte arrays manually or have at least coding data description?

Thanks for any advice

 

You made two changes only ?
I can also see another two changed bytes in the first line. Even though you have tried to put 2 parameters back to original values, it is like there is another config change still active i.e 5C which it is trying to copy to the airbag module. I'm assuming the airbag module doesn't support the config change behind that 5C value.

Why are you doing this ?

 

Try CTRL-ALT-c. It seems to allow you to change the current data and do a custom proxi alignment. Be careful ! Put the value back to 7C manually.

 

Yes, unfortunately I have made two changes only. Those first two lines starting with 6F 04 00... are no actual Proxy data. Those start at 30 34 31 when I hit CTRL+ALT+C for custom proxy. Silly is, that there is an 7C at byte 69 already. Even if I try default proxy values with 7C, the procedure always tries to put 5C and airbag node fails. I am starting to think, it is a MES bug.
Why to do this?
With all theDTCs described before I am out of VDC, ASR, Adaptive Xenon lights and DNA selector. There is this configuration fail of missing calibration that needs to be dismissed and lock to lock procedure with steering wheel does nothing

 

Sounds like MES memory is corrupted, disconnect and start again. Disconnect the battery. Connect again and see what values the proxi alignment procedure pulls from the BCM. You could try an older or newer version of MES. I saw one comment where the poster said he had to do it 3/4 times before it worked, that suggests timing or timeout issues between MES and different modules and also where the alignment failed but the status of all the modules were OK/EOL OK.

 

try buckle your seatbelts and do proxi then.

 

Hello everybody. I finally got rid of all the issues. I got an older version of MES (4.7R3 > 4.6R1). After reading multiple threads I composed following procedure.
1. Front seat belts buckled.
2. Scan DTCs (no adapter) >remove DTSc
3. Scan DTCs (yellow adapter) > remove DTCs (Probably not necessary. No errors present at the time)
4. Proxi alignment > default values (Start stop present, aux disabled etc.)
5. Proxi alignment procedure > All nodes, including airbag node alignment succesful, everything OK. Feels damn good.
6. Key off, key on > No errors, DNA switch is working again and the car is all good as new.

It feels pretty satisfying riding in Dynamic after almost two weeks of Natural pain. Giulietta should be like "Always in D"

Thanks for everyone´s advice!

 

Hello everybody. I finally got rid of all the issues. I got an older version of MES (4.7R3 > 4.6R1). After reading multiple threads I composed following procedure.
1. Front seat belts buckled.
2. Scan DTCs (no adapter) >remove DTSc
3. Scan DTCs (yellow adapter) > remove DTCs (Probably not necessary. No errors present at the time)
4. Proxi alignment > default values (Start stop present, aux disabled etc.)
5. Proxi alignment procedure > All nodes, including airbag node alignment succesful, everything OK. Feels damn good.
6. Key off, key on > No errors, DNA switch is working again and the car is all good as new.

It feels pretty satisfying riding in Dynamic after almost two weeks of Natural pain. Giulietta should be like "Always in D"

Thanks for everyone´s advice!

I just bought the licence key for v5.0, and I'm told the key cannot be used on older versions! Did you have to buy a new key?

 

@petankurka if your engine is 1.4MAir 165HP then type6 is correct - MES hasn't included all descriptions.

 

@shpuncik I have realised so. type6 had been there when I bought the car. It is just wrong description in MES 4.7