dataTaker - Data Loggers, Powerful and Flexible Data Acquisition & Data Logging Systems

STATUS Command

The STATUS command produces a report of the current configuration of the dataTaker.

The STATUS reports are returned to the host computer, and some are displayed on the display panel (See Section III - Keypad and Display) as 8 predefined Status Screens. Status reports cannot be logged.

General STATUS

Using DeTransfer, a general status report for the dataTaker is returned to the host computer by the STATUS command as follows

STATUS

which produces a response similar to

dataTaker 0 Version 7.08
A B C,none Scan Schedules Active,Halted
3,0 Alarms Active,Halted
4 Polynomials/Spans Defined
Logging is ON
166530,0 Internal Data Points Free,Stored
217630,125350 Card Data Points Free,Stored
4090,0 Program Characters Free,Stored
/a/C/d/E/f/h/J/K/l/M/N/o/Q/R/S/t/U/v/w/x/y/Z

for an programmed logger.

If the Units Text Switch is disabled (/u), then the format of the status report is truncated to data only. The Parameter22 and Parameter24 commands can be used with this format to define the delimiters for the status information.

If the Units Text Switch is disabled (/u) and Parameter22=13 and Parameter24=13, the general status report is returned without text

0,7.08
A B C,none
3,0
4
0
166530,0
217630,125350
4090,0
/a/C/d/E/f/h/J/K/l/M/N/o/Q/R/S/t/u/v/w/x/y/Z

With the Units Text Switch disabled (/u) and Parameter22=44 and Parameter24=13, the general status report is returned in a single line (although shown here with line wrap)

0,7.00,A B C,none,3,0,4,0,166530,0,217630,125350,4090,0
/a/C/d/E/f/h/J/K/l/M/N/o/Q/R/S/t/u/v/w/x/y/Z

These formats of the status report facilitates reading the dataTaker status into dedicated host software. This computer compatible format of the status report can also be defined for the individual status reports described below.

Using DeLogger, the general status report is available by selecting dataTaker:StatusÖ from the main menu bar, or by clicking the Status button on the toolbar,

 

 

which produces a dialog similar to the following which details the various status information, in this case for an unprogrammed logger.

 

Individual STATUS

Individual status reports can also be returned using the STATUS command, which provide greater detail of the configuration.

These individual status reports are not supported by DeLogger, however these could be obtained by issuing the following commands from the Entry Screen of the Text View.

Individual status reports are returned by the command

STATUSn

where

n              is the individual status level required (1 - 13)

The individual status reports to which the 13 status levels relate are listed below

STATUS1     ñ dataTaker network address and firmware version
STATUS2     ñ lists Schedules active and halted
STATUS3     ñ lists Alarms active and halted
STATUS4     ñ lists polynomials and spans defined
STATUS5     ñ reports current setting of LOGON/LOGOFF
STATUS6     ñ reports data memory free and data stored in the internal memory
STATUS7     ñ reports data memory free and data stored in the memory card
STATUS8     ñ lists the program stored in the memory card
STATUS9     ñ lists current switch settings
STATUS10   ñ lists information about the current program
STATUS11   ñ lists the program on the memory card
STATUS12   ñ lists the time and date of the first and last data points stored in the internal memory
STATUS13   ñ lists the time and date of the first and last data points stored in the memory card

The status reports returned by the individual STATUS commands is illustrated in the following examples.

These individual status reports are not supported by DeLogger.

STATUS1

The STATUS1 command returns the dataTaker Network address and Firmware version number as follows

STATUS1

dataTaker 0 Version 7.08

STATUS2

The STATUS2 command lists the Triggered Schedules that are currently defined, active and halted, as follows

if there is no memory card inserted, the Schedules currently defined in the dataTaker are returned

if an invalid memory card containing other data is inserted, then the Schedules used to acquire the data in the memory card are returned. These Schedules may be different to those which are currently defined in the dataTaker.

STATUS2

A B C,none Scan Schedules Active,Halted
RA5M  1..3V  8..10TT
RB1H  1..4DS  1..4C
RC15M  4..6L(S2)

STATUS3

The STATUS3 command lists the currently defined alarms, active and halted, and the Alarms Schedule as follows

