19 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHAnnoying Beeping... Need Help!
Leading reported evidence
Replace assembly and cleared/
Performed · outcome unconfirmed
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Performed · outcome unconfirmed · Original poster
They replaced the assembly and cleared/reset the codes.
Leading evidence: 'Replace assembly and cleared/' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'horn going off' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Check settings' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that suspect a cause
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suspected cause · Original poster
At first I thought it was the horn going off for some reason, but the pitch of the horn is much different than these little beeps.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion · Original poster
They replaced the assembly and cleared/reset the codes.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
Had no idea what "set" meant on the trip computer stalk, I actually thought the speed display which was always "- - " was just something that wasn't displayed because the speed was already digitally displayed.
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
Had no idea what "set" meant on the trip computer stalk, I actually thought the speed display which was always "- - " was just something that wasn't displayed because the speed was already digitally displayed.
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
19 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Rennlist: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
1 acknowledgements have no verified action link; they do not establish a repair result.
My 71,000 mile 2002 Cab has begun giving off little "beeps", maybe more like "chirps", usually two very fast ones, when driving along. At first I thought it was the horn going off for some reason, but the pitch of the horn is much different than these little beeps. All gauges read fine and no lights blink when the beeps sound off.
Any ideas of what's going on??? Many thanks!
Bill
Bill: Does it sound like the alarm horn which is different than the main horn. The alarm horn is the one that goes off when you try to lock the car with the key and something is open inside the car i.e. window down-glove box lid-etc. could mean something about the top but not sure as I don't own a cab.
Yes, it does sound more like the alarm horn. But more like "Chirps". So far, it seems to only happen when the top is down, but I'm not totally sure about that. Will have to pay closer attention!
Bill
Speed limit warning would by my guess. I have noticed that sometimes it migrates from 82MPH where I have it set to odd other speeds. it seems to coincide with my wife driving the car so I assume it is related to random button and lever pressing that often accompanies that event
You can reset it from the lever behind the steering wheel to a more suitable speed
I just figured out that my car had the speed warning a few weeks ago during a long drive on the highway. Had no idea what "set" meant on the trip computer stalk, I actually thought the speed display which was always "- - " was just something that wasn't displayed because the speed was already digitally displayed. Then I found out it was a speed warning because I had set it for the first time on my road trip playing around with the trip computer.
OK... I checked and the speed Limit was deactivated. I did notice the limit was set to + or - 30mph though.
I reset everything. Set the speed to + or - 180mph and again hit the switch to deactivate the Limit. Will report back after driving again. Many thanks to those who probably figured this out for me!
Bill
Welp.... I took a 30 mile drive and the problem reoccurred. Also went off several times after I turned off the ignition. My wife said it’s the same sound as when you push the remote to unlock the car. SO.., I locked the car with the door key inserted. Will be taking it out again in an hour or so and will report back.
Welp again... drove home and the darn thing started beeping again. This time, however, the LIMIT sign came on. It still read "Nonactivated", but the 186 mph speed limit I'd set earlier changed to read 38mph.
What's going on here???? Computer short circuit?
Bill
Well your wife hasn't read the owner's manual...locking/unlocking emits no beep unless there's a fault - e.g., glove box open, hood open, etc. If I remember correctly, the alarm horn is to the driver's side of the battery forward while the horn is hear the passenger side of the front bumper. Maybe if you can determine which location the sound is coming from it will help in your diagnosis. Do you happen to have an aftermarket device like Remote Key or Smart Top? Good luck - let us know what you find.
OK... I took the car over to my ace Porsche mechanic and he diagnosed the problem as a fault in the driver's door alarm system. New part ordered, car will be back and pain free tomorrow.
Thanks for all the excellent advice above!
Bill
Got the car back and all is fine now.
The driver's door lock mechanism was defective. They replaced the assembly and cleared/reset the codes. Total bill came to $840.00.
Door lock mechanism Part #8N1 837 015 C.
Top is down and I'm heading for the coast!
Bill
