How to solve Display Communication Issue -12 -33 in Medical QAWeb Agent

Article number: [2005] - Legacy code: [12130]

If during a display calibration or quality assurance tests made by Medical QAWeb Agent (old QAWeb1), the process gets stopped and the user gets notified with a display communication error message -33 or -12 as follow, please proceed with the recommendations here below: 

Notification on QAWeb Agent (after a calibration process got manually triggered):

Notification on QAWeb Server:

Root cause: 

The root cause of this issue is a recent change made in the MXRT driver 10.184.2.0

Explanation:

We made a fix in barcomfd.dll, for supporting thunderbolt hotplugging, for the situation when a USB device is not cleanly restarted, it could prevent the graphics driver from cleanly restart.

Unfortunately, this solution is causing the unintended side effect where during calibration, a devnode change notification could come through and leads to USB structure being lost, and leads to QAWeb lose USB communication and fails to complete calibration.

Solution: 

The issue has been addressed in the MXRT Drivers 10.184.2.1 and later (see KB6421)

Properties

Last updated Jul 19, 2023