-
-
Notifications
You must be signed in to change notification settings - Fork 362
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
not working: ExeGate Power RM UNL-1500 LCD - Lakeview Research UPS USB Mon V2.0 #2764
Comments
I suppose you are following up from tests reported in issue #2125? One idea to try: do not constrain In that other issue, a |
Yep, I followed tests from that issue. Q1 protocol
sbin/upsdrvctl start
bin/upsc exegate@localhost
With no protocol selected
sbin/upsdrvctl start
sbin/upsdrvctl stop nut-server logs:
|
Curious about that exit due to Signal 2. Do you have a |
I think signal 2 is Ctrl+c. The output of bin/nutdrv_qx -a exegate -DDDDDDD is looping and I press Ctrl+c to exit. I do not have |
Aha, Ctrl+C would be it. A sibling driver kill-off could also send that signal I think.
Literally that file name, in a "statepath" expected by that build of |
Just in case, is your |
… fail to connect [networkupstools#2764] Signed-off-by: Jim Klimov <[email protected]>
…pipe) the driver now listens on [networkupstools#2764] Signed-off-by: Jim Klimov <[email protected]>
…T_INIT_LISTENER envvar [networkupstools#2764] Signed-off-by: Jim Klimov <[email protected]>
…when we fail to connect [networkupstools#2764] Signed-off-by: Jim Klimov <[email protected]>
…ssible variants [networkupstools#2764] Signed-off-by: Jim Klimov <[email protected]>
…ks [networkupstools#2764] Signed-off-by: Jim Klimov <[email protected]>
…UNIX_PATH_MAX etc. [networkupstools#2764] Signed-off-by: Jim Klimov <[email protected]>
networkupstools#2764] Signed-off-by: Jim Klimov <[email protected]>
I'm trying to run this ExeGate Power RM UNL-1500 LCD, I compiled the latest version but it doesn't work, it seems the Lakeview Research UPS USB Mon V2.0 is not supported.
With UPS I have received a disk with richcomm powermanager.
build proccess:
lsusb -v -d0925:1234
/usr/local/ups/bin/nutdrv_qx -s exegate -u root -DDDDDD -x productid=1234 -x vendorid=0925 -x subdriver=armac -x port=auto
/bin/richcomm_usb -a exegate -DDDDD -u root
../bin/nutdrv_qx -a exegate -DDDDD -x protocol=megatec -x subdriver=armac
The text was updated successfully, but these errors were encountered: