Item 331: 00 value is invalid

[mudHOAX]

Hello,

I did a OTA update on my polestar from v3.3.16 to v3.4.4 and when I connect to the car using Orbit, I get an error regarding my configuration being invalid. More specifically, Item 331: 00 value is invalid.

I've reset to OEM settings, but the error persists.
I've also attempted to unlock Pilot Assist - Level 2, but I ended up with a bunch of fault codes, and couldn't engage Drive or Reverse; so I've just left it as OEM for the time being.

Any idea's?

Thanks.

[R1maS]

I had the same issue with 331. After changing it to 01 or 02, the config became OK, but (do not know exactly if it is the cause, have to check later) on DIM now is the message that something wrong with low beams
What it strange, but it is not possible to return the old 00 value with OrBit - there's no such a setting - only 01 and 02...

The car is XC40 2024

[Poleman]

Hello,

I did a OTA update on my polestar from v3.3.16 to v3.4.4 and when I connect to the car using Orbit, I get an error regarding my configuration being invalid. More specifically, Item 331: 00 value is invalid.

I've reset to OEM settings, but the error persists.
I've also attempted to unlock Pilot Assist - Level 2, but I ended up with a bunch of fault codes, and couldn't engage Drive or Reverse; so I've just left it as OEM for the time being.

Any idea's?

Thanks.

Hi,

I came on here to ask about the exact same issue...

I changed 331 to 01, it cleared the config error.

I then went to program ACC using the config wizard... all programmed fine but wouldn't work, kept saying unavailable on the instrument panel.

I finally tried resetting the ECUs after I had programmed ACC (level 1)... and doing this is got it to work for me.

Hope this helps.

[silentacoustics]

I’m new to Orbit and having the same issue. In my case however, it is not writing to car the 331 change.

It’s saying CEM is not ready for programming, then reconnects.

I’m not sure what I’m doing wrong.

I’ve added the CEM PIN and reran update profile.
I’ve cleared DTCs.
I’ve reset ECUs.
I’ve unplugged the battery for 6 minutes and tried it all again. 
I’ve tried restore OEM
It’s also stating no VGM Detected.

I have a s60 2024 with AAOS so I’m not sure what I’m doing wrong.

[Power6]

FYI, this is a Volvo/Polestar bug in 3.4.4 system update. The CEM is looking for the config item to be set, but the current software on the CEM does not set that config item. 

You can safely ignore it, or you can try setting it, to make the config error go away. It's a new config item, I don't know what "turn indicator intensity" is yet, but safe to assume the "01 Standard..." setting is the safest bet.

Setting back to "00" is a problem in OrBit, as it is not really a setting value, it is the undefined value of a config item that is not used. But you CAN get back to the original undefined value, if you "Restore to OEM" config.

I’m new to Orbit and having the same issue. In my case however, it is not writing to car the 331 change.

It’s saying CEM is not ready for programming, then reconnects.

I’m not sure what I’m doing wrong.

I’ve added the CEM PIN and reran update profile.
I’ve cleared DTCs.
I’ve reset ECUs.
I’ve unplugged the battery for 6 minutes and tried it all again. 
I’ve tried restore OEM
It’s also stating no VGM Detected.

I have a s60 2024 with AAOS so I’m not sure what I’m doing wrong.

Having a problem writing the config, is totally unrelated to what config item you have changed. You are having a general programming problem. You may want to look at the troubleshooting guide for connection issues when programming: https://forums.spaycetech.com/showthread.php?tid=225

If that doesn't help or doesn't describe the problem you have, send a message to support(at)spaycetech<dot>com we will help you to get things working!