Re: [Nut-upsuser] Sven Power Pro 1000+
upsc and upscmd work fine. upsrw returns nothing, but I believe this is the expected behaviour - previous versions didn't suggest any RW vars for my UPS either. Shutdown sequence also works. The system didn't turn back on automatically, but that might be due to BIOS settings, or maybe I just didn't wait long enough. Best regards, Vlad - Original Message - From: Arnaud Quette aquette@gmail.com To: Vlad n...@wolf.umail.net Cc: nut-upsuser@lists.alioth.debian.org nut-upsuser@lists.alioth.debian.org Sent: 07.07.2011 13:21:03 Subject: Re: [Nut-upsuser] Sven Power Pro 1000+ Hi 2011/7/6 Vlad n...@wolf.umail.net Hi. Dev version seems to work fine. excellent. can you please also check the data returned by upsc, upsrw and upscmd. along with testing a shutdown sequence: http://www.networkupstools.org/docs/user-manual.chunked/ar01s06.html#Testing_shutdowns once I get your feedback, I'll add the following entry in the hardware compatibility list: SVEN ups 2 Power Pro+ series USB blazer_usb (USB ID :) cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Sven Power Pro 1000+
Hi 2011/7/6 Vlad n...@wolf.umail.net Hi. Dev version seems to work fine. excellent. can you please also check the data returned by upsc, upsrw and upscmd. along with testing a shutdown sequence: http://www.networkupstools.org/docs/user-manual.chunked/ar01s06.html#Testing_shutdowns once I get your feedback, I'll add the following entry in the hardware compatibility list: SVENups2Power Pro+ seriesUSBblazer_usb (USB ID :) cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Sven Power Pro 1000+
Hi. Dev version seems to work fine. $ sudo ./blazer_usb -DDD -u root -a sven_blazer Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.6.1-3126) 0.00 debug level is '3' 0.260154 Checking device (/) (009/002) 0.304526 - VendorID: 0.304540 - ProductID: 0.304544 - Manufacturer: 0.304547 - Product: 010937 0.304551 - Serial Number: 0.304553 - Bus: 009 0.304556 Trying to match device 0.304564 Device matches 0.310532 Trying megatec protocol... 0.310542 send: Q1 0.559511 read: (235.6 140.0 202.0 013 50.0 27.5 30.0 00101000 0.559569 Status read in 1 tries 0.559573 Supported UPS detected with megatec protocol 0.559577 send: F 0.691518 read: #220.0 000 024.0 50.0 0.691533 blazer_rating: short reply 0.691537 Rating read 1 failed 0.691541 send: F 0.823518 read: #220.0 000 024.0 50.0 0.823533 blazer_rating: short reply 0.823537 Rating read 2 failed 0.823542 send: F 0.955517 read: #220.0 000 024.0 50.0 0.955532 blazer_rating: short reply 0.955536 Rating read 3 failed 0.955540 Rating information unavailable 0.955544 send: I 1.162504 read: # VT12094S 1.162530 blazer_vendor: short reply 1.162540 Vendor information read 1 failed 1.162549 send: I 1.370511 read: # VT12094S 1.370526 blazer_vendor: short reply 1.370530 Vendor information read 2 failed 1.370534 send: I 1.578531 read: # VT12094S 1.578547 blazer_vendor: short reply 1.578551 Vendor information read 3 failed 1.578554 Vendor information unavailable 1.578558 Battery runtime will not be calculated (runtimecal not set) 1.578573 send: Q1 2.071496 read: (235.6 140.0 202.0 013 50.0 27.5 30.0 00101000 2.082049 dstate_init: sock /var/state/ups/blazer_usb-sven_blazer open on fd 5 2.082067 send: Q1 2.329488 read: (235.6 140.0 202.0 013 50.0 27.5 30.0 00101000 4.083874 send: Q1 4.331460 read: (235.6 140.0 202.0 013 50.0 27.5 30.0 00101000 6.084631 send: Q1 Here is the output from 2.4.3. $ sudo /lib/nut/blazer_usb -DDD -u root -a sven_blazer Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.4.3) 0.00 debug level is '3' 0.251628 Checking device (/) (009/002) 0.296171 - VendorID: 0.296185 - ProductID: 0.296189 - Manufacturer: 0.296192 - Product: 010937 0.296195 - Serial Number: 0.296198 - Bus: 009 0.296201 Trying to match device 0.296205 Device matches 0.296223 failed to claim USB device: could not claim interface 0: Device or resource busy 0.296236 detached kernel driver from USB device... 0.302181 Trying megatec protocol... 0.302192 send: Q1 0.550161 blazer_status: short reply 0.550177 Status read 1 failed 0.550181 send: Q1 0.798163 blazer_status: short reply 0.798180 Status read 2 failed 0.798185 send: Q1 1.047158 blazer_status: short reply 1.047173 Status read 3 failed 1.047177 Trying mustek protocol... 1.047181 send: QS 1.047185 read: QS 1.047188 blazer_status: short reply 1.047191 Status read 1 failed 1.047194 send: QS 1.047196 read: QS 1.047199 blazer_status: short reply 1.047202 Status read 2 failed 1.047204 send: QS 1.047207 read: QS 1.047210 blazer_status: short reply 1.047213 Status read 3 failed 1.047215 Trying megatec/old protocol... 1.047218 send: D 1.047221 read: D 1.047224 blazer_status: short reply 1.047226 Status read 1 failed 1.047229 send: D 1.047232 read: D 1.047234 blazer_status: short reply 1.047237 Status read 2 failed 1.047240 send: D 1.047242 read: D 1.047245 blazer_status: short reply 1.047248 Status read 3 failed 1.047251 No supported UPS detected Best regards, Vlad - Original Message - From: Arjen de Korte nut+us...@de-korte.org To: nut-upsuser@lists.alioth.debian.org Sent: 01.07.2011 00:17:01 Subject: Re: [Nut-upsuser] Sven Power Pro 1000+ Citeren Vlad n...@wolf.umail.net: I'll try to install dev version and see whether it works. What kind of diagnostic info would you need? USB ID of my device is :. Could you also try the blazer_usb driver from nut-2.4.3 (the same version as the megatec_usb driver that worked for you)? /path/to/blazer_usb -DDD -u root -a upsname Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected
[Nut-upsuser] Sven Power Pro 1000+
Hi, Arjen. Sorry for the late reply and lack of quoting - I occasionally messed up my subscription settings and didn't get your message. I'll try to install dev version and see whether it works. What kind of diagnostic info would you need? USB ID of my device is :. -- Vlad ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Sven Power Pro 1000+
Citeren Vlad n...@wolf.umail.net: I'll try to install dev version and see whether it works. What kind of diagnostic info would you need? USB ID of my device is :. Could you also try the blazer_usb driver from nut-2.4.3 (the same version as the megatec_usb driver that worked for you)? /path/to/blazer_usb -DDD -u root -a upsname Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Sven Power Pro 1000+
Citeren Martin Ewing martin.s.ew...@gmail.com: This seems very similar to the trouble I have with a Belkin UPS (USB) with Natty (64 bit). Not at all. You seem to be suffering from a permissions problem, where Vlad is not (most likely, there is a problem in the protocol handling). These are totally unrelated issues. Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Sven Power Pro 1000+
Citeren Vlad n...@wolf.umail.net: I downgraded back to 2.4.3, configured nut to use megatec_usb again, and it started working again. However, it seems strange that I cannot use the latest version. This is not strange at all. We have reworked this driver core and could not find people with access to these device and willing to test this. Note that blazer_usb has been in the stable version since 2.4.0 was released and have urged people to switch over to this one. We have had no reports that the subdriver that is used by this series of UPS devices was broken. In that case, there is nothing more we can do than to switch to the new driver and see what happens. We've had some changes after 2.6.0 was released in this driver, so you could try if upgrading to that helps. There are some more changes underway, but due to the lack of help we're getting from the userbase, this is put on the back burner (without people volunteering to test changes, there is no point in putting effort in it). You could help us here by running the development version for this driver and report back your results, since we will need testing from as many different flavors of the krauler series of devices as possible (USB ID's 0001: and :). Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
[Nut-upsuser] Sven Power Pro 1000+
Hello. I recently upgraded from Ubuntu Maverick to Natty and hence upgraded nut from 2.4.3-1ubuntu5 to 2.6.0-1ubuntu3. My Sven PowerPro+ 1000 UPS ( http://en.sven.ru/catalog/ups/power_pro_plus_1000.htm ) worked fine with the previous version, using megatec_usb driver, but doesn't work with the current version, since megatec_usb is no longer available. Here is the output from blazer_usb. sudo /lib/nut/blazer_usb -a sven1 -DDD Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.4.3) 0.00 debug level is '3' 0.251050 Checking device (/) (009/002) 0.295442 - VendorID: 0.295451 - ProductID: 0.295456 - Manufacturer: 0.295460 - Product: 010937 0.295464 - Serial Number: 0.295468 - Bus: 009 0.295472 Trying to match device 0.295477 Device matches 0.295493 failed to claim USB device: could not claim interface 0: Device or resource busy 0.295505 detached kernel driver from USB device... 0.301458 Trying megatec protocol... 0.301466 send: Q1 0.549441 blazer_status: short reply 0.549453 Status read 1 failed 0.549458 send: Q1 1.042431 blazer_status: short reply 1.042444 Status read 2 failed 1.042449 send: Q1 1.291425 blazer_status: short reply 1.291435 Status read 3 failed 1.291440 Trying mustek protocol... 1.291445 send: QS 1.291449 read: QS 1.291453 blazer_status: short reply 1.291457 Status read 1 failed 1.291460 send: QS 1.291464 read: QS 1.291467 blazer_status: short reply 1.291470 Status read 2 failed 1.291473 send: QS 1.291476 read: QS 1.291479 blazer_status: short reply 1.291482 Status read 3 failed 1.291486 Trying megatec/old protocol... 1.291489 send: D 1.291492 read: D 1.291495 blazer_status: short reply 1.291498 Status read 1 failed 1.291502 send: D 1.291505 read: D 1.291508 blazer_status: short reply 1.291511 Status read 2 failed 1.291514 send: D 1.291517 read: D 1.291520 blazer_status: short reply 1.291524 Status read 3 failed 1.291527 No supported UPS detected I downgraded back to 2.4.3, configured nut to use megatec_usb again, and it started working again. However, it seems strange that I cannot use the latest version. -- Vlad ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Sven Power Pro 1000+
On Sat, Jun 25, 2011 at 8:13 PM, Vlad n...@wolf.umail.net wrote: Hello. I recently upgraded from Ubuntu Maverick to Natty and hence upgraded nut from 2.4.3-1ubuntu5 to 2.6.0-1ubuntu3. My Sven PowerPro+ 1000 UPS ( http://en.sven.ru/catalog/ups/power_pro_plus_1000.htm) worked fine with the previous version, using megatec_usb driver, but doesn't work with the current version, since megatec_usb is no longer available. Here is the output from blazer_usb. sudo /lib/nut/blazer_usb -a sven1 -DDD Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.4.3) 0.00debug level is '3' 0.251050Checking device (/) (009/002) 0.295442- VendorID: 0.295451- ProductID: 0.295456- Manufacturer: 0.295460- Product: 010937 0.295464- Serial Number: 0.295468- Bus: 009 0.295472Trying to match device 0.295477Device matches 0.295493failed to claim USB device: could not claim interface 0: Device or resource busy 0.295505detached kernel driver from USB device... 0.301458Trying megatec protocol... 0.301466send: Q1 0.549441blazer_status: short reply 0.549453Status read 1 failed 0.549458send: Q1 1.042431blazer_status: short reply 1.042444Status read 2 failed 1.042449send: Q1 1.291425blazer_status: short reply 1.291435Status read 3 failed 1.291440Trying mustek protocol... 1.291445send: QS 1.291449read: QS 1.291453blazer_status: short reply 1.291457Status read 1 failed 1.291460send: QS 1.291464read: QS 1.291467blazer_status: short reply 1.291470Status read 2 failed 1.291473send: QS 1.291476read: QS 1.291479blazer_status: short reply 1.291482Status read 3 failed 1.291486Trying megatec/old protocol... 1.291489send: D 1.291492read: D 1.291495blazer_status: short reply 1.291498Status read 1 failed 1.291502send: D 1.291505read: D 1.291508blazer_status: short reply 1.291511Status read 2 failed 1.291514send: D 1.291517read: D 1.291520blazer_status: short reply 1.291524Status read 3 failed 1.291527No supported UPS detected I downgraded back to 2.4.3, configured nut to use megatec_usb again, and it started working again. However, it seems strange that I cannot use the latest version. -- Vlad ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser Vlad, This seems very similar to the trouble I have with a Belkin UPS (USB) with Natty (64 bit). Martin -- Martin Ewing Branford, Connecticut martin.s.ew...@gmail.com ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
