[help needed] HOWTO use Bluetooth module

[opelpanfan]

If anyone has an issue accessing JDY-31 using putty.

4afab98f1db9d61bbc477d42b3c4ff55.jpg

You can try Arduino IDE serial monitor:

image.png

Also tried to use Serial Port Utility and it works as well.

image (2).png

Link to windows software: https://wiki.wit-motion.com/english/lib/exe/fetch.php?media=serial_port_utility.rar

serial_port_utility.zip

Spec and AT command sheet can be found:

http://myosuploads3.banggood.com/products/20190129/20190129043725SKUA87502.pdf

[AndreyB]

Weird, how come?! Wonder which settings are we not setting in Putty to not have it working

[opelpanfan]

Maybe default Flow control?

image.png

Putty defaults to XON/XOFF

[AndreyB]

Wow that Serial Port Utility has done the trick for me! Got "AT+VERSION" response from my JDY-33

image.png

[AndreyB]

If anyone has an issue accessing JDY-31 using putty.

4afab98f1db9d61bbc477d42b3c4ff55.jpg

It's a small world. It has Beken BK3231S chip see https://rusefi.com/forum/viewtopic.php?f=13&t=1999 where JDY was not mentioned

And JDY-33 sometimes says BK3432 https://www.bekencorp.com/en/goods/detail/cid/17.html

[AndreyB]

Anyway there is also JDY-40 based on BK2461

And then there is https://www.elektroda.com/rtvforum/topic3758492.html calling all these clones of NRF24L01 ?

[jlowens76]

Weird, how come?! Wonder which settings are we not setting in Putty to not have it working

it has to do with the end of line characters, the correct ones aren't sent with the apps that don't work, you can play with them and see which specific that work by using arduino serial monitor and changing them, seeing which work and which dont then trying that in the other apps.

I used arduino serial monitor for a bit till i got tired of that and started using RealTerm

image.png

lets you specify if your sending numbers/vs ascii, pick EOL characters, and \n

image.png

[scfrontier]

I just fixed a bug relating to the initialization of our bluetooth modules (using RUSEFI console commands). When a baud rate change was requested, we were trying to connect at the new baud rate instead of the current "working" baud rate. This was reporting back to the console as a NAME change failure. Now we connect at the working baud rate - then make changes - reset - find working baud - repeat...
Hope this helps.

[AndreyB]

Current status with a questionable chip:

Code: Select all

2024-06-26_12_13_28_844: EngineState: confirmation_bluetooth_jdy 115200 alphax 1234:32
2024-06-26_12_13_29_191: EngineState: *** Bluetooth module setup procedure ***
2024-06-26_12_13_32_255: EngineState: Restarting at 115200
2024-06-26_12_13_32_256: EngineState: sending AT  
2024-06-26_12_13_34_781: EngineState: Timeout waiting for BT reply after 0 byte(s)
2024-06-26_12_13_34_782: EngineState: sending AT+DISC  
2024-06-26_12_13_37_222: EngineState: Timeout waiting for BT reply after 0 byte(s)
2024-06-26_12_13_37_222: EngineState: Restarting at 9600
2024-06-26_12_13_37_222: EngineState: sending AT  
2024-06-26_12_13_37_333: EngineState: Received 5 +OK  
2024-06-26_12_13_37_333: EngineState: sending AT+VERSION  
2024-06-26_12_13_37_334: EngineState: Received 41 +VERSION=JDY-33-V1.1,Bluetooth V3.0+BLE  
2024-06-26_12_13_37_334: EngineState: sending AT+BAUD  
2024-06-26_12_13_37_335: EngineState: Received 9 +BAUD=4  
2024-06-26_12_13_37_335: EngineState: sending AT+TYPE  
2024-06-26_12_13_37_445: EngineState: Received 9 +TYPE=1  
2024-06-26_12_13_37_446: EngineState: sending AT+PIN  
2024-06-26_12_13_37_446: EngineState: Received 11 +PIN=1234  
2024-06-26_12_13_37_446: EngineState: sending AT+LADDR  
2024-06-26_12_13_37_446: EngineState: Received 21 +LADDR=1FD9C6BB0E40  
2024-06-26_12_13_37_447: EngineState: sending AT+STAT  
2024-06-26_12_13_37_447: EngineState: Received 10 +STAT=00  
2024-06-26_12_13_37_448: EngineState: sending AT+DEFAULT  
2024-06-26_12_13_37_557: EngineState: Received 5 +OK  
2024-06-26_12_13_37_557: EngineState: sending AT+ENLOG0  
2024-06-26_12_13_37_557: EngineState: Received 5 +OK  
2024-06-26_12_13_37_557: EngineState: sending AT+TYPE0  
2024-06-26_12_13_37_558: EngineState: Received 5 +OK  
2024-06-26_12_13_37_558: EngineState: sending AT+NAMEalphax  
2024-06-26_12_13_37_669: EngineState: Received 7 +O+OK  
2024-06-26_12_13_37_669: EngineState: FAIL! Command AT+NAMEalphax   failed

now sure if anything is broken here, is name officially broken due to https://github.com/rusefi/rusefi/issues/5918?

[puff]

AT+NAME=Param1 - did you miss '='?