Mystery Of Onstar Vcim Purchase Restrictions

[Spurshot]

There's been a lot of grumbling on the various forums about GM's restricted sales of Onstar VCIMs for those that want to add Bluetooth by purchasing later model VCIMs. When the dealers order VCIMs, they have to go thru some extra hoops to ensure the VCIM is a true "apple for apple" replacement due to failure, theft, fire, etc.. Upgraders are frustrated at the policy and don't seem to understand the reason for such a policy.

 

 

My speculation of why the policy exists is pretty straightforward. The Onstar system has the ability to recieve information from, transmit information to, and command functions on, vehicles out there in service. The system identifies individual vehicles thru unique identification (VINs?). If you buy a VCIM and it has a VIN (or whatever identifier they use) the same as another vehicle, any Onstar command, or data could be erroneous. For example: if the owner of the other vehicle with the same VIN in his VCIM were to request the doors to be unlocked, your doors may be unlocked too. Theft tracking and all other functions might be corrupted in similar ways. Essentially, Onstar relies on being able to uniquely identify individual vehicles out there and loosing control of VCIM identifiers could collapse their house of cards.

 

That's my 2 cents of speculation anyway.

[music]

Seeing that I know absolutely nothing about the VCIM, and haven't even considered adding bluetooth... I can fully agree with you Chuck... without consequence:)

 

However... (and again, I know zip about the Onstar/VCIM/Bluetooth topic...)

 

If the VCIM is the "logic box" behind ONSTAR, then it has a unique hardware address (akin to a cell phone hardware address). That physical address would be unique on planet Earth and "married" to a VIN/owner/etc. in their database. Swapping a VCIM should also, then, require that the owner notify GM/Onstar to update their database to remarry the VCIM to the new VIN. It's possible that the VIN is hard-coded into the VCIM, but it would be unusual... as all other physical addresses (e.g., Ethernet, CDMA, etc.) are unique at the hardware level, but then matched to a user-value (e.g., phone number, tcp address, etc.) at the DNS/router level (in this case, the Onstar database).

[Matt_]

lol chuck.. go outside and cut the grass or something... you're thinking way too much about this VCIM stuff.

 

=D

[Spurshot]

Matt,

I did end up convincing a parts guy to go around the restrictions by putting in faked responses to the required information. I got my VCIM by providing a VIN from an 09 truck listed on the web. When that owner gets Onstar to unlock his doors, mine will probably unlock or something.

 

My latest distraction is bbq. I've been makin some great stuff on the new pit.

 

[dlstewart01]

Its not paranoia if they really are after you...

[C. Charles Hahn]

Matt,

I did end up convincing a parts guy to go around the restrictions by putting in faked responses to the required information. I got my VCIM by providing a VIN from an 09 truck listed on the web. When that owner gets Onstar to unlock his doors, mine will probably unlock or something.

 

More irrational concerns, Chuck.

 

The VCIM has to be activated to the vehicle once physically installed before OnStar can actually do anything to "control your vehicle" -- yours isn't activated, and thus won't do anything.

 

Onstar VCIMs are identified within their network by ESN/STID (basically a module serial number) and NOT by vehicle VIN. No two VCIMs have the same ESN/STID.

[Spurshot]

Matt,

I did end up convincing a parts guy to go around the restrictions by putting in faked responses to the required information. I got my VCIM by providing a VIN from an 09 truck listed on the web. When that owner gets Onstar to unlock his doors, mine will probably unlock or something.

 

More irrational concerns, Chuck.

 

The VCIM has to be activated to the vehicle once physically installed before OnStar can actually do anything to "control your vehicle" -- yours isn't activated, and thus won't do anything.

 

Onstar VCIMs are identified within their network by ESN/STID (basically a module serial number) and NOT by vehicle VIN. No two VCIMs have the same ESN/STID.

 

 

 

I'm not concerned in the least. I have plenty of aluminum foil for a helmet.

[cfeiring]

Now the question begs to be asked.

 

If one installs a new box in the truck can the onstar and all the other functions be made functional after the install?

 

How much does the new box from GM cost it can be acquired?

 

Just curious as I like the onstar svc, I do a lot of driving in very rural areas, like the ability to "phone home" in case something bad happens, plus I have two teenage daughters that drive as well, so its worth those few extra dollars a month for the safe and sound plan.

 

Yeah somebody knows where I am / been but not too worried, I live a rather boring life, so I do not gather that much attention.

[C. Charles Hahn]

Now the question begs to be asked.

 

If one installs a new box in the truck can the onstar and all the other functions be made functional after the install?

 

