thr3ads.net - Nut upsuser - [Nut-upsuser] The dreaded Tripp Lite SMART500RT1U and NUT [Jun 2014]

If this information is useful, please help other people find it:
Share via:

Steve Ballantyne

2014-Jun-26 18:31 UTC

[Nut-upsuser] The dreaded Tripp Lite SMART500RT1U and NUT

<nut-upsuser at lists.alioth.debian.org>
I am doing my best to avoid have to spend $280 for a network monitoring
card to put into a $190 UPS just to have some good remote monitoring
capabilities.  Rather, I would like to monitor my many 1U Tripp Lite's on
my network using a Raspberry Pi running Raspian and using NUT.

However, I cannot seem to get it working.  And I while the hardware
compatibility list says that it is supported - I certainly have my doubts.

According to the list, I should be using the usbhid-ups driver. But when I
do that, it fails and tells me that I should be using tripplite_usb instead.

pi at raspberrypi ~ $ sudo /lib/nut/usbhid-ups -DDD -u root -a SMART500RT1U
Network UPS Tools - Generic HID driver 0.37 (2.6.4)
USB communication driver 0.32
   0.000000     debug level is '3'
   0.007268     upsdrv_initups...
   0.011293     Checking device (09AE/0001) (001/009)
   0.015827     - VendorID: 09ae
   0.017073     - ProductID: 0001
   0.018406     - Manufacturer: TRIPP LITE
   0.019801     - Product: TRIPP LITE SMART500RT1U
   0.021422     - Serial Number: unknown
   0.022460     - Bus: 001
   0.022639     Trying to match device
   0.023645     This Tripp Lite device (09ae/0001) is not supported by
usbhid-ups.
Please use the tripplite_usb driver instead.
8< SNIP!

Fine!  But when I use the tripplite_usb driver, it don't work either ...

