What the Black Box Remembers: The Alarm Log Inspectors and Auditors Ask For

▌  APPLICATION NOTE  ·  OCTOBER 2026  ·  BLACK BOX DATA RECORDING

What the Black Box Remembers: The Alarm Log Inspectors and Auditors Ask For

A tower crane records a great deal as it works, and almost none of it is looked at on an ordinary day. The record matters on the days that are not ordinary: an inspection, an audit, a near miss, or a claim about what a crane was doing at a particular moment. The ZNAO-TG2 tower crane safety monitoring system, product code CR-SMS-TG2, keeps a log of alarms and the conditions around them, and that log is often the first thing an inspector asks to see.

This application note explains what the black box stores, how an inspector or auditor tends to read it, and how a site can turn the log from a document that is produced reluctantly into a routine part of shift management. It stays strictly with what the system actually does: sensing load weight, moment, trolley radius, hook height, slew angle, wind speed and tilt; raising overload and threshold alarms with a sounder; and logging those alarms for audit, inspection and accident back-trace.

01  WHY A LOG CHANGES THE CONVERSATION

Without a record, a question about a lift gets answered from memory. The operator remembers lowering slowly, the signalman remembers the load swinging, the supervisor remembers the wind picking up at about lunchtime. Memory is honest and useful, but it is also approximate, and when two accounts disagree there is no way to settle the point. A log turns those accounts into a timeline with values attached.

The value of that is not only legal. A log changes the tone of an inspection. When an inspector can see a continuous record of load, radius, moment and wind, the conversation moves from suspicion to verification. The site is not asked to prove that it behaved; the record shows how the machine actually behaved, and the discussion can move on to the things that need action.

▌  RECORD, NOT MEMORY  A log replaces approximate recollection with a timeline of values, which is why it settles the questions that memory cannot.

▌  VERIFICATION TONE  When the working behaviour is visible on the record, an inspection becomes a verification exercise rather than an argument.

▌  CONTINUOUS EVIDENCE  The log samples the machine as it works, so the ordinary shifts are documented as well as the eventful ones.

02  WHAT GETS WRITTEN DOWN

The system senses load weight, moment, trolley radius, hook height, slew angle, wind speed and tilt. Those are the quantities that decide whether a lift is inside its limits, so they are the quantities that are worth keeping. Alongside them the system raises overload and threshold alarms with a sounder, and each of those alarm events is written to the log.

Sensor accuracy matters here, because a log is only as credible as the numbers inside it. The ZNAO-TG2 states radius to 0.1 m, height to 0.1 m, slew to 0.1 degrees, load to 0.01 percent and wind to 0.1 m/s. Those resolutions mean the record can distinguish a lift that was close to a limit from one that was comfortably inside it, instead of reducing everything to a vague sense that it was probably fine.

The system also watches its own health. If a sensor fails, it raises a yellow prompt and resets automatically once the condition clears, so a gap or a fault in the data is itself part of what the record shows. An inspector reading the log is not left guessing whether a quiet period meant a quiet crane or a dead sensor.

▌  THE SEVEN QUANTITIES  Load, moment, radius, height, slew, wind and tilt are logged because they are the measurements that define a lift.

▌  STATED RESOLUTION  Radius 0.1 m, height 0.1 m, slew 0.1 degrees, load 0.01 percent and wind 0.1 m/s make the record specific rather than approximate.

▌  SELF-MONITORING  A sensor-failure prompt with auto-reset means faults appear in the record instead of hiding inside a silent gap.

▌  LIVE PICTURE IN THE CAB  The 11.6-inch 1920x1080 industrial display shows the live values in the cab while the Linux host writes the log.

03  HOW AN INSPECTOR READS IT

An inspector usually starts at the end and works backwards. The event that prompted the visit comes first: an alarm, a near miss, a complaint. From that point the log is read outwards, checking what the crane was doing before the event, how close the values ran to the limits, and whether the same pattern appeared earlier in the shift or on previous days.

Repetition is the thing an auditor looks for hardest. A single alarm on an unusual lift is a fact; the same alarm at the same stage of the same operation every morning is a procedure. That is why the log is often more useful to the site than to the visitor. It shows patterns that no single day reveals, and it shows them in the machine's own numbers rather than in anyone's recollection.

