Skip to content
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

Open
wkleinhenz opened this issue May 22, 2018 · 18 comments
Open

MInuteman UPS #555

wkleinhenz opened this issue May 22, 2018 · 18 comments
Labels

Comments

@wkleinhenz
Copy link

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

@zykh
Copy link
Contributor

zykh commented May 22, 2018

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.

@wkleinhenz
Copy link
Author

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

@clepple
Copy link
Member

clepple commented May 23, 2018

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 lsusb -vvv trimmed to the Minuteman UPS would also be useful for reference. Thanks!

@wkleinhenz
Copy link
Author

sorry im not able to find the drivers/usbhid-ups file but attached below is the output of lsusb -vvv ill keep looking for the other bit

thanks

minuteman ups lsusb output.txt

@clepple
Copy link
Member

clepple commented May 23, 2018

That path is if you are building from source. If it's a Debian/Ubuntu-derived distribution, the driver gets installed to /lib/nut/usbhid-ups. If not, let us know which distribution (I don't know the other common paths off the top of my head).

@clepple
Copy link
Member

clepple commented May 23, 2018

Also, thanks for posting the lsusb output. wDescriptorLength 1028 is a good indication that usbhid-ups can be adapted to work with this UPS.

@wkleinhenz
Copy link
Author

usbhid-ups output.txt
got it

@clepple
Copy link
Member

clepple commented May 24, 2018

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 -x explore thing is a good test), then we can add the USB vendor/product IDs into the tripplite-hid.c file, and see how well that matches.

@wkleinhenz
Copy link
Author

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

@clepple
Copy link
Member

clepple commented May 25, 2018

I added the USB VID:PID to a branch. You can get that code with git fetch and then git checkout minuteman-HID, then rebuild.

At that point, you should be able to run the driver without the -x explore option. Logs (with -DD) would help with figuring out the line/battery problem (although if it stays stuck at around 80% battery, there may be an issue with the charging circuitry)

@wkleinhenz
Copy link
Author

wkleinhenz commented May 25, 2018

attached to this, you need usbhid-ups correct
usbhid-ups output.txt

@clepple
Copy link
Member

clepple commented May 29, 2018

(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 upsc output, is it still switching between battery and line (ups.status going between OL and OB), or is that no longer the case? The log you just posted shows UPS.PowerSummary.PresentStatus.ACPresent as 1, so if it is switching, we might need a higher debug level to see which other variable is affecting it.

@wkleinhenz
Copy link
Author

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
https://pastebin.com/C4TDBts4

@clepple
Copy link
Member

clepple commented May 30, 2018

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 upsc and upsmon.

@clepple
Copy link
Member

clepple commented May 30, 2018

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.

@wkleinhenz
Copy link
Author

I dont believe so, tomorrow ill try a fresh install just in case, is there anything else i could check

@wkleinhenz
Copy link
Author

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?

@ghost
Copy link

ghost commented Mar 28, 2020

Hello,

I also have a minuteman UPS.

lsusb shows it as:
Bus 001 Device 005: ID 05dd:a011 Delta Electronics, Inc.

Any updates on this issue? Will support be added to NUT upstream? Is best bet to run the minuteman branch?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants