Bluetooth app crashes after certain time period

[nex7-7]

I am creating an app that sends Slider and Accelerometer data over bluetooth to an Adruino using HC05 Bluetooth Module.

I am using a timer so that app doesn't crash due to accelerometer sending data too frequently. I am also using variable "timer" that prevents values to be written to global variables t, xA, yA, zA, while they are being read. I have set the timer to 500ms.

I am able to setup a bluetooth connection and receieve values for a while untill the app freezes and then crashes.

Kindly Help
Feel free to ask to share any code or setup details
Thank You

[ABG]

Maybe this handshake approach will help:

Bluetooth connection button color

In addition to what @Ghica and @Taifun have already siad, the way that I've used in my app's is to make a handshake between the client and the server. In other words the connected device shall send periodically (i.e. once each minute) a "live" character that the app shall read. If within two minutes the app does not receive the "live", it is intended as a BT disconnection and the "Disconnection warning" is issued. To actuate the reading every two minutes the app shall set a specific clock. In d…

from

FAQ Section: BlueTooth Starter Guides

BlueTooth Problems Disconnection detection through handshakes - @uskiara How to get Device Information BlueTooth Client Polling Rate Explained - @ewpatton Links to bluetooth guides on communication, numeric data and arduino BLE Connection Starter Guide - @ewpatton FAQ Section: BlueTooth/BLE and Arduino Starter FAQ Section: BlueTooth/BLE and Micro:bit FAQ Section: BlueTooth/BLE and HM-10 FAQ Section: BlueTooth/BLE nb158 and later (current release info)

[nex7-7]

Thank You for replying. I tried this but didn't help. I noticed that the app stops sending data at around 1 min 40 sec mark at every run. The connection stays live, then the app freezes and closes automatically after sometime.

[uskiara]

Dear @nex7-7,
to avoid that the app goes to sleep you can use an extension made by @taifun ( !!!)
that features the following block:

You can invoke this block into the screen1 initialization. In such a way the app remains active "forever" until you close it :

[nex7-7]

@uskiara Thank you for replying
I tried this fix, but no avail.

The following is the arduino sketch that I am running to recieve data. I shared incase I am doing something incorrectly.

const int LED = 13;
char switchstate;
void setup()  {
  Serial.begin(9600);
  pinMode(LED,  OUTPUT);
}
void loop() {
  if(Serial.available()){ 
    switchstate = Serial.read();
    Serial.print(switchstate);
    delay(1);
  }
}

[ABG]

So the sketch talks but the app doesn't listen?

Is this a buffer filling up?

[nex7-7]

@ABG I am not quite sure if I follow. I have set up so that the app sends data, and sketch recieves it. I think the sketch is listening but the app isn't talking. Apologies if that's not what you mean.

[ABG]

Serial is both the incoming Bluetooth stream and the output Bluetooth stream?

[nex7-7]

Yes, I am using serial to recieve data as well as print it on the Serial Monitor. Is it the incorrect method? Are there any known issues with this approach?

[ABG]

I am stumped.

Better call in a hardware guy like @uskiara

[nex7-7]

@ABG Thank you for helping out.
Just wanted to share that HC05 is connected to arduino like following:

HC05	Arduino
+5V	+5V
GND	GND
RX	TX
TX	RX

Shared incase that helps the discussion

[nex7-7]

Update: I have been testing individual components and realized that is issue is with sending/recieving of the sent string.

If I send a single letter it keeps recieveing for quite long. However as soon as I switch to sending larger strings, it will jam up after certain time period and stop.

Update2: I changed the timer to send data at every 15ms and I am only sending letter A at each clock firing. I count the number of As recieved before it froze and it came out to be 631.

[nex7-7]

Thank You @ABG

@ABG

So the sketch talks but the app doesn't listen?

Is this a buffer filling up?

I realised what I was doing wrong. I didn't understand the working of Serial properly. I assumed that Serial.print just prints it on the Serial Monitor, but then I realised that it also sends printed lines.

The recieve buffer on the app/phone was filling up which caused the app to crash.
I created a Software serial to recieve data and used Serial to print data.

[uskiara]

Dear all (@nex7-7 and @ABG ),
sorry not having responded earlier but I was travelling (I'm out for a historical car rally-race).
I see that you have already solved, and that's fine.
Have a great WE.
Cheers.