Campbell::Comm - Revision history

127.0.0.1 at 21:31, 6 July 2007

2007-07-06T21:31:17Z

127.0.0.1 at 21:30, 6 July 2007

2007-07-06T21:30:32Z

127.0.0.1 at 20:32, 6 July 2007

2007-07-06T20:32:32Z

127.0.0.1 at 20:14, 6 July 2007

2007-07-06T20:14:53Z

127.0.0.1 at 20:13, 6 July 2007

2007-07-06T20:13:33Z

127.0.0.1 at 20:12, 6 July 2007

2007-07-06T20:12:31Z

127.0.0.1 at 19:20, 6 July 2007

2007-07-06T19:20:27Z

127.0.0.1 at 17:40, 6 July 2007

2007-07-06T17:40:43Z

127.0.0.1 at 17:15, 6 July 2007

2007-07-06T17:15:27Z

127.0.0.1 at 17:02, 6 July 2007

2007-07-06T17:02:01Z

← Older revision		Revision as of 21:31, 6 July 2007
Line 71:		Line 71:

	==querylogger.pl==		==querylogger.pl==
−	This perl script was written to exercise and test the Campbell::Comm	+	This perl script was written to exercise and test the Campbell::Comm
−	~~module, but may be useful in its own right as a way to interface with~~

@@ Line 32: / Line 32: @@
 ==Campbell/Comm.pm==
 This module becomes part of a Perl program via the '''use''' or '''require'''
@@ Line 72: / Line 73: @@
 This perl script was written to exercise and test the Campbell::Comm
 module, but may be useful in its own right as a way to interface with

← Older revision		Revision as of 20:32, 6 July 2007
Line 152:		Line 152:
	** append the log message to the site log file		** append the log message to the site log file

		+	In summary, the '''loggerdata.pl''' program:
		+
		+	* tries to download data from the last available location
		+	** all data retrieved is integrity-checked, then stored
		+	* checks (& maybe sets) the time
		+	* maybe downloads the datalogger's current program
		+
		+	In general, we make every attempt to ensure that data is downloaded as
		+	it exists on the datalogger, and safely stored on the data-gathering
		+	computer. Data is not skipped; in particular, if a remote site has "fallen
		+	behind", the program will patiently and persistently try to bring the
		+	local (on-computer) data store in line with the remote logger.
		+
		+	The datalogger's time setting is of particular importance mainly so that
		+	connection times can be kept ''in synch'', assuming that the radios are
		+	powered on only at certain times. Of course, another benefit in checking/setting
		+	the logger's time is that the stored data timestamps are meaningful in an
		+	absolute sense -- but note that this could also be achieved by only checking
		+	(and not setting) the time.

@@ Line 70: / Line 70: @@
 ==querylogger.pl==
 This perl script was written to exercise and test the Campbell::Comm
 module, but may be useful in its own right as a way to interface with
@@ Line 118: / Line 117: @@
 module.
