--- title: Connect a device slug: litmusedge/product-features/devicehub/devices/connect-a-device description: Learn how to connect and configure devices. docTags: createdAt: 2022-05-13T19:50:45.000Z --- Connecting a device to Litmus Edge allows DeviceHub to collect data from the device using the appropriate industrial driver. Once connected, LE normalizes the device's data and publishes it message broker, where it becomes available for flows, analytics, integrations, and other platform features. Before connecting a device, make sure it is physically configured and that you have its connection parameters. Refer to the [Industrial Systems Connection Guide](docId\:eR7j0MOGTLktBXYupdcD-) and locate your device for specific instructions. Connect a device by selecting a driver, entering its connection parameters, and configuring optional properties such as metadata, alias topics, and logging. After you create the device, DeviceHub begins collecting data from the device immediately. # Video :::Iframe{iframeHeight="0" code=""} ::: # Connection Types Litmus Edge supports the following device connection types: | **Connection Type** | **Description** | | ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Ethernet** | Connects to devices over TCP/IP using an IP address and port number. The most common connection type for modern PLCs and networked industrial equipment. | | **Serial** | Connects to devices over a serial interface (RS232, RS485). Requires a communication port, baud rate, data bits, parity, and stop bits. | | **CAN** | Connects to devices on a Controller Area Network (CAN) bus. Requires a CAN bus module to be present on the hardware. | | **File-based** | Connects to data sources through a shared file path, such as a network share. | # Step 1: Select device to connect First, select the device type you want to connect and enter a name and description. **To connect a device:** 1. Navigate to **DeviceHub **> **Devices**. 2. From the *DeviceHub *pane, click the **Connect a Device **box. The *Connect Device* dialog box appears. ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/AON8AdMdrmxJB5taUBXgl_image.png" size="80" width="1050" height="839" position="flex-start" darkWidth="1050" darkHeight="839" showCaption="false" indent="2"} 3. From the **Device Type** drop-down list, select a device type. 4. From the **Driver Name** drop-down list, select a device name. 5. Enter a name and description for the device. The name can have numbers, uppercase and lowercase characters, and special characters. It can't start or end with a whitespace. # Step 2: Define device-specific parameters Define the parameters specific to the type of device you are connecting to. Refer to the following resources for information on specific drivers and how-to guides: - [Industrial Systems Connection Guide](docId\:eR7j0MOGTLktBXYupdcD-) - [DeviceHub Use Cases](docId\:jrI2-fmSAIGVuq8VScoaA) - [Gen1 and Gen2 Driver Differences](docId\:HaIxS2l_OqxFj1YVYWNc1) :::hint{type="warning"} **Important:** If you are connecting a device with a serial connection and using an RS232 to USB adapter, use only adapters with FTDI chips. Other adapters are not validated or recommended. If Litmus Edge doesn't have the driver for the adapter you are using, you can't install it separately. ::: ### Asset discovery tool Depending on the device and driver you select, you may have the option of using the [Asset Discovery Tool](docId\:Hg1GCidAOfT4mVkIBeYgx), which searches for devices and pre-fills network parameters to connect the device to Litmus Edge. Refer to the table below for the required and optional parameters for device types. | **Device Type** | **Required and Optional Parameters** | | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Ethernet device

| - **Network Address:** Enter a network address. This is the IP address for the device. - **Network Port:** Enter a network port. - **Slot Number **(Optional): Enter a value that indicates the position of the CPU located in a slot. | | Serial device

| * **Communication Port: **Enter up to three characters, and then select an available port. * **Baud Rate** (Optional): Enter a value. * **Data Bits**: Enter a value. * **Parity **(Optional): Select a value from the drop-down list. * **Slot Number** (Optional): Enter a value that indicates the position of the CPU located in a slot. * **Stop Bits** (Optional): Enter a value. | | CAN device

