Jump to content

Crazy door chime after wiring an amp.

Dio1983
 Share

Recommended Posts

Dio1983 Enthusiast

Dio1983

Posted
Posted

I just hooked up an Alpine mini 4 channel amp to my factory radio and now the chime and turn signal are beyond too loud. I've read just about everything that I can find with a google search and no one has a clear solution. What I'm going to try is switching the amp to 2 channel and getting the signal from the rear speakers instead of front and rear. Has anyone tried that?

DeepBlue17 Enthusiast

DeepBlue17

Posted
Posted

Have you tried going in to the settings and turning down the volume on the chime? Also you need to check your gain settings on the amp. You may have them up too high. If you're maxing out speaker volume with your volume knob at half way that is too much. The gain is designed to match input voltage from the source unit. It is not a volume control. Turning down the gain doesn't mean less power. Just means you have to turn the volume up on the radio more to max out which is how it is designed.

Dio1983 Enthusiast

Dio1983

Posted
  • Author
Posted

Yeah I have always had the volume setting for the chime all the way down. I have the gain on the amp set about half.

DeepBlue17 Enthusiast

DeepBlue17

Posted
Posted

I would try adjusting the gain down as far as you can that still produces the amount of listening volume at 3/4 or full volume from the head unit. Beyond that you're kind of stuck unless you change out the radio.

Dio1983 Enthusiast

Dio1983

Posted
  • Author
Posted

I'm hoping to avoid a new head unit. I'll give the low gain a shot but won't that defeat the purpose of the amp? Wiring one up to turn it basically all the way down seems like a bit of a waste. I'm probably wrong on that though.

DeepBlue17 Enthusiast

DeepBlue17

Posted
Posted

Yeah. Like I said the gain is for matching input voltage. And since you're using a high voltage input from the factory radio. I.e. not low voltage RCAs. It should be almost all the way down. You're still getting the advertised wattage output. You're also then not going to overdrive the inputs causing distortion and premature wear. Trust me if the chime is that loud your gain is way too high.

DeepBlue17 Enthusiast

DeepBlue17

Posted
Posted

Easiest way to set the gain is turn it all the way down. Turn your radio up to 3/4 volume and then slowly turn the gain up to the desired output level.

Dio1983 Enthusiast

Dio1983

Posted
  • Author
Posted

Damn that made a hell of a difference. The gain is now down to a little less than quarter and it's back to being what was normally to loud. Thanks a lot. Sounds clearer at higher volume and saved me from opening up the dash again.

DeepBlue17 Enthusiast

DeepBlue17

Posted
Posted

Damn that made a hell of a difference. The gain is now down to a little less than quarter and it's back to being what was normally to loud. Thanks a lot. Sounds clearer at higher volume and saved me from opening up the dash again.

No problem. Glad I could help.

  • 5 years later...
casey55 New Member

casey55

Posted
Posted

I have a 2022 silverado, non bose here. I am having the same issue with my turn signals, door chime after installing a alpine ktp-44u power pack. I will try this. thank you!

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a good correction. I think “severity” was probably the wrong word for what I meant. What I really mean is closer to event priority, relevance, and actionability — not “this code is severe” or “replace this part.” I agree that a truck can have a lot of trivial or historical communication codes, and if the product starts pushing alerts for every stored or low-value event, people will ignore it very quickly. So the alert logic would need to be filtered. For example, I would not want a random old communication code to generate a push notification by itself. A useful alert would probably need to be based on things like: - new vs historical - active vs stored - repeated vs one-time - duration of the event - whether it happened near the driver-marked symptom - whether it happened together with voltage drop, reset, bus-off, misfire, oil-pressure change, etc. - whether the same pattern repeats under similar conditions So instead of saying “severity,” maybe the product should organize events by affected system and priority. For example: Misfire event: Show misfire counts / roughness first, then fuel trims, RPM/load, DFM/AFM state if available, coolant/oil temp, voltage, and related DTCs. Oil-pressure event: Show oil pressure first, but only in context — RPM, load, oil temperature, coolant temperature, DFM/AFM state if available, voltage, and baseline comparison. Communication event: Show which module/network/message dropped, whether voltage dropped, whether the recorder reset, whether it was active or historical, and whether it repeated. Voltage/reset event: Show battery voltage, crank/wake/sleep state, module reset, communication dropouts, and what came back online first. That also solves the display-order problem you mentioned. The main report should not always show the same fixed list first. It should show the system that appears abnormal first, and then the supporting values for that system. I also agree that the truck already has an oil pressure gauge and MIL. The point would not be to duplicate those. The value would be in showing what else was happening before and after the warning or symptom. For example, if the MIL comes on for a misfire, the truck already told the driver there is a problem. The useful part would be: - which cylinder or bank looked abnormal first - whether it happened after an AFM/DFM transition - whether fuel trims were already moving - whether oil pressure or voltage changed at the same time - whether the same pattern happened previously without a MIL On the OBD port point, I think you may be right for a consumer-facing version. OBD is much easier for the average owner: - easier install - easier removal - inside the cabin - easier phone connection - easier data download - easier to include a pass-through port for another scanner OBD is also the right place for DTCs, freeze frame, VIN, calibration information, Mode 6, and normal scan-tool parameters. The reason I was looking at ECM-side recording is that some events may be gone by the time someone plugs in a scanner, and some powertrain-side network evidence may not be available the same way through the DLC. But I agree that if an OBD-based version can capture enough useful evidence for most owners, that is probably the cleaner consumer product. Maybe the split is: - OBD/DLC version for most consumers - ECM-side version only if it proves it adds evidence that the OBD version cannot get - shop/pro version if deeper powertrain-side event evidence is actually useful So I would not want to force the inline approach if the OBD workflow solves most of the real-world problem. Your last point is probably the key product requirement: the report should be specific to the system showing the abnormality. Not “here are 50 parameters.” More like: “Misfire-related event detected. Here are the misfire/fuel/DFM/context values.” or “Oil-pressure-related event detected. Here is oil pressure compared with RPM/load/temp/baseline.” or “Communication event detected. Here is what dropped, when, and whether voltage/reset happened first.” That is a much better way to think about the report.
    • KARNUT
      2027 GMC Sierra: Official Discussion

      By KARNUT · Posted

      It was all part of the tiny bit of fuel savings it goes towards what was mandated by the government. Much like cylinder deactivation. That was relaxed by the recent administration. All that doesn’t help the individual buyer. But as a whole helps the manufacturer to try to reach the previous ridiculous past mileage per gallon mandate. So yes it was mandated and added cost to the vehicle. 
    • newdude
      2027 GMC Sierra: Official Discussion

      By newdude · Posted

      You do realize that auto stop/start...was never mandated by the fed...right?     EPA Says It's 'Killing' Stop-Start, and Here's What Automakers Have to Say   "Start‑stop technology has never been federally mandated, and the EPA’s recent action removes regulatory incentives associated with it rather than prohibiting its use."
    • Jsdirt
      2027 GMC Sierra: Official Discussion

      By Jsdirt · Posted

      Anytime the government mandates something, you can bet on it being absolutely senseless.
    • c4racer2
      summer road trips in the 2026 2500HD

      By c4racer2 · Posted

      just logged my best MPG for one leg this am - drove home from the Denver Airport, 45 min drive - all freeway, lots of traffic so speeds were limited and some stop and go, got 17.7 for the ~30 mile trip.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...