I have a question if you could check something for me. I installed a 350 gauge cluster but the car will chime when the driver door is open all of the time. I bought a 350 headlight switch and plugged it in real quick and it does the same thing. I was wondering if you get the chance to see if plugging in the normal 15-17 switch causes the 350 to chime constantly. It should chime with the door open and no switch plugged in.
These are the conditions you want me to test?
Yes those would be perfect! All the lights being turned on is weird as heck. With the 350 cluster installed my car chimes even with the switch installed but I was interested to see if the 350 would chime without the switch or the switch with the foglight buttons. The 350 switch worked on the GT but you just couldn’t use the foglights (was hoping the chime would stop). I figured it might have been the switch the cluster didn’t like since car chimed like there was no headlight switch plugged in but that wasn’t the case for me.
I don't think you're correct. What you stated there is tied to models, trims, and packages as far as I'm aware. They aren't standalone options. So you just have to know what the package entails.
There is this sheet that someone made specifically for GT350s, although I'd avoid it because the characters aren't properly isolated. You generally never want to just blindly swap an entire line of as-built. For example, we generally refer to as-built mods like this:
Where the x means to leave that character alone. So you'd just set the 10th character to 8. But what's in that GT350 sheet is all like this:
That's really bad practice! Only one of those digits is responsible for the awesome feature, but changing all of the digits can (and often does) have unintended consequences.
Is that in reference to my earlier post? I would say it hugely complements AsBuiltExplorer. You could use (and I do use) AsBuiltExplorer to compare cars with slightly different options to figure out how the As-Built interacts with those options.
Yes
Browse dealer sites and gather a list of VIN's. Then go to the service site and download as-builts and ETIS files. It's tedious but it works.
The sheet you linked to was developed as the Forscan tweeks were just being understood here. Though it might not follow the emerging protocol about how to communicate changes, there's no reason doubt the information contained. It was developed, maintained, and protected by member [MENTION=18007]mattlqx[/MENTION], a trusted source.
Ok, got it.
Actually as Spart previously stated, you do NOT want to blindly change an entire as-built line of code without knowing what you're doing. While you might want to just change a single thing, switching the entire code will change multiple things, potentially causing unwanted results. However trust worthy your source is, posting an entire code from another car is not the correct answer to making changes.