[Nut-upsuser] safenet on debian etch
Hi List, I just got myself a new everpower-1000va. according to the compatibility list, the 'safenet' driver supposed to support it, however, when I try, I get this in syslog: Jul 24 15:05:22 tv upsd[26458]: Can't connect to UPS [everpower1000] (safenet-ttyS1): No such file or directory this is my ups.conf: [everpower1000] driver = safenet port = /dev/ttyS1 desc = firefang.net I am using nut installed via apt on debian-etch. any suggestions? Omry. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] safenet on debian etch
mån 2006-07-24 klockan 15:06 +0300 skrev Omry Yadan: Hi List, Hi Omry, I just got myself a new everpower-1000va. according to the compatibility list, the 'safenet' driver supposed to support it, however, when I try, I get this in syslog: Jul 24 15:05:22 tv upsd[26458]: Can't connect to UPS [everpower1000] (safenet-ttyS1): No such file or directory As you can see, it is the upsd that need to connect. Check that you have the /var/state/ups dirrectory, and that it is writable by the user you run nut as. What upsd is looking for is the socket named safenet-ttyS1. This should be created in /var/state/ups. This is how it looks on my computer running bcmxcp-usb driver. ls -al /var/state/ups/ totalt 8 drwxrwx--- 2 nut nut 144 24 jul 08.39 . drwxr-xr-x 3 root root 96 23 feb 15.52 .. srw-rw 1 nut nut0 24 jul 08.39 bcmxcp_usb-auto -rw-r--r-- 1 nut nut5 24 jul 08.39 bcmxcp_usb-auto.pid -rw-r--r-- 1 nut nut5 24 jul 08.39 upsd.pid this is my ups.conf: [everpower1000] driver = safenet port = /dev/ttyS1 desc = firefang.net Ok. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] safenet on debian etch
I just got myself a new everpower-1000va. according to the compatibility list, the 'safenet' driver supposed to support it, That depends. The hardware this driver is written for is usually OEM equipment and vendors tend to shop for the lowest bidder. So quite often they change the internals of the UPS, without changing the typenumber or even the box it is packaged in. If your UPS came with 'SafeNet v1.0' software for Windows (either in the box or via download) it should be supported by this driver. If something else is bundled, you'll have to continue your search as it probably won't be supported by this driver. however, when I try, I get this in syslog: Jul 24 15:05:22 tv upsd[26458]: Can't connect to UPS [everpower1000] (safenet-ttyS1): No such file or directory This usually means the safenet driver isn't running. You may want to run the driver from the commandline with '-D' added to make it more verbose. Chances are that it will be telling you why it can't be started. This can be as trivial as a serial port without the proper permissions. [...] I am using nut installed via apt on debian-etch. This isn't very helpful for people not running Debian. Please list version number of kernel and NUT. Regards, Arjen -- Eindhoven - The Netherlands Key fingerprint - 66 4E 03 2C 9D B5 CB 9B 7A FE 7E C1 EE 88 BC 57 -- Eindhoven - The Netherlands Key fingerprint - 66 4E 03 2C 9D B5 CB 9B 7A FE 7E C1 EE 88 BC 57 ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Problems with MGE ESV 8+ and NUT 2.0.3
Hello, I recently had a failure with my old MGE ESV8 ups, it just died on me so I had to get a new one. I found a MGE ESV8+ cheap and everything seems to work fine with it except the communication with the computer. The old ESV8 (non +) worked fine with NUT after applying some patches I got from the mailing list, but I think they are in the source tree now. I'm using the same cable that worked with my old ups, as it's the same protocol mge-utalk and same cable to the new ups. I'm running FreeBSD 6.1 amd64 with NUT 2.0.3 installed from ports and my problem is that I can't seem to get any data out of the UPS. When starting upsd I get this: Network UPS Tools - UPS driver controller 2.0.3 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.87 (2.0.3) Could not get multiplier table: using raw readings. .Detected Si on /dev/cuad0 updateinfo: Cannot update system status Starting nut. Network UPS Tools upsd 2.0.3 Connected to UPS [ups]: mge-utalk-cuad0 Synchronizing giving up and my message log is filled with: Jun 29 13:14:12 zeus mge-utalk[78111]: updateinfo: Cannot update system status Jun 29 13:14:12 zeus upsd[78121]: Data for UPS [ups] is stale - check driver Jun 29 13:14:13 zeus upsd[78121]: UPS [ups] data is no longer stale Jun 29 13:14:23 zeus mge-utalk[78111]: updateinfo: Cannot update system status Jun 29 13:14:23 zeus upsd[78121]: Data for UPS [ups] is stale - check driver Jun 29 13:14:23 zeus upsd[78121]: UPS [ups] data is no longer stale I'm able to run upsc but I get no data out of the ups: battery.charge: 000.0 battery.charge.low: 00 battery.runtime: 0 battery.voltage: 000.0 battery.voltage.nominal: 000.0 driver.name: mge-utalk driver.parameter.port: /dev/cuad0 driver.version: 2.0.3 driver.version.internal: 0.87 input.frequency: 00.00 input.transfer.boost.high: 000.0 input.transfer.boost.low: 000.0 input.transfer.high: 000.0 input.transfer.low: 000.0 input.transfer.trim.high: 000.0 input.transfer.trim.low: 000.0 input.voltage: 000.0 output.current: 000.0 output.voltage: 000.0 ups.delay.shutdown: 000 ups.delay.start: 000 ups.firmware: 1 ups.id: Si 1 ups.load: 000.0 ups.mfr: MGE UPS SYSTEMS ups.model: Si ups.status: ups.temperature: 000.0 ups.test.interval: 000 This is what my conf files looks like.. ups.conf: [ups] driver = mge-utalk port = /dev/cuad0 desc = MGE Pulsar ESV 8+ upsd.conf: ACL all 0.0.0.0/0 ACL localhost 127.0.0.1/32 ACL localnet 192.168.1.0/24 ACCEPT localhost ACCEPT localnet REJECT all Any ideas what I can do to get this to work? MGE ESV8+ should be supported, right? My ESV8 worked just fine. I'm glad for all help I can get. -- Daniel Johansson - [EMAIL PROTECTED] smime.p7s Description: S/MIME Cryptographic Signature ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Problems with MGE ESV 8+ and NUT 2.0.3
Hi Daniel,2006/6/29, Daniel Johansson [EMAIL PROTECTED]: Hello, I recently had a failure with my old MGE ESV8 ups, it just diedon me so I had to get a new one. I found a MGE ESV8+ cheap andeverything seems to work fine with it except the communication with thecomputer. The old ESV8 (non +) worked fine with NUT after applying some patches I got from the mailing list, but I think they are in the sourcetree now. I'm using the same cable that worked with my old ups, as it'sthe same protocol mge-utalk and same cable to the new ups.I'm running FreeBSD 6.1 amd64 with NUT 2.0.3 installed from ports and myproblem is that I can't seem to get any data out of the UPS.When starting upsd I get this:Network UPS Tools - UPS driver controller 2.0.3Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.87 (2.0.3)Could not get multiplier table: using raw readings..Detected Si on /dev/cuad0updateinfo: Cannot update system statusStarting nut.Network UPS Tools upsd 2.0.3Connected to UPS [ups]: mge-utalk-cuad0 Synchronizing giving upand my message log is filled with:Jun 29 13:14:12 zeus mge-utalk[78111]: updateinfo: Cannot update systemstatusJun 29 13:14:12 zeus upsd[78121]: Data for UPS [ups] is stale - check driver Jun 29 13:14:13 zeus upsd[78121]: UPS [ups] data is no longer staleJun 29 13:14:23 zeus mge-utalk[78111]: updateinfo: Cannot update systemstatusJun 29 13:14:23 zeus upsd[78121]: Data for UPS [ups] is stale - check driver Jun 29 13:14:23 zeus upsd[78121]: UPS [ups] data is no longer staleI'm able to run upsc but I get no data out of the ups:battery.charge: 000.0battery.charge.low: 00battery.runtime: 0battery.voltage : 000.0battery.voltage.nominal: 000.0driver.name: mge-utalkdriver.parameter.port: /dev/cuad0driver.version: 2.0.3driver.version.internal: 0.87input.frequency: 00.00 input.transfer.boost.high: 000.0input.transfer.boost.low: 000.0input.transfer.high: 000.0input.transfer.low: 000.0input.transfer.trim.high: 000.0input.transfer.trim.low: 000.0input.voltage: 000.0 output.current: 000.0output.voltage: 000.0ups.delay.shutdown: 000ups.delay.start: 000ups.firmware: 1ups.id: Si 1ups.load: 000.0ups.mfr: MGE UPS SYSTEMSups.model : Siups.status:ups.temperature: 000.0ups.test.interval: 000This is what my conf files looks like..ups.conf:[ups]driver = mge-utalkport = /dev/cuad0desc = MGE Pulsar ESV 8+ upsd.conf:ACL all 0.0.0.0/0ACL localhost 127.0.0.1/32ACL localnet 192.168.1.0/24ACCEPT localhost ACCEPT localnetREJECT allAny ideas what I can do to get this to work? MGE ESV8+ should besupported, right? My ESV8 worked just fine. I'm glad for all help I can get.please, send back a gzip'ed output of mge-utalk -D -a ups Also, have you tried the tip mentionned in mge-utalk manpage (section KNOWN ISSUES) Repetitive stale status ‐ Loss of communication Older models, such as ES/ESV ones, might report repetitive data stale errors. This is due to the fact that these models doesn't support too much polling. To solve this problem, add pollinter‐ val=20 in ups.conf, and change the value of MAXAGE to 25 in upsd.conf, and DEADTIME to 25 in upsmon.conf.Arnaud-- Linux / Unix Expert - MGE UPS SYSTEMS - RD DptNetwork UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/OpenSource Developer - http://arnaud.quette.free.fr/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Tripp Lite Smart1000LCD driver problem
Thanks Kjell for the help with the build problem. Thanks for your input, too, Charles. Now I have a new problem that I think has already been solved. I have Tripp Lite Smart1000LCD UPS (usb), but I can't get the newhidups driver to communicate correctly. I found a thread on the development list from last December where Jonathan Freedman described had a problem with this UPS in a thread called Fun with TrippLite. The problem apparently was resolved with some help from Charles, so presumably is can work. The command I'm trying is: newhidups -x vendorid=09ae -x productid=2005 -DD -uroot auto The relevant part of the output: Checking device (09AE/2005) (001/003) - VendorID: 09ae - ProductID: 2005 - Manufacturer: Tripp Lite - Product: TRIPP LITE UPS - Serial Number: 692195 A - Bus: 001 Trying to match device Device matches HID descriptor retrieved (Reportlen = 459) Unable to get Report descriptor (-75) No appropriate HID device found No matching HID UPS found In case it is helpful, lsusb -v gives the following for the UPS (trimmed for brevity--let me know if you want it all): Bus 001 Device 003: ID 09ae:2005 Tripp Lite Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x09ae Tripp Lite idProduct 0x2005 bcdDevice0.10 iManufacturer 3 Tripp Lite iProduct1 TRIPP LITE UPS iSerial 2 692195 A bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Devices bInterfaceSubClass 0 No Subclass bInterfaceProtocol 0 None iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 bytes 8 once bInterval 40 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.10 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 618 Report Descriptor: (length is 618) Item(Global): Usage Page, data= [ 0x84 ] 132 Power Device Page Item(Local ): Usage, data= [ 0x04 ] 4 UPS Item(Main ): Collection, data= [ 0x01 ] 1 Application Item(Local ): Usage, data= [ 0x24 ] 36 Power Summary Item(Main ): Collection, data= [ 0x02 ] 2 Logical Item(Global): Usage Page, data= [ 0x84 ] 132 Power Device Page Item(Global): Report ID, data= [ 0x28 ] 40 Item(Local ): Usage, data= [ 0xfe ] 254 iProduct cut Thanks for any help! Phil ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] safenet on debian etch
first of all, I am using version 2.0.2 on kernel 2.6.15 I played with the init.d startup script, and figured it was indeed a permissions problem accessing the port file. now I have, as you anticipated, a new problem : the protocol does not seem to match. this is what I get when I try: # /etc/init.d/nut start Starting Network UPS Tools:Network UPS Tools - UPS driver controller 2.0.2 Network UPS Tools - Generic SafeNet UPS driver 0.03 (2.0.2) Communications with UPS lost: Status read failed Communications with UPS lost: Status read failed SafeNet protocol compatible UPS not found on /dev/ttyS1 Driver failed to start (exit status=1) (upsdrvctl failed). any suggestions? Omry. Arjen de Korte wrote: I just got myself a new everpower-1000va. according to the compatibility list, the 'safenet' driver supposed to support it, That depends. The hardware this driver is written for is usually OEM equipment and vendors tend to shop for the lowest bidder. So quite often they change the internals of the UPS, without changing the typenumber or even the box it is packaged in. If your UPS came with 'SafeNet v1.0' software for Windows (either in the box or via download) it should be supported by this driver. If something else is bundled, you'll have to continue your search as it probably won't be supported by this driver. however, when I try, I get this in syslog: Jul 24 15:05:22 tv upsd[26458]: Can't connect to UPS [everpower1000] (safenet-ttyS1): No such file or directory This usually means the safenet driver isn't running. You may want to run the driver from the commandline with '-D' added to make it more verbose. Chances are that it will be telling you why it can't be started. This can be as trivial as a serial port without the proper permissions. [...] I am using nut installed via apt on debian-etch. This isn't very helpful for people not running Debian. Please list version number of kernel and NUT. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripp Lite Smart1000LCD driver problem
What does /proc/bus/usb/devices say about the UPS? -- - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripp Lite Smart1000LCD driver problem
Here's the relevant /proc/bus/usb/devices output: T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 3 Spd=1.5 MxCh= 0 D: Ver= 1.10 Cls=00(ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=09ae ProdID=2005 Rev= 0.10 S: Manufacturer=Tripp Lite S: Product=TRIPP LITE UPS S: SerialNumber=692195 A C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=(none) E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=40ms Thanks! Phil ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Error during make: *** No rule to make target `usb.h', needed by `tripplite-hid.o'. Stop.
2006/7/24, Charles Lepple [EMAIL PROTECTED]: On 7/23/06, Kjell Claesson [EMAIL PROTECTED] wrote: Hi Phil. lör 2006-07-22 klockan 12:25 -0500 skrev Phil DeBoest: I downloaded the latest development tree (revision 471), ran configure with the following command: ./configure --with-user=nut --with-drivers=tripplite-hid[...] It bombs out on the make as the target is an usb driver. But it builds on the 'make usb'. Actually, it looks like tripplite-hid is a sub-driver of newhidups, sothat could be confusing the configure script as well.Kjell was right. a depend update was needed, and done this afternoon. Everything seems fine now. But it's also right that the above call isn't good... Arnaud-- Linux / Unix Expert - MGE UPS SYSTEMS - RD DptNetwork UPS Tools (NUT) Project Leader - http://www.networkupstools.org/Debian Developer - http://people.debian.org/~aquette/OpenSource Developer - http://arnaud.quette.free.fr/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Re: UPS data.
Hi Chris, I am cc'ing this to the nut-upsuser mailing list. Chris Hotte wrote: Hello Peter! First of all, allow me to thank you in advance for all the work and information you have assembled on UPS devices. I'm currently (not a pun) investigating UPS solutions for my Linux based server. The summer has hit and were getting a lot of brownouts. I would like to get a 900VA box that can handle both my Linux box and windows box and single display together. http://www.canadacomputers.com/index.php?do=ShowProductcmd=pdpid=010761cid=PS.643 I'm wondering if the USB can be run through a hub and used with both computers. I kicked around the web for a bit and found no mention of this being tried. Unlike Ethernet, USB is not a symmetric protocol. You can have hubs, but each hub can only have a single uplink and multiple downlinks. By definition, computers are up and devices are down, so you can connect an (almost) unlimited number of devices to a single computer, but not multiple computers to a single device. So as far as I know, what you suggest cannot be done with USB. However, it is not really necessary to drive the USB from both computers. For starters, you can use the USB without any driver, and this will bridge short and medium-length blackouts and brownouts without any need to shut down the operating system. The purpose of the driver is only to shut down the computer cleanly just before the battery runs out. Also, NUT allows computers to listen to shutdown requests from drivers that run on other computers. Thus, the computer that has the USB attached is the master, and the others are slaves that receive notifications of critical events. This is done via ordinary network sockets (i.e., TCP/IP). However, I don't know how this works with a Windows machine. Someone on this list might know. Does the daemon poll the UPS periodically to determine status? Alternatively, does the driver set up an interrupt vector for the UPS to call the daemon? The second approach makes more sense in terms of the cost of polling air, but has the downside of breaking any possibility of my envisioned two computer setup. As far as I know, both can happen and do happen within the NUT newhidups driver. Not all UPS devices are well-engineered, and some don't support interrupt pipelines correctly. In any case, if you're not a driver writer, chances are this will make little difference to you. The overhead in doing a poll every 5 seconds or so is minimal. I've done no USB programming so I don't know if this is even feasible within the domain of the USB protocol. Is the USB broadcast or is it coded with a device id destination like IP? Neither, actually. A USB device is accessed, at the protocol level, as a physical path, for example, the 3rd device on the hub which is the 2nd device on the hub which is the 4th device on the root hub which is on the 4th controller The operating system usually provides an abstraction so that you (and the driver) don't actually need to see this mess. -- Peter Questions, questions, questions. *laugh* Thanks for any answer you might have, - Chris. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
