search

networkupstools / nut

The Network UPS Tools repository. UPS management protocol Informational RFC 9271 published by IETF at https://www.rfc-editor.org/info/rfc9271 Please star NUT on GitHub, this helps with sponsorships!
https://networkupstools.org/
Other
1.99k stars 349 forks source link

East UPS EA600RT 1000VA #1670

Open trecords opened 2 years ago

trecords commented 2 years ago

Dear All,

I have issue to find out proper driver and communicate with UPS in my debian server. Included CD contains UPSmart for this device which is works on Windows. Please suggest how can I debug and make it work. I have added 2 different drivers into ups.conf for to test each of them.

Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 0001:0000 Fry's Electronics ATCL FOR UPS    <<<<<
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[UPS]
        driver = nutdrv_atcl_usb
        port = auto

[UPS1]
        driver = nutdrv_qx
        subdriver = fabula
        productid = 0000
        vendorid = 0001
        port = auto

MODE=standalone

Network UPS Tools - UPS driver controller 2.7.4
   0.000000
If you're not a NUT core developer, chances are that you're told to enable debugging
to see why a driver isn't working for you. We're sorry for the confusion, but this is
the 'upsdrvctl' wrapper, not the driver you're interested in.

Below you'll find one or more lines starting with 'exec:' followed by an absolute
path to the driver binary and some command line option. This is what the driver
starts and you need to copy and paste that line and append the debug flags to that
line (less the 'exec:' prefix).

   0.000084     Starting UPS: UPS
   0.000094     3 remaining attempts
   0.000098     exec:  /lib/nut/nutdrv_atcl_usb -a UPS
Network UPS Tools - 'ATCL FOR UPS' USB driver 1.1 (2.7.4)
Warning: This is an experimental driver.
Some features may not function correctly.

Duplicate driver instance detected! Terminating other driver!
Communications with UPS lost: Query to UPS failed
  10.265024     Starting UPS: UPS1
  10.265056     3 remaining attempts
  10.265063     exec:  /lib/nut/nutdrv_qx -a UPS1
Network UPS Tools - Generic Q* USB/Serial driver 0.28 (2.7.4)
USB communication driver 0.33
Device not supported!
Device not supported!
  11.180574     Driver failed to start (exit status=1)
  16.180677     2 remaining attempts
  16.180719     exec:  /lib/nut/nutdrv_qx -a UPS1
Network UPS Tools - Generic Q* USB/Serial driver 0.28 (2.7.4)
USB communication driver 0.33
Device not supported!
Device not supported!
  16.716321     Driver failed to start (exit status=1)
  21.716422     1 remaining attempts
  21.716458     exec:  /lib/nut/nutdrv_qx -a UPS1
Network UPS Tools - Generic Q* USB/Serial driver 0.28 (2.7.4)
USB communication driver 0.33
Device not supported!
Device not supported!
  22.000379     Driver failed to start (exit status=1)

nut-server.service - Network UPS Tools - power devices information server
     Loaded: loaded (/lib/systemd/system/nut-server.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2022-10-07 09:41:09 +04; 1h 49min ago
    Process: 1145 ExecStart=/sbin/upsd (code=exited, status=0/SUCCESS)
   Main PID: 1146 (upsd)
      Tasks: 1 (limit: 18983)
     Memory: 1.5M
        CPU: 118ms
     CGroup: /system.slice/nut-server.service
             └─1146 /lib/nut/upsd

Oct 07 11:05:29 TurkelServer upsd[1146]: Data for UPS [UPS] is stale - check driver
Oct 07 11:06:37 TurkelServer upsd[1146]: Can't connect to UPS [UPS] (nutdrv_atcl_usb-UPS): No such file or directory
Oct 07 11:06:43 TurkelServer upsd[1146]: Connected to UPS [UPS]: nutdrv_atcl_usb-UPS
Oct 07 11:06:45 TurkelServer upsd[1146]: Data for UPS [UPS] is stale - check driver
Oct 07 11:17:50 TurkelServer upsd[1146]: Can't connect to UPS [UPS] (nutdrv_atcl_usb-UPS): No such file or directory
Oct 07 11:18:00 TurkelServer upsd[1146]: Connected to UPS [UPS]: nutdrv_atcl_usb-UPS
Oct 07 11:18:02 TurkelServer upsd[1146]: Data for UPS [UPS] is stale - check driver
Oct 07 11:23:08 TurkelServer upsd[1146]: Can't connect to UPS [UPS] (nutdrv_atcl_usb-UPS): No such file or directory
Oct 07 11:23:18 TurkelServer upsd[1146]: Connected to UPS [UPS]: nutdrv_atcl_usb-UPS
Oct 07 11:23:28 TurkelServer upsd[1146]: Data for UPS [UPS] is stale - check driver
jimklimov commented 2 years ago

UPSmart supported devices typically are handled by drivers for Megatec Qx family of protocols, so nutdrv_qx was a good choice (might also try blazer_usb).

Higher debug level, more so with modern NUT (2.8.0 or a build from master branch), may show why it got rejected - maybe permissions, etc.? Did udev get reconfigured to let nut account access the USB device node?

trecords commented 2 years ago

No luck. I think my subdriver is hunnox but it is not included into 2.7 but I see it is in 2.8 nut version. I have installed nut 2.8 from testing sources in debian but it came without hunnox driver too. Is there are any way to install extra subdriver for nut ? I dont want to run git and mess production server((

jimklimov commented 2 years ago

For SUBdriver, which is built into a binary along with others and shared code, probably have to "mess" - at least to build with same settings as packaging and insert that driver binary into the setup (maybe rename the older one instead of overwriting) :\

MasterOfStar commented 1 year ago

I also have an EAST ups which also uses UPSmart. But it doesn't connect via USB, it connects via the serial port. Which driver should I use?

blazer_ser is ok

jimklimov commented 1 year ago

Should also be nutdrv_qx (it's unified for ser and USB devices), or blazer_ser

lavavrik commented 1 year ago

I also have an EAST ups which also uses UPSmart. But it doesn't connect via USB, it connects via the serial port. Which driver should I use?

blazer_ser is ok

@MasterOfStar What exact EAST model you have? I have EA-280P and can’t get it to work reliably with Qx/hunnox :/

MasterOfStar commented 1 year ago

I also have an EAST ups which also uses UPSmart. But it doesn't connect via USB, it connects via the serial port. Which driver should I use? blazer_ser is ok

@MasterOfStar What exact EAST model you have? I have EA-280P and can’t get it to work reliably with Qx/hunnox :/

EAST EA-305 and uses blazer_ser mode. But, it is a serial UPS. This mode may not apply to your UPS model.