elaw wrote:Hey... has anyone successfully done a firmware update using this type of setup?
I tried to update my MS3 to the latest beta yesterday and it was NOT interested in working. The firmware uploader didn't recognize the bluetooth com port, either via autodetect or when I manually entered it.
Problem easily solved by hooking up a cable, but just wondering what others' experience has been with this?
The module's PIO11 (Pin32) is a mode selection pin to swith between normal mode and AT command mode. In the application schematic, it is connected to a button S1. When it is press down the module enter AT command mode, it come back to normal mode if the button is released. Note that, when the link is not established, once the module enter AT command mode, it will not come back to normal mode until link established or send a AT+RESET command or re-power the module.
Use the cheaper EGBT-046S if your application will
connect to a master Bluetooth device, such as PC
or laptops. Use the EGBT-045MS if your application
must connect to a slave Bluetooth device, such as
with EGBT-046S. Note that EGBT-045MS will work
as well as a slave Bluetooth device
Slave - EGBT-045MS acts as discoverable wireless
UART device ready for transparent data exchange.
Master - Scans for a remote bluetooth (slave) device,
pairs, and setup connection for a transparent
data exchange detween devices
Slave-Loop - Data loop-back Rx-Tx. Used mainly for
Users browsing this forum: Bing [Bot] and 2 guests