similar to: Nut-upsuser Digest, Vol 127, Issue 3

Hi all, I'm trying to configure Nut to connect to an APC BackUPS Pro 900VA. This ups uses a serial port on which _simple_ or _smart_ signaling should be spoken. I've connected the UPS to a serial port using the original 940_0128A cable from APC. Unfortunately I've not yet managed to read any data from the ups. If I try to load the apcsmart driver it tells me that it cannot communicate

Hello Charles, >> On Sep 29, 2015, at 3:29 PM, Juergen Edner <juergen at eisfair.org> wrote: >> >> Now I wonder why it isn't possible to send a forced shutdown command >> to a specific UPS only. > > It is possible - simply send a "shutdown.reboot" or "shutdown.stayoff" > command via `upscmd`. > > Other instant commands (which

On Sep 29, 2015, at 3:29 PM, Juergen Edner <juergen at eisfair.org> wrote: > > Now I wonder why it isn't possible to send a forced shutdown command > to a specific UPS only. It is possible - simply send a "shutdown.reboot" or "shutdown.stayoff" command via `upscmd`. Other instant commands (which may or may not be implemented on your UPS):

Something just occurred to me. My kernel does not include USB->Serial code. Long ago, I had to figure out how to build a module for the ch341 USB->Serial adapter I use for running my Heyu home automation system. I never built one for Cypress and that seems to be what the Belkin is using. I know this because I see a line for it using "lsusb" that disappears if I unplug the UPS.

Hi all, I'm using Nut v2.7.3 on my Linux server to monitor two UPS at the same time, which are used to secure several different network devices. This set-up works fine for several month now. Due to the fact that different devices, connected to different UPS are generating a different load, the batteries of each UPS are discharged with a different speed. I now want to react on the events of

Hi all, I'm trying to configure Nut to connect to an APC BackUPS Pro 900VA. This ups uses a serial port on which _simple_ or _smart_ signaling should be spoken. I've connected the UPS to a serial port using the original 940_0128A cable from APC. Unfortunately I've not yet managed to read any data from the ups. If I try to load the apcsmart driver it tells me that it cannot communicate

Hello all and thanks. I read here <https://mn3m.info/posts/configure-ups-monitor-using-nut-on-debian/> while searching around for my issue's resolution. In this I see that this nut driver is creating and using an entry in /dev (in this case ttyS0). So I "ll tty*" and see nothing with nut. Since this is a USB UPS, I suppose I should be looking for something in /dev/ttyUSB*.

Hi Charles, I'll try the blazer_ser and the nutdrv_qx with version 2.7.1 later. Below, the result of 'lsusb -vvv' requested: Bus 004 Device 002: ID 04b4:5500 Cypress Semiconductor Corp. HID->COM RS232 Adapter Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass 0 (Defined at Interface level)

please subscribe to the list: http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev On Feb 19, 2014, at 7:52 AM, Thiago Tiedtke dos Reis wrote: > If I try to access the port /dev/ttyUSB0 using minicon (minicom -D /dev/ttyUSB0) or cat ( cat /dev/ttyUSB0 ), the access to device is denied. even as root? > Then, I try these instructions [0], but nothing changes when I try to

Hi All I am connecting a ups via a usb to serial converter. Works fine, however when the converter is unplugged and plugged back in, udev creates another device e.g instead of ttyUSB0 it creates ttyUSB1. Here is the udev rule that I added to the top of the 025_nut-usbups.rules file in order to create a static symlink should udev decide to create the device as either ttyUSB0 or ttyUSB1.

>> I setup apcsmart driver on port /dev/ttyUSB0 in ups.conf and check that runing user=root. >> > user=root is only for testing- this may cause other permissions problems later. It looks like the simplest way to handle this on Debian is to add the system 'nut' user to the 'dialout' group: $ sudo adduser nut dialout > I have been meaning to collect some

On May 7, 2019, at 9:09 AM, Gene Heskett wrote: > > On Tuesday 07 May 2019 08:38:44 am Charles Lepple wrote: > >> On May 7, 2019, at 5:06 AM, Gene Heskett wrote: >>> New testing install(stretch) >>> pulled in nut stuff from repo. >>> copied old wheezy configs to /etc/nut, overwriting the resident >>> files can't talk to ups, missing

thanks for these info. 2009/3/19 Artyom Mikhailov <artyom.mikhailov at gmail.com> > Hi there, > > Great project you have - NUT, thx for the development! > I just thought it might be usefull to let you know that APC SC1500I ups can > be found supported by NUT. > I used the following settings: > [sc1500i] > driver = apcsmart > port = /dev/ttyUSB0

[please use the nut-upsuser@ address rather than nut-upsuser-owner@ and be sure to use Reply-All - thanks!] On Dec 23, 2014, at 1:52 PM, Janez Kremzer <janez256 at gmail.com> wrote: > Hi! > > I woud like to use Raspberry Pi with NUT installed whic coud shut down NAS in the office. > NAS doesn't have comport and this is the reasion why not to use NAS directly. > >

Yes I do have Linux. I have assigned the ups.conf file as seen below.. [testups] Driver = usbhid-ups Port = /dev/ttyUSB0 When I try to start the ups driver I get the following error... $ sudo upsdrvctl start Network Ups Tools - UPS driver controller 2.7.1 Network Ups Tools - Generic HID driver 0.38 (2.7.1) USB communication driver 0.32 No matching HID UPS found Driver failed to start (exit

Hi, I''m having a weird validation issue. Validation isn''t working for certain attributes and, for some reason, it''s also affecting things outside of validation. For campers on certain camp types, we require some information about their school. I tried to validate the information this way: validates_presence_of :school_type, :if => Proc.new { |c| !c.booking.nil?

There is no need to set the same capabilities for each cpu individually. This can be done for all cpus in platform initialization. Cc: Alok Kataria <akataria at vmware.com> Cc: Thomas Gleixner <tglx at linutronix.de> Cc: Ingo Molnar <mingo at redhat.com> Cc: "H. Peter Anvin" <hpa at zytor.com> Cc: x86 at kernel.org Cc: virtualization at lists.linux-foundation.org

On Tuesday 07 May 2019 09:49:47 am Charles Lepple wrote: > On May 7, 2019, at 9:09 AM, Gene Heskett wrote: > > On Tuesday 07 May 2019 08:38:44 am Charles Lepple wrote: > >> On May 7, 2019, at 5:06 AM, Gene Heskett wrote: > >>> New testing install(stretch) > >>> pulled in nut stuff from repo. > >>> copied old wheezy configs to /etc/nut,

Kernel parameters aside (console=ttyUSB0 console=tty0), I am trying to get a login console working on a USB-to-serial adapter. systemctl enable serial-getty at ttyUSB0.service systemctl start serial-getty at ttyUSB0.service This works without issue on Debian 8. However when running the same on CentOS 7, my logs are filled with: May 16 12:44:58 localhost.localdomain systemd[1]: Starting Serial

Hi, On Wed, Feb 3, 2010 at 3:57 AM, Heyu Zhu <zhu.heyu at gmail.com> wrote: > Hi everyone, > > It seems variable arguments is not support by mips backend in llvm-2.6. > > int func(int i, ...) { >   return 0; > } > > llvm-gcc    func.c -emit-llvm -c  -O3   -o func.bc > llc    func.bc -relocation-model=static  -march=mips -O0  -o func.s > > Command llc