TS Shara / UPS Senoidal 3200va

[bpbastos]

Hello,

I am able to use this UPS using blazer_ser driver, but according to the docs TS Shara UPSs is supposed to use nutdrv_qx with sgs subdriver. Tried all sort of configurations but no success. At the moment I am using these configs:

[tsshara] driver = blazer_ser desc = "TS Shara" port = /dev/ttyACM0 protocol = "megatec"

Any chance to get this UPS working with nutdrv_qx?

Vendor ID = 0483 Product ID= 5740

Thanks!

[favarete]

My UPS is almost the same one (2200va in my case) and I can't make it to work using either blazer_ser not nutdrc_qx

[ovosimpatico]

Same here - got a UPS TS Shara Senoidal 2200va and it isn't working on any driver, nor is it detected using nut-scanner -U

[jimklimov]

FWIW, which NUT versions are you using? 2.7.4 (7 year old but still packaged by many distros), 2.8.0, or newer (e.g. custom master build)?

[ovosimpatico]

I tested 2.7.4 on Debian 11 (My server) and 2.8.0 on my Fedora Linux laptop.

Both of them do not recognize the UPS.

[dantti]

I have one and it just works, one thing that http://mylowtechstuff.blogspot.com/2018/02/utilizando-nut-para-controle-de-nobreak.html did not mention was that I needed to start the nut server sudo systemctl start nut-server, after this both blazer_ser and nutdrv_qx worked.

Ubuntu 22.04 LTS, and I made sure nut user was in dialup group to be able to open the serial port sudo gpasswd -a nut dialout.

BTW I recommend using /dev/serial/by-id/ instead of ttyACM which can have random numbers if some other device is attached.

[pedrovanzella]

@dantti what's the firmware version on your UPS? Mine's 23.002.001 and it works with blazer_ser but not with nutdrv_qx.

[bpbastos]

Just a little update, it seems like the firmware is the culprit.

# /lib/nut/nutdrv_qx  -DDDD -a tsshara
Network UPS Tools - Generic Q* USB/Serial driver 0.32 (2.8.0)
USB communication driver (libusb 1.0) 0.43
   0.000000     [D3] main_arg: var='driver' val='nutdrv_qx'
   0.000041     [D3] main_arg: var='desc' val='TS Shara'
   0.000048     [D3] main_arg: var='port' val='/dev/ttyACM1'
   0.000056     [D3] main_arg: var='protocol' val='megatec'
   0.000065     [D3] main_arg: var='runtimecal' val='2169,100,4339,50,8678,25,11108,20,17357,10'
   0.000077     [D3] main_arg: var='default.battery.voltage.high' val='27.00'
   0.000084     [D3] main_arg: var='default.battery.voltage.low' val='20.80'
   0.000095     [D1] debug level is '4'
   0.001125     [D1] upsdrv_initups...
   0.101687     [D2] Skipping protocol Voltronic 0.06
   0.101699     [D2] Skipping protocol Voltronic-QS 0.07
   0.101702     [D2] Skipping protocol Voltronic-QS-Hex 0.10
   0.101706     [D2] Skipping protocol Mustek 0.07
   0.101709     [D2] Skipping protocol Megatec/old 0.07
   0.101712     [D2] Skipping protocol BestUPS 0.06
   0.101715     [D2] Skipping protocol Mecer 0.07
   0.101786     [D3] send: 'Q1'
   0.310485     [D3] read: '(129.0 129.0 126.0 013 60.0 27.4 30.0 00001001'
   0.310630     [D3] send: 'I'
   0.482153     [D3] read: 'TS Shara        UPS Seno.  Saida 115V '
   0.482177     [D2] qx_process_answer: ups.firmware - invalid start character [54], expected [23]
   0.482258     [D3] send: 'Q1'
   0.691182     [D3] read: '(128.0 128.0 126.0 013 60.0 27.4 30.0 00001001'
   0.691315     [D3] send: 'I'
   0.862786     [D3] read: 'TS Shara        UPS Seno.  Saida 115V '
   0.862827     [D2] qx_process_answer: ups.firmware - invalid start character [54], expected [23]
   0.862907     [D3] send: 'Q1'
   1.071754     [D3] read: '(129.0 129.0 126.0 013 60.0 27.4 30.0 00001001'
   1.071895     [D3] send: 'I'
   1.243377     [D3] read: 'TS Shara        UPS Seno.  Saida 115V '
   1.243402     [D2] qx_process_answer: ups.firmware - invalid start character [54], expected [23]
   1.243411     [D2] Skipping protocol Zinto 0.06
   1.243415     [D2] Skipping protocol Masterguard 0.02
   1.243418     [D2] Skipping protocol Hunnox 0.01
   1.243422     [D2] Skipping protocol Ablerex 0.01
   1.243428     [D2] Skipping protocol Q1 0.07
   1.243433     Device not supported!
   1.243452     Device not supported!

[jimklimov]

Interesting... FWIW, ASCII 0x23 is the hash # character and it sees 0x54 T (from TS Shara...) in the reply. Not sure OTOH which is correct, if the spec says anything about it. Commuting now.

[bpbastos]

Is there anything I can do to help @jimklimov? Maybe it could be accents like "ãéïòû" that are commonly used in Brazilian Portuguese.