STATUS3

3,1 Alarms Active,Halted
RZ20S
ALARM3(1V>1000.0)"Voltage Over-range"
ALARM4(5TT<>100,105/60S)"Boiler Fault"
ALARM22(1C><256,512)"[RA1S 1C]"
alarm25(T>10:00:00)"Start Logging [GA GB]"

Active alarms are shown with the ALARM command in upper case, and inactive alarms are shown with the alarm keyword in lower case.

STATUS4

The STATUS4 command lists the currently defined polynomials and spans as follows

STATUS4

3 Polynomials/Spans Defined
Y1=2.364,1.002,2.2,0.945"KPa"
S5=0.0,1000.0,0.0,100.0"Deg C"
S6=20.0,100.0,0.0,500.0"% RH"

STATUS5

The STATUS5 command returns the current setting of the LOGON or LOGOFF commands as follows

STATUS5

Logging is ON

or

Logging is OFF

STATUS6

The STATUS6 command returns the amount of data memory free and the amount of data stored for the internal memory as follows

STATUS6

166530,0 Internal Data Points Free,Stored

STATUS7

The STATUS7 command returns the amount of data memory free and the amount of data stored for the memory card as follows

STATUS7

217630,125350 Card Data Points Free,Stored

However if there is no memory card inserted in the dataTaker, then the STATUS7 command returns

No Card Inserted

 

STATUS8

The STATUS8 command returns the number of program characters free and stored in the memory card, and lists the program if there is one stored in the memory card, as follows

STATUS8

4008,82 Program Characters Free,Stored
;CSCANS CALARMS
;/m /n /u P22=44 P24=13
;BEGIN
;RA5M
;1V  3..5TT  2HSC
;ALARM2(5TT>50.0)"Temperature Alarm"
;END
;LOGON

if there is a program stored in the memory card, or returns

4090,0 Program Characters Free,Stored

if there is no program stored in the memory card.

However if there is no memory card inserted in the dataTaker, then the STATUS8 command returns

No Card Inserted

STATUS9

The STATUS9 command lists the current switch settings as follows

STATUS9

/a/C/d/E/f/h/J/K/l/M/N/o/Q/R/S/t/U/v/w/x/y/Z

STATUS10

The STATUS10 command details the data that will be returned by the current dataTaker program.

STATUS10

27113,1989,1,0,"",<A,"2S",H,<"Dry bulb","",0,0,5,4,3>, <"Wet bulb","",0,0,5,4,3>,<"Humidity",%RH",0,0,5,4,3> >,<B>,<C>,<D>,<X>

 

the items returned are in the order

program ID
base year
time resolution
card status
$ string definition
followed by Schedule fields that identify individual channels, their format and their units

For a detailed description, consult the "dataTaker Advanced Communications Manual".

STATUS11

The STATUS11 command details the data that will be returned by the program in the memory card.

STATUS11

0,0,0,0,"",<A>,<B>,<C>,<D>,<X>

The format of the data returned is the same as for STATUS10 command. The above example indicates the memory card does not contain a program.

STATUS12

The STATUS12 command returns the time and date of the first and last data points stored in the dataTaker's internal memory.

STATUS12

08:00:00 on 19/06/2003, 14:25:00 on 20/06/2003 Internal data Start, End times

STATUS13

The STATUS13 command returns the time and date of the first and last data points stored in the memory card.

STATUS13

08:00:00 on 19/06/2003, 14:25:00 on 20/06/2003 External data Start, End times

Fixed Format Data Mode

The STATUSn commands return status in a different format if the Fixed Format Mode for data is enabled (/H). The format is described in the "dataTaker Advanced Communications Manual".

 


RESET Command

Whenever the dataTaker is powered up or hardware reset, the logger executes an initialisation and system reset routine.

During a system reset, the following operations are performed by the dataTaker

check the ROM and the RAM memory, and initialise the internal data storage memory

reset the Parameter variables to the default values (See Section III ñ Parameter Commands)

reset the Switches to the default settings (See Section III ñ Switch Commands)

calibrate the analog to digital converter, checking for calibration errors (See Section III ñ TEST Command)

