# Why the realport keeps returning character 'T'?

**URL:** <https://forums.digi.com/t/why-the-realport-keeps-returning-character-t/15565>\
**Category:** Realport\
**Tags:** realport\
**Created:** [October 12, 2015, 4:29pm UTC](https://forums.digi.com/t/why-the-realport-keeps-returning-character-t/15565 "2015-10-12T16:29:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![CarlCarl](https://avatars.discourse-cdn.com/v4/letter/c/bbce88/32.png) [@CarlCarl](https://forums.digi.com/u/CarlCarl)\
**Post date:** [October 12, 2015, 4:29pm UTC](https://forums.digi.com/t/why-the-realport-keeps-returning-character-t/15565/1 "2015-10-12T16:29:17Z")

</div>

I am using Digi TS16 server and configured to use realports. The port keeps returning character ‘T’ no matter the physical port is connected to another device or not.

What is the meaning of that ‘T’ character?

---

<div class="post-metadata">

**Author:** ![userid0](https://avatars.discourse-cdn.com/v4/letter/u/f6c823/32.png) [@userid0](https://forums.digi.com/u/userid0)\
**Post date:** [October 13, 2015, 9:34am UTC](https://forums.digi.com/t/why-the-realport-keeps-returning-character-t/15565/2 "2015-10-13T09:34:44Z")

</div>

The letter T could point to a mismatch of the settings between the serial port and the attached device. I recommend checking the baud rate, stop bits, character bits and parity settings to ensure the match.

Also, it might be a good idea to run a loopback test to make sure the port is functional on the Digi unit:

[http://knowledge.digi.com/articles/Knowledge\_Base\_Article/HOW-TO-Loopback-Test-Portserver-or-Digi-One-family-Device-or-Terminal-Server-products-through-the-CLI-using-Connect](http://knowledge.digi.com/articles/Knowledge_Base_Article/HOW-TO-Loopback-Test-Portserver-or-Digi-One-family-Device-or-Terminal-Server-products-through-the-CLI-using-Connect)
