DeviceHub

industrial devices such as plcs store data in registers using proprietary protocols that data is not accessible to modern systems without a translation layer devicehub is that translation layer it connects your devices to litmus edge, maps registers to named tags, and publishes tag values to the internal message broker devicehub supports devices from most major manufacturers, such as siemens, allen bradley, and hitachi, through device specific drivers for serial, ethernet, socketcan, and file based protocols for the full list of supported devices and drivers, see the industrial systems connection guide docid\ er7j0mogtlktbxyupdcd how devicehub connects industrial devices industrial devices such as plcs use proprietary protocols and register based memory without a translation layer, that data stays locked on the device devicehub bridges the gap centralized connection management add, configure, and monitor all your devices from one place protocol flexibility connect to devices over serial, ethernet, socketcan, or file based interfaces without writing custom code asset discovery scan the network to find devices connected to litmus edge before you configure them network diagnostics test ip connectivity and port accessibility for a device before adding it tag browsing browse predefined tags on a connected device and add them directly, without manually entering register addresses bulk tag import upload multiple tags at once from a csv file to configure data collection in bulk scheduled data collection define how often each tag is polled so you get the right data at the right cadence down stream flexibility once data is on the message broker, any subscriber, such as a dashboard, analytics pipeline, or alerting system, can use it how it works drivers form a two way connection with plc hardware devices and other industrial assets and collect register information from them each register is mapped to a litmus edge tag register information is stored in tags and the tags are published as topics to the internal message broker you can save data to the internal datastore by enabling the enable data store option and setting a retention time when you add a tag to a connected device, litmus edge polls that tag for data at the frequency you select the system normalizes the polled data and posts it to the internal message broker you can then subscribe to the data from the message broker for processing, visualization, and analysis what's next set up and manage devices and tags devices docid\ gcl1wovduhiq28as8aduk add and connect devices edit, refresh, and start and stop connections add metadata as key value pairs tags docid\ claxedp pbj aavc89tno add tags individually, in bulk, or by browsing a connected device modify, view, and copy tags asset discovery docid\ v4tnatjlih1uozozhchfz discover devices on the network that litmus edge is connected to utilities docid 5svpdf26uyftkyygxup3q test ip connectivity and port accessibility guides and reference industrial systems connection guide docid\ er7j0mogtlktbxyupdcd full list of supported devices and drivers devicehub guides docid\ jri2 fmsaigvuq8vscoaa step by step how to guides devicehub troubleshooting docid 7fa2 on6ftihpuds8v3sk troubleshoot connectivity and tag issues