[Apcupsd-users] cable for BK500M

[Hank Barta]

I have a Back UPS 500 (model BK500M) and I'd like to use apcupsd with it
but I do not have the cable it shipped with. I am unable to find
information on the APC web site to indicate which cable is correct. I can
make one according to the instructions found at
http://www.apcupsd.org/manual/manual.html#cables. I'm not sure if this is a
'smart' or 'dumb' unit. It has a female DB9 connector on the back labeled
"computer interface port."

Is there a way to determine which cable I should make up and use or does
someone know the answer to this question? It's an old unit but I have
replaced the battery and it carries my desktop for about 20 minutes.

Thanks!

[William Pasquill]

Hi,

The BK500M uses the 940-0020 DB9F to DB9M simple signalling cable.

Post by Hank Barta
I have a Back UPS 500 (model BK500M) and I'd like to use apcupsd with it
but I do not have the cable it shipped with. I am unable to find
information on the APC web site to indicate which cable is correct. I can
make one according to the instructions found at http://www.apcupsd.org/
manual/manual.html#cables. I'm not sure if this is a 'smart' or 'dumb'
unit. It has a female DB9 connector on the back labeled "computer interface
port."
Is there a way to determine which cable I should make up and use or does
someone know the answer to this question? It's an old unit but I have
replaced the battery and it carries my desktop for about 20 minutes.
Thanks!
--
'03 BMW F650CS - hers
'98 Dakar K12RS - "BABY K" grew up.
'93 R100R w/ Velorex 700 (MBD starts...)
'95 Miata - "OUR LC"
polish visor: apply squashed bugs, rinse, repeat
Beautiful Sunny Winfield, Illinois
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Apcupsd-users mailing list
https://lists.sourceforge.net/lists/listinfo/apcupsd-users

[Hank Barta]

Post by William Pasquill
Hi,
The BK500M uses the 940-0020 DB9F to DB9M simple signalling cable.

Thank you. then what I want to make up is
http://www.apcupsd.org/manual/manual.html#simple-custom-voltage-signalling-cable-for-dumb-upses

best,
hank

[Pavel Boček]

Pinouts list few more variants: http://pinouts.ru/UPS/apc_back_cable_pinout.
shtml
--
S uctivÃœm pozdravem/best regards,

Pavel Boček
Jabber: ***@jabber.cz
[phone]
http://www.hwworld.cz (kondenzátory, akumulátory, baterie aj./capacitors and
more)
http://www.hardwareinsights.com (power supply reviews and more)

---------- Původní e-mail ----------
Od: Hank Barta <***@gmail.com>
Komu: Apcupsd Discussion List <apcupsd-***@lists.sourceforge.net>
Datum: 15. 7. 2017 0:34:53
Předmět: Re: [Apcupsd-users] cable for BK500M
"


On Fri, Jul 14, 2017 at 1:01 PM, William Pasquill <***@gmail.com
(mailto:***@gmail.com)> wrote:
"
Hi,



The BK500M uses the 940-0020 DB9F to DB9M simple signalling cable. 

"



