similar to: Can't select phoenix as subdriver in megatec_usb

Dear Andreas, some googling revealed, you created a driver for the xanto series of online-usv.de. In what state it is currently? I've to manage a S2000 and would like to use nut for it, is it usable by now? Do you need another tester? TIA, Pete

Hi, a few days ago, I bought some of those Mustek UPSes that have both a serial and a USB connector. Currently only the serial port is supported by the megatec driver. This works fine so far. Now I have seen there is a megatec_usb driver, which currently only supports 2 other UPSes. How can I help to find out whether the PowerMust might actually work with the megatec_usb driver? -- Regards,

can you also give a try to megatec and send us back some upsc output of your various tests? Mathias Mayrhofer wrote: > > Arnaud QUETTE wrote: > > > Mathias Mayrhofer wrote: > it works (except of the temperature) > > thanks a million!! > > > > Sorry to bother you, > > > 'nut' is great (it was the only thing that worked on by belkin usv), >

Looking for ioctl() calls in the drivers, I noticed that the energizerups.c code looks a lot like a megatec protocol over a USB connection. It uses 8 bytes per packet, which makes it look like the agiler subdriver in megatec_usb. Do we know if there are people that use this driver now and that might be able to verify this? Best regards, Arjen -- Eindhoven - The Netherlands Key fingerprint - 66

j T wrote: > >- allow the value to be NULL if a subdriver does not require > > initialization. > > Am I right in thinking that this is simply a case of doing: > > subdriver_t some_subdriver = { > /* ... */ > some_format_serial, > NULL, > } > > Rather than: > > subdriver_t belkin_subdriver = { > /* ... */ >

Ok, so please correct me if I?m wrong?. The quickest way to get my UPS running with nut (as the current release exists) is to either: 1) Add my vendor and device ID to the openups_usb_device_table OR 2) Create my own driver file, and then add that driver to the usbhid-ups subdriver_list And then recompile/install. Obviously #1 will be easier at this point, but I understand that it

On Feb 25, 2015, at 11:35 AM, Rob Groner <rgroner at RTD.com> wrote: > The quickest way to get my UPS running with nut (as the current release exists) is to either: > > 1) Add my vendor and device ID to the openups_usb_device_table OR > 2) Create my own driver file, and then add that driver to the usbhid-ups subdriver_list > > And then recompile/install.

Hi! Are there any subdriver to get PowerMust 600 work with megatec_usb already? I've tried with agile, but that dosen't work. My only way is to use the RS-232 cable and a COM port, but the problem is that I have only one, and a remote control was plugged there jejeje. If someone needs a "Guinea pig", I don't mind (I have the UPS working with the RS-232...) Thanks!

Browsing through the newhidups.c code, I stumbled across the following: /* master list of avaiable subdrivers */ static subdriver_t *subdriver_list[] = { #ifndef SHUT_MODE &generic_subdriver, #endif &mge_subdriver, #ifndef SHUT_MODE &apc_subdriver, &belkin_subdriver, &tripplite_subdriver, NULL #endif }; Shouldn't the 'NULL' terminator be outside the

Hello all: I have a Yukai PowerMust 1000 USB and it used to work on another computer using megatec_usb driver. Now, I have it in a new computer, but the driver does not detect it. It is there: # lsusb|grep Cypress Bus 006 Device 007: ID 0665:5161 Cypress Semiconductor USB to Serial Permissions are OK: # ls -l /dev/bus/usb/006/007 crw-rw-r-- 1 root nut 189, 646 ago 8 01:51

Hi all, I attached a driver for MiniBox openUPS device ( http://www.mini-box.com/OpenUPS) and a dump of the hid usages. I had the possibility to make a few adjustments to the device firmware for HID usages, and although I haven't managed to produce a good structure many issues from previous firmware were at least fixed and new information added. ATM the driver only shows pertaining

Hi Sven, 2008/1/25, Sven Koch <haegar at sdinet.de>: > Package: nut > Version: 2.2.1-1 > Severity: normal > > I am using a Mustec PowerMust 1000 USB, connected with a USB cable to > the PC. > > With nut 2.2.0-2.1 everything works without problems - but since the > 2.2.1-1 update the "upsdrvctl start" from the init script just fails, > executing the

Hi, I'm trying to get a sweex ups working with nut on debian sarge. This one: http://www.sweex.com/producten.php?lang=1&%20sectie=&item=59&artikel=95 It's shipped with UPSmart and according to the compatibility list it should work with the genericups upstype=7 driver. But it doesn't. I get: mybox:/etc/nut# /etc/init.d/nut start Starting Network UPS Tools: (upsdrvctl

Hi, the following UPS isnt supported by the driver "usbhid-ups". Manufacturer: APC Model: Back-UPS 950 (https://www.apc.com/shop/de/de/products/APC-BACK-UPS-950VA-230V-AVR-Schuko- Sockets/P-BX950U-GR) Config: [USV] driver = usbhid-ups port = auto desc = "USV" . MODE=standalone Terminal: root at debian-jessie-final:~# sudo upsd -u root

Disclaimer: I've setup APC UPS monitoring and it works... ... but when it comes to mustek powermust 600usb (connected via com-port), I can't make it work. Got NUT installed via aptitude in ubuntu feisty and a basic setup, exactly the same as for the apc, except for the name of the ups and the corresponding section of ups.conf -- [mustek] driver = megatec port = /dev/ttyS1

Hi, I cant get it working. Here is my terminal output: root at debian-jessie-final:~# lsusb -d 051d:0002 Bus 001 Device 010: ID 051d:0002 American Power Conversion Uninterruptible Power Supply root at debian-jessie-final:~# ls -l /dev/bus/usb/001/010 crw-rw-r-- 1 root nut 189, 9 Mai 6 15:35 /dev/bus/usb/001/010 root at debian-jessie-final:~# sudo upsdrvctl start Network UPS Tools - UPS driver

Good morning, i have an Xanto S1000 USV the Manufactor is ONLINE USV-Systeme AG. I tried all the buildin drivers, also the driver for the driver for the Generic UPS, nothing worked for this UPS so now my question has anyone else this UPS and functional driver? Thanks and Greets Dennis

Well, having spent a decent amount of time trying to get my driver file added into the Makefile build system (and failing), I've decided that for now, simply adding that one line to the openups-hid.c file and recompiling is the best route to go. When I can no longer live with the limited nature of the openups-hid driver, I'll revisit writing our own. Thanks for the helps. Sincerely,

A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 188 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20071124/3ceb35d2/attachment.pgp

Hello ! first off, thank you all for making this piece of software. from what i have seen so far this seems to be a really mature and advanced tool for all sorts of UPS models ! I`d like to tell that I own a UPS which isn`t listed on the compatibility list, but seems to be compatible. It is a PowerWalker - see this at