# Output Types

[![awh-guide-outputs.png](https://osr.wiki/uploads/images/gallery/2024-02/scaled-1680-/awh-guide-outputs.png)](https://osr.wiki/uploads/images/gallery/2024-02/awh-guide-outputs.png)

There are two main types of outputs: **Network** and **Serial**.

##### **Network**

[![add-buss-driver-serial.PNG](https://osr.wiki/uploads/images/gallery/2023-11/scaled-1680-/add-buss-driver-serial.PNG)](https://osr.wiki/uploads/images/gallery/2023-11/add-buss-driver-serial.PNG)

Network outputs enable connections to devices or software via [TCP](https://en.wikipedia.org/wiki/Transmission_Control_Protocol) or [UDP](https://en.wikipedia.org/wiki/User_Datagram_Protocol) protocols. In TCP mode, Ayva WebSocket Hub attempts to establish a connection to a WebSocket at the `/ws` endpoint on the specified host and port. In UDP mode, packets are sent directly to the designated host and port. Note that because UDP is *connectionless*, a UDP output will always be displayed as *Connected*, even if no application or device is actively listening at the specified host and port.

TCP is typically used to connect to WiFi-enabled devices, while UDP is typically used to stream to a [Virt-a-mate](https://osr.wiki/books/glossary/page/virt-a-mate) plugin such as [BusDriver](https://osr.wiki/books/busdriver) (though it can also be used for WiFi-enabled devices that support UDP).

##### **Serial**

**[![awh-guide-3.PNG](https://osr.wiki/uploads/images/gallery/2023-11/scaled-1680-/awh-guide-3.PNG)](https://osr.wiki/uploads/images/gallery/2023-11/awh-guide-3.PNG)**

**[![awh-guide-4.PNG](https://osr.wiki/uploads/images/gallery/2023-11/scaled-1680-/awh-guide-4.PNG)](https://osr.wiki/uploads/images/gallery/2023-11/awh-guide-4.PNG)**

Serial outputs facilitate device connections via the Serial protocol, typically through USB. However, they can also operate over [virtual serial ports](https://en.wikipedia.org/wiki/Virtual_COM_port) that emulate physical connections for other protocols, including Bluetooth Classic.