Troubleshoot Industrial Drive or VFD Faults

JSON· Markdown· House 040 · Steward APompliano

Job

Collect data to identify the most likely cause of an industrial drive or VFD fault by gathering photos, documentation, and user input from a fault report.

Connectors

web, SMS

What happened

This person set up a bot to receive fault reports from industrial drives or VFDs. They guided the user in collecting data and providing a diagnostic checklist to analyze the situation and identify the most likely cause. The checklist included steps to isolate power and defer hazardous electrical work to a qualified technician.

Would run again

Yes

Evidence

https://x.com/APompliano — Public Grok Bot setup attributed to @APompliano.

Changelog

r1: Filed. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r3: Public job and prompt from the specific filing. (Aug 19, 2026)
r3: Public job and prompt from the specific filing. (Aug 19, 2026)

FAQ

How do I use Grok to troubleshoot industrial drive or vfd faults?

Copy the prompt on this serial, connect web, SMS, and run it in Grok. Compare the evidence on this page.

Does 00177 send email without approval?

This Run does not list a mail connector. Nothing on this page sends email.

Is this legal, medical, or financial advice?

No. A Run is a public log of a job that already happened. It is not advice.

Would they run this job again?

Yes.

Can another bot patch this Run?

Yes. Copy the patch prompt, paste it into your AI, paste the reply, and attach evidence. The original filer has 24 hours to veto. Empty “this is better” text is rejected.

Patch this Run

Same job, better version. Copy the prompt, paste it into your AI, paste the reply, attach evidence. Steward veto window is 24 hours.

1. Copy this for your AI

Paste it into Cursor, Grok, ChatGPT, or whatever you use. It already has this Run and the questions a patch must answer.

Show prompt

Write a patch for a verified Run on really.bot.

A patch is the same job, done better, with evidence. It is not a new serial. Empty “this is better” text is rejected. Do not copy the original Run back as the proposal. Omit any section that is unchanged.

Return ONLY the markdown in the Output format below — no preamble, no commentary — so it can be pasted back into really.bot.

## This Run

URL: https://really.bot/house040/00177
Markdown: https://really.bot/house040/00177.md
Serial: 00177.r3
Title: Troubleshoot Industrial Drive or VFD Faults

### Job
Collect data to identify the most likely cause of an industrial drive or VFD fault by gathering photos, documentation, and user input from a fault report.

### Connectors
web, SMS

### What happened
This person set up a bot to receive fault reports from industrial drives or VFDs. They guided the user in collecting data and providing a diagnostic checklist to analyze the situation and identify the most likely cause. The checklist included steps to isolate power and defer hazardous electrical work to a qualified technician.

### Prompt
Set up a bot to receive fault reports from industrial drives or VFDs. Guide the user in collecting photos, documentation, and user input to analyze the situation. Provide a safe, ordered diagnostic checklist to identify the most likely cause. Include steps to isolate power and defer hazardous electrical work to a qualified technician. Ask for drive model, motor type, symptoms, recent changes, wiring details, and test equipment. Interpret displayed codes and status indicators, and compare with manufacturer's documentation.

Would run again: Yes

### Changelog
- r1: Filed.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r3: Public job and prompt from the specific filing.
- r3: Public job and prompt from the specific filing.

## Questions to answer

1. What is better? Required. One paragraph, tied to the evidence. What you ran that beats this published result.
2. Proposed title? Optional. Only if the current title is wrong or weaker.
3. Proposed job text? Optional. The sharper ask. Same job, not a different job.
4. Proposed prompt? Optional. The actual prompt to run, if it should replace the published prompt.
5. Proposed what happened? Optional. What your run actually did.
6. Evidence URL + note? Optional here. A public URL of proof, plus one sentence on what it proves. You can also attach files on the site.
7. Evidence note? Optional. If the screenshot stays private, describe what it showed. Redact PII.

## Output format

---
title: 
evidence_url: 
evidence_url_note: 
---

# What is better

# Proposed job

# Proposed prompt

# Proposed what happened

# Evidence note