Page 75 of 110
Rev. G
and contents of this transmissions will depend on whether each parameter
has already changed within the specified period.
i. Send Anchors: This feature causes not only the value that met the
exception for a parameter to be sent, but also the previous value it was
compared to during the evaluation. The values will be sent with sequential
time stamps. This is a feature that is similar to the OSIsoft Interface and
should be used with caution.
j. Scaling: This setting allows for normal or reverse scaling of each parameter.
k. Buffering Mode: This setting enables or disables data buffering and allows
a selection for which medium is used for buffering. Data buffering is where
we store data and timestamps if a connection is not available.
i. To Memory: Buffers data in RAM memory, which is faster, but is
volatile, so if mCore loses power the buffered data will be lost.
ii. To Disk: Buffers data to the eMMC non-volatile storage. Considerably
slower, but easily fast enough for most applications. However, if
buffering is constant and used a great deal, then it will eventually
damage the eMMC storage.
l. Buffering File Limit: Allows you to choose the amount of memory
dedicated to buffering. Keep in mind that you if you use Data Logging, it will
take some memory as well.
Section 9: Live Data Viewer
Live Data Viewer is a tool used to view live data either when connected to mCore locally
or remotely using an internet browser. Once you’ve added a group with mapped out
parameters and committed all changes, you can view live data. To be clear, the bottom
left-hand menu must read COMMITTED in order to view live data. Refresh rates are
typically between .5s to 1s.
To Next Page
Loading...