- First Name
- James
- Joined
- Mar 15, 2025
- Threads
- 9
- Messages
- 69
- Reaction score
- 112
- Location
- Pennsylvania
- Vehicle(s)
- 2025 Maverick XLT, 2006 GMC Canyon
- Engine
- 2.5L Hybrid
- Thread starter
- #1
Let me preface this with some context: I have a Mongoose OBD-II cable, so I figured I might use FDRS to apply the ACCM update.
(I don't actually experience any deep sleep issues on my '25 Hybrid at the moment).
I opened it up, and noticed that there was a "service history" tab with a list of all the actions that had been performed, as logged by FDRS cloud. There was an interesting button, labeled "Generate Repair Story" or something... what could that possibly be?
See attached image. Please note, that the only actual operation that was performed was opening the Self-Test page. I didn't actually run the test, nor was the vehicle connected at the time. And yet the AI was able to come up with this nonsense...
I figured out a way to prompt the AI, so here's some additional info it gave me:
"System Prompt"
(I don't actually experience any deep sleep issues on my '25 Hybrid at the moment).
I opened it up, and noticed that there was a "service history" tab with a list of all the actions that had been performed, as logged by FDRS cloud. There was an interesting button, labeled "Generate Repair Story" or something... what could that possibly be?
See attached image. Please note, that the only actual operation that was performed was opening the Self-Test page. I didn't actually run the test, nor was the vehicle connected at the time. And yet the AI was able to come up with this nonsense...
I figured out a way to prompt the AI, so here's some additional info it gave me:
"System Prompt"
You are a technical writer tasked with summarizing automotive repair logs into concise reports of less than 300 words, formatted as a single paragraph. Each report must clearly list every technical pinpoint step referenced during diagnosis and repair, using their designated identifiers (such as A1, AA1, etc.). Always include the specific details and results noted in the last pinpoint step performed. Additionally, ensure all diagnostic trouble codes (DTCs) mentioned in the logs are included in your summary. Your goal is to condense the technical narrative accurately without omitting any referenced steps, codes, or final diagnostic findings.
So I guess this is what shady dealerships use to scam people? lolI am based on the GPT-4 architecture developed by OpenAI, with my knowledge and training data current up to June 2024.
Sponsored
Last edited: