NUTDRV_ATCL_USB(8)

📦
version 2.8.5 · 18 versions
, in fedora 43, fedora 44

💖 NUTDRV_ATCL_USB 💖

okay so bestie, this is the man page for nutdrv_atcl_usb, one of the drivers in the NUT (Network UPS Tools) manual, section 8. it's the driver for 'ATCL FOR UPS' equipment. yes that's the whole vibe. let's get into it 🫶

✨ NAME ✨

nutdrv_atcl_usb — the driver for 'ATCL FOR UPS' equipment, periodt 💅

🌸 SYNOPSIS 🌸

nutdrv_atcl_usb -h

nutdrv_atcl_usb -a UPS_NAME [OPTIONS]
not me dropping a lil note here: this man page only documents the specific features of the nutdrv_atcl_usb driver. for the lore on the core driver, go read nutupsdrv(8). iykyk 💜

🎀 SUPPORTED HARDWARE 🎀

so this driver is for UPS hardware that identifies itself as USB idVendor 0001 and idProduct 0000, with iManufacturer of ATCL FOR UPS. known manufacturers include Kanji and Plexus. that's the whole guest list 🧚

the UPS interface seems to be a generic USB-to-serial chip, and for the hardware made by Kanji and Plexus, the microcontroller appears to emulate a traditional contact-closure interface. what does that mean for you? it means there are literally only three states in ups.status: OL, OB and OB LB — very similar to genericups(8). no other dynamic status values get reported. that's it. that's the tea ☕

⚠️ heads up: these USB identifiers (including the iManufacturer string) have also been seen on devices that are supported by the fuji subdriver of nutdrv_qx(8), and some others too. so don't assume, okay? 🙈

👑 EXTRA ARGUMENTS 👑

this driver supports the following optional setting:

  • vendor = name — if your iManufacturer (Vendor) string does not exactly match ATCL FOR UPS, you may provide an alternate string right here. OR, if your device does not provide a vendor string at all but you still want this driver to match it, specify "NULL". slay, options 💅

also, a more likely case for a mismatch is that your device is actually handled by another driver for 0001:0000 devices, such as nutdrv_qx(8). just saying 👀

Note: this driver does not intend to support the USB-matching settings that are common to other drivers, like vendorid, product, productid, serial, device or bus. and lowkey important: the vendor setting supported here is not a regular expression. no regex shenanigans, bestie, it's just a plain string 🚫

💀 BUGS 💀

ngl, this is the part where we hold hands and read carefully 🫶

  • the UPS returns the same code for "load power is off" as for "on line power". this condition will not be observed if the NUT upsmon in primary mode runs on the box that's powered by the UPS — but it may be an issue if the UPS is monitored by a remote (secondary) system. so like, remote monitoring? watch out 😭
  • the time between the shutdown command and the removal of power seems to be fixed at 30 seconds. so make sure the NUT shutdown script gets invoked as late as possible in the shutdown procedure, in case some services take longer than others to clean up. don't get caught lacking ⏳
  • most contact-closure UPSes will not power down the load if the line power is present. this can create a race when using secondary upsmon(8) systems. see the upsmon(8) man page for more info. the solution to this whole problem is to upgrade to a smart protocol UPS of some kind that allows detection and proper load cycling on command. treat yourself, upgrade ✨

🌈 AUTHOR 🌈

Charles Lepple — iconic, we stan 👑

🦋 SEE ALSO 🦋

The core driver:

The generic serial driver:

The Qx driver:

Internet resources:

and that's a wrap bestie 🎀 this was Network UPS Tools 2.8.5, dated 10/07/2026 — go forth and monitor your UPS responsibly, mwah 💖✨

📦 where this page comes from