[Nut-upsuser] Unitek Alpha 650 ipE

Andrej Podzimek andrej at podzimek.org
Mon Jul 14 19:50:18 UTC 2008


> 
> I apologize, it should really be -DDDDD. :)
> 

Yes, that works. This is the verbose output:

	[root at charon ~]# megatec_usb -DDDDD -a unitek -u root
	Network UPS Tools 2.2.2 - Megatec protocol driver 1.5.14 [megatec_usb]
	Carlos Rodrigues (c) 2003-2008

	Serial-over-USB transport layer for Megatec protocol driver [megatec_usb]
	Andrey Lelikov (c) 2006, Alexander Gordeev (c) 2006-2007, Jon Gough (c) 2007

	debug level is '5'
	Checking device (0F03/0001) (001/007)
	- VendorID: 0f03
	- ProductID: 0001
	- Manufacturer: Ver 1.0
	- Product: USB To RS232 Interface (V1.0) BaudRate 2400bps
	- Serial Number: unknown
	- Bus: 001
	Trying to match device
	Device matches
	failed to claim USB device, trying 2 more time(s)...
	detaching kernel driver from USB device...
	trying again to claim USB device...
	get_data_agiler: raw dump: (0 bytes) =>
	Starting UPS detection process...
	Asking for UPS status [Q1]...
	get_data_agiler: raw dump: (0 bytes) =>
	get_data_agiler: raw dump: (0 bytes) =>
	Q1 => FAILED [short read]
	Q1 detail: (0 bytes) =>
	Asking for UPS status [Q1]...
	get_data_agiler: raw dump: (0 bytes) =>
	get_data_agiler: raw dump: (0 bytes) =>
	Q1 => FAILED [short read]
	Q1 detail: (0 bytes) =>
	Asking for UPS status [Q1]...
	get_data_agiler: raw dump: (0 bytes) =>
	get_data_agiler: raw dump: (0 bytes) =>
	Q1 => FAILED [short read]
	Q1 detail: (0 bytes) =>
	Asking for UPS status [Q1]...
	get_data_agiler: raw dump: (0 bytes) =>
	get_data_agiler: raw dump: (0 bytes) =>
	Q1 => FAILED [short read]
	Q1 detail: (0 bytes) =>
	Asking for UPS status [Q1]...
	get_data_agiler: raw dump: (0 bytes) =>
	get_data_agiler: raw dump: (0 bytes) =>
	Q1 => FAILED [short read]
	Q1 detail: (0 bytes) =>
	5 out of 5 detection attempts failed (minimum failures: 2).
	Megatec protocol UPS not detected.

What does that mean? Sounds like a broken UPS... :-(

Andrej



More information about the Nut-upsuser mailing list