cable for BK500M

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

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!

--
'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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: cable for BK500M

William Pasquill
Hi,

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

On Fri, Jul 14, 2017 at 8:12 AM, Hank Barta <[hidden email]> wrote:
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users



------------------------------------------------------------------------------
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: cable for BK500M

Hank Barta
On Fri, Jul 14, 2017 at 1:01 PM, William Pasquill <[hidden email]> wrote:
Hi,

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


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

------------------------------------------------------------------------------
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users
G2
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RaspberryPi v3 ubuntu/mate apcupsd init.d not starting

G2
In reply to this post by Hank Barta
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'.

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




--

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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: cable for BK500M

Pavel Boček
In reply to this post by Hank Barta
Pinouts list few more variants: http://pinouts.ru/UPS/apc_back_cable_pinout.shtml

--
S uctivým pozdravem/best regards,

Pavel Boček
Jabber: [hidden email]
+420 739 190 151
http://www.hwworld.cz (kondenzátory, akumulátory, baterie aj./capacitors and more)
http://www.hardwareinsights.com (power supply reviews and more)


On Fri, Jul 14, 2017 at 1:01 PM, William Pasquill <[hidden email]> wrote:
Hi,

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


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
------------------------------------------------------------------------------
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users

------------------------------------------------------------------------------
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: RaspberryPi v3 ubuntu/mate apcupsd init.d not starting

Sandro Bordacchini
In reply to this post by G2
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:

This is my /lib/systemd/system/multipleapcupsd@.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.

2017-07-15 2:10 GMT+02:00 G2 <[hidden email]>:
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'.

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




--

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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users


------------------------------------------------------------------------------
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users
G2
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: RaspberryPi v3 ubuntu/mate apcupsd init.d not starting

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


> 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/multipleapcupsd@.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.

> 2017-07-15 2:10 GMT+02:00 G2 <[hidden email]>:

> 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'.


> #------------------------------------------------------------------------------




--
Bill
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: RaspberryPi v3 ubuntu/mate apcupsd init.d not starting

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.


2017-07-16 2:18 GMT+02:00 G2 <[hidden email]>:
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


> 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/multipleapcupsd@.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.

> 2017-07-15 2:10 GMT+02:00 G2 <[hidden email]>:

> 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'.


> #------------------------------------------------------------------------------




--
Bill
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users
Loading...