[Nut-upsuser] APC Back UPS?

[Ben Kamen]

On 12/28/18 6:28 PM, David Melik wrote:
> On 12/27/18 8:09 AM, Charles Lepple wrote:
>> [...] That's Ben's point - either it is actual Ethernet (usually found on an add-on UPS SNMP monitoring card, where the jack typically has two status LEDs, one on either side of the notch for the modular plug tab) that needs to go to another Ethernet jack on a NIC or a switch, or it is a proprietary APC cable that vaguely resembles an Ethernet cable on one end. (I was incorrect when I said 8P8C before - MGE uses 8P8C modular jacks for similar USB/serial proprietary cables.) [...]
>
> On 12/27/18 8:17 AM, Charles Lepple wrote:
>> [...] Correction to my correction: apparently APC uses both 8-pin and 10-pin modular jacks.
>>
>> The SmartUPS C1000 has a 10-pin jack labeled serial (and the industry-standard USB Type B jack for USB, hooray), but for your models, a few images online seem to show an 8-pin jack labeled "data port" for the BackUPS Pro 1000 and BackUPS NS 1080. [...] 
>
> On 12/28/18 12:30 AM, Manuel Wolfshant wrote:
>> [...] No, they are USB cables with dubious connectors :)
>> You could look for the pinout on internet and make one. That's what I did. After all there are only 4 wires. 2 for data, V+ and V-.
>
> I guess I'm a bit off-topic now, but found zero results for 'APC eight-pin cable' in Google.  Does anyone have the image, or if I asked my local PC shop to make cables, do you think they would know?  I'll probably ask them as they gave/sold me the UPSes and I don't feel skilled with hardware... 



I have one of these cables somewhere. I'll look to see if I can find it.

  -Ben


-- 
Ben Kamen - O.D.T., S.P.
----------------------------------------------------------------------
Email: ben AT benkamen DOT net                 http://www.benkamen.net
Cell:  224.619.9006                http://www.linkedin.com/in/benkamen
-                                                                    -
NOTICE: All legal disclaimers sent to benkamen.net
or any of its affiliated domains are rendered null and void on
receipt of communications and will be handled/considered as such.