Campbell Scientific CR6 CR6 Measurement and Control System - Page 394

Initiating Telecommunications Callback

Page 394 highlights

Section 8. Operation • 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.4.3 Initiating Telecommunications (Callback) Telecommunication sessions are usually initiated by a PC. Once telecommunication is 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 telecommunication networks are installed. Typically, the PC initiates telecommunications with the CR6 with datalogger support software (p. 604). However, some applications require the CR6 to call back the PC (initiate telecommunications). This feature is called 'Callback'. Special features exclusive to LoggerNet (p. 604) 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 telecommunication hardware may discuss Callback options. Contact a Campbell Scientific application engineer for the latest information in Callback applications. Caution When using the ComME communication port with non-PakBus® protocols, incoming characters can be corrupted by concurrent use of the CS I/O for SDC communication. PakBus® communication uses a low level protocol of a pause / finish / ready sequence to stop incoming data while SDC occurs. Non-PakBus® communication includes PPP protocol, ModBus, DNP3, and generic, CRBasic-driven use of CS I/O. Though usually unnoticed, a short burst of SDC communication 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 SDC activity is the datalogger querying the SDC to see if the external keyboard display is available. When DevConfig and PakBus Graph retrieve settings, the CR6 queries 394

  • 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
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392
  • 393
  • 394
  • 395
  • 396
  • 397
  • 398
  • 399
  • 400
  • 401
  • 402
  • 403
  • 404
  • 405
  • 406
  • 407
  • 408
  • 409
  • 410
  • 411
  • 412
  • 413
  • 414
  • 415
  • 416
  • 417
  • 418
  • 419
  • 420
  • 421
  • 422
  • 423
  • 424
  • 425
  • 426
  • 427
  • 428
  • 429
  • 430
  • 431
  • 432
  • 433
  • 434
  • 435
  • 436
  • 437
  • 438
  • 439
  • 440
  • 441
  • 442
  • 443
  • 444
  • 445
  • 446
  • 447
  • 448
  • 449
  • 450
  • 451
  • 452
  • 453
  • 454
  • 455
  • 456
  • 457
  • 458
  • 459
  • 460
  • 461
  • 462
  • 463
  • 464
  • 465
  • 466
  • 467
  • 468
  • 469
  • 470
  • 471
  • 472
  • 473
  • 474
  • 475
  • 476
  • 477
  • 478
  • 479
  • 480
  • 481
  • 482
  • 483
  • 484
  • 485
  • 486
  • 487
  • 488
  • 489
  • 490
  • 491
  • 492
  • 493
  • 494
  • 495
  • 496
  • 497
  • 498
  • 499
  • 500
  • 501
  • 502
  • 503
  • 504
  • 505
  • 506
  • 507
  • 508
  • 509
  • 510
  • 511
  • 512
  • 513
  • 514
  • 515
  • 516
  • 517
  • 518
  • 519
  • 520
  • 521
  • 522
  • 523
  • 524
  • 525
  • 526
  • 527
  • 528
  • 529
  • 530
  • 531
  • 532
  • 533
  • 534
  • 535
  • 536
  • 537
  • 538
  • 539
  • 540
  • 541
  • 542
  • 543
  • 544
  • 545
  • 546
  • 547
  • 548
  • 549
  • 550
  • 551
  • 552
  • 553
  • 554
  • 555
  • 556
  • 557
  • 558
  • 559
  • 560
  • 561
  • 562
  • 563
  • 564
  • 565
  • 566
  • 567
  • 568
  • 569
  • 570
  • 571
  • 572
  • 573
  • 574
  • 575
  • 576
  • 577
  • 578
  • 579
  • 580
  • 581
  • 582
  • 583
  • 584
  • 585
  • 586
  • 587
  • 588
  • 589
  • 590
  • 591
  • 592
  • 593
  • 594
  • 595
  • 596
  • 597
  • 598
  • 599
  • 600
  • 601
  • 602
  • 603
  • 604
  • 605
  • 606
  • 607
  • 608
  • 609
  • 610
  • 611
  • 612
  • 613
  • 614
  • 615
  • 616
  • 617
  • 618
  • 619
  • 620
  • 621
  • 622
  • 623
  • 624
  • 625
  • 626

Section 8.
Operation
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.4.3
Initiating Telecommunications (Callback)
Telecommunication sessions are usually initiated by a PC.
Once
telecommunication is 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
telecommunication networks are installed.
Typically, the PC initiates telecommunications with the CR6 with
datalogger
support software
(p. 604).
However, some applications require the CR6 to call back
the PC (initiate telecommunications).
This feature is called 'Callback'.
Special
features exclusive to
LoggerNet
(p. 604)
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 telecommunication hardware may discuss Callback options. Contact a
Campbell Scientific application engineer for the latest information in Callback
applications.
Caution
When using the ComME communication port with non-PakBus®
protocols, incoming characters can be corrupted by concurrent use of the
CS I/O for SDC communication.
PakBus® communication uses a low
level protocol of a pause / finish / ready sequence to stop incoming data
while SDC occurs.
Non-PakBus
®
communication includes PPP protocol, ModBus, DNP3, and
generic, CRBasic-driven use of CS I/O.
Though usually unnoticed, a short burst of SDC communication 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
SDC activity is the datalogger querying the SDC to see if the external
keyboard display is available.
When
DevConfig
and
PakBus Graph
retrieve settings, the CR6 queries
394