Specifications

230 Module 131: Hardware Programming | Troubleshooting Hardware
Encryption Summary
 The server issues a different key each time it negotiates encryption with a controller
 Encryption can be enabled for one controller and disabled for another
 If both the server and controller have encryption disabled, communications are possible
 If both the server and controller have encryption enabled and the keys match, communications are possible
 If the server has encryption enabled but the controller does not, communications are not possible
 If the server does not have encryption enabled but the controller does, communications are not possible
 If the server and controller both have encryption enabled but the keys do not match, communications are
not possible
Disabling Encryption
Defaulting the controller is the only way to remove the encryption key.
This is by design and intended as a security feature. It means that physical access to the controller must be
gained before encryption can be disabled.
If the controller is defaulted, encryption must be disabled at the server before communications can be
established. This is done in the controller configuration tab.
The software will warn you prior to disabling encryption. Once this has been done, the Controller must be
defaulted to clear the encryption key.
If you are unsure of the state of encryption of either the Server or Controller, disable it at the Server then default
the Controller. This will ensure that neither are currently encrypted and will rule this out as a cause of
communications problems. Encryption should then be enabled once communications are established.