Technical FAQs

Ask a Question

Unity fails to connect to the M340 using the USB PLC driver in Windows 10.

Goals and Symptoms
Unity fails to connect to the M340 using the USB PLC driver in Windows 10.
Facts and Change
Unity 12

Causes and Fixes​
Unity fails to connect to the M340 PLC The BMX CPU option will appear to be connected when viewing the Windows
'Add Remove Hardware' drop down  list The Device Manager will also show that the BMX CPU is not recognized with a code 52.  


Code 52 is the error code returned by Windows 10 indicating that the driver is unsigned.  Starting with Windows 10
build 1607 and as part of the secure boot feature, Microsoft requires all drivers to be digitally signed before
they can be installed.  The PC driver provided with Unity 12 is not digitally signed.  This is the reason for the issue.

This is a known issue and Engineering is working on resolving it.  As a workaround, the driver enforcement can be disabled
by using the procedure described in the attachment document named 'Secureboot_Workaround_Error52.pdf'..

***** Update: This has been resolved with PLC USB Driver Suite version 14.12 (3.15 IE25) *****
 
Was this helpful?
What can we do to improve the information ?