> For the complete documentation index, see [llms.txt](https://docs.intrepidcs.com/neovi-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intrepidcs.com/neovi-api/development-faqs/how-do-i-open-more-than-one-channel-on-a-single-piece-of-hardware-intrepidcs-api.md).

# How do I open more than one channel on a single piece of hardware? - neoVI API

When calling [OpenNeoDevice](/neovi-api/win32-api-overview-intrepidcs-api/basic-functions-overview-intrepidcs-api/openneodevice-method-intrepidcs-api.md) or [OpenPortEx](/neovi-api/win32-api-overview-intrepidcs-api/deprecated-functions-overview-intrepidcs-api/openportex-method-intrepidcs-api.md) to connect to the device, all the enabled channels on the device are active. Nothing special needs to be done "open" another channel. Calling [GetMessages](/neovi-api/win32-api-overview-intrepidcs-api/message-functions-overview-intrepidcs-api/getmessages-method-intrepidcs-api.md) will get messages on all enabled channels. Looking at the [NetworkID](/neovi-api/win32-api-overview-intrepidcs-api/structures-types-and-defines-overview-intrepidcs-api/setting-structures-overview-intrepidcs-api/message-structures-neovi-api.md) in the message structure for that message, the channel the message occurred on can be determined. When transmitting a message using [TxMessage](/neovi-api/win32-api-overview-intrepidcs-api/message-functions-overview-intrepidcs-api/txmessages-method-intrepidcs-api.md), the third parameter is the [Network ID](/neovi-api/win32-api-overview-intrepidcs-api/structures-types-and-defines-overview-intrepidcs-api/setting-structures-overview-intrepidcs-api/neovi-network-id-list.md) to send the message out on.