2004 Honda Civic EX Flock Gauge Setup
2004 · 1.7L; verify market and emissions specification
Does this setup work with Flock?
Start by confirming the ECU protocol and basic OBD-II communication. Factory air/fuel-sensor data needs verification on this exact ECU; it is not confirmed merely by the presence of a factory sensor.
Readings to plan around
- Coolant temperature
- RPM
- Measured lambda / AFR
- Wired oil pressure
These are monitoring priorities, not a promise that every value is available through OBD-II. Available ECU readings depend on the exact car and configuration. The gauge can combine diagnostic data and compatible independent sensors.
Notes for this Civic EX
- Factory sensor equipment and diagnostic exposure can vary by emissions specification. Confirm the actual sensor and ECU rather than treating all 2004 EX cars alike.
- A narrowband O2 voltage or commanded equivalence ratio is not measured wideband AFR.
- Only add a custom air/fuel query after its response layout and scaling are confirmed. If reliable AFR is required, use a compatible wideband controller's documented 0–5V output.
Set up and verify
- Record the vehicle year, market, engine, transmission, ECU and any tune or conversion. Check the current Flock release instructions before configuring the gauge.
- Confirm the diagnostic protocol or aftermarket ECU output before selecting an adapter. A matching connector is not proof that the data format is supported.
- Verify each selected reading against a trusted diagnostic tool. For a custom PID, confirm the request, module header, session requirements, data-byte positions, formula, units and installed firmware support.
- Add compatible independent sensors for missing readings. Test a complete start, warm-up and shutdown cycle, then save the display layout and set warnings from the engine service data.
If a reading is missing
Confirm that a basic channel still works before changing a custom query. Collect the ECU identity, protocol, adapter and gauge firmware versions, and a diagnostic response for the missing channel. A factory sensor or a reading in another app is useful evidence, but the request and response still need to match the gauge. Use a dedicated wired sensor when a dependable measurement is needed and ECU access cannot be verified.
My car was not listed. Does that mean it is unsupported?
No. The guides describe setup paths and known limitations. For a car with diagnostic data, confirm its protocol and the specific readings you need. A dedicated sensor setup can be used independently of factory diagnostic support.
Which sensor fittings and warning values should I use?
Use the service information for the installed engine and the sensor manufacturer’s specifications. This guide does not assign unverified port threads, torque settings, wiring pinouts or universal alarm temperatures. Keep factory warning devices in service.
Sources and next steps
Vehicle documents establish model details; they do not certify Flock compatibility. Third-party diagnostic definitions require verification with the actual ECU and released gauge firmware.