Useful feedback connects the written file version with a clearly recorded operating condition. It helps the development team assess a request or symptom and link the next revision to the correct data.
On this page6 topics ⌄
01
Record the order and file version first
Provide the order number, written file and writing date. Include ECU/TCU identification, tool, fuel and current hardware. State any changes since the initial order. For Mapswitch, identify the active map set as well.
02
Describe the question the log should answer
Explain what happens, in which operating condition and whether it is repeatable. Add relevant diagnostic faults with context. A single peak value or “the car does not drive properly” leaves too much open. Keep the description concise and specific.
03
Agree on log channels with development
There is no single channel list for every engine. Agree on the measurements, sample rate and conditions for your order. Depending on the question, engine speed, load, relevant requested/actual values, temperatures and torque information may be useful. Recording too many channels at once can reduce the tool’s time resolution.
04
Keep the measurement conditions clear
Record the conditions and vehicle state. Load testing belongs on a suitable dyno or in an appropriate, permitted and safe environment. Do not operate recording equipment while driving. Resolve technical faults and agree on the next step before further load tests.
05
Submit raw data in the existing order
Send the original log format with its time axis and units. A screenshot can mark a point of interest but does not replace the full recording. Vehicle measurements and a flash tool’s communication logs are different kinds of data; identify which you are uploading. Keep questions and revisions within the same portal order.
Record which revision was written and whether the reported behaviour changed. Retain the original software and previous versions separately. Compare measurements only when the conditions are understood. Agree on the next development step from the recorded feedback.
A screenshot can show a symptom. The original measurement data, time axis, units, file version and test conditions are more useful for assessing the full sequence.
Which channels should I log?+
That depends on the ECU and the question. Agree on the required values and measurement conditions with development; there is no universal channel list.
On this page3 topics ⌄
01
Keep the event sequence intact
A revision report should show what was fitted when the observation was made. If a new file, hardware component or fuel configuration was introduced, record its position in the sequence. Do not combine measurements from different versions under one generic filename. When several technicians share the job, the order reference and version record should allow the next person to follow the same sequence without guessing.
Keep the full log even if you also highlight a short section for discussion. The surrounding operating conditions may help explain the event, while the original units and time axis keep the values interpretable. If an export alters those details, identify it as an export and retain the native recording separately.
After a revision is written, describe what changed in the observed behaviour and whether the same condition could be assessed again. If the conditions differed, state that rather than presenting the measurements as a direct comparison. A clear account of what was checked can be more useful than adding a larger number of unrelated channels.
If the issue concerns Mapswitch, identify the active map set. If engine and transmission software are involved, record both installed versions. These details keep the evidence connected to the actual calibration combination instead of leaving development to infer it from a filename.
A request for different hardware, another fuel or an additional function may change the original development brief. Explain that change explicitly in the portal order. It is different from reporting an observation against an unchanged configuration. The next step can then be agreed as work on a revised specification or as a targeted review of the existing delivery, with the relevant files and evidence kept together.