| - **Channel:** Make sure that there is a CAN bus module already available as a part of the hardware by checking that there is a value in the field. - **Bit Rate:** Enter a value. | | File-based device
| * **Path:** Enter the shared path. * **Min Req. Number** (Optional): Enter a value. * **Max Req. Number** (Optional): Enter a value. | # Step 3: Additional attributes You have the option of configuring the additional attributes of metadata and status register settings. ## Meta Data The *Meta Data *option summarizes basic information about data. It enables you to define, modify or delete key-value pair data for the device output payload later on. You can then use it to find, use, and reuse particular instances of data. :::hint{type="info"} **Note**: If you use special characters in meta data key names, the special characters are replaced with underscore characters in the payload. This can cause two key names to be combined into one. For example, configuring the key names `a**b` and `a&&b` creates only one key name (`a__b`). ::: See [Organize Device and Tag Data by Using Metadata](docId\:MU-6j6Zhi0CvCHDad0w8n) to learn more. If you enable **Meta Data**, the section expands with parameters to complete. By default, the list of Meta Data key-value pairs displays *No records defined*. ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/LPjPIDltza_oaSh_xphCC_image.png" size="80" width="1142" height="799" position="flex-start" darkWidth="1142" darkHeight="799" showCaption="false"} **To define meta tags:** 1. In the *Key *field, enter the meta tag key. 2. In the *Value *field, enter the meta tag value. 3. Click **+ Add**. 4. Continue adding key-value pairs you want to add. ## Status Register The *Status Register* option allows you to define a register for keeping track of the device status (either connected or disconnected). See [Use the Status Register to Connect a PLC](docId\:sfmoDfjGo5uzGl9Xx_-A7) to learn more. If you select the **Status Register** check box, the section expands. The parameters to configure depend on the specific device and tag parameters. See the [Industrial Systems Connection Guide](docId\:eR7j0MOGTLktBXYupdcD-) and refer to the *Tag Parameters* section for the device you are configuring. As long as the above register responds to polling by DeviceHub, the device appears in the UI as *Connected*, regardless of the status of any other tags added to that device. ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/VdWhJao44_sWGp640fPIc_image.png" size="80" width="1170" height="717" position="flex-start" darkWidth="1170" darkHeight="717" showCaption="false"} # Step 4: Optional settings You have the following optional settings you can configure for the device. ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/T83CWc952hHt4Q3ZNosMZ_image.png" size="80" width="1132" height="623" position="flex-start" darkWidth="1132" darkHeight="623" showCaption="false"} ## Enable alias topics The *Enable alias topics* option allows you to substitute long, unreadable device and tag IDs with human-readable device and tag names in topic names. See [Default Topics and Descriptions](docId:8U4c20-xGyzkJRP24GEvM) for more information. The **Enable alias topics** check box is selected by default. :::hint{type="info"} **Note:** - When you enable alias topics, DeviceHub stops publishing to raw topics and publishes only to alias topics. - Litmus Edge substitutes all special characters in aliases with "\_" (underscore). - When alias topics are enabled for a device, you can't use batch write topics. To use batch write topics, clear the **Enable alias topics** check box in the device configuration. See [Default Topics and Descriptions](docId:8U4c20-xGyzkJRP24GEvM) for more information. ::: ## Enable logging The Enable Logging option is available only for Gen 2 drivers. Once you connect the device, click the device tile and select the **Logs **tab to view the log. ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/_SicUYZ2w2QIIAmXkVPNV_image.png" size="80" width="1294" height="569" position="flex-start" caption="Logs tab" darkWidth="1294" darkHeight="569" showCaption="true"} ## Enable data store The Enable Data Store option allows you to define how long you want to store data locally. To enable this option, select the **Enable Data Store** check box, and then define the number of hours in the **Retention Hours** field. After creating the device, a data store icon appears in the top-right corner of the device tile. ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/N7_pDCKBhSYHHCzIRc_s9_image.png" size="60" width="428" height="328" position="flex-start" caption="The Enable Data Store icon" darkWidth="428" darkHeight="328" showCaption="true"} ## Publish on polling interval :::hint{type="info"} **Note**: This option is only available for Gen 2 drivers. ::: - If this option is selected, the driver always publishes messages according to the polling interval configuration. If the driver has not completed the request to read the data at a polling interval, the payload has a `success=false` message. - If this option is not selected, the driver does not publish a message at the polling interval if the request to read data has not completed. ## Watchdog :::hint{type="info"} **Note**: This option is not available for all drivers. For example, drivers that act as servers don't have this option, such as Industrial OT Server and OSI Agent. ::: If this option is selected, the driver is monitored based on the Watchdog period (in seconds) you configure. If an issue is detected, then the driver restarts. ## Publish additional attributes This option is disabled by default. You can enable or disable this option, which includes the status code, source timestamp, and server timestamp in the new DeviceHub payload fields. :::hint{type="info"} **Note**: This option is only available for the following Gen 2 drivers: - BACnet - DNP3 - Modbus - OPC UA - Siemens S7 ::: - **Source Timestamp**: This option reflects the exact time the data source applied the timestamp to a variable value. If selected, the driver will ensures accurate tracking of when data was generated and allows for better incident analysis. - **Server Timestamp**: This option captures the moment the server received the value. It provides additional information for the timing of data accuracy and reliability. - **Status Code**: This option indicates the quality or state of the data being received. It helps you identify errors or issues with communication. # Step 5: Create device When done defining the new device, click **Create Device**. A tile for the new device appears in the *Devices *pane. A green **CONNECTED** indicator means that a connection to the device has been established. You can stop a device to disconnect it. If you have connectivity issues, see [Device Connectivity Issues](docId\:Duoc4Zw_wFVhoTUXjzBzL) for troubleshooting information.