similar to: Changing UPS to a bigger APC 1500 1000WA, what driver?

On Sep 14, 2019, at 3:30 PM, Gene Heskett wrote: > > I've drug it as far under the table as I can get it on a 30% heart. > Yeah, I'm getting on, I'll be 85 in about 2 weeks. Heart surgury will be > scheduled in the next few days to replace a worn out, leaky aortic > valve. Piece if cake if my veins are big enough. > Hope the procedure goes well! > gene at

On Sunday 08 December 2019 22:17:39 Gene Heskett wrote: > On Sunday 08 December 2019 21:48:03 Charles Lepple wrote: > > On Dec 7, 2019, at 7:01 PM, Gene Heskett <gheskett at shentel.net> wrote: > > > What driver do I now put in /etc/nut/ups.conf? hid-generic doesn't > > > seem to want to talk to it, and the original name _(usbhid-ups) > > >

Greetings all; Mother nature stomping around bumping the service enough to kill a print job, but the ender 3 can be restarted from where it was interrupted. So when that job was done, I strung a 50 foot cord from an outlet driven by the 1500 WA supply, and restarted that job for the 3rd time. Thats a startup draw of 250 watts or so added to this ups. So once that was done and the job was

Hi Charles; Had a fire on the mobo of my old server, replaced it all with about 10x the hardware. dmesg now says this: 71068.842780] usb 1-9: new full-speed USB device number 10 using xhci_hcd [71069.012577] usb 1-9: New USB device found, idVendor=051d, idProduct=0003 [71069.012579] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [71069.012579] usb 1-9: Product:

On Wed, 8 Jan 2020, Gene Heskett wrote: > On Wednesday 08 January 2020 06:44:03 Roger Price wrote: >> I am surprised that there is no ups.delay.start for this UPS. > My new APC Smart-UPS_1500 doesn't have it either. Hello Gene, The NUT 2.7.2 "device dump library" entry for the APC Smart-UPS 1500 at https://networkupstools.org/ddl/APC/Smart-UPS_1500.html shows an entry

Greetings Jim & friends; Just installed nut 2.7.4 on a debian bullseye system. ups is: Bus 001 Device 006: ID 051d:0003 American Power Conversion UPS Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor

On 6/19/23 18:57, gene heskett wrote: > Greetings Jim & friends; > > Just installed nut 2.7.4 on a debian bullseye system.? ups is: > Bus 001 Device 006: ID 051d:0003 American Power Conversion UPS > Device Descriptor: > ? bLength??????????????? 18 > ? bDescriptorType???????? 1 > ? bcdUSB?????????????? 2.00 > ? bDeviceClass??????????? 0 > ?

On 6/19/23 20:29, gene heskett wrote: Some speeling korrections > On 6/19/23 18:57, gene heskett wrote: >> Greetings Jim & friends; >> >> Just installed nut 2.7.4 on a debian bullseye system.? ups is: >> Bus 001 Device 006: ID 051d:0003 American Power Conversion UPS >> Device Descriptor: >> ?? bLength??????????????? 18 >> ?? bDescriptorType????????

Gene's posting: https://alioth-lists.debian.net/pipermail/nut-upsuser/2020-January/011654.html contains a NUT 2.7.4 update for the APC Smart-UPS_1500 device dump at https://networkupstools.org/ddl/APC/Smart-UPS_1500.html Please note the changes since the 2.7.2 report, e.g. ups.delay.start is no longer supported. Roger

On Wednesday 08 January 2020 15:44:10 Roger Price wrote: > Gene's posting: > https://alioth-lists.debian.net/pipermail/nut-upsuser/2020-January/011 >654.html contains a NUT 2.7.4 update for the APC Smart-UPS_1500 device > dump at https://networkupstools.org/ddl/APC/Smart-UPS_1500.html > > Please note the changes since the 2.7.2 report, e.g. ups.delay.start > is no longer

On Sunday 08 December 2019 21:48:03 Charles Lepple wrote: > On Dec 7, 2019, at 7:01 PM, Gene Heskett <gheskett at shentel.net> wrote: > > What driver do I now put in /etc/nut/ups.conf? hid-generic doesn't > > seem to want to talk to it, and the original name _(usbhid-ups) > > doesn't work from new mobo. Oh wait, I can't spell. But that didn't > >

On Thu, 2 Jan 2020, Harlan Stenn wrote: > On 1/2/2020 3:12 AM, Roger Price wrote: >> On Wed, 1 Jan 2020, Gene Heskett wrote: >>> But I should preface this with the fact that I have a 20kw nat gas >>> fired standby with a sub 10 second startup time in the back yard. >>> > My understanding is: > > If there is a power outage, there comes a point where

> >> Maybe it's not a standard ethernet-to-UPS cable? > > 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

Has anyone been able to get an APC Smart UPS C1000 to work with NUT on pfSense? I can't figure it out. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20120830/d1f5b864/attachment.html>

On 12/26/18 8:55 AM, Charles Lepple wrote: > On Dec 25, 2018, at 4:07 AM, David Melik wrote: >> Lately I got (used) an APC Back UPS Pro 1000 and Back UPS NS 1080. I got an [8P8C]-to-USB cable from another UPS, but the Pro isn't detected (with usbhid-ups.) I haven't tried the NS yet but it seems to not be on the list though looks just like the Pro. >> > There are a few

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

On Wednesday 08 January 2020 06:44:03 Roger Price wrote: > On Tue, 7 Jan 2020, Eyal Lebedinsky wrote: > > On 2020-01-07 23:01, Roger Price wrote: > >> There is no report for variable "ups.delay.start" in your upsc > >> output. What does command "upsc <ups> ups.delay.start" report? > > > > $ upsc eaton ups.delay.start > > Init

On Sat, 6 May 2023 10:15:29 +0800, Hao Chen <chenh at yusur.tech> wrote: > When VIRTIO_NET_F_MTU(3) Device maximum MTU reporting is supported. > If offered by the device, device advises driver about the value of its > maximum MTU. If negotiated, the driver uses mtu as the maximum > MTU value. But there the driver also uses it as default mtu, > some devices may have a maximum

On Sat, May 06, 2023 at 10:15:29AM +0800, Hao Chen wrote: > When VIRTIO_NET_F_MTU(3) Device maximum MTU reporting is supported. > If offered by the device, device advises driver about the value of its > maximum MTU. If negotiated, the driver uses mtu as the maximum > MTU value. But there the driver also uses it as default mtu, > some devices may have a maximum MTU greater than 1500,

On 6 May 2023 09:56:35 BST, Hao Chen <chenh at yusur.tech> wrote: >In the current code, if the maximum MTU supported by the virtio net hardware is 9000, the default MTU of the virtio net driver will also be set to 9000. When sending packets through "ping -s 5000", if the peer router does not support negotiating a path MTU through ICMP packets, the packets will be discarded.