initialise the digital input circuits and counters, checking for any malfunctions (See Section III ñ TEST Command)

search the internal serial bus for any Channel Expansion Modules, keypad displays, signal conditioning boards, etc. and configure the logger accordingly for those found

Caution : Resetting the dataTaker will erase all data stored in the internal memory, erase all schedules and alarms, and erase all polynomial and span declarations. However resetting the logger does not clear data or programs from an inserted memory card.

The reset takes approximately 600mS to complete, and commands should not be entered until the reset function is complete. This delay applies to a power up, hardware or commanded reset.

Using the RESET Command with DeTransfer

Using DeTransfer, a system reset is commanded as follows

RESET

Whenever a system reset is performed, the dataTaker returns the sign on message to the host computer or terminal as follows

dataTaker 0 Version 7.00
Initialising...Done

All checking of ROM and RAM memory, initialisation of interfaces, setting of defaults, checking of digital input circuits, and calibration of the analog to digital converter, occurs between the 'Initialising...' and 'Done' messages being returned.

Any errors which occur during reset and calibration produce error messages at this time. The error messages are displayed directly by DeTransfer in the upper Receive window, and may be any combination of the following

E13-digital failure
E30-calibration failure nn
E33ñCSIO bus failure
E46-ROM checksum error
E60-RAM n failure

The meaning and cause of each of these initialisation error messages is discussed in the dataTaker Technical/Service Manual.

These error messages indicate that the dataTaker has failed in some manner. If you receive any of these error messages then disconnect all sensors, actuators, etc. from the dataTaker and enter the RESET command again. If there are no error messages now, then

check that there are no large offset or common mode voltages on the input signals

check that there are no ground loops either between the logger and sensors, and between the logger and the host computer

check that the logger power supply is of the correct voltage and current capacity

If the error messages persist, then the logger should be returned to a service centre for repair.

Using the RESET Command with DeLogger

Using DeLogger, a system reset is performed by selecting dataTaker:ResetÖ from the main menu bar, or by clicking the Reset button on the main tool bar

 

 

DeLogger displays any error messages that occur during reset and calibration in the Events Log window, which is usually at the bottom of the screen (make sure View:Show Error Events and View:View Events are checked on the main menu bar).

 


TEST Command

The TEST command is used to force the dataTaker to recalibrate and self-test the analog to digital converter, and to report the status of the analog to digital converter and various internal parameters.

Using TEST Command with DeTransfer

Using DeTransfer, the system TEST is commanded as follows

TEST

and returns the test information similar to the following

dataTaker524  Ver 7.08
Vos (mV) 0.118
Vfo  (V) 7.875
Fc (kHz) 17.778
CMRR(db) 98.4
Vos3(mV) 0.314
Tos      1.0022
Ios (nA) 0
Ibia(nA) 8
Ibat(mA) -102.1
Vbat (V) 6.3
Vos*(uV) -11
Vos+(uV) 41
Vos-(uV) 27
VosR(uV) -10
Vosd(uV) 44
Ics1(mA) 2.5012
Ics2(uA) 249.93
PASS

The meaning of each of these test data is described in the table overleaf.

These test data provide diagnostic assistance if a dataTaker is malfunctioning. Their interpretation for fault diagnosis is described in the dataTaker Technical/Service Manual.

The format of the test data can be changed with the Units Text Switch and the Parameter24 command. If the Units Text Switch is enabled (/U) then the verbose format of the test parameters as illustrated above is returned.

If the Units Text Switch is disabled (/u) then the brief format of the test data as illustrated below is returned (without the line wrap). The separator between individual test parameters is defined by the Parameter22 command, which by default is a space character

524 3.35 0.116 7.875 17.777 98.2 0.317 1.0022 0 8 -102.4 6.3 -10 42 27 -11 46 2.5011 249.92 PASS

If the separator character is set to a comma (Parameter22=44) then the test parameters are returned as illustrated below (without the line wrap)

524,3.35,0.117,7.875,17.777,98.8,0.315,1.0022,0,8,-102.2,6.3,-11,41,26,
-9,45,2.5 011,249.92,PASS

Self Checking of Test Parameters

