Can you troubleshoot and improve the quick client status and diagnostics? They have a great purpose however using TCP driver with devices other than PLCs, noticed that the device connection is broken sometimes demanding manual device connection restart for data string or message function. The quick client diagnostic tool shows "connected", and the diagnostic tag says "good" misleading the real status (broken connection). As a mitigation tactic I scripted system.device.restart function to restart the device in the gateway after every 15 minutes of data stream inactivity. The idea will be getting an alert or alarm based on real broken connection captured in the messaging diagnostic tag . Thanks