Applicability

Logging plans, sample settings and reproducible diagnostic data.

Record the fault and when it happens

A cold-start problem, a lean boost transition and sync loss need different channels. Note the RPM, load and temperature when the fault occurs. Save the trace around the event, rather than just a screenshot of a peak value.

Choose channels that explain the event

For a fuel issue, compare RPM, load, target and measured lambda, pulse width and supply voltage. For trigger faults, compare RPM, synchronization and trigger errors. Add fuel pressure, timing and corrections where available.

Separate sample rate, bandwidth and capacity

GEN1 MaxxECU PC logging at 20 Hz differs from internal maximum rates; G4X’s 100 kHz is aggregate. Memory controls storage, while channel count and rates affect duration; one peak figure is insufficient.

Save the matching map and conditions

Keep the raw log, matching map, software and firmware versions, event time, units and operator actions. After a change, save a new log under similar conditions so the results can be compared.

Reference documents

MaxxECU — GEN1 pinout, trigger system and troubleshooting
Document language: English
Referenced chapters: Pin allocation, trigger synchronization and output tests
Link — G4X and G4+ Quickstart Guides / PCLink Help
Document language: English
Referenced chapters: Sensors, shared I/O, CAN, logging and first start