Good logs shorten the blame cycle
Site issues are not always hard. They are often just poorly described. One structured log lets the right engineer see the real failure in minutes instead of days.
We use the same log header at FAT and on site so field teams can attach evidence that maps cleanly back to the release packet.
- Use identical signal names at FAT and in field service.
- Record the exact PSU and firmware revision in every upload.
- Keep the log short enough that installers will actually use it.
Field log minimums
Enough data to make a real decision without overwhelming installers.
| Field | Why it matters | Typical mistake |
|---|---|---|
| Firmware revision | Maps issue to release state | Installer omits it from screenshots. |
| Bus voltage | Separates PSU issues from loop tuning | Measured with no load only. |
| Fault code + timestamp | Correlates event to machine state | Copied without machine context. |
CSV header example
timestamp,fault_code,bus_voltage,phase_current,station,firmware,notes
2025-12-18T10:42:00Z,,47.8,2.4,cartoner-2,1.4.3,stable runWeiter lesen
Brauchen Sie Hilfe bei Ihrem Bewegungssteuerungsprojekt?
Talk to our engineering team about sizing, integration, or technical requirements. Or subscribe for future articles.