Driver Subcommand - Accessing Drivers

Several Laser Model Interface (LMI) commands use the DRIVER subcommand, for example:

LMI DRIVER ‘abc|c:\abc\prog.dll|login=user’ QUERY APIVERSION

The string following the driver keyword ‑ the vendor’s identification string - contains between one and three fields separated by bar (‘|’) characters. The fields are, i) a tag string, ii) the full path to the driver Dynamic Link Library (DLL) file, and iii) the driver’s connect string. The driver’s connect string can be any string, as required by the vendor company to connect to their driver, or it can be omitted if the driver requires no special connection information.

Once one LMI DRIVER command has been used, the string can be shortened to just the tag for all subsequent commands, for example:

LMI DRIVER ‘abc’ QUERY DRIVERVERSION

Or, the DRIVER subcommand can be omitted completely, in which case the command is directed to the most recently referenced driver:

LMI QUERY DRIVERVERSION