Bus 001 Device 004: ID 0001:0000 Fry's Electronics #1947
Comments
|
Additional info: |
jimklimov
added
USB VID=0001 PID=0000 (Fry's Electronics/MEC0003)
|
In the configuration, you would benefit from setting additionally ...which are checked first generally. Matching by Looking how it returns "unknown" for the basic fields, it seems that the NUT driver's run-time account (and libusb as part of the driver) can not access the device. Possibly kernel has grabbed it and won't give back, try finding and updating the While you experiment, you can also try running Also make sure another copy of a NUT driver (e.g. via init-scripts or systemd units) is not already holding the device. There can be only one... exclusive owner at a time :) |
|
thanks. I am using raspbian (buster) and apt only provides this version. and how can I update udev.rules ? |
|
root@raspbx: |
|
I just tested with the included Windows software (UPSmart) How can I get 2.8.0 ? |
just compiled from source now. (didn't install, running from the source folder) I also copied nut-usbups.rules to /etc/udev/rules.d/62-nut-usbups.rules as described in: srefreshed the bus : but none of these changed the result. |
|
installed 2.8.0 and run "nut_scanner" says: output is: still no luck. |
|
it worked with this config: now the driver output is like : AND , upsd can be run, upsc can read from it: But, since I compiled from source, I don't know how to setup. What components should be run for the server to start at system boot ? |
|
I'm a bit surprised how it can't find the product name and other USB metadata, but sees reasonable info from it. Every day for us, something new... Congratulations on getting it usable! Regarding installation, https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests suggests a reasonable approach to getting systemd units enabled. You may want to re-configure and rebuild first, at least to use better user accounts than root or nobody by default. |
jimklimov
added
HCL
DDL
Powercool
|
systemd is installed and works fine now. thanks for all the help. |
|
btw, the UPS brand is Makelsan. It is a local company in Turkey. |
|
Ok, so I misunderstood your earlier post? It is not a Powercool, just compatible? Or same OEM model, different sales brand? |
|
FWIW, to mark it better in HCL/DDL - can you please post what is the sold product fully called? :) |
|
It is not PowerCool. I copied powercool config from another post. |
|
with this driver it generally works but there is no battery.runtime in the output. |
|
Many devices indeed do not offer that information (popularly also load or charge level are often missing), so that may well be just absent completely. If vendor software does provide that, it might be interesting to somehow sniff and debug and find out how it does query (or estimate) that. Some NUT drivers calculate that information artificially, if some other data are available, and |
|
I have an interesting issue. The difference is the "Generic Q* Serial driver 0.32" what is this , and how can I make it 0.45 ? |
|
Actually the The Looking at https://github.com/networkupstools/nut/blob/master/drivers/nutdrv_qx.c#LL2681C1-L2682C72 I guess your other system did not include a Check with |
|
I'm away from home now so I will check the prereqs later. I want to make sure I understand correct. You mean, 0.32 is the correct version but my first PI missed something and compiled/used another variant of the driver. As a result , it reports 0.45 version which worked for me. now I am confused. |
|
No, not quite so. It has the When libusb (library and development files like headers and pkgconf manifest) is present on the build system, that layer is compiled into the main driver and opens up both USB ability (mixing third-party API and our common framework for resource descriptor queries and decoding), and the device-specific In your earlier post, it used a |
|
weird. Both systems have same version of libusb. root@octopi:~/nut-master# apt list --installed | grep libusb WARNING: apt does not have a stable CLI interface. Use with caution in scripts. libusb-0.1-4/oldstable,now 2:0.1.12-32 armhf [installed,automatic] root@raspbx:~# apt list --installed | grep libusb WARNING: apt does not have a stable CLI interface. Use with caution in scripts. libusb-0.1-4/oldstable,now 2:0.1.12-32 armhf [installed] The difference is libusd-dev package. |
|
OK. installed libusb-dev and now it works. detects the UPS and gets info. However, I have another issue when installing the service. also "/usr/local/ups/bin/nutdrv_qx -DD -a Makelsan" says "Access denied (insufficient permissions)" |
I would expect autogen is offtopic here, it typically makes a As for perms - did you |
|
:( |
|
I can also confirm a Makelsan Lion 850VA working with this configuration. The manufacturer's listing of the product line is here, for future inclusion in the compatibility list: https://www.makelsan.com.tr/en/makelsan-ups-kgk-urundetay.php?urunID=500 |
|
I also got a Makelsan 650VA. It did not work with this configuration. I had to change the config a little. |
|
Got a Lion 2200VA recently. I've to setup a UPS server to manage shut down the NAS properly in case of power outage. I hope your adventure will help me. Thanks for the detailed comments. |
|
Hey there! I managed to configure my Makelsan Lion 2200VA USB UPS with this configuration I found here I changed subdriver from hunnox to snr to try to find anything will be changed, but the change is not affected to anything. Readings looks like normal: But, So, with this case, do I need to change anything to work things better? |
|
@RecNes : congratulations, I guess. How did you run the NUT driver for the first screenshots (with working graphs) and later (with access errors)? I feel the former was as a service (so as the user account who may access the USB device node, per udev/upower/... config), and the latter you tried as "yourself" and could not see the USB port. And/or some other program/driver-instance/kernel/hypervisor/... held the port at that time. Does this guess fit? |
|
@RecNes :
How did you specify those values? |
After identifying the correct driver and defining users, I just make services to be restarted, Then I completed the necessary configurations by gathered from various sites, installing nginx, ensuring the system for CGI is secured, etc. Here is full configuration and action steps:
When it's all ready I just restarted the services:
That's how I get the screenshot I posted in previous message. While I'm seeing the UPS data on browser the BTW settings are not working: |
I didn't. I found the whole driver configuration from another topic in here and just used. Link is in my previous message. |
|
Check the definition in man page about the two couples of numbers and what they mean ;) |
If you are pointing my reply, I'm trying to say, that line might have no function for "my configuration". Not the other way. I think, if I remove that line, the system will still work though. Also you're right, I have to check the man page. |
I will. Thank you |
|
My model is R-Smart 1510 from CDP. I have run sucesfully with Megatec and Lagfix but lately it fails to run on boot and session login. Manajro KDE. And below is my config. I have tried all sub drivers on man 8 blazer_usb: phoenix, ippon, cypress, and krauler. I am going to see if nut-scanner reports different bus upon reboot and see if that is the problem. I took out bus, device and busport and the driver worked so I will see if it works on next reboot without those. Errors: nut-scanner: With that conf: This is how it worked but I will see on next boot and report back: UPDATE AFTER RESTART: |
|
@binarydepth : bus/device/port are enumeration-based so on some systems tend to change over time (device replugs, bus resets...) and may cause more problems than they solve :\ They are not suggested by default with I am a bit more concerned about "libusb1: Could not open any HID devices: insufficient permissions on everything" -- this means that either:
|
|
I tried this solution from Artcle and no go still. I took out the bus entries and still works with command after login. Can read read on NDE but in that instance is there a know solution you can provide? WORKAROUND I do lsusb and if the Fry's Electronics is not there which usually does I unplug and re-plug the USB cable and do sudo upsdrvctl start |
|
I have CROWN CMU-SP800 EURO LCD USB I think I was able to get it to work, but I'm confused by the voltage information. Here are my configs and logs: ups.conf/etc/udev/rules.d/50-ups.rulesupsdrvctl startupscPower on: Power off: Is it possible to fix this? |
|
Thanks for the report! Can you please elaborate about the voltage - what exactly looks wrong to you? For PbAc (typical) batteries with 12V nominal, the reported numbers look OK. Input/output voltage is a bit low for areas with 220V nominal - it seems your utility network gives too little (house overloaded the nearest transformer, etc.) but it is deemed sufficiently high by the device and its settings (if it has any for boosting) that it is not trying to use the battery or inverter to boost the low voltage into closer to nominal - UPS thinks it is already in acceptable range. As for adding to the site, it is a bit of a sore point regarding a long backlog of low-priority issues to update HCL (in main NUT repo, |
In log: So what do you mean that all functionality works correctly? But how can I turn off the beep? I also don’t quite understand how I can configure the server to shut down when the charge level drops below 50%. And how to turn off the UPS.
Well, I'll leave it to you. If you need any other logs or tests, I can provide them. |
|
PbAc nominal 12V is because it indeed can show 13.5-14V when fully charged, then quickly loses it down to ~12V, and stays close to 12V (slowly decreasing) as it discharges; then a near-dead battery quickly drops to 10-something V. I did have some Powercom UPS 20 years ago which displayed completely different data when on-line or on-battery. So it may also be that different chips or different calibrations are responsible for different power cases, too. |
Hi,
I have a noname UPS which shows up like below on lsusb command:
"Bus 001 Device 004: ID 0001:0000 Fry's Electronics"
From what I read on different discussions, it might work with "nutdrv_qx" driver.
But I am not sure how I should configure this.
What I have now in config:
and the driver command shows :
I also tried with this config:
This time , the output is shorter:
I am new to NUTS so I don't know how to configure and/or troubleshoot.
I'd appreciate any help.
The text was updated successfully, but these errors were encountered: