You can set the maximum timeout using the <jap_timeout> parameter with AT+CWJAP. The "busy" prompt indicates that the system is processing the previous command and cannot respond to the current input. AT command processing is linear, meaning it can only accept the next command after completing the previous one.

Reason: The internal configuration paths are different, so it's necessary to clear the previous file configurations first.

Solution 1: Open the files in VSCode, then click on the trash can icon below to clear them, and finally recompile the firmware.

Solution 2: Delete the "build" folder in the project files, and then recompile.

That's possible; however, the standard AT firmware currently doesn't have this feature enabled. To enable this feature, you need to enable the driver's functionality in the ESP-AT framework and then recompile and flash the new firmware. (Note: SPI, I2C, PWM, and other functionalities can be used, but you won't be able to configure the pins as regular GPIOs.)

Yes, there are Modbus demo examples in the ESP-IDF code for ESP32.

The theoretical specification is 150Mbps (18.75Mbit/s), and the measured maximum speed is up to 18.65Mbit/s.

The default AT firmware does not support this feature; firmware that enables web functionality and sets the port number to greater than 12 is required for parts involving embedded web pages.

After modifying the factory_param_data.csv file, delete the sdkconfig file and the build directory,

then recompile the AT firmware and flash it.

Currently, ESP-AT only supports BLE 4.2 specifications.