Campbell CR800 Series - Alternate Comms Protocols; TCP;IP - Details

Section 8. Operation
428
Caution When using the ComME com port with non-PakBus protocols,
incoming characters can be corrupted by concurrent use of the CS I/O for
SDC comms. PakBus comms use a low-level protocol (pause / finish /
ready sequence) to stop incoming data while SDC occurs.
Non-PakBus comms include TCP/IP protocols, ModBus, DNP3, and
generic, CRBasic-driven use of CS I/O.
Though usually unnoticed, a short burst of SDC comms occurs at power-
up and other times when the datalogger is reset, such as when compiling
a program or changing settings that require recompiling. This activity is the
datalogger querying to see if the CR1000KD Keyboard/Display is
available.
When DevConfig and PakBus Graph retrieve settings, the CR800 queries
to determine what SDC devices are connected. Results of the query can
be seen in the DevConfig and PakBusGraph settings tables. SDC
queries occur whether or not an SDC device is attached.
8.10 Alternate Comms Protocols
Related Topics:
• Alternate Comms Protocols — Overview (p. 78)
• Alternate Comms Protocols — Details (p. 428)
The CR800 communicates with datalogger support software (p. 86) and other
Campbell Scientific dataloggers
(p. 561) using the PakBus (p. 508) protocol.
Modbus, DNP3, TCP/IP, and several industry-specific protocols are also
supported. CAN bus is supported when using the Campbell Scientific SDM-CAN
(p. 568) communication module.
8.10.1 TCP/IP — Details
Related Topics:
• TCP/IP — Overview
• TCP/IP — Details
(p. 428)
• TCP/IP Links — List (p. 570)
The following TCP/IP protocols are supported by the CR800 when using network
links
(p. 570) that use the resident IP stack or when using a cell modem with the
PPP/IP key enabled. The following sections include information on some of
these protocols: