I want my HC-05 module to connect bluetooth keyboard as master.
So, after reading http://eskimon.fr/wp-content/uploads/2014/10/commandes_AT_HC05.pdf and few tutorials i've done something like this:
AT+ORGL
OK
AT+RMAAD
OK
AT+ROLE=1
OK
AT+INQM=0,3,48
OK
AT+CMODE=0
OK //There i've tryed to AT+RESET device, but it makes no difference.
AT+INIT
OK
AT+INQ
+INQ:C473:1E:69A2C1,8043C,7FFF
+INQ:6C5D:63:4099E0,2540,7FFF //AT+RNAME of this device returns "bluetooth keyboard".
+INQ:1C7B:21:75618C,5A020C,7FFF
OK
AT+PAIR=6C5D,63,4099E0 //There I type "1234" and press enter on keyboard.
OK
AT+BIND=6C5D,63,4099E0
OK
AT+LINK=6C5D,63,4099E0
FAIL // There module starts re-inq devices.
Last command returns "FAIL" realy quckly, almoust with no delay, wich is strange, i guess. Ive tryed to press little button on keyboard, marked as "Connect" while linking, but it makes no difference. I've also tried to Link to the phone. It's successfully paired, but failed to link again.
EDIT:
I've unpaired my keyboard from phone, and HC-05 module begin to think a little, before return FAIL. Idk why it would make a difference. Any way, i become to think this is bluetooth versions issue. Keboard have v3.0 and HC-05 have 2.0+ version. But im sure all BT version must be back compat, are'nt they?
If anyone else runs into same idea:
I found out, that HC-05 and similar modules implements SPP bluetooth profile, whereas keyboard using HID profile, wich is more secure and complicated. So, i guess this is impossible to do via HC-XX modules.
Related
So, I'm trying to connect to a custom board using ST-Link. My board uses STM32 Microcontroller and I use ST link utility software to see if I can connect to it.
Right now, If I press connect on utility software and press reset on my board at the same time, the connection is successful. But as soon as I remove my finger from the reset button the connection to the device is lost. Is this expected? And how can I make it stay connected without me keeping the reset button pressed!
Also, assuming I keep pressing it, the utility software gives me an internal command error when I try to erase chip. this happens when I try to program the chip as well.
Any suggestions are appreciated.
So the way to resolve the issue was to pull-up the NRST pin on the board and st link and disconnect it after pressing the reset button.
I still have not found a solution for erasing the chip but I believe the flash is protected. When I try to change the Option Bytes in st link utility, it disconnects from the board saying:
Could not set Option bytes!
Please reset the target and retry!
And then disconnects from the device.
Any clues how I can change the options bytes? That might actually solve the problem!
Thanks
By my experience all of such this problems come from bad assembling one way that may help you to find out first put a light in the back of your PCB right under your micro-controller and see if any pin is outside of footprint if it is aligned correctly,gently press your micro to the PCB and and test if it is disconnecting if it solves your problem then some of pins are not soldered correctly
Goodmorning,
I'm working quite hard on my own app. At this point I want to run it on my android (galaxy note 3) phone. Unfortunately Appcelerator studio doesn't detect my android phone; Windows does. I've tried it with the new Galaxy s7 of a friend, but same result.
Off course I searched the web like crazy and found several possible (old) answers, but none did the magic.
When I consult the log, there's no new info to be read!
Does anyone have a clue where to look? Looking forward to your answers…
Kind regards!
One thing you should check is if you have set up your phone for development. You can see the instructions here: http://developer.android.com/tools/device.html (... tap 7 times... - took me a while to discover!)
And the small obvious thing is in Appcecelerator Studio you may need to select "Refresh devices" when you try to run the project.
/John
When you say "Windows" detects it, what exactly do you mean? Does adb detect it?
If you run
adb devices
on the command line, does it report your device ID?
On my Mac, I run this and I can see my connected S4:
List of devices attached
9726ea90 device
I'm assuming that the Windows version of adb would output a similar report.
With all the Samsung phones I've debugged with, I always have to go to the notification bar and choose "connect as media device" (or something similar). The default connection mode does not work for debugging. And unfortunately, you have to do this every time you connect the device.
I got the email back from Google and they said they have, but having trouble getting it to show up under devices using some of the example code they provide, but now wondering if maybe I gave them the wrong serial or something and it really hasn't been white-listed.
You can always email them with the developer ID (Should be in the email), app ID, and your serial # to have them check. One thing I learned, though (when experiencing the same thing), was that I forgot to configure my chromecast with the "send this serial # to Google when communicating about updates" flag. If that isn't checked, then your Chromecast can't be notified that it is allowed to communicate with your app id. Also note that the Chromecast Android app had a bug (don't know if today's update fixed it) where setting that flag wouldn't stick, so I had to do it through the desktop app and then reboot the Chromecast and wait a few hours for the next time it pinged Google.
Make sure you have the "Send this Chromecast's serial number when checking for updates" setting enabled using one of the ChromeCast setup apps for your OS or Android. And reboot your ChromeCast device after enabling that setting.
You should be able to open Chrome and enter http://[ip.to.chrome.cast]:9222 in the browser address field. If your cromecast device is whitelisted the page will open.
I got a letter in the mail that contained a small USB device. Here is what it loks like: http://imgur.com/a/VEtNK
When I plug it into my computer it seems to hover over the programs in my Dock and then opens one. It then types a link into a text field that is available. I originally had Skype in the dock and it defaulted to that one, strange. I removed Skype from the dock and now it opens to System Preferences.
Here's a video of what happens as I plug it in: https://www.dropbox.com/s/yuw6ggvo77rkvwh/Test1MysteryDevice.mov
Also, it does not appear like a memory stick does on my computer. I can't seem to locate it when it's plugged in. It would be cool if I could find it somehow. It would be even cooler if I could program it to do something I wanted.
Thanks, and if anyone can help out that's awesome or if you could point me to a forum/anywhere that might be able to help out, that'd be great!
Probably it self-identifies as a HID (Human Interface Device), specifically a keyboard. As soon as it is accepted as a keyboard by the OS it can send any sequence of keystrokes, and the OS will assume that it is input from a human user.
Scripting such behavior is easy using Applescript.
However automatically running a program from a USB stick when it is inserted is supposed to be impossible on OS X, as auto-run is a security risk.
Of course at the very least a custom USB device could be made to act like a mouse and keyboard, so even without autorun it's a risk to plug strange devices into your computer.
To get more info on the device you can go to System Profiler and look for the device on the USB bus.
If it is a custom device pretending to be a keyboard then it's probably hardwired to do what it does, and you probably won't be able to reprogram it; you'd need to find a manufacturer that will sell you customized devices.
I have a piece of hardware that we created that connects to my PC via USB. We also wrote the drivers for it. EVERY time I plug this device in, the new device message comes up, even though the drivers are installed. I can cancel the dialog and it works fine, but it looks like crap and I'll be selling this product and want it to function like other USB products and only throw this dialog up once.
How do I make this happen?
Do you have all of the USB device descriptor fields populated in your device? Specifically, I am asking about the serial number field.
http://blogs.msdn.com/oldnewthing/archive/2004/11/10/255047.aspx