the latest version. i'll compile in release mode and try it this weekend. again, it happens inconsistently. the service is started immediately on a successful connection to the bluetooth module (which happens immediately on program startup). perhaps there is some delay that is necessary before i try to interact with the BT module. however, i am monitoring the communications on the bluetooth side (and also with a saleae logic analyzer) and it does get the data being sent via astreams.write2 but the b4a program fails on receipt of the bytes requested from the bluetooth module. does the error message above indicate in any way what line of code is causing the issue? or does it point to the "End Sub" line by default because it is some time of "generic" error?
i'll see if i can find a routine to make it fail consistently.