Campbell Scientific CR10X TD Operating System Addendum for CR510, CR10X, and C - Page 22

Values in Routing Table

Page 22 highlights

TD ADDENDUM  SECTION 1. FUNCTIONAL MODES The *D15 entries are sent when the program is retrieved. They can also be set like other *D settings via the DLD file. 1.8.9 ALLOCATE MEMORY FOR GENERAL PURPOSE FILES *D16:xx ;allocate xx 64K byte chunks of memory for general purpose files. The area comes out of final storage space. Files are stored in a circular buffer (ring memory) in this space. 1.8.10 VIEW ROUTING TABLE *D17 allows viewing the current routing table information. This is view only. TABLE 1.8-12. Values in Routing Table Key Entry Display Comments 1.8.11 SET PAKBUS ROUTER BEACON INTERVAL TABLE 1.8-13. Set Beacon interval Key Entry Display Comments *D 13:00 18A Enter Command Enter the beacon interval settings A 01:xxxx Enter the Interval (seconds) for SDC7 A 02:xxxx Enter the Interval (seconds) for SDC8 A 03:xxxx Enter the Interval (seconds) for CS I/O Pin Enabled, 9600 baud *D 13:00 17A Enter Command Enter the view routing table command A 04:xxxx Enter the Interval (seconds) for RS232, 9600 baud (CR23X only) 1.8.12 PAKBUS NEIGHBOR FILTER 01:xxxx ;pakbus address of destination node In some networks, sending beacons can be disruptive. Entering values in the *D19 mode 02:xxxx ;via neighbor with xxxx pakbus disables the beacon. A PakBus datalogger with address nonzero *D19 settings will not send beacons and will only respond to beacons from nodes 03:xxxx ;a worst case response time with addresses in the neighbor list. metric (seconds) Instead of sending beacons, the datalogger will (Repeats for next destination node.) send "hello" messages to neighbors in the list to determine if it can communicate with them. Neighbors (or potential neighbors) should be nodes that communicate directly with the datalogger without going through a router. Note that this list is not automatically cleared by compiling a new program. (It may be changed if the new program contains *D19 entries.) It can be edited by changing entries. Once 0 is entered for a neighbor address, all entries beyond the 0 entry are cleared. AD-1-6

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62

TD ADDENDUM
SECTION 1.
FUNCTIONAL MODES
AD-1-6
The *D15 entries are sent when the program is
retrieved.
They can also be set like other *D
settings via the DLD file.
1.8.9 ALLOCATE MEMORY FOR GENERAL
PURPOSE FILES
*D16:xx
;allocate xx 64K byte chunks of
memory for general purpose files.
The area comes out of final storage
space.
Files are stored in a circular
buffer (ring memory) in this space.
1.8.10
VIEW ROUTING TABLE
*D17 allows viewing the current routing table
information. This is view only.
TABLE 1.8-12.
Values in Routing Table
Key
Entry
Display
Comments
*D
13:00
Enter Command
17A
Enter the view routing table
command
01:xxxx
;pakbus address of destination
node
02:xxxx
;via neighbor with xxxx pakbus
address
03:xxxx
;a worst case response time
metric (seconds)
(Repeats for next destination node.)
1.8.11
SET PAKBUS ROUTER BEACON
INTERVAL
TABLE 1.8-13.
Set Beacon interval
Key
Entry
Display
Comments
*D
13:00
Enter Command
18A
Enter the beacon interval
settings
A
01:xxxx
Enter the Interval (seconds) for
SDC7
A
02:xxxx
Enter the Interval (seconds) for
SDC8
A
03:xxxx
Enter the Interval (seconds) for
CS I/O Pin Enabled, 9600 baud
A
04:xxxx
Enter the Interval (seconds) for
RS232, 9600 baud (CR23X
only)
1.8.12
PAKBUS NEIGHBOR FILTER
In some networks, sending beacons can be
disruptive.
Entering values in the *D19 mode
disables the beacon.
A PakBus datalogger with
nonzero *D19 settings will not send beacons
and will only respond to beacons from nodes
with addresses in the neighbor list.
Instead of sending beacons, the datalogger will
send “hello” messages to neighbors in the list to
determine if it can communicate with them.
Neighbors (or potential neighbors) should be
nodes that communicate directly with the
datalogger without going through a router.
Note that this list is not automatically cleared by
compiling a new program.
(It may be changed
if the new
program contains *D19 entries.)
It
can be edited by changing entries.
Once 0 is
entered for a neighbor address, all entries
beyond the 0 entry are cleared.