Section 8. Operation
515
the minimum is actually 24 bytes. Declare string variables
Public
and
sample string variables into data tables only as needed.
•
When using
GetVariables()
/
SendVariables()
to send values between
dataloggers, put the data in an array and use one command to get the
multiple values. Using one command to get 10 values from an array and
swath of 10 is much more efficient (requires only 1 transaction) than
using 10 commands to get 10 single values (requires 10 transactions).
•
Set the CR6 to be a PakBus router only as needed. When the CR6 is a
router, and it connects to another router like LoggerNet, it exchanges
routing information with that router and, possibly (depending on your
settings), with other routers in the network.
•
Set PakBus beacons and verify intervals properly. For example, there is
no need to verify routes every five minutes if communications are
expected only every 6 hours.
8.9.3 Initiating Comms (Callback)
Comms sessions are usually initiated by a PC. Once comms are established, the
PC issues commands to send programs, set clocks, collect data, etc. Because data
retrieval is managed by the PC, several PCs can have access to a CR6 without
disrupting the continuity of data. PakBus® allows multiple PCs to communicate
with the CR6 simultaneously when proper comms networks are installed.
Typically, the PC initiates comms with the CR6 with
datalogger support software
(p. 663).
However, some applications require the CR6 to call back the PC (initiate
comms). This feature is called 'Callback'. Special
LoggerNet
(p. 663)
features
enable the PC to receive calls from the CR6.
For example, if a fruit grower wants a frost alarm, the CR6 can contact him by
calling a PC, sending an email, text message, or page, or calling him with
synthesized-voice over telephone. Callback has been used in applications
including Ethernet, land-line telephone, digital cellular, and direct connection.
Callback with telephone is well documented in
CRBasic Editor Help
(search term
"callback"). For more information on other available Callback features, manuals
for various comms hardware may discuss Callback options.
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.
Summary of Contents for CR6 Series
Page 2: ......
Page 4: ......
Page 6: ......
Page 32: ......
Page 36: ......
Page 38: ......
Page 76: ...Section 5 Overview 76 FIGURE 20 Half Bridge Wiring Example Wind Vane Potentiometer ...
Page 80: ...Section 5 Overview 80 FIGURE 23 Pulse Input Wiring Example Anemometer ...
Page 136: ......
Page 454: ...Section 8 Operation 454 FIGURE 104 Narrow Sweep High Noise ...
Page 459: ...Section 8 Operation 459 FIGURE 106 Vibrating Wire Sensor Calibration Report ...
Page 535: ...Section 8 Operation 535 8 11 2 Data Display FIGURE 121 CR1000KD Displaying Data ...
Page 537: ...Section 8 Operation 537 FIGURE 123 CR1000KD Real Time Custom ...
Page 538: ...Section 8 Operation 538 8 11 2 3 Final Storage Data FIGURE 124 CR1000KD Final Storage Data ...
Page 539: ...Section 8 Operation 539 8 11 3 Run Stop Program FIGURE 125 CR1000KD Run Stop Program ...
Page 541: ...Section 8 Operation 541 FIGURE 127 CR1000KD File Edit ...
Page 546: ......
Page 552: ......
Page 610: ...Section 11 Glossary 610 FIGURE 137 Relationships of Accuracy Precision and Resolution ...
Page 612: ......
Page 648: ......
Page 650: ......
Page 688: ......
Page 689: ......