Apcupsd est un système de contrôle UPS qui permet l’arrêt méthodique de votre\nordinateur en cas de panne de courant.\nCopie et distribution de ce fichier, avec ou sans modification,\nsont autorisés sur n'importe quel support sans redevance à condition d'appeler le nom Apcupsd,\nla notice de copyright, et cette notice sont préservées.\nLe code source d'Apcupsd est publié sous licence GNU General Public License\nversion 2. Veuillez voir le fichier COPYING dans le répertoire source principal.\nPour plus d'informations sur le projet, veuillez visiter le site web principal\nau http://www.apcupsd.com
"},{"id":"text-2","type":"text","heading":"","plain_text":"Personne ne devrait s’appuyer sur le contenu du manuel de l’APCUPSD («le manuel»)\nsans avoir au préalable obtenu l’avis du support technique APC.\nLe manuel est fourni sur les termes et comprendre que:","html":"Personne ne devrait s’appuyer sur le contenu du manuel de l’APCUPSD («le manuel»)\nsans avoir au préalable obtenu l’avis du support technique APC.\nLe manuel est fourni sur les termes et comprendre que:
"},{"id":"text-3","type":"text","heading":"","plain_text":"les auteurs, contributeurs et éditeurs ne sont pas responsables de la\nles résultats des actions entreprises sur la base des informations contenues dans le manuel,\nni pour toute erreur ou omission dans le manuel; et\nles auteurs, contributeurs et éditeurs ne sont pas impliqués dans le rendu\nconseils ou services techniques ou autres.","html":"les auteurs, contributeurs et éditeurs ne sont pas responsables de la\nles résultats des actions entreprises sur la base des informations contenues dans le manuel,\nni pour toute erreur ou omission dans le manuel; et\nles auteurs, contributeurs et éditeurs ne sont pas impliqués dans le rendu\nconseils ou services techniques ou autres.
"},{"id":"text-4","type":"text","heading":"","plain_text":"Les auteurs, contributeurs et éditeurs, déclinent expressément tout et tout\nresponsabilité envers toute personne, que ce soit un lecteur du manuel\nou non, à l'égard de quoi que ce soit, et des conséquences de quoi que ce soit, fait ou\nomis par une telle personne en toute confiance, en tout ou en partie,\nsur tout ou partie du contenu du manuel. Sans limiter le\nla généralité de ce qui précède, aucun auteur, contributeur ou éditeur ne doit avoir\nresponsabilité pour tout acte ou omission de tout autre auteur, contributeur ou\néditeur.","html":"Les auteurs, contributeurs et éditeurs, déclinent expressément tout et tout\nresponsabilité envers toute personne, que ce soit un lecteur du manuel\nou non, à l'égard de quoi que ce soit, et des conséquences de quoi que ce soit, fait ou\nomis par une telle personne en toute confiance, en tout ou en partie,\nsur tout ou partie du contenu du manuel. Sans limiter le\nla généralité de ce qui précède, aucun auteur, contributeur ou éditeur ne doit avoir\nresponsabilité pour tout acte ou omission de tout autre auteur, contributeur ou\néditeur.
"},{"id":"text-5","type":"text","heading":"","plain_text":"Ceci est le manuel pour apcupsd, un\ndémon pour la communication avec les UPS (Uninterruptible Power\nFournitures) fabriquées par American Power Conversion Corporation (APC). Si vous avez un\nLes onduleurs fabriqués par APC, qu’ils soient vendus sous la plaque signalétique APC ou OEM (par exemple, le\nPowerTrust 2997A), et vous voulez le faire fonctionner avec un ordinateur en marche\nLinux, Unix ou Windows, vous lisez le bon document.\nCe manuel est divisé en parties qui augmentent en profondeur technique\ncomme ils vont. Si vous venez d'acheter un onduleur à la pointe de la technologie\navec une interface USB ou Ethernet, et vous exécutez un courant\nversion de Red Hat ou SUSE Linux, alors apcupsd est\npresque plug-and-play et vous devrez lire que le De base\nGuide de l'utilisateur.\nSi votre système d’exploitation est plus ancien ou si vous avez un système démodé\nl’onduleur série, vous devrez vous renseigner sur l’installation en série (voir\nInstallation: Onduleurs de ligne série). Si vous avez besoin de plus\ndes détails sur l’administration dans des situations inhabituelles (comme un\nconfiguration maître / esclave ou multi-UPS), vous devez lire les sections sur\nces sujets aussi. Finalement,\nil existe un certain nombre de sections de référence techniques qui\ndonne des détails complets sur des choses comme les directives de fichier de configuration et\nformats de journalisation des événements.\nVous devriez commencer par lire le guide de démarrage rapide (voir Démarrage rapide pour\nDébutants) instructions.","html":"Ceci est le manuel pour apcupsd, un\ndémon pour la communication avec les UPS (Uninterruptible Power\nFournitures) fabriquées par American Power Conversion Corporation (APC). Si vous avez un\nLes onduleurs fabriqués par APC, qu’ils soient vendus sous la plaque signalétique APC ou OEM (par exemple, le\nPowerTrust 2997A), et vous voulez le faire fonctionner avec un ordinateur en marche\nLinux, Unix ou Windows, vous lisez le bon document.\nCe manuel est divisé en parties qui augmentent en profondeur technique\ncomme ils vont. Si vous venez d'acheter un onduleur à la pointe de la technologie\navec une interface USB ou Ethernet, et vous exécutez un courant\nversion de Red Hat ou SUSE Linux, alors apcupsd est\npresque plug-and-play et vous devrez lire que le De base\nGuide de l'utilisateur.\nSi votre système d’exploitation est plus ancien ou si vous avez un système démodé\nl’onduleur série, vous devrez vous renseigner sur l’installation en série (voir\nInstallation: Onduleurs de ligne série). Si vous avez besoin de plus\ndes détails sur l’administration dans des situations inhabituelles (comme un\nconfiguration maître / esclave ou multi-UPS), vous devez lire les sections sur\nces sujets aussi. Finalement,\nil existe un certain nombre de sections de référence techniques qui\ndonne des détails complets sur des choses comme les directives de fichier de configuration et\nformats de journalisation des événements.\nVous devriez commencer par lire le guide de démarrage rapide (voir Démarrage rapide pour\nDébutants) instructions.
"},{"id":"text-6","type":"text","heading":"","plain_text":"Démarrage rapide pour les débutants\napcupsd est un logiciel complexe, mais\nla plupart de ses complexités sont destinées à traiter avec du matériel ancien\net systèmes d'exploitation. Obtention du matériel et des logiciels actuels\ncourir ne devrait pas être très compliqué.\nCe qui suit est un guide d’aide sur les étapes à suivre pour obtenir apcupsd\nmis en place et en cours d'exécution aussi indolore que possible.","html":"Démarrage rapide pour les débutants\napcupsd est un logiciel complexe, mais\nla plupart de ses complexités sont destinées à traiter avec du matériel ancien\net systèmes d'exploitation. Obtention du matériel et des logiciels actuels\ncourir ne devrait pas être très compliqué.\nCe qui suit est un guide d’aide sur les étapes à suivre pour obtenir apcupsd\nmis en place et en cours d'exécution aussi indolore que possible.
"},{"id":"text-7","type":"text","heading":"","plain_text":"Vérifiez si apcupsd prend en charge votre UPS et votre câble (voir\nUPS et câbles pris en charge).\nVérifiez si apcupsd prend en charge votre système d’exploitation (voir\nSystèmes d'exploitation pris en charge).\nPlanifiez votre type de configuration (voir Choisir une configuration\nType). Si vous avez juste un UPS et\nun ordinateur, c'est facile. Si vous avez plus d’une machine en cours de\ndesservi par le même UPS, ou par plus d’un UPS alimentant\nordinateurs qui sont sur le même réseau local, vous avez plus de choix\nfaire.\nDéterminez si vous avez l'une des configurations faciles. Si vous avez une clé USB\nUPS, et un système d'exploitation pris en charge et que vous souhaitez utiliser un UPS\navec un ordinateur, la configuration est simple. APC fournit le câble\nbesoin de parler avec cet UPS avec l'onduleur. Tout ce que vous devez faire\nvérifiez que votre sous-système USB fonctionne (voir USB\nConfiguration) si oui, vous pouvez aller à la construction\net installez l'étape.\nSi vous avez un onduleur conçu pour communiquer via SNMP via\nEthernet, c'est aussi une installation relativement facile. Détails\nsont fournis dans Assistance pour les onduleurs SNMP.\nSi vous avez un UPS qui communique via un port série RS232C\nl'interface et c'est un SmartUPS, alors les choses sont relativement simples,\nsinon, votre vie est sur le point de devenir intéressante.","html":"Vérifiez si apcupsd prend en charge votre UPS et votre câble (voir\nUPS et câbles pris en charge).\nVérifiez si apcupsd prend en charge votre système d’exploitation (voir\nSystèmes d'exploitation pris en charge).\nPlanifiez votre type de configuration (voir Choisir une configuration\nType). Si vous avez juste un UPS et\nun ordinateur, c'est facile. Si vous avez plus d’une machine en cours de\ndesservi par le même UPS, ou par plus d’un UPS alimentant\nordinateurs qui sont sur le même réseau local, vous avez plus de choix\nfaire.\nDéterminez si vous avez l'une des configurations faciles. Si vous avez une clé USB\nUPS, et un système d'exploitation pris en charge et que vous souhaitez utiliser un UPS\navec un ordinateur, la configuration est simple. APC fournit le câble\nbesoin de parler avec cet UPS avec l'onduleur. Tout ce que vous devez faire\nvérifiez que votre sous-système USB fonctionne (voir USB\nConfiguration) si oui, vous pouvez aller à la construction\net installez l'étape.\nSi vous avez un onduleur conçu pour communiquer via SNMP via\nEthernet, c'est aussi une installation relativement facile. Détails\nsont fournis dans Assistance pour les onduleurs SNMP.\nSi vous avez un UPS qui communique via un port série RS232C\nl'interface et c'est un SmartUPS, alors les choses sont relativement simples,\nsinon, votre vie est sur le point de devenir intéressante.
"},{"id":"text-8","type":"text","heading":"","plain_text":"Si vous avez un câble fourni par le fournisseur, déterminez quel type de câble\nvous avez un numéro sur les extrémités plates du câble,\ncomme le 940-0020A, estampé dans le plastique.\nSi vous n'avez pas de câble fourni par le fournisseur ou si votre type n'est pas\nvous devrez peut-être en construire un vous-même (voir\nCâbles). Voici en espérant que tu es bon avec une soudure\nle fer!","html":"Si vous avez un câble fourni par le fournisseur, déterminez quel type de câble\nvous avez un numéro sur les extrémités plates du câble,\ncomme le 940-0020A, estampé dans le plastique.\nSi vous n'avez pas de câble fourni par le fournisseur ou si votre type n'est pas\nvous devrez peut-être en construire un vous-même (voir\nCâbles). Voici en espérant que tu es bon avec une soudure\nle fer!
"},{"id":"text-9","type":"text","heading":"","plain_text":"Vous êtes maintenant prêt à lire le document Building and Install (voir\nConstruire et installer apcupsd)\nsection du manuel et suivez ces instructions. Si vous êtes\nl’installation à partir d’un RPM ou d’une autre forme de paquet binaire, cette\nL’étape consistera probablement à exécuter une seule commande.\nModifiez votre fichier /etc/apcupsd/apcupsd.conf si nécessaire. Souvent il\nne sera pas.\nModifiez les paramètres du BIOS (voir Organiser le redémarrage sur\nPower-Up) sur ton ordinateur\nde sorte que chaque démarrage, il démarre. (Ce n'est pas la valeur par défaut\nsur la plupart des systèmes.)\nPour vérifier que votre UPS communique avec votre ordinateur et\nva faire la bonne chose quand le courant est coupé, lire et suivre\nles instructions du test (voir Essai\nApcupsd) section.\nSi vous rencontrez des problèmes, consultez la liste de messagerie des utilisateurs d'apcupsd\narchive pour des problèmes similaires. C’est une excellente ressource avec\nréponses à toutes sortes de questions. Voir\nhttp://sourceforge.net/mailarchive/forum.php?forum_name=apcupsd-users.\nSi vous avez toujours besoin d'aide, envoyez un message au courrier électronique des utilisateurs d'apcupsd.\nliste (apcupsd-users@lists.sourceforge.net) décrivant votre\nproblème, quelle version de\napcupsd que vous utilisez, quel système d'exploitation vous utilisez et\ntout ce que vous pensez pourrait être utile.\nLisez la section du manuel sur la surveillance et le réglage de votre onduleur.","html":"Vous êtes maintenant prêt à lire le document Building and Install (voir\nConstruire et installer apcupsd)\nsection du manuel et suivez ces instructions. Si vous êtes\nl’installation à partir d’un RPM ou d’une autre forme de paquet binaire, cette\nL’étape consistera probablement à exécuter une seule commande.\nModifiez votre fichier /etc/apcupsd/apcupsd.conf si nécessaire. Souvent il\nne sera pas.\nModifiez les paramètres du BIOS (voir Organiser le redémarrage sur\nPower-Up) sur ton ordinateur\nde sorte que chaque démarrage, il démarre. (Ce n'est pas la valeur par défaut\nsur la plupart des systèmes.)\nPour vérifier que votre UPS communique avec votre ordinateur et\nva faire la bonne chose quand le courant est coupé, lire et suivre\nles instructions du test (voir Essai\nApcupsd) section.\nSi vous rencontrez des problèmes, consultez la liste de messagerie des utilisateurs d'apcupsd\narchive pour des problèmes similaires. C’est une excellente ressource avec\nréponses à toutes sortes de questions. Voir\nhttp://sourceforge.net/mailarchive/forum.php?forum_name=apcupsd-users.\nSi vous avez toujours besoin d'aide, envoyez un message au courrier électronique des utilisateurs d'apcupsd.\nliste (apcupsd-users@lists.sourceforge.net) décrivant votre\nproblème, quelle version de\napcupsd que vous utilisez, quel système d'exploitation vous utilisez et\ntout ce que vous pensez pourrait être utile.\nLisez la section du manuel sur la surveillance et le réglage de votre onduleur.
"},{"id":"text-10","type":"text","heading":"","plain_text":"Systèmes d'exploitation supportés\napcupsd prend en charge de nombreux systèmes d’exploitation de type UNIX, ainsi que plusieurs\nvariantes de Windows. En raison du manque de normalisation des API, la prise en charge USB n’est pas prise en charge.\ndisponible sur toutes les plateformes. Voir Support de la plateforme ci-dessous pour plus de détails.\nEn général, il est recommandé d’obtenir un paquet pré-construit pour votre plate-forme.\nCompte tenu de la manière dont apcupsd doit s’intégrer au mécanisme d’arrêt du\nsystème d’exploitation et la vitesse à laquelle ces mécanismes sont modifiés par\nfournisseurs, les ports de plate-forme de l’arborescence apcupsd peuvent devenir obsolètes. Dans\nDans certains cas, les paquets binaires sont fournis par l’équipe apcupsd (RedHat,\nMandriva, SuSE, Windows, Mac OS X). Pour les autres plateformes, il est recommandé de\nvérifier les référentiels de paquets de votre fournisseur et les référentiels tiers pour\npaquets binaires récents. Notez que certains fournisseurs continuent à distribuer\nanciennes versions de apcupsd avec des défauts connus. Ces paquets devraient ne pas être\nutilisé.","html":"Systèmes d'exploitation supportés\napcupsd prend en charge de nombreux systèmes d’exploitation de type UNIX, ainsi que plusieurs\nvariantes de Windows. En raison du manque de normalisation des API, la prise en charge USB n’est pas prise en charge.\ndisponible sur toutes les plateformes. Voir Support de la plateforme ci-dessous pour plus de détails.\nEn général, il est recommandé d’obtenir un paquet pré-construit pour votre plate-forme.\nCompte tenu de la manière dont apcupsd doit s’intégrer au mécanisme d’arrêt du\nsystème d’exploitation et la vitesse à laquelle ces mécanismes sont modifiés par\nfournisseurs, les ports de plate-forme de l’arborescence apcupsd peuvent devenir obsolètes. Dans\nDans certains cas, les paquets binaires sont fournis par l’équipe apcupsd (RedHat,\nMandriva, SuSE, Windows, Mac OS X). Pour les autres plateformes, il est recommandé de\nvérifier les référentiels de paquets de votre fournisseur et les référentiels tiers pour\npaquets binaires récents. Notez que certains fournisseurs continuent à distribuer\nanciennes versions de apcupsd avec des défauts connus. Ces paquets devraient ne pas être\nutilisé.
"},{"id":"text-11","type":"text","heading":"","plain_text":"Support de plate-forme\nLINUX","html":"Support de plate-forme\nLINUX
"},{"id":"text-12","type":"text","heading":"","plain_text":"Chapeau rouge \nSuSE \nMandriva / Mandrake \nDebian \nSlackware \nEngarde \nChien jaune \nGentoo","html":"Chapeau rouge \nSuSE \nMandriva / Mandrake \nDebian \nSlackware \nEngarde \nChien jaune \nGentoo
"},{"id":"text-13","type":"text","heading":"","plain_text":"LES FENÊTRES","html":"LES FENÊTRES
"},{"id":"text-14","type":"text","heading":"","plain_text":"Windows NT 4 \nWindows 98 / ME / 2000 \nWindows XP / Vista (y compris 64 bits) \nWindows Server 2003/2008 (64 bits inclus) \nWindows 7","html":"Windows NT 4 \nWindows 98 / ME / 2000 \nWindows XP / Vista (y compris 64 bits) \nWindows Server 2003/2008 (64 bits inclus) \nWindows 7
"},{"id":"text-15","type":"text","heading":"","plain_text":"AUTRES","html":"AUTRES
"},{"id":"text-16","type":"text","heading":"","plain_text":"Mac OS X Darwin \nSolaris 8/9 \nSolaris 10\nNetBSD\nFreeBSD\nOpenBSD\nHPUX \nUnifix \nQNX","html":"Mac OS X Darwin \nSolaris 8/9 \nSolaris 10\nNetBSD\nFreeBSD\nOpenBSD\nHPUX \nUnifix \nQNX
"},{"id":"text-17","type":"text","heading":"","plain_text":"UPS et câbles pris en charge\napcupsd prend en charge presque tous les modèles d'onduleurs APC existants et suffisamment\ndifférents types de câbles à connecter à chacun d’eux.\nle UPSTYPE le champ est la valeur que vous allez mettre en\nvotre fichier /etc/apcupsd/apcupsd.conf pour indiquer à apcupsd quel type d'onduleur\ntu as. Nous allons décrire les valeurs possibles ici, car ils sont\nun bon moyen d'expliquer l'interface la plus importante de votre UPS\npropriété: le type de protocole utilisé pour parler avec ses\nordinateur.","html":"UPS et câbles pris en charge\napcupsd prend en charge presque tous les modèles d'onduleurs APC existants et suffisamment\ndifférents types de câbles à connecter à chacun d’eux.\nle UPSTYPE le champ est la valeur que vous allez mettre en\nvotre fichier /etc/apcupsd/apcupsd.conf pour indiquer à apcupsd quel type d'onduleur\ntu as. Nous allons décrire les valeurs possibles ici, car ils sont\nun bon moyen d'expliquer l'interface la plus importante de votre UPS\npropriété: le type de protocole utilisé pour parler avec ses\nordinateur.
"},{"id":"text-18","type":"text","heading":"","plain_text":"apcsmart\nLe protocole 'apcsmart' utilise une connexion série RS232 pour passer\ncommandes dans un langage primitif ressemblant à\ncodes de contrôle du modem. APC appelle cette langue "UPS-Link". À l'origine\nintroduit pour les modèles Smart-UPS (d'où le nom «apcsmart»), cette\nla classe d'onduleurs est en déclin, elle est rapidement remplacée par le produit d'APC\nligne par UPS et MODBUS.\nUSB\nUn onduleur USB parle un contrôle universel bien défini\nla langue sur un fil USB. La plupart des membres d'APC utilisent maintenant cette méthode\nà la fin de 2003, et il semble probable qu’il prendra complètement le relais\nleur gamme basse et moyenne. Les derniers onduleurs APC ne prennent en charge qu’une\nensemble limité de données sur l'interface USB. MODBUS (voir ci-dessous) est requis\nafin d'accéder aux données avancées.\nnet\nC’est le mot clé pour spécifier si vous utilisez votre\nUPS en mode esclave (c’est-à-dire que la machine n’est pas directement connectée à\nl'onduleur, mais à une autre machine qui est), et il est connecté à\nle maître via une connexion ethernet. Vous devez avoir apcupsd's\nNetwork Information Services NIS activé pour que ce mode fonctionne.\nsnmp\nLes onduleurs SNMP communiquent via une carte réseau Ethernet et\nfirmware qui parle Simple Network Management Protocol.\nstupide\nUn onduleur muet ou à signalisation de tension et son ordinateur\ncommuniquer via les lignes de contrôle (pas les lignes de données) sur un RS232C\nconnexion série. Pas grand-chose ne peut être réellement transmis de cette façon autre que\nun ordre de fermeture. Les UPS de signalisation de tension sont obsolètes. toi\nsont peu susceptibles de rencontrer un autre que comme matériel hérité. Si vous\nSi vous avez le choix, nous vous recommandons d’éviter les simples UPS de signalisation.\npcnet\nPCNET est une alternative au SNMP disponible sur APC\nFamille AP9617 de modules de logement intelligent. Le protocole est beaucoup plus simple\net potentiellement plus sécurisé que SNMP.\nmodbus\nMODBUS est le dernier protocole APC et fonctionne sur des liaisons série RS232 ou\nUSB. MODBUS est le remplacement d'APC pour le 'apcsmart' (UPS-Link)\nprotocole. MODBUS est le seul moyen d'accéder à un contrôle et à un statut détaillés\ninformations sur les onduleurs les plus récents (en particulier ceux de la série SMT).","html":"apcsmart\nLe protocole 'apcsmart' utilise une connexion série RS232 pour passer\ncommandes dans un langage primitif ressemblant à\ncodes de contrôle du modem. APC appelle cette langue "UPS-Link". À l'origine\nintroduit pour les modèles Smart-UPS (d'où le nom «apcsmart»), cette\nla classe d'onduleurs est en déclin, elle est rapidement remplacée par le produit d'APC\nligne par UPS et MODBUS.\nUSB\nUn onduleur USB parle un contrôle universel bien défini\nla langue sur un fil USB. La plupart des membres d'APC utilisent maintenant cette méthode\nà la fin de 2003, et il semble probable qu’il prendra complètement le relais\nleur gamme basse et moyenne. Les derniers onduleurs APC ne prennent en charge qu’une\nensemble limité de données sur l'interface USB. MODBUS (voir ci-dessous) est requis\nafin d'accéder aux données avancées.\nnet\nC’est le mot clé pour spécifier si vous utilisez votre\nUPS en mode esclave (c’est-à-dire que la machine n’est pas directement connectée à\nl'onduleur, mais à une autre machine qui est), et il est connecté à\nle maître via une connexion ethernet. Vous devez avoir apcupsd's\nNetwork Information Services NIS activé pour que ce mode fonctionne.\nsnmp\nLes onduleurs SNMP communiquent via une carte réseau Ethernet et\nfirmware qui parle Simple Network Management Protocol.\nstupide\nUn onduleur muet ou à signalisation de tension et son ordinateur\ncommuniquer via les lignes de contrôle (pas les lignes de données) sur un RS232C\nconnexion série. Pas grand-chose ne peut être réellement transmis de cette façon autre que\nun ordre de fermeture. Les UPS de signalisation de tension sont obsolètes. toi\nsont peu susceptibles de rencontrer un autre que comme matériel hérité. Si vous\nSi vous avez le choix, nous vous recommandons d’éviter les simples UPS de signalisation.\npcnet\nPCNET est une alternative au SNMP disponible sur APC\nFamille AP9617 de modules de logement intelligent. Le protocole est beaucoup plus simple\net potentiellement plus sécurisé que SNMP.\nmodbus\nMODBUS est le dernier protocole APC et fonctionne sur des liaisons série RS232 ou\nUSB. MODBUS est le remplacement d'APC pour le 'apcsmart' (UPS-Link)\nprotocole. MODBUS est le seul moyen d'accéder à un contrôle et à un statut détaillés\ninformations sur les onduleurs les plus récents (en particulier ceux de la série SMT).
"},{"id":"text-19","type":"text","heading":"","plain_text":"Choisir un type de configuration\nIl y a trois principaux\nmanières de faire fonctionner apcupsd sur votre système. Le premier est un autonome\nconfiguration où apcupsd contrôle un seul onduleur, qui alimente un\nordinateur unique. C'est la configuration la plus courante. Si vous êtes\ntravaillant avec une seule machine et un onduleur, ignorez le reste de cette\nsection.\nVos choix deviennent plus intéressants si vous utilisez un petit\ncluster ou une grande batterie de serveurs. Dans ces circonstances, il se peut que\nêtre possible ou même souhaitable de coupler un onduleur à chaque\nmachine. apcupsd prend en charge certains arrangements alternatifs.\nLe second type de configuration est le NIS (Network Information Information Network).\nServeur) serveur et client. Dans cette configuration, où un UPS\nalimente plusieurs ordinateurs, une copie d’apcupsd en exécutant un\nl'ordinateur agira en tant que serveur, tandis que les autres agiront en tant que\nclients du réseau qui interrogent le serveur pour obtenir des informations sur la\nUPS. Notez que "NIS" est ne pas liés au service d'annuaire de Sun\négalement appelé "NIS" ou "Pages Jaunes".\nLa troisième configuration est celle où un seul\nl'ordinateur contrôle plusieurs UPS. Dans ce cas, il y a plusieurs\ncas d’apcupsd sur le même ordinateur, chacun contrôlant un\ndifférent UPS. Une instance d’apcupsd s’exécutera en mode autonome, et\nl'autre instance fonctionnera normalement en mode réseau.\nCe type de configuration peut convenir aux gros serveurs\nexploitations utilisant une seule machine dédiée à la surveillance et à\nDiagnostique\nVoici un schéma qui résume les possibilités:","html":"Choisir un type de configuration\nIl y a trois principaux\nmanières de faire fonctionner apcupsd sur votre système. Le premier est un autonome\nconfiguration où apcupsd contrôle un seul onduleur, qui alimente un\nordinateur unique. C'est la configuration la plus courante. Si vous êtes\ntravaillant avec une seule machine et un onduleur, ignorez le reste de cette\nsection.\nVos choix deviennent plus intéressants si vous utilisez un petit\ncluster ou une grande batterie de serveurs. Dans ces circonstances, il se peut que\nêtre possible ou même souhaitable de coupler un onduleur à chaque\nmachine. apcupsd prend en charge certains arrangements alternatifs.\nLe second type de configuration est le NIS (Network Information Information Network).\nServeur) serveur et client. Dans cette configuration, où un UPS\nalimente plusieurs ordinateurs, une copie d’apcupsd en exécutant un\nl'ordinateur agira en tant que serveur, tandis que les autres agiront en tant que\nclients du réseau qui interrogent le serveur pour obtenir des informations sur la\nUPS. Notez que "NIS" est ne pas liés au service d'annuaire de Sun\négalement appelé "NIS" ou "Pages Jaunes".\nLa troisième configuration est celle où un seul\nl'ordinateur contrôle plusieurs UPS. Dans ce cas, il y a plusieurs\ncas d’apcupsd sur le même ordinateur, chacun contrôlant un\ndifférent UPS. Une instance d’apcupsd s’exécutera en mode autonome, et\nl'autre instance fonctionnera normalement en mode réseau.\nCe type de configuration peut convenir aux gros serveurs\nexploitations utilisant une seule machine dédiée à la surveillance et à\nDiagnostique\nVoici un schéma qui résume les possibilités:
"},{"id":"text-20","type":"text","heading":"","plain_text":"Types de configuration\n----------*----R4----*----< TxD (3)\n |\n | 1N4148\n *----K|---------< RTS (7) Shutdown","html":"Types de configuration\n----------*----R4----*----< TxD (3)\n |\n | 1N4148\n *----K|---------< RTS (7) Shutdown
"},{"id":"text-21","type":"text","heading":"","plain_text":"POWER-FAIL (2) >--------------------------< RxD,RI (2,9) On Batt","html":"POWER-FAIL (2) >--------------------------< RxD,RI (2,9) On Batt
"},{"id":"text-22","type":"text","heading":"","plain_text":"GROUND (4,9) >--------------------------< GND (5)","html":"GROUND (4,9) >--------------------------< GND (5)
"},{"id":"text-23","type":"text","heading":"","plain_text":"Operation:","html":"Operation:
"},{"id":"text-24","type":"text","heading":"","plain_text":"DTR is "cable power" and must be held at SPACE. DSR or CTS may\nbe used as a loopback input to determine if the cable is plugged\ndans.","html":"DTR is "cable power" and must be held at SPACE. DSR or CTS may\nbe used as a loopback input to determine if the cable is plugged\ndans.
"},{"id":"text-25","type":"text","heading":"","plain_text":"DCD is the "battery low" signal to the computer. A SPACE on this\nline means the battery is low. This is signalled by BATTERY-LOW\nbeing pulled down (it is probably open circuit normally).\nNormally, the transistor is turned off, and DCD is held at the MARK\nvoltage by TxD. When BATTERY-LOW is pulled down, the voltage\ndivider R2/R1 biases the transistor so that it is turned on,\ncausing DCD to be pulled up to the SPACE voltage.","html":"DCD is the "battery low" signal to the computer. A SPACE on this\nline means the battery is low. This is signalled by BATTERY-LOW\nbeing pulled down (it is probably open circuit normally).\nNormally, the transistor is turned off, and DCD is held at the MARK\nvoltage by TxD. When BATTERY-LOW is pulled down, the voltage\ndivider R2/R1 biases the transistor so that it is turned on,\ncausing DCD to be pulled up to the SPACE voltage.
"},{"id":"text-26","type":"text","heading":"","plain_text":"TxD must be held at MARK; this is the default state when no data\nis being transmitted. This sets the default bias for both DCD and\nSHUTDOWN. If this line is an open circuit, then when BATTERY-LOW is\nsignalled, SHUTDOWN will be automatically signalled; this would be\ntrue if the cable were plugged in to the UPS and not the computer,\nor if the computer were turned off.","html":"TxD must be held at MARK; this is the default state when no data\nis being transmitted. This sets the default bias for both DCD and\nSHUTDOWN. If this line is an open circuit, then when BATTERY-LOW is\nsignalled, SHUTDOWN will be automatically signalled; this would be\ntrue if the cable were plugged in to the UPS and not the computer,\nor if the computer were turned off.
"},{"id":"text-27","type":"text","heading":"","plain_text":"RTS is the "shutdown" signal from the computer. A SPACE on this\nline tells the UPS to shut down.","html":"RTS is the "shutdown" signal from the computer. A SPACE on this\nline tells the UPS to shut down.
"},{"id":"text-28","type":"text","heading":"","plain_text":"RxD and RI are both the "power-fail" signals to the computer. UNE\nMARK on this line means the power has failed.","html":"RxD and RI are both the "power-fail" signals to the computer. UNE\nMARK on this line means the power has failed.
"},{"id":"text-29","type":"text","heading":"","plain_text":"SPACE is a positive voltage, typically +12V. MARK is a negative\nvoltage, typically -12V. Linux appears to translate SPACE to a 1\nand MARK to a 0.","html":"SPACE is a positive voltage, typically +12V. MARK is a negative\nvoltage, typically -12V. Linux appears to translate SPACE to a 1\nand MARK to a 0.
"},{"id":"text-30","type":"text","heading":"","plain_text":"940-0095B Cable Wiring","html":"940-0095B Cable Wiring
"},{"id":"text-31","type":"text","heading":"","plain_text":"Supported Models:\nMany simple-signaling (aka voltage signaling)\nmodels such as BackUPS","html":"Supported Models:\nMany simple-signaling (aka voltage signaling)\nmodels such as BackUPS
"},{"id":"text-32","type":"text","heading":"","plain_text":"This diagram is for informational purposes and may not be complete.\nWe don't recommend that use it to build you build one yourself.","html":"This diagram is for informational purposes and may not be complete.\nWe don't recommend that use it to build you build one yourself.
"},{"id":"text-33","type":"text","heading":"","plain_text":"APC Part# - 940-0095B","html":"APC Part# - 940-0095B
"},{"id":"text-34","type":"text","heading":"","plain_text":"Signal Computer UPS\n DB9F DB9M\n DTR 4 ----*\n CTS 8 ----|\n DSR 6 ----|\n DCD 1 ----*\n GND 5 ---------------*---- 4 Ground\n |\n *---- 9 Common\n RI 9 ----*\n |\n RxD 2 ----*--------------- 2 On Battery\n TxD 3 ----------[####]---- 1 Kill UPS Power\n 4.7K ohm","html":"Signal Computer UPS\n DB9F DB9M\n DTR 4 ----*\n CTS 8 ----|\n DSR 6 ----|\n DCD 1 ----*\n GND 5 ---------------*---- 4 Ground\n |\n *---- 9 Common\n RI 9 ----*\n |\n RxD 2 ----*--------------- 2 On Battery\n TxD 3 ----------[####]---- 1 Kill UPS Power\n 4.7K ohm
"},{"id":"text-35","type":"text","heading":"","plain_text":"940-0119A Cable Wiring","html":"940-0119A Cable Wiring
"},{"id":"text-36","type":"text","heading":"","plain_text":"Supported Models:\nOlder BackUPS Office","html":"Supported Models:\nOlder BackUPS Office
"},{"id":"text-37","type":"text","heading":"","plain_text":"This diagram is for informational purposes and may not be complete.\nWe don't recommend that use it to build you build one yourself.","html":"This diagram is for informational purposes and may not be complete.\nWe don't recommend that use it to build you build one yourself.
"},{"id":"text-38","type":"text","heading":"","plain_text":"APC Part# - 940-0119A","html":"APC Part# - 940-0119A
"},{"id":"text-39","type":"text","heading":"","plain_text":" UPS Computer\n pins pins Signal Signal meaning\n1 (brown) 4,6 DSR DTR On battery power\n3 (blue) 1,2 CD RxD -> Low battery\n4 (red) 5 Ground\n5 (yellow) 7 RTS <- Begin signalling on other pins\n6 (none) none","html":"UPS Computer\n pins pins Signal Signal meaning\n1 (brown) 4,6 DSR DTR On battery power\n3 (blue) 1,2 CD RxD -> Low battery\n4 (red) 5 Ground\n5 (yellow) 7 RTS <- Begin signalling on other pins\n6 (none) none
"},{"id":"text-40","type":"text","heading":"","plain_text":"Serial BackUPS ES Wiring","html":"Serial BackUPS ES Wiring
"},{"id":"text-41","type":"text","heading":"","plain_text":"Supported Models:\nOlder Serial BackUPS ES","html":"Supported Models:\nOlder Serial BackUPS ES
"},{"id":"text-42","type":"text","heading":"","plain_text":"Contributed by:\nWilliam Stock","html":"Contributed by:\nWilliam Stock
"},{"id":"text-43","type":"text","heading":"","plain_text":"The BackUPS ES has a straight through serial cable with no\nidentification on the plugs. To make it work with apcupsd, specify\nthe UPSCABLE 940-0119A and UPSTYPE backups. The equivalent of\ncable 940-0119A is done on a PCB inside the unit.","html":"The BackUPS ES has a straight through serial cable with no\nidentification on the plugs. To make it work with apcupsd, specify\nthe UPSCABLE 940-0119A and UPSTYPE backups. The equivalent of\ncable 940-0119A is done on a PCB inside the unit.
"},{"id":"text-44","type":"text","heading":"","plain_text":"computer ----------- BackUPS-ES -----------------\nDB9-M DB-9F\npin signal pin","html":"computer ----------- BackUPS-ES -----------------\nDB9-M DB-9F\npin signal pin
"},{"id":"text-45","type":"text","heading":"","plain_text":" 4 DSR -> 4 --+\n | diode resistor\n 6 DTR -> 6 --+---->|----///---o kill power","html":"4 DSR -> 4 --+\n | diode resistor\n 6 DTR -> 6 --+---->|----///---o kill power
"},{"id":"text-46","type":"text","heading":"","plain_text":" 1 DCD <- 1 --+\n |\n 2 RxD 7 --------+--///--+\n |\n +--///--+\n |\n 8 RI <- 8 --+----------------+--o on battery\n |\n 9 CTS <- 9 --+","html":"1 DCD <- 1 --+\n |\n 2 RxD 7 --------+--///--+\n |\n +--///--+\n |\n 8 RI <- 8 --+----------------+--o on battery\n |\n 9 CTS <- 9 --+
"},{"id":"text-47","type":"text","heading":"","plain_text":" 5 GND --- 5 ----------------------o ground","html":"5 GND --- 5 ----------------------o ground
"},{"id":"text-48","type":"text","heading":"","plain_text":" 3 TxD 3 nc","html":"3 TxD 3 nc
"},{"id":"text-49","type":"text","heading":"","plain_text":"940-0128A Cable Wiring","html":"940-0128A Cable Wiring
"},{"id":"text-50","type":"text","heading":"","plain_text":"Supported Models:\nOlder USB BackUPS ES and CS","html":"Supported Models:\nOlder USB BackUPS ES and CS
"},{"id":"text-51","type":"text","heading":"","plain_text":"Contributed by:\nMany, thanks to all for your help!","html":"Contributed by:\nMany, thanks to all for your help!
"},{"id":"text-52","type":"text","heading":"","plain_text":"Though these UPSes are USB UPSes, APC supplies a serial cable\n(typically with a green DB9 F connector) that has 940-0128A stamped\ninto one side of the plastic serial port connector. The other end\nof the cable is a 10 pin RJ45 connector that plugs into the UPS\n(thanks to Dean Waldow for sending a cable!). Apcupsd version 3.8.5\nand later supports this cable when specified as UPSCABLE\n940-0128A and UPSTYPE dumb. However, running in this mode much\nof the information that would be available in USB mode is lost. Dans\naddition, when apcupsd attempts to instruct the UPS to kill the\npower, it begins cycling about 4 times a second between battery and\nline. The solution to the problem (thanks to Tom Suzda) is to\nunplug the UPS and while it is still chattering, press the power\nbutton (on the front of the unit) until the unit beeps and the\nchattering stops. After that the UPS should behave normally and\npower down 1-2 minutes after requested to do so.\nThanks to all the people who have helped test this and have\nprovided information on the cable wiring, our best guess for the\ncable schematic is the following:","html":"Though these UPSes are USB UPSes, APC supplies a serial cable\n(typically with a green DB9 F connector) that has 940-0128A stamped\ninto one side of the plastic serial port connector. The other end\nof the cable is a 10 pin RJ45 connector that plugs into the UPS\n(thanks to Dean Waldow for sending a cable!). Apcupsd version 3.8.5\nand later supports this cable when specified as UPSCABLE\n940-0128A and UPSTYPE dumb. However, running in this mode much\nof the information that would be available in USB mode is lost. Dans\naddition, when apcupsd attempts to instruct the UPS to kill the\npower, it begins cycling about 4 times a second between battery and\nline. The solution to the problem (thanks to Tom Suzda) is to\nunplug the UPS and while it is still chattering, press the power\nbutton (on the front of the unit) until the unit beeps and the\nchattering stops. After that the UPS should behave normally and\npower down 1-2 minutes after requested to do so.\nThanks to all the people who have helped test this and have\nprovided information on the cable wiring, our best guess for the\ncable schematic is the following:
"},{"id":"text-53","type":"text","heading":"","plain_text":"APC Part# - 940-0128A","html":"APC Part# - 940-0128A
"},{"id":"text-54","type":"text","heading":"","plain_text":"computer --------- Inside the Connector--------- UPS\nDB9-F | | RJ45\npin - signal | | Pin - Color\n | |\n 4 DSR ->|---+ |\n | | diode resistor |\n 6 DTR ->|---+---->|----///---o kill power | 8 Orange\n | |\n 1 DCD <-|----+ |\n | | |\n 2 RxD |----------+--///--+ |\n | | |\n | +--///--+ |\n | | |\n 8 RI <-|----+----------------+--o on battery | 2 Black\n | | |\n 9 CTS <-|----+ |\n | signal |\n 5 GND --|-----------------------o ground | 7 Red\n | |\n 3 TxD | |\n | chassis |\n Chassis/GND |-----------------------o ground | 4 Black\n | |\n | Not connected | 1, 5, 6, 9, 10\n --------------------------------------","html":"computer --------- Inside the Connector--------- UPS\nDB9-F | | RJ45\npin - signal | | Pin - Color\n | |\n 4 DSR ->|---+ |\n | | diode resistor |\n 6 DTR ->|---+---->|----///---o kill power | 8 Orange\n | |\n 1 DCD <-|----+ |\n | | |\n 2 RxD |----------+--///--+ |\n | | |\n | +--///--+ |\n | | |\n 8 RI <-|----+----------------+--o on battery | 2 Black\n | | |\n 9 CTS <-|----+ |\n | signal |\n 5 GND --|-----------------------o ground | 7 Red\n | |\n 3 TxD | |\n | chassis |\n Chassis/GND |-----------------------o ground | 4 Black\n | |\n | Not connected | 1, 5, 6, 9, 10\n --------------------------------------
"},{"id":"text-55","type":"text","heading":"","plain_text":"The RJ45 pins are: looking at the end of the connector:","html":"The RJ45 pins are: looking at the end of the connector:
"},{"id":"text-56","type":"text","heading":"","plain_text":"10 9 8 7 6 5 4 3 2 1\n_______________________\n| . . . . . . . . . . |\n| |\n-----------------------\n |____|","html":"10 9 8 7 6 5 4 3 2 1\n_______________________\n| . . . . . . . . . . |\n| |\n-----------------------\n |____|
"},{"id":"text-57","type":"text","heading":"","plain_text":"940-0128D Cable Wiring","html":"940-0128D Cable Wiring
"},{"id":"text-58","type":"text","heading":"","plain_text":"Supported Models:\nBackUPS XS1000(BX-1000), Possibly other USB models","html":"Supported Models:\nBackUPS XS1000(BX-1000), Possibly other USB models
"},{"id":"text-59","type":"text","heading":"","plain_text":"Contributed by:\nJan Babinski jbabinsk at pulsarbeacon dot com","html":"Contributed by:\nJan Babinski jbabinsk at pulsarbeacon dot com
"},{"id":"text-60","type":"text","heading":"","plain_text":"940-0128D is functionally similar to the 940-0128A cable except for\nNC on (6) DTR and (2) RD on the computer side.\nUnverified: Try setting apcupsd to UPSTYPE dumb et UPSCABLE 940-0128A.","html":"940-0128D is functionally similar to the 940-0128A cable except for\nNC on (6) DTR and (2) RD on the computer side.\nUnverified: Try setting apcupsd to UPSTYPE dumb et UPSCABLE 940-0128A.
"},{"id":"text-61","type":"text","heading":"","plain_text":"APC Part# - 940-0128D","html":"APC Part# - 940-0128D
"},{"id":"text-62","type":"text","heading":"","plain_text":"DB9(Computer) RJ45-10(UPS)","html":"DB9(Computer) RJ45-10(UPS)
"},{"id":"text-63","type":"text","heading":"","plain_text":" (5) (1) ____________\n( o o o o o ) [ oooooooooo ]\n o o o o / [____________]\n (9) (6) (10) [_] (1)","html":"(5) (1) ____________\n( o o o o o ) [ oooooooooo ]\n o o o o / [____________]\n (9) (6) (10) [_] (1)
"},{"id":"text-64","type":"text","heading":"","plain_text":" RI(9)<---+\n |\nCTS(8)|---------| 2k 1N5819\n +---vvvv---+--[>|------<(3)LowBatt\n | |\n +--- C |\n |___|\n /| B\nDCD(1)-------------------------->(8)KillPwr","html":"RI(9)<---+\n |\nCTS(8)|---------| 2k 1N5819\n +---vvvv---+--[>|------<(3)LowBatt\n | |\n +--- C |\n |___|\n /| B\nDCD(1)-------------------------->(8)KillPwr
"},{"id":"text-65","type":"text","heading":"","plain_text":"GND(5)----------------------------(7)Signal GND\n(Shield)--------------------------(4)Chassis GND","html":"GND(5)----------------------------(7)Signal GND\n(Shield)--------------------------(4)Chassis GND
"},{"id":"text-66","type":"text","heading":"","plain_text":"940-0127B Cable Wiring","html":"940-0127B Cable Wiring
"},{"id":"text-67","type":"text","heading":"","plain_text":"Supported Models:\nBackUPS XS1000(BX-1000), Possibly other USB models","html":"Supported Models:\nBackUPS XS1000(BX-1000), Possibly other USB models
"},{"id":"text-68","type":"text","heading":"","plain_text":"Contributed by:\nJan Babinski jbabinsk at pulsarbeacon dot com","html":"Contributed by:\nJan Babinski jbabinsk at pulsarbeacon dot com
"},{"id":"text-69","type":"text","heading":"","plain_text":"Standard USB cable for USB-capable models with 10-pin RJ45 connector.","html":"Standard USB cable for USB-capable models with 10-pin RJ45 connector.
"},{"id":"text-70","type":"text","heading":"","plain_text":"APC Part# - 940-0127B","html":"APC Part# - 940-0127B
"},{"id":"text-71","type":"text","heading":"","plain_text":"USB(Computer) RJ45-10(UPS)\n _________ ____________\n| = = = = | [ oooooooooo ]\n|_________| [____________]\n (1) (4) (10) [_] (1)","html":"USB(Computer) RJ45-10(UPS)\n _________ ____________\n| = = = = | [ oooooooooo ]\n|_________| [____________]\n (1) (4) (10) [_] (1)
"},{"id":"text-72","type":"text","heading":"","plain_text":" +5V(1)-----------(1)+5V\nDATA+(2)-----------(9)DATA+\nDATA-(3)-----------(10)DATA-\n GND(4)-----------(7)Signal GND\n(Shield)-----------(4)Chassis GRND","html":"+5V(1)-----------(1)+5V\nDATA+(2)-----------(9)DATA+\nDATA-(3)-----------(10)DATA-\n GND(4)-----------(7)Signal GND\n(Shield)-----------(4)Chassis GRND
"},{"id":"text-73","type":"text","heading":"","plain_text":"Win32 Implementation Restrictions for Simple UPSes\nDue to inadequacies in the\nWin32 API, it is not possible to set/clear/get all the serial port\nline signals. apcupsd can detect: CTS, DSR, RNG, and CD. It can set\nand clear: RTS and DTR.\nThis imposes a few minor restrictions on the functionality of some\nof the cables. In particular, LineDown on the Custom Simple cable,\nand Low Battery on the 0023A cable are not implemented.","html":"Win32 Implementation Restrictions for Simple UPSes\nDue to inadequacies in the\nWin32 API, it is not possible to set/clear/get all the serial port\nline signals. apcupsd can detect: CTS, DSR, RNG, and CD. It can set\nand clear: RTS and DTR.\nThis imposes a few minor restrictions on the functionality of some\nof the cables. In particular, LineDown on the Custom Simple cable,\nand Low Battery on the 0023A cable are not implemented.
"},{"id":"text-74","type":"text","heading":"","plain_text":"Note: In a future release of apcupsd this procedure will be\nreplaced by a daemon operation that can be performed on all types\nof UPS.\nThis section does not apply to voltage-signalling or dumb UPSes\nsuch as the older BackUPS models.\nSmart UPSes internally compute the remaining runtime, and apcupsd\nuses the value supplied by the UPS. As the batteries age (after say\ntwo or three years), the runtime computation may no longer be\naccurate since the batteries no longer hold the same charge. As a\nconsequence, in the event of a power failure, the UPS and thus\napcupsd can report a runtime of 5 minutes remaining when in fact\nonly one minute remains. This can lead to a shutdown before you\nmight expect it, because regardless of the runtime remaining that\nis reported, the UPS will always correctly detect low batteries and\nreport it, thus causing apcupsd to correctly shutdown your\ncomputer.\nIf you wish to have the UPS recalibrate the remaining runtime\ncalculations, you can do so manually as the current version of\napcupsd does not support this feature. To do so,","html":"Note: In a future release of apcupsd this procedure will be\nreplaced by a daemon operation that can be performed on all types\nof UPS.\nThis section does not apply to voltage-signalling or dumb UPSes\nsuch as the older BackUPS models.\nSmart UPSes internally compute the remaining runtime, and apcupsd\nuses the value supplied by the UPS. As the batteries age (after say\ntwo or three years), the runtime computation may no longer be\naccurate since the batteries no longer hold the same charge. As a\nconsequence, in the event of a power failure, the UPS and thus\napcupsd can report a runtime of 5 minutes remaining when in fact\nonly one minute remains. This can lead to a shutdown before you\nmight expect it, because regardless of the runtime remaining that\nis reported, the UPS will always correctly detect low batteries and\nreport it, thus causing apcupsd to correctly shutdown your\ncomputer.\nIf you wish to have the UPS recalibrate the remaining runtime\ncalculations, you can do so manually as the current version of\napcupsd does not support this feature. To do so,
"},{"id":"text-75","type":"text","heading":"","plain_text":"Shutdown apcupsd\ncontact your UPS directly using some terminal program such as\nminicom, tip, or cu with the settings 2400 8N1 (2400 baud, 8 bits,\nno parity, 1 stop bit). Be extremely careful what you send to your\nUPS as certain characters may cause it to power down or may even\ncause damage to the UPS. Try sending an upper case Y to the UPS\n(without a return at the end). It should respond with SM. If this\nis not the case, read the chapter on testing. If you fat finger the\nY and enter y instead, no cause for alarm, you will simply get the\nAPC copyright notice.\nwhen you are sure you are properly connected send an upper case\nD (no cr). This will put the UPS into calibration mode, and it will\ndrain the battery down to 25% capacity (35% for a Matrix) at which\npoint it will go back on the mains. In doing so, it will recompute\nthe runtime calibration.\nIf you wish to abort the calibration, enter a second D command.\nWhen you are done, restart apcupsd.","html":"Shutdown apcupsd\ncontact your UPS directly using some terminal program such as\nminicom, tip, or cu with the settings 2400 8N1 (2400 baud, 8 bits,\nno parity, 1 stop bit). Be extremely careful what you send to your\nUPS as certain characters may cause it to power down or may even\ncause damage to the UPS. Try sending an upper case Y to the UPS\n(without a return at the end). It should respond with SM. If this\nis not the case, read the chapter on testing. If you fat finger the\nY and enter y instead, no cause for alarm, you will simply get the\nAPC copyright notice.\nwhen you are sure you are properly connected send an upper case\nD (no cr). This will put the UPS into calibration mode, and it will\ndrain the battery down to 25% capacity (35% for a Matrix) at which\npoint it will go back on the mains. In doing so, it will recompute\nthe runtime calibration.\nIf you wish to abort the calibration, enter a second D command.\nWhen you are done, restart apcupsd.
"},{"id":"text-76","type":"text","heading":"","plain_text":"In principle, you should be able to do this with the computer\npowered by the UPS, but if you wish to be completely safe, you\nshould plug your computer into the wall prior to performing the\nruntime calibration. In that case, you will need to artificially\nload the UPS with light bulbs or other means. You should supply a\nload of about 30 to 35% but not more than 50%. You can determine\nthe load by looking at the output of the apcaccess status\ncommand while apcupsd is running.\nYou should not run the recalibration command more than once or\ntwice per year as discharging these kinds of batteries tends to\nshorten their life span.","html":"In principle, you should be able to do this with the computer\npowered by the UPS, but if you wish to be completely safe, you\nshould plug your computer into the wall prior to performing the\nruntime calibration. In that case, you will need to artificially\nload the UPS with light bulbs or other means. You should supply a\nload of about 30 to 35% but not more than 50%. You can determine\nthe load by looking at the output of the apcaccess status\ncommand while apcupsd is running.\nYou should not run the recalibration command more than once or\ntwice per year as discharging these kinds of batteries tends to\nshorten their life span.
"},{"id":"text-77","type":"text","heading":"","plain_text":"There is a good deal of information available about the UPS and apcupsd's\nstatut. This document describes the format of that information.\nNormally you will get at it via apcaccess, but there are other ways\nainsi que.","html":"There is a good deal of information available about the UPS and apcupsd's\nstatut. This document describes the format of that information.\nNormally you will get at it via apcaccess, but there are other ways\nainsi que.
"},{"id":"text-78","type":"text","heading":"","plain_text":"Status report format\nSTATUS output is in ASCII format with a single data value or piece\nof information on each line output. Because not all UPSes supply\nthe same information, the output varies based on the type of UPS\nthat you are using. In general, if the information is not available\nfor your UPS, the line will be missing entirely or the data portion of\nthe output record will contain an N / A indicating that the information\nis not available.\nStatus logging consists of periodically logging ALL available\ninformation concerning the UPS. Since the volume of data is rather\nlarge (over 1000 bytes per status), the STATUS data is not\nautomatically sent to the system log file. Instead, it is written\nas a series of data records in a specific file (normally\n/etc/apcupsd/apcupsd.status).\nAfter each write, the file is rewound so that the size of the file\nremains constant. The STATUS file is kept for backward compatibility\nand will be eliminated in a future version of apcupsd. The preferred\nmethod for obtaining this information is from apcaccess or by using\nthe CGI interface (see apcupsd Network Monitoring (CGI) Programs).\nTo make reading the status data reliable via a named pipe, the\nfirst record written contains a version number, the number of\nrecords that follow the first record, and the total number of bytes\nin those subsequent records. An actual example of such a status\nfile (/etc/apcupsd/apcupsd.status) is shown below.\nConsequently, the first record always consists of 24 bytes (23\ncharacters followed by a newline). This record starts with APC and\nas indicated in the example is followed by 37 records\nconsisting of 906 bytes. The last record begins with END APC and\ncontains the date and time matching the DATE record.\nWhen this data is written to a file, it is written as two records,\nthe first record, and all the other records together. In reading\nthe file, it can be either be read a record at a time, or in one\nbig read.\nWhen this data is written to syslog(), it is written a record at a\ntemps. The first record is the first 24 bytes. By having the number\nof records and the size in the first record, the complete status\ncan be reliably reassembled.","html":"Status report format\nSTATUS output is in ASCII format with a single data value or piece\nof information on each line output. Because not all UPSes supply\nthe same information, the output varies based on the type of UPS\nthat you are using. In general, if the information is not available\nfor your UPS, the line will be missing entirely or the data portion of\nthe output record will contain an N / A indicating that the information\nis not available.\nStatus logging consists of periodically logging ALL available\ninformation concerning the UPS. Since the volume of data is rather\nlarge (over 1000 bytes per status), the STATUS data is not\nautomatically sent to the system log file. Instead, it is written\nas a series of data records in a specific file (normally\n/etc/apcupsd/apcupsd.status).\nAfter each write, the file is rewound so that the size of the file\nremains constant. The STATUS file is kept for backward compatibility\nand will be eliminated in a future version of apcupsd. The preferred\nmethod for obtaining this information is from apcaccess or by using\nthe CGI interface (see apcupsd Network Monitoring (CGI) Programs).\nTo make reading the status data reliable via a named pipe, the\nfirst record written contains a version number, the number of\nrecords that follow the first record, and the total number of bytes\nin those subsequent records. An actual example of such a status\nfile (/etc/apcupsd/apcupsd.status) is shown below.\nConsequently, the first record always consists of 24 bytes (23\ncharacters followed by a newline). This record starts with APC and\nas indicated in the example is followed by 37 records\nconsisting of 906 bytes. The last record begins with END APC and\ncontains the date and time matching the DATE record.\nWhen this data is written to a file, it is written as two records,\nthe first record, and all the other records together. In reading\nthe file, it can be either be read a record at a time, or in one\nbig read.\nWhen this data is written to syslog(), it is written a record at a\ntemps. The first record is the first 24 bytes. By having the number\nof records and the size in the first record, the complete status\ncan be reliably reassembled.
"},{"id":"text-79","type":"text","heading":"","plain_text":"Status Report Example\nAn example of output from a BackUPS RS 1500 follows:","html":"Status Report Example\nAn example of output from a BackUPS RS 1500 follows:
"},{"id":"text-80","type":"text","heading":"","plain_text":"APC : 001,037,0906\nDATE : Sun Apr 26 17:22:22 EDT 2009\nHOSTNAME : mail.kroptech.com\nVERSION : 3.14.2 (10 September 2007) redhat\nUPSNAME : ups0\nCABLE : USB Cable\nMODEL : Back-UPS RS 1500\nUPSMODE : Stand Alone\nSTARTTIME: Sun Apr 26 10:22:46 EDT 2009\nSTATUS : ONLINE\nLINEV : 123.0 Volts\nLOADPCT : 24.0 Percent Load Capacity\nBCHARGE : 100.0 Percent\nTIMELEFT : 144.5 Minutes\nMBATTCHG : 5 Percent\nMINTIMEL : 3 Minutes\nMAXTIME : 0 Seconds\nSENSE : Medium\nLOTRANS : 097.0 Volts\nHITRANS : 138.0 Volts\nALARMDEL : Always\nBATTV : 26.8 Volts\nLASTXFER : Low line voltage\nNUMXFERS : 0\nTONBATT : 0 seconds\nCUMONBATT: 0 seconds\nXOFFBATT : N/A\nSELFTEST : NO\nSTATFLAG : 0x07000008 Status Flag\nMANDATE : 2003-05-08\nSERIALNO : JB0319033692\nBATTDATE : 2001-09-25\nNOMINV : 120\nNOMBATTV : 24.0\nFIRMWARE : 8.g6 .D USB FW:g6\nAPCMODEL : Back-UPS RS 1500\nEND APC : Sun Apr 26 17:22:32 EDT 2009","html":"APC : 001,037,0906\nDATE : Sun Apr 26 17:22:22 EDT 2009\nHOSTNAME : mail.kroptech.com\nVERSION : 3.14.2 (10 September 2007) redhat\nUPSNAME : ups0\nCABLE : USB Cable\nMODEL : Back-UPS RS 1500\nUPSMODE : Stand Alone\nSTARTTIME: Sun Apr 26 10:22:46 EDT 2009\nSTATUS : ONLINE\nLINEV : 123.0 Volts\nLOADPCT : 24.0 Percent Load Capacity\nBCHARGE : 100.0 Percent\nTIMELEFT : 144.5 Minutes\nMBATTCHG : 5 Percent\nMINTIMEL : 3 Minutes\nMAXTIME : 0 Seconds\nSENSE : Medium\nLOTRANS : 097.0 Volts\nHITRANS : 138.0 Volts\nALARMDEL : Always\nBATTV : 26.8 Volts\nLASTXFER : Low line voltage\nNUMXFERS : 0\nTONBATT : 0 seconds\nCUMONBATT: 0 seconds\nXOFFBATT : N/A\nSELFTEST : NO\nSTATFLAG : 0x07000008 Status Flag\nMANDATE : 2003-05-08\nSERIALNO : JB0319033692\nBATTDATE : 2001-09-25\nNOMINV : 120\nNOMBATTV : 24.0\nFIRMWARE : 8.g6 .D USB FW:g6\nAPCMODEL : Back-UPS RS 1500\nEND APC : Sun Apr 26 17:22:32 EDT 2009
"},{"id":"text-81","type":"text","heading":"","plain_text":"Status Report Fields\nThe meaning of the above variables are:","html":"Status Report Fields\nThe meaning of the above variables are:
"},{"id":"text-82","type":"text","heading":"","plain_text":"APC\nHeader record indicating the STATUS format\nrevision level, the number of records that follow the APC\nstatement, and the number of bytes that follow the record.\nDATE\nThe date and time that the information was last obtained from the UPS.\nHOSTNAME\nThe name of the machine that collected the UPS data.\nUPSNAME\nThe name of the UPS as stored in the EEPROM or in the UPSNAME\ndirective in the configuration file.\nVERSION\nThe apcupsd release number, build date, and platform.\nCABLE\nThe cable as specified in the configuration file (UPSCABLE).\nMODÈLE\nThe UPS model as derived from information from the UPS.\nUPSMODE\nThe mode in which apcupsd is operating as specified in the configuration\nfile (UPSMODE)\nSTARTTIME\nThe time/date that apcupsd was started.\nSTATUS\nThe current status of the UPS (ONLINE, ONBATT, etc.)\nLINEV\nThe current line voltage as returned by the UPS.\nLOADPCT\nThe percentage of load capacity as estimated by the UPS.\nBCHARGE\nThe percentage charge on the batteries.\nTIMELEFT\nThe remaining runtime left on batteries as estimated by the UPS.\nMBATTCHG\nIf the battery charge percentage (BCHARGE)\ndrops below this value, apcupsd will shutdown your system.\nValue is set in the configuration file (BATTERYLEVEL)\nMINTIMEL\napcupsd will shutdown your system if the\nremaining runtime equals or is below this point.\nValue is set in the configuration file (MINUTES)\nMAXTIME\napcupsd will shutdown your system if the time\non batteries exceeds this value. A value of zero disables the\nfeature. Value is set in the configuration file (TIMEOUT)\nMAXLINEV\nThe maximum line voltage since the UPS was started, as reported by the UPS\nMINLINEV\nThe minimum line voltage since the UPS was started, as returned by the UPS\nOUTPUTV\nThe voltage the UPS is supplying to your equipment\nSENSE\nThe sensitivity level of the UPS to line voltage fluctuations.\nDWAKE\nThe amount of time the UPS will wait before restoring power to your\nequipment after a power off condition when the power is restored.\nDSHUTD\nThe grace delay that the UPS gives after\nreceiving a power down command from apcupsd before it powers off\nyour equipment.\nDLOWBATT\nThe remaining runtime below which the UPS\nsends the low battery signal. At this point apcupsd will force an\nimmediate emergency shutdown.\nLOTRANS\nThe line voltage below which the UPS will switch to batteries.\nHITRANS\nThe line voltage above which the UPS will switch to batteries.\nRETPCT\nThe percentage charge that the batteries must\nhave after a power off condition before the UPS will restore power\nto your equipment.\nITEMP\nInternal UPS temperature as supplied by the UPS.\nALARMDEL\nThe delay period for the UPS alarm.\nBATTV\nBattery voltage as supplied by the UPS.\nLINEFREQ\nLine frequency in hertz as given by the UPS.\nLASTXFER\nThe reason for the last transfer to batteries.\nNUMXFERS\nThe number of transfers to batteries since apcupsd startup.\nXONBATT\nTime and date of last transfer to batteries, or N/A.\nTONBATT\nTime in seconds currently on batteries, or 0.\nCUMONBATT\nTotal (cumulative) time on batteries in seconds since apcupsd startup.\nXOFFBATT\nTime and date of last transfer from batteries, or N/A.\nSELFTEST","html":"APC\nHeader record indicating the STATUS format\nrevision level, the number of records that follow the APC\nstatement, and the number of bytes that follow the record.\nDATE\nThe date and time that the information was last obtained from the UPS.\nHOSTNAME\nThe name of the machine that collected the UPS data.\nUPSNAME\nThe name of the UPS as stored in the EEPROM or in the UPSNAME\ndirective in the configuration file.\nVERSION\nThe apcupsd release number, build date, and platform.\nCABLE\nThe cable as specified in the configuration file (UPSCABLE).\nMODÈLE\nThe UPS model as derived from information from the UPS.\nUPSMODE\nThe mode in which apcupsd is operating as specified in the configuration\nfile (UPSMODE)\nSTARTTIME\nThe time/date that apcupsd was started.\nSTATUS\nThe current status of the UPS (ONLINE, ONBATT, etc.)\nLINEV\nThe current line voltage as returned by the UPS.\nLOADPCT\nThe percentage of load capacity as estimated by the UPS.\nBCHARGE\nThe percentage charge on the batteries.\nTIMELEFT\nThe remaining runtime left on batteries as estimated by the UPS.\nMBATTCHG\nIf the battery charge percentage (BCHARGE)\ndrops below this value, apcupsd will shutdown your system.\nValue is set in the configuration file (BATTERYLEVEL)\nMINTIMEL\napcupsd will shutdown your system if the\nremaining runtime equals or is below this point.\nValue is set in the configuration file (MINUTES)\nMAXTIME\napcupsd will shutdown your system if the time\non batteries exceeds this value. A value of zero disables the\nfeature. Value is set in the configuration file (TIMEOUT)\nMAXLINEV\nThe maximum line voltage since the UPS was started, as reported by the UPS\nMINLINEV\nThe minimum line voltage since the UPS was started, as returned by the UPS\nOUTPUTV\nThe voltage the UPS is supplying to your equipment\nSENSE\nThe sensitivity level of the UPS to line voltage fluctuations.\nDWAKE\nThe amount of time the UPS will wait before restoring power to your\nequipment after a power off condition when the power is restored.\nDSHUTD\nThe grace delay that the UPS gives after\nreceiving a power down command from apcupsd before it powers off\nyour equipment.\nDLOWBATT\nThe remaining runtime below which the UPS\nsends the low battery signal. At this point apcupsd will force an\nimmediate emergency shutdown.\nLOTRANS\nThe line voltage below which the UPS will switch to batteries.\nHITRANS\nThe line voltage above which the UPS will switch to batteries.\nRETPCT\nThe percentage charge that the batteries must\nhave after a power off condition before the UPS will restore power\nto your equipment.\nITEMP\nInternal UPS temperature as supplied by the UPS.\nALARMDEL\nThe delay period for the UPS alarm.\nBATTV\nBattery voltage as supplied by the UPS.\nLINEFREQ\nLine frequency in hertz as given by the UPS.\nLASTXFER\nThe reason for the last transfer to batteries.\nNUMXFERS\nThe number of transfers to batteries since apcupsd startup.\nXONBATT\nTime and date of last transfer to batteries, or N/A.\nTONBATT\nTime in seconds currently on batteries, or 0.\nCUMONBATT\nTotal (cumulative) time on batteries in seconds since apcupsd startup.\nXOFFBATT\nTime and date of last transfer from batteries, or N/A.\nSELFTEST
"},{"id":"text-83","type":"text","heading":"","plain_text":"The results of the last self test, and may have the following values:","html":"The results of the last self test, and may have the following values:
"},{"id":"text-84","type":"text","heading":"","plain_text":"OK: self test indicates good battery\nBT: self test failed due to insufficient battery capacity\nNG: self test failed due to overload\nNO: No results (i.e. no self test performed in the last 5 minutes)","html":"OK: self test indicates good battery\nBT: self test failed due to insufficient battery capacity\nNG: self test failed due to overload\nNO: No results (i.e. no self test performed in the last 5 minutes)
"},{"id":"text-85","type":"text","heading":"","plain_text":"STESTI\nThe interval in hours between automatic self tests.\nSTATFLAG\nStatus flag. English version is given by STATUS.\nDIPSW\nThe current dip switch settings on UPSes that have them.\nREG1\nThe value from the UPS fault register 1.\nREG2\nThe value from the UPS fault register 2.\nREG3\nThe value from the UPS fault register 3.\nMANDATE\nThe date the UPS was manufactured.\nSERIALNO\nThe UPS serial number.\nBATTDATE\nThe date that batteries were last replaced.\nNOMOUTV\nThe output voltage that the UPS will attempt to supply when on battery\nPuissance.\nNOMINV\nThe input voltage that the UPS is configured to expect.\nNOMBATTV\nThe nominal battery voltage.\nNOMPOWER\nThe maximum power in Watts that the UPS is designed to supply.\nHUMIDITY\nThe humidity as measured by the UPS.\nAMBTEMP\nThe ambient temperature as measured by the UPS.\nEXTBATTS\nThe number of external batteries as\ndefined by the user. A correct number here helps the UPS compute\nthe remaining runtime more accurately.\nBADBATTS\nThe number of bad battery packs.\nFIRMWARE\nThe firmware revision number as reported by the UPS.\nAPCMODEL\nThe old APC model identification code.\nEND APC\nThe time and date that the STATUS record was written.","html":"STESTI\nThe interval in hours between automatic self tests.\nSTATFLAG\nStatus flag. English version is given by STATUS.\nDIPSW\nThe current dip switch settings on UPSes that have them.\nREG1\nThe value from the UPS fault register 1.\nREG2\nThe value from the UPS fault register 2.\nREG3\nThe value from the UPS fault register 3.\nMANDATE\nThe date the UPS was manufactured.\nSERIALNO\nThe UPS serial number.\nBATTDATE\nThe date that batteries were last replaced.\nNOMOUTV\nThe output voltage that the UPS will attempt to supply when on battery\nPuissance.\nNOMINV\nThe input voltage that the UPS is configured to expect.\nNOMBATTV\nThe nominal battery voltage.\nNOMPOWER\nThe maximum power in Watts that the UPS is designed to supply.\nHUMIDITY\nThe humidity as measured by the UPS.\nAMBTEMP\nThe ambient temperature as measured by the UPS.\nEXTBATTS\nThe number of external batteries as\ndefined by the user. A correct number here helps the UPS compute\nthe remaining runtime more accurately.\nBADBATTS\nThe number of bad battery packs.\nFIRMWARE\nThe firmware revision number as reported by the UPS.\nAPCMODEL\nThe old APC model identification code.\nEND APC\nThe time and date that the STATUS record was written.
"},{"id":"text-86","type":"text","heading":"","plain_text":"Logging the STATUS Information\nIf specified in the configuration file, the STATUS data will also be\nwritten to the system log file. Please note, that it would not\nnormally be wise to write this data to a normal system log file as\nthere is no mechanism in syslog() to rewind the file and hence the\nlog file would quickly become enormous. However, in two cases, it\ncan be very useful to use syslog() to write this information.\nThe first case is to set up your syslog.conf file so that the data\nis written to a named pipe. In this case, normally not more than\nabout 8192 bytes of data will be kept before it is discarded by the\nsystème.\nThe second case is to setup your syslog.conf file so that the\nstatus data is sent to another machine, which presumably then\nwrites it to a named pipe. Consequently, with this mechanism,\nprovides a simple means of networking apcupsd STATUS information.\nAlthough we mention system logging of STATUS information, we\nstrongly recommend that you use apcaccess or the CGI interface to\nget this information.","html":"Logging the STATUS Information\nIf specified in the configuration file, the STATUS data will also be\nwritten to the system log file. Please note, that it would not\nnormally be wise to write this data to a normal system log file as\nthere is no mechanism in syslog() to rewind the file and hence the\nlog file would quickly become enormous. However, in two cases, it\ncan be very useful to use syslog() to write this information.\nThe first case is to set up your syslog.conf file so that the data\nis written to a named pipe. In this case, normally not more than\nabout 8192 bytes of data will be kept before it is discarded by the\nsystème.\nThe second case is to setup your syslog.conf file so that the\nstatus data is sent to another machine, which presumably then\nwrites it to a named pipe. Consequently, with this mechanism,\nprovides a simple means of networking apcupsd STATUS information.\nAlthough we mention system logging of STATUS information, we\nstrongly recommend that you use apcaccess or the CGI interface to\nget this information.
"},{"id":"text-87","type":"text","heading":"","plain_text":"Shutdown Sequence\nIf you experienced so problems with the testing procedures, or if\nyou are porting apcupsd to another system, or you are simply\ncurious, you may want to know exactly what is going on during the\nshutdown process.\nThe shutdown sequence is as follows:","html":"Shutdown Sequence\nIf you experienced so problems with the testing procedures, or if\nyou are porting apcupsd to another system, or you are simply\ncurious, you may want to know exactly what is going on during the\nshutdown process.\nThe shutdown sequence is as follows:
"},{"id":"text-88","type":"text","heading":"","plain_text":"apcupsd detects that there is a power problem and it calls\n/etc/apcupsd/apccontrol powerout. By default this event\ndoes nothing, but it can be overridden to notify users, etc.","html":"apcupsd detects that there is a power problem and it calls\n/etc/apcupsd/apccontrol powerout. By default this event\ndoes nothing, but it can be overridden to notify users, etc.
"},{"id":"text-89","type":"text","heading":"","plain_text":"After the configured ONBATTERYDELAY, apcupsd\ncalls /etc/apcupsd/apccontrol onbattery, which normally sends a\nmessage to all users informing them that the UPS is on batteries.","html":"After the configured ONBATTERYDELAY, apcupsd\ncalls /etc/apcupsd/apccontrol onbattery, which normally sends a\nmessage to all users informing them that the UPS is on batteries.
"},{"id":"text-90","type":"text","heading":"","plain_text":"When one of the conditions listed below occurs, apcupsd issues a\nshutdown command by calling /etc/apcupsd/apccontrol doshutdown,\nwhich should perform a shutdown of your system using the system\nshutdown(8) command. You can modify the behavior as described in\nCustomizing Event Handling.\nThe conditions that trigger the shutdown can be any of the following:","html":"When one of the conditions listed below occurs, apcupsd issues a\nshutdown command by calling /etc/apcupsd/apccontrol doshutdown,\nwhich should perform a shutdown of your system using the system\nshutdown(8) command. You can modify the behavior as described in\nCustomizing Event Handling.\nThe conditions that trigger the shutdown can be any of the following:
"},{"id":"text-91","type":"text","heading":"","plain_text":"Running time on batteries have expired (TIMEOUT)\nThe battery runtime remaining is below the configured value (BATTERYLEVEL)\nThe estimated remaining runtime is below the configured value (MINUTES)\nThe UPS signals that the batteries are exhausted.","html":"Running time on batteries have expired (TIMEOUT)\nThe battery runtime remaining is below the configured value (BATTERYLEVEL)\nThe estimated remaining runtime is below the configured value (MINUTES)\nThe UPS signals that the batteries are exhausted.
"},{"id":"text-92","type":"text","heading":"","plain_text":"A shutdown could also be initiated if apcupsd detects that the\nbatteries are no longer functioning correctly. This case, though\nvery unusual, can happen at any time even if there is proper mains\nvoltage, and /etc/apcupsd/apccontrol emergency is called.\nJust before initiating any shutdown through the apccontrol script,\napcupsd will create the file /etc/apcupsd/powerfail. This file will\nbe used later in the shutdown sequence to recall apcupsd after\nsyncing of the disks to initiate a power off of the UPS.\nIf the /etc/nologin file has not already been created, it will\nnormally be created during the shutdown sequence to prevent\nadditional users from logging in (see the NOLOGIN configuration\ndirective).\nEven though apcupsd has requested the system to perform a shutdown,\nit continues running.","html":"A shutdown could also be initiated if apcupsd detects that the\nbatteries are no longer functioning correctly. This case, though\nvery unusual, can happen at any time even if there is proper mains\nvoltage, and /etc/apcupsd/apccontrol emergency is called.\nJust before initiating any shutdown through the apccontrol script,\napcupsd will create the file /etc/apcupsd/powerfail. This file will\nbe used later in the shutdown sequence to recall apcupsd after\nsyncing of the disks to initiate a power off of the UPS.\nIf the /etc/nologin file has not already been created, it will\nnormally be created during the shutdown sequence to prevent\nadditional users from logging in (see the NOLOGIN configuration\ndirective).\nEven though apcupsd has requested the system to perform a shutdown,\nit continues running.
"},{"id":"text-93","type":"text","heading":"","plain_text":"When the system signals apcupsd to do exit, it does so. This is\npart of the normal system shutdown (at least on Unix and Linux\nsystems) and the exact time that apcupsd receives the termination\nsignal depends on how the shutdown links (usually in /etc/rc.d) are\nset.\nNote that on Windows NT systems, apcupsd apparently continues to\nrun as a Service even though the machine is "shutdown".","html":"When the system signals apcupsd to do exit, it does so. This is\npart of the normal system shutdown (at least on Unix and Linux\nsystems) and the exact time that apcupsd receives the termination\nsignal depends on how the shutdown links (usually in /etc/rc.d) are\nset.\nNote that on Windows NT systems, apcupsd apparently continues to\nrun as a Service even though the machine is "shutdown".
"},{"id":"text-94","type":"text","heading":"","plain_text":"During the shutdown of the system after apcupsd has been forced\nto exit, one of the last things done by the system shutdown is to\ncall the halt script, which is usually in /etc/rc.d/halt or\n/etc/rc.d/init.d/halt, or possibly in /sbin/init.d/rc.0 depending\non your system. If apcupsd was properly installed, this standard\nhalt script was modified to include a bit of new logic just before\nthe final halt of the system. It first tests if the file\n/etc/apcupsd/powerfail exists, and if it does, it executes\n/etc/apcupsd/apccontrol killpower. It is this last step that will\ncause apcupsd to be re-executed with the --killpower option\non the command line. This option tells apcupsd to inform the UPS to\nkill the power.","html":"During the shutdown of the system after apcupsd has been forced\nto exit, one of the last things done by the system shutdown is to\ncall the halt script, which is usually in /etc/rc.d/halt or\n/etc/rc.d/init.d/halt, or possibly in /sbin/init.d/rc.0 depending\non your system. If apcupsd was properly installed, this standard\nhalt script was modified to include a bit of new logic just before\nthe final halt of the system. It first tests if the file\n/etc/apcupsd/powerfail exists, and if it does, it executes\n/etc/apcupsd/apccontrol killpower. It is this last step that will\ncause apcupsd to be re-executed with the --killpower option\non the command line. This option tells apcupsd to inform the UPS to\nkill the power.
"},{"id":"text-95","type":"text","heading":"","plain_text":"This final step is important if you want to ensure that your system\nwill automatically reboot when the power comes back on. The actual\ncode used on the Red Hat version is:","html":"This final step is important if you want to ensure that your system\nwill automatically reboot when the power comes back on. The actual\ncode used on the Red Hat version is:
"},{"id":"text-96","type":"text","heading":"","plain_text":"# See if this is a powerfail situation. # ***apcupsd***\nif [ -f /etc/apcupsd/powerfail ]; then # ***apcupsd***\n echo # ***apcupsd***\n echo "APCUPSD will now power off the UPS" # ***apcupsd***\n echo # ***apcupsd***\n /etc/apcupsd/apccontrol killpower # ***apcupsd***\n echo # ***apcupsd***\n echo "Please ensure that the UPS has powered off before rebooting" # ***apcupsd***\n echo "Otherwise, the UPS may cut the power during the reboot!!!" # ***apcupsd***\n echo # ***apcupsd***\nfi # ***apcupsd***","html":"# See if this is a powerfail situation. # ***apcupsd***\nif [ -f /etc/apcupsd/powerfail ]; then # ***apcupsd***\n echo # ***apcupsd***\n echo "APCUPSD will now power off the UPS" # ***apcupsd***\n echo # ***apcupsd***\n /etc/apcupsd/apccontrol killpower # ***apcupsd***\n echo # ***apcupsd***\n echo "Please ensure that the UPS has powered off before rebooting" # ***apcupsd***\n echo "Otherwise, the UPS may cut the power during the reboot!!!" # ***apcupsd***\n echo # ***apcupsd***\nfi # ***apcupsd***
"},{"id":"text-97","type":"text","heading":"","plain_text":"The above code must be inserted as late as possible in the halt\nscript. On many systems, such as Red Hat, all the disk drives were\nunmounted, then remounted read-only, thus permitting access to the\n/etc files and the apcupsd executable. If your system does not\nexplicitly remount the disks, you must remount them in read-only\nmode in the code that you add. Examples of code fragments that do\nthis can be found in the distributions/suse subdirectory of the\nla source.\nIf you are not able to insert the above code in your halt script\nbecause there is no halt script, or because your halt script calls\nthe init program as some Unix systems do, you can either just\nforget about powering off the UPS, which means that your machine\nwill not automatically reboot after a power failure, or there is\nyet another alternative, though not at all as satisfying as\ninserting code in the halt script.\nOnly if you cannot insert the appropriate code in the halt script,\nwhen you start apcupsd, normally from the /etc/rc.d/init.d/apcupsd\nscript, use the --kill-on-powerfail option. This will cause\napcupsd to program the UPS to shutoff the power just before it\n(apcupsd) does the system shutdown. Please note that this is not\nthe most ideal solution. Read on to understand why.\nA very important consideration is that you must set the EEPROM in\nyour UPS so that it waits a sufficient time for the system to halt\nbefore it shuts off the UPS power.\nWhen using a USB connection, apcupsd automatically sets this value\nto 60 seconds. When using a serial connection to a SmartUPS, you\nmust configure the value in the UPS EEPROM by hand using apctest.","html":"The above code must be inserted as late as possible in the halt\nscript. On many systems, such as Red Hat, all the disk drives were\nunmounted, then remounted read-only, thus permitting access to the\n/etc files and the apcupsd executable. If your system does not\nexplicitly remount the disks, you must remount them in read-only\nmode in the code that you add. Examples of code fragments that do\nthis can be found in the distributions/suse subdirectory of the\nla source.\nIf you are not able to insert the above code in your halt script\nbecause there is no halt script, or because your halt script calls\nthe init program as some Unix systems do, you can either just\nforget about powering off the UPS, which means that your machine\nwill not automatically reboot after a power failure, or there is\nyet another alternative, though not at all as satisfying as\ninserting code in the halt script.\nOnly if you cannot insert the appropriate code in the halt script,\nwhen you start apcupsd, normally from the /etc/rc.d/init.d/apcupsd\nscript, use the --kill-on-powerfail option. This will cause\napcupsd to program the UPS to shutoff the power just before it\n(apcupsd) does the system shutdown. Please note that this is not\nthe most ideal solution. Read on to understand why.\nA very important consideration is that you must set the EEPROM in\nyour UPS so that it waits a sufficient time for the system to halt\nbefore it shuts off the UPS power.\nWhen using a USB connection, apcupsd automatically sets this value\nto 60 seconds. When using a serial connection to a SmartUPS, you\nmust configure the value in the UPS EEPROM by hand using apctest.
"},{"id":"text-98","type":"text","heading":"","plain_text":"Shutdown Problems\nObviously if your halt script is not properly modified, apcupsd\nwill not be able to shut off the power to the UPS, and if the power\nreturns before the batteries are exhausted your system will not\nautomatically reboot. In any case, your machine should have been\ncleanly shut down.","html":"Shutdown Problems\nObviously if your halt script is not properly modified, apcupsd\nwill not be able to shut off the power to the UPS, and if the power\nreturns before the batteries are exhausted your system will not\nautomatically reboot. In any case, your machine should have been\ncleanly shut down.
"},{"id":"text-99","type":"text","heading":"","plain_text":"Master/Slave Shutdown\nIn master/slave configurations, however, the master cannot be 100\npercent sure that the slaves have all shutdown before it performs\nthe power off. To avoid this situation, be sure to configure any\nslaves (clients) to shut down before the master by setting different\nTIMEOUT, BATTERYLEVEL, ou MINUTES parameters in the\nconfig file.\nAlso, on a slave machine, you do not want to use the modified halt\nscript since it will recall apcupsd, which will detect that it is a\nslave (i.e. no connection to the UPS) and will complain that it\ncannot do the killpower. This situation is not harmful just\nannoying and possibly confusing.\nOne possible problem during shutdown can be caused by remnants of\nold versions. Please be sure to delete or rename all prior versions\n(/usr/local/sbin/apcupsd or /sbin/powersc).","html":"Master/Slave Shutdown\nIn master/slave configurations, however, the master cannot be 100\npercent sure that the slaves have all shutdown before it performs\nthe power off. To avoid this situation, be sure to configure any\nslaves (clients) to shut down before the master by setting different\nTIMEOUT, BATTERYLEVEL, ou MINUTES parameters in the\nconfig file.\nAlso, on a slave machine, you do not want to use the modified halt\nscript since it will recall apcupsd, which will detect that it is a\nslave (i.e. no connection to the UPS) and will complain that it\ncannot do the killpower. This situation is not harmful just\nannoying and possibly confusing.\nOne possible problem during shutdown can be caused by remnants of\nold versions. Please be sure to delete or rename all prior versions\n(/usr/local/sbin/apcupsd or /sbin/powersc).
"},{"id":"text-100","type":"text","heading":"","plain_text":"Startup\nNormally, apcupsd is automatically started when\nyour system is rebooted. This normally occurs because the startup\nscript apcupsd is linked into the appropriate places in /etc/rc.d.\nOn most Linux systems, there is a program called chkconfig(8) that\nwill automatically link the startup script. This program is invoked\nby the make install scripts, or it is explicitly done for those\nsystems that do not have chkconfig(8). If this is not the case, you\ncan either link it in appropriately yourself or explicitly call it\nfrom your rc.local file. The appropriate manual way to startup\napcupsd is by executing:","html":"Startup\nNormally, apcupsd is automatically started when\nyour system is rebooted. This normally occurs because the startup\nscript apcupsd is linked into the appropriate places in /etc/rc.d.\nOn most Linux systems, there is a program called chkconfig(8) that\nwill automatically link the startup script. This program is invoked\nby the make install scripts, or it is explicitly done for those\nsystems that do not have chkconfig(8). If this is not the case, you\ncan either link it in appropriately yourself or explicitly call it\nfrom your rc.local file. The appropriate manual way to startup\napcupsd is by executing:
"},{"id":"text-101","type":"text","heading":"","plain_text":"/apcupsd start","html":"/apcupsd start
"},{"id":"text-102","type":"text","heading":"","plain_text":"où path is normally /etc/rc.d or /etc/rc.d/init.d depending on\nyour system. Using this script is\nimportant so that any files remaining around after a power failure\nare removed. Likewise, shutting down apcupsd should be done with\nthe same script:","html":"où path is normally /etc/rc.d or /etc/rc.d/init.d depending on\nyour system. Using this script is\nimportant so that any files remaining around after a power failure\nare removed. Likewise, shutting down apcupsd should be done with\nthe same script:
"},{"id":"text-103","type":"text","heading":"","plain_text":"/apcupsd stop","html":"/apcupsd stop
"},{"id":"text-104","type":"text","heading":"","plain_text":"The APC UPS\nprotocol was originally analyzed by Pavel Korensky with additions\nfrom Andre H. Hendrick beginning in 1995, and we want to give\ncredit for good, hard work, where credit is due. After having said\nthat, you will see that Steven Freed built much of the original\napcupsd information file.\nThe start of this chapter of the apcupsd manual in HTML format was\npulled from the Network UPS Tools (NUT) site\n(http://www.networkupstools.org/ups-protocols/apcsmart.html). Il\nhas been an invaluable tool in improving apcupsd, and I consider it\nthe Bible of APC UPS programming. In the course of using it, I\nhave added information gleaned from apcupsd and information\ngraciously supplied by APC.","html":"The APC UPS\nprotocol was originally analyzed by Pavel Korensky with additions\nfrom Andre H. Hendrick beginning in 1995, and we want to give\ncredit for good, hard work, where credit is due. After having said\nthat, you will see that Steven Freed built much of the original\napcupsd information file.\nThe start of this chapter of the apcupsd manual in HTML format was\npulled from the Network UPS Tools (NUT) site\n(http://www.networkupstools.org/ups-protocols/apcsmart.html). Il\nhas been an invaluable tool in improving apcupsd, and I consider it\nthe Bible of APC UPS programming. In the course of using it, I\nhave added information gleaned from apcupsd and information\ngraciously supplied by APC.
"},{"id":"text-105","type":"text","heading":"","plain_text":"La description\nHere's the information on the elusive APC smart signaling protocol\nused by their higher end units (Back-UPS Pro, Smart-UPS,\nMatrix-UPS, etc). What you see here has been collected from a\nvariety of sources. Some people analyzed the chatter between\nPowerChute and their hardware. Others sent various characters to\nthe UPS and figured out what the results meant.","html":"La description\nHere's the information on the elusive APC smart signaling protocol\nused by their higher end units (Back-UPS Pro, Smart-UPS,\nMatrix-UPS, etc). What you see here has been collected from a\nvariety of sources. Some people analyzed the chatter between\nPowerChute and their hardware. Others sent various characters to\nthe UPS and figured out what the results meant.
"},{"id":"text-106","type":"text","heading":"","plain_text":"RS-232 differences\nNormal 9 pin serial connections have TxD on 3 and RxD on 2. APC's\nsmart serial ports put TxD on pin 1 and RxD on pin 2. This means\nyou go nowhere if you use a normal straight through serial cable.\nIn fact, you might even power down the load if you plug one of\nthose cables in. This is due to the odd routing of pins – DTR and\nRTS from the PC usually wind up driving the on/off line. So, when\nyou open the port, they go high and *poof* your computer dies.","html":"RS-232 differences\nNormal 9 pin serial connections have TxD on 3 and RxD on 2. APC's\nsmart serial ports put TxD on pin 1 and RxD on pin 2. This means\nyou go nowhere if you use a normal straight through serial cable.\nIn fact, you might even power down the load if you plug one of\nthose cables in. This is due to the odd routing of pins – DTR and\nRTS from the PC usually wind up driving the on/off line. So, when\nyou open the port, they go high and *poof* your computer dies.
"},{"id":"text-107","type":"text","heading":"","plain_text":"The Smart Protocol\nDespite the lack of official information from APC, this table has\nbeen constructed. It's standard RS-232 serial communications at\n2400 bps/8N1. Don't rush the UPS while transmitting or it may stop\ntalking to you. This isn't a problem with the normal single\ncharacter queries, but it really does matter for multi-char things\nlike "@000". Sprinkle a few calls to usleep() in your code and\neverything will work a lot better.\nThe following table describes the single character "Code" or\ncommand that you can send to the UPS, its meaning, and what sort of\nresponse the UPS will provide. Typically, the response shown below\nis followed by a newline (n in C) and a carriage return (r in\nC). If you send the UPS a command that it does not recognize or\nthat is not available on your UPS, it will normally respond with "NA"\nfor "not available", otherwise the response is given in the\n"Typical results" column.","html":"The Smart Protocol\nDespite the lack of official information from APC, this table has\nbeen constructed. It's standard RS-232 serial communications at\n2400 bps/8N1. Don't rush the UPS while transmitting or it may stop\ntalking to you. This isn't a problem with the normal single\ncharacter queries, but it really does matter for multi-char things\nlike "@000". Sprinkle a few calls to usleep() in your code and\neverything will work a lot better.\nThe following table describes the single character "Code" or\ncommand that you can send to the UPS, its meaning, and what sort of\nresponse the UPS will provide. Typically, the response shown below\nis followed by a newline (n in C) and a carriage return (r in\nC). If you send the UPS a command that it does not recognize or\nthat is not available on your UPS, it will normally respond with "NA"\nfor "not available", otherwise the response is given in the\n"Typical results" column.
"},{"id":"text-108","type":"text","heading":"","plain_text":"Personnage\nSens\nTypical results\nOther info","html":"Personnage\nSens\nTypical results\nOther info
"},{"id":"text-109","type":"text","heading":"","plain_text":"^A\nModel string\nSMART-UPS 700\nSpotty support for this query on older\ndes modèles","html":"^A\nModel string\nSMART-UPS 700\nSpotty support for this query on older\ndes modèles
"},{"id":"text-110","type":"text","heading":"","plain_text":"^N\nTurn on UPS\nn / a\nSend twice, with 1.5s delay between\nchars. Only on 3rd gen SmartUPS and\nBlack Back-UPS Pros","html":"^N\nTurn on UPS\nn / a\nSend twice, with 1.5s delay between\nchars. Only on 3rd gen SmartUPS and\nBlack Back-UPS Pros
"},{"id":"text-111","type":"text","heading":"","plain_text":"^Z\nPermitted\nEEPROM\nValues\nlong string\nGives the EEPROM permitted values for\nyour model. See EEPROM Values for\ndetails.","html":"^Z\nPermitted\nEEPROM\nValues\nlong string\nGives the EEPROM permitted values for\nyour model. See EEPROM Values for\ndetails.
"},{"id":"text-112","type":"text","heading":"","plain_text":"UNE\nFront panel\ntest\nLight show +\n"OK"\nAlso sounds the beeper for 2 seconds","html":"UNE\nFront panel\ntest\nLight show +\n"OK"\nAlso sounds the beeper for 2 seconds
"},{"id":"text-113","type":"text","heading":"","plain_text":"B\nBatterie\nvoltage\n27.87\nVaries based on current level of\ncharge. See also Nominal Battery\nVoltage.","html":"B\nBatterie\nvoltage\n27.87\nVaries based on current level of\ncharge. See also Nominal Battery\nVoltage.
"},{"id":"text-114","type":"text","heading":"","plain_text":"C\nInterne\nTemperature\n036.0\nUnits are degrees C","html":"C\nInterne\nTemperature\n036.0\nUnits are degrees C
"},{"id":"text-115","type":"text","heading":"","plain_text":"ré\nRuntime\ncalibration\n!, then $\nRuns until battery is below 25% (35%\nfor Matrix) Updates the 'j' values.\nOnly works at 100% battery charge. Pouvez\nbe aborted with a second "D"","html":"ré\nRuntime\ncalibration\n!, then $\nRuns until battery is below 25% (35%\nfor Matrix) Updates the 'j' values.\nOnly works at 100% battery charge. Pouvez\nbe aborted with a second "D"
"},{"id":"text-116","type":"text","heading":"","plain_text":"E\nAutomatic\nself test\ninterval\n336","html":"E\nAutomatic\nself test\ninterval\n336
"},{"id":"text-117","type":"text","heading":"","plain_text":"Writable variable. Possible values:","html":"Writable variable. Possible values:
"},{"id":"text-118","type":"text","heading":"","plain_text":""336" (14 days)\n"168" (7 days)\n"ON " (at power on) note extra space\n"OFF" (never)","html":""336" (14 days)\n"168" (7 days)\n"ON " (at power on) note extra space\n"OFF" (never)
"},{"id":"text-119","type":"text","heading":"","plain_text":"F\nLigne\nla fréquence\n60.00\nUnits are Hz. Value varies based on\nlocality, usually 50/60.","html":"F\nLigne\nla fréquence\n60.00\nUnits are Hz. Value varies based on\nlocality, usually 50/60.
"},{"id":"text-120","type":"text","heading":"","plain_text":"g\nCause of\nlast\ntransfert\nto battery\nO","html":"g\nCause of\nlast\ntransfert\nto battery\nO
"},{"id":"text-121","type":"text","heading":"","plain_text":"Possible values:","html":"Possible values:
"},{"id":"text-122","type":"text","heading":"","plain_text":"R (unacceptable utility voltage rate\nof change)\nH (high utility voltage)\nL (low utility voltage)\nT (line voltage notch or spike)\nO (no transfers since turnon)\nS (transfer due to U command or\nactivation of UPS test from front\npanel)\nNA (transfer reason still not\navailable; read again)","html":"R (unacceptable utility voltage rate\nof change)\nH (high utility voltage)\nL (low utility voltage)\nT (line voltage notch or spike)\nO (no transfers since turnon)\nS (transfer due to U command or\nactivation of UPS test from front\npanel)\nNA (transfer reason still not\navailable; read again)
"},{"id":"text-123","type":"text","heading":"","plain_text":"je\nMeasure-UPS\nAlarm enable\nFF\nnot decoded yet","html":"je\nMeasure-UPS\nAlarm enable\nFF\nnot decoded yet
"},{"id":"text-124","type":"text","heading":"","plain_text":"J\nMeasure-UPS\nAlarm status\n0F,00\nnot decoded yet","html":"J\nMeasure-UPS\nAlarm status\n0F,00\nnot decoded yet
"},{"id":"text-125","type":"text","heading":"","plain_text":"K\nShutdown\nwith grace\nperiod (no\nreturn)\nOK or *\nSend twice with > 1.5s delay between\nchars. Older units send "*" instead of\n"OK". Length of grace period is set\nwith Grace Period command. UPS will\nremain off and NOT power on if utility\npower is restored.","html":"K\nShutdown\nwith grace\nperiod (no\nreturn)\nOK or *\nSend twice with > 1.5s delay between\nchars. Older units send "*" instead of\n"OK". Length of grace period is set\nwith Grace Period command. UPS will\nremain off and NOT power on if utility\npower is restored.
"},{"id":"text-126","type":"text","heading":"","plain_text":"L\nInput line\nvoltage\n118.3\nValue varies based on locality. Does\nnot always read 000.0 on line failure.","html":"L\nInput line\nvoltage\n118.3\nValue varies based on locality. Does\nnot always read 000.0 on line failure.
"},{"id":"text-127","type":"text","heading":"","plain_text":"M\nMaximum line\nvoltage\n118.9\nThis is the max voltage since the last\ntime this query was run.","html":"M\nMaximum line\nvoltage\n118.9\nThis is the max voltage since the last\ntime this query was run.
"},{"id":"text-128","type":"text","heading":"","plain_text":"N\nMinimum line\nvoltage\n118.1\nThis is the min voltage since the last\ntime this query was run.","html":"N\nMinimum line\nvoltage\n118.1\nThis is the min voltage since the last\ntime this query was run.
"},{"id":"text-129","type":"text","heading":"","plain_text":"O\nOutput\nvoltage\n118.3\nAlso see on battery output voltage.","html":"O\nOutput\nvoltage\n118.3\nAlso see on battery output voltage.
"},{"id":"text-130","type":"text","heading":"","plain_text":"P\nPower load\n%\n023.5\nRelative to capacity of the UPS.","html":"P\nPower load\n%\n023.5\nRelative to capacity of the UPS.
"},{"id":"text-131","type":"text","heading":"","plain_text":"Q\nStatus flags\n08\nBitmapped, see status bits below","html":"Q\nStatus flags\n08\nBitmapped, see status bits below
"},{"id":"text-132","type":"text","heading":"","plain_text":"R\nTurn dumb\nBYE\nOnly on 3rd gen SmartUPS, SmartUPS\nv/s, BackUPS Pro. Must send enter\nsmart mode command to resume comms.","html":"R\nTurn dumb\nBYE\nOnly on 3rd gen SmartUPS, SmartUPS\nv/s, BackUPS Pro. Must send enter\nsmart mode command to resume comms.
"},{"id":"text-133","type":"text","heading":"","plain_text":"S\nSoft\nshutdown\nD'accord\nCommand executes after grace period.\nUPS goes online when power returns.\nOnly works when on battery.","html":"S\nSoft\nshutdown\nD'accord\nCommand executes after grace period.\nUPS goes online when power returns.\nOnly works when on battery.
"},{"id":"text-134","type":"text","heading":"","plain_text":"U\nSimulate\npower\nfailure\n!, then $\nSee Alert messages section for info\non ! and $.","html":"U\nSimulate\npower\nfailure\n!, then $\nSee Alert messages section for info\non ! and $.
"},{"id":"text-135","type":"text","heading":"","plain_text":"V\nOld firmware\nrevision\n"GWD" or "IWI"\nVoir Interpretation of the Old\nFirmware Revision","html":"V\nOld firmware\nrevision\n"GWD" or "IWI"\nVoir Interpretation of the Old\nFirmware Revision
"},{"id":"text-136","type":"text","heading":"","plain_text":"W\nSelf test\nD'accord\nTests battery, like pushing button on\nthe front panel. Results stored in "X"","html":"W\nSelf test\nD'accord\nTests battery, like pushing button on\nthe front panel. Results stored in "X"
"},{"id":"text-137","type":"text","heading":"","plain_text":"X\nSelf test\nrésultats\nD'accord","html":"X\nSelf test\nrésultats\nD'accord
"},{"id":"text-138","type":"text","heading":"","plain_text":"Possible values:","html":"Possible values:
"},{"id":"text-139","type":"text","heading":"","plain_text":"OK = good battery\nBT = failed due to insufficient\ncapacité\nNG = failed due to overload\nNO = no results available (no test\nperformed in last 5 minutes)","html":"OK = good battery\nBT = failed due to insufficient\ncapacité\nNG = failed due to overload\nNO = no results available (no test\nperformed in last 5 minutes)
"},{"id":"text-140","type":"text","heading":"","plain_text":"Y\nEnter smart\nmode\nSM\nThis must be sent before any other\ncommands will work. See also turn dumb\ncommand to exit smart mode.","html":"Y\nEnter smart\nmode\nSM\nThis must be sent before any other\ncommands will work. See also turn dumb\ncommand to exit smart mode.
"},{"id":"text-141","type":"text","heading":"","plain_text":"Z\nShutdown\nimmédiatement\nn / a\nSend twice with > 1.5s delay between\nchars. UPS switches load off\nimmediately (no grace period)","html":"Z\nShutdown\nimmédiatement\nn / a\nSend twice with > 1.5s delay between\nchars. UPS switches load off\nimmediately (no grace period)
"},{"id":"text-142","type":"text","heading":"","plain_text":"une\nProtocol\ninfo\nlong string","html":"une\nProtocol\ninfo\nlong string
"},{"id":"text-143","type":"text","heading":"","plain_text":"Returns three main sections delimited\nby periods:","html":"Returns three main sections delimited\nby periods:
"},{"id":"text-144","type":"text","heading":"","plain_text":"Protocol version\nAlert messages (aka async notifiers)\nValid commands","html":"Protocol version\nAlert messages (aka async notifiers)\nValid commands
"},{"id":"text-145","type":"text","heading":"","plain_text":"b\nFirmware\nrevision\n50.9.D","html":"b\nFirmware\nrevision\n50.9.D
"},{"id":"text-146","type":"text","heading":"","plain_text":"Voir Interpretation of the New\nFirmware Revision.\nDecoding the example:","html":"Voir Interpretation of the New\nFirmware Revision.\nDecoding the example:
"},{"id":"text-147","type":"text","heading":"","plain_text":"50 = SKU (variable length)\n9 = firmware revision\nD = country code (D=USA,\nI=International, A=Asia, J=Japan,\nM=Canada)","html":"50 = SKU (variable length)\n9 = firmware revision\nD = country code (D=USA,\nI=International, A=Asia, J=Japan,\nM=Canada)
"},{"id":"text-148","type":"text","heading":"","plain_text":"c\nUPS local\nid\nUPS_IDEN\nWritable variable. Up to 8 letter\nidentifier for keeping track of your\nhardware.","html":"c\nUPS local\nid\nUPS_IDEN\nWritable variable. Up to 8 letter\nidentifier for keeping track of your\nhardware.
"},{"id":"text-149","type":"text","heading":"","plain_text":"e\nReturn\nthreshold\n00","html":"e\nReturn\nthreshold\n00
"},{"id":"text-150","type":"text","heading":"","plain_text":"Writable variable. Minimum battery\ncharge % before UPS will return online\nafter a soft shutdown. Possible\nvalues:","html":"Writable variable. Minimum battery\ncharge % before UPS will return online\nafter a soft shutdown. Possible\nvalues:
"},{"id":"text-151","type":"text","heading":"","plain_text":"00 = 00% (UPS turns on immediately)\n01 = 15%\n02 = 25%\n03 = 90%","html":"00 = 00% (UPS turns on immediately)\n01 = 15%\n02 = 25%\n03 = 90%
"},{"id":"text-152","type":"text","heading":"","plain_text":"f\nBatterie\nlevel %\n099.0\nPercentage of battery charge remaining","html":"f\nBatterie\nlevel %\n099.0\nPercentage of battery charge remaining
"},{"id":"text-153","type":"text","heading":"","plain_text":"g\nNominal\nbatterie\nvoltage\n024\nThe battery voltage that's expected to\nbe present in the UPS normally. Cette\nis a constant based on the type,\nnumber, and wiring of batteries in the\nUPS. Typically "012", "024" or "048".","html":"g\nNominal\nbatterie\nvoltage\n024\nThe battery voltage that's expected to\nbe present in the UPS normally. Cette\nis a constant based on the type,\nnumber, and wiring of batteries in the\nUPS. Typically "012", "024" or "048".
"},{"id":"text-154","type":"text","heading":"","plain_text":"h\nMeasure-UPS\nambient\nhumidity (%)\n042.4\nPercentage. Only works on models with\nMeasure-UPS SmartSlot card.","html":"h\nMeasure-UPS\nambient\nhumidity (%)\n042.4\nPercentage. Only works on models with\nMeasure-UPS SmartSlot card.
"},{"id":"text-155","type":"text","heading":"","plain_text":"je\nMeasure-UPS\ndry contacts\n00","html":"je\nMeasure-UPS\ndry contacts\n00
"},{"id":"text-156","type":"text","heading":"","plain_text":"Bitmapped hex variable. Mapping:","html":"Bitmapped hex variable. Mapping:
"},{"id":"text-157","type":"text","heading":"","plain_text":"10 = contact 1\n20 = contact 2\n40 = contact 3\n80 = contact 4","html":"10 = contact 1\n20 = contact 2\n40 = contact 3\n80 = contact 4
"},{"id":"text-158","type":"text","heading":"","plain_text":"j\nEstimated\nruntime\n0327:\nValue is in minutes. Terminated with\na colon.","html":"j\nEstimated\nruntime\n0327:\nValue is in minutes. Terminated with\na colon.
"},{"id":"text-159","type":"text","heading":"","plain_text":"k\nAlarm delay\n0","html":"k\nAlarm delay\n0
"},{"id":"text-160","type":"text","heading":"","plain_text":"Writable variable. Controls behavior\nof UPS beeper. Possible values:","html":"Writable variable. Controls behavior\nof UPS beeper. Possible values:
"},{"id":"text-161","type":"text","heading":"","plain_text":"0 = 5 second delay after power fail\nT = 30 second delay\nL = alarm at low battery only\nN = no alarm","html":"0 = 5 second delay after power fail\nT = 30 second delay\nL = alarm at low battery only\nN = no alarm
"},{"id":"text-162","type":"text","heading":"","plain_text":"l\nLow transfer\nvoltage\n103\nWritable variable. UPS goes on battery\nwhen voltage drops below this point.","html":"l\nLow transfer\nvoltage\n103\nWritable variable. UPS goes on battery\nwhen voltage drops below this point.
"},{"id":"text-163","type":"text","heading":"","plain_text":"m\nManufacture\ndate\n11/29/96\nFormat may vary by country (MM/DD/YY\nvs DD/MM/YY). Unique within groups of\nUPSes (production runs)","html":"m\nManufacture\ndate\n11/29/96\nFormat may vary by country (MM/DD/YY\nvs DD/MM/YY). Unique within groups of\nUPSes (production runs)
"},{"id":"text-164","type":"text","heading":"","plain_text":"n\nSerial\nnombre\nWS9643050926\nUnique for each UPS","html":"n\nSerial\nnombre\nWS9643050926\nUnique for each UPS
"},{"id":"text-165","type":"text","heading":"","plain_text":"o\nNominal\nOutput\nTension\n115\nExpected output voltage when running\non batteries. May be a writable\nvariable on 220/230/240 VAC units.","html":"o\nNominal\nOutput\nTension\n115\nExpected output voltage when running\non batteries. May be a writable\nvariable on 220/230/240 VAC units.
"},{"id":"text-166","type":"text","heading":"","plain_text":"p\nShutdown\ngrace delay\n020\nSeconds. Writable variable. Sets the\ndelay before soft shutdown completes.\n(020/180/300/600)","html":"p\nShutdown\ngrace delay\n020\nSeconds. Writable variable. Sets the\ndelay before soft shutdown completes.\n(020/180/300/600)
"},{"id":"text-167","type":"text","heading":"","plain_text":"q\nLow battery\nwarning\n02\nMinutes. Writable variable. The UPS\nwill report a low battery condition\nthis many minutes before it runs out\nof power","html":"q\nLow battery\nwarning\n02\nMinutes. Writable variable. The UPS\nwill report a low battery condition\nthis many minutes before it runs out\nof power
"},{"id":"text-168","type":"text","heading":"","plain_text":"r\nWakeup delay\n000\nSeconds. Writable variable. The UPS\nwill wait this many seconds after\nreaching the minimum charge before\nreturning online. (000/060/180/300)","html":"r\nWakeup delay\n000\nSeconds. Writable variable. The UPS\nwill wait this many seconds after\nreaching the minimum charge before\nreturning online. (000/060/180/300)
"},{"id":"text-169","type":"text","heading":"","plain_text":"s\nSensitivity\nH","html":"s\nSensitivity\nH
"},{"id":"text-170","type":"text","heading":"","plain_text":"Writable variable. Possible values:","html":"Writable variable. Possible values:
"},{"id":"text-171","type":"text","heading":"","plain_text":"H = highest\nM = medium\nL = lowest\nA = autoadjust (Matrix only)","html":"H = highest\nM = medium\nL = lowest\nA = autoadjust (Matrix only)
"},{"id":"text-172","type":"text","heading":"","plain_text":"t\nMeasure-UPS\nambient\ntemperature\n80.5\nDegrees C. Only works on models with\nthe Measure-UPS SmartSlot card.","html":"t\nMeasure-UPS\nambient\ntemperature\n80.5\nDegrees C. Only works on models with\nthe Measure-UPS SmartSlot card.
"},{"id":"text-173","type":"text","heading":"","plain_text":"vous\nUpper\ntransfert\nvoltage\n132\nWritable variable. UPS goes on battery\nwhen voltage rises above this point.","html":"vous\nUpper\ntransfert\nvoltage\n132\nWritable variable. UPS goes on battery\nwhen voltage rises above this point.
"},{"id":"text-174","type":"text","heading":"","plain_text":"v\nMeasure-UPS\nfirmware\n4Kx\nFirmware information for Measure-UPS\nboard","html":"v\nMeasure-UPS\nfirmware\n4Kx\nFirmware information for Measure-UPS\nboard
"},{"id":"text-175","type":"text","heading":"","plain_text":"X\nLast battery\nchange date\n11/29/96\nWritable variable. Holds whatever the\nuser set in it. Eight characters.","html":"X\nLast battery\nchange date\n11/29/96\nWritable variable. Holds whatever the\nuser set in it. Eight characters.
"},{"id":"text-176","type":"text","heading":"","plain_text":"y\ndroits d'auteur\nremarquer\n(C) APCC\nOnly works if firmware letter is\nlater than O","html":"y\ndroits d'auteur\nremarquer\n(C) APCC\nOnly works if firmware letter is\nlater than O
"},{"id":"text-177","type":"text","heading":"","plain_text":"z\nReset to\nfactory\nsettings\nCLEAR\nResets most variables to initial\nfactory values except identity or\nbattery change date. Not available on\nSmartUPS v/s or BackUPS Pro.","html":"z\nReset to\nfactory\nsettings\nCLEAR\nResets most variables to initial\nfactory values except identity or\nbattery change date. Not available on\nSmartUPS v/s or BackUPS Pro.
"},{"id":"text-178","type":"text","heading":"","plain_text":"+\nCapability\ncycle\n(forward)\nvarious\nCycle forward through possible\ncapability values. UPS sends\nafterward to confirm change to EEPROM.","html":"+\nCapability\ncycle\n(forward)\nvarious\nCycle forward through possible\ncapability values. UPS sends\nafterward to confirm change to EEPROM.
"},{"id":"text-179","type":"text","heading":"","plain_text":"–\nCapability\ncycle\n(backward)\nvarious\nCycle backward through possible\ncapability values. UPS sends\nafterward to confirm change to EEPROM.","html":"–\nCapability\ncycle\n(backward)\nvarious\nCycle backward through possible\ncapability values. UPS sends\nafterward to confirm change to EEPROM.
"},{"id":"text-180","type":"text","heading":"","plain_text":"@nnn\nShutdown and\nrevenir\nOK or *\nUPS shuts down after grace period with\ndelayed wakeup after nnn tenths of an\nhour plus any wakeup delay time. Older\nmodels send "*" instead of "OK".","html":"@nnn\nShutdown and\nrevenir\nOK or *\nUPS shuts down after grace period with\ndelayed wakeup after nnn tenths of an\nhour plus any wakeup delay time. Older\nmodels send "*" instead of "OK".
"},{"id":"text-181","type":"text","heading":"","plain_text":"0x7f\nAbort\nshutdown\nD'accord\nUse to abort @, S, K","html":"0x7f\nAbort\nshutdown\nD'accord\nUse to abort @, S, K
"},{"id":"text-182","type":"text","heading":"","plain_text":"~\nRegister #1\nsee below\nSee Register 1 table","html":"~\nRegister #1\nsee below\nSee Register 1 table
"},{"id":"text-183","type":"text","heading":"","plain_text":"'\nRegister #2\nsee below\nSee Register 2 table","html":"'\nRegister #2\nsee below\nSee Register 2 table
"},{"id":"text-184","type":"text","heading":"","plain_text":"0\nBatterie\nconstant\n \nVoir Resetting the UPS Battery\nConstant","html":"0\nBatterie\nconstant\n \nVoir Resetting the UPS Battery\nConstant
"},{"id":"text-185","type":"text","heading":"","plain_text":"4\n???\n \nPrints 35 on SmartUPS 1000","html":"4\n???\n \nPrints 35 on SmartUPS 1000
"},{"id":"text-186","type":"text","heading":"","plain_text":"5\n???\n \nPrints EF on SmartUPS 1000","html":"5\n???\n \nPrints EF on SmartUPS 1000
"},{"id":"text-187","type":"text","heading":"","plain_text":"6\n???\n \nPrints F9 on SmartUPS 1000","html":"6\n???\n \nPrints F9 on SmartUPS 1000
"},{"id":"text-188","type":"text","heading":"","plain_text":"sept\nDIP switch\npositions\n \nSee Dip switch info","html":"sept\nDIP switch\npositions\n \nSee Dip switch info
"},{"id":"text-189","type":"text","heading":"","plain_text":"8\nRegister #3\nsee below\nSee Register 3 table","html":"8\nRegister #3\nsee below\nSee Register 3 table
"},{"id":"text-190","type":"text","heading":"","plain_text":"9\nLine quality\nFF","html":"9\nLine quality\nFF
"},{"id":"text-191","type":"text","heading":"","plain_text":"Possible values:","html":"Possible values:
"},{"id":"text-192","type":"text","heading":"","plain_text":"00 = unacceptable\nFF = acceptable","html":"00 = unacceptable\nFF = acceptable
"},{"id":"text-193","type":"text","heading":"","plain_text":">\nNumber of\nexterne\nbatterie\npacks\n \nSmartCell models return number of\nconnected packs. Other models return\nvalue set by the user (use +/-).","html":">\nNumber of\nexterne\nbatterie\npacks\n \nSmartCell models return number of\nconnected packs. Other models return\nvalue set by the user (use +/-).
"},{"id":"text-194","type":"text","heading":"","plain_text":"[[[[\nMeasure-UPS\nUpper temp\nlimit\nNO,NO\nDegrees C. Writable Variable. Possible\nvalues: 55, 50, 45, …, 05.\nUse +/- to change values.","html":"[[[[\nMeasure-UPS\nUpper temp\nlimit\nNO,NO\nDegrees C. Writable Variable. Possible\nvalues: 55, 50, 45, …, 05.\nUse +/- to change values.
"},{"id":"text-195","type":"text","heading":"","plain_text":"]\nMeasure-UPS\nlower temp\nlimit\nNO,NO\nDegrees C. Writable Variable. Possible\nvalues: 55, 50, 45, …, 05.\nUse +/- to change values.","html":"]\nMeasure-UPS\nlower temp\nlimit\nNO,NO\nDegrees C. Writable Variable. Possible\nvalues: 55, 50, 45, …, 05.\nUse +/- to change values.
"},{"id":"text-196","type":"text","heading":"","plain_text":"Measure-UPS\nUpper\nhumidity\nlimit\nNO,NO\nPercentage. Writable Variable.\nPossible values: 90, 80, 70, …, 10.\nUse +/- to change values.","html":"Measure-UPS\nUpper\nhumidity\nlimit\nNO,NO\nPercentage. Writable Variable.\nPossible values: 90, 80, 70, …, 10.\nUse +/- to change values.
"},{"id":"text-197","type":"text","heading":"","plain_text":"Measure-UPS\nlower\nhumidity\nlimit\nNO,NO\nPercentage. Writable Variable.\nPossible values: 90, 80, 70, …, 10.\nUse +/- to change values.","html":"Measure-UPS\nlower\nhumidity\nlimit\nNO,NO\nPercentage. Writable Variable.\nPossible values: 90, 80, 70, …, 10.\nUse +/- to change values.
"},{"id":"text-198","type":"text","heading":"","plain_text":"Matrix-UPS and Symmetra Commands","html":"Matrix-UPS and Symmetra Commands
"},{"id":"text-199","type":"text","heading":"","plain_text":"^\nRun in\nbypass mode\nBYP, INV, ERR\nIf online, "BYP" response is received\nas bypass mode starts. If already in\nbypass, "INV" is received and UPS goes\nonline. If UPS can't transfer, "ERR"\nreceived","html":"^\nRun in\nbypass mode\nBYP, INV, ERR\nIf online, "BYP" response is received\nas bypass mode starts. If already in\nbypass, "INV" is received and UPS goes\nonline. If UPS can't transfer, "ERR"\nreceived
"},{"id":"text-200","type":"text","heading":"","plain_text":"<\nNumber of\nbad battery\npacks\n000\nCount of bad packs connected to the\nUPS","html":"<\nNumber of\nbad battery\npacks\n000\nCount of bad packs connected to the\nUPS
"},{"id":"text-201","type":"text","heading":"","plain_text":"/\nLoad current\nnn.nn\nTrue RMS load current drawn by UPS","html":"/\nLoad current\nnn.nn\nTrue RMS load current drawn by UPS
"},{"id":"text-202","type":"text","heading":"","plain_text":"Apparent\nload power\nnnn.nn\nOutput load as percentage of full\nrated load in VA.","html":"Apparent\nload power\nnnn.nn\nOutput load as percentage of full\nrated load in VA.
"},{"id":"text-203","type":"text","heading":"","plain_text":"^V\nOutput\nvoltage\nselection","html":"^V\nOutput\nvoltage\nselection
"},{"id":"text-204","type":"text","heading":"","plain_text":"Writable variable. Possible values:","html":"Writable variable. Possible values:
"},{"id":"text-205","type":"text","heading":"","plain_text":"A = automatic (based on input tap)\nM = 208 VAC\nI = 240 VAC","html":"A = automatic (based on input tap)\nM = 208 VAC\nI = 240 VAC
"},{"id":"text-206","type":"text","heading":"","plain_text":"^L\nFront panel\nlanguage","html":"^L\nFront panel\nlanguage
"},{"id":"text-207","type":"text","heading":"","plain_text":"Writable variable. Possible values:","html":"Writable variable. Possible values:
"},{"id":"text-208","type":"text","heading":"","plain_text":"E = English\nF = French\nG = German\nS = Spanish\n1 = unknown\n2 = unknown\n3 = unknown\n4 = unknown","html":"E = English\nF = French\nG = German\nS = Spanish\n1 = unknown\n2 = unknown\n3 = unknown\n4 = unknown
"},{"id":"text-209","type":"text","heading":"","plain_text":"w\nRun time\nconservation","html":"w\nRun time\nconservation
"},{"id":"text-210","type":"text","heading":"","plain_text":"Writable variable. Minutes of runtime\nto leave in battery (UPS shuts down\n"early"). Possible values:","html":"Writable variable. Minutes of runtime\nto leave in battery (UPS shuts down\n"early"). Possible values:
"},{"id":"text-211","type":"text","heading":"","plain_text":"NO = disabled\n02 = leave 2 minutes of runtime\n05 = leave 5 minutes\n08 = leave 8 minutes","html":"NO = disabled\n02 = leave 2 minutes of runtime\n05 = leave 5 minutes\n08 = leave 8 minutes
"},{"id":"text-212","type":"text","heading":"","plain_text":"Dip switch info","html":"Dip switch info
"},{"id":"text-213","type":"text","heading":"","plain_text":"Bit\nCommutateur\nOption when bit=1","html":"Bit\nCommutateur\nOption when bit=1
"},{"id":"text-214","type":"text","heading":"","plain_text":"0\n4\nLow battery alarm changed from 2 to 5 mins. Autostartup disabled on\nSU370ci and 400","html":"0\n4\nLow battery alarm changed from 2 to 5 mins. Autostartup disabled on\nSU370ci and 400
"},{"id":"text-215","type":"text","heading":"","plain_text":"1\n3\nAudible alarm delayed 30 seconds","html":"1\n3\nAudible alarm delayed 30 seconds
"},{"id":"text-216","type":"text","heading":"","plain_text":"2\n2\nOutput transfer set to 115 VAC (from 120 VAC) or to 240 VAC (from\n230 VAC)","html":"2\n2\nOutput transfer set to 115 VAC (from 120 VAC) or to 240 VAC (from\n230 VAC)
"},{"id":"text-217","type":"text","heading":"","plain_text":"3\n1\nUPS desensitized – input voltage range expanded","html":"3\n1\nUPS desensitized – input voltage range expanded
"},{"id":"text-218","type":"text","heading":"","plain_text":"4-7\n \nUnused at this time","html":"4-7\n \nUnused at this time
"},{"id":"text-219","type":"text","heading":"","plain_text":"Status bits\nThis is probably the most important register of the UPS, which\nindicates the overall UPS status. Some common things you'll see:","html":"Status bits\nThis is probably the most important register of the UPS, which\nindicates the overall UPS status. Some common things you'll see:
"},{"id":"text-220","type":"text","heading":"","plain_text":"08 = On line, battery OK\n10 = On battery, battery OK\n50 = On battery, battery low\nSM = Status bit is still not available (retry reading)","html":"08 = On line, battery OK\n10 = On battery, battery OK\n50 = On battery, battery low\nSM = Status bit is still not available (retry reading)
"},{"id":"text-221","type":"text","heading":"","plain_text":"Bit\nMeaning when bit=1","html":"Bit\nMeaning when bit=1
"},{"id":"text-222","type":"text","heading":"","plain_text":"0\nRuntime calibration occurring\n(Not reported by Smart UPS v/s and BackUPS Pro)","html":"0\nRuntime calibration occurring\n(Not reported by Smart UPS v/s and BackUPS Pro)
"},{"id":"text-223","type":"text","heading":"","plain_text":"1\nSmartTrim (Not reported by 1st and 2nd generation SmartUPS models)","html":"1\nSmartTrim (Not reported by 1st and 2nd generation SmartUPS models)
"},{"id":"text-224","type":"text","heading":"","plain_text":"2\nSmartBoost","html":"2\nSmartBoost
"},{"id":"text-225","type":"text","heading":"","plain_text":"3\nOn line (this is the normal condition)","html":"3\nOn line (this is the normal condition)
"},{"id":"text-226","type":"text","heading":"","plain_text":"4\nOn battery","html":"4\nOn battery
"},{"id":"text-227","type":"text","heading":"","plain_text":"5\nOverloaded output","html":"5\nOverloaded output
"},{"id":"text-228","type":"text","heading":"","plain_text":"6\nBattery low","html":"6\nBattery low
"},{"id":"text-229","type":"text","heading":"","plain_text":"sept\nReplace battery","html":"sept\nReplace battery
"},{"id":"text-230","type":"text","heading":"","plain_text":"Alert messages\nThese single character messages are sent by the UPS any time there\nis an Alert condition. All other responses indicated above are sent\nby the UPS only in response to a query or action command.","html":"Alert messages\nThese single character messages are sent by the UPS any time there\nis an Alert condition. All other responses indicated above are sent\nby the UPS only in response to a query or action command.
"},{"id":"text-231","type":"text","heading":"","plain_text":"Personnage\nSens\nLa description","html":"Personnage\nSens\nLa description
"},{"id":"text-232","type":"text","heading":"","plain_text":"!\nLine Fail\nSent when the UPS goes on-battery, repeated every 30\nseconds until low battery condition reached. quelquefois\noccurs more than once in the first 30 seconds.","html":"!\nLine Fail\nSent when the UPS goes on-battery, repeated every 30\nseconds until low battery condition reached. quelquefois\noccurs more than once in the first 30 seconds.
"},{"id":"text-233","type":"text","heading":"","plain_text":"$\nReturn from\nline fail\nUPS back on line power. Only sent if a ! has been sent\npreviously.","html":"$\nReturn from\nline fail\nUPS back on line power. Only sent if a ! has been sent\npreviously.
"},{"id":"text-234","type":"text","heading":"","plain_text":"%\nLow battery\nSent to indicate low battery. Not implemented on\nSmartUPS v/s or BackUPS Pro models","html":"%\nLow battery\nSent to indicate low battery. Not implemented on\nSmartUPS v/s or BackUPS Pro models
"},{"id":"text-235","type":"text","heading":"","plain_text":"+\nReturn from\nlow batt\nSent when the battery has been recharged to some level\nOnly sent if a % has been sent previously.","html":"+\nReturn from\nlow batt\nSent when the battery has been recharged to some level\nOnly sent if a % has been sent previously.
"},{"id":"text-236","type":"text","heading":"","plain_text":"?\nAbnormal\nétat\nSent for conditions such as "shutdown due to overload"\nor "shutdown due to low battery capacity". Also occurs\nwithin 10 minutes of turnon.","html":"?\nAbnormal\nétat\nSent for conditions such as "shutdown due to overload"\nor "shutdown due to low battery capacity". Also occurs\nwithin 10 minutes of turnon.
"},{"id":"text-237","type":"text","heading":"","plain_text":"=\nReturn from\nabnormal\nétat\nSent when the UPS returns from an abnormal condition\nwhere ? was sent, but not a turn-on. Not implemented on\nSmartUPS v/s or BackUPS Pro models.","html":"=\nReturn from\nabnormal\nétat\nSent when the UPS returns from an abnormal condition\nwhere ? was sent, but not a turn-on. Not implemented on\nSmartUPS v/s or BackUPS Pro models.
"},{"id":"text-238","type":"text","heading":"","plain_text":"*\nAbout to\nturn off\nSent when the UPS is about to switch off the load. Non\ncommands are processed after this character is sent. ne pas\nimplemented on SmartUPS v/s, BackUPS Pro, or 3rd\ngeneration SmartUPS models.","html":"*\nAbout to\nturn off\nSent when the UPS is about to switch off the load. Non\ncommands are processed after this character is sent. ne pas\nimplemented on SmartUPS v/s, BackUPS Pro, or 3rd\ngeneration SmartUPS models.
"},{"id":"text-239","type":"text","heading":"","plain_text":"#\nRemplacer\nbatterie\nSent when the UPS detects that the battery needs to be\nreplaced. Sent every 5 hours until a new battery test is\nrun or the UPS is shut off. Not implemented on SmartUPS\nv/s or BackUPS Pro models.","html":"#\nRemplacer\nbatterie\nSent when the UPS detects that the battery needs to be\nreplaced. Sent every 5 hours until a new battery test is\nrun or the UPS is shut off. Not implemented on SmartUPS\nv/s or BackUPS Pro models.
"},{"id":"text-240","type":"text","heading":"","plain_text":"Et\nCheck alarm\nregister\nfor fault\n(Measure-UPS)\nSent to signal that temp or humidity out of set limits.\nAlso sent when one of the contact closures changes\nEtat. Sent every 2 minutes until the alarm conditions\nare reset. Only sent for alarms enabled with I. Cause of\nalarm may be determined with J. Not implemented on\nSmartUPS v/s or BackUPS Pro.","html":"Et\nCheck alarm\nregister\nfor fault\n(Measure-UPS)\nSent to signal that temp or humidity out of set limits.\nAlso sent when one of the contact closures changes\nEtat. Sent every 2 minutes until the alarm conditions\nare reset. Only sent for alarms enabled with I. Cause of\nalarm may be determined with J. Not implemented on\nSmartUPS v/s or BackUPS Pro.
"},{"id":"text-241","type":"text","heading":"","plain_text":"|\nVariable\nchange in\nEEPROM\nSent whenever any EEPROM variable is changed. Only\nsupported on Matrix UPS and 3rd generation SmartUPS\nmodels.","html":"|\nVariable\nchange in\nEEPROM\nSent whenever any EEPROM variable is changed. Only\nsupported on Matrix UPS and 3rd generation SmartUPS\nmodels.
"},{"id":"text-242","type":"text","heading":"","plain_text":"Register 1\nAll bits are valid on the Matrix UPS. SmartUPS models only support\nbits 6 and 7. Other models do not respond.","html":"Register 1\nAll bits are valid on the Matrix UPS. SmartUPS models only support\nbits 6 and 7. Other models do not respond.
"},{"id":"text-243","type":"text","heading":"","plain_text":"Bit\nMeaning when bit=1","html":"Bit\nMeaning when bit=1
"},{"id":"text-244","type":"text","heading":"","plain_text":"0\nIn wakeup mode (typically lasts < 2s)","html":"0\nIn wakeup mode (typically lasts < 2s)
"},{"id":"text-245","type":"text","heading":"","plain_text":"1\nIn bypass mode due to internal fault (see Register 2 or Register 3)","html":"1\nIn bypass mode due to internal fault (see Register 2 or Register 3)
"},{"id":"text-246","type":"text","heading":"","plain_text":"2\nGoing to bypass mode due to command","html":"2\nGoing to bypass mode due to command
"},{"id":"text-247","type":"text","heading":"","plain_text":"3\nIn bypass mode due to command","html":"3\nIn bypass mode due to command
"},{"id":"text-248","type":"text","heading":"","plain_text":"4\nReturning from bypass mode","html":"4\nReturning from bypass mode
"},{"id":"text-249","type":"text","heading":"","plain_text":"5\nIn bypass mode due to manual bypass control","html":"5\nIn bypass mode due to manual bypass control
"},{"id":"text-250","type":"text","heading":"","plain_text":"6\nReady to power load on user command","html":"6\nReady to power load on user command
"},{"id":"text-251","type":"text","heading":"","plain_text":"sept\nReady to power load on user command or return of line power","html":"sept\nReady to power load on user command or return of line power
"},{"id":"text-252","type":"text","heading":"","plain_text":"Register 2\nMatrix UPS models report bits 0-5. SmartUPS models only support\nbits 4-6. SmartUPS v/s and BackUPS Pro report bits 4, 6, 7.\nUnused bits are set to 0. Other models do not respond.","html":"Register 2\nMatrix UPS models report bits 0-5. SmartUPS models only support\nbits 4-6. SmartUPS v/s and BackUPS Pro report bits 4, 6, 7.\nUnused bits are set to 0. Other models do not respond.
"},{"id":"text-253","type":"text","heading":"","plain_text":"Bit\nMeaning when bit=1","html":"Bit\nMeaning when bit=1
"},{"id":"text-254","type":"text","heading":"","plain_text":"0\nFan failure in electronics, UPS in bypass","html":"0\nFan failure in electronics, UPS in bypass
"},{"id":"text-255","type":"text","heading":"","plain_text":"1\nFan failure in isolation unit","html":"1\nFan failure in isolation unit
"},{"id":"text-256","type":"text","heading":"","plain_text":"2\nBypass supply failure","html":"2\nBypass supply failure
"},{"id":"text-257","type":"text","heading":"","plain_text":"3\nOutput voltage select failure, UPS in bypass","html":"3\nOutput voltage select failure, UPS in bypass
"},{"id":"text-258","type":"text","heading":"","plain_text":"4\nDC imbalance, UPS in bypass","html":"4\nDC imbalance, UPS in bypass
"},{"id":"text-259","type":"text","heading":"","plain_text":"5\nBattery is disconnected","html":"5\nBattery is disconnected
"},{"id":"text-260","type":"text","heading":"","plain_text":"6\nRelay fault in SmartTrim or SmartBoost","html":"6\nRelay fault in SmartTrim or SmartBoost
"},{"id":"text-261","type":"text","heading":"","plain_text":"sept\nBad output voltage","html":"sept\nBad output voltage
"},{"id":"text-262","type":"text","heading":"","plain_text":"Register 3\nAll bits are valid on the Matrix UPS and 3rd generation SmartUPS\nmodels. SmartUPS v/s and BackUPS Pro models report bits 0-5. Tout\nothers report 0-4. State change of bits 1,2,5,6,7 are reported\nasynchronously with ? and = messages.","html":"Register 3\nAll bits are valid on the Matrix UPS and 3rd generation SmartUPS\nmodels. SmartUPS v/s and BackUPS Pro models report bits 0-5. Tout\nothers report 0-4. State change of bits 1,2,5,6,7 are reported\nasynchronously with ? and = messages.
"},{"id":"text-263","type":"text","heading":"","plain_text":"Bit\nMeaning when bit=1","html":"Bit\nMeaning when bit=1
"},{"id":"text-264","type":"text","heading":"","plain_text":"0\nOutput unpowered due to shutdown by low battery","html":"0\nOutput unpowered due to shutdown by low battery
"},{"id":"text-265","type":"text","heading":"","plain_text":"1\nUnable to transfer to battery due to overload","html":"1\nUnable to transfer to battery due to overload
"},{"id":"text-266","type":"text","heading":"","plain_text":"2\nMain relay malfunction – UPS turned off","html":"2\nMain relay malfunction – UPS turned off
"},{"id":"text-267","type":"text","heading":"","plain_text":"3\nIn sleep mode from @ command (maybe others)","html":"3\nIn sleep mode from @ command (maybe others)
"},{"id":"text-268","type":"text","heading":"","plain_text":"4\nIn shutdown mode from S command","html":"4\nIn shutdown mode from S command
"},{"id":"text-269","type":"text","heading":"","plain_text":"5\nBattery charger failure","html":"5\nBattery charger failure
"},{"id":"text-270","type":"text","heading":"","plain_text":"6\nBypass relay malfunction","html":"6\nBypass relay malfunction
"},{"id":"text-271","type":"text","heading":"","plain_text":"sept\nNormal operating temperature exceeded","html":"sept\nNormal operating temperature exceeded
"},{"id":"text-272","type":"text","heading":"","plain_text":"Interpretation of the Old Firmware Revision\nThe Old Firmware Revision is obtained with the "V" command, which\ngives a typical response such as "GWD" or "IWI", and can be\ninterpreted as follows:","html":"Interpretation of the Old Firmware Revision\nThe Old Firmware Revision is obtained with the "V" command, which\ngives a typical response such as "GWD" or "IWI", and can be\ninterpreted as follows:
"},{"id":"text-273","type":"text","heading":"","plain_text":"Old Firmware revision and model ID String for SmartUPS & MatrixUPS","html":"Old Firmware revision and model ID String for SmartUPS & MatrixUPS
"},{"id":"text-274","type":"text","heading":"","plain_text":"This is a three character string XYZ","html":"This is a three character string XYZ
"},{"id":"text-275","type":"text","heading":"","plain_text":" where X == Smart-UPS or Matrix-UPS ID Code.\n range 0-9 and A-P\n 1 == unknown\n 0 == Matrix 3000\n 5 == Matrix 5000\n the rest are Smart-UPS and Smart-UPS-XL\n 2 == 250 3 == 400 4 == 400\n 6 == 600 7 == 900 8 == 1250\n 9 == 2000 A == 1400 B == 1000\n C == 650 D == 420 E == 280\n F == 450 G == 700 H == 700XL\n I == 1000 J == 1000XL K == 1400\n L == 1400XL M == 2200 N == 2200XL\n O == 3000 P == 5000","html":"where X == Smart-UPS or Matrix-UPS ID Code.\n range 0-9 and A-P\n 1 == unknown\n 0 == Matrix 3000\n 5 == Matrix 5000\n the rest are Smart-UPS and Smart-UPS-XL\n 2 == 250 3 == 400 4 == 400\n 6 == 600 7 == 900 8 == 1250\n 9 == 2000 A == 1400 B == 1000\n C == 650 D == 420 E == 280\n F == 450 G == 700 H == 700XL\n I == 1000 J == 1000XL K == 1400\n L == 1400XL M == 2200 N == 2200XL\n O == 3000 P == 5000
"},{"id":"text-276","type":"text","heading":"","plain_text":" where Y == Possible Level of Smart Features, unknown???\n G == Stand Alone\n T == Stand Alone\n V == ???\n W == Rack Mount","html":"where Y == Possible Level of Smart Features, unknown???\n G == Stand Alone\n T == Stand Alone\n V == ???\n W == Rack Mount
"},{"id":"text-277","type":"text","heading":"","plain_text":" where Z == National Model Use Only Codes\n D == Domestic 115 Volts\n I == International 230 Volts\n A == Asia ?? 100 Volts\n J == Japan ?? 100 Volts","html":"where Z == National Model Use Only Codes\n D == Domestic 115 Volts\n I == International 230 Volts\n A == Asia ?? 100 Volts\n J == Japan ?? 100 Volts
"},{"id":"text-278","type":"text","heading":"","plain_text":"Interpretation of the New Firmware Revision","html":"Interpretation of the New Firmware Revision
"},{"id":"text-279","type":"text","heading":"","plain_text":"New Firmware revision and model ID String in NN.M.L is the format","html":"New Firmware revision and model ID String in NN.M.L is the format
"},{"id":"text-280","type":"text","heading":"","plain_text":" where NN == UPS ID Code.\n 12 == Back-UPS Pro 650\n 13 == Back-UPS Pro 1000\n 52 == Smart-UPS 700\n 60 == SmartUPS 1000\n 72 == Smart-UPS 1400","html":"where NN == UPS ID Code.\n 12 == Back-UPS Pro 650\n 13 == Back-UPS Pro 1000\n 52 == Smart-UPS 700\n 60 == SmartUPS 1000\n 72 == Smart-UPS 1400
"},{"id":"text-281","type":"text","heading":"","plain_text":" where NN now Nn has possible meanings.\n N == Class of UPS\n 1n == Back-UPS Pro\n 5n == Smart-UPS\n 7n == Smart-UPS NET","html":"where NN now Nn has possible meanings.\n N == Class of UPS\n 1n == Back-UPS Pro\n 5n == Smart-UPS\n 7n == Smart-UPS NET
"},{"id":"text-282","type":"text","heading":"","plain_text":" n == Level of intelligence\n N1 == Simple Signal, if detectable WAG(*)\n N2 == Full Set of Smart Signals\n N3 == Micro Subset of Smart Signals","html":"n == Level of intelligence\n N1 == Simple Signal, if detectable WAG(*)\n N2 == Full Set of Smart Signals\n N3 == Micro Subset of Smart Signals
"},{"id":"text-283","type":"text","heading":"","plain_text":" where M == Possible Level of Smart Features, unknown???\n 1 == Stand Alone\n 8 == Rack Mount\n 9 == Rack Mount","html":"where M == Possible Level of Smart Features, unknown???\n 1 == Stand Alone\n 8 == Rack Mount\n 9 == Rack Mount
"},{"id":"text-284","type":"text","heading":"","plain_text":" where L == National Model Use Only Codes\n D == Domestic 115 Volts\n I == International 230 Volts\n A == Asia ?? 100 Volts\n J == Japan ?? 100 Volts\n M == North America 208 Volts (Servers)","html":"where L == National Model Use Only Codes\n D == Domestic 115 Volts\n I == International 230 Volts\n A == Asia ?? 100 Volts\n J == Japan ?? 100 Volts\n M == North America 208 Volts (Servers)
"},{"id":"text-285","type":"text","heading":"","plain_text":"EEPROM Values\nUpon sending a ^Z, your UPS will probably spit back approximately\n254 characters something like the following (truncated here for the\nexample):","html":"EEPROM Values\nUpon sending a ^Z, your UPS will probably spit back approximately\n254 characters something like the following (truncated here for the\nexample):
"},{"id":"text-286","type":"text","heading":"","plain_text":"#uD43132135138129uM43229234239224uA43110112114108 ....","html":"#uD43132135138129uM43229234239224uA43110112114108 ....
"},{"id":"text-287","type":"text","heading":"","plain_text":"It looks bizarre and ugly, but is easily parsed. The # is some kind\nof marker/ident character. Skip it. The rest fits this form:","html":"It looks bizarre and ugly, but is easily parsed. The # is some kind\nof marker/ident character. Skip it. The rest fits this form:
"},{"id":"text-288","type":"text","heading":"","plain_text":"Command character – use this to select the value\nLocale – use 'b' to find out what yours is (the last character),\n'4' applies to all\nNumber of choices – '4' means there are 4 possibilities coming\nen haut\nChoice length – '3' means they are all 3 chars long","html":"Command character – use this to select the value\nLocale – use 'b' to find out what yours is (the last character),\n'4' applies to all\nNumber of choices – '4' means there are 4 possibilities coming\nen haut\nChoice length – '3' means they are all 3 chars long
"},{"id":"text-289","type":"text","heading":"","plain_text":"Then it's followed by the choices, and it starts over.\nMatrix-UPS models have ## between each grouping for some reason.\nHere is an example broken out to be more readable:","html":"Then it's followed by the choices, and it starts over.\nMatrix-UPS models have ## between each grouping for some reason.\nHere is an example broken out to be more readable:
"},{"id":"text-290","type":"text","heading":"","plain_text":"CMD DFO RSP FSZ FVL\nu D 4 3 127 130 133 136\nu M 4 3 229 234 239 224\nu A 4 3 108 110 112 114\nu I 4 3 253 257 261 265\nl D 4 3 106 103 100 097\nl M 4 3 177 172 168 182\nl A 4 3 092 090 088 086\nl I 4 3 208 204 200 196\ne 4 4 2 00 15 50 90\no D 1 3 115\no J 1 3 100\no I 1 3 230 240 220 225\no M 1 3 208\ns 4 4 1 H M L L\nq 4 4 2 02 05 07 10\np 4 4 3 020 180 300 600\nk 4 4 1 0 T L N\nr 4 4 3 000 060 180 300\nE 4 4 3 336 168 ON OFF","html":"CMD DFO RSP FSZ FVL\nu D 4 3 127 130 133 136\nu M 4 3 229 234 239 224\nu A 4 3 108 110 112 114\nu I 4 3 253 257 261 265\nl D 4 3 106 103 100 097\nl M 4 3 177 172 168 182\nl A 4 3 092 090 088 086\nl I 4 3 208 204 200 196\ne 4 4 2 00 15 50 90\no D 1 3 115\no J 1 3 100\no I 1 3 230 240 220 225\no M 1 3 208\ns 4 4 1 H M L L\nq 4 4 2 02 05 07 10\np 4 4 3 020 180 300 600\nk 4 4 1 0 T L N\nr 4 4 3 000 060 180 300\nE 4 4 3 336 168 ON OFF
"},{"id":"text-291","type":"text","heading":"","plain_text":"CMD == UPSlink Command.\n u = upper transfer voltage\n l = lower transfer voltage\n e = return threshold\n o = output voltage\n s = sensitivity\n p = shutdown grace delay\n q = low battery warning\n k = alarm delay\n r = wakeup delay\n E = self test interval","html":"CMD == UPSlink Command.\n u = upper transfer voltage\n l = lower transfer voltage\n e = return threshold\n o = output voltage\n s = sensitivity\n p = shutdown grace delay\n q = low battery warning\n k = alarm delay\n r = wakeup delay\n E = self test interval
"},{"id":"text-292","type":"text","heading":"","plain_text":"DFO == (4)-all-countries (D)omestic (I)nternational (A)sia (J)apan\n (M) North America - servers.\nRSP == Total number possible answers returned by a given CMD.\nFSZ == Max. number of field positions to be filled.\nFVL == Values that are returned and legal.","html":"DFO == (4)-all-countries (D)omestic (I)nternational (A)sia (J)apan\n (M) North America - servers.\nRSP == Total number possible answers returned by a given CMD.\nFSZ == Max. number of field positions to be filled.\nFVL == Values that are returned and legal.
"},{"id":"text-293","type":"text","heading":"","plain_text":"Programming the UPS EEPROM\nThere are at this time a maximum of 12 different values that can be\nprogrammed into the UPS EEPROM. They are:","html":"Programming the UPS EEPROM\nThere are at this time a maximum of 12 different values that can be\nprogrammed into the UPS EEPROM. They are:
"},{"id":"text-294","type":"text","heading":"","plain_text":"Commander\nSens","html":"Commander\nSens
"},{"id":"text-295","type":"text","heading":"","plain_text":"c\nThe UPS Id or name","html":"c\nThe UPS Id or name
"},{"id":"text-296","type":"text","heading":"","plain_text":"X\nThe last date the batteries were replaced","html":"X\nThe last date the batteries were replaced
"},{"id":"text-297","type":"text","heading":"","plain_text":"vous\nThe Upper Transfer Voltage","html":"vous\nThe Upper Transfer Voltage
"},{"id":"text-298","type":"text","heading":"","plain_text":"l\nThe Lower Transfer Voltage","html":"l\nThe Lower Transfer Voltage
"},{"id":"text-299","type":"text","heading":"","plain_text":"e\nThe Return Battery Charge Percentage","html":"e\nThe Return Battery Charge Percentage
"},{"id":"text-300","type":"text","heading":"","plain_text":"o\nThe Output Voltage when on Batteries","html":"o\nThe Output Voltage when on Batteries
"},{"id":"text-301","type":"text","heading":"","plain_text":"s\nThe Sensitivity to Line Quality","html":"s\nThe Sensitivity to Line Quality
"},{"id":"text-302","type":"text","heading":"","plain_text":"p\nThe Shutdown Grace Delay","html":"p\nThe Shutdown Grace Delay
"},{"id":"text-303","type":"text","heading":"","plain_text":"q\nThe Low Battery Warning Delay","html":"q\nThe Low Battery Warning Delay
"},{"id":"text-304","type":"text","heading":"","plain_text":"k\nThe Alarm Delay","html":"k\nThe Alarm Delay
"},{"id":"text-305","type":"text","heading":"","plain_text":"r\nThe Wakeup Delay","html":"r\nThe Wakeup Delay
"},{"id":"text-306","type":"text","heading":"","plain_text":"E\nThe Automatic Self Test Interval","html":"E\nThe Automatic Self Test Interval
"},{"id":"text-307","type":"text","heading":"","plain_text":"The first two cases (Ident and Batt date) are somewhat special in\nthat you tell the UPS you want to change the value, then you supply\n8 characters that are saved in the EEPROM. The last ten item are\nprogrammed by telling the UPS that you want it to cycle to the next\npermitted value.\nIn each case, you indicate to the UPS that you want to change the\nEEPROM by first sending the appropriate query command (e.g. "c" for\nthe UPS ID or "u" for the Upper Transfer voltage. This command is\nthen immediately followed by the cycle EEPROM command or "-". Dans\nthe case of the UPS Id or the battery date, you follow the cycle\ncommand by the eight characters that you want to put in the EEPROM.\nIn the case of the other ten items, there is nothing more to\nenter.\nThe UPS will respond by "OK" and approximately 5 seconds later by a\nvertical bar (|) to indicate that the EEPROM was changed.","html":"The first two cases (Ident and Batt date) are somewhat special in\nthat you tell the UPS you want to change the value, then you supply\n8 characters that are saved in the EEPROM. The last ten item are\nprogrammed by telling the UPS that you want it to cycle to the next\npermitted value.\nIn each case, you indicate to the UPS that you want to change the\nEEPROM by first sending the appropriate query command (e.g. "c" for\nthe UPS ID or "u" for the Upper Transfer voltage. This command is\nthen immediately followed by the cycle EEPROM command or "-". Dans\nthe case of the UPS Id or the battery date, you follow the cycle\ncommand by the eight characters that you want to put in the EEPROM.\nIn the case of the other ten items, there is nothing more to\nenter.\nThe UPS will respond by "OK" and approximately 5 seconds later by a\nvertical bar (|) to indicate that the EEPROM was changed.
"},{"id":"text-308","type":"text","heading":"","plain_text":"Click to rate this post!\n \n [Total: 0 Average: 0]","html":"Click to rate this post!\n \n [Total: 0 Average: 0]
"}],"sections":[{"id":"text-1","heading":"Text","content":"Apcupsd est un système de contrôle UPS qui permet l’arrêt méthodique de votre\nordinateur en cas de panne de courant.\nCopie et distribution de ce fichier, avec ou sans modification,\nsont autorisés sur n'importe quel support sans redevance à condition d'appeler le nom Apcupsd,\nla notice de copyright, et cette notice sont préservées.\nLe code source d'Apcupsd est publié sous licence GNU General Public License\nversion 2. Veuillez voir le fichier COPYING dans le répertoire source principal.\nPour plus d'informations sur le projet, veuillez visiter le site web principal\nau http://www.apcupsd.com"},{"id":"text-2","heading":"Text","content":"Personne ne devrait s’appuyer sur le contenu du manuel de l’APCUPSD («le manuel»)\nsans avoir au préalable obtenu l’avis du support technique APC.\nLe manuel est fourni sur les termes et comprendre que:"},{"id":"text-3","heading":"Text","content":"les auteurs, contributeurs et éditeurs ne sont pas responsables de la\nles résultats des actions entreprises sur la base des informations contenues dans le manuel,\nni pour toute erreur ou omission dans le manuel; et\nles auteurs, contributeurs et éditeurs ne sont pas impliqués dans le rendu\nconseils ou services techniques ou autres."},{"id":"text-4","heading":"Text","content":"Les auteurs, contributeurs et éditeurs, déclinent expressément tout et tout\nresponsabilité envers toute personne, que ce soit un lecteur du manuel\nou non, à l'égard de quoi que ce soit, et des conséquences de quoi que ce soit, fait ou\nomis par une telle personne en toute confiance, en tout ou en partie,\nsur tout ou partie du contenu du manuel. Sans limiter le\nla généralité de ce qui précède, aucun auteur, contributeur ou éditeur ne doit avoir\nresponsabilité pour tout acte ou omission de tout autre auteur, contributeur ou\néditeur."},{"id":"text-5","heading":"Text","content":"Ceci est le manuel pour apcupsd, un\ndémon pour la communication avec les UPS (Uninterruptible Power\nFournitures) fabriquées par American Power Conversion Corporation (APC). Si vous avez un\nLes onduleurs fabriqués par APC, qu’ils soient vendus sous la plaque signalétique APC ou OEM (par exemple, le\nPowerTrust 2997A), et vous voulez le faire fonctionner avec un ordinateur en marche\nLinux, Unix ou Windows, vous lisez le bon document.\nCe manuel est divisé en parties qui augmentent en profondeur technique\ncomme ils vont. Si vous venez d'acheter un onduleur à la pointe de la technologie\navec une interface USB ou Ethernet, et vous exécutez un courant\nversion de Red Hat ou SUSE Linux, alors apcupsd est\npresque plug-and-play et vous devrez lire que le De base\nGuide de l'utilisateur.\nSi votre système d’exploitation est plus ancien ou si vous avez un système démodé\nl’onduleur série, vous devrez vous renseigner sur l’installation en série (voir\nInstallation: Onduleurs de ligne série). Si vous avez besoin de plus\ndes détails sur l’administration dans des situations inhabituelles (comme un\nconfiguration maître / esclave ou multi-UPS), vous devez lire les sections sur\nces sujets aussi. Finalement,\nil existe un certain nombre de sections de référence techniques qui\ndonne des détails complets sur des choses comme les directives de fichier de configuration et\nformats de journalisation des événements.\nVous devriez commencer par lire le guide de démarrage rapide (voir Démarrage rapide pour\nDébutants) instructions."},{"id":"text-6","heading":"Text","content":"Démarrage rapide pour les débutants\napcupsd est un logiciel complexe, mais\nla plupart de ses complexités sont destinées à traiter avec du matériel ancien\net systèmes d'exploitation. Obtention du matériel et des logiciels actuels\ncourir ne devrait pas être très compliqué.\nCe qui suit est un guide d’aide sur les étapes à suivre pour obtenir apcupsd\nmis en place et en cours d'exécution aussi indolore que possible."},{"id":"text-7","heading":"Text","content":"Vérifiez si apcupsd prend en charge votre UPS et votre câble (voir\nUPS et câbles pris en charge).\nVérifiez si apcupsd prend en charge votre système d’exploitation (voir\nSystèmes d'exploitation pris en charge).\nPlanifiez votre type de configuration (voir Choisir une configuration\nType). Si vous avez juste un UPS et\nun ordinateur, c'est facile. Si vous avez plus d’une machine en cours de\ndesservi par le même UPS, ou par plus d’un UPS alimentant\nordinateurs qui sont sur le même réseau local, vous avez plus de choix\nfaire.\nDéterminez si vous avez l'une des configurations faciles. Si vous avez une clé USB\nUPS, et un système d'exploitation pris en charge et que vous souhaitez utiliser un UPS\navec un ordinateur, la configuration est simple. APC fournit le câble\nbesoin de parler avec cet UPS avec l'onduleur. Tout ce que vous devez faire\nvérifiez que votre sous-système USB fonctionne (voir USB\nConfiguration) si oui, vous pouvez aller à la construction\net installez l'étape.\nSi vous avez un onduleur conçu pour communiquer via SNMP via\nEthernet, c'est aussi une installation relativement facile. Détails\nsont fournis dans Assistance pour les onduleurs SNMP.\nSi vous avez un UPS qui communique via un port série RS232C\nl'interface et c'est un SmartUPS, alors les choses sont relativement simples,\nsinon, votre vie est sur le point de devenir intéressante."},{"id":"text-8","heading":"Text","content":"Si vous avez un câble fourni par le fournisseur, déterminez quel type de câble\nvous avez un numéro sur les extrémités plates du câble,\ncomme le 940-0020A, estampé dans le plastique.\nSi vous n'avez pas de câble fourni par le fournisseur ou si votre type n'est pas\nvous devrez peut-être en construire un vous-même (voir\nCâbles). Voici en espérant que tu es bon avec une soudure\nle fer!"},{"id":"text-9","heading":"Text","content":"Vous êtes maintenant prêt à lire le document Building and Install (voir\nConstruire et installer apcupsd)\nsection du manuel et suivez ces instructions. Si vous êtes\nl’installation à partir d’un RPM ou d’une autre forme de paquet binaire, cette\nL’étape consistera probablement à exécuter une seule commande.\nModifiez votre fichier /etc/apcupsd/apcupsd.conf si nécessaire. Souvent il\nne sera pas.\nModifiez les paramètres du BIOS (voir Organiser le redémarrage sur\nPower-Up) sur ton ordinateur\nde sorte que chaque démarrage, il démarre. (Ce n'est pas la valeur par défaut\nsur la plupart des systèmes.)\nPour vérifier que votre UPS communique avec votre ordinateur et\nva faire la bonne chose quand le courant est coupé, lire et suivre\nles instructions du test (voir Essai\nApcupsd) section.\nSi vous rencontrez des problèmes, consultez la liste de messagerie des utilisateurs d'apcupsd\narchive pour des problèmes similaires. C’est une excellente ressource avec\nréponses à toutes sortes de questions. Voir\nhttp://sourceforge.net/mailarchive/forum.php?forum_name=apcupsd-users.\nSi vous avez toujours besoin d'aide, envoyez un message au courrier électronique des utilisateurs d'apcupsd.\nliste (apcupsd-users@lists.sourceforge.net) décrivant votre\nproblème, quelle version de\napcupsd que vous utilisez, quel système d'exploitation vous utilisez et\ntout ce que vous pensez pourrait être utile.\nLisez la section du manuel sur la surveillance et le réglage de votre onduleur."},{"id":"text-10","heading":"Text","content":"Systèmes d'exploitation supportés\napcupsd prend en charge de nombreux systèmes d’exploitation de type UNIX, ainsi que plusieurs\nvariantes de Windows. En raison du manque de normalisation des API, la prise en charge USB n’est pas prise en charge.\ndisponible sur toutes les plateformes. Voir Support de la plateforme ci-dessous pour plus de détails.\nEn général, il est recommandé d’obtenir un paquet pré-construit pour votre plate-forme.\nCompte tenu de la manière dont apcupsd doit s’intégrer au mécanisme d’arrêt du\nsystème d’exploitation et la vitesse à laquelle ces mécanismes sont modifiés par\nfournisseurs, les ports de plate-forme de l’arborescence apcupsd peuvent devenir obsolètes. Dans\nDans certains cas, les paquets binaires sont fournis par l’équipe apcupsd (RedHat,\nMandriva, SuSE, Windows, Mac OS X). Pour les autres plateformes, il est recommandé de\nvérifier les référentiels de paquets de votre fournisseur et les référentiels tiers pour\npaquets binaires récents. Notez que certains fournisseurs continuent à distribuer\nanciennes versions de apcupsd avec des défauts connus. Ces paquets devraient ne pas être\nutilisé."},{"id":"text-11","heading":"Text","content":"Support de plate-forme\nLINUX"},{"id":"text-12","heading":"Text","content":"Chapeau rouge \nSuSE \nMandriva / Mandrake \nDebian \nSlackware \nEngarde \nChien jaune \nGentoo"},{"id":"text-13","heading":"Text","content":"LES FENÊTRES"},{"id":"text-14","heading":"Text","content":"Windows NT 4 \nWindows 98 / ME / 2000 \nWindows XP / Vista (y compris 64 bits) \nWindows Server 2003/2008 (64 bits inclus) \nWindows 7"},{"id":"text-15","heading":"Text","content":"AUTRES"},{"id":"text-16","heading":"Text","content":"Mac OS X Darwin \nSolaris 8/9 \nSolaris 10\nNetBSD\nFreeBSD\nOpenBSD\nHPUX \nUnifix \nQNX"},{"id":"text-17","heading":"Text","content":"UPS et câbles pris en charge\napcupsd prend en charge presque tous les modèles d'onduleurs APC existants et suffisamment\ndifférents types de câbles à connecter à chacun d’eux.\nle UPSTYPE le champ est la valeur que vous allez mettre en\nvotre fichier /etc/apcupsd/apcupsd.conf pour indiquer à apcupsd quel type d'onduleur\ntu as. Nous allons décrire les valeurs possibles ici, car ils sont\nun bon moyen d'expliquer l'interface la plus importante de votre UPS\npropriété: le type de protocole utilisé pour parler avec ses\nordinateur."},{"id":"text-18","heading":"Text","content":"apcsmart\nLe protocole 'apcsmart' utilise une connexion série RS232 pour passer\ncommandes dans un langage primitif ressemblant à\ncodes de contrôle du modem. APC appelle cette langue "UPS-Link". À l'origine\nintroduit pour les modèles Smart-UPS (d'où le nom «apcsmart»), cette\nla classe d'onduleurs est en déclin, elle est rapidement remplacée par le produit d'APC\nligne par UPS et MODBUS.\nUSB\nUn onduleur USB parle un contrôle universel bien défini\nla langue sur un fil USB. La plupart des membres d'APC utilisent maintenant cette méthode\nà la fin de 2003, et il semble probable qu’il prendra complètement le relais\nleur gamme basse et moyenne. Les derniers onduleurs APC ne prennent en charge qu’une\nensemble limité de données sur l'interface USB. MODBUS (voir ci-dessous) est requis\nafin d'accéder aux données avancées.\nnet\nC’est le mot clé pour spécifier si vous utilisez votre\nUPS en mode esclave (c’est-à-dire que la machine n’est pas directement connectée à\nl'onduleur, mais à une autre machine qui est), et il est connecté à\nle maître via une connexion ethernet. Vous devez avoir apcupsd's\nNetwork Information Services NIS activé pour que ce mode fonctionne.\nsnmp\nLes onduleurs SNMP communiquent via une carte réseau Ethernet et\nfirmware qui parle Simple Network Management Protocol.\nstupide\nUn onduleur muet ou à signalisation de tension et son ordinateur\ncommuniquer via les lignes de contrôle (pas les lignes de données) sur un RS232C\nconnexion série. Pas grand-chose ne peut être réellement transmis de cette façon autre que\nun ordre de fermeture. Les UPS de signalisation de tension sont obsolètes. toi\nsont peu susceptibles de rencontrer un autre que comme matériel hérité. Si vous\nSi vous avez le choix, nous vous recommandons d’éviter les simples UPS de signalisation.\npcnet\nPCNET est une alternative au SNMP disponible sur APC\nFamille AP9617 de modules de logement intelligent. Le protocole est beaucoup plus simple\net potentiellement plus sécurisé que SNMP.\nmodbus\nMODBUS est le dernier protocole APC et fonctionne sur des liaisons série RS232 ou\nUSB. MODBUS est le remplacement d'APC pour le 'apcsmart' (UPS-Link)\nprotocole. MODBUS est le seul moyen d'accéder à un contrôle et à un statut détaillés\ninformations sur les onduleurs les plus récents (en particulier ceux de la série SMT)."},{"id":"text-19","heading":"Text","content":"Choisir un type de configuration\nIl y a trois principaux\nmanières de faire fonctionner apcupsd sur votre système. Le premier est un autonome\nconfiguration où apcupsd contrôle un seul onduleur, qui alimente un\nordinateur unique. C'est la configuration la plus courante. Si vous êtes\ntravaillant avec une seule machine et un onduleur, ignorez le reste de cette\nsection.\nVos choix deviennent plus intéressants si vous utilisez un petit\ncluster ou une grande batterie de serveurs. Dans ces circonstances, il se peut que\nêtre possible ou même souhaitable de coupler un onduleur à chaque\nmachine. apcupsd prend en charge certains arrangements alternatifs.\nLe second type de configuration est le NIS (Network Information Information Network).\nServeur) serveur et client. Dans cette configuration, où un UPS\nalimente plusieurs ordinateurs, une copie d’apcupsd en exécutant un\nl'ordinateur agira en tant que serveur, tandis que les autres agiront en tant que\nclients du réseau qui interrogent le serveur pour obtenir des informations sur la\nUPS. Notez que "NIS" est ne pas liés au service d'annuaire de Sun\négalement appelé "NIS" ou "Pages Jaunes".\nLa troisième configuration est celle où un seul\nl'ordinateur contrôle plusieurs UPS. Dans ce cas, il y a plusieurs\ncas d’apcupsd sur le même ordinateur, chacun contrôlant un\ndifférent UPS. Une instance d’apcupsd s’exécutera en mode autonome, et\nl'autre instance fonctionnera normalement en mode réseau.\nCe type de configuration peut convenir aux gros serveurs\nexploitations utilisant une seule machine dédiée à la surveillance et à\nDiagnostique\nVoici un schéma qui résume les possibilités:"},{"id":"text-20","heading":"Text","content":"Types de configuration\n----------*----R4----*----< TxD (3)\n |\n | 1N4148\n *----K|---------< RTS (7) Shutdown"},{"id":"text-21","heading":"Text","content":"POWER-FAIL (2) >--------------------------< RxD,RI (2,9) On Batt"},{"id":"text-22","heading":"Text","content":"GROUND (4,9) >--------------------------< GND (5)"},{"id":"text-23","heading":"Text","content":"Operation:"},{"id":"text-24","heading":"Text","content":"DTR is "cable power" and must be held at SPACE. DSR or CTS may\nbe used as a loopback input to determine if the cable is plugged\ndans."},{"id":"text-25","heading":"Text","content":"DCD is the "battery low" signal to the computer. A SPACE on this\nline means the battery is low. This is signalled by BATTERY-LOW\nbeing pulled down (it is probably open circuit normally).\nNormally, the transistor is turned off, and DCD is held at the MARK\nvoltage by TxD. When BATTERY-LOW is pulled down, the voltage\ndivider R2/R1 biases the transistor so that it is turned on,\ncausing DCD to be pulled up to the SPACE voltage."},{"id":"text-26","heading":"Text","content":"TxD must be held at MARK; this is the default state when no data\nis being transmitted. This sets the default bias for both DCD and\nSHUTDOWN. If this line is an open circuit, then when BATTERY-LOW is\nsignalled, SHUTDOWN will be automatically signalled; this would be\ntrue if the cable were plugged in to the UPS and not the computer,\nor if the computer were turned off."},{"id":"text-27","heading":"Text","content":"RTS is the "shutdown" signal from the computer. A SPACE on this\nline tells the UPS to shut down."},{"id":"text-28","heading":"Text","content":"RxD and RI are both the "power-fail" signals to the computer. UNE\nMARK on this line means the power has failed."},{"id":"text-29","heading":"Text","content":"SPACE is a positive voltage, typically +12V. MARK is a negative\nvoltage, typically -12V. Linux appears to translate SPACE to a 1\nand MARK to a 0."},{"id":"text-30","heading":"Text","content":"940-0095B Cable Wiring"},{"id":"text-31","heading":"Text","content":"Supported Models:\nMany simple-signaling (aka voltage signaling)\nmodels such as BackUPS"},{"id":"text-32","heading":"Text","content":"This diagram is for informational purposes and may not be complete.\nWe don't recommend that use it to build you build one yourself."},{"id":"text-33","heading":"Text","content":"APC Part# - 940-0095B"},{"id":"text-34","heading":"Text","content":"Signal Computer UPS\n DB9F DB9M\n DTR 4 ----*\n CTS 8 ----|\n DSR 6 ----|\n DCD 1 ----*\n GND 5 ---------------*---- 4 Ground\n |\n *---- 9 Common\n RI 9 ----*\n |\n RxD 2 ----*--------------- 2 On Battery\n TxD 3 ----------[####]---- 1 Kill UPS Power\n 4.7K ohm"},{"id":"text-35","heading":"Text","content":"940-0119A Cable Wiring"},{"id":"text-36","heading":"Text","content":"Supported Models:\nOlder BackUPS Office"},{"id":"text-37","heading":"Text","content":"This diagram is for informational purposes and may not be complete.\nWe don't recommend that use it to build you build one yourself."},{"id":"text-38","heading":"Text","content":"APC Part# - 940-0119A"},{"id":"text-39","heading":"Text","content":" UPS Computer\n pins pins Signal Signal meaning\n1 (brown) 4,6 DSR DTR On battery power\n3 (blue) 1,2 CD RxD -> Low battery\n4 (red) 5 Ground\n5 (yellow) 7 RTS <- Begin signalling on other pins\n6 (none) none"},{"id":"text-40","heading":"Text","content":"Serial BackUPS ES Wiring"},{"id":"text-41","heading":"Text","content":"Supported Models:\nOlder Serial BackUPS ES"},{"id":"text-42","heading":"Text","content":"Contributed by:\nWilliam Stock"},{"id":"text-43","heading":"Text","content":"The BackUPS ES has a straight through serial cable with no\nidentification on the plugs. To make it work with apcupsd, specify\nthe UPSCABLE 940-0119A and UPSTYPE backups. The equivalent of\ncable 940-0119A is done on a PCB inside the unit."},{"id":"text-44","heading":"Text","content":"computer ----------- BackUPS-ES -----------------\nDB9-M DB-9F\npin signal pin"},{"id":"text-45","heading":"Text","content":" 4 DSR -> 4 --+\n | diode resistor\n 6 DTR -> 6 --+---->|----///---o kill power"},{"id":"text-46","heading":"Text","content":" 1 DCD <- 1 --+\n |\n 2 RxD 7 --------+--///--+\n |\n +--///--+\n |\n 8 RI <- 8 --+----------------+--o on battery\n |\n 9 CTS <- 9 --+"},{"id":"text-47","heading":"Text","content":" 5 GND --- 5 ----------------------o ground"},{"id":"text-48","heading":"Text","content":" 3 TxD 3 nc"},{"id":"text-49","heading":"Text","content":"940-0128A Cable Wiring"},{"id":"text-50","heading":"Text","content":"Supported Models:\nOlder USB BackUPS ES and CS"},{"id":"text-51","heading":"Text","content":"Contributed by:\nMany, thanks to all for your help!"},{"id":"text-52","heading":"Text","content":"Though these UPSes are USB UPSes, APC supplies a serial cable\n(typically with a green DB9 F connector) that has 940-0128A stamped\ninto one side of the plastic serial port connector. The other end\nof the cable is a 10 pin RJ45 connector that plugs into the UPS\n(thanks to Dean Waldow for sending a cable!). Apcupsd version 3.8.5\nand later supports this cable when specified as UPSCABLE\n940-0128A and UPSTYPE dumb. However, running in this mode much\nof the information that would be available in USB mode is lost. Dans\naddition, when apcupsd attempts to instruct the UPS to kill the\npower, it begins cycling about 4 times a second between battery and\nline. The solution to the problem (thanks to Tom Suzda) is to\nunplug the UPS and while it is still chattering, press the power\nbutton (on the front of the unit) until the unit beeps and the\nchattering stops. After that the UPS should behave normally and\npower down 1-2 minutes after requested to do so.\nThanks to all the people who have helped test this and have\nprovided information on the cable wiring, our best guess for the\ncable schematic is the following:"},{"id":"text-53","heading":"Text","content":"APC Part# - 940-0128A"},{"id":"text-54","heading":"Text","content":"computer --------- Inside the Connector--------- UPS\nDB9-F | | RJ45\npin - signal | | Pin - Color\n | |\n 4 DSR ->|---+ |\n | | diode resistor |\n 6 DTR ->|---+---->|----///---o kill power | 8 Orange\n | |\n 1 DCD <-|----+ |\n | | |\n 2 RxD |----------+--///--+ |\n | | |\n | +--///--+ |\n | | |\n 8 RI <-|----+----------------+--o on battery | 2 Black\n | | |\n 9 CTS <-|----+ |\n | signal |\n 5 GND --|-----------------------o ground | 7 Red\n | |\n 3 TxD | |\n | chassis |\n Chassis/GND |-----------------------o ground | 4 Black\n | |\n | Not connected | 1, 5, 6, 9, 10\n --------------------------------------"},{"id":"text-55","heading":"Text","content":"The RJ45 pins are: looking at the end of the connector:"},{"id":"text-56","heading":"Text","content":"10 9 8 7 6 5 4 3 2 1\n_______________________\n| . . . . . . . . . . |\n| |\n-----------------------\n |____|"},{"id":"text-57","heading":"Text","content":"940-0128D Cable Wiring"},{"id":"text-58","heading":"Text","content":"Supported Models:\nBackUPS XS1000(BX-1000), Possibly other USB models"},{"id":"text-59","heading":"Text","content":"Contributed by:\nJan Babinski jbabinsk at pulsarbeacon dot com"},{"id":"text-60","heading":"Text","content":"940-0128D is functionally similar to the 940-0128A cable except for\nNC on (6) DTR and (2) RD on the computer side.\nUnverified: Try setting apcupsd to UPSTYPE dumb et UPSCABLE 940-0128A."},{"id":"text-61","heading":"Text","content":"APC Part# - 940-0128D"},{"id":"text-62","heading":"Text","content":"DB9(Computer) RJ45-10(UPS)"},{"id":"text-63","heading":"Text","content":" (5) (1) ____________\n( o o o o o ) [ oooooooooo ]\n o o o o / [____________]\n (9) (6) (10) [_] (1)"},{"id":"text-64","heading":"Text","content":" RI(9)<---+\n |\nCTS(8)|---------| 2k 1N5819\n +---vvvv---+--[>|------<(3)LowBatt\n | |\n +--- C |\n |___|\n /| B\nDCD(1)-------------------------->(8)KillPwr"},{"id":"text-65","heading":"Text","content":"GND(5)----------------------------(7)Signal GND\n(Shield)--------------------------(4)Chassis GND"},{"id":"text-66","heading":"Text","content":"940-0127B Cable Wiring"},{"id":"text-67","heading":"Text","content":"Supported Models:\nBackUPS XS1000(BX-1000), Possibly other USB models"},{"id":"text-68","heading":"Text","content":"Contributed by:\nJan Babinski jbabinsk at pulsarbeacon dot com"},{"id":"text-69","heading":"Text","content":"Standard USB cable for USB-capable models with 10-pin RJ45 connector."},{"id":"text-70","heading":"Text","content":"APC Part# - 940-0127B"},{"id":"text-71","heading":"Text","content":"USB(Computer) RJ45-10(UPS)\n _________ ____________\n| = = = = | [ oooooooooo ]\n|_________| [____________]\n (1) (4) (10) [_] (1)"},{"id":"text-72","heading":"Text","content":" +5V(1)-----------(1)+5V\nDATA+(2)-----------(9)DATA+\nDATA-(3)-----------(10)DATA-\n GND(4)-----------(7)Signal GND\n(Shield)-----------(4)Chassis GRND"},{"id":"text-73","heading":"Text","content":"Win32 Implementation Restrictions for Simple UPSes\nDue to inadequacies in the\nWin32 API, it is not possible to set/clear/get all the serial port\nline signals. apcupsd can detect: CTS, DSR, RNG, and CD. It can set\nand clear: RTS and DTR.\nThis imposes a few minor restrictions on the functionality of some\nof the cables. In particular, LineDown on the Custom Simple cable,\nand Low Battery on the 0023A cable are not implemented."},{"id":"text-74","heading":"Text","content":"Note: In a future release of apcupsd this procedure will be\nreplaced by a daemon operation that can be performed on all types\nof UPS.\nThis section does not apply to voltage-signalling or dumb UPSes\nsuch as the older BackUPS models.\nSmart UPSes internally compute the remaining runtime, and apcupsd\nuses the value supplied by the UPS. As the batteries age (after say\ntwo or three years), the runtime computation may no longer be\naccurate since the batteries no longer hold the same charge. As a\nconsequence, in the event of a power failure, the UPS and thus\napcupsd can report a runtime of 5 minutes remaining when in fact\nonly one minute remains. This can lead to a shutdown before you\nmight expect it, because regardless of the runtime remaining that\nis reported, the UPS will always correctly detect low batteries and\nreport it, thus causing apcupsd to correctly shutdown your\ncomputer.\nIf you wish to have the UPS recalibrate the remaining runtime\ncalculations, you can do so manually as the current version of\napcupsd does not support this feature. To do so,"},{"id":"text-75","heading":"Text","content":"Shutdown apcupsd\ncontact your UPS directly using some terminal program such as\nminicom, tip, or cu with the settings 2400 8N1 (2400 baud, 8 bits,\nno parity, 1 stop bit). Be extremely careful what you send to your\nUPS as certain characters may cause it to power down or may even\ncause damage to the UPS. Try sending an upper case Y to the UPS\n(without a return at the end). It should respond with SM. If this\nis not the case, read the chapter on testing. If you fat finger the\nY and enter y instead, no cause for alarm, you will simply get the\nAPC copyright notice.\nwhen you are sure you are properly connected send an upper case\nD (no cr). This will put the UPS into calibration mode, and it will\ndrain the battery down to 25% capacity (35% for a Matrix) at which\npoint it will go back on the mains. In doing so, it will recompute\nthe runtime calibration.\nIf you wish to abort the calibration, enter a second D command.\nWhen you are done, restart apcupsd."},{"id":"text-76","heading":"Text","content":"In principle, you should be able to do this with the computer\npowered by the UPS, but if you wish to be completely safe, you\nshould plug your computer into the wall prior to performing the\nruntime calibration. In that case, you will need to artificially\nload the UPS with light bulbs or other means. You should supply a\nload of about 30 to 35% but not more than 50%. You can determine\nthe load by looking at the output of the apcaccess status\ncommand while apcupsd is running.\nYou should not run the recalibration command more than once or\ntwice per year as discharging these kinds of batteries tends to\nshorten their life span."},{"id":"text-77","heading":"Text","content":"There is a good deal of information available about the UPS and apcupsd's\nstatut. This document describes the format of that information.\nNormally you will get at it via apcaccess, but there are other ways\nainsi que."},{"id":"text-78","heading":"Text","content":"Status report format\nSTATUS output is in ASCII format with a single data value or piece\nof information on each line output. Because not all UPSes supply\nthe same information, the output varies based on the type of UPS\nthat you are using. In general, if the information is not available\nfor your UPS, the line will be missing entirely or the data portion of\nthe output record will contain an N / A indicating that the information\nis not available.\nStatus logging consists of periodically logging ALL available\ninformation concerning the UPS. Since the volume of data is rather\nlarge (over 1000 bytes per status), the STATUS data is not\nautomatically sent to the system log file. Instead, it is written\nas a series of data records in a specific file (normally\n/etc/apcupsd/apcupsd.status).\nAfter each write, the file is rewound so that the size of the file\nremains constant. The STATUS file is kept for backward compatibility\nand will be eliminated in a future version of apcupsd. The preferred\nmethod for obtaining this information is from apcaccess or by using\nthe CGI interface (see apcupsd Network Monitoring (CGI) Programs).\nTo make reading the status data reliable via a named pipe, the\nfirst record written contains a version number, the number of\nrecords that follow the first record, and the total number of bytes\nin those subsequent records. An actual example of such a status\nfile (/etc/apcupsd/apcupsd.status) is shown below.\nConsequently, the first record always consists of 24 bytes (23\ncharacters followed by a newline). This record starts with APC and\nas indicated in the example is followed by 37 records\nconsisting of 906 bytes. The last record begins with END APC and\ncontains the date and time matching the DATE record.\nWhen this data is written to a file, it is written as two records,\nthe first record, and all the other records together. In reading\nthe file, it can be either be read a record at a time, or in one\nbig read.\nWhen this data is written to syslog(), it is written a record at a\ntemps. The first record is the first 24 bytes. By having the number\nof records and the size in the first record, the complete status\ncan be reliably reassembled."},{"id":"text-79","heading":"Text","content":"Status Report Example\nAn example of output from a BackUPS RS 1500 follows:"},{"id":"text-80","heading":"Text","content":"APC : 001,037,0906\nDATE : Sun Apr 26 17:22:22 EDT 2009\nHOSTNAME : mail.kroptech.com\nVERSION : 3.14.2 (10 September 2007) redhat\nUPSNAME : ups0\nCABLE : USB Cable\nMODEL : Back-UPS RS 1500\nUPSMODE : Stand Alone\nSTARTTIME: Sun Apr 26 10:22:46 EDT 2009\nSTATUS : ONLINE\nLINEV : 123.0 Volts\nLOADPCT : 24.0 Percent Load Capacity\nBCHARGE : 100.0 Percent\nTIMELEFT : 144.5 Minutes\nMBATTCHG : 5 Percent\nMINTIMEL : 3 Minutes\nMAXTIME : 0 Seconds\nSENSE : Medium\nLOTRANS : 097.0 Volts\nHITRANS : 138.0 Volts\nALARMDEL : Always\nBATTV : 26.8 Volts\nLASTXFER : Low line voltage\nNUMXFERS : 0\nTONBATT : 0 seconds\nCUMONBATT: 0 seconds\nXOFFBATT : N/A\nSELFTEST : NO\nSTATFLAG : 0x07000008 Status Flag\nMANDATE : 2003-05-08\nSERIALNO : JB0319033692\nBATTDATE : 2001-09-25\nNOMINV : 120\nNOMBATTV : 24.0\nFIRMWARE : 8.g6 .D USB FW:g6\nAPCMODEL : Back-UPS RS 1500\nEND APC : Sun Apr 26 17:22:32 EDT 2009"},{"id":"text-81","heading":"Text","content":"Status Report Fields\nThe meaning of the above variables are:"},{"id":"text-82","heading":"Text","content":"APC\nHeader record indicating the STATUS format\nrevision level, the number of records that follow the APC\nstatement, and the number of bytes that follow the record.\nDATE\nThe date and time that the information was last obtained from the UPS.\nHOSTNAME\nThe name of the machine that collected the UPS data.\nUPSNAME\nThe name of the UPS as stored in the EEPROM or in the UPSNAME\ndirective in the configuration file.\nVERSION\nThe apcupsd release number, build date, and platform.\nCABLE\nThe cable as specified in the configuration file (UPSCABLE).\nMODÈLE\nThe UPS model as derived from information from the UPS.\nUPSMODE\nThe mode in which apcupsd is operating as specified in the configuration\nfile (UPSMODE)\nSTARTTIME\nThe time/date that apcupsd was started.\nSTATUS\nThe current status of the UPS (ONLINE, ONBATT, etc.)\nLINEV\nThe current line voltage as returned by the UPS.\nLOADPCT\nThe percentage of load capacity as estimated by the UPS.\nBCHARGE\nThe percentage charge on the batteries.\nTIMELEFT\nThe remaining runtime left on batteries as estimated by the UPS.\nMBATTCHG\nIf the battery charge percentage (BCHARGE)\ndrops below this value, apcupsd will shutdown your system.\nValue is set in the configuration file (BATTERYLEVEL)\nMINTIMEL\napcupsd will shutdown your system if the\nremaining runtime equals or is below this point.\nValue is set in the configuration file (MINUTES)\nMAXTIME\napcupsd will shutdown your system if the time\non batteries exceeds this value. A value of zero disables the\nfeature. Value is set in the configuration file (TIMEOUT)\nMAXLINEV\nThe maximum line voltage since the UPS was started, as reported by the UPS\nMINLINEV\nThe minimum line voltage since the UPS was started, as returned by the UPS\nOUTPUTV\nThe voltage the UPS is supplying to your equipment\nSENSE\nThe sensitivity level of the UPS to line voltage fluctuations.\nDWAKE\nThe amount of time the UPS will wait before restoring power to your\nequipment after a power off condition when the power is restored.\nDSHUTD\nThe grace delay that the UPS gives after\nreceiving a power down command from apcupsd before it powers off\nyour equipment.\nDLOWBATT\nThe remaining runtime below which the UPS\nsends the low battery signal. At this point apcupsd will force an\nimmediate emergency shutdown.\nLOTRANS\nThe line voltage below which the UPS will switch to batteries.\nHITRANS\nThe line voltage above which the UPS will switch to batteries.\nRETPCT\nThe percentage charge that the batteries must\nhave after a power off condition before the UPS will restore power\nto your equipment.\nITEMP\nInternal UPS temperature as supplied by the UPS.\nALARMDEL\nThe delay period for the UPS alarm.\nBATTV\nBattery voltage as supplied by the UPS.\nLINEFREQ\nLine frequency in hertz as given by the UPS.\nLASTXFER\nThe reason for the last transfer to batteries.\nNUMXFERS\nThe number of transfers to batteries since apcupsd startup.\nXONBATT\nTime and date of last transfer to batteries, or N/A.\nTONBATT\nTime in seconds currently on batteries, or 0.\nCUMONBATT\nTotal (cumulative) time on batteries in seconds since apcupsd startup.\nXOFFBATT\nTime and date of last transfer from batteries, or N/A.\nSELFTEST"},{"id":"text-83","heading":"Text","content":"The results of the last self test, and may have the following values:"},{"id":"text-84","heading":"Text","content":"OK: self test indicates good battery\nBT: self test failed due to insufficient battery capacity\nNG: self test failed due to overload\nNO: No results (i.e. no self test performed in the last 5 minutes)"},{"id":"text-85","heading":"Text","content":"STESTI\nThe interval in hours between automatic self tests.\nSTATFLAG\nStatus flag. English version is given by STATUS.\nDIPSW\nThe current dip switch settings on UPSes that have them.\nREG1\nThe value from the UPS fault register 1.\nREG2\nThe value from the UPS fault register 2.\nREG3\nThe value from the UPS fault register 3.\nMANDATE\nThe date the UPS was manufactured.\nSERIALNO\nThe UPS serial number.\nBATTDATE\nThe date that batteries were last replaced.\nNOMOUTV\nThe output voltage that the UPS will attempt to supply when on battery\nPuissance.\nNOMINV\nThe input voltage that the UPS is configured to expect.\nNOMBATTV\nThe nominal battery voltage.\nNOMPOWER\nThe maximum power in Watts that the UPS is designed to supply.\nHUMIDITY\nThe humidity as measured by the UPS.\nAMBTEMP\nThe ambient temperature as measured by the UPS.\nEXTBATTS\nThe number of external batteries as\ndefined by the user. A correct number here helps the UPS compute\nthe remaining runtime more accurately.\nBADBATTS\nThe number of bad battery packs.\nFIRMWARE\nThe firmware revision number as reported by the UPS.\nAPCMODEL\nThe old APC model identification code.\nEND APC\nThe time and date that the STATUS record was written."},{"id":"text-86","heading":"Text","content":"Logging the STATUS Information\nIf specified in the configuration file, the STATUS data will also be\nwritten to the system log file. Please note, that it would not\nnormally be wise to write this data to a normal system log file as\nthere is no mechanism in syslog() to rewind the file and hence the\nlog file would quickly become enormous. However, in two cases, it\ncan be very useful to use syslog() to write this information.\nThe first case is to set up your syslog.conf file so that the data\nis written to a named pipe. In this case, normally not more than\nabout 8192 bytes of data will be kept before it is discarded by the\nsystème.\nThe second case is to setup your syslog.conf file so that the\nstatus data is sent to another machine, which presumably then\nwrites it to a named pipe. Consequently, with this mechanism,\nprovides a simple means of networking apcupsd STATUS information.\nAlthough we mention system logging of STATUS information, we\nstrongly recommend that you use apcaccess or the CGI interface to\nget this information."},{"id":"text-87","heading":"Text","content":"Shutdown Sequence\nIf you experienced so problems with the testing procedures, or if\nyou are porting apcupsd to another system, or you are simply\ncurious, you may want to know exactly what is going on during the\nshutdown process.\nThe shutdown sequence is as follows:"},{"id":"text-88","heading":"Text","content":"apcupsd detects that there is a power problem and it calls\n/etc/apcupsd/apccontrol powerout. By default this event\ndoes nothing, but it can be overridden to notify users, etc."},{"id":"text-89","heading":"Text","content":"After the configured ONBATTERYDELAY, apcupsd\ncalls /etc/apcupsd/apccontrol onbattery, which normally sends a\nmessage to all users informing them that the UPS is on batteries."},{"id":"text-90","heading":"Text","content":"When one of the conditions listed below occurs, apcupsd issues a\nshutdown command by calling /etc/apcupsd/apccontrol doshutdown,\nwhich should perform a shutdown of your system using the system\nshutdown(8) command. You can modify the behavior as described in\nCustomizing Event Handling.\nThe conditions that trigger the shutdown can be any of the following:"},{"id":"text-91","heading":"Text","content":"Running time on batteries have expired (TIMEOUT)\nThe battery runtime remaining is below the configured value (BATTERYLEVEL)\nThe estimated remaining runtime is below the configured value (MINUTES)\nThe UPS signals that the batteries are exhausted."},{"id":"text-92","heading":"Text","content":"A shutdown could also be initiated if apcupsd detects that the\nbatteries are no longer functioning correctly. This case, though\nvery unusual, can happen at any time even if there is proper mains\nvoltage, and /etc/apcupsd/apccontrol emergency is called.\nJust before initiating any shutdown through the apccontrol script,\napcupsd will create the file /etc/apcupsd/powerfail. This file will\nbe used later in the shutdown sequence to recall apcupsd after\nsyncing of the disks to initiate a power off of the UPS.\nIf the /etc/nologin file has not already been created, it will\nnormally be created during the shutdown sequence to prevent\nadditional users from logging in (see the NOLOGIN configuration\ndirective).\nEven though apcupsd has requested the system to perform a shutdown,\nit continues running."},{"id":"text-93","heading":"Text","content":"When the system signals apcupsd to do exit, it does so. This is\npart of the normal system shutdown (at least on Unix and Linux\nsystems) and the exact time that apcupsd receives the termination\nsignal depends on how the shutdown links (usually in /etc/rc.d) are\nset.\nNote that on Windows NT systems, apcupsd apparently continues to\nrun as a Service even though the machine is "shutdown"."},{"id":"text-94","heading":"Text","content":"During the shutdown of the system after apcupsd has been forced\nto exit, one of the last things done by the system shutdown is to\ncall the halt script, which is usually in /etc/rc.d/halt or\n/etc/rc.d/init.d/halt, or possibly in /sbin/init.d/rc.0 depending\non your system. If apcupsd was properly installed, this standard\nhalt script was modified to include a bit of new logic just before\nthe final halt of the system. It first tests if the file\n/etc/apcupsd/powerfail exists, and if it does, it executes\n/etc/apcupsd/apccontrol killpower. It is this last step that will\ncause apcupsd to be re-executed with the --killpower option\non the command line. This option tells apcupsd to inform the UPS to\nkill the power."},{"id":"text-95","heading":"Text","content":"This final step is important if you want to ensure that your system\nwill automatically reboot when the power comes back on. The actual\ncode used on the Red Hat version is:"},{"id":"text-96","heading":"Text","content":"# See if this is a powerfail situation. # ***apcupsd***\nif [ -f /etc/apcupsd/powerfail ]; then # ***apcupsd***\n echo # ***apcupsd***\n echo "APCUPSD will now power off the UPS" # ***apcupsd***\n echo # ***apcupsd***\n /etc/apcupsd/apccontrol killpower # ***apcupsd***\n echo # ***apcupsd***\n echo "Please ensure that the UPS has powered off before rebooting" # ***apcupsd***\n echo "Otherwise, the UPS may cut the power during the reboot!!!" # ***apcupsd***\n echo # ***apcupsd***\nfi # ***apcupsd***"},{"id":"text-97","heading":"Text","content":"The above code must be inserted as late as possible in the halt\nscript. On many systems, such as Red Hat, all the disk drives were\nunmounted, then remounted read-only, thus permitting access to the\n/etc files and the apcupsd executable. If your system does not\nexplicitly remount the disks, you must remount them in read-only\nmode in the code that you add. Examples of code fragments that do\nthis can be found in the distributions/suse subdirectory of the\nla source.\nIf you are not able to insert the above code in your halt script\nbecause there is no halt script, or because your halt script calls\nthe init program as some Unix systems do, you can either just\nforget about powering off the UPS, which means that your machine\nwill not automatically reboot after a power failure, or there is\nyet another alternative, though not at all as satisfying as\ninserting code in the halt script.\nOnly if you cannot insert the appropriate code in the halt script,\nwhen you start apcupsd, normally from the /etc/rc.d/init.d/apcupsd\nscript, use the --kill-on-powerfail option. This will cause\napcupsd to program the UPS to shutoff the power just before it\n(apcupsd) does the system shutdown. Please note that this is not\nthe most ideal solution. Read on to understand why.\nA very important consideration is that you must set the EEPROM in\nyour UPS so that it waits a sufficient time for the system to halt\nbefore it shuts off the UPS power.\nWhen using a USB connection, apcupsd automatically sets this value\nto 60 seconds. When using a serial connection to a SmartUPS, you\nmust configure the value in the UPS EEPROM by hand using apctest."},{"id":"text-98","heading":"Text","content":"Shutdown Problems\nObviously if your halt script is not properly modified, apcupsd\nwill not be able to shut off the power to the UPS, and if the power\nreturns before the batteries are exhausted your system will not\nautomatically reboot. In any case, your machine should have been\ncleanly shut down."},{"id":"text-99","heading":"Text","content":"Master/Slave Shutdown\nIn master/slave configurations, however, the master cannot be 100\npercent sure that the slaves have all shutdown before it performs\nthe power off. To avoid this situation, be sure to configure any\nslaves (clients) to shut down before the master by setting different\nTIMEOUT, BATTERYLEVEL, ou MINUTES parameters in the\nconfig file.\nAlso, on a slave machine, you do not want to use the modified halt\nscript since it will recall apcupsd, which will detect that it is a\nslave (i.e. no connection to the UPS) and will complain that it\ncannot do the killpower. This situation is not harmful just\nannoying and possibly confusing.\nOne possible problem during shutdown can be caused by remnants of\nold versions. Please be sure to delete or rename all prior versions\n(/usr/local/sbin/apcupsd or /sbin/powersc)."},{"id":"text-100","heading":"Text","content":"Startup\nNormally, apcupsd is automatically started when\nyour system is rebooted. This normally occurs because the startup\nscript apcupsd is linked into the appropriate places in /etc/rc.d.\nOn most Linux systems, there is a program called chkconfig(8) that\nwill automatically link the startup script. This program is invoked\nby the make install scripts, or it is explicitly done for those\nsystems that do not have chkconfig(8). If this is not the case, you\ncan either link it in appropriately yourself or explicitly call it\nfrom your rc.local file. The appropriate manual way to startup\napcupsd is by executing:"},{"id":"text-101","heading":"Text","content":"/apcupsd start"},{"id":"text-102","heading":"Text","content":"où path is normally /etc/rc.d or /etc/rc.d/init.d depending on\nyour system. Using this script is\nimportant so that any files remaining around after a power failure\nare removed. Likewise, shutting down apcupsd should be done with\nthe same script:"},{"id":"text-103","heading":"Text","content":"/apcupsd stop"},{"id":"text-104","heading":"Text","content":"The APC UPS\nprotocol was originally analyzed by Pavel Korensky with additions\nfrom Andre H. Hendrick beginning in 1995, and we want to give\ncredit for good, hard work, where credit is due. After having said\nthat, you will see that Steven Freed built much of the original\napcupsd information file.\nThe start of this chapter of the apcupsd manual in HTML format was\npulled from the Network UPS Tools (NUT) site\n(http://www.networkupstools.org/ups-protocols/apcsmart.html). Il\nhas been an invaluable tool in improving apcupsd, and I consider it\nthe Bible of APC UPS programming. In the course of using it, I\nhave added information gleaned from apcupsd and information\ngraciously supplied by APC."},{"id":"text-105","heading":"Text","content":"La description\nHere's the information on the elusive APC smart signaling protocol\nused by their higher end units (Back-UPS Pro, Smart-UPS,\nMatrix-UPS, etc). What you see here has been collected from a\nvariety of sources. Some people analyzed the chatter between\nPowerChute and their hardware. Others sent various characters to\nthe UPS and figured out what the results meant."},{"id":"text-106","heading":"Text","content":"RS-232 differences\nNormal 9 pin serial connections have TxD on 3 and RxD on 2. APC's\nsmart serial ports put TxD on pin 1 and RxD on pin 2. This means\nyou go nowhere if you use a normal straight through serial cable.\nIn fact, you might even power down the load if you plug one of\nthose cables in. This is due to the odd routing of pins – DTR and\nRTS from the PC usually wind up driving the on/off line. So, when\nyou open the port, they go high and *poof* your computer dies."},{"id":"text-107","heading":"Text","content":"The Smart Protocol\nDespite the lack of official information from APC, this table has\nbeen constructed. It's standard RS-232 serial communications at\n2400 bps/8N1. Don't rush the UPS while transmitting or it may stop\ntalking to you. This isn't a problem with the normal single\ncharacter queries, but it really does matter for multi-char things\nlike "@000". Sprinkle a few calls to usleep() in your code and\neverything will work a lot better.\nThe following table describes the single character "Code" or\ncommand that you can send to the UPS, its meaning, and what sort of\nresponse the UPS will provide. Typically, the response shown below\nis followed by a newline (n in C) and a carriage return (r in\nC). If you send the UPS a command that it does not recognize or\nthat is not available on your UPS, it will normally respond with "NA"\nfor "not available", otherwise the response is given in the\n"Typical results" column."},{"id":"text-108","heading":"Text","content":"Personnage\nSens\nTypical results\nOther info"},{"id":"text-109","heading":"Text","content":"^A\nModel string\nSMART-UPS 700\nSpotty support for this query on older\ndes modèles"},{"id":"text-110","heading":"Text","content":"^N\nTurn on UPS\nn / a\nSend twice, with 1.5s delay between\nchars. Only on 3rd gen SmartUPS and\nBlack Back-UPS Pros"},{"id":"text-111","heading":"Text","content":"^Z\nPermitted\nEEPROM\nValues\nlong string\nGives the EEPROM permitted values for\nyour model. See EEPROM Values for\ndetails."},{"id":"text-112","heading":"Text","content":"UNE\nFront panel\ntest\nLight show +\n"OK"\nAlso sounds the beeper for 2 seconds"},{"id":"text-113","heading":"Text","content":"B\nBatterie\nvoltage\n27.87\nVaries based on current level of\ncharge. See also Nominal Battery\nVoltage."},{"id":"text-114","heading":"Text","content":"C\nInterne\nTemperature\n036.0\nUnits are degrees C"},{"id":"text-115","heading":"Text","content":"ré\nRuntime\ncalibration\n!, then $\nRuns until battery is below 25% (35%\nfor Matrix) Updates the 'j' values.\nOnly works at 100% battery charge. Pouvez\nbe aborted with a second "D""},{"id":"text-116","heading":"Text","content":"E\nAutomatic\nself test\ninterval\n336"},{"id":"text-117","heading":"Text","content":"Writable variable. Possible values:"},{"id":"text-118","heading":"Text","content":""336" (14 days)\n"168" (7 days)\n"ON " (at power on) note extra space\n"OFF" (never)"},{"id":"text-119","heading":"Text","content":"F\nLigne\nla fréquence\n60.00\nUnits are Hz. Value varies based on\nlocality, usually 50/60."},{"id":"text-120","heading":"Text","content":"g\nCause of\nlast\ntransfert\nto battery\nO"},{"id":"text-121","heading":"Text","content":"Possible values:"},{"id":"text-122","heading":"Text","content":"R (unacceptable utility voltage rate\nof change)\nH (high utility voltage)\nL (low utility voltage)\nT (line voltage notch or spike)\nO (no transfers since turnon)\nS (transfer due to U command or\nactivation of UPS test from front\npanel)\nNA (transfer reason still not\navailable; read again)"},{"id":"text-123","heading":"Text","content":"je\nMeasure-UPS\nAlarm enable\nFF\nnot decoded yet"},{"id":"text-124","heading":"Text","content":"J\nMeasure-UPS\nAlarm status\n0F,00\nnot decoded yet"},{"id":"text-125","heading":"Text","content":"K\nShutdown\nwith grace\nperiod (no\nreturn)\nOK or *\nSend twice with > 1.5s delay between\nchars. Older units send "*" instead of\n"OK". Length of grace period is set\nwith Grace Period command. UPS will\nremain off and NOT power on if utility\npower is restored."},{"id":"text-126","heading":"Text","content":"L\nInput line\nvoltage\n118.3\nValue varies based on locality. Does\nnot always read 000.0 on line failure."},{"id":"text-127","heading":"Text","content":"M\nMaximum line\nvoltage\n118.9\nThis is the max voltage since the last\ntime this query was run."},{"id":"text-128","heading":"Text","content":"N\nMinimum line\nvoltage\n118.1\nThis is the min voltage since the last\ntime this query was run."},{"id":"text-129","heading":"Text","content":"O\nOutput\nvoltage\n118.3\nAlso see on battery output voltage."},{"id":"text-130","heading":"Text","content":"P\nPower load\n%\n023.5\nRelative to capacity of the UPS."},{"id":"text-131","heading":"Text","content":"Q\nStatus flags\n08\nBitmapped, see status bits below"},{"id":"text-132","heading":"Text","content":"R\nTurn dumb\nBYE\nOnly on 3rd gen SmartUPS, SmartUPS\nv/s, BackUPS Pro. Must send enter\nsmart mode command to resume comms."},{"id":"text-133","heading":"Text","content":"S\nSoft\nshutdown\nD'accord\nCommand executes after grace period.\nUPS goes online when power returns.\nOnly works when on battery."},{"id":"text-134","heading":"Text","content":"U\nSimulate\npower\nfailure\n!, then $\nSee Alert messages section for info\non ! and $."},{"id":"text-135","heading":"Text","content":"V\nOld firmware\nrevision\n"GWD" or "IWI"\nVoir Interpretation of the Old\nFirmware Revision"},{"id":"text-136","heading":"Text","content":"W\nSelf test\nD'accord\nTests battery, like pushing button on\nthe front panel. Results stored in "X""},{"id":"text-137","heading":"Text","content":"X\nSelf test\nrésultats\nD'accord"},{"id":"text-138","heading":"Text","content":"Possible values:"},{"id":"text-139","heading":"Text","content":"OK = good battery\nBT = failed due to insufficient\ncapacité\nNG = failed due to overload\nNO = no results available (no test\nperformed in last 5 minutes)"},{"id":"text-140","heading":"Text","content":"Y\nEnter smart\nmode\nSM\nThis must be sent before any other\ncommands will work. See also turn dumb\ncommand to exit smart mode."},{"id":"text-141","heading":"Text","content":"Z\nShutdown\nimmédiatement\nn / a\nSend twice with > 1.5s delay between\nchars. UPS switches load off\nimmediately (no grace period)"},{"id":"text-142","heading":"Text","content":"une\nProtocol\ninfo\nlong string"},{"id":"text-143","heading":"Text","content":"Returns three main sections delimited\nby periods:"},{"id":"text-144","heading":"Text","content":"Protocol version\nAlert messages (aka async notifiers)\nValid commands"},{"id":"text-145","heading":"Text","content":"b\nFirmware\nrevision\n50.9.D"},{"id":"text-146","heading":"Text","content":"Voir Interpretation of the New\nFirmware Revision.\nDecoding the example:"},{"id":"text-147","heading":"Text","content":"50 = SKU (variable length)\n9 = firmware revision\nD = country code (D=USA,\nI=International, A=Asia, J=Japan,\nM=Canada)"},{"id":"text-148","heading":"Text","content":"c\nUPS local\nid\nUPS_IDEN\nWritable variable. Up to 8 letter\nidentifier for keeping track of your\nhardware."},{"id":"text-149","heading":"Text","content":"e\nReturn\nthreshold\n00"},{"id":"text-150","heading":"Text","content":"Writable variable. Minimum battery\ncharge % before UPS will return online\nafter a soft shutdown. Possible\nvalues:"},{"id":"text-151","heading":"Text","content":"00 = 00% (UPS turns on immediately)\n01 = 15%\n02 = 25%\n03 = 90%"},{"id":"text-152","heading":"Text","content":"f\nBatterie\nlevel %\n099.0\nPercentage of battery charge remaining"},{"id":"text-153","heading":"Text","content":"g\nNominal\nbatterie\nvoltage\n024\nThe battery voltage that's expected to\nbe present in the UPS normally. Cette\nis a constant based on the type,\nnumber, and wiring of batteries in the\nUPS. Typically "012", "024" or "048"."},{"id":"text-154","heading":"Text","content":"h\nMeasure-UPS\nambient\nhumidity (%)\n042.4\nPercentage. Only works on models with\nMeasure-UPS SmartSlot card."},{"id":"text-155","heading":"Text","content":"je\nMeasure-UPS\ndry contacts\n00"},{"id":"text-156","heading":"Text","content":"Bitmapped hex variable. Mapping:"},{"id":"text-157","heading":"Text","content":"10 = contact 1\n20 = contact 2\n40 = contact 3\n80 = contact 4"},{"id":"text-158","heading":"Text","content":"j\nEstimated\nruntime\n0327:\nValue is in minutes. Terminated with\na colon."},{"id":"text-159","heading":"Text","content":"k\nAlarm delay\n0"},{"id":"text-160","heading":"Text","content":"Writable variable. Controls behavior\nof UPS beeper. Possible values:"},{"id":"text-161","heading":"Text","content":"0 = 5 second delay after power fail\nT = 30 second delay\nL = alarm at low battery only\nN = no alarm"},{"id":"text-162","heading":"Text","content":"l\nLow transfer\nvoltage\n103\nWritable variable. UPS goes on battery\nwhen voltage drops below this point."},{"id":"text-163","heading":"Text","content":"m\nManufacture\ndate\n11/29/96\nFormat may vary by country (MM/DD/YY\nvs DD/MM/YY). Unique within groups of\nUPSes (production runs)"},{"id":"text-164","heading":"Text","content":"n\nSerial\nnombre\nWS9643050926\nUnique for each UPS"},{"id":"text-165","heading":"Text","content":"o\nNominal\nOutput\nTension\n115\nExpected output voltage when running\non batteries. May be a writable\nvariable on 220/230/240 VAC units."},{"id":"text-166","heading":"Text","content":"p\nShutdown\ngrace delay\n020\nSeconds. Writable variable. Sets the\ndelay before soft shutdown completes.\n(020/180/300/600)"},{"id":"text-167","heading":"Text","content":"q\nLow battery\nwarning\n02\nMinutes. Writable variable. The UPS\nwill report a low battery condition\nthis many minutes before it runs out\nof power"},{"id":"text-168","heading":"Text","content":"r\nWakeup delay\n000\nSeconds. Writable variable. The UPS\nwill wait this many seconds after\nreaching the minimum charge before\nreturning online. (000/060/180/300)"},{"id":"text-169","heading":"Text","content":"s\nSensitivity\nH"},{"id":"text-170","heading":"Text","content":"Writable variable. Possible values:"},{"id":"text-171","heading":"Text","content":"H = highest\nM = medium\nL = lowest\nA = autoadjust (Matrix only)"},{"id":"text-172","heading":"Text","content":"t\nMeasure-UPS\nambient\ntemperature\n80.5\nDegrees C. Only works on models with\nthe Measure-UPS SmartSlot card."},{"id":"text-173","heading":"Text","content":"vous\nUpper\ntransfert\nvoltage\n132\nWritable variable. UPS goes on battery\nwhen voltage rises above this point."},{"id":"text-174","heading":"Text","content":"v\nMeasure-UPS\nfirmware\n4Kx\nFirmware information for Measure-UPS\nboard"},{"id":"text-175","heading":"Text","content":"X\nLast battery\nchange date\n11/29/96\nWritable variable. Holds whatever the\nuser set in it. Eight characters."},{"id":"text-176","heading":"Text","content":"y\ndroits d'auteur\nremarquer\n(C) APCC\nOnly works if firmware letter is\nlater than O"},{"id":"text-177","heading":"Text","content":"z\nReset to\nfactory\nsettings\nCLEAR\nResets most variables to initial\nfactory values except identity or\nbattery change date. Not available on\nSmartUPS v/s or BackUPS Pro."},{"id":"text-178","heading":"Text","content":"+\nCapability\ncycle\n(forward)\nvarious\nCycle forward through possible\ncapability values. UPS sends\nafterward to confirm change to EEPROM."},{"id":"text-179","heading":"Text","content":"–\nCapability\ncycle\n(backward)\nvarious\nCycle backward through possible\ncapability values. UPS sends\nafterward to confirm change to EEPROM."},{"id":"text-180","heading":"Text","content":"@nnn\nShutdown and\nrevenir\nOK or *\nUPS shuts down after grace period with\ndelayed wakeup after nnn tenths of an\nhour plus any wakeup delay time. Older\nmodels send "*" instead of "OK"."},{"id":"text-181","heading":"Text","content":"0x7f\nAbort\nshutdown\nD'accord\nUse to abort @, S, K"},{"id":"text-182","heading":"Text","content":"~\nRegister #1\nsee below\nSee Register 1 table"},{"id":"text-183","heading":"Text","content":"'\nRegister #2\nsee below\nSee Register 2 table"},{"id":"text-184","heading":"Text","content":"0\nBatterie\nconstant\n \nVoir Resetting the UPS Battery\nConstant"},{"id":"text-185","heading":"Text","content":"4\n???\n \nPrints 35 on SmartUPS 1000"},{"id":"text-186","heading":"Text","content":"5\n???\n \nPrints EF on SmartUPS 1000"},{"id":"text-187","heading":"Text","content":"6\n???\n \nPrints F9 on SmartUPS 1000"},{"id":"text-188","heading":"Text","content":"sept\nDIP switch\npositions\n \nSee Dip switch info"},{"id":"text-189","heading":"Text","content":"8\nRegister #3\nsee below\nSee Register 3 table"},{"id":"text-190","heading":"Text","content":"9\nLine quality\nFF"},{"id":"text-191","heading":"Text","content":"Possible values:"},{"id":"text-192","heading":"Text","content":"00 = unacceptable\nFF = acceptable"},{"id":"text-193","heading":"Text","content":">\nNumber of\nexterne\nbatterie\npacks\n \nSmartCell models return number of\nconnected packs. Other models return\nvalue set by the user (use +/-)."},{"id":"text-194","heading":"Text","content":"[[[[\nMeasure-UPS\nUpper temp\nlimit\nNO,NO\nDegrees C. Writable Variable. Possible\nvalues: 55, 50, 45, …, 05.\nUse +/- to change values."},{"id":"text-195","heading":"Text","content":"]\nMeasure-UPS\nlower temp\nlimit\nNO,NO\nDegrees C. Writable Variable. Possible\nvalues: 55, 50, 45, …, 05.\nUse +/- to change values."},{"id":"text-196","heading":"Text","content":"Measure-UPS\nUpper\nhumidity\nlimit\nNO,NO\nPercentage. Writable Variable.\nPossible values: 90, 80, 70, …, 10.\nUse +/- to change values."},{"id":"text-197","heading":"Text","content":"Measure-UPS\nlower\nhumidity\nlimit\nNO,NO\nPercentage. Writable Variable.\nPossible values: 90, 80, 70, …, 10.\nUse +/- to change values."},{"id":"text-198","heading":"Text","content":"Matrix-UPS and Symmetra Commands"},{"id":"text-199","heading":"Text","content":"^\nRun in\nbypass mode\nBYP, INV, ERR\nIf online, "BYP" response is received\nas bypass mode starts. If already in\nbypass, "INV" is received and UPS goes\nonline. If UPS can't transfer, "ERR"\nreceived"},{"id":"text-200","heading":"Text","content":"<\nNumber of\nbad battery\npacks\n000\nCount of bad packs connected to the\nUPS"},{"id":"text-201","heading":"Text","content":"/\nLoad current\nnn.nn\nTrue RMS load current drawn by UPS"},{"id":"text-202","heading":"Text","content":"Apparent\nload power\nnnn.nn\nOutput load as percentage of full\nrated load in VA."},{"id":"text-203","heading":"Text","content":"^V\nOutput\nvoltage\nselection"},{"id":"text-204","heading":"Text","content":"Writable variable. Possible values:"},{"id":"text-205","heading":"Text","content":"A = automatic (based on input tap)\nM = 208 VAC\nI = 240 VAC"},{"id":"text-206","heading":"Text","content":"^L\nFront panel\nlanguage"},{"id":"text-207","heading":"Text","content":"Writable variable. Possible values:"},{"id":"text-208","heading":"Text","content":"E = English\nF = French\nG = German\nS = Spanish\n1 = unknown\n2 = unknown\n3 = unknown\n4 = unknown"},{"id":"text-209","heading":"Text","content":"w\nRun time\nconservation"},{"id":"text-210","heading":"Text","content":"Writable variable. Minutes of runtime\nto leave in battery (UPS shuts down\n"early"). Possible values:"},{"id":"text-211","heading":"Text","content":"NO = disabled\n02 = leave 2 minutes of runtime\n05 = leave 5 minutes\n08 = leave 8 minutes"},{"id":"text-212","heading":"Text","content":"Dip switch info"},{"id":"text-213","heading":"Text","content":"Bit\nCommutateur\nOption when bit=1"},{"id":"text-214","heading":"Text","content":"0\n4\nLow battery alarm changed from 2 to 5 mins. Autostartup disabled on\nSU370ci and 400"},{"id":"text-215","heading":"Text","content":"1\n3\nAudible alarm delayed 30 seconds"},{"id":"text-216","heading":"Text","content":"2\n2\nOutput transfer set to 115 VAC (from 120 VAC) or to 240 VAC (from\n230 VAC)"},{"id":"text-217","heading":"Text","content":"3\n1\nUPS desensitized – input voltage range expanded"},{"id":"text-218","heading":"Text","content":"4-7\n \nUnused at this time"},{"id":"text-219","heading":"Text","content":"Status bits\nThis is probably the most important register of the UPS, which\nindicates the overall UPS status. Some common things you'll see:"},{"id":"text-220","heading":"Text","content":"08 = On line, battery OK\n10 = On battery, battery OK\n50 = On battery, battery low\nSM = Status bit is still not available (retry reading)"},{"id":"text-221","heading":"Text","content":"Bit\nMeaning when bit=1"},{"id":"text-222","heading":"Text","content":"0\nRuntime calibration occurring\n(Not reported by Smart UPS v/s and BackUPS Pro)"},{"id":"text-223","heading":"Text","content":"1\nSmartTrim (Not reported by 1st and 2nd generation SmartUPS models)"},{"id":"text-224","heading":"Text","content":"2\nSmartBoost"},{"id":"text-225","heading":"Text","content":"3\nOn line (this is the normal condition)"},{"id":"text-226","heading":"Text","content":"4\nOn battery"},{"id":"text-227","heading":"Text","content":"5\nOverloaded output"},{"id":"text-228","heading":"Text","content":"6\nBattery low"},{"id":"text-229","heading":"Text","content":"sept\nReplace battery"},{"id":"text-230","heading":"Text","content":"Alert messages\nThese single character messages are sent by the UPS any time there\nis an Alert condition. All other responses indicated above are sent\nby the UPS only in response to a query or action command."},{"id":"text-231","heading":"Text","content":"Personnage\nSens\nLa description"},{"id":"text-232","heading":"Text","content":"!\nLine Fail\nSent when the UPS goes on-battery, repeated every 30\nseconds until low battery condition reached. quelquefois\noccurs more than once in the first 30 seconds."},{"id":"text-233","heading":"Text","content":"$\nReturn from\nline fail\nUPS back on line power. Only sent if a ! has been sent\npreviously."},{"id":"text-234","heading":"Text","content":"%\nLow battery\nSent to indicate low battery. Not implemented on\nSmartUPS v/s or BackUPS Pro models"},{"id":"text-235","heading":"Text","content":"+\nReturn from\nlow batt\nSent when the battery has been recharged to some level\nOnly sent if a % has been sent previously."},{"id":"text-236","heading":"Text","content":"?\nAbnormal\nétat\nSent for conditions such as "shutdown due to overload"\nor "shutdown due to low battery capacity". Also occurs\nwithin 10 minutes of turnon."},{"id":"text-237","heading":"Text","content":"=\nReturn from\nabnormal\nétat\nSent when the UPS returns from an abnormal condition\nwhere ? was sent, but not a turn-on. Not implemented on\nSmartUPS v/s or BackUPS Pro models."},{"id":"text-238","heading":"Text","content":"*\nAbout to\nturn off\nSent when the UPS is about to switch off the load. Non\ncommands are processed after this character is sent. ne pas\nimplemented on SmartUPS v/s, BackUPS Pro, or 3rd\ngeneration SmartUPS models."},{"id":"text-239","heading":"Text","content":"#\nRemplacer\nbatterie\nSent when the UPS detects that the battery needs to be\nreplaced. Sent every 5 hours until a new battery test is\nrun or the UPS is shut off. Not implemented on SmartUPS\nv/s or BackUPS Pro models."},{"id":"text-240","heading":"Text","content":"Et\nCheck alarm\nregister\nfor fault\n(Measure-UPS)\nSent to signal that temp or humidity out of set limits.\nAlso sent when one of the contact closures changes\nEtat. Sent every 2 minutes until the alarm conditions\nare reset. Only sent for alarms enabled with I. Cause of\nalarm may be determined with J. Not implemented on\nSmartUPS v/s or BackUPS Pro."},{"id":"text-241","heading":"Text","content":"|\nVariable\nchange in\nEEPROM\nSent whenever any EEPROM variable is changed. Only\nsupported on Matrix UPS and 3rd generation SmartUPS\nmodels."},{"id":"text-242","heading":"Text","content":"Register 1\nAll bits are valid on the Matrix UPS. SmartUPS models only support\nbits 6 and 7. Other models do not respond."},{"id":"text-243","heading":"Text","content":"Bit\nMeaning when bit=1"},{"id":"text-244","heading":"Text","content":"0\nIn wakeup mode (typically lasts < 2s)"},{"id":"text-245","heading":"Text","content":"1\nIn bypass mode due to internal fault (see Register 2 or Register 3)"},{"id":"text-246","heading":"Text","content":"2\nGoing to bypass mode due to command"},{"id":"text-247","heading":"Text","content":"3\nIn bypass mode due to command"},{"id":"text-248","heading":"Text","content":"4\nReturning from bypass mode"},{"id":"text-249","heading":"Text","content":"5\nIn bypass mode due to manual bypass control"},{"id":"text-250","heading":"Text","content":"6\nReady to power load on user command"},{"id":"text-251","heading":"Text","content":"sept\nReady to power load on user command or return of line power"},{"id":"text-252","heading":"Text","content":"Register 2\nMatrix UPS models report bits 0-5. SmartUPS models only support\nbits 4-6. SmartUPS v/s and BackUPS Pro report bits 4, 6, 7.\nUnused bits are set to 0. Other models do not respond."},{"id":"text-253","heading":"Text","content":"Bit\nMeaning when bit=1"},{"id":"text-254","heading":"Text","content":"0\nFan failure in electronics, UPS in bypass"},{"id":"text-255","heading":"Text","content":"1\nFan failure in isolation unit"},{"id":"text-256","heading":"Text","content":"2\nBypass supply failure"},{"id":"text-257","heading":"Text","content":"3\nOutput voltage select failure, UPS in bypass"},{"id":"text-258","heading":"Text","content":"4\nDC imbalance, UPS in bypass"},{"id":"text-259","heading":"Text","content":"5\nBattery is disconnected"},{"id":"text-260","heading":"Text","content":"6\nRelay fault in SmartTrim or SmartBoost"},{"id":"text-261","heading":"Text","content":"sept\nBad output voltage"},{"id":"text-262","heading":"Text","content":"Register 3\nAll bits are valid on the Matrix UPS and 3rd generation SmartUPS\nmodels. SmartUPS v/s and BackUPS Pro models report bits 0-5. Tout\nothers report 0-4. State change of bits 1,2,5,6,7 are reported\nasynchronously with ? and = messages."},{"id":"text-263","heading":"Text","content":"Bit\nMeaning when bit=1"},{"id":"text-264","heading":"Text","content":"0\nOutput unpowered due to shutdown by low battery"},{"id":"text-265","heading":"Text","content":"1\nUnable to transfer to battery due to overload"},{"id":"text-266","heading":"Text","content":"2\nMain relay malfunction – UPS turned off"},{"id":"text-267","heading":"Text","content":"3\nIn sleep mode from @ command (maybe others)"},{"id":"text-268","heading":"Text","content":"4\nIn shutdown mode from S command"},{"id":"text-269","heading":"Text","content":"5\nBattery charger failure"},{"id":"text-270","heading":"Text","content":"6\nBypass relay malfunction"},{"id":"text-271","heading":"Text","content":"sept\nNormal operating temperature exceeded"},{"id":"text-272","heading":"Text","content":"Interpretation of the Old Firmware Revision\nThe Old Firmware Revision is obtained with the "V" command, which\ngives a typical response such as "GWD" or "IWI", and can be\ninterpreted as follows:"},{"id":"text-273","heading":"Text","content":"Old Firmware revision and model ID String for SmartUPS & MatrixUPS"},{"id":"text-274","heading":"Text","content":"This is a three character string XYZ"},{"id":"text-275","heading":"Text","content":" where X == Smart-UPS or Matrix-UPS ID Code.\n range 0-9 and A-P\n 1 == unknown\n 0 == Matrix 3000\n 5 == Matrix 5000\n the rest are Smart-UPS and Smart-UPS-XL\n 2 == 250 3 == 400 4 == 400\n 6 == 600 7 == 900 8 == 1250\n 9 == 2000 A == 1400 B == 1000\n C == 650 D == 420 E == 280\n F == 450 G == 700 H == 700XL\n I == 1000 J == 1000XL K == 1400\n L == 1400XL M == 2200 N == 2200XL\n O == 3000 P == 5000"},{"id":"text-276","heading":"Text","content":" where Y == Possible Level of Smart Features, unknown???\n G == Stand Alone\n T == Stand Alone\n V == ???\n W == Rack Mount"},{"id":"text-277","heading":"Text","content":" where Z == National Model Use Only Codes\n D == Domestic 115 Volts\n I == International 230 Volts\n A == Asia ?? 100 Volts\n J == Japan ?? 100 Volts"},{"id":"text-278","heading":"Text","content":"Interpretation of the New Firmware Revision"},{"id":"text-279","heading":"Text","content":"New Firmware revision and model ID String in NN.M.L is the format"},{"id":"text-280","heading":"Text","content":" where NN == UPS ID Code.\n 12 == Back-UPS Pro 650\n 13 == Back-UPS Pro 1000\n 52 == Smart-UPS 700\n 60 == SmartUPS 1000\n 72 == Smart-UPS 1400"},{"id":"text-281","heading":"Text","content":" where NN now Nn has possible meanings.\n N == Class of UPS\n 1n == Back-UPS Pro\n 5n == Smart-UPS\n 7n == Smart-UPS NET"},{"id":"text-282","heading":"Text","content":" n == Level of intelligence\n N1 == Simple Signal, if detectable WAG(*)\n N2 == Full Set of Smart Signals\n N3 == Micro Subset of Smart Signals"},{"id":"text-283","heading":"Text","content":" where M == Possible Level of Smart Features, unknown???\n 1 == Stand Alone\n 8 == Rack Mount\n 9 == Rack Mount"},{"id":"text-284","heading":"Text","content":" where L == National Model Use Only Codes\n D == Domestic 115 Volts\n I == International 230 Volts\n A == Asia ?? 100 Volts\n J == Japan ?? 100 Volts\n M == North America 208 Volts (Servers)"},{"id":"text-285","heading":"Text","content":"EEPROM Values\nUpon sending a ^Z, your UPS will probably spit back approximately\n254 characters something like the following (truncated here for the\nexample):"},{"id":"text-286","heading":"Text","content":"#uD43132135138129uM43229234239224uA43110112114108 ...."},{"id":"text-287","heading":"Text","content":"It looks bizarre and ugly, but is easily parsed. The # is some kind\nof marker/ident character. Skip it. The rest fits this form:"},{"id":"text-288","heading":"Text","content":"Command character – use this to select the value\nLocale – use 'b' to find out what yours is (the last character),\n'4' applies to all\nNumber of choices – '4' means there are 4 possibilities coming\nen haut\nChoice length – '3' means they are all 3 chars long"},{"id":"text-289","heading":"Text","content":"Then it's followed by the choices, and it starts over.\nMatrix-UPS models have ## between each grouping for some reason.\nHere is an example broken out to be more readable:"},{"id":"text-290","heading":"Text","content":"CMD DFO RSP FSZ FVL\nu D 4 3 127 130 133 136\nu M 4 3 229 234 239 224\nu A 4 3 108 110 112 114\nu I 4 3 253 257 261 265\nl D 4 3 106 103 100 097\nl M 4 3 177 172 168 182\nl A 4 3 092 090 088 086\nl I 4 3 208 204 200 196\ne 4 4 2 00 15 50 90\no D 1 3 115\no J 1 3 100\no I 1 3 230 240 220 225\no M 1 3 208\ns 4 4 1 H M L L\nq 4 4 2 02 05 07 10\np 4 4 3 020 180 300 600\nk 4 4 1 0 T L N\nr 4 4 3 000 060 180 300\nE 4 4 3 336 168 ON OFF"},{"id":"text-291","heading":"Text","content":"CMD == UPSlink Command.\n u = upper transfer voltage\n l = lower transfer voltage\n e = return threshold\n o = output voltage\n s = sensitivity\n p = shutdown grace delay\n q = low battery warning\n k = alarm delay\n r = wakeup delay\n E = self test interval"},{"id":"text-292","heading":"Text","content":"DFO == (4)-all-countries (D)omestic (I)nternational (A)sia (J)apan\n (M) North America - servers.\nRSP == Total number possible answers returned by a given CMD.\nFSZ == Max. number of field positions to be filled.\nFVL == Values that are returned and legal."},{"id":"text-293","heading":"Text","content":"Programming the UPS EEPROM\nThere are at this time a maximum of 12 different values that can be\nprogrammed into the UPS EEPROM. They are:"},{"id":"text-294","heading":"Text","content":"Commander\nSens"},{"id":"text-295","heading":"Text","content":"c\nThe UPS Id or name"},{"id":"text-296","heading":"Text","content":"X\nThe last date the batteries were replaced"},{"id":"text-297","heading":"Text","content":"vous\nThe Upper Transfer Voltage"},{"id":"text-298","heading":"Text","content":"l\nThe Lower Transfer Voltage"},{"id":"text-299","heading":"Text","content":"e\nThe Return Battery Charge Percentage"},{"id":"text-300","heading":"Text","content":"o\nThe Output Voltage when on Batteries"},{"id":"text-301","heading":"Text","content":"s\nThe Sensitivity to Line Quality"},{"id":"text-302","heading":"Text","content":"p\nThe Shutdown Grace Delay"},{"id":"text-303","heading":"Text","content":"q\nThe Low Battery Warning Delay"},{"id":"text-304","heading":"Text","content":"k\nThe Alarm Delay"},{"id":"text-305","heading":"Text","content":"r\nThe Wakeup Delay"},{"id":"text-306","heading":"Text","content":"E\nThe Automatic Self Test Interval"},{"id":"text-307","heading":"Text","content":"The first two cases (Ident and Batt date) are somewhat special in\nthat you tell the UPS you want to change the value, then you supply\n8 characters that are saved in the EEPROM. The last ten item are\nprogrammed by telling the UPS that you want it to cycle to the next\npermitted value.\nIn each case, you indicate to the UPS that you want to change the\nEEPROM by first sending the appropriate query command (e.g. "c" for\nthe UPS ID or "u" for the Upper Transfer voltage. This command is\nthen immediately followed by the cycle EEPROM command or "-". Dans\nthe case of the UPS Id or the battery date, you follow the cycle\ncommand by the eight characters that you want to put in the EEPROM.\nIn the case of the other ten items, there is nothing more to\nenter.\nThe UPS will respond by "OK" and approximately 5 seconds later by a\nvertical bar (|) to indicate that the EEPROM was changed."},{"id":"text-308","heading":"Text","content":"Click to rate this post!\n \n [Total: 0 Average: 0]"}],"media":{"primary_image":""},"relations":[{"rel":"canonical","href":"https://tutos-gameserver.fr/2019/10/21/manuel-utilisateur-apcupsd-serveur-dimpression/"},{"rel":"alternate","href":"https://tutos-gameserver.fr/2019/10/21/manuel-utilisateur-apcupsd-serveur-dimpression/llm","type":"text/html"},{"rel":"alternate","href":"https://tutos-gameserver.fr/2019/10/21/manuel-utilisateur-apcupsd-serveur-dimpression/llm.json","type":"application/json"},{"rel":"llm-manifest","href":"https://tutos-gameserver.fr/llm-endpoints-manifest.json","type":"application/json"}],"http_headers":{"X-LLM-Friendly":"1","X-LLM-Schema":"1.1.0","Content-Security-Policy":"default-src 'none'; img-src * data:; style-src 'unsafe-inline'"},"license":"CC BY-ND 4.0","attribution_required":true,"allow_cors":false}