-
-
Notifications
You must be signed in to change notification settings - Fork 346
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MInuteman UPS #555
Comments
Here (-> https://www.minutemanups.com/support/manuals/EnterprisePlus_UPS_Users_Manual_EN.pdf) they mention HID for USB communications -- I'd start from usbhid-ups. |
I gave that driver a try but it doesnt seems to be picking anything up, im going to unplug the other ups(cyberpower) and figure out the port the Minuteman one is using and double check |
Unfortunately, the usbhid-ups driver doesn't handle USB IDs that aren't in its database yet (it's been on the backlog for a while, though: #112) Can you post the log (as an attachment, please! it can be hard to read inline in the issue webpage) from the explore command under "Writing a subdriver" in the developer guide? The output from |
sorry im not able to find the drivers/usbhid-ups file but attached below is the output of thanks |
That path is if you are building from source. If it's a Debian/Ubuntu-derived distribution, the driver gets installed to |
Also, thanks for posting the lsusb output. |
usbhid-ups output.txt |
The standard HID PDC IDs look good, and the vendor-specific IDs look similar to Tripp-Lite. Next step is to rebuild the driver. Instructions for Ubuntu are here: https://github.com/networkupstools/nut/wiki/Building-NUT-on-Debian,-Raspbian-and-Ubuntu Once you can build and run the driver from source (the |
Looks like its working now do you want me to give you output or test anything specific. One note it seems that NUT reports the ups switching between battery and line power. line to battery after a minute then back to line after 5 seconds |
I added the USB VID:PID to a branch. You can get that code with At that point, you should be able to run the driver without the |
attached to this, you need usbhid-ups correct |
(Just stumbled across your update - note that Github doesn't notify via email for edits, so it's probably best to add a new comment if you add something like a new log file.) If you monitor the |
I took some more, the messaged still happens, it seems at some point the connection times out or something. would and increase in the poll_time or Max Dead time help? Sorry had to use pastebin, the file wouldn't take |
Polling less frequently might help, but the "busy" error is worrisome (that's why the driver reconnects). Details on the polling times here: http://new.networkupstools.org/docs/man/usbhid-ups.html#_usb_polling_and_interrupt_transfers The polling frequency doesn't explain why the UPS occasionally returns ACPresent as 0. Looks like flaky firmware. MAXDEAD and others are for when you get "data stale" messages from |
Potentially stupid question, but are there any other packages that might be polling the UPS at the same time? UPower might be, though it might also not know about this USB VID:PID combination. |
I dont believe so, tomorrow ill try a fresh install just in case, is there anything else i could check |
Sorry i haven't messaged in a bit, but i rebuilt NUT and have it working with the ups and am seeing the same issue but it seems a little less common. What would be the best approach for trying to figure this issue out? |
Hello, I also have a minuteman UPS. lsusb shows it as: Any updates on this issue? Will support be added to NUT upstream? Is best bet to run the minuteman branch? |
Currently i was able to acquire a minuteman Enterprise plus E1500RM2U UPS, if possible i was wonder if there is a plan to support this brand/model and if so how I can help
Thanks
The text was updated successfully, but these errors were encountered: