Forum >Replies by graham
Replies （6）
- You Reply: When you get
not in sync: resp=0xNN
1) This will not work if the BLE is connected/paired to a host. Try and stop this and then upload your sketch
2) If that still doesn't work, but you can connect to AT mode via serial port (I have this problem whenever I put the Bluno in HID mode) you should be able to re-upload a sketch again by resetting it with AT+SETTING=DEFAULT - You Reply: Using the AT+ commands, 2 bluno's can connect to each other automatically (one "central" and one "peripheral") and easily send their Serial output back and forth.
But no more than 2. - You Reply: Kinda looks like this is a problem with the OSX implementation with CoreBluetooth... The demo app has the same results as my own app, but different to when debugging IOS.
I can read all the other characteristics (firmware versions, vendor etc), but just not DF01 and DF02 (as before, I can read & write one byte, but it's not what I have on my serial)
I've tried pairing with central & peripheral mode, which works, but no good for me (as I need multiple peripherals). - You Reply: Aha! I went to try the sample apps in case my implementation was doing something odd...
https://github.com/DFRobot/BlunoTest
On ios, this worked great, and I'm seeing exactly what I wrote to the serial.
Now porting over to OSX as they share bluetooth to see whether the problem lies at my CoreBluetooth implementation, or the bluetooth stack in OSX... fingers crossed it's my code that's wrong... - You Reply: I've managed to get into AT mode, so I can see I have firmware 1.97.
It's in peripheral mode, I can turn USB debug on and off, which is all fine, but the data I get over bluetooth is still just an echo of whatever I write TO the bluno.
I feel like the serial output must be going to a different service or something. The DFB1 and 2 data seem to just remember what they last were (maybe written to EEPROM as it's remembered even after a reboot)
I've tried HID mode, and have kinda made a keyboard (although a lot of the time it gets into a state where I can't reupload the sketch)
So it does communicate in SOME way. (This is slightly more controllable, so I may have to go down this direction, I just need to know when a pin is down sent to OSX, with 10 auto-connected blunos)
Maybe time to investigate the firmware to find out exactly what it's doing. - You Reply: So, reading this page (which seems to have a bit more in-depth information than I can find from DFRobot - the demo source is great, but doesn't explain any details)
http://www.lucadentella.it/en/2018/01/2 ... no-beetle/
It seems the USB serial is just a mirror/bridge, so seeing MY output in the arduino sieral monitor makes sense.
But the serial monitor doesn't respond to +++ for AT mode.
Should it? It seems like it should. Or can I only access AT commands from a bluetooth serial connection? (maybe my bluno's are not in the right mode...)
I cannot find any documentation on the difference between the characteristics DFB1 and DFB2... Are they distinct in any way?