5 - 2 5X80 Series Software Development Kit (SDK) User’s GuideSetCommDriverHandleSetCommDriverHandle receives the handle to the open communications port. The handle can then be used to access privatedriver ioctl calls.Syntaxvoid SetCommDriverHandle(HANDLE hDriver)Parameter DescriptionhDriver The current handle to the open driver used to communicate with the imager.SetHardwareTriggerSetHardwareTrigger triggers the imager hardware trigger line, depending on bEnable. The hardware trigger line is active low.Syntaxvoid SetHardwareTrigger(bool bEnable)Parameter DescriptionbEnable If true, set trigger line low to trigger imager. If false, set trigger line high to turn off trigger.WakeUpImagerWakeUpImager toggles the imager hardware wakeup line from low to high, delay, (see Integration Manual for timing), then fromhigh back to low.Syntaxvoid ImagerPoweredDown(void)Registry EntriesThere are two registry entries used to modify the SDK default behavior. The values are both located in the registry keyHKEY_LOCAL_MACHINE\SOFTWARE\Hand Held Products\MatrixDemos.Baud RateThe SDK will not normally allow high speed serial connections (connections greater than 115200 baud) unless it recognizes thedriver name in the registry. The first registry value, BaudRate, specifies the first baud rate at which the demos will attempt toconnect. It also overrides the normal block that sets high speed baud rates. This lets you specify a baud rate greater than115200.ForceHmodemThe SDK does not normally use its Y-Modem variant, Hmodem, if a high speed serial connection is specified. However, if yourdriver does not support true hardware RTS flow control, there is a substantial risk of communication buffer overruns. Theseoverruns can cause data loss, especially during image transfer. The registry value ForceHmodem lets you force the use of thecommunications protocol, preventing data buffer overflow.