Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In classic Bluetooth mode, the module will still have no data downstream, and the module will automatically recover, but the time is too long, which takes 1 to 2 minutes #808

Open
3 tasks done
aithinker2222 opened this issue Feb 29, 2024 · 1 comment
Labels
Awaiting Response awaiting a response from the author

Comments

@aithinker2222
Copy link

Answers checklist

  • I have read the documentation ESP-AT Programming Guide and the issue is not addressed there.
  • I have used the latest released firmware or have updated my ESP-AT branch (master or release) to the latest version and checked that the issue is present there.
  • I have searched the issue tracker for a similar issue and not found a similar issue.

AT+GMR

AT+GMR
AT version:4.1.0.0-dev(s-27cc2e2 - ESP32 - Jan 26 2024 08:55:46)
SDK version:v5.0.4-dirty
compile time(afa4104):Jan 31 2024 14:37:48
Bin version:v3.2.0.0(WROOM-32)

OK

ESP-AT Firmware Source

Compile ESP-AT Project Locally

Hardware Information

ESP32

Power Supply used

External 3.3V

What is the expected behavior?

Fix bugs

What is the actual behavior?

  1. In classic Bluetooth mode, the module will still have no data downstream, and the module will automatically recover, but the time is too long, which takes 1 to 2 minutes;
  2. In WiFi mode, you can search the WiFi hotspot in the notebook, but you cannot connect it.
    It needs a little more refinement
    Bluetooth reconnection time optimization to less than 5 seconds is better, WiFi this problem please check why can be found but not normal connection, is the transmission protocol has been adjusted?

Probability of recurrence

must appear

AT+SYSRAM?

AT+SYSRAM?
+SYSRAM:151936,144796
OK

Steps to reproduce

AT+BTINIT=1
AT+BTSPPINIT=2
AT+BTNAME="FJD2300181"
AT+BTSCANMODE=2
AT+BTSPPSTART
AT+BTSPPSEND

AT command port output

AT+BTINIT=1
AT+BTSPPINIT=2
AT+BTNAME="FJD2300181"
AT+BTSCANMODE=2
AT+BTSPPSTART
AT+BTSPPSEND

AT log port output

AT+BTINIT=1
AT+BTSPPINIT=2
AT+BTNAME="FJD2300181"
AT+BTSCANMODE=2
AT+BTSPPSTART
AT+BTSPPSEND
$GNGGA,,,,,,0,,,,,,,,*78
$GPZDA,,,,,,*48
$GPGSA,,1,,,,,,,,,,,,,,,,*73
$GNRMC,,V,,,,,,,,,,N,V*37
$GPGST,,,,,,,,*57
лђ   � � ��Q1 �1,А�Р �c�1 #
лђ   � � J�PFJJS01F23300181ZC               �	� ��    d9xЂ3130CH1DAZBSA00181�и �t�sр �T
лђ   � � ��тJ017.00.051011                Э
лђ   � � !�\�000000000000000000000000        �
лђ   � � ��тJ017.00.051011                Я
лђ   � � ��Rv����®tlBSA00001  �V
лђ   � � ��V  c
лђ   � 	 ��&��5
лђ   � 
 ��/��?
лђ   � � ��-��>
$GNGGA,,,,,,0,,,,,,,,*78

More Information.

none

@Luxin812
Copy link
Contributor

Recently, the master branch has fixed similar problems. You can update your firmware to the latest and test again to see if your problem is also fixed.(https://github.com/espressif/esp-at/actions/runs/8294336044)

@ustccw ustccw added the Awaiting Response awaiting a response from the author label May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Response awaiting a response from the author
Projects
None yet
Development

No branches or pull requests

3 participants