The TEST command checks each of these test data against internal limits. These limits are listed in the table overleaf. The dataTaker returns a general message at the end of the test report to indicate overall condition of the logger, as follows

PASS

or

FAIL

The FAIL message is returned if one or more of the test parameters does not fall within the respective limits. If the Units Text Switch is enabled (/U), then the message ë- failí is also appended to each test parameter that has failed. For example the test parameter result

CMRR(db) 80.3 ñ fail

indicates that the common mode rejection is unacceptable.

The meaning and allowable limits for the test parameters included in the TEST report are discussed in detail in the dataTaker Technical / Service Manual. Diagnostic and service procedures for correcting out of range test parameters is also described.

Individual TEST Data

Individual test data can also be returned by the command

TESTn

where

n    is the individual test line level required
(See the following dataTaker Test Table for the individual test data n)

Using DeTransfer for example

TEST4

returns individual test data for line 4 of the general TEST data, which is the common mode rejection ratio (CMRR) test data

CMRR(db) 98.4

Repeating TEST Data

Test data can be returned repeatedly using the TESTR or TESTnR commands, which will continually repeat the entire test data or an individual test data item. Repeating test reports are returned by the general commands

TESTR
or
TESTnR

See the following dataTaker Test Table to identify the individual test data n.

dataTaker Test Table

 

Test Data

n

Description

Limits

dataTaker 524 7.00

0

dataTaker config & firmware version

 

Vos (mV)    0.009

1

Input offset voltage

±1mV

Vfo  (V)    7.308

2

Input voltage for VCO=0Hz

6.0 to 8.50V

Fc (kHz)    18.200

3

VCO centre frequency

11.46 to 23.87kHz

CMRR(db)    99.6

4

Common mode rejection ratio

>90db

Vos3(mV)    0.238

5

Three wire input offset voltage

--1.9 to 3.1mV

Tos         1.0023

6

Terminator attenuation for T channel option

0.99 to 1.01

Ios (nA)    -3

7

Input bias current offset

±30nA

Ibia(nA)    15

8

Input bias current

±90nA

Ibat(mA)    0.5

9

Battery current: + charging, -- discharging

--500 to +600mA

Vbat (V)    6.6

10

Battery voltage

5.4 to 13.0V

Vos*(uV)    -95

11

Multiplexer * single ended offset voltage

--600 to +110µV

Vos+(uV)    33

12

Multiplexer + single ended offset voltage

±180µV

Vos-(uV)    10

13

Multiplexer -- single ended offset voltage

±180µV

VosR(uV)    66

14

Multiplexer R single ended offset voltage

--110 to 600µV

Vosd(uV)    5

15

Multiplexer differential offset voltage

±180µV

Ics1(mA)    2.5012

16

Current source 1 current

0.5mA to 10mA

Ics2(µA)    249.93

17

Current source 2 current

1µA to 500µA

PASS

23

Test pass or fail

 

 

Using DeTransfer, the command

TEST16

will repeatedly return the data for excitation current source 1 (2.500 mA).

The repeating TEST can be stopped by the Halt command, by a Carriage Return (hit the Enter key).

Battery Status

The test parameters returned by the TEST command also contain information of the internal battery status.

The internal battery can be any of the following

1.2Ah gel cell lead acid battery mounted under the top cover of a dataTaker 500/600

4Ah gel cell lead acid battery connected to BAT+ and BATñ of the dataTaker 500/600

17Ah alkaline battery connected to the internal battery connector of the dataTaker 500/600

4Ah gel cell lead acid battery connected to the Lead Acid + and ñ terminals of a dataTaker 50

17Ah alkaline battery connected to the Alkaline + and ñ terminals of a dataTaker 50

The test parameter Ibat reports the battery current as follows

if the Ibat data is positive, then the battery is being charged from an external power supply

if the Ibat data is negative, then the battery is powering the logger and is discharging

The test parameter Vbat reports the battery voltage.

dataTaker Configuration Code

The first test data returned by the TEST Command is the dataTaker configuration, and the version number of the firmware within the logger as follows

dataTaker524 Ver 7.08

The configuration code describes the composition of the dataTaker as follows

First digit                5 = DT5xx series logger

 

