# UART output as well as input **URL:** \ **Category:** Support\ **Created:** [September 8, 2017, 9:19pm UTC](https://forum.qoitech.com/t/uart-output-as-well-as-input/79 "2017-09-08T21:19:34Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![jeremy](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.qoitech.com/jeremy/32/20_2.png) [@jeremy](https://forum.qoitech.com/u/jeremy)\ **Post date:** [September 8, 2017, 9:19pm UTC](https://forum.qoitech.com/t/uart-output-as-well-as-input/79/1 "2017-09-08T21:19:35Z")
Is it possible to send commands to the target device via the UART? It would be handy to be able to interact with a target device via the UART when connected to the Arc. On the subject of UART, would it be possible to use a different UART port than the one on the Arc? ---
**Author:** ![chrfle](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.qoitech.com/chrfle/32/288_2.png) [@chrfle](https://forum.qoitech.com/u/chrfle)\ **Post date:** [September 11, 2017, 8:37am UTC](https://forum.qoitech.com/t/uart-output-as-well-as-input/79/2 "2017-09-11T08:37:20Z")
Hello Jeremy It is possible through the scripting interface available to Premium users to send commands via UART. See [device:write\_tx](https://www.qoitech.com/help/scripting/modules/otii.html#device:write_tx) in the documentation for more information. Currently we do not have any support in the UI to write to an UART. I’m not sure what you mean with “different UART port”. You can use traditional UART cables as well, but unfortunately, it’s read only at the moment. ---
**Author:** ![jeremy](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.qoitech.com/jeremy/32/20_2.png) [@jeremy](https://forum.qoitech.com/u/jeremy)\ **Post date:** [September 15, 2017, 10:08am UTC](https://forum.qoitech.com/t/uart-output-as-well-as-input/79/3 "2017-09-15T10:08:25Z")
> [@chrfle](#): > > It is possible through the scripting interface available to Premium users to send commands via UART. See device:write\_tx in the documentation for more information. Currently we do not have any support in the UI to write to an UART. I was more thinking about just dynamically typing commands in rather than anything scripted. > [@chrfle](#): > > I’m not sure what you mean with “different UART port”. You can use traditional UART cables as well, but unfortunately, it’s read only at the moment. So for example maybe the device does not directly expose a UART to connect to the Arc and you have to use a special adaptor or maybe the console is a virtual serial device over USB. So just generally just allow selection of any com port on the (host) system. ---
**Author:** ![chrfle](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.qoitech.com/chrfle/32/288_2.png) [@chrfle](https://forum.qoitech.com/u/chrfle)\ **Post date:** [September 15, 2017, 11:23am UTC](https://forum.qoitech.com/t/uart-output-as-well-as-input/79/4 "2017-09-15T11:23:46Z")
> [@jeremy](#): > > So just generally just allow selection of any com port on the (host) system. We loop through all devices considered serial ports and add them as UART device if they don’t match a known hardware. There’s a file in the otii directory of your documents directory named uart\_blacklist.json. Open that and double check that we don’t ignore the vid & pid of your device. You can safely remove all the items blacklisted. If you want to go back to default just delete the file and we will create a new one on next start with standard values. ---
**Author:** ![jeremy](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.qoitech.com/jeremy/32/20_2.png) [@jeremy](https://forum.qoitech.com/u/jeremy)\ **Post date:** [September 15, 2017, 12:52pm UTC](https://forum.qoitech.com/t/uart-output-as-well-as-input/79/5 "2017-09-15T12:52:00Z")
Ah right I see, just updated to the latest version of the software and can see them now, Thanks. ---
**Author:** ![adnexo\_gmbh](https://avatars.discourse-cdn.com/v4/letter/a/e99b99/32.png) [@adnexo\_gmbh](https://forum.qoitech.com/u/adnexo_gmbh)\ **Post date:** [September 23, 2017, 11:26am UTC](https://forum.qoitech.com/t/uart-output-as-well-as-input/79/6 "2017-09-23T11:26:05Z")
I agree with @jeremy, a way to send commands via UART would be nice. Since it’s still a manual task it does not replace the scripting / premium package in any way 🙂 Of course it’s possible through an FTDI dongle in parallel, but it’s less convenient. ---
**Author:** ![chrfle](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.qoitech.com/chrfle/32/288_2.png) [@chrfle](https://forum.qoitech.com/u/chrfle)\ **Post date:** [September 26, 2017, 7:41am UTC](https://forum.qoitech.com/t/uart-output-as-well-as-input/79/7 "2017-09-26T07:41:27Z")
I’ll add this feature request to our internal backlog. ---
**Author:** ![chrfle](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.qoitech.com/chrfle/32/288_2.png) [@chrfle](https://forum.qoitech.com/u/chrfle)\ **Post date:** [September 17, 2018, 12:28pm UTC](https://forum.qoitech.com/t/uart-output-as-well-as-input/79/8 "2018-09-17T12:28:23Z")
Today we released 2.2.0 software and 1.0.10 firmware. With the combination of those, Uart TX is now supported in the Otii UI. Get it on the [download page](https://www.qoitech.com/download). Hope you like it. ---
**Author:** ![jeremy](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.qoitech.com/jeremy/32/20_2.png) [@jeremy](https://forum.qoitech.com/u/jeremy)\ **Post date:** [September 17, 2018, 1:30pm UTC](https://forum.qoitech.com/t/uart-output-as-well-as-input/79/9 "2018-09-17T13:30:04Z")
Excellent, I will give it a try ---
**Author:** ![isakvisini](https://avatars.discourse-cdn.com/v4/letter/i/4491bb/32.png) [@isakvisini](https://forum.qoitech.com/u/isakvisini)\ **Post date:** [May 15, 2020, 6:03pm UTC](https://forum.qoitech.com/t/uart-output-as-well-as-input/79/11 "2020-05-15T18:03:18Z")
Hi…i had the similar situation and i observed that If I write a UART output function, the actual data outputed is shown in a window in uvision GUI (UART1 window pane).I need a window to initiate the reverse operationSomewhere for me to manually type data that will be seen by the simulating environment (uvision) as having been received on the serial port.