receive only encrypted commands and data. Header level information needed for
routing is not encrypted. An encrypted CR1000 can also communicate with an
unencrypted datalogger. Use an EncryptExempt() instruction in the CRBasic
program to define one or more PakBus addresses to which encrypted messages
will not be sent.
Campbell Scientific products supporting PakBus encryption include the
following:
• LoggerNet 4.2
• CR1000 datalogger (OS26 and later)
• CR3000 datalogger (OS26 and later)
• CR800 series dataloggers (OS26 and later)
• CR1000 series dataloggers (OS1 and later)
Device Configuration Utility (DevConfig) v. 2.04 and later
• Network Planner v. 1.6 and later.
Portions of the protocol to which PakBus encryption is applied include:
• All BMP5 messages
• All settings related messages
Note Basic PakBus messages such as Hello, Hello Request, Send Neighbors,
Get Neighbors, and Echo are NOT encrypted.
The PakBus encryption key can be set in the CR1000 datalogger through:
• DevConfig Deployment tab
• DevConfig Settings Editor tab
• PakBusGraph settings editor dialog
• Keyboard display
Be careful to record the encryption key in a secure location. If the encryption key
is lost, it needs to be reset. Reset the key on the keyboard display by deleting the
bullet characters that appear in the field, then enter the new key.
Note Encryption key cannot be set through the CRBasic program.
Setting the encryption key in datalogger support software (p. 512) (LoggerNet 4.2
and higher):
• Applies to CR1000, CR3000, CR800 series, and CR1000 dataloggers, and
PakBus routers, and PakBus port device types.
• Can be set through the LoggerNet Set Up screen, Network Planner, or
CoraScript (only CoraScript can set the setting for a PakBus port).
Note Setting the encryption key for a PakBus port device will force all messages
it sends to use encryption.
8.6 Alternate Telecommunications — Details
Related Topics:
• Alternate Telecommunications — Overview (p. 90)
• Alternate Telecommunications — Details (p. 407)
407