Subsequent digits     1 = DT50 series CMOS multiplexer I/O board
                            2 = DT500 series CMOS multiplexer I/O board
                            3 = DT500 series relay multiplexer I/O board
                            4 = Keypad display module in logger or external panel mount module
                            5 = Vibrating wire conditioning board
                            6 = Channel expansion module

The subsequent digits are in the order that respective components of the particular dataTaker are configured to the internal serial bus. The components are reported in the order

ñ 5 (always the first digit)
– signal conditioning board
– multiplexer I/O board
– Channel expansion board(s)
– Keypad and display module (integrated or external)

Some examples of common configuration codes follow

51            dataTaker 50 with CMOS multiplexer board

514           dataTaker 50 with CMOS multiplexer board and external panel display

52            dataTaker 500 with CMOS multiplexer board

524           dataTaker 500 with CMOS multiplexer board and external keypad display

                dataTaker 600 with CMOS multiplexer board and integral keypad display

53            dataTaker 505 with relay multiplexer board

534           dataTaker 505 with relay multiplexer board and external keypad display

                dataTaker 605 with relay multiplexer board and integral keypad display

553           Geologger 515 with vibrating wire conditioning board and relay multiplexer board

5534         Geologger 515 with vibrating wire conditioning board, relay multiplexer board
                and external keypad display

                Geologger 615 with vibrating wire conditioning board, relay multiplexer board
                and integral keypad display

5366         dataTaker 505 with relay multiplexer board and 2 channel expansion modules

5264         dataTaker 500 with CMOS multiplexer board, 1 channel expansion module and
                external keypad display

                dataTaker 600 with CMOS multiplexer board, 1 Channel expansion module and
                integral keypad display

553664     Geologger 515 with vibrating wire conditioning board, relay multiplexer board,
                2 channel expansion modules and external keypad display

Using the TEST Command with DeLogger

The TEST command is available by selecting dataTaker:TestÖ from the main menu bar, or by clicking the Test button on the main toolbar

 

 

and DeLogger displays the test data in the following dialog

 

 

The green checkmarks indicate that the respective test data are within acceptable limits. Any test data that is outside acceptable limits is marked with a red cross.

The overall test result Pass or Fail is displayed at the bottom of the dialog.

DeLogger does not support individual TESTn commands directly, however these could be obtained by issuing the commands from the Entry Screen of the Text View.

Page Content


Home

Title and Waranty

Go to: Section 2 | Section 3

Section 1


Construction of the dataTaker 50

Construction of the dataTaker 500 600

Construction of the CEM

Getting Started

 

Section 2


Interfacing

Powering the dataTaker

Powering Sensors from the dataTaker

The Serial Interfaces

The RS232 COMMS Serial Interface

The NETWORK Interface

Analog Process

Connect Analog

Analog Chns

Measuring Low Level Voltages

Measuring High Level Voltages

Measuring Currents

Measuring 4-20mA Current Loops

Measuring Resistance

Measuring Frequency and Period

Measuring Analog Logic State

Measuring Temperature

Measuring Temperature with Thermocouples

Measuring Temperature with RTDs

Measuring Temperature with IC Temperature Sensors

Measuring Temperature with Thermistors

Measuring Bridges and Strain Gauges

Measuring Vibrating Wire Strain Gauges

The Digital Input Channels

Monitoring Digital State

The Low Speed Counters

The Phase Encoder Counter

The High Speed Counters

The Digital Output Channels

The Channel Expansion Module

Installing The Panel Mount Display

 

Section 3


Programming the dataTaker

Communication Protocols and Commands

Entering Commands and Programs

Format of Returned Data

Specifying Channels

The Analog Input Channels

The Digital Input Channels

The Counter Channels

The Digital Output Channels

The Real Time Clock

The Internal Channels

Channel Options

Schedules

Alarms

Scaling Data - Polynomials, Spans and Functions

CVs Calcs and Histogram

Logging Data to Memory

Programming from Memory Cards

STATUS RESET TEST

Switches and Parameters

Networking

Writing Programs

Keypad and Display

Error Mess Text

Appendix A - ASCII

Appendix B - ADC Timing