similar to: man page for megatec_usb

--- Arjen de Korte <nut+users at de-korte.org> wrote: > > > I also did: > > > > # ./megatec_usb -DDDDD -x vendor=06da -x mfr=OMRON > > /dev/usb/hiddev0 > > Please have a look at 'man 8 megatec_usb' again. > > You probably need to specify the '-x vendorid' and > '-x productid' options > and most likely, the

--- Arjen de Korte <nut+users at de-korte.org> wrote: > > > I also did: > > > > # ./megatec_usb -DDDDD -x vendor=06da -x mfr=OMRON > > /dev/usb/hiddev0 > > Please have a look at 'man 8 megatec_usb' again. > > You probably need to specify the '-x vendorid' and > '-x productid' options > and most likely, the

Hello, all. Some time ago I bought myself a UPS which was advertised as USB-HID. It was a surprise to learn that while it definitely is recognized as USB device, the HID descriptor has no UPS pages at all. The only software it came with was a windows program written in visual basic. Trying to research this topic I found a reference to energizer USB ups driver and learned about variety of

> Author: agordeev-guest > Date: Wed Oct 3 00:09:21 2007 > New Revision: 1136 > > Log: > - drivers/megatec_usb.c: added ability to do subdriver-specific > initialization, and moved some shared code to agiler init function > since krauler doesn't need it. [...] I'm not very thrilled about this patch: 1) Down at the subdriver level, one shouldn't use

Hi Alexey, Please post the output of 'lsusb' and 'megatec_usb -a sven_625 -u nut -DDDDD'. On Monday 15 June 2009 14:32:16 you wrote: > Package: nut > Version: 2.4.1-3 > Severity: normal > > I have a SVEN Pro+ 625 ups that uses megatec_usb driver. > In ups.conf I describe it like: > [sven_625] > driver = megatec_usb > port = auto > desc =

Trying to use it with Sven Smart RM2000 (seems to be an OEM clone of Sysgration Smart RM UPS: http://www.sysgration.com/product.asp?KID=7). I have just compiled the latest svn trunk. Unfortunately it does not work with that UPS: dbely at vserver1:~/nut-svn$ sudo /usr/local/ups/bin/megatec_usb -u root -a myups Network UPS Tools 2.1.0 - Megatec protocol driver 1.5.3 [megatec_usb] Carlos Rodrigues

Gidday all - I've got a 1700VA dynamix UPS which is USB. The previous model (with a serial port) worked wonderfully with megatec, but this new one with USB is not working. It feels like the kernel is not handing the USB device properly. The web has not yeilded any useful info. What can I do from here? =========================================== [root at hera ups]# lsusb Bus 006 Device 002:

Hi, I'm new in the list and I'm having a little bit trouble to put the megatec_usb to work. I've been using NUT for a while with the apc and megatec driver (serial), with no problem. The server is a Ubuntu 8.04.2 with NUT version 2.2.1-2.1ubuntu7.2, the default package version in this ubuntu release. I've configured the ups.conf as follows: [sms] driver = megatec_usb

Hi, I'm new in the list and I'm having a little bit trouble to put the megatec_usb to work. I've been using NUT for a while with the apc and megatec driver (serial), with no problem. The server is a Ubuntu 8.04.2 with NUT version 2.2.1-2.1ubuntu7.2, the default package version in this ubuntu release. I've configured the ups.conf as follows: [sms] driver = megatec_usb

Hello again! Thanks to the precious help from Henning Brauer, I managed to solve an issue with my UPS (a rebranded UPS speaking in Ablerex-ese over USB). Under OpenBSD 4.3, the UPS was claimed by HID. Now that I recompiled the kernel, adding a USB_quirk, this is what I get when I insert the USB cable: ugen0 at uhub0 port 2 "UIS_ABLER USB to Serial" rev 1.00/1.00 addr 2 So far, so

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,

Hey all, thanks for your work on nut. I recently got myself a new cheap UPS, and have thus far determined very little about it. I can run whatever you like to help identify and work with it. So far I've played around with various settings and have had some limited success with the megatec_usb driver (Debian testing version): ----ups.conf---- [plexus] driver=megatec_usb model=500VA mfr=Plexus

Hi, Just purchashed this UPS. The megatec_usb driver appears to be communicating with the UPS - however, the ups.status field always states "off" /usr/local/ups/bin/megatec_usb -a plexus -DD Network UPS Tools 2.2.1 - Megatec protocol driver 1.5.9 [megatec_usb] Carlos Rodrigues (c) 2003-2007 Serial-over-USB transport layer for Megatec protocol driver [megatec_usb] Andrey Lelikov (c)

Hi, Just purchashed this UPS. The megatec_usb driver appears to be communicating with the UPS - however, the ups.status field always states "off" /usr/local/ups/bin/megatec_usb -a plexus -DD Network UPS Tools 2.2.1 - Megatec protocol driver 1.5.9 [megatec_usb] Carlos Rodrigues (c) 2003-2007 Serial-over-USB transport layer for Megatec protocol driver [megatec_usb] Andrey Lelikov (c)

Hi, I'm having a hard time configuring a Mustek Powermust 600VA ups to work via USB with nut. I read somewhere that nut works OK via the rs232 cable, but unfortunately I don't have a COM port in my computer. The kernel detects the ups as an Xbox pad :) and loads the xpad module. I tried running /lib/nut/megatec with different /dev/ttySx but it displays megatec protocol UPS was not

Hi Bj?rn, 2009/10/9 Bj?rn Torkelsson > Public bug reported: > > Binary package hint: nut > > I have recently upgraded from hardy to intrepid to jaunty. After > upgrading to Intrepid the megatec_usb stopped recognizing my Trust PW- > 4130M ups, it still does not work on Jaunty. It worked without any > problems in hardy. > > I tried the megatec_usb driver from hardy

Hi, Sorry for the forwarding. I sent this with the wrong "from" address and got rejected by the list. ---------- Forwarded message ---------- From: Carlos Rodrigues <cefrodrigues at mail.telepac.pt> Date: Jun 18, 2007 9:34 PM Subject: Re: Megatec - modem control lines [impact to megatec_usb] To: Arjen de Korte <nut+devel at de-korte.org> Cc: ups-dev-list <nut-upsdev at

I'm trying to see if we can make upsd autodetect the driver sockets from the STATEPATH. This works quite well and uses surprisingly little code (much less than parsing the 'ups.conf' file). However, since I can no longer read the name from the 'ups.conf' file, I need to extract this from the name of the socket. We might simply strip the drivername from the socket name again,

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 Alexander, thanks for your good work on the megatec_usb driver. I have made a few more (cosmetic) changes. Is the driver now working stably for your device? In particular, do the instant commands (and particularly "upsdrvctl -k") work properly? In this case, we could hopefully mark the device as "supported" and merge the driver to the main branch. There is still the