MAN ME: exporting MOP event logs for remote troubleshooting
EL-0169 · Procedure · rating 0 · occurred 31 Jul 2022
Source: /cases/el-0169
Scope#
This is how I export the Event Log and the HCU, HPS and Cylinder Events from the MOP of a MAN ES (formerly MAN Diesel & Turbo) ME engine, to send to a remote troubleshooter. There are two parts:
- Procedure A: export the Event Log (alarm and event history).
- Procedure B: export HCU, HPS and Cylinder Events.
The steps follow the MAN guide "Data Collection for Troubleshooting", rev. 5, reference EEO9/THSK/2018-01-03, pages 14 to 19 of 34 (section 3 and section 4.1). Section 4.2 (bulk export from the "MAD" folder) and the rest of the guide are not covered here. I don't have software versions or the differences between MOP screens.
Safety#
The guide pages I use give no safety notes. The steps use only the MOP screens and a USB stick.
Tools & parts#
- One empty USB stick.
- Access to MOP-A or MOP-B for the Event Log.
- Access to MOP-B for HCU/HPS/Cylinder Events.
Steps#
Procedure A — Event Log (either MOP)
- On MOP-A or MOP-B, open Alarms > Event Log.
- If you need only part of the log, press "Time Span Filter". Choose the time period and press "Apply". For the full log, do not use the filter.
- Press "Export".
- Put the empty USB stick into the MOP.
- Press "Save". The time to save depends on how many events you export; a big log can take some time. Wait until it finishes.
Procedure B — HCU/HPS/Cylinder Events (MOP-B only)
- On MOP-B, open Troubleshooting > HCU/HPS Events. These events are not on MOP-A.
- An event can be recorded in two ways:
- automatically, when an alarm starts the recording;
- manually, by the operator. HCU, HPS and Cylinder events are all collected in the same way.
- To record an event manually, press "Log Manually". Then select one cylinder or more. After a short time, the new log shows in the list on the left side.
- To export, put the empty USB stick into MOP-B.
- Select the event in the list.
- Press "Export", then press "Save".
- If you need many files, note that all of them are in the "MAD" folder. The guide explains this in section 4.2, which I don't cover here.
Check after#
- Check that the exported files are on the USB stick before you send them.
- I record events about once a month in normal running, and also every time there is a problem. Regular records help the troubleshooter and give a baseline to compare with.
- I also record MOP graphs at several loads while the engine is in good condition, and learn how to read them. In my experience, a healthy baseline makes faults much easier to find.
Example — exhaust valve position overshoot
| Check | Result |
|---|---|
| Engine | MAN 6S60ME-C |
| Exhaust valve position graph | Signal overshoot (jump) seen |
| Operating modes | Overshoot seen in all modes |
| Engine running | No effect |
| Exhaust gas temperatures | Normal |
This overshoot is normal. The valve opens as it should, and damping force acts on it. Because of this force, the valve comes back to a higher position. This damping is usually found on high-force exhaust valves. No fault was found or repaired.
Comments · 0
No comments yet.