▌  START AT THE EVENT  Inspectors read backwards from the event, then check what led to it and whether it repeats.

▌  PATTERNS OVER INCIDENTS  One alarm is a fact; a repeating alarm is a procedure that needs changing.

▌  SITE VALUE FIRST  The log is most useful to the people who can act on the pattern, which is usually the site, not the visitor.

▌  ZONE AND COLLISION CONTEXT  Zone limiting of line, triangle, quadrilateral and circle obstacles, up to 8 zones, and group anti-collision pre-warning add context to the alarm entries.

04  TURNING THE LOG INTO ROUTINE

If the log is only opened during a problem, it is being wasted. A short weekly read costs very little and catches the drift that supervisors otherwise notice late: a lift that has been running closer to its limit, a point in the day when wind alarms begin, a stage of the cycle where the moment peaks. None of that requires a specialist; it requires a habit.

The same record supports the toolbox talk. A supervisor can refer to what the machine logged without naming individuals and without a debate about memory. Because the quantities are specific, the conversation becomes about the lift rather than about who was driving. Used this way, the log quietly raises the standard of the discussion on a site.

▌  WEEKLY READ  A short, regular review catches gradual drift long before it becomes an incident.

▌  TOOLBOX MATERIAL  Logged values give a supervisor concrete material for briefings that does not turn into an argument about recollection.

▌  EXPORT AND STORE  With RS485, USB and LAN outputs on a Linux host, the record can be exported, archived and compared over time.

05  WHAT THE LOG DOES NOT SETTLE

It is worth being plain about the limits. A log documents what the sensors measured. It does not explain why a decision was made, and it does not replace the lift plan, the risk assessment, the competence of the crew or the requirements of the standards that apply in a market, such as ISO 12480-1, EN 14439, BS 7121, LOLER 1998 or OSHA 29 CFR 1926 Subpart CC.

The record also depends on the machine being powered and monitored as intended. A system that is switched off writes nothing, and a system that is trusted but never checked is worse than none, because it invites confidence in a record that is not being made. The log is evidence, not a substitute for supervision, and it is strongest when the site treats it as a working tool rather than a document to produce on demand.

▌  DOCUMENTS, NOT EXPLAINS  The log shows what was measured, not why a person made a particular decision.

▌  RULES STILL GOVERN  Local standards and the lift plan remain the authority; the record supports them and never overrides them.

▌  POWER REQUIRED  A switched-off system logs nothing, so the discipline of leaving it running is part of the evidence itself.

PROCUREMENT IMPACT

●  If inspections and audits are a recurring cost on your sites, ask what the system stores and how it is exported, because a log that cannot be retrieved easily is not much of a record.

●  Check the stated sensor resolution against the lifts you actually perform, since a log is only as credible as the numbers inside it.

●  Confirm how sensor faults appear on the record, so that a quiet period can be distinguished from a failed channel.

●  Decide where the log will live: on the Linux host at the crane, an export over LAN, or a docked enterprise or regulatory cloud, and plan the network accordingly.

●  Treat the 4G plus 433M wireless and the RS485, USB and LAN outputs as part of the record system, not as accessories, because retrieval is what turns stored data into evidence.

WHAT TO WATCH

●  Watch whether the log is actually left running across shifts, because the most common gap in a record is simply a system that was switched off.

●  Watch the pre-shift check. If the display and the sensors are not confirmed healthy before the first lift, the record for that shift is unreliable.

●  Watch for repeating alarm patterns in the weekly review, since repetition is the earliest visible sign that a routine needs to change.

●  Watch how faults are logged. A record that hides sensor failures cannot be trusted when it looks quiet.

●  Watch the standard that applies in your market, and keep the log in whatever form that regime requires from the operator.

ABOUT  ZN Industrial (Shandong Zhinuo) designs and manufactures crane safety monitoring systems, positioning systems and mechanical auxiliary handling equipment for overseas construction, industrial and steel markets.

Standards and regulations vary by market — local rules still govern your site.

▌  CONTACT  shandongzhinuo@outlook.com  +86 176 6371 0314 · en.znaqkj.com

SOURCES · ISO 12480-1 · EN 14439 · BS 7121 · LOLER 1998 · OSHA 29 CFR 1926 Subpart CC