Hi, I've tried the new richcomm_usb, but no success, i saw when updating my copy via svn that the lakeview driver also had updates. This one at first seemed to work. The output was this:
[EMAIL PROTECTED]:/usr/local/ups/etc# ../bin/lakeview_usb -a UPS -DDDDD -u root Network UPS Tools - Lakeview Research compatible USB UPS driver 0.02 (2.3.0-1609) Warning: This is an experimental driver. Some features may not function correctly. debug level is '5' usb_interrupt_read return code: 4 usb_interrupt_read return code: 4 usb_interrupt_read return code: 4 usb_interrupt_read return code: 4 usb_interrupt_read return code: 4 send_to_all: SETINFO driver.version.internal "0.02" send_to_all: SETINFO ups.mfr "Lakeview Research compatible" send_to_all: SETINFO ups.model "Unknown" usb_interrupt_read return code: 4 send_to_all: SETINFO ups.status "OL" send_to_all: DATAOK dstate_init: sock /var/state/ups/lakeview_usb-UPS open on fd 5 send_to_all: SETINFO driver.version "2.3.0-1609" send_to_all: SETINFO driver.name "lakeview_usb" send_to_all: SETINFO driver.parameter.pollinterval "2" usb_interrupt_read return code: 4 usb_interrupt_read return code: 4 usb_interrupt_read return code: 4 usb_interrupt_read return code: 4 So i've started the upscrtl & upsd and used upsc to view the status. But this status gives OL always, even when i pull the plug of the UPS it still shows OL. Any idea what could cause this error? If you need more info please ask. Regards, Tom -----Oorspronkelijk bericht----- Van: Arjen de Korte [mailto:[EMAIL PROTECTED] Verzonden: zondag 7 december 2008 16:26 Aan: Tom Cassimon CC: 'Charles Lepple'; 'nut-upsdev' Onderwerp: Re: [Nut-upsdev] Sweex 1000VA UPS (Lakeview Research) Citeren Tom Cassimon <[EMAIL PROTECTED]>: [...] > Checking device (0925/1234) (007/002) > - VendorID: 0925 > - ProductID: 1234 > - Manufacturer: ? > - Product: UPS USB MON V1.4 > - Serial Number: unknown > - Bus: 007 > Trying to match device > Device matches OK, at least the device matching seems to work. > send: (4 bytes) => 01 00 00 30 > read: Resource temporarily unavailable > do_command: Resource temporarily unavailable And from here, that's it. No response at all. Maybe this is because the driver expects the query to be sent as a HID_REPORT_TYPE_INPUT instead of the HID_REPORT_TYPE_FEATURE that usb->set_report uses. Could you try again with the latest version (r1604) from the trunk? If that fails, we also have 'lakeview_usb', which might be worth trying out. [...] > I use the -u root option because the udev system doesn't seem to change the > permissions of the device. I know, this udev rules will be generated automatically in the future (and the driver is already setup to support that), but this isn't activate yet. For now I have modified this too. Best regards, Arjen -- Please keep list traffic on the list _______________________________________________ Nut-upsdev mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