-See below for the [[data site architecture]] assumed by the system.
+See below for the [[#data site architecture]] assumed by the system.
 Like [[#querylogger.pl]], '''loggerdata.pl''' runs in

@@ Line 120: / Line 120: @@
 See below for the [[data site architecture]] assumed by the system.
-Like [[#querylogger.pl]], or [#querylogger.pl], '''loggerdata.pl''' runs in
+Like [[#querylogger.pl]], '''loggerdata.pl''' runs in
 a non-interactive or ''batch'' mode.  But where the former program is
 driven according to the set of commands provided on the command line, the

← Older revision		Revision as of 20:12, 6 July 2007
Line 120:		Line 120:
	See below for the [[data site architecture]] assumed by the system.		See below for the [[data site architecture]] assumed by the system.

−	Like [[#querylogger.pl]],	+	Like [[#querylogger.pl]], or [#querylogger.pl], '''loggerdata.pl''' runs in
		+	a non-interactive or ''batch'' mode. But where the former program is
		+	driven according to the set of commands provided on the command line, the
		+	latter is hard-wired to follow a set sequence of commands.
		+
		+	As with any computer program, the details of what this program does are
		+	spelled out in its source code. The following steps are from memory, and
		+	should be confirmed...
		+
		+	* a connection is established to the datalogger
		+	* several ''escape characters'' are sent in case the datalogger has been left in an edit or other state
		+	* the datalogger command prompt, '''"*"''' is obtained
		+	* the "next data memory location" ('''DSP''') is retrieved from the site state on disk (not on the logger)
		+	* the datalogger's current data memory position ('''MPTR''') is obtained
		+	* the '''G''' logger telecommunications command is used to set the '''MPTR''' to the last '''DSP''' value
		+	* data is requested in either ASCII (the '''D''' command) or binary (the '''F''' command) mode
		+	* incoming data is integrity-checked using checksums or ''signatures''
		+	* confirmed-good data is stored on disk
		+	* update the stored '''DSP''' state information
		+	* repeat the above data query steps until:
		+	** the '''DSP''' value reaches the logger's '''MPTR'''
		+	** the query times out
		+	** the allowed processing time for the session elapses
		+	* query the datalogger's time
		+	** if the logger time is off by more than a specified amount (e.g., 10 seconds), set the time
		+	* if the logger program hasn't been downloaded for greater than a specified time (e.g., 10 days), download the program
		+	** store the logger program to a '''version control system''' (RCS)
		+	* query and store the datalogger ''flags'' settings
		+	* disconnect from the remote logger
		+	* compose a ''log message'' summarizing the session
		+	** print the log message if the session has been run by a user
		+	** append the log message to the site log file
		+
		+
		+
		+

← Older revision		Revision as of 19:20, 6 July 2007
Line 113:		Line 113:
	==loggerdata.pl==		==loggerdata.pl==

−	~~THIS IS A STUB~~ .... ~~NEEDS WORK!~~	+	The '''loggerdata.pl''' script is the workhorse of WERC's data
		+	gathering system from CR10X loggers, and besides the '''querylogger.pl'''
		+	script (see above) is the only script we've written around the Campbell::Comm
		+	module.
		+
		+	See below for the [[data site architecture]] assumed by the system.
		+
		+	Like [[#querylogger.pl]],
		+

@@ Line 23: / Line 23: @@
 License (GPL).
-Brief technical descriptions of the primary components follow...
+Technical descriptions of the primary components follow...
@@ Line 45: / Line 50: @@
 implemented in the (or various...) open() methods.
-A _bug_ in Net::Telnet (this is my view; it may be considered a _feature_
+A ''bug'' in Net::Telnet (this is my view; it may be considered a ''feature''
 by the authors...) requires a patch; this should be represented in the
 Net::Telnet version included in the above tree.  Specifically, Net::Telnet
@@ Line 60: / Line 65: @@
 Due to the specific need to communicate with dataloggers via FreeWave
-radios, the ...
+radios, the Campbell::Comm module was written with this capability perhaps

@@ Line 42: / Line 42: @@
 Besides the nominal TCP/IP connections, Net::Telnet is capable of supporting
-interfaces using a direct serial or modem connection
+interfaces using a direct serial or modem connection.  This usage is
-Most of WERC's research datalogging systems are
+A _bug_ in Net::Telnet (this is my view; it may be considered a _feature_

← Older revision		Revision as of 17:02, 6 July 2007
Line 16:		Line 16:
	WERC's code is posted online at http://www.uaf.edu/water/staff/irving/csi-code/,		WERC's code is posted online at http://www.uaf.edu/water/staff/irving/csi-code/,
	including a [http://www.uaf.edu/water/staff/irving/csi-code/readme README] file.		including a [http://www.uaf.edu/water/staff/irving/csi-code/readme README] file.
		+	This system has been in use for several years, downloading data from up to 50
		+	remote loggers hourly in several different radio networks.
		+
		+	This code has not been packaged for distribution, or automatic
		+	installation, but it is intended to be available under the GNU Public
		+	License (GPL).
		+
		+	Brief technical descriptions of the primary components follow...
		+
		+
		+	==Campbell/Comm.pm==
		+
		+	This module becomes part of a Perl program via the '''use''' or '''require'''
		+	keywords. It provides the machinery to connect and send/receive commands
		+	to/from a remote datalogger using Perl's object-oriented programming
		+	methodology. Individual ''methods'' are provided corresponding to some/most
		+	of the ''telecommunications'' commands documented in the Campbell Scientific
		+	CR10 family manuals.
		+
		+	Another Perl module is needed in order to interact with remote dataloggers,
		+	and that is Net::Telnet, which is included in the standard Perl distribution.
		+	This module allows automating the telnet protocol, but boils down to being
		+	able to send commands to the remote system and then wait for and handle
		+	responses -- or no response, if that's necessary.
		+
		+	Besides the nominal TCP/IP connections, Net::Telnet is capable of supporting
		+	interfaces using a direct serial or modem connection
		+
		+	Most of WERC's research datalogging systems are