Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
IHU
#11
From what I've seen, the IHU has a certificate for authentication. Each car has it's own certificate.
Somehow the certificate should be moved from the old unit to the new one. Then it should work again.

It is possible to do a ihu certificate reload in VIDA.
- MY2020 V60 T8 Polestar Engineered, Full options
Reply
#12
(08-05-2024, 07:38 AM)TweakeNL Wrote: From what I've seen, the IHU has a certificate for authentication. Each car has it's own certificate.
Somehow the certificate should be moved from the old unit to the new one. Then it should work again.

It is possible to do a ihu certificate reload in VIDA.
It has nothing to do with certification nor authentication. I connected the car via my laptop's wifi and captured the whole traffic between the IHU and the VOLVO servers. 
IHU successfully hand shakes with the volvo servers in TLSv 1.2 and TCP > HTTPS, server and client exchanges hello and encryption keys. 
Then communication begins. Requesting the list of available updates and new applications.   The problem is, when the IHU requests the download, the request includes the VIN number. Then VOLVO compares the VIN number to the IHU's unique number that requests the download. That unique number does not match to the recorded one tied to the VIN in the VOLVO database thus VOLVO server stops and does not provide download link.
Reply
#13
@Power6 Any update on adding IHU reflashing to Oribt. It would be great to be able to update to a new faster IHU and be able to use used parts.
Reply
#14
Sorry for polluting your thread but i have a similar problem.
After my last visit to the dealer i cannot download anything - there is a notification of new updates but once i click the download it goes to paused instant. I suspect a certificate mismatch IHU <-> VCM . Of course the dealer went directly to the replacement of the VCM which is close to EUR 2000. I've heard that a VMC certificate reload or smth similar will fix it.
Is this something Orbit can do ? 

Thank you !
Reply
#15
Do not let those scumbags fool you! It has nothing to do with the VCM.  I sniffed the whole communication between the IHU and the VOLVO servers there is no VCM in that communication. It's purely between the IHU and VOLVO servers for updates and downloads. 

The service you went messed up something with your IHU, they might tried to do or did a total upgrade which includes several updates on the IHU itself. Something might have gone wrong with it.  

Besides, I would force them to fix it since they have caused it!  Force them to do IHU reload for free! Contact VOLVO and complain about the service if they don't.
Reply
#16
Thank you for the reply. 
Unfortunately the service declines all responsibility ... 
Is there any way to do the certificates stuff with Orbit?

Thank you !
Reply
#17
I don't think Orbit can update the certificate inside the IHU. It's part of the downloaded reload software. 
The downloaded reload software(s) from VIDA are all encrypted packages. VIDA runs scripts to decrypt and unpack the individual VBFs. 
Once the VIDA updates the IHU, it also updates the VOLVO servers matching the car's VIN to IHU HW/SW and diagnostic part numbers. 
Your issue might not have anything to do with certificate. It might be the second step where VIDA updates the VOLVO servers. If you are getting available new applications and updates, this means IHU already passed the certificate (authentication). 
The cheapest option you have, is reloading the IHU from VIDA that would update the VOLVO servers.
Reply


Forum Jump:


Users browsing this thread: althon64fx, 1 Guest(s)