gemini: critique of HOWTO-Start-An-Engine

[rusefillc]

just asked gemini "how could https://wiki.rusefi.com/HOWTO-Start-An-Engine/ be improved" in light of https://www.reddit.com/r/projectcar/comments/1pzt5ag/rusefi_guide/

based on my experience like the pre-start checklist

• make sure battery is charged
• warm-up with OEM ECU if that's an option

AI response below:

Based on the current content of the page, here are several ways the "Performing the First Start On a New rusEFI Install" guide could be improved to be more user-friendly, safe, and effective.

1. Add a "Safety First" Section

Current State: The guide jumps straight into technical requirements.
Improvement: A dedicated safety warning block at the very top is standard practice for engine tuning guides.

• Fire Safety: Remind users to have a fire extinguisher nearby (fuel leaks are common on new installs).
• Personal Safety: Warnings about keeping hands/clothing clear of belts and fans.
• Ventilation: Ensure the area is well-ventilated to avoid carbon monoxide buildup.

2. enhance "Visual Aids"

Current State: The text describes software interfaces (e.g., "grey bars that match your expected trigger pattern," "green vertical line" for TDC).
Improvement:

• Screenshots: Add actual screenshots of the rusEFI Console and TunerStudio showing:

• A healthy "Engine Sniffer" log with the expected grey bars.

• The specific menu where "Global Trigger Angle Offset" is located.

• The "High Speed Logger" window.

• Diagrams: A simple diagram showing the relationship between the trigger wheel, the sensor, and TDC would help visualize the offset concept.

3. Clarify the "TDC / Trigger Offset" Procedure

Current State: The guide suggests a "brute force" method: "try different values between 0 and 720. For example, try 0, then 20, then 40."
Improvement: This section needs a more methodical approach.

• Timing Light Procedure: Explicitly list the steps for using a timing light:

1. Lock timing to a fixed value (e.g., 0 or 10 degrees).
2. Crank engine and observe timing mark.
3. Adjust offset until the mark aligns.

• Alternative Method: Explain why the trial-and-error method is a last resort. Suggesting 20-degree jumps might skip the sweet spot. A binary search approach (0, 360, then narrow down) or checking the manual for the specific engine's standard offset would be better.

4. Expand on "Showconfig" and Console Commands

Current State: The text says "Use showconfig to see current setting" but doesn't explain where to type this.
Improvement:

• Context: Explain that showconfig is a command entered in the rusEFI Console text field.
• Output: Briefly explain what output the user should look for when they type it.

5. Create a "Pre-Start Checklist"

Current State: The requirements are written in paragraphs.
Improvement: A clickable or bulleted checklist would be easier to follow during the actual crank attempt.

• Battery fully charged?
• Fire extinguisher ready?
• Oil and Coolant levels checked?
• Fuel pump primes?
• No fuel leaks detected?
• Laptop connected and logging?

6. Improve "Troubleshooting" Flow

Current State: The "Diagnostics" section is at the bottom, separate from the steps where errors occur.
Improvement: Integrate "What if?" scenarios into the main steps.

• In the "Cranking" section: "If RPM stays at 0, check your Crank Position Sensor wiring."
• In the "Fuel" section: "If plugs are dry after cranking, check injector power (12v) and ground triggers."

7. Terminology and Links

Current State: Terms like "ETB config" are used without definition.
Improvement:

• Definitions: Briefly define ETB (Electronic Throttle Body) or link to the ETB setup guide.
• Base Map: Emphasize the importance of starting with a "Base Map" or "Base Tune" that closely matches the engine, rather than starting from scratch. Link to the rusefi_online tune repository.

8. Addressing Common "First Start" Issues

Improvement: Add a section on common pitfalls:

• Flooding: What to do if the engine floods (explain "Flood Clear" mode: usually cranking with 100% throttle cuts fuel).
• Fouled Plugs: Remind users to check spark plugs if the engine almost starts but then dies.
• Reverse Polarity: A common VR sensor mistake. Mention that if the timing drifts while revving, the sensor polarity might be flipped.

[chuckwagoncomputing]

my notes:

* make sure battery is charged

Good note, should be added

* warm-up with OEM ECU if that's an option

Found in https://wiki.rusefi.com/HOWTO-Get-Running-PnP, which is all it's relevant to.

1. Add a "Safety First" Section

Current State: The guide jumps straight into technical requirements. Improvement: A dedicated safety warning block at the very top is standard practice for engine tuning guides.

