That's pretty nice already! But the list of commands don't look anything like the those in the official HM-10 datasheet.Īfter lots of scrabbling about on the net we eventually found this article ( ) which explains that our devices were in fact BLE-CC41a clones. We used the command AT+NAMEChrisBLE and successfully changed the name of our bluetooth device - so when a phone scans, it appears with our custom name. +VERSION=Firmware V3.0.6,Bluetooth V4.0 LEĪfter a bit of wire-swapping, we discovered that the device is entirely 5v tolerant, and runs just fine off a usb-to-serial adapter, running at 5v without any external power supply, nor requiring any level shifters on the tx/rx lines. Note: (M) = The command support slave mode only.įor more information, please visit All rights reserved. The silkscreen on the back of the device says it needs a 3.6v-6v power supply, but the TX/RX pins are labelled with a legend saying level 3.3vĪT Check if the command terminal work normallyĪT+VERSION Get firmware, bluetooth, HCI and LMP versionĪT+IMME System wait for command when power on. We had the curious EN pin, and tried with that pulled high, pulled low and left floating, and still nothing worked. It didn't help that different online sources suggest trying them at different baud rates. Getting the device to respond to AT commands was problematic at first. Like many of these kinds of plug-n-play type modules, interfacing with it is relatively simple, but there are a couple of gotchas to be aware of to get it up and running reliably. As it turned out, the outer pins are not strictly needed to make the device work (though it took a lot of messing about with the pin labelled EN - looking like an enable pin - before we worked this out and got any kind of response to our AT commands)
Our device had a six-pin connector rather than the four-pin shown. The first thing, when using a module like this, is to try out some straight-to-serial AT commands.
0 kommentar(er)