How much does the new box from GM cost it can be acquired?

 

Just curious as I like the onstar svc, I do a lot of driving in very rural areas, like the ability to "phone home" in case something bad happens, plus I have two teenage daughters that drive as well, so its worth those few extra dollars a month for the safe and sound plan.

 

Yeah somebody knows where I am / been but not too worried, I live a rather boring life, so I do not gather that much attention.

 

Looks like you have some reading to do:

 

http://www.gm-trucks.com/forums/index.php?showtopic=110155

 

http://www.gm-trucks.com/forums/index.php?showtopic=78031

[Silver Wraith]

Mmmm....barbeque! Where'd you get the bbq? My mission this summer is to get serious about it

 

Matt,

I did end up convincing a parts guy to go around the restrictions by putting in faked responses to the required information. I got my VCIM by providing a VIN from an 09 truck listed on the web. When that owner gets Onstar to unlock his doors, mine will probably unlock or something.

 

My latest distraction is bbq. I've been makin some great stuff on the new pit.

 

[stormrider]

Its not paranoia if they really are after you...

 

If you look real close there is a little red "guy" hiding behind the tree in his yard......behind the grill

[Matt_]

Matt,

I did end up convincing a parts guy to go around the restrictions by putting in faked responses to the required information. I got my VCIM by providing a VIN from an 09 truck listed on the web. When that owner gets Onstar to unlock his doors, mine will probably unlock or something.

 

My latest distraction is bbq. I've been makin some great stuff on the new pit.

 

 

 

From the sequence of these pictures... i get the feeling you cooked your dog!!!

[MarkD]

First, I wouldn't worry about 2 VCIM's being associated with 2 different VIN's.

 

I would agree that it makes sense that there is a "marrying" process in the OnStar database between the hardware address and the VIN.

 

If you get the old VCIM and a new one is installed (why would anyone do this anyway with a functioning BT VCIM?) by following the "correct" procedure through GM and Onstar, there would have to be a "divorce" and a "second marriage" in the OnStar database.

 

I would imagine that this "marrying" process is a highly restricted function, possibly requiring lots of internal paperwork and multiple management approvals. This is probably the reason for the GM/OnStar reluctance to promote the upgrade.

[C. Charles Hahn]

First, I wouldn't worry about 2 VCIM's being associated with 2 different VIN's.

 

I would agree that it makes sense that there is a "marrying" process in the OnStar database between the hardware address and the VIN.

 

If you get the old VCIM and a new one is installed (why would anyone do this anyway with a functioning BT VCIM?) by following the "correct" procedure through GM and Onstar, there would have to be a "divorce" and a "second marriage" in the OnStar database.

 

I would imagine that this "marrying" process is a highly restricted function, possibly requiring lots of internal paperwork and multiple management approvals. This is probably the reason for the GM/OnStar reluctance to promote the upgrade.

 

Mark, with all due respect, have you even read through any of the other threads about VCIM retrofitting and the bluetooth upgrade process? While you are on the right track about the way the OnStar database works from a technical standpoint, you're way off when it comes to the actual procedural steps necessary for performing a swap.

 

In all reality, VCIM swaps aren't all that uncommon. Swaps that involve installing specific hardware into a vehicle that did not come factory equipped with the same hardware are where the problems arise, but they're nothing to do with any policy about needing managerial approval to set up the account or altering the database.

[mitchtazz]

i'm pretty sure all onStar VCIM's are vin specific. Which is another reason why when you order it you give your vin. It comes with the vin already stored into it, and since your ecm has the vehicles vin stored, when ever they try to mate they have a domestic disturbance and the onStar portion of the VCIM shuts down and you get the red light on your mirror..

 

for example, person A has a vehicle with vin 123456 and person B has a vehicle with vine 654321. Person B wants BT so tries to order another VCIM, they tell the dealer they want the VCIM from a 2010 sierra with BT, dealer asks for vin knowing full well what the customer wants to do. Customer gives vin to 2010 sierra 123456.. Onstar doesn't send a new VCIM with no vin stored into it. They send one with the vin you gave to the dealer already programmed into it. Customer takes VCIM home and installs. VCIM and ECM begin to disagree and onStar portion of VCIM shuts down only allowing BT. so even though there's two VCIM's out there with the same vin, it doesn't matter if the other guys remotely unlocks their doors cause your OnStar is disabled.. seems like one cool azz safety feature if ya ask me. In that case, the key to getting BT and OnStar would be to find a way to "spoof" your vin onto the VCIM with BT.