There are several reasons you may get a “Motherboard Initialization Failed" error message. One error is "Motherboard initialization failed, unsupported structure version." With this error, you can have transient communication issues (disconnects) or even data loss.
One cause for this error happens on sites where heavy equipment is present. This type of equipment creates surges on the input power and EFI (Electromagnetic Field Interference) to occur. This gets picked up by the USB cable which serves as an antenna. This then causes the arm to disconnect or can cause other communications issues with the arm.
Another major cause is when you have MIG, TIG, or plasma cutters within 150 feet of the Romer Arm. The arc that these devices creates causes (EMI) Electromagnetic Interference with the USB communication cable between the arm and the computer.
To resolve the issue, try to do one or more of the following:
Move the arm away from the offending equipment or devices.
Integrate a power conditioner.
Use a modified USB cable.
Instead of a USB cable, use Wi-Fi to communicate with the arm.
For other solutions and related information, see the "What are some possible causes of Romer Arm disconnects and motherboard initialization errors?" article on the Hexagon Knowledgebase site.
More: