Palm Developer Forum digest wrote:
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
SysTaskDelay() is a really bad thing when you are doing bluetooth
transfer. Bluetooth subsystem heavy rely on various notifications and
SysTaskDelay blocks them. Alert running a runloop where notifications
and callback are dispatched. It seems your runloop isn't suitable for
bluetooth modules in some kind.
Anyway I'd suggest to avoid using Bluetooth vdrv driver, low level
bluetooth is quite stable once connection is established _if_ you are
doing all things according to the documentation :)
--
Dmytro Pohromskyy,
Softick Ltd.
skype: dmp-softick
--
For information on using the ACCESS Developer Forums, or to unsubscribe, please
see http://www.access-company.com/developers/forums/