Thank you. then what I want to make up is http://www.apcupsd.org/manual/
manual.html#simple-custom-voltage-signalling-cable-for-dumb-upses
(http://www.apcupsd.org/manual/manual.html#simple-custom-voltage-signalling-cable-for-dumb-upses)




best,

hank
--
'03 BMW F650CS - hers
'98 Dakar K12RS - "BABY K" grew up.
'93 R100R w/ Velorex 700 (MBD starts...)
'95 Miata - "OUR LC"
polish visor: apply squashed bugs, rinse, repeat
Beautiful Sunny Winfield, Illinois


----------------------------------------------------------------------------

[G2]

this board for multi UPSs is raspberry v3 running ubuntu/mate and apcupsd v 3/14/12 (29 march 2014)

i'm not sure where/why the error, listed below, is happening. the init.d/apcupsd file never gets a chance to really start. i've run the 'systemct daemon-reload' command a few times with no success in getting /init.d/apcupsd to start.

can i get a few pointers of where/how to help me fix this?
tia



#------------------------------------------------------------------------------
[....] Starting apcupsd (via systemctl): apcupsd.serviceWarning: apcupsd.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Job for apcupsd.service failed because the control process exited with error code. See "systemctl status apcupsd.service" and "journalctl -xe" for details.
failed!



● apcupsd.service - LSB: Controls the apcupsd daemon for multiple UPS devices
Loaded: loaded (/etc/init.d/apcupsd; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2017-07-14 16:52:59 PDT; 1min 25s ago
Docs: man:systemd-sysv-generator(8)
Process: 12541 ExecStart=/etc/init.d/apcupsd start (code=exited, status=203/EXEC)

Jul 14 16:52:59 rasppi-ups1 systemd[1]: Starting LSB: Controls the apcupsd daemon for multiple UPS devices...
Jul 14 16:52:59 rasppi-ups1 systemd[1]: apcupsd.service: Control process exited, code=exited status=203
Jul 14 16:52:59 rasppi-ups1 systemd[1]: Failed to start LSB: Controls the apcupsd daemon for multiple UPS devices.
Jul 14 16:52:59 rasppi-ups1 systemd[1]: apcupsd.service: Unit entered failed state.
Jul 14 16:52:59 rasppi-ups1 systemd[1]: apcupsd.service: Failed with result 'exit-code'.

#------------------------------------------------------------------------------

[Sandro Bordacchini]

Hi G2.
I have your scenario too, a raspberry pi 3 connected to 2 ups.

I decided to switch to a systemd approach to run multiple instances of
apcupsd: that is actually nativetly supported from systemd through what
they call "template unit files".

Please refer to these links to understand how they works and how you can
setup your system:
https://fedoramagazine.org/systemd-template-unit-files/
http://0pointer.de/blog/projects/instances.html
https://serverfault.com/questions/730239/start-n-processes-with-one-systemd-service-file

This is my /lib/systemd/system/***@.service file


[Unit]
Description=UPS '%i' power management daemon
Documentation=man:apcupsd(8)

[Service]
ExecStartPre=/lib/apcupsd/prestart
ExecStart=/sbin/apcupsd -f /etc/apcupsd/apcupsd-%i.conf -P
/var/run/apcupsd-%i.pid
Type=forking
KillMode=process
PIDFile=/var/run/apcupsd-%i.pid

[Install]
WantedBy=multi-user.target



I hope to have been helpful

Bye,
Sandro.

Post by G2
this board for multi UPSs is raspberry v3 running ubuntu/mate and apcupsd
v 3/14/12 (29 march 2014)
i'm not sure where/why the error, listed below, is happening. the
init.d/apcupsd file never gets a chance to really start. i've run the
'systemct daemon-reload' command a few times with no success in getting
/init.d/apcupsd to start.
can i get a few pointers of where/how to help me fix this?
tia
#-----------------------------------------------------------
-------------------
apcupsd.service changed on disk. Run 'systemctl daemon-reload' to reload
units.
Job for apcupsd.service failed because the control process exited with
error code. See "systemctl status apcupsd.service" and "journalctl -xe" for
details.
failed!
● apcupsd.service - LSB: Controls the apcupsd daemon for multiple UPS
devices
Loaded: loaded (/etc/init.d/apcupsd; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2017-07-14 16:52:59 PDT; 1min 25s ago
Docs: man:systemd-sysv-generator(8)
Process: 12541 ExecStart=/etc/init.d/apcupsd start (code=exited, status=203/EXEC)
Jul 14 16:52:59 rasppi-ups1 systemd[1]: Starting LSB: Controls the apcupsd
daemon for multiple UPS devices...
Jul 14 16:52:59 rasppi-ups1 systemd[1]: apcupsd.service: Control process
exited, code=exited status=203
Jul 14 16:52:59 rasppi-ups1 systemd[1]: Failed to start LSB: Controls the
apcupsd daemon for multiple UPS devices.
Jul 14 16:52:59 rasppi-ups1 systemd[1]: apcupsd.service: Unit entered failed state.
Jul 14 16:52:59 rasppi-ups1 systemd[1]: apcupsd.service: Failed with result 'exit-code'.
#-----------------------------------------------------------
-------------------
--
Key fingerprint = C472 148A 4185 ED70 2A61 B77C B428 3668 5D84 4495
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Apcupsd-users mailing list
https://lists.sourceforge.net/lists/listinfo/apcupsd-users

[G2]

Hey Sandro,

very interesting! this raspberrypi ubuntu/mate ver is a systemd ver and not upstart(fairly sure). i'm going to try your systemd approach. haven't read all the material from your supplied links but will this weekend.

does one still require the /etc/init.d/apcupsd file for startup?

G2

Post by Sandro Bordacchini
Hi G2.
I have your scenario too, a raspberry pi 3 connected to 2 ups.
I decided to switch to a systemd approach to run multiple instances
of apcupsd: that is actually nativetly supported from systemd
through what they call "template unit files".
https://fedoramagazine.org/systemd-template-unit-files/
http://0pointer.de/blog/projects/instances.html
https://serverfault.com/questions/730239/start-n-processes-with-one-systemd-service-file
[Unit]
Description=UPS '%i' power management daemon
Documentation=man:apcupsd(8)
[Service]
ExecStartPre=/lib/apcupsd/prestart
ExecStart=/sbin/apcupsd -f /etc/apcupsd/apcupsd-%i.conf -P /var/run/apcupsd-%i.pid
Type=forking
KillMode=process
PIDFile=/var/run/apcupsd-%i.pid
[Install]
WantedBy=multi-user.target
I hope to have been helpful
Bye,
Sandro.
this board for multi UPSs is raspberry v3 running ubuntu/mate and apcupsd v 3/14/12 (29 march 2014)
i'm not sure where/why the error, listed below, is happening. the
init.d/apcupsd file never gets a chance to really start. i've run
the 'systemct daemon-reload' command a few times with no success in getting /init.d/apcupsd to start.
can i get a few pointers of where/how to help me fix this?
tia
#------------------------------------------------------------------------------
apcupsd.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Job for apcupsd.service failed because the control process exited
with error code. See "systemctl status apcupsd.service" and "journalctl -xe" for details.
failed!
● apcupsd.service - LSB: Controls the apcupsd daemon for multiple UPS devices
Loaded: loaded (/etc/init.d/apcupsd; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2017-07-14 16:52:59 PDT; 1min 25s ago
Docs: man:systemd-sysv-generator(8)
Process: 12541 ExecStart=/etc/init.d/apcupsd start (code=exited, status=203/EXEC)
Jul 14 16:52:59 rasppi-ups1 systemd[1]: Starting LSB: Controls the
apcupsd daemon for multiple UPS devices...
Jul 14 16:52:59 rasppi-ups1 systemd[1]: apcupsd.service: Control
process exited, code=exited status=203
Controls the apcupsd daemon for multiple UPS devices.
Jul 14 16:52:59 rasppi-ups1 systemd[1]: apcupsd.service: Unit entered failed state.
Jul 14 16:52:59 rasppi-ups1 systemd[1]: apcupsd.service: Failed with result 'exit-code'.
#------------------------------------------------------------------------------

[Sandro Bordacchini]

No, you should need only the template unit file I pasted in the previous
mail.
Just pay attention when you enable the services to give the template the
exact name to match the configuration file.

S.

Post by G2
Hey Sandro,
very interesting! this raspberrypi ubuntu/mate ver is a systemd ver and
not upstart(fairly sure). i'm going to try your systemd approach. haven't
read all the material from your supplied links but will this weekend.
does one still require the /etc/init.d/apcupsd file for startup?
G2

Post by Sandro Bordacchini
Hi G2.
I have your scenario too, a raspberry pi 3 connected to 2 ups.
I decided to switch to a systemd approach to run multiple instances
of apcupsd: that is actually nativetly supported from systemd
through what they call "template unit files".
Please refer to these links to understand how they works and how you can
https://fedoramagazine.org/systemd-template-unit-files/
http://0pointer.de/blog/projects/instances.html
https://serverfault.com/questions/730239/start-n-

processes-with-one-systemd-service-file

Post by Sandro Bordacchini
[Unit]
Description=UPS '%i' power management daemon
Documentation=man:apcupsd(8)
[Service]
ExecStartPre=/lib/apcupsd/prestart
ExecStart=/sbin/apcupsd -f /etc/apcupsd/apcupsd-%i.conf -P

/var/run/apcupsd-%i.pid

Post by Sandro Bordacchini
Type=forking
KillMode=process
PIDFile=/var/run/apcupsd-%i.pid
[Install]
WantedBy=multi-user.target
I hope to have been helpful
Bye,
Sandro.
this board for multi UPSs is raspberry v3 running ubuntu/mate and

apcupsd v 3/14/12 (29 march 2014)

Post by Sandro Bordacchini
i'm not sure where/why the error, listed below, is happening. the
init.d/apcupsd file never gets a chance to really start. i've run
the 'systemct daemon-reload' command a few times with no success in

getting /init.d/apcupsd to start.

Post by Sandro Bordacchini
can i get a few pointers of where/how to help me fix this?
tia
#-----------------------------------------------------------

-------------------

Post by Sandro Bordacchini
apcupsd.service changed on disk. Run 'systemctl daemon-reload' to reload

units.

Post by Sandro Bordacchini
Job for apcupsd.service failed because the control process exited
with error code. See "systemctl status apcupsd.service" and "journalctl

-xe" for details.

Post by Sandro Bordacchini
failed!
● apcupsd.service - LSB: Controls the apcupsd daemon for multiple UPS

devices

Post by Sandro Bordacchini
Loaded: loaded (/etc/init.d/apcupsd; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2017-07-14 16:52:59

PDT; 1min 25s ago

Post by Sandro Bordacchini
Docs: man:systemd-sysv-generator(8)
Process: 12541 ExecStart=/etc/init.d/apcupsd start (code=exited,

status=203/EXEC)

Post by Sandro Bordacchini
Jul 14 16:52:59 rasppi-ups1 systemd[1]: Starting LSB: Controls the
apcupsd daemon for multiple UPS devices...
Jul 14 16:52:59 rasppi-ups1 systemd[1]: apcupsd.service: Control
process exited, code=exited status=203
Controls the apcupsd daemon for multiple UPS devices.
Jul 14 16:52:59 rasppi-ups1 systemd[1]: apcupsd.service: Unit entered

failed state.

Post by Sandro Bordacchini
Jul 14 16:52:59 rasppi-ups1 systemd[1]: apcupsd.service: Failed with

result 'exit-code'.

Post by Sandro Bordacchini
#-----------------------------------------------------------

-------------------
--
Bill
Key fingerprint = C472 148A 4185 ED70 2A61 B77C B428 3668 5D84 4495