SMT2200I SmartUPS with only USB and serial: View details of info from display

[jb_dk]

Our Small Business uses a SmartUPS SMT2220I with a USB port for potential server interface and an RJ45 serial port.  Currently it is not connected to any UPS management software (partially because there is no obvious download page for this model, and only older/smaller SMT-series models are listed in the combined firmware 4.3.8v9a zip file from 2026-Jan-09).

The built in LCD display displays some settings whose names are so abbreviated as to be ambiguous in their meaning and effect .  And the display also lists some highly relevant log events, but with no indication of when each event occurred (either in wall clock date/time or in hours/minutes/seconds before viewing the log entry).

So the question is if there is a tool to extract the information shown on the LCD, but with maximum details, either to a computer screen or some kind of readable computer file.

[Teken]

For more detailed information would require a (NMC) Network Management Card to be purchased and inserted into the rear Smart Slot.

You may consider purchasing the following legacy EOL NMC AP9630, AP9631 or current generation and supported model AP9640, AP9641 NMC.

The NMC provides a internal web interface to setup, manage, control, and view events along with sending email alerts.

The NMC provides many services to help integrate with third party services / applications such as SNMP, SysLog, etc.

In the interim you may connect the unit to a computer that is running APC Power Chute Software (PCSS) to help setup, manage, and view the event / data logs.

PCSS also supports SNMP, Email notification.

Questions Ask . . . 👍

[jb_dk]

You misunderstand the log issue.

The SMT-series SmartUPS already logs the info and displays it on the front panel LCD, but the LCD display omits some details to fit on the small display.  The logging desire is to simply extract the data already logged and stored in the core UPS electronics, but without the truncation.  Not to set up any larger logging infrastructure such as an NMC card or the APC cloud service.  Extraction would be done by a technician plugging in a pre-configured laptop into each SmartUPS to be investigated for questions like "Did this standalone UPS trip at the time when the protected equipment visibly glitched during use (according to local personnel)?"  "Was it an external power loss, Front panel commend or an artifact of one of the builtin self-tests?"

As for my notes on timestamps, this was simply a concept for how a non-networked APC UPS that has no managed clock and no time sync client can still store the equivalent of a timestamp while leaving the translation from "seconds since battery first charged" to real date/time values would be done by PowerChute comparing to the "seconds since" clock for the time when extracting data over the next version of the Smart protocol, then correcting for the date/time on the PowerChute computer.  Thus the UPS would just remember that "UPS transitioned to power acceptable" at 123456789 seconds since UPS initially obtained enough battery charge to count internal clock cycles and report that the status/log query happened at 234567890 seconds on the same scale, PowerChute would then know that the transition happened 111111101 seconds earlier and that the computer running PowerChute has a local system clock of 2027-04-05t13:45, thus the transition happened at 2023-09-27 at 13:33:19 .  For newly designed protocol fields, the seconds count should be at least 40 bits in case a more expensive UPS products gets proper battery hot-plug replacements and service every 5 years for over a century, while being fed from am even bigger UPS that had almost no interruptions for so much time.

The configuration desire was to get the more verbose field descriptions which I have since found to be included in the "PowerChute Serial" web interface.

[Teken]

Your question was how to obtain a more verbose human readable text of the event logs.

Two APC options were provided here. ☝️

If this is was a serious installation a NMC would be installed and monitored by a NMS. It’s clear to me this isn’t a serious installation that must follow any ISO Standards or Insurance Standards.

If it was the infrastructure to monitor the most critical infrastructure of power delivery and management would already be present and used.

Having a random person connecting a laptop to obtain past events with no historical reference provides absolutely no context or insight! 🤢

Hence why all serious Enterprise installations monitor the systems via SNMP, SysLog, etc.

As every metric of the system can be tracked, monitored, and flagged. Connecting via Power Chute only provides you a snap shot if it’s not running continuously on a dedicated computer system or connected through a SBC using APCUPSD / NUT.