2A1 is a variant of the popular 2A0 and increases 2A0's on-board logging capacity by 32 times to 1 Mega byte. On-board logging times of tens of minutes, at the fastest logging rate, are now possible.

All 2A0 features are retained and owners of 2A0 units can upgrade their existing units by either purchasing an upgrade kit and doing it themselves, or returning their 2A0 and getting Tech Edge to do it for them.

The images show that the position of the new logging button is now closer to the existing three LEDs and there is an additional smaller red LED to show logging activity (rate of flashing indicates data rate).

| Logging Tech. (main page) | 1 Mbyte hardware | 32 kByte hardware

Overview - On-Board Memory & Serial Logging

For a detailed description of on-board logging for the 2A0 unit go here (new window). The diagram at right is described on that page.

The rest of this page describes the software aspects of the 1 Mb version of 2A0.

For technical specifications of the 2A1 unit, see the 2A0 information.

2A1 Software Logging Commands

With 2A0's 32 kByte on-board memory, the tn, xn, ywwww & z RS232 commands were sufficient to control the saving and restoring of data to and from on-board memory. The wwww parameter was sufficient to address any byte between address 0 and 7FFF.

2A1 introduces the concept of sectors of data and logging sessions to manage the 1,048 k bytes of memory. Sectors are 4096 bytes in size, and up to 255 sessions can be logged. The new commands to support this scheme are :




Stop/Start logging of data to on-board memory.
    n = 0, stop logging (ie. x0) - same as pressing the logging button to STOP logging.
    n = 1, start logging (ie. x1) - same as pressing the logging button to START logging.
    n = 2 (or more) same as the q command without parameters (described below).


This is a special case of the set logging pointer command and effectively clears all logging sessions and can be used after all data has been downloaded to a PC. It is equivalent to pressing the on-board logging button (from the logging OFF state) for more than 4 seconds. The status LED will do about 10 very fast flashes to indicate the action.



Dump data from on-board memory. The first form dumps saved data from session with ID nn (assuming it is a valid session).
The second form, without parameter, dumps all of memory from the first to last valid session. Session IDs start from 00 (the first) to a maximum of 7E (the 255th session).


Query on-board memory status. The first form, without parameter, returns aabb where :
    aa = number of sectors of memory used.
    bb = number of logging sessions saved.
As a logging session uses at least one sector, aa will be equal or greater than bb.


The second form, with parameter nn returns the byte length of session nn. The length is a six digit hex number hhhhhh.


Read the memory type ID string. A 4 digit hex string is returned 
    BF80 = SST memory device of 8 Mega bits used.
    FFFF = No memory device present or readable.


Set logging control byte (at address 03) to nn. Bits are as (default = bold) :
    b7 - Frame generation, 1 = Auto (always produced), 0 = Manual.
    b6 - Frame type, 1 = Binary, 0 = hex/ASCII.
    b5 - USR inputs, 1 = scale to 1.5 format (scaled x8 = 13 bits), 0 = raw.
    b4 - Checksum 1 = debug mode (ASCII/Hex), 0 = normal (binary).
    b3 - Special, 1 = invert checksum in binary mode, no LF in ASCII/Hex mode.
                        0 = normal checksum, CR/LF at line ends.
    b2-0 Frame type
        0 : V1.5 compatible mode.
        1 : V2.0 mode frame.
        2 : Calibration mode.
        3 : Debug/Diagnostic mode (PID and status codes).


Set the logging delay between frames to nn (hex) in units of 10 mSec. Minimum value is 1, maximum is 100 (0x64).