INSTRUCTION MANUAL PakBus Networking Guide for the CR10X, CR510, CR23X, and CR200 Series and LoggerNet 2.1C Revision: 3/05 C o p y r i g h t ( c ) 2 0 0 4 - 2 0 0 5 C a m p b e l l S c i e n t i f i c , I n c .
PakBus Networking Table of Contents PDF viewers note: These page numbers refer to the printed version of this document. Use the Adobe Acrobat® bookmarks tab for links to specific sections. 1. Introduction.................................................................1 2. Quick Start – A Basic PakBus Network.....................2 Step 1 Set Up Base RF400 Series Radio.........................................................3 Step 2 Set Up Remote RF400 Series ................................................
PakBus Networking Table of Contents 4.2 LoggerNet PakBus Setup ....................................................................... 36 4.2.1 PakBusPort................................................................................... 36 4.2.2 PakBusPort is Dialed.................................................................... 36 5. Communication Device Setups................................36 5.1 RF400 Series ..........................................................................................
PakBus Networking Table of Contents 7.4.5 Hello Exchange .............................................................................57 7.4.6 Hop Metric ....................................................................................58 7.4.7 Goodbye Message .........................................................................58 7.4.8 Broadcast Packets .........................................................................59 7.5 Router ..............................................................
PakBus Networking Table of Contents Q. Log View ................................................................Q-1 Figures 1. PakCom I/O Terminal Screen .................................................................... 4 2. Edlog PakBus Settings .............................................................................. 6 3. PakCom CR2XX Settings / Tools ............................................................. 8 4. PakCom Radio Settings / OS Download ............................................
PakBus Networking Guide 1. Introduction We know the advantages of email vs. a telephone conversation: • A real time connection is not necessary as the network accepts messages at any time. • Network devices have buffers to handle multiple messages on the network. • The network itself intelligently optimizes routes. • Backup routes are possible. In similar fashion, PakBus improves upon traditional connection-based datalogger communications.
PakBus Networking Guide 2. Quick Start – A Basic PakBus Network Ingredients of a PakBus Network • LoggerNet (server). • PakBus devices (dataloggers with PakBus OS or native PakBus devices such as the CR200 Series). • Routers (if used; typically dataloggers with PakBus OS and configured as routers). • Communication peripherals (RF400 Series, COM210, COM310, NL100, etc.). Setup of a PakBus Network • Create the device map in LoggerNet.
PakBus Networking Guide Router uses neighbor filter potential neighbor settings to discover CR205_2 CR205_3 Server uses static route to discover CR10XPB_1 ROUTER PC (LoggerNet Server) RF400 RF400 CR205_2 CR10XPB_1 CR205_3 For this Quick Start network example you will need the following items or the equivalent: 1. Compatible PC with LoggerNet 2.1c or higher and PakCom software. 2. CR10XPB or CR510PB datalogger (with PakBus OS). 3. CR10KD keyboard display. 4.
PakBus Networking Guide FIGURE 1. PakCom I/O Terminal Screen • Click on I/O Terminal, click on Open Port, and press the RF400’s “Program” green button. • Press “3” to Restore Defaults. You have just selected (among other things) the default Hopping Sequence of “0”. It is best to have an ‘unused’ Hopping Sequence.
PakBus Networking Guide d. Configure Standby Mode to “< 24 mA always on” e. In Standard Setup configure the Active Interface = Datalogger CSDC (by default this will be CSDC 7). f. Save All Parameters and Exit Setup. Step 3 – Establish Temporary Direct Communications to CR10XPB_1 a. Connect CR10XPB to 12 VDC power supply and turn on 12V power. b. Using an SC12 cable and SC32B, connect the CR10XPB to the LoggerNet PC’s active COM port. c. Attach CR10KD keyboard display to CR10XPB using SC12 cable.
PakBus Networking Guide 3: Data Table (P84) 1: 0 Seconds into Interval 2: 10 Seconds Interval 3: 0 (0 = auto allocate, -x = redirect to inloc x) 4: BASIC Table Name 4: Sample (P70) 1: 1 2: 1 Reps Loc [ Battery 5: Sample (P70) 1: 1 2: 2 Reps Loc [ Panel_Temp b. ] ] Save as “BASIC.CSI” in Edlog. Step 5 – Do CR10XPB PakBus Setup in Edlog and Send it to Datalogger a. Click on Edlog, Options, PakBus Settings. b. Configure as shown below FIGURE 2.
PakBus Networking Guide When sent to the datalogger, the program with the above settings: CAUTION • Sets the CR10XPB PakBus Address to 1. • Configures the CR10XPB as a router by entering non-zero values in Max Nodes, Max Neighbors, and Max Routers.
PakBus Networking Guide BeginProg Scan(10,sec) 'Make Measurements Therm109 (AirTemp_C,1,1,Ex1,1.0,0) CallTable AirTemp NextScan EndProg d. Save and compile the program as “TEMP_PROBE.CR2”. Step 7 – Set up CR205s and Download Program a. Label one CR205 as “CR205_2” and the other as “CR205_3” representing their future PakBus Addresses. b. Connect the CR205s to 12VDC supplies. c. Using an SC12 cable, connect CR205_2’s RS-232 port to an available COM port.
PakBus Networking Guide g. Using Download Program button, download TEMP_PROBE.BIN to the datalogger. Check the Information window to be sure the program is running. h. Repeat Step 7 with CR205_3 except make its PakBus Address (Datalogger Address) = 3. Step 8 – Set up CR205 Radios Do the following setup for CR205_2 and CR205_3 in turn. a. Using PakCom, verify that the PC Address is 4094 (LoggerNet’s PakBus Address). b.
PakBus Networking Guide FIGURE 4. PakCom Radio Settings / OS Download c. Select the Radio Hop Sequence decided upon for the RF400s in Step 2. d. Select the Radio Net Address decided upon in Step 2. e. Leave Radio Address = 0. f. Select Radio Power Mode = RF_ON (radio not duty cycling). g. Click Save Settings button to transfer settings to CR205. h. Repeat Step 8 for an exact match in these settings with CR205_3. i.
PakBus Networking Guide critical). On each CR205 connect a 10KΩ resistor from EX1 to SE1 and a (signal ground). These 22KΩ resistor from SE1 to the adjacent resistors simulate a 109 thermister probe at approximately 22 degrees Celsius. c. With CR205 cabled to your PC’s COM port, connect with PakCom, click on Monitor Data Tables, enter an Update in Seconds of “2”, and select the Public data table. The AirTemp_C that you are measuring or simulating will be displayed as below. FIGURE 5.
PakBus Networking Guide e. Highlight ComPort_1 and select a COM port that is available on your machine. Communications Enabled should be checked and Extra Response Time should be zero. f. Highlight PakBusPort and make the Beacon Interval = 0 (apply it). FIGURE 6. PakBusPort Settings g. 12 Highlight CR10XPB_1 and verify the settings shown.
PakBus Networking Guide FIGURE 7. CR10XPB_1 Settings h. Highlight CR205_2 and select PakBus Address 2. FIGURE 8.
PakBus Networking Guide i. Highlight CR205_3 and change PakBus Address to 3. FIGURE 9. CR205_3 Setup Step 11 – Set up Network Hardware a. Verify the following: 9 Antennas are on RF400s and CR205s. 9 12V supply is connected to base RF400 9 Base RF400’s RS-232 port is attached by SC12 cable to PC COM port b. Cable the ‘router’ RF400’s CSI/O port to the CR10XPB. c. Place CR10XPB/RF400 and CR205s within range of each other.
PakBus Networking Guide Step 12 – LoggerNet Connect to Dataloggers a. Highlight the CR10XPB_1 device in LoggerNet Connect Screen’s Station window. b. Click the Connect button. c. Open Status Monitor on the LoggerNet Toolbar and highlight ComPort_1. Click View I/O and size/position the Low Level Log window to view I/O occurring between LoggerNet and the CR10XPB. On the left of the window the “T”s represent data LoggerNet transmitted and the “R”s represent data LoggerNet has received.
PakBus Networking Guide and AirTemp_C. The values associated with these will update every 10 seconds which is the scan rate of TEMP_PROBE.CR2. FIGURE 11. Display of CR205_2 Variables h. Connect to and view AirTemp_C, etc. in CR205_3. i. Your PakBus Network is now functioning. You can collect data, send a different program, or monitor any of the three PakBus dataloggers. j. With LoggerNet not beaconing, you must connect to CR10XPB_1 to discover it.
PakBus Networking Guide When should PakBus be used? When adding to an existing system it may make sense to remain mixed-array, especially if your network must include non-PakBus dataloggers such as the 21X, CR7, etc., or if you rely on storage modules. However, communication equipment costs for PakBus systems are usually the same as for traditional communication and, although, like any other change, it takes some time and effort to learn the ins and outs of PakBus networking, the advantages are many.
PakBus Networking Guide NOTE PakBusPort is not an actual device, rather, it tells the LoggerNet server to use PakBus communication protocols with any device below it. • Configure the CR10XPB in the device map the same as the datalogger’s PakBus Address. • When you Connect to CR10XPB the connection works because CR10XPB is in LoggerNet’s device map which constitutes a “static route” to CR10XPB.
PakBus Networking Guide • The PC's RF400 needs its own 12 VDC supply. • This network behaves the same as the ‘minimum network’. • You can install a Neighbor Filter in CR10XPB making it a ROUTER and add CR205s to the network. By so doing you would end up with the Quick Start network described in Section 2 of this guide. 3.1.
PakBus Networking Guide • CSDC and SDC All PakBus dataloggers support CSDC (concurrent synchronous device communications). The CR10KD and COM310 can be used with PakBus dataloggers. Older SDC devices, such as the COM300, are not PakBus compatible. • RS-232 The CR23X with PakBus OS supports PakBus communications on its RS232 port. It can connect directly with the NL100. The CR200 series (some with built in radio) have an RS-232 port for direct connection to a COM port or NL100.
PakBus Networking Guide • RF400 Series or other transparent communications devices such as spread spectrum radios produced by Freewave Technologies, Inc. 3.2 Approaches to Network Configuration PakBus routing and buffering capabilities make possible multiple network topologies. For example, if an RF400 is used to communicate with a datalogger, which in turn communicates (through the same RF400) with more distant dataloggers, there are at least three basic ways to configure the network.
PakBus Networking Guide APPROACH 1 separate data files (CR205s) Remote Datalogger Router Remote (CR510, 10X, 23X PB) Remote (RF400s) APPROACH 2 highest throughput Remote LoggerNet Central Datalogger Data Collection P190s Remote (CR510, 10X, 23X PB) (RF400s) Remote APPROACH 3 lowest remote power budgets Remote Wireless Network Remote Host Datalogger P193 (CR510, 10X, 23X PB) Remote (RF400s) FIGURE 13.
PakBus Networking Guide 3.2.1 LoggerNet Direct (Approach 1) LoggerNet communicates with each datalogger to collect historic data, resulting in separate files for each datalogger in the network. Each remote datalogger can have its own collection schedule. 3.2.2 P190 Datalogger (Approach 2) A datalogger plays the role of concentrator using P190 instructions to obtain data values from the remotes. It processes the data and puts it into its own final storage for LoggerNet to collect to one file.
PakBus Networking Guide • IP (Internet Protocol) NL100 default router Redwing cellular digital packet data (CDPD) • SAT HDR GOES • PDA (Palm Handheld Device) using CSI’s PConnect software 3.3.2 Don’t Support PakBus Communications • RF3xx radios/modems • MD9 • COM300 • Storage modules These can sometimes be used as a transparent link ahead of the PakBus network.
PakBus Networking Guide FIGURE 14.
PakBus Networking Guide 3.4 Beaconing vs. Neighbor Filter Hello Once you have chosen the collection approach and communication devices for your PakBus network, you need to provide a way for the PakBus devices to discover in-range devices. Some PakBus devices function as routers and, as such, are responsible to know the best route to every PakBus device in the network. The first step is for routers to discover their own neighbors. Next, they share their neighbor lists with all other routers in the network.
PakBus Networking Guide message back to the beaconing device. The beaconing device answers with a hello message to the CR200 Series device which returns a hello response message and they become neighbors. Discovery begins quickly for CR200 Series devices but it may take several beacons for all to be discovered depending on the quantity. 3.4.2 CR10X/CR510/CR23X PakBus Datalogger Since beacons are packets of data, the more devices that beacon, the more significant the overhead in the communications channel.
PakBus Networking Guide A2: Yes, whether or not CR10XPB is in LoggerNet’s device map provided LoggerNet’s PakBus Address is ≥ 4000. Q3: Will CR10XPB with no neighbor filter put a non-beaconing LN server in its neighbor list? A3: Yes and No. Not initially. There must be communications first. Yes, after you connect once to CR10XPB it will put LN in its neighbor list and keep it there until 2.5 × the CVI times out.
PakBus Networking Guide FIGURE 15.
PakBus Networking Guide FIGURE 16. Edlog PakBus Datalogger Setup If you don’t want to change a category, check the “Do not change current settings” box and when the program compiles in the datalogger, that area will remain the way it was. Be sure to save/compile the program after making the PakBus Settings changes before sending to the datalogger. Notes Zeroing a PakBus Settings “Communication Interval” will delete the selected port when the program is compiled and sent to the datalogger.
PakBus Networking Guide 4.1.2.1 *D15 Set PakBus Address and Create Routing Table Set PakBus Address 15:xxxx (1 to 4093, default = 1, be careful with numbers > 3999 (see Neighbor Filter section)). NOTE If you make 01, 02, 03 values too small, you may not be able to connect to all network nodes. Configure Routing Table CAUTION 01 :xxxx Maximum nodes in PakBus network (enter 0 if a leaf node, non-zero if a router). 02 :xxxx Maximum neighbors to this PakBus Address (Maximum nodes must be non-zero).
PakBus Networking Guide For example - the Quick Start network in Section 1: Number of nodes = 4 (LoggerNet is one node) CR10XPB memory usage = 64 bytes Number of neighbors to the CR10XPB router = 3CR10XPB memory usage = 24 bytes Number of routers = 2 (counting LoggerNet) CR10XPB memory usage = 4 bytes 4.1.2.
PakBus Networking Guide 4.1.2.3 *D18 Set Beacon Interval and Port Protocol 01 :xxxx Enter interval (seconds) for CSDC 7 02 :xxxx Enter interval (seconds) for CSDC 8 03 :xxxx Enter interval (seconds) for Pin Enabled, 9600 baud (required for “9600” NL100 PakBus connection) 04 :xxxx Enter interval (seconds) for RS-232 port, 9600 baud (CR23X only) A value of “0” produces no beacons.
PakBus Networking Guide Notes If you have already set up the *D15 Router Table, as soon as you compile neighbor filter settings the datalogger starts sending hello messages. The potential neighbors soon appear in the *D17 Routing Table, enabling the datalogger to communicate with those devices (now neighbors) and, possibly, use them as routers.
PakBus Networking Guide • Type yyy A (1st address) • Type nn A (swath of nn addresses) • Type *0 to save *D19 settings The datalogger will now attempt to do hello exchanges with the PakBus Addresses you put in the potential neighbor list.
PakBus Networking Guide 4.2 LoggerNet PakBus Setup 4.2.1 PakBusPort A PakBus port must be set up in the device map prior to adding a PakBus datalogger. In order to communicate to a datalogger via another datalogger from LoggerNet's Connect window (i.e., communicating with a CR205 via a CR10XPB) the datalogger through which you will be communicating must be set up as a router. This is done by entering the number of remote dataloggers to which the router will be connecting in *D15, parameter 2. 4.2.
PakBus Networking Guide 5.1.2 Addresses All PakBus network RF400 Series should be configured with the same Network Address and Radio Address. PakBus devices that are in-range ‘hear’ every packet transferred, but they only respond to the packets addressed to them. Default addresses usually work. If you are in a busy RF400 area, you can reduce retries by choosing non-default Network and Radio Addresses. 5.1.
PakBus Networking Guide RS-232 port is connected directly to an RF400 Series communicating with CR200 Series remotes (see Appendix B). Alternatively, the NL100 can be configured as a PakBus device with a PakBus Address and beacons enabled: FIGURE 17. NL100 Configured as PakBus Device In the above example, both the NL100’s CSI/O port and RS-232 port are configured for “PakBus” mode. 5.3.1 CS I/O and RS-232 Can be “TcpSer” for transparent operation or “PakBus” (see figure above) to create a PakBus device.
PakBus Networking Guide 6.1.1 P190 – Send or Get Input Locations Purpose: To send or get Input Location data from a non-CRBasic datalogger in a PakBus network. Best for large networks in terms of getting data from many remotes the most quickly since the P190 can execute as fast as responses allow. P190 can also act as a Modbus master and issue commands to Modbus devices.
PakBus Networking Guide then the CR205 becomes a neighbor to the datalogger which it then advertises to network routers including LoggerNet. A P190 addressed device doesn’t have to be a neighbor to the datalogger. The route to the address specified in P190 can be through a neighbor router. If a default router is configured in *D15, the datalogger will send the packet to that node rather than assuming that the P190 Parameter 2 address is a neighbor.
PakBus Networking Guide Example: 9: PakBus - Wireless Network Master (P193) 1: 10 Number of Remotes 2: 1 First Remote Address ; 1st CR205 "Datalogger Address" 3: 0 Time Into Transmit Interval (sec) 4: 60 Transmit Interval (sec, 0 = use execution interval) 5: 3 Transmit Delay Between Remotes (sec) 6: 4 Swath to Receive ; Number of data values each CR205 7: 11 First Loc for Data Received [ DataRcvd_1 ] 8: 5 Swath to Send 9: 21 First Loc to Send [ HostBattr_1 ] 10: 3 Result Code Loc [ Response ] ; RCV’d, -1 =
PakBus Networking Guide Example: 4: PakBus - Seconds Until Transmit (P194) 1: 0003 Input Loc with Seconds Until P196 Transmit [ ____ ] If the host has not been heard (using P193), then the Time Until Transmit is set at a random time slot within a 1 minute interval. 6.1.5 P195 – Set Clock from Address Purpose: Sets local datalogger’s clock from a remote datalogger’s clock after the remote datalogger executes a P192 to send a Clock Report.
PakBus Networking Guide The master’s P193 automatically handles clock synchronization with the P196 remote. 6.1.7 P197 – Force Route through Address Purpose: To enter a PakBus Address into a datalogger’s routing table forcing the first hop where user wants to avoid using the auto-routing broadcast. Example: 7: PakBus - Force Route (P197) 1: 17 Local DL Port 2: 0005 Neighbor (Address of first hop) 3: 0010 Destination PakBus Address (same as neighbor if only one hop) 4: 01 Hops to Destination Node 6.1.
PakBus Networking Guide Result Codes: 1. 2. 3. 4. 5. –1001 –1002 –1003 0 >1 Attempted setting is read only Out of space in the remote Syntax error Success Number of communication failures 6.1.9 P199 - Routing Table to Input Locations Purpose: Used for trouble-shooting; instruction stores the datalogger’s routing table in Input Locations.
PakBus Networking Guide 6.2 CRBasic PakBus Dataloggers The CR205 is a CRBasic programmed, PakBus compatible datalogger. Soon to come is CSI’s full featured, CRBasic programmed, PakBus datalogger - the CR1000. 6.2.1 SendGetData Purpose The SendGetData instruction is used in remote CR200 Series dataloggers to send an array of values to the host datalogger, and/or retrieve an array of data from the host datalogger.
PakBus Networking Guide • GetData The GetData parameter is the variable or variable array in which the array of data from the Host datalogger will be stored. If a 0 is entered, no values will be stored. • SendData The SendData parameter is the variable or variable array that will be transmitted to the host datalogger. If a 0 is entered, no data will be transmitted.
PakBus Networking Guide Remarks The TimeUntilTransmit value is derived from the time slot information that is sent by the host datalogger. If the host datalogger has not yet sent time slot information, this instruction will use a random time interval between 0 and 60 seconds until communications with the host is established. Parameter • Port The Port parameter is used to specify the CR200 Series com port that will be used for communications. Enter a numeric code: Code 1 2 Description RF RS232 7.
PakBus Networking Guide 7.1.3 Leaf Node A leaf node is a PakBus Device that cannot route packets. It can send and receive packets only. The CR205 is always a leaf node. By default, the CR10XPB, CR510PB and CR23XPB are configured as a leaf node (not set up in *D15 as a router to forward packets toward other devices). 7.2 Packets In a PakBus network, all communications take place via packet transfer.
PakBus Networking Guide 7.2.1 Packet Types PakCtrl Packets (Protocol 0) Command Response Function 02 82 Clock Message 03 83 Echo 07 87 Read Device Settings 08 88 Write Device Settings 09 89 Hello 0a 8a Send Neighbor List 0b 8b Get Neighbor List 0c --Reset Router 0d --Goodbye 81 --Delivery Failure Message Note: the beacon has no defined packet type.
PakBus Networking Guide BMP5 Example Packet – XTD Clock Check/Set Command and Response 09:24:40.105 09:24:40.105 09:24:40.137 09:24:40.152 T T R R bd 5e bd 58 a0 01 6f fe 10 01 0f fe 03 2e 00 00 00 00 d2 bd af fe 10 01 1f fe 00 01 83 2e 00 27 5b 2a 99 c0 00 d1 77 bd ...o............ ^. ............'[*. X...w. Note: 9th digit and packet type are underlined 7.2.3 Packet Protocol Levels Notice that some packet numbers are shared between protocols.
PakBus Networking Guide 7.2.4.2 Two Level Packet Addressing Examination of a packet header reveals four PakBus Addresses. Referring to the above BMP5 Example Packet (portrayed below) hex digits 2 – 4 (“001”) represent the neighbor PakBus Address to which the packet is going. Digits 6 – 8 represent the neighbor PakBus Address from which the packet came (“ffe”).
PakBus Networking Guide removed from its neighbor list. The same removal procedure will happen in the other device. When a network route’s neighbor list changes (either neighbor added or neighbor removed), it then shares that information with other routers. This behavior fundamentally drives the network routing process. A device with a neighbor always has an associated communications verification interval. If a device has several neighbors, each link has a separate communications verification interval.
PakBus Networking Guide filter which must describe all potential neighbors, but beacon traffic can be reduced or eliminated so long as neighbor communications are usually successful. The P193 instruction does not initiate communications so it cannot be relied upon to discover neighbors.
PakBus Networking Guide Once nodes establish themselves as neighbors, if a node does not hear from the other (either by beacon or by addressed communication) within the communications verification interval established in the hello exchange × 2.5, then that node will issue a hello message (up to 4 times if unsuccessful) and delete that node from its neighbor list if the hello message is not answered.
PakBus Networking Guide The advantage of Neighbor Filter over beaconing is that you avoid generating the periodic rf activity, and the possibility of rf collisions so long as there is some kind of communications within the interval you set, such as a scheduled data collection. More importantly, a neighbor filter avoids selecting marginal rf routes.
PakBus Networking Guide 01: 0003 01: 0003 PakBus Address of destination node via neighbor with PakBus Address (this line not present if destination is a neighbor) 01: 1.0000 maximum response time in seconds 7.4.3 Communications Verification Interval (CVI) A PakBus device with neighbor filter verifies its neighbors by sending each of them a hello message according to the programmed communications verification interval. If a device in its neighbor list does not communicate for a period of time equal to 2.
PakBus Networking Guide 7.4.4.2 Manual To manually reset a device’s neighbor list, you can send a program to a datalogger with the desired potential neighbor list in the program (see Edlog PakBus Settings section of this guide). 7.4.5 Hello Exchange A Hello Exchange is the way two devices are established as neighbors. When a network device beacons, any non-neighbor CRxxxPB device within range responds after a random delay of 1 to 4 seconds by sending a hello command (09) packet to the beaconing device.
PakBus Networking Guide Example 2 – LoggerNet (ffe) is beaconing and CR205 (003) is nearby: LoggerNet broadcast beacon: 15:37:21.665 T bd bd bd bd bd bd bd 8f ff 8f fe 0f ff 0f fe e6 60 bd CR205 responds with hello request (0e) message: 15:37:21.800 R bd af fe 00 03 0f fe 00 03 0e e6 60 bd LoggerNet sends CR205 hello (09) message: 15:37:22.133 T bd a0 03 7f fe 00 03 0f fe 09 2a 01 03 00 1e f1 5b bd CR205 sends hello response (89) to LoggerNet: 15:37:22.
PakBus Networking Guide 7.4.8 Broadcast Packets The most common use of broadcast packets by a PakBus device is to send beacons for link discovery and verification. The interval at which these messages are sent is controlled by a beacon interval setting that is port specific (the server has a similar setting for its PakBusPort device type). When beacons are sent they are generally sent as an empty message with a high protocol code of type PakCtrl.
PakBus Networking Guide 7.5 Router A router is a PakBus device which can accept a packet and forward it toward its network destination. Network routing is fundamentally driven by a router learning who its neighbors are and then sharing that information with other routers in the network. Send Neighbor List and Get Neighbor List packets are used to accomplish the sharing.
PakBus Networking Guide its command/setup interface. The "t" or "tables" command will report the NL100’s current routing tables. Every router (including LoggerNet) sends around its neighbor list to every other router. Routers construct their Routing Tables using their own neighbor list and the neighbor lists (all with hop metrics) received from the other routers in the network. A device will be removed from another device’s neighbor list (and routing table) if a hello exchange fails after 4 attempts.
PakBus Networking Guide 7.5.3 Forced Routing 7.5.3.1 Tree vs. Flat Device Map If you build the device map with the remote PakBus devices as children of the ‘base’ router you have a ‘flat’ device map configuration. Un-represented RF400 Series are assumed here with all hop sequences, network addresses, radio addresses, and standby modes (normally “< 24 mA always on) configured the same. FIGURE 19.
PakBus Networking Guide If there is no beaconing in the network, LoggerNet can connect to CR10XPB_1 because it is in LoggerNet’s static routes. If CR10XPB_1 does not have CR205_2 in its neighbor list, LoggerNet’s routing algorithm cannot route toward CR205_2. By adding CR205_2 to CR10XPB_1’s neighbor filter potential neighbor list, you essentially force that route to CR205_2. If LoggerNet were beaconing, it could discover CR205_2 directly (sometimes creating an undesirable, weak rf link).
PakBus Networking Guide long, direct path weak rf link CR10XPB (P190 to address 30) CR205 RF400 Series ROUTER CR510PB PakBus Address = 30 PakBus Address = 10 RF400 Series strong rf link Neighbor Filter Potential Neighbor: 20 PakBus Address = 20 strong rf link Neighbor Filter Potential Neighbors: 30 10 FIGURE 21. Neighbor Filter Force a Path through Router 7.
PakBus Networking Guide 7.7 CR200 Series 7.7.1 Beaconing, Neighbor List and Comms Verification Interval In this section the term “CR205” includes the CR215, both having internal radios, and the CR200 in some networks. The CR205’s neighbor ‘list’ will accept only one device. If a CR205 has no device in its neighbor list it will respond to a beacon after a random 0 to 1 second delay by sending a hellorequest message to the beaconer.
PakBus Networking Guide Possible reason 3 No PakBusPort in device map between root and datalogger. Remedy 3 Add PakBusPort. Possible reason 4 No PakBus OS in datalogger Remedy 4 If you have two in-range routers using neighbor filters, in order for them to discover one another you must list each of them as a potential neighbor in the other’s neighbor filter. 8.2 LoggerNet can’t communicate via datalogger-router to a certain remote datalogger.
PakBus Networking Guide Remedy 3 Set all network radios exactly the same in the above parameters. Network RF400s’ Active Interfaces may vary from node to node, however, they will typically be configured for CSDC 7 or 8 except for a ‘base’ radio which is typically AutoSense or M.E..
PakBus Networking Guide 8.5 Rapid spurious communications lasting a few seconds at a time between devices in RF400 network. Possible reason Two network devices have the same PakBus Address. Remedy Change one of the duplicate PakBus Addresses. Make all addresses unique throughout the network. 8.6 In P193 network, certain CR200 Series devices don’t transfer data. Possible reason The Master datalogger’s *D15 setting configures too few max nodes, max neighbors, and max routers.
Appendix A. Glossary of PakBus Terms Active Interface An RF400 Series’ or MD485’s selected com port. It could be SDC, CSDC 7, CSDC 8, Modem Enabled, or RS-232. Beacon A broadcast packet intended to discover in-range neighbor PakBus devices. Devices that receive a beacon answer by initiating a hello-exchange with the beaconing device if not already neighbors. A device with neighbor filter will ignore beacons from addresses not in their potential neighbor list unless the beacon address is ≥ 4000.
Appendix A. Glossary of PakBus Terms A-2 CVI Abbreviation for Communications Verification Interval. Directed Packet A relative term; from the vantagepoint of a particular PakBus device, a directed packet is a packet that is addressed to the particular PakBus device. It is also referred to as “addressed communications.” Dynamic Link A learned route, distinguished by the fact that the PakBus device addresses exist in one another’s neighbor lists.
Appendix A. Glossary of PakBus Terms Hopping Sequence Also called Hop Sequence or Hop Table, this refers to a particular pattern the spread spectrum radio uses to ‘hop’ among its assigned frequencies. In a PakBus network all RF400s must have the same hopping sequence. Leaf Node A PakBus device which cannot serve as a router, although it can send or receive packets. Link A viable communication path between two PakBus devices. Link State Network level: offline, ring, ready, finished, or pause status.
Appendix A. Glossary of PakBus Terms A-4 Packet A frame, typically 1000 bytes or less, containing a header and data that is transferred over a packetswitching network. Packets transfer information between LoggerNet and PakBus dataloggers usually via routers. P19x PakBus instructions for non-CRBasic PakBus capable dataloggers such as the CR10X. For example, the P193 instruction is used for master/slave communications with a group of remote CR200 Series wireless sensors.
Appendix A. Glossary of PakBus Terms Potential Neighbor List A list of possible neighbors installed in a datalogger’s neighbor filter using *D19, PakBusGraph \ Show Settings, or Edlog \ Options \ PakBus Settings. Protocol An agreed-upon format for transmitting data between two devices.
Appendix A. Glossary of PakBus Terms A-6 Standby Mode RF400’s or CR200 Series’ low power budget mode. Adjustable in 7 ranges from ‘always on’ to listening briefly once every 8 seconds (0 to 7). The RF400 default is “<4 mA ½ sec cycle.” Static Route Route that exists by virtue of a LoggerNet Setup device map or a P19x instruction. Switched Packet Network A network where packets are transferred, not by transparent links, but by intermediate routers.
Appendix B. NL100 TcpServer to RF400 to CR510PB-Router/RF400 to 20 CR205s Network LoggerNet does 60 minute scheduled collections from remote CR205s via NL100 configured as TcpServer and a CR510PB router using RF400 for communications. The CR510 router extends the range from NL100 to CR205s. Additional CR510PB/RF400 ‘repeaters’/routers can be added to extend any branch in the network, for example, to get over a hill to some of the CR205s. The NL100 is transparent in this mode (it has no PakBus address).
Appendix B. NL100 TcpServer to RF400 to CR510PB-Router/RF400 to 20 CR205s Network LoggerNet Schedule Tab Collection Interval – 60 minutes Primary Retry Intervals – 20 minutes Number of Primary Retries – 2 Secondary Retry Interval – 240 minutes NL100 Configuration Menu Settings (Any NL100 options not shown above are disabled). A PakBus Address is required by setup even though not used.
Appendix B. NL100 TcpServer to RF400 to CR510PB-Router/RF400 to 20 CR205s Network CR205 Settings 1. Configure all CR205s with the same Radio Address, Net Address, and Hopping Sequence using the same settings as the RF400s have. 2. Configure each CR205 with a unique PakBus address (“Datalogger Address” in PakCom) starting with “1” and ending with “20.” 3. Configure Radio Power Mode = RF_ON 4.
Appendix B. NL100 TcpServer to RF400 to CR510PB-Router/RF400 to 20 CR205s Network Be sure to OK the PakBus settings and save/compile the program in Edlog before sending it to the CR510PB. When you send the program to the CR510PB the above settings should be visible in *D15 and *D19. After the CR205 has had a few minutes to discover its CR205 neighbors, you can view them in the *D17 Routing Table. The server should also show up as a neighbor to the CR510PB.
Appendix C. NL100 TcpServer to RF400-Router to 20 CR205s Network In this configuration LoggerNet does 60 minute scheduled collections from remote CR205s via NL100 configured as TcpServer and an RF400 for communications. In this configuration, the CR205s have to be relatively close to the NL100. The network configuration described in Appendix B shows how to extend range with a ‘repeater’/router. Notice that the LoggerNet, NL100, RF400 and CR205 setups are the same as in Appendix B.
Appendix C. NL100 TcpServer to RF400-Router to 20 CR205s Network NL100 Configuration Menu Settings (Any NL100 options not shown above are disabled). A PakBus Address is required by setup even though not used. RF400 Settings In a PakBus rf network all radios must have the same radio and network addresses and hopping sequence setting. Addressing is accomplished using the unique PakBus addresses assigned to the PakBus devices (dataloggers). 1.
Appendix C. NL100 TcpServer to RF400-Router to 20 CR205s Network 3. Configure Radio Power Mode = RF_ON 4.
Appendix C. NL100 TcpServer to RF400-Router to 20 CR205s Network This is a blank page.
Appendix D. COM210 to CR510PBRouter to 10 CR205s Network In this configuration LoggerNet does 15 minute scheduled collections from remote CR205s via COM210 dialed link and a CR510PB configured as router.
Appendix D. COM210 to CR510PB-Router to 10 CR205s Network CR205 Settings D-2 1. Configure all CR205s with the same Radio Address, Net Address, and Hopping Sequence using the same settings as the RF400 has. 2. Configure each CR205 with a unique PakBus address (“Datalogger Address” in PakCom) starting with “1” and ending with “10.” 3.
Appendix E. CR510PB w/ P190s to CR205s Network In this configuration LoggerNet does 15 minute scheduled collections of a remote CR510XPB running P190s to transfer variable values from 5 remote CR205s. This approach results in the fastest data transfer compared to P193 and LoggerNet direct collection of CR205s. The P190 instruction which has the CR205’s address does device discovery in this configuration. One P190 is required for each remote.
Appendix E. CR510PB w/ P190s to CR205s Network LoggerNet Device Map ComPort_1 PhoneBase PhoneRemote PakBusPort CR510PB (PakBus Address = 100) CR200_1 (PakBus Address = 1) CR200_2 (PakBus Address = 2) CR200_3 (PakBus Address = 3) CR200_4 (PakBus Address = 4) CR200_5 (PakBus Address = 5) After once dialing up and connecting in LoggerNet, PakBusGraph will display the CR510PB and all its CR205 neighbors.
Appendix E. CR510PB w/ P190s to CR205s Network 4. In LoggerNet CRBasic key in the following program for the CR205s: Public AirTemp_C Public RF_Strength DataTable (AirTemp,1,1000) DataInterval (0,1,min) Average (1,AirTemp_C,0) EndTable BeginProg Scan(10,sec) 'Make Measurements Therm109 (AirTemp_C,1,1,Ex1,1.0,0) RF_Strength=(Status.rfsignallevel(1,1)) ‘ Indicates CR205’s relative received signal strength (RSSI) CallTable AirTemp NextScan EndProg 5. Save it as TEMP_PROBE.dld and compile it. 6.
Appendix E.
Appendix E.
Appendix E. CR510PB w/ P190s to CR205s Network 17: Extended Parameters 4 Digit (P68) 1: 82 Option 2: 70 Option 3: 95 Option 4: 83 Option 5: 116 Option 6: 114 Option 7: 101 Option 8: 110 Option 18: Extended Parameters 4 Digit (P68) 1: 103 Option 2: 116 Option 3: 104 Option 4: 0000 Option 5: 0000 Option 6: 0000 Option 7: 0000 Option 8: 0000 Option ;R ;F ;_ ;S ;t ;r ;e ;n ;g ;t ;h ; *Table 2 Program 02: 0.0000 Execution Interval (seconds) *Table 3 Subroutines End Program 2.
Appendix E. CR510PB w/ P190s to CR205s Network 4. Configure a CR510PB PakBus address of “100” like this inEdlog’s Options\Pakbus Settings: FIGURE E-2. P190 Edlog PakBus Settings Configuring the maximum nodes, maximum neighbors, and maximum routers allows the CR510PB to function as a router in the network. Notice that “Network” is the only setup group unchecked. There is no need of Neighbor Filter or Beacon setup because the P190 instruction creates a static route to each CR205 in the swath. 5.
Appendix E. CR510PB w/ P190s to CR205s Network FIGURE E-3. P190 Numeric Display If P190 communication is failing, the StatusOfGetx will increment every scan of the CR205. If zero, communication is successful.
Appendix F. CR510PB w/ P193 Master to CR205s Network In this configuration LoggerNet does 15 minute scheduled collections of a remote CR510PB running a P193 to transfer variable values from 5 remote CR205s (may be other rf CR200 Series). This approach results in the lowest remote average current drain because the remotes originate the data transfer and their RF400 Series radios are off the rest of the time. The P193 instruction has all the CR205s’ addresses and does device discovery.
Appendix F.
Appendix F. CR510PB w/ P193 Master to CR205s Network Standby Mode = “< 24 mA always on” (other modes work in some situations if other network radios are the same). CR205 Settings and Program 1. Configure all CR205s with the same radio address, network address, and hopping sequence using the same settings as the RF400 has. 2. Configure each CR205 with a unique PakBus address (“Datalogger Address” in PakCom) starting with address “1” and ending with address “5.” 3.
Appendix F. CR510PB w/ P193 Master to CR205s Network SendGetData (HostResponse,host(),Remote(),1,100,100,0) 'Host response of 0 = success Endif CallTable(Table1) NextScan EndProg 5. Save the program as WIRELESS.CR2 and compile it. 6. Using PakCom (or LoggerNet), send WIRELESS.bin to each CR205 in network. 7. Connect power supply and antenna to each CR205. CR510PB Settings and Program 1.
Appendix F.
Appendix F. CR510PB w/ P193 Master to CR205s Network from SE1 to and the 10KΩ resistor from EX1 to SE1. The result will be a simulated temperature reading of 22°C ± 2 degrees. 2. Configure a CR510PB PakBus address of “100” in Edlog’s Options\Pakbus Settings: FIGURE F-2. P193 Edlog PakBus Settings The maximum nodes, maximum neighbors, and maximum routers entries allow the CR510PB to function as a router in the network. Notice that “Network” is the only setup group unchecked.
Appendix F. CR510PB w/ P193 Master to CR205s Network FIGURE F-3. P193 Numeric Display Remote2 and Remote4 are missing in the above network, hence the “0.00” values and incrementing ResultCodes. When the CR510PB receives a wireless message from a remote, the corresponding Result Code Location is set to -1. When Instruction 193 is executed, the Result Code Location is incremented by 1. Therefore, if communication is successful, the Result Code Location will be 0 after the execution of Instruction 193.
Appendix F. CR510PB w/ P193 Master to CR205s Network This is a blank page.
Appendix G. Phone to CR205s Network In this configuration LoggerNet does direct 15 minute scheduled collections of 5 remote CR205s (may be other rf CR200 Series). This approach results in the greatest number of files collected from the remotes (as compared to the P190 or P193 approach). There is no beaconing in this configuration. LoggerNet needs no beacon as it can discover CR205s using the static routes created by the device map.
Appendix G. Phone to CR205s Network LoggerNet Schedule Tab Collection Interval – 15 minutes Primary Retry Intervals – 5 minutes Number of Primary Retries – 2 Secondary Retry Interval – 60 minutes RF400 Settings In a PakBus rf network, all RF400 Series radios are set up the same, except, possibly, the com ports. 1. Configure RF400 radio with the same network address, radio address, and hopping sequence as the CR205s.
Appendix G. Phone to CR205s Network DataTable(Table1,1,-1) DataInterval(0,1,min) Sample(1,Batt_Volt) Sample(1,Therm_C) Sample(1,Therm_F) EndTable BeginProg Scan(1,sec) Therm109 (Thermister_C,1,1,Ex1,1.0,0) Therm_C = Thermister_C Therm_F = Therm_C*9/5 +32 Battery(Batt_Volt) TimeUntilTx = TimeUntilTransmit(1) If TimeUntilTx = 0 Then SendGetData (HostResponse,host(),Remote(),1,100,100,0) 'Host response of 0 = success Endif CallTable(Table1) NextScan EndProg 5. Save the program as WIRELESS.dld and compile it.
Appendix G. Phone to CR205s Network This is a blank page.
Appendix H. Adding Direct or P190 Router to RF400 Network If you have two locations that cannot be dependably rf linked using high gain antennas, tall tripods/towers or by optimizing antenna locations, sometimes adding a router is the best solution. The following shows how to add a router to an existing rf network using neighbor filter discovery. For this router you will need: 1. 2. 3. 4. 5. 6. 7. 8. CR510 with PakBus OS RF400 PS12LA or equivalent 12 VDC power supply 9591 18V/1.
Appendix H. Adding Direct or P190 Router to RF400 Network Antenna Height and Location • Arrange the router antenna’s height and/or position so that it has a good ‘view’ of the antennas of both the ‘toward LoggerNet’ and the ‘toward destination’ stations (height is everything in rf links).
Appendix H. Adding Direct or P190 Router to RF400 Network Router RF400 Configuration • Configure the RF400s’ Active Interfaces to CSDC 7 (defaults to 7). • Configure the RF400’s Standby Mode to the Standby Mode setting that CR10XPB_1’s RF400 and the CR205s use. • Configure CR510PB_2’s RF400 net address, radio address, and hopping sequence the same as the network’s.
Appendix H. Adding Direct or P190 Router to RF400 Network This is a blank page.
Appendix P. PakBusGraph PakBusGraph is a LoggerNet server client that allows a graphic view of a PakBus network from LoggerNet’s perspective. This is a way to view LoggerNet’s routing table. PakBusGraph also allows settings to be changed in nodes across the network, and it provides functions such as LoggerNet router reset and broadcast reset. NOTE PakBusGraph is prototype software. If you own LoggerNet and desire a copy of PakBusGraph, please contact an application engineer for assistance.
Appendix P. PakBusGraph In this example, a CR10XPB PakBus node was selected. Show Settings Displays: FIGURE P-2. Show Settings PakBusAddress – Datalogger’s own PakBus Address = 100 Hello17 (CSDC 7 Port) – Active with *D19 configured for 60 second communications verification interval; Potential Neighbors are PakBus device address 3 (swath of 1), and PakBus devices addresses 5 and 6 (5, swath of 2). Hello18 (CSDC 8 Port) – not selected Hello2 (M.E.
Appendix P. PakBusGraph PakCtrlCodes – shows the low level packet types supported BMP5 Codes – shows the application level codes supported Max Packet Size – advertises the max packet size this device can receive Reset Router Allows you to reset the Routing Table and Neighbor List of the selected PakBus Device so that it must re-learn its neighbors (by beacons, hello messages, P190, P191, P192, P196, P198, P224 or static routes).
Appendix P. PakBusGraph Neighbor Filter: If one of a neighbor filter’s listed potential neighbors happens to fail, neighbor filter hello-ing will occur at random 1 to 15 second intervals until either the failed device is removed as a potential neighbor or communications is restored. Removal can be done from LoggerNet using PakBusGraph. You can edit a node’s neighbor filter by using PakBusGraph\Show Settings to edit the neighbor filter settings.
Appendix Q. Log View NOTE Log View is prototype software. If you own LoggerNet and desire a copy of Log View, please contact an application engineer for assistance. LogView is a non-client software tool designed to interpret PakBus packets. Using the Low Level logs generated by the LoggerNet server (logs enabled in Status Monitor), you can view packet decoding to help you determine what is happening in the network. The logs are typically found in C:\Campbellsci\LoggerNet\Logs.
Appendix Q. Log View Protocol BMP refers to BMP5 packet protocol for PakBus. The “(1)”also refers to the BMP type of packet. No protocol listed indicates the low-level (PakCtrl) protocol used for functions such as helloing, and neighbor list sharing. Expect More 0 = last data in this direction 1 = more data to come in this direction 2 = neutral 3 = expect more in reverse direction Message Type The packet type. For example, XTD Clock Check/Set Response or Hello Command.
Appendix Q. Log View Hop Count Indicates how many routers the packet passes through from source to destination. Priority Indicates a packet’s importance from 0 to 3. 3 indicates highest priority. Transaction Number Indicates a server serialized transaction number. This number follows a packet through to the destination and appears in response packets. For example a hello command packet might have transaction number 58. The hello response packet would also indicate a transaction number of 58.
Appendix Q. Log View This is a blank page.
This is a blank page.
Campbell Scientific Companies Campbell Scientific, Inc. (CSI) 815 West 1800 North Logan, Utah 84321 UNITED STATES www.campbellsci.com info@campbellsci.com Campbell Scientific Africa Pty. Ltd. (CSAf) PO Box 2450 Somerset West 7129 SOUTH AFRICA www.csafrica.co.za sales@csafrica.co.za Campbell Scientific Australia Pty. Ltd. (CSA) PO Box 444 Thuringowa Central QLD 4812 AUSTRALIA www.campbellsci.com.au info@campbellsci.com.au Campbell Scientific do Brazil Ltda.
