similar to: nut with 2 salicru ups

Hi NUT developers, we rely on NUT to access valuable UPS data for our autonomous telescopes (see http://rts2.org for list, locations are not complete..) . Thanks for a software which does exactly what we need. Now we are starting new era, with installing telescopes on hostile spots without infrastructure. So we will have a solar cells, storing power to batteries during day, to be used during

Hello, i try to setup NUT service to read/control my UPS but without success. Problem is when i try to start "/usr/local/ups/bin/upsdrvctl -DDDD -u root start" i got: /Network UPS Tools - UPS driver controller 2.6.2/ / 0.000000/ /If you're not a NUT core developer, chances are that you're told to enable debugging/ /to see why a driver

Hello, I have a Salicru SPS One 700VA device, I want to manage it with Debian Whezzy. I read some information in the net about how to configure but I can not get it working. Could you help with this? This is the log when I connect the USB: [ 3194.688204] usb 4-4: new low-speed USB device number 2 using ohci_hcd [ 3194.857239] usb 4-4: New USB device found, idVendor=0665, idProduct=5161 [

Hello all, I have a Salicru UPS (Salicru SPS One 700VA) working great in Debian Wheezy, but I want to move it to a OpenWRT router. I configured same as in Debian but I can not get it working: # upsd Network UPS Tools upsd 2.6.5 fopen /var/run/upsd.pid: No such file or directory listening on 192.168.1.240 port 3493 /etc/nut/ is world readable Can't connect to UPS [salicru]

On Nov 8, 2013, at 3:23 AM, Josu Lazkano wrote: > Hello, I have a Salicru SPS One 700VA device, I want to manage it with > Debian Whezzy. > > I read some information in the net about how to configure but I can > not get it working. I'm assuming you mean this blog post? http://blog.ciberterminal.net/2013/04/28/ups-salicru-en-nut/ > Could you help with this? > >

Hi, another UPS piece supported by blazer_usb: ALLSAI model LV 2K upsc output: battery.voltage: 82.08 battery.voltage.nominal: 72.0 beeper.status: enabled device.mfr: device.model: LV 2K device.type: ups driver.name: blazer_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.4.3 driver.version.internal: 0.03 input.current.nominal: 18.0 input.frequency: 59.9

On 8/19/20 12:55 PM, Marc Franquesa wrote: > Thanks all for the quick responses on the question (always a good sign > of this mailing list). > > (Tim Dawson, Manuel Wolfshant): > Regarding root cause of my current problem pointing to a faulty > battery, this is not the first time that someone points to it. However > I made a simple test with the vendor tools (Windows) and

On Feb 8, 2015, at 2:29 PM, Josu Lazkano <josu.lazkano at gmail.com> wrote: > # upsd > Network UPS Tools upsd 2.6.5 > fopen /var/run/upsd.pid: No such file or directory > listening on 192.168.1.240 port 3493 > /etc/nut/ is world readable > Can't connect to UPS [salicru] (blazer_usb-salicru): No such file or directory Check the messages from the blazer_usb driver when

Sorry, because this is not a technical question rather than a Hardware advice/recommendation. I have been using NUT-UPS perfectly for more than 7 years using two different Eaton/MGE models. After a battery replacement (replaced 1 year ago) after 5 years of service, my current unit seems to behave faulty, as just after 1-2 minutes of power outage, shows the LB battery flag and sets FSD although

Hi, I am not sure if you are the list to hit with this, but NUT's megatec driver support ours "Numeric Digital 3000 sw" UPS - at least that's what it claims on front- at the Watcher telescope at Boyden Observatory / RSA. I wasn't able to find manufacturer, but it looks Numeric is some existing UPS factory. I did not receive any informations from manufacturer, so I believ

Not of a big help here, but I think it's a voltronic power vesta 650: http://www.voltronicpower.com/oCart2/index.php?route=product/product&path=37&product_id=52 If that is the case, it should work both with the blazer drivers (i.e. all but the shutdown sequence) and with the now defunct voltronic ones. With arno's words: "We are currently merging a new driver to replace

i am trying to build an R package and submit to CRAN. i am using - package.skeleton(name="xxzz", code_files = "H:\xxzz.R") to build package xxzz. --------------------------- The code above generates 'xxzz' folder. It seems that I have to manually edit the files generated in xxzz folder (to add titles, authors, etc) -------------------------- But when I re-run -

Each register is a 4-component (namely, r, g, b, a) vector register. They are actually defined as llvm packed [4xfloat]. The instruction: add_sat r0.a, r1_bias.xxyy, r3_x2.zzzz Explaination: '.a' is a writemask. only the specified component will be update '.xxyy' and '.zzzz' are swizzle masks, specify the component permutation, simliar to the Intel SSE permutation

Actually the problems that Tzu-Chien Chiu are encountering are similar to what should be done for generating SSE code in the X86 backend and also other SIMD instruction sets. I think LLVM neeeds to add instructions for permuting components, extracting and injecting elements in packed types. If the architecture has instructions which can do permutations for each instruction (for example

What am I doing wrong? (please cc me when replying) yy <- 1:10 xx <- yy*2 xYplot(yy~xx,ylab="") #this plots as it should text(.4,5,expression(paste(log, frac(p(b),p(a)) ))) Error in text.default(0.4, 13, expression(paste(log, frac(p(b), p (a))))) : plot.new has not been called yet This is the case even when I write: xxyy <- xYplot(yy~xx,ylab="") xxyy <-

Hello, I wanted to send an email to the administrator of the web to update an information, I do not know if this mailing list is appropriate. I just wanted to say that I have a UPS SALICRU SOHO + 1600VA and after several days trying to configure it I found out the problem. This UPS has usb 1.0 HID, so it does not work with the driver usb blazer if you have to use the driver usbhid-ups. I think

I have a device that seems almost, but not quite supported, I'd like very much to help get it working, though I am no programmer. Feel free to ask me to test :) This could probably go in https://networkupstools.org/ddl/ : -------file: Salicru__SPS_2000_ADV_T__usbhid-ups__2.8.1-94-gd59c05349__01.dev , or maybe 1__2000__usbhid-ups__2.8.1-94-gd59c05349__01.dev # DEVICE:URL:VENDOR:

Thanks Charles, This is the permission tree: # ls -l /dev/bus/usb/001/001 crw-r--r-- 1 root root 189, 0 Feb 8 20:23 /dev/bus/usb/001/001 If I attache the USB cable there is nothing in dmesg, and there is nothing in lsusb: # lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub It looks like it is not detected. In Debian it looks great: # lsusb Bus 004 Device

I would also be very interested in this topic. Best Regards, Bart pon., 17 sie 2020, 12:55 użytkownik Marc Franquesa <marc.franquesa at gmail.com> napisał: > Sorry, because this is not a technical question rather than a Hardware > advice/recommendation. > > I have been using NUT-UPS perfectly for more than 7 years using two > different Eaton/MGE models. > > After a

Thanks all for the quick responses on the question (always a good sign of this mailing list). (Tim Dawson, Manuel Wolfshant): Regarding root cause of my current problem pointing to a faulty battery, this is not the first time that someone points to it. However I made a simple test with the vendor tools (Windows) and didn't found any issue, as well as they discharged normally (although only