Hi! Recently I got an HC-05 Bluetooth module and an Arduino nano (check my previous post)!
I wanted to change the name, using this tutorial:
[iurl=https://create.arduino.cc/projecthub/akshayjoseph666/change-the-name-and-password-of-hc-05-bluetooth-module-826db5]Change the Name and password of HC-05 Bluetooth Module - Arduino Project Hub
[/iurl]I double checked everything, connections, code, bluetooth module but it didn't work!
And yes it is in AT mode.
Connected Tx-Tx Rx-Rx, Tx-Rx Rx-Tx, it didnt give any respond when using serial monitor.
and I tried using serial print in the code, THAT DIDN'T WORK
Please help!
I double checked everything, connections, code, bluetooth module but it didn't work!
And yes it is in AT mode.
"it didn't work" doesn't help us much.
Do you see "OK" to a simple "AT" with CR/LF?
Is the module powered with 3.3v (like in the tutorial) or 5v?
If I power it with 3v and the enable in with 3v then it won't even turn on, no "OK", even after the "AT" command.
If I power it with 5v and the enable pin with 3v then it works perfectly, but still cannot send, receive commands
If I power it with 5v and the enable pin with 3v then it works perfectly
What does this mean?
but still cannot send, receive commands
No "OK" to an "AT" or no name change.
If I connect the Vcc pin in the module and the enable pin to the 3.3v it works fine.
But, if I connect the Vcc pin to 3.3v and the enable pin to 3.3v or 5v, it doesn't work
it ONLY works if it gets 5v on the Vcc pin.
And if I type AT there is no response, no anything. (and yes its set to 38400 and is set to both NL and CR )
I use pins 10 and 11 with SoftwareSerial --
You may want to try following Martyn Curry's procedure using software serial and a programmed Arduino instead of the serial pass through method.
http://www.martyncurrey.com/arduino-with-hc-05-bluetooth-module-at-mode/
There are several other tutorial available by him through his website, and there may be differences between the different versions of the modules.
5v on Vcc and 3.3v on enable is correct.
rego0116:
Connected Tx-Tx Rx-Rx, Tx-Rx Rx-Tx, it didnt give any respond when using serial monitor.
and I tried using serial print in the code, THAT DIDN'T WORK
Connect Tx>Rx and Rx<Tx.
Transmitters transmit to receivers. Receivers don't hear anything from other receivers.
Connect Tx>Rx and Rx<Tx.
Normally, this is correct. However in this case, based on a tutorial which uses the Arduino's on-board USB-to-TTL converter to directly connect to an external serial device and bypasses the processor chip, the connection is TX>TX and RX>RX.
See this discussion here
https://create.arduino.cc/projecthub/PatelDarshil/ways-to-use-arduino-as-usb-to-ttl-converter-475533
Tx AND Rx CONNECTIONS
Normally, when connecting two serial devices together, the Tx pin of one device is connected to the Rx pin of the other device (and vice versa). HOWEVER, for this project (i.e. using the Arduino's on-board USB-to-TTL converter to directly connect to an external serial device), we actually want to connect the pin labelled as "Tx" on the Arduino board, to the external device's Tx pin, and the Arduino board's "Rx" pin to the device's Rx pin.
This is because the Arduino board pin labelling is from the point of view of the Arduino's ATmega32 processor, which we are bypassing for this project. If you look at a schematic of an Arduino UNO (or compatible) board, you will see that the Arduino "Tx" pin is, indeed, connected to the ATmega32's Tx pin, but this, in turn, is connected to the Arduino's on-board USB-to-TTL converter's Rx pin (so that the USB-to-TTL converter Rx pin is connected to the ATmega32 and Arduino board Tx pin - as it should be). Similarly, the Arduino board Rx pin is connected to the ATmega32 Rx pin and the USB-to-TTL converter's Tx pin.
Therefore, for this particular usage, the connection between the Arduino and external serial device goes against normal convention, and we connect Tx to Tx and Rx to Rx, because we are not actually using any Arduino sketch to allow the ATmega32 to communicate with the external device; rather, we are using the Arduino on-board USB-to-TTL converter to communicate directly with the external serial device. Your three different methods each cause the ATmega32 chip to be completely bypassed.
Gee, is that relevant to connecting an HC-05 to a Nano? God, I hope not...
This has come up before. It is so confusing that I have never finished reading it. I suppose I really need to check just what project PatelDarshil is talking about.