* **Fire Safety:** Remind users to have a fire extinguisher nearby (fuel leaks are common on new installs).

https://wiki.rusefi.com/HOWTO-Get-Running-PnP mentions a fire extinguisher

https://wiki.rusefi.com/How-Do-I-Set-My-Trigger-Offset has instructions for disabling fuel.

* **Personal Safety:** Warnings about keeping hands/clothing clear of belts and fans.
* **Ventilation:** Ensure the area is well-ventilated to avoid carbon monoxide buildup.

Maybe let's not insult the intelligence of the customer.

2. enhance "Visual Aids"

Current State: The text describes software interfaces (e.g., "grey bars that match your expected trigger pattern," "green vertical line" for TDC). Improvement:

* **Screenshots:** Add actual screenshots of the **rusEFI Console** and **TunerStudio** showing:

* A healthy "Engine Sniffer" log with the expected grey bars.

* The specific menu where "Global Trigger Angle Offset" is located.

* The "High Speed Logger" window.

* **Diagrams:** A simple diagram showing the relationship between the trigger wheel, the sensor, and TDC would help visualize the offset concept.

Nobody seems willing to take screenshots which I could add to the wiki (see #255), so I guess this a WONTFIX

3. Clarify the "TDC / Trigger Offset" Procedure

Current State: The guide suggests a "brute force" method: "try different values between 0 and 720. For example, try 0, then 20, then 40." Improvement: This section needs a more methodical approach.

* **Timing Light Procedure:** Explicitly list the steps for using a timing light:


1. Lock timing to a fixed value (e.g., 0 or 10 degrees).

2. Crank engine and observe timing mark.

3. Adjust offset until the mark aligns.


* **Alternative Method:** Explain _why_ the trial-and-error method is a last resort. Suggesting 20-degree jumps might skip the sweet spot. A binary search approach (0, 360, then narrow down) or checking the manual for the specific engine's standard offset would be better.

Links to https://wiki.rusefi.com/How-Do-I-Set-My-Trigger-Offset/, but I guess it should be clearer that that page should be read for instructions, and instructions on this page should be reduced.

4. Expand on "Showconfig" and Console Commands

Current State: The text says "Use showconfig to see current setting" but doesn't explain where to type this. Improvement:

* **Context:** Explain that `showconfig` is a command entered in the rusEFI Console text field.

* **Output:** Briefly explain what output the user should look for when they type it.

#641

5. Create a "Pre-Start Checklist"

Current State: The requirements are written in paragraphs. Improvement: A clickable or bulleted checklist would be easier to follow during the actual crank attempt.

* [ ]  Battery fully charged?[ ]  Fire extinguisher ready?[ ]  Oil and Coolant levels checked?[ ]  Fuel pump primes?[ ]  No fuel leaks detected?[ ]  Laptop connected and logging?

meh, users can do this themselves if they want.

6. Improve "Troubleshooting" Flow

Current State: The "Diagnostics" section is at the bottom, separate from the steps where errors occur. Improvement: Integrate "What if?" scenarios into the main steps.

* _In the "Cranking" section:_ "If RPM stays at 0, check your Crank Position Sensor wiring."

* _In the "Fuel" section:_ "If plugs are dry after cranking, check injector power (12v) and ground triggers."

OK whatever

7. Terminology and Links

Current State: Terms like "ETB config" are used without definition. Improvement:

* **Definitions:** Briefly define ETB (Electronic Throttle Body) or link to the ETB setup guide.

* **Base Map:** Emphasize the importance of starting with a "Base Map" or "Base Tune" that closely matches the engine, rather than starting from scratch. Link to the `rusefi_online` tune repository.

A link to https://wiki.rusefi.com/Online/ wouldn't hurt

A link to https://wiki.rusefi.com/Get-tuning-with-TunerStudio-and-your-rusEFI/ already exists as the next step in the process for the user to follow.

8. Addressing Common "First Start" Issues

Improvement: Add a section on common pitfalls:

* **Flooding:** What to do if the engine floods (explain "Flood Clear" mode: usually cranking with 100% throttle cuts fuel).

* **Fouled Plugs:** Remind users to check spark plugs if the engine almost starts but then dies.

* **Reverse Polarity:** A common VR sensor mistake. Mention that if the timing drifts while revving, the sensor polarity might be flipped.

Same as troubleshooting