My app receives 8-byte Bluetooth messages from a measuring device. I handle nilEvents in the EventLoop and call a proc every second to check for data availability with a call to SrmReceiveCheck. It works fine everywhere, except on *some* TX devices, like mine, where this API never seems to see the data. For unknown reasons, on-device debugging has long stopped working on my PC, so I'm left to adding alerts for tracing. But when I add an alert at the beginning of that proc, my TX handles messages fine. What is the effect of an alert on comms??? I instead tried a less obstrusive SysTaskDelay(1), without sucess. Do I have to write to screen or wait for user input to "prompt" data reception? Ideas welcome.
Luc Le Blanc http://www.speleo.qc.ca/Auriga -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
