Quote:
Originally Posted by Mark805
As far as interface adaptors go:
As far as I know.. the purple wire deal was for the pac audio, specific to the OS2-Bose adaptor. This was in order to get the interface to work on the H3. Here's the website http://www.pac-audio.com/products/pr...ar%20Interface.
Also here is a link to the directions on their web site: http://www.pac-audio.com/bulletins/2...ringchange.pdf
Personally I would avoid the Pac-audio adaptor. Its what I had with the D1 and it would make a loud "pop" sound when turning OnStar on and off.
There are now specific H3 adaptors out there that eliminate this splicing stuff.
KodiakZ is a pro on this topic fyi. He helped me talk the installer at CarToys through alot of the glitches.
|
I have had some ongoing discussions with Peripheral and I guess I have confused the technician. Their diagrams show the onstar inputs coming into the device on the 24-pin connector, and they actually come into the 12-pin. I believe it is a typo, but he is getting frustrated.
I will be ordering the Peripheral adapters, even if I do continue to drive the tech crazy.

I feel I owe it to the poor guy.
The purple wires are actually easy to understand, but not sure why Peripheral does not fix the adapter. I bet they will in the future since all the new GM radios are being wired the way the H3 is wired.
The reason for splicing the wires is that the class 2 serial data information comes into the radio on pin A2 (24-pin connector) and then is sent out to the XM module through Pin G (12-pin connector), and to the VCIM (onstar module) on Pin A1 (24-pin connector). This pass through of the two-way serial data link is fairly new to GM vehicles, but will be standard in the future. Without splicing the wires, the BCM will lose contact with the VCIM, and XM module, and the modules will not operate since they need VIN confirmation from the BCM, and the BCM is looking for the modules (good reason to keep the XM module powered up, even if not used). So, the work-around is to splice the wires together. Being a class 2 circuit, there is no problem due to the identifier codes from the input/output signals.
I have written Kodiakz, but no answer. Possibly on vacation or too busy installing systems.