Section 7. Installation
327
Q: What are the termination conditions that will stop incoming data from being
stored?
A: Termination conditions:
•
TerminationChar argument is received
•
MaxNumChars argument is met
•
TimeOut argument is exceeded
SerialIn() does NOT stop storing when a Null character (&h00) is received
(unless a NULL character is specified as the termination character). As a string
variable, a NULL character received will terminate the string, but nevertheless
characters after a NULL character will continue to be received into the variable
space until one of the termination conditions is met. These characters can later
be accessed with MoveBytes() if necessary.
Q: How can a variable populated by SerialIn() be used in more than one
sequence and still avoid using the variable in other sequences when it contains old
data?
A: A simple caution is that the destination variable should not be used in more
than one sequence to avoid using the variable when it contains old data.
However, this is not always possible and the root problem can be handled more
elegantly.
When data arrives independent from execution of the CRBasic program, such as
occurs with streaming data, measures must be taken to ensure that the incoming
data are updated in time for subsequent processes using that data. When the task
of writing data is separate from the task of reading data, you should control the
flow of data with deliberate control features such as the use of flags or a time-
stamped weigh point as can be obtained from a data table.
There is nothing unique about SerialIn() with regard to understanding how to
correctly write to and read from global variables using multiple sequences.
SerialIn() is writing into an array of characters. Many other instructions write
into an array of values (characters, floats, or longs), such as Move(),
MoveBytes(), GetVariables(), SerialInRecord(), SerialInBlock(). In all cases,
when writing to an array of values, it is important to understand what you are
reading, if you are reading it asynchronously, in other words reading it from some
other task that is polling for the data at the same time as it is being written,
whether that other task is some other machine reading the data, like LoggerNet, or
a different sequence, or task, within the same machine. If the process is
relatively fast, like the Move() instruction, and an asynchronous process is
reading the data, this can be even worse because the “reading old data” will
happen less often but is more insidious because it is so rare.
7.7.19 String Operations
String operations are performed using CRBasic string functions.
Summary of Contents for CR3000 Micrologger
Page 2: ......
Page 3: ......
Page 4: ......
Page 6: ......
Page 30: ......
Page 34: ......
Page 36: ......
Page 96: ......
Page 485: ...Section 8 Operation 485 8 11 2 Data Display FIGURE 110 Keyboard and Display Displaying Data ...
Page 487: ...Section 8 Operation 487 FIGURE 112 CR1000KD Real Time Custom ...
Page 491: ...Section 8 Operation 491 FIGURE 116 Keyboard and Display File Edit ...
Page 496: ......
Page 502: ......
Page 564: ...Section 11 Glossary 564 FIGURE 126 Relationships of Accuracy Precision and Resolution ...
Page 566: ......
Page 594: ......
Page 598: ......
Page 600: ......
Page 602: ......
Page 624: ......
Page 642: ......
Page 643: ......
