Module Operations:
Cmd | Description |
<STX>x | File delete from module |
<STX>q | Module clear |
<STX>Q | Modules, clear all |
<STX>z | Module, compress |
<STX>W | Module, directory request |
<STX>X | Module, set default |
<STX>w | Module, FLASH memory Test |
<STX>t | Module, RAM memory Test |
<STX>Kp | Module Protection |
Comment
Supported
Supported
Supported Not Supported Partially Supported Supported
Do the stutus report, always oke Do the stutus report, always oke Not Supported
DGL will emulate 2 different Modules: Ram and Flash. Datamax has several Flash and Ram modules, but DGL will map all Flash modules to the same PTX Flash File System, and all Ram Modules to the global Memory Pool.
When recalling something from a module, the Module Identifier is not specified in the command, so this should not cause a problem when DGL maps them to a single Flash / Ram module.
The only problem that might occur is when there is
When specifying a module that is not available, the printer will automatically select the default module.
Bi-Directional Communications
Datamax describes the time critical responses as follows:
When the printer receives a Status and Control Command, its current operation will be momentarily interrupted to respond to the command. Status and Control Commands may be issued before or after
Commands that require immediate action (including commands that request immediate response) will not be supported.
Non
Cutter Commands
The Commands to activate the Cutter (System Level Command <STX>o, and Label Formatting Commands ‘c’ and ‘:’) are only processed when the Media Handling menu is set to ‘Cut’, and the DGL
41