Device Connectivity Issues

at times, a device may display as disconnected or a tag may generate a success=false message refer to the following error messages and the following table explains conditions that might cause a device to disconnect or a tag to generate a false value, the reasons it disconnected, and the steps to connect the device error message steps to resolve free tag explicit register name required certain device drivers do not have a list of register names in the devicehub add tag form when a list of registers is not provided, the case sensitive register name must be entered exactly as it is defined in the plc the device does not display a connected status until a tag with a correct register name is created add a tag with a case sensitive register name see add tags docid\ xgwokqbtpevii7or82ll0 to learn more hid device in wait state some hid (human interface devices), such as barcode scanners, are always disconnected and only show a connected status when they send data to litmus edge this is a temporary state and no intervention is required the device connects when there is data to receive incorrect plc configuration if configuration changes have been made to a plc, the best way to ensure accurate status is to delete and recreate the device in devicehub delete the device see manage devices docid\ esazv soo0efdw5 ivc6y for more information create a new device with the correct plc configuration see connect a device docid\ ish7bqhzxswtdx8vbnszb and the industrial systems connection guide docid 8o4ksduafz6jcegj0whs4 for more information incorrect tag information to prevent the plc from going into fail safe mode or from crashing the process when a tag has incorrect information, litmus edge disconnects communication with the plc for example, a tag may contain an incorrect address monitor all the tags in flows to identify the bad tag find the tag with a success flag set to false delete the tag from devicehub see manage tags docid 19fclype fbpdvcxxwrb4 for more information if there is no data on the flows, restart the plc if a node in a flow indicates "waiting for messages" and nothing is displayed in the debug console, this means that litmus edge has stopped communicating with the plc, so there is no data success=false message this could be caused for several reasons wrong configuration for address or data type the tag doesn't exist in the plc the plc is not able to respond in time to the poll request if there are intermittent false messages and a majority of tag messages are success=true , this could be due to the plc not being able to respond in time to the poll requests you can increase the poll interval in the devicehub tag configuration to give more time to the plc to respond to requests you can also add a filter to remove the false messages if the configuration of the tag is incorrect, the status of the devicehub device will eventually show a disconnected status to prevent the plc from going into an error state to resolve this, you can delete the incorrect tag and refresh the device if this doesn't resolve the issue, you can reboot the gateway