Volvo remote behavior

[brobert]

Oh you just answered when I added a question to my posting.
Maybe the orange5 did the checksumming on the fly? Or was it literally editing a file and uploading it again?

It's the latter. I read the UEM's EEPROM, punched in my hex data in the Orange5 editor and wrote it back to the UEM. There is no automated checksum as Orange5 can be used on anything from a Volvo to a Samsung microwave!

I copied the data from a UEM. The 2nd code on the Volvo package for the remote is NOT what is stored in the UEM.
There is an encoding that takes place when using ViDA. And yes, I used the remote paired with that UEM.

I would love to hear from folks that have registered a remote, still have the code from the package and can read their UEM... We need to understand what happens.

/BR

[brobert]

Off topic but the lock cylinder on my Volvo s60 2005 is broken and I can remove the key from the steering column with the engine running. I have to try to lock it and see what happens.

I'd be interested to know the result of your test when removing the key.

I did more testing on my V70 tonight and determined that if a key is in the ignition:
a) It won't let me lock the car with another key (engine was running).
b) Remote fob buttons do not work (from key in ignition or spare remote fob).

To see if this was due to the key's internal transponder, I removed it from the ignition but held it near (so the transponder could still be read).
The car reacted to all remote fob buttons normally.
This makes me think that it's the key-in-ignition signal that prevents door locking and remote fob use.
If this is right, you should be able to lock your car while the engine is running (because you can remove your key) - lucky guy.
/BR

[npexcept]

Off topic but the lock cylinder on my Volvo s60 2005 is broken and I can remove the key from the steering column with the engine running. I have to try to lock it and see what happens.

I'd be interested to know the result of your test when removing the key.

You have to be careful with that!
With the key removed, the steering lock will engage, not good while driving for obvious reasons!
Here in germany, the TÜV (car inspection, MOT) has this even on their checklist (checking if the key can be removed while driving)

[dikidera]

Off topic but the lock cylinder on my Volvo s60 2005 is broken and I can remove the key from the steering column with the engine running. I have to try to lock it and see what happens.

I'd be interested to know the result of your test when removing the key.

You have to be careful with that!
With the key removed, the steering lock will engage, not good while driving for obvious reasons!
Here in germany, the TÜV (car inspection, MOT) has this even on their checklist (checking if the key can be removed while driving)

I mean it's true, you are correct, but nobody would try to remove it while driving. This is simply an experiment to see if it's possible to leave the car idling and running, lock and return later on.

[WhizzMan]

So in summary, when you have another UEM with a keyfob that works with that, you can copy the data on the addresses into your own UEM and then the keyfob works on your own car. The codes you found are not sufficient to program the keyfob to a car using the official dealer method.

[brobert]

So in summary, when you have another UEM with a keyfob that works with that, you can copy the data on the addresses into your own UEM and then the keyfob works on your own car. The codes you found are not sufficient to program the keyfob to a car using the official dealer method.

You got it - the long code (8 bytes or Keeloq code) from the Volvo bag containing the remote fob is NOT what is stored in the UEM.
That code is encoded by the ViDA Volvo installation process prior to writing to the UEM.
The short code (4 bytes or Remote ID) is stored in the UEM without transformation.

/BR