riello IPG 800 serial. Serial-to-USB cable

[angelbarrera92]

Hi!

I am having problems configuring my Riello IPG 800 that comes with a serial port. I bought a serial-to-usb cable to connect to my proxmox server.

I am the only one trying to connect a UPS with a serial-to-usb cable? I tried configuring nut with both drivers: riello_ser and riello_usb. None working :(

Any tip to debug the issue?

[jimklimov]

On one hand, wondering if you are using the (pre-packaged) older NUT release 2.7.4, which does not benefit from later fixes (and maybe bugs) in the master branch - and if you can deploy a custom build of NUT. In particular, there were some riello fixes are in open or recently closed PRs. On another hand, you would need a serial driver for the serial port device, probably using "port = /dev/ttyUSB0" or similar config option. Beside riello, you can try nutdrv_qx as the new common driver for many "Qx" protocol devices. Driver binaries can be started with debug args (-DDDDDD) to see better what fails (might be not protocol mismatch, but e.g. FS permissions to access the device node - can try running as `-u root` then).

…

On Thu, Feb 17, 2022, 06:38 Ángel Barrera ***@***.***> wrote: Hi! I am having problems configuring my Riello IPG 800 that comes with a serial port. I bought a serial-to-usb cable to connect to my proxmox server. I am the only one trying to connect a UPS with a serial-to-usb cable? I tried configuring nut with both drivers: riello_ser and riello_usb. None working :( Any tip to debug the issue? — Reply to this email directly, view it on GitHub <#1302>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMPTFCKIOHLLW6EY2AADH3U3SCUZANCNFSM5OTUWGBA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[angelbarrera92]

Hi @jimklimov

Ye, you are right, i were trying the pre-packaged version (2.7.4).
Today i've tested building nut by following this doc: https://github.com/networkupstools/nut/wiki/Building-NUT-on-Debian,-Raspbian-and-Ubuntu
But i'm facing the same error with all drivers i'm testing:

Configuration file looks like:
ups.conf file:

maxretry = 3
[sai]
  driver = nutdrv_qx
  port = /dev/ttyUSB0

Im using the /dev/ttyUSB0 after checking dmesg logs:

[    5.062684] usb 1-4: ch341-uart converter now attached to ttyUSB0

Testing the riello_ser binary/driver:

/lib/nut/riello_ser -DDDDDDDDD -a sai -u root
Network UPS Tools - Riello serial driver 0.07 (2.7.4.1)
Warning: This is an experimental driver.
Some features may not function correctly.

   0.000000	[D3] do_global_args: var='maxretry' val='3'
   0.000011	[D3] main_arg: var='driver' val='riello_ser'
   0.000017	[D3] main_arg: var='port' val='/dev/ttyUSB0'
   0.000024	[D5] send_to_all: SETINFO driver.parameter.port "/dev/ttyUSB0"
   0.000031	[D1] Built-in default or configured user for drivers 'nut' was ignored due to 'root' specified on command line
   0.000034	[D1] debug level is '9'
   0.000801	[D5] send_to_all: SETINFO device.type "ups"
   0.000809	[D2] entering upsdrv_initups()
   0.001161	[D2] set baudrate 9600
   0.001332	[D2] try to detect SENTR
   5.004991	[D2] try to detect GPSER
  10.010020	[D2] set baudrate 1200
  10.010399	[D2] try to detect SENTR
  15.014676	[D2] try to detect GPSER
  20.016940	Can't connect to the UPS on port /dev/ttyUSB0!

Trying riello_usb:

/lib/nut/riello_usb -DDDDDDDDD -a sai -u root
Network UPS Tools - Riello USB driver 0.07 (2.7.4.1)
Warning: This is an experimental driver.
Some features may not function correctly.

   0.000000	[D3] do_global_args: var='maxretry' val='3'
   0.000013	[D3] main_arg: var='driver' val='riello_usb'
   0.000017	[D3] main_arg: var='port' val='/dev/ttyUSB0'
   0.000022	[D5] send_to_all: SETINFO driver.parameter.port "/dev/ttyUSB0"
   0.000032	[D1] Built-in default or configured user for drivers 'nut' was ignored due to 'root' specified on command line
   0.000034	[D1] debug level is '9'
   0.001089	[D5] send_to_all: SETINFO device.type "ups"
   0.117922	[D3] usb_busses=0x55d8e1ed9e10
   0.117938	[D2] Checking device (152D/0561) (002/002)
   0.118565	[D2] - VendorID: 152d
   0.118572	[D2] - ProductID: 0561
   0.118593	[D2] - Manufacturer: unknown
   0.118597	[D2] - Product: External USB 3.0
   0.118600	[D2] - Serial Number: DD564198838B4
   0.118604	[D2] - Bus: 002
   0.118607	[D2] - Device: 002
   0.118610	[D2] - Device release number: 0007
   0.118614	[D2] Trying to match device
   0.118617	[D3] match_function_regex: matching a device...
   0.118621	[D2] Device does not match - skipping
   0.118628	[D2] Checking device (1D6B/0003) (002/001)
   0.118773	[D2] - VendorID: 1d6b
   0.118781	[D2] - ProductID: 0003
   0.118786	[D2] - Manufacturer: Linux 5.4.157-1-pve xhci-hcd
   0.118804	[D2] - Product: xHCI Host Controller
   0.118821	[D2] - Serial Number: 0000:00:14.0
   0.118827	[D2] - Bus: 002
   0.118832	[D2] - Device: 001
   0.118837	[D2] - Device release number: 0504
   0.118842	[D2] Trying to match device
   0.118847	[D3] match_function_regex: matching a device...
   0.118853	[D2] Device does not match - skipping
   0.118863	[D2] Checking device (8087/0AAA) (001/003)
   0.118876	[D2] - VendorID: 8087
   0.118881	[D2] - ProductID: 0aaa
   0.118886	[D2] - Manufacturer: unknown
   0.118891	[D2] - Product: unknown
   0.118896	[D2] - Serial Number: unknown
   0.118901	[D2] - Bus: 001
   0.118906	[D2] - Device: 003
   0.118911	[D2] - Device release number: 0002
   0.118916	[D2] Trying to match device
   0.118921	[D3] match_function_regex: matching a device...
   0.118927	[D2] Device does not match - skipping
   0.118948	[D2] Checking device (1A86/7523) (001/002)
   0.119239	[D2] - VendorID: 1a86
   0.119247	[D2] - ProductID: 7523
   0.119253	[D2] - Manufacturer: unknown
   0.119258	[D2] - Product: USB2.0-Ser!
   0.119263	[D2] - Serial Number: unknown
   0.119267	[D2] - Bus: 001
   0.119273	[D2] - Device: 002
   0.119278	[D2] - Device release number: 0254
   0.119283	[D2] Trying to match device
   0.119289	[D3] match_function_regex: matching a device...
   0.119296	[D2] Device does not match - skipping
   0.119304	[D2] Checking device (1D6B/0002) (001/001)
   0.119435	[D2] - VendorID: 1d6b
   0.119443	[D2] - ProductID: 0002
   0.119462	[D2] - Manufacturer: Linux 5.4.157-1-pve xhci-hcd
   0.119466	[D2] - Product: xHCI Host Controller
   0.119471	[D2] - Serial Number: 0000:00:14.0
   0.119476	[D2] - Bus: 001
   0.119495	[D2] - Device: 001
   0.119500	[D2] - Device release number: 0504
   0.119505	[D2] Trying to match device
   0.119511	[D3] match_function_regex: matching a device...
   0.119517	[D2] Device does not match - skipping
   0.119525	[D2] libusb0: No appropriate HID device found
   0.119534	No supported devices found. Please check your device availability with 'lsusb'
and make sure you have an up-to-date version of NUT. If this does not help,
try running the driver with at least 'subdriver', 'vendorid' and 'productid'
options specified. Please refer to the man page for details about these options
(man 8 riello_usb).

Output with the generic driver you mentioned above:

/lib/nut/nutdrv_qx -DDDDDDDDD -a sai -u root
Network UPS Tools - Generic Q* USB/Serial driver 0.32 (2.7.4.1)
USB communication driver (libusb 0.1) 0.42
   0.000000	[D3] do_global_args: var='maxretry' val='3'
   0.000013	[D3] main_arg: var='driver' val='nutdrv_qx'
   0.000019	[D3] main_arg: var='port' val='/dev/ttyUSB0'
   0.000038	[D5] send_to_all: SETINFO driver.parameter.port "/dev/ttyUSB0"
   0.000045	[D1] Built-in default or configured user for drivers 'nut' was ignored due to 'root' specified on command line
   0.000066	[D1] debug level is '9'
   0.000887	[D5] send_to_all: SETINFO device.type "ups"
   0.000894	[D1] upsdrv_initups...
   0.101552	[D3] send: 'QGS'
   1.102711	[D3] read: timeout (0)
   1.102733	[D2] qx_process_answer: short reply (input.voltage)
   1.102819	[D3] send: 'QGS'
   2.103935	[D3] read: timeout (0)
   2.103949	[D2] qx_process_answer: short reply (input.voltage)
   2.104034	[D3] send: 'QGS'
   3.104764	[D3] read: timeout (0)
   3.104806	[D2] qx_process_answer: short reply (input.voltage)
   3.104886	[D3] send: 'M'
   4.105941	[D3] read: timeout (0)
   4.105957	[D2] qx_process_answer: short reply (ups.firmware.aux)
   4.106044	[D3] send: 'M'
   5.106699	[D3] read: timeout (0)
   5.106746	[D2] qx_process_answer: short reply (ups.firmware.aux)
   5.106820	[D3] send: 'M'
   6.107930	[D3] read: timeout (0)
   6.107944	[D2] qx_process_answer: short reply (ups.firmware.aux)
   6.108024	[D3] send: 'M'
   7.108791	[D3] read: timeout (0)
   7.108824	[D2] qx_process_answer: short reply (ups.firmware.aux)
   7.108924	[D3] send: 'M'
   8.109215	[D3] read: timeout (0)
   8.109231	[D2] qx_process_answer: short reply (ups.firmware.aux)
   8.109312	[D3] send: 'M'
   9.110336	[D3] read: timeout (0)
   9.110371	[D2] qx_process_answer: short reply (ups.firmware.aux)
   9.110441	[D3] send: 'QS'
  10.110733	[D3] read: timeout (0)
  10.110748	[D2] qx_process_answer: short reply (input.voltage)
  10.110836	[D3] send: 'QS'
  11.111343	[D3] read: timeout (0)
  11.111378	[D2] qx_process_answer: short reply (input.voltage)
  11.111464	[D3] send: 'QS'
  12.111576	[D3] read: timeout (0)
  12.111606	[D2] qx_process_answer: short reply (input.voltage)
  12.111705	[D3] send: 'D'
  13.112490	[D3] read: timeout (0)
  13.112524	[D2] qx_process_answer: short reply (input.voltage)
  13.112634	[D3] send: 'D'
  14.112784	[D3] read: timeout (0)
  14.112799	[D2] qx_process_answer: short reply (input.voltage)
  14.112872	[D3] send: 'D'
  15.113607	[D3] read: timeout (0)
  15.113622	[D2] qx_process_answer: short reply (input.voltage)
  15.113742	[D3] send: 'Q1'
  16.114781	[D3] read: timeout (0)
  16.114802	[D2] qx_process_answer: short reply (input.voltage)
  16.114878	[D3] send: 'Q1'
  17.115943	[D3] read: timeout (0)
  17.115959	[D2] qx_process_answer: short reply (input.voltage)
  17.116049	[D3] send: 'Q1'
  18.116794	[D3] read: timeout (0)
  18.116811	[D2] qx_process_answer: short reply (input.voltage)
  18.116883	[D3] send: 'Q1'
  19.117911	[D3] read: timeout (0)
  19.117928	[D2] qx_process_answer: short reply (input.voltage)
  19.118044	[D3] send: 'Q1'
  20.119091	[D3] read: timeout (0)
  20.119110	[D2] qx_process_answer: short reply (input.voltage)
  20.119181	[D3] send: 'Q1'
  21.120203	[D3] read: timeout (0)
  21.120217	[D2] qx_process_answer: short reply (input.voltage)
  21.120305	[D3] send: 'Q1'
  22.120796	[D3] read: timeout (0)
  22.120824	[D2] qx_process_answer: short reply (input.voltage)
  22.120923	[D3] send: 'Q1'
  23.121507	[D3] read: timeout (0)
  23.121536	[D2] qx_process_answer: short reply (input.voltage)
  23.121624	[D3] send: 'Q1'
  24.121780	[D3] read: timeout (0)
  24.121794	[D2] qx_process_answer: short reply (input.voltage)
  24.121878	[D3] send: 'Q1'
  25.122962	[D3] read: timeout (0)
  25.122982	[D2] qx_process_answer: short reply (input.voltage)
  25.123066	[D3] send: 'Q1'
  26.123675	[D3] read: timeout (0)
  26.123692	[D2] qx_process_answer: short reply (input.voltage)
  26.123828	[D3] send: 'Q1'
  27.124769	[D3] read: timeout (0)
  27.124793	[D2] qx_process_answer: short reply (input.voltage)
  27.124809	[D2] find_nut_info: info type series not found
  27.124814	[D2] claim: cannot find series
  27.124821	[D2] find_nut_info: info type series not found
  27.124826	[D2] claim: cannot find series
  27.124833	[D2] find_nut_info: info type series not found
  27.124838	[D2] claim: cannot find series
  27.124914	[D3] send: 'Q1'
  28.125970	[D3] read: timeout (0)
  28.125986	[D2] qx_process_answer: short reply (input.voltage)
  28.126071	[D3] send: 'Q1'
  29.127147	[D3] read: timeout (0)
  29.127163	[D2] qx_process_answer: short reply (input.voltage)
  29.127232	[D3] send: 'Q1'
  30.128255	[D3] read: timeout (0)
  30.128274	[D2] qx_process_answer: short reply (input.voltage)
  30.128350	[D3] send: 'Q1'
  31.128929	[D3] read: timeout (0)
  31.128950	[D2] qx_process_answer: short reply (input.voltage)
  31.129034	[D3] send: 'Q1'
  32.129525	[D3] read: timeout (0)
  32.129545	[D2] qx_process_answer: short reply (input.voltage)
  32.129620	[D3] send: 'Q1'
  33.130645	[D3] read: timeout (0)
  33.130662	[D2] qx_process_answer: short reply (input.voltage)
  33.130683	[D3] send: 'Q1'
  34.131705	[D3] read: timeout (0)
  34.131724	[D2] qx_process_answer: short reply (input.voltage)
  34.131810	[D3] send: 'Q1'
  35.132797	[D3] read: timeout (0)
  35.132818	[D2] qx_process_answer: short reply (input.voltage)
  35.132882	[D3] send: 'Q1'
  36.133910	[D3] read: timeout (0)
  36.133925	[D2] qx_process_answer: short reply (input.voltage)
  36.133928	Device not supported!
  36.133948	Device not supported!

I don't know if this UPS is supported :(

[jimklimov]

Seems #498 also touched on (poor) support of Riello IDG devices, with https://alioth-lists.debian.net/pipermail/nut-upsdev/2017-November/007357.html for details - however there apparently they had some data. Some other PRs and issues about it like #530 #957 #1280 imply that for some devices of this name we have support, even if it was in need of improvements (no idea if same HW/protocol behind the name... vendors do mix things sometimes).

Is the serial-to-usb converter part of the UPS or a separate device? Can you check with something (ideally some COM console of another PC/server/switch/... or even by shorting the RX and TX pins) that it actually works as a serial port? Also, is the serial cable the one supplied with the UPS? Some vendors have special pin-outs, or even additional components inside the cable/connectors, etc. so a standard DB9-DB9 null-modem cable would not work for them; no idea if this can be the case here though.

[NilByte]

https://www.mail-archive.com/nut-upsdev@alioth-lists.debian.net/msg00124.html

Links to:

https://view.officeapps.live.com/op/view.aspx?src=https%3A%2F%2Fwww.mail-archive.com%2Fnut-upsdev%40alioth-lists.debian.net%2Fmsg00124%2FRiello_UPS_protocol_list_02-2021.xlsx&wdOrigin=BROWSELINK

IPG800 is supposed to be supported.

[angelbarrera92]

Seems #498 also touched on (poor) support of Riello IDG devices, with https://alioth-lists.debian.net/pipermail/nut-upsdev/2017-November/007357.html for details - however there apparently they had some data. Some other PRs and issues about it like #530 #957 #1280 imply that for some devices of this name we have support, even if it was in need of improvements (no idea if same HW/protocol behind the name... vendors do mix things sometimes).

Is the serial-to-usb converter part of the UPS or a separate device? Can you check with something (ideally some COM console of another PC/server/switch/... or even by shorting the RX and TX pins) that it actually works as a serial port? Also, is the serial cable the one supplied with the UPS? Some vendors have special pin-outs, or even additional components inside the cable/connectors, etc. so a standard DB9-DB9 null-modem cable would not work for them; no idea if this can be the case here though.

About the seria-to-usb converter... I bought it in another famous online store (china). I don't think I have nothing at home to test the serial port :(
I've sent an email to riello support to know what driver to use and so on...

https://www.mail-archive.com/nut-upsdev@alioth-lists.debian.net/msg00124.html

Links to:

https://view.officeapps.live.com/op/view.aspx?src=https%3A%2F%2Fwww.mail-archive.com%2Fnut-upsdev%40alioth-lists.debian.net%2Fmsg00124%2FRiello_UPS_protocol_list_02-2021.xlsx&wdOrigin=BROWSELINK

IPG800 is supposed to be supported.

Ye, I know, but seems that there are two different version, the current one ships with a USB port. Mine seems to be an older one with a serial/com port.