pi at raspberrypi ~ $ sudo /lib/nut/tripplite_usb -u root -a SMART500RT1U
-DDDDD
Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.6.4)
Warning: This is an experimental driver.
Some features may not function correctly.

   0.000000     debug level is '5'
   0.009252     Checking device (09AE/0001) (001/009)
   0.013935     - VendorID: 09ae
   0.015179     - ProductID: 0001
   0.016578     - Manufacturer: TRIPP LITE
   0.017984     - Product: TRIPP LITE SMART500RT1U
   0.019899     - Serial Number: unknown
   0.020123     - Bus: 001
   0.020785     Trying to match device
   0.020974     Device matches
   0.022584     Detected a UPS: TRIPP LITE/TRIPP LITE SMART500RT1U
   0.022884     send_to_all: SETINFO ups.vendorid "09ae"
   0.023091     send_to_all: SETINFO ups.productid "0001"
   0.024146     send_to_all: SETINFO device.type "ups"
   0.024961     send_to_all: SETINFO driver.version "2.6.4"
   0.025174     send_to_all: SETINFO driver.version.internal "0.20"
   0.025897     send_to_all: SETINFO driver.name "tripplite_usb"
   0.026152     send_cmd(msg_len=2, type='
   0.026694     send_cmd: sending  3a 00 ff 0d 00 00 00 00 '........'
   1.130244     libusb_get_interrupt: Connection timed out
   1.131657     libusb_get_interrupt() returned 0 instead of 8 while
sending 3a 00 ff 0d 00 00 00 00 '........'
   2.133695     libusb_get_interrupt: Connection timed out
   2.135035     libusb_get_interrupt() returned 0 instead of 8 while
sending 3a 00 ff 0d 00 00 00 00 '........'
   3.137419     libusb_get_interrupt: Connection timed out
   3.138950     libusb_get_interrupt() returned 0 instead of 8 while
sending 3a 00 ff 0d 00 00 00 00 '........'
   4.141155     libusb_get_interrupt: Connection timed out
   4.142488     libusb_get_interrupt() returned 0 instead of 8 while
sending 3a 00 ff 0d 00 00 00 00 '........'
   5.144640     libusb_get_interrupt: Connection timed out
   5.145957     libusb_get_interrupt() returned 0 instead of 8 while
sending 3a 00 ff 0d 00 00 00 00 '........'
   6.147561     libusb_get_interrupt: Connection timed out
   6.148989     libusb_get_interrupt() returned 0 instead of 8 while
sending 3a 00 ff 0d 00 00 00 00 '........'
   7.150974     libusb_get_interrupt: Connection timed out
   7.152289     libusb_get_interrupt() returned 0 instead of 8 while
sending 3a 00 ff 0d 00 00 00 00 '........'
   8.154643     libusb_get_interrupt: Connection timed out
   8.156024     libusb_get_interrupt() returned 0 instead of 8 while
sending 3a 00 ff 0d 00 00 00 00 '........'
   9.158554     libusb_get_interrupt: Connection timed out
   9.159965     libusb_get_interrupt() returned 0 instead of 8 while
sending 3a 00 ff 0d 00 00 00 00 '........'
   9.262678     send_cmd: received 00 30 05 58 58 58 58 0d '.0.XXXX.'
(OK)
   9.264042     send_to_all: SETINFO ups.debug.0 "30 05 58 58 58 58 0d
'0.XXXX.'"
   9.265665     send_to_all: SETINFO ups.firmware.aux "protocol 3005"
   9.267228     send_cmd(msg_len=3, type='W')
   9.267744     send_cmd: sending  3a 57 00 a8 0d 00 00 00 '.W......'
   9.370082     send_cmd: received 57 00 0d 00 00 00 00 00 'W.......'
(OK)
   9.370367     send_cmd(msg_len=2, type='S')
   9.370565     send_cmd: sending  3a 53 ac 0d 00 00 00 00 '.S......'
   9.472418     send_cmd: received 53 01 04 00 00 64 00 0d 'S....d..'
(OK)
   9.472712     send_to_all: SETINFO ups.mfr "Tripp Lite"
   9.472899     send_cmd(msg_len=2, type='P')
   9.473087     send_cmd: sending  3a 50 af 0d 00 00 00 00 '.P......'
   9.575667     send_cmd: received 50 30 30 35 30 30 58 0d 'P00500X.'
(OK)
   9.576026     send_to_all: SETINFO ups.model "SMART500RT1U"
   9.576848     send_to_all: SETINFO ups.power.nominal "500"
   9.577346     send_cmd(msg_len=2, type='F')
   9.578194     send_cmd: sending  3a 46 b9 0d 00 00 00 00 '.F......'
   9.679786     send_cmd: received 46 33 33 34 34 30 31 0d 'F334401.'
(OK)
   9.680087     send_to_all: SETINFO ups.firmware "F334401"
   9.680278     send_cmd(msg_len=2, type='V')
   9.680463     send_cmd: sending  3a 56 a9 0d 00 00 00 00 '.V......'
   9.782790     send_cmd: received 56 02 00 0c 01 58 58 0d 'V....XX.'
(OK)
   9.783126     Unknown input voltage range: 0x02
   9.783308     Unknown number of switchable load banks: 0x01
   9.783476     send_cmd(msg_len=2, type='V')
   9.783664     send_cmd: sending  3a 56 a9 0d 00 00 00 00 '.V......'
   9.885906     send_cmd: received 56 02 00 0c 01 58 58 0d 'V....XX.'
(OK)
   9.886240     send_to_all: SETINFO ups.debug.V "02 00 0c 01 58 58 0d
'....XX.'"
   9.886425     send_cmd(msg_len=2, type='U')
   9.886618     send_cmd: sending  3a 55 aa 0d 00 00 00 00 '.U......'
   9.988651     send_cmd: received 55 00 00 0d 00 00 00 00 'U.......'
(OK)
   9.989595     send_to_all: SETINFO ups.id "0"
   9.990206     send_to_all: SETFLAGS ups.id RW STRING
   9.990984     send_to_all: SETAUX ups.id 5
   9.991202     Unit ID: 0
   9.991406     send_to_all: SETINFO input.voltage.nominal "120"
   9.991607     send_to_all: SETINFO battery.voltage.nominal "0"
   9.992388     send_to_all: SETINFO ups.debug.load_banks "0"
   9.993437     send_to_all: SETINFO ups.delay.shutdown "64"
   9.993654     send_to_all: SETFLAGS ups.delay.shutdown RW STRING
   9.994438     send_to_all: SETAUX ups.delay.shutdown 3
   9.994961     send_to_all: ADDCMD shutdown.return
Unknown protocol (3005)Attached to Tripp Lite SMART500RT1U
   9.995802     send_cmd(msg_len=2, type='S')
   9.996015     send_cmd: sending  3a 53 ac 0d 00 00 00 00 '.S......'
  10.097779     send_cmd: received 53 01 04 00 00 64 00 0d 'S....d..'
(OK)
  10.098216     send_to_all: SETINFO ups.debug.S "01 04 00 00 64 00 0d
'....d..'"
  10.099156     Unknown value for s[1]: 0x01
  10.099388     send_to_all: SETINFO ups.status ""
  10.099568     send_cmd(msg_len=2, type='L')
  10.100346     send_cmd: sending  3a 4c b3 0d 00 00 00 00 '.L......'
  10.202393     send_cmd: received 4c 00 00 00 07 58 58 0d 'L....XX.'
(OK)
  10.202731     send_to_all: SETINFO ups.debug.L "00 00 00 07 58 58 0d
'....XX.'"
  10.202923     send_cmd(msg_len=2, type='D')
  10.203115     send_cmd: sending  3a 44 bb 0d 00 00 00 00 '.D......'
  10.304883     send_cmd: received 44 00 79 00 86 0d 00 00 'D.y.....'
(OK)
  10.305216     send_to_all: SETINFO ups.debug.D "00 79 00 86 0d 00 00
'.y.....'"
  10.305412     send_cmd(msg_len=2, type='V')
  10.306322     send_cmd: sending  3a 56 a9 0d 00 00 00 00 '.V......'
  10.408136     send_cmd: received 56 02 00 0c 01 58 58 0d 'V....XX.'
(OK)
  10.408437     send_cmd(msg_len=2, type='M')
  10.408636     send_cmd: sending  3a 4d b2 0d 00 00 00 00 '.M......'
  10.510511     send_cmd: received 4d 00 75 00 7c 0d 00 00 'M.u.....'
(OK)
  10.510851     send_to_all: SETINFO ups.debug.M "00 75 00 7c 0d 00 00
'.u.....'"
  10.511656     send_cmd(msg_len=2, type='T')
  10.512689     send_cmd: sending  3a 54 ab 0d 00 00 00 00 '.T......'
  10.614504     send_cmd: received 54 21 00 02 58 01 58 0d 'T...X.X.'
(OK)
  10.614835     send_to_all: SETINFO ups.debug.T "21 00 02 58 01 58 0d
'...X.X.'"
  10.615028     send_cmd(msg_len=2, type='P')
  10.615820     send_cmd: sending  3a 50 af 0d 00 00 00 00 '.P......'
  10.717503     send_cmd: received 50 30 30 35 30 30 58 0d 'P00500X.'
(OK)
  10.717838     send_to_all: SETINFO ups.debug.P "30 30 35 30 30 58 0d
'00500X.'"
  10.718023     send_to_all: DATAOK
  10.718606     dstate_init: sock /var/run/nut/tripplite_usb-SMART500RT1U
open on fd 5
  10.719616     send_to_all: SETINFO driver.parameter.pollinterval "2"
  10.720403     send_to_all: SETINFO device.mfr "Tripp Lite"
  10.721489     send_to_all: SETINFO device.model "SMART500RT1U"
  10.721708     send_cmd(msg_len=2, type='S')
  10.722544     send_cmd: sending  3a 53 ac 0d 00 00 00 00 '.S......'
  10.824514     send_cmd: received 53 01 04 00 00 64 00 0d 'S....d..'
(OK)
  10.824815     Unknown value for s[1]: 0x01
  10.824999     send_to_all: DATASTALE
  10.825812     send_cmd(msg_len=2, type='L')
  10.826909     send_cmd: sending  3a 4c b3 0d 00 00 00 00 '.L......'
  10.928616     send_cmd: received 4c 00 00 00 07 58 58 0d 'L....XX.'
(OK)
  10.928996     send_cmd(msg_len=2, type='D')
  10.929205     send_cmd: sending  3a 44 bb 0d 00 00 00 00 '.D......'
  11.031612     send_cmd: received 44 00 79 00 86 0d 00 00 'D.y.....'
(OK)
  11.031919     send_cmd(msg_len=2, type='V')
  11.032120     send_cmd: sending  3a 56 a9 0d 00 00 00 00 '.V......'
  11.133853     send_cmd: received 56 02 00 0c 01 58 58 0d 'V....XX.'
(OK)
  11.134151     send_cmd(msg_len=2, type='M')
  11.134349     send_cmd: sending  3a 4d b2 0d 00 00 00 00 '.M......'
  11.236481     send_cmd: received 4d 00 75 00 7c 0d 00 00 'M.u.....'
(OK)
  11.236790     send_cmd(msg_len=2, type='T')
  11.236988     send_cmd: sending  3a 54 ab 0d 00 00 00 00 '.T......'
  11.338728     send_cmd: received 54 21 00 02 58 01 58 0d 'T...X.X.'
(OK)
  11.339094     send_cmd(msg_len=2, type='P')
  11.339295     send_cmd: sending  3a 50 af 0d 00 00 00 00 '.P......'
  11.441597     send_cmd: received 50 30 30 35 30 30 58 0d 'P00500X.'
(OK)
  11.441902     send_to_all: DATAOK
  12.723124     send_cmd(msg_len=2, type='S')
  12.723419     send_cmd: sending  3a 53 ac 0d 00 00 00 00 '.S......'
  13.490411     send_cmd: received 53 01 04 00 00 64 00 0d 'S....d..'
(OK)
  13.491763     Unknown value for s[1]: 0x01
  13.493169     send_to_all: DATASTALE
  13.494659     send_cmd(msg_len=2, type='L')
  13.495869     send_cmd: sending  3a 4c b3 0d 00 00 00 00 '.L......'
  13.598529     send_cmd: received 4c 00 00 00 07 58 58 0d 'L....XX.'
(OK)
  13.599934     send_cmd(msg_len=2, type='D')
  13.600988     send_cmd: sending  3a 44 bb 0d 00 00 00 00 '.D......'
  13.702775     send_cmd: received 44 00 79 00 86 0d 00 00 'D.y.....'
(OK)
  13.703086     send_cmd(msg_len=2, type='V')
  13.703284     send_cmd: sending  3a 56 a9 0d 00 00 00 00 '.V......'
  13.805384     send_cmd: received 56 02 00 0c 01 58 58 0d 'V....XX.'
(OK)
  13.806270     send_cmd(msg_len=2, type='M')
  13.806489     send_cmd: sending  3a 4d b2 0d 00 00 00 00 '.M......'
  13.908517     send_cmd: received 4d 00 75 00 7c 0d 00 00 'M.u.....'
(OK)
  13.908944     send_cmd(msg_len=2, type='T')
  13.910002     send_cmd: sending  3a 54 ab 0d 00 00 00 00 '.T......'
  14.012381     send_cmd: received 54 21 00 02 57 01 58 0d 'T...W.X.'
(OK)
  14.012708     send_to_all: SETINFO ups.debug.T "21 00 02 57 01 58 0d
'...W.X.'"
  14.012902     send_cmd(msg_len=2, type='P')
  14.013099     send_cmd: sending  3a 50 af 0d 00 00 00 00 '.P......'
  14.115379     send_cmd: received 50 30 30 35 30 30 58 0d 'P00500X.'
(OK)
  14.115681     send_to_all: DATAOK

8< SNIP!

That last little bit between DATASTALE and DATAOK seems to loop on through
infinity.  Has anyone actually made this model work with nut?  I have dug
up some other very old threads that all seem to dead end without a
solution.

I should also mention that I have tried both a serial and a USB connection
for this.  But using a device with no actual serial port, the serial is
actually a Prolific pl2303 converter.

Steve Ballantyne
Network Engineer
MCSE/MCDST; Novell CLA; LPIC-1; CTT+; A+; Network+; Linux+; Server+;
I-Net+; Security+; SonicWALL CSSA
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20140626/1dd6882f/attachment-0001.html>

Charles Lepple

2014-Jun-26 20:12 UTC

head link

[Nut-upsuser] The dreaded Tripp Lite SMART500RT1U and NUT

On Thu, Jun 26, 2014 at 2:31 PM, Steve Ballantyne
<steve.ballantyne at gmail.com> wrote:> According to the list, I should be using the usbhid-ups driver. But when I
> do that, it fails and tells me that I should be using tripplite_usb
instead.
Sigh, it sounds like a collision of "protocol" numbers. If I recall,
Tripp Lite assured us that the USB Product ID (if not 0001) mapped to
the "protocol", but not necessarily vice versa. So the compatibility
list is referring to a device with USB IDs 09AE/3005.

09AE/0001 is essentially a USB-to-serial converter, and is not
compatible with usbhid-ups. (Theoretically, we could have a companion
driver that talks the same protocols over a real RS-232 port, but the
hardware I used to develop the tripplite_usb driver only has a USB
port.)

However, we don't have all of the 09AE/0001 protocols decoded in the
tripplite_usb driver.
> Fine!  But when I use the tripplite_usb driver, it don't work either
...
>
> pi at raspberrypi ~ $ sudo /lib/nut/tripplite_usb -u root -a SMART500RT1U
> -DDDDD
> Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.6.4)
> Warning: This is an experimental driver.
> Some features may not function correctly.
>
>    0.000000     debug level is '5'
>    0.009252     Checking device (09AE/0001) (001/009)
>    0.013935     - VendorID: 09ae
>    0.015179     - ProductID: 0001
>    0.016578     - Manufacturer: TRIPP LITE
>    0.017984     - Product: TRIPP LITE SMART500RT1U
>    0.019899     - Serial Number: unknown
>    0.020123     - Bus: 001
>    0.020785     Trying to match device
>    0.020974     Device matches
>    0.022584     Detected a UPS: TRIPP LITE/TRIPP LITE SMART500RT1U
>    0.022884     send_to_all: SETINFO ups.vendorid "09ae"
>    0.023091     send_to_all: SETINFO ups.productid "0001"
>    0.024146     send_to_all: SETINFO device.type "ups"
>    0.024961     send_to_all: SETINFO driver.version "2.6.4"
>    0.025174     send_to_all: SETINFO driver.version.internal
"0.20"
>    0.025897     send_to_all: SETINFO driver.name "tripplite_usb"
>    0.026152     send_cmd(msg_len=2, type='
>    0.026694     send_cmd: sending  3a 00 ff 0d 00 00 00 00
'........'
>    1.130244     libusb_get_interrupt: Connection timed out
>    1.131657     libusb_get_interrupt() returned 0 instead of 8 while
sending
> 3a 00 ff 0d 00 00 00 00 '........'
>    2.133695     libusb_get_interrupt: Connection timed out
>    2.135035     libusb_get_interrupt() returned 0 instead of 8 while
sending
> 3a 00 ff 0d 00 00 00 00 '........'
>    3.137419     libusb_get_interrupt: Connection timed out
>    3.138950     libusb_get_interrupt() returned 0 instead of 8 while
sending
> 3a 00 ff 0d 00 00 00 00 '........'
>    4.141155     libusb_get_interrupt: Connection timed out
>    4.142488     libusb_get_interrupt() returned 0 instead of 8 while
sending
> 3a 00 ff 0d 00 00 00 00 '........'
>    5.144640     libusb_get_interrupt: Connection timed out
>    5.145957     libusb_get_interrupt() returned 0 instead of 8 while
sending
> 3a 00 ff 0d 00 00 00 00 '........'
>    6.147561     libusb_get_interrupt: Connection timed out
>    6.148989     libusb_get_interrupt() returned 0 instead of 8 while
sending
> 3a 00 ff 0d 00 00 00 00 '........'
>    7.150974     libusb_get_interrupt: Connection timed out
>    7.152289     libusb_get_interrupt() returned 0 instead of 8 while
sending
> 3a 00 ff 0d 00 00 00 00 '........'
>    8.154643     libusb_get_interrupt: Connection timed out
>    8.156024     libusb_get_interrupt() returned 0 instead of 8 while
sending
> 3a 00 ff 0d 00 00 00 00 '........'
>    9.158554     libusb_get_interrupt: Connection timed out
>    9.159965     libusb_get_interrupt() returned 0 instead of 8 while
sending
> 3a 00 ff 0d 00 00 00 00 '........'
Hmm, this shouldn't take that long. Does it do that every time you
start the tripplite_usb driver, or only the first time?
>    9.262678     send_cmd: received 00 30 05 58 58 58 58 0d
'.0.XXXX.' (OK)
>    9.264042     send_to_all: SETINFO ups.debug.0 "30 05 58 58 58 58 0d
> '0.XXXX.'"
>    9.265665     send_to_all: SETINFO ups.firmware.aux "protocol
3005"
Here's that 3005 protocol ID.
>    9.267228     send_cmd(msg_len=3, type='W')
>    9.267744     send_cmd: sending  3a 57 00 a8 0d 00 00 00
'.W......'
>    9.370082     send_cmd: received 57 00 0d 00 00 00 00 00
'W.......' (OK)
Your unit might support a watchdog timer.
>    9.370367     send_cmd(msg_len=2, type='S')
>    9.370565     send_cmd: sending  3a 53 ac 0d 00 00 00 00
'.S......'
>    9.472418     send_cmd: received 53 01 04 00 00 64 00 0d
'S....d..' (OK)
Ah, what we should be seeing here is that "01 04" status in ASCII. I
think the 3004 protocol also encodes it in binary.
>    9.472712     send_to_all: SETINFO ups.mfr "Tripp Lite"
>    9.472899     send_cmd(msg_len=2, type='P')
>    9.473087     send_cmd: sending  3a 50 af 0d 00 00 00 00
'.P......'
>    9.575667     send_cmd: received 50 30 30 35 30 30 58 0d
'P00500X.' (OK)
>    9.576026     send_to_all: SETINFO ups.model "SMART500RT1U"
>    9.576848     send_to_all: SETINFO ups.power.nominal "500"
500W sounds right based on the name.
>    9.577346     send_cmd(msg_len=2, type='F')
>    9.578194     send_cmd: sending  3a 46 b9 0d 00 00 00 00
'.F......'
>    9.679786     send_cmd: received 46 33 33 34 34 30 31 0d
'F334401.' (OK)
>    9.680087     send_to_all: SETINFO ups.firmware "F334401"
>    9.680278     send_cmd(msg_len=2, type='V')
>    9.680463     send_cmd: sending  3a 56 a9 0d 00 00 00 00
'.V......'
>    9.782790     send_cmd: received 56 02 00 0c 01 58 58 0d
'V....XX.' (OK)
>    9.783126     Unknown input voltage range: 0x02
>    9.783308     Unknown number of switchable load banks: 0x01
Is this a 230V unit? Again, it's looking for the ASCII version of 0x02
(which would be 0x32)
>    9.783476     send_cmd(msg_len=2, type='V')
>    9.783664     send_cmd: sending  3a 56 a9 0d 00 00 00 00
'.V......'
>    9.885906     send_cmd: received 56 02 00 0c 01 58 58 0d
'V....XX.' (OK)
>    9.886240     send_to_all: SETINFO ups.debug.V "02 00 0c 01 58 58 0d
> '....XX.'"
>    9.886425     send_cmd(msg_len=2, type='U')
>    9.886618     send_cmd: sending  3a 55 aa 0d 00 00 00 00
'.U......'
>    9.988651     send_cmd: received 55 00 00 0d 00 00 00 00
'U.......' (OK)
>    9.989595     send_to_all: SETINFO ups.id "0"
>    9.990206     send_to_all: SETFLAGS ups.id RW STRING
>    9.990984     send_to_all: SETAUX ups.id 5
>    9.991202     Unit ID: 0
>    9.991406     send_to_all: SETINFO input.voltage.nominal "120"
^ 120V might just be the default.
> That last little bit between DATASTALE and DATAOK seems to loop on through
> infinity.  Has anyone actually made this model work with nut?  I have dug
up
> some other very old threads that all seem to dead end without a solution.
Don't think so, but I think we can make this work with some code
changes. Do you have access to a Windows box to verify some of the
readings, or does it have a readout on the front?

I can also get access to a Raspberry Pi if needed to rebuild the NUT package.

-- 
- Charles Lepple

Maybe Matching Threads

Search for more reasonably related threads

Nut upsuser - Jun 2014 - The dreaded Tripp Lite SMART500RT1U and NUT

[Nut-upsuser] The dreaded Tripp Lite SMART500RT1U and NUT

[Nut-upsuser] The dreaded Tripp Lite SMART500RT1U and NUT

Maybe Matching Threads