Arduino: Having trouble connecting/writing AT commands to Bluetooth HC05 module via USB serial

Question

As an introduction, I bought myself an arduino and a few modules to learn some software stuff. The project is to eventually connect to a bluetooth OBD2 reader on my car to display real time data on a small LCD.

The problem

I am either not able to connect to, or not write to, my HC05 module via software serial. I think I have narrowed this down to a couple possibilities.

1. I am unable to connect to the module in the first place.

I have a Mega 2560 and HC05.

5V <-> VCC

GND <-> GND

D2 <-> RXD

D3 <-> TXD

Note that I have seen 9600 and 38400 baud rates for connecting but neither worked, so I made this function to try them all for me...

//set up serial relay into HC05.
SoftwareSerial hc05(2,3);

//computer serial baud rate 115200

bool hc05_connect() { 
  long baud_list[] = {300, 1200, 2400, 4800, 9600, 19200, 38400, 57600, 74880, 115200, 230400}; 
  Serial.println("Attempting to connect to HC05 bluetooth module...");
  bool success = 0;
  for (int i=0; i<(sizeof(baud_list) / sizeof(baud_list[0])); i++) {
    Serial.print("Baud rate ");
    Serial.print(baud_list[i]);
    Serial.print("...");
    hc05.begin(baud_list[i]);
    hc05.write("AT");
    delay(1000);
    if (hc05.available()) {
      Serial.println(" successful!");
      success = 1;
      return success;
    } else {
      Serial.println(" failed");
    }
  }
  return success;
}

Notes:

• This has always returned failed for every baud rate.
• I have the bluetooth module in command mode, initiated by pressing the button as I supply power.
• I have tried unplugging the TX/RX pins while uploading the sketch. No difference noted.

2. My attempts to send commands to the HC05 are failing.

Below is my function for sending commands to the module.

void loop() {
  // listen for communication from the ESP8266 and then write it to the serial monitor
  if (hc05.available()) {
    Serial.write(hc05.read());
  }

  // listen for user input and send it to the ESP8266
  if (Serial.available() > 0) {
    Serial.println("Writing to hc05...");
    Serial.println(Serial.available());
    Serial.println(Serial.read());
    hc05.write(Serial.read());
  }
}

I have added in a few lines which write back to Serial so I can see what's being sent, and the monitor returns weird stuff. For example, if I send "AT", this is what the monitor reads:

Writing to hc05...
3
65
Writing to hc05...
1
10

Notes:

• Why is it sending 2 different items?
• Why is it sending integers rather than the characters I said?
• Does this indicate I'm just sending it nonsense commands so it's not responding?

I can provide full code if you want, this is already a huge textwall though. Please help me!

Edit

So I have been able to get communication two ways via the bluetooth module using a modified version of the code in this instructable: https://www.instructables.com/How-to-Set-Up-and-Test-Arduino-Bluetooth-Connectio/

I was able to send from PC only and not receive to an android bluetooth terminal using SoftwareSerial with HC05's RX - TX0 / TX - RX0. And I was able to receive to PC and not send using hardware serial / Serial1 with HC05's RX - TX1 / TX - RX1.

So now I have RX - TX0 / TX - RX1. It seems to communicate through terminal like this.

void setup() {
  Serial.begin(9600); //open the serial port
  Serial1.begin(9600);
}

void loop() {
  if (Serial1.available()) {
    Serial.print("(Received)");
    Serial.println(Serial1.readString()); // send from serial to bluetooth
  }
  if (Serial.available()) {
    Serial.print("(Sent)");
    Serial.println(Serial.readString());
    Serial1.println(Serial.readString()); // send from bluetooth to serial
  }
}

But if I apply this to my code, I still can't get it to work.

Before I try to hack this together, why am I getting serial to work across 2 different serial channels? Weird...

Answer 1

Okay, so I figured it out. (I can't say I fully understand, but maybe this will help people in future.)

1. Unable to connect to module

Thanks @ukBaz for suggesting I connect with the terminal app on my phone, this allowed me to debug the connection to the module in the first place. and @Juraj for suggesting that the Mega uses hardware serial.

Serial1 apparently is broken on my board, so I am using Serial3. I bluetoothed to the device with my phone, and was able to send commands back and forth between Serial and Serial3 both on 9600 baud rate. Here is the code I used:

void setup() {
  Serial.begin(9600); //open the serial port to PC
  Serial3.begin(9600); //open serial port to HC05. TX -> 15, RX -> 14
}

void loop() {
  if(Serial3.available()){
    Serial.print(Serial3.readString()); // send from serial to bluetooth
  }
  if(Serial.available()){
    Serial3.print(Serial.readString()); // send from bluetooth to serial
  }
}

I suspect I was using the wrong read/readString and write/print/println for my purpose initially.

2. Unable to issue commands to the module

Once I got that working, I changed the baud rate to 38400, and tied the STATE pin of the module to VCC (rather than using the button). Uploaded code, disconnected 5V, reconnected 5V, reset arduino.

At that point, I could issue "AT" to the module via Serial Monitor, and receive "OK" back. Woohoo!

I think I understand now that @hlovdal was suggesting that I was issuing a command to the module and never parsing a response I got, so it was.. clogged parhaps? In any case. I can now successfully issue commands and receive responses from the module.

Thanks everyone for your help.

Answer 2

There are some problems with how you are communicating AT command lines to your device. For instance:

hc05.write("AT");
delay(1000);

You do not send an AT command to a modem, you send an AT command line that contains zero or more AT commands, followed by a command line terminating character (that always should be '\r', aka carriage return (or <CR>)).

You are missing that terminating character here, so the modem will never send you a reply, because you have not sent it a command line.

And also, you should never, ever use delay as a substitute for reading and parsing the responses that the modem sends back. See this answer for some more details.