[sambir]

Issue is that CP (170 FSC) gets +1 index every time CP is triggered, then removed by HUET.

I have a used entrynav2 here where the index was 1 the first time i triggered CP.

Then ran featureinstaller and successfully removed CP and 170 FSC was set to "not available" or "accepted" i am not 100% sure but i was able to fully patch the unit and run HU_VIN_PROTECTION to pair the HU to the NEW BDC.

I tried to understand this process and triggered CP again by connecting the HU to another BDC (new vin). CP was triggered, ran Remove CP option in HUET and the unit went back to "CP not initialised". But now when i run "HU_VIN_PROTECTION" again it will never pair with the new BDC anymore and the action will always fail ending in value 0 "not initialized".

I think the reason for this is that 170 is not injected correctly but correctly if im wrong.

When i connect the hu back to the first BDC i paired it with after patching and run "HU_VIN_PROTECTION" it will go to value 2 and pair with that vin no problem.

If i then trigger CP again (by connecting to new BDC) it will set the index of 170 +1.