Matrix Orbital GTT70A - Manual (Page 8)

Command Summary 4
Animations
While the image data for animations is stored in the Animation buffer, the actual state of animations is
stored in a separate location. This allows animations to be removed from the screen, but remain in
buffer memory. The animation descriptor file is a simple text file, with a series of lines of times to
display a frame, and a path from the root directory to a bitmap file to use for that frame. For example:
Figure 3: Animation File Example
The above example defines the first four frames of a sample logo animation stored in the Animation
folder, with each frame displayed for 20ms, 2ms, 5ms, and 10ms respectively.
1.1 Scripting
The Autoexec File
On startup, the module will check the root directory of the SD card for a file named AUTOEXEC. If that
file exists, it will be loaded directly into the in buffer and parsed as if it came from the input
communications port. This is useful for having custom power on defaults. Simply place the binary
stream of values that the module should execute on startup in the AUTOEXEC. The default autoexec file
below, which ships from the factory, loads and displays a start screen before clearing the bitmap buffer.
Figure 4: Autoexec File Example
Please note, if a command is started within the AUTOEXEC, however is not completed with the data in
the AUTOEXEC, the command will wait for data from the serial port to complete the command. After
which, the module will return to normal operations. The AUTOEXEC file is a special example of the script
feature available on the GTT line.