Refer to question: Get MAC address of bluetooth low energy peripheral
We have board where we have kept MAC id in encrypted form in advertisement packet and reading those MAC-id in our iOS App. Since Apple actually suppress MAC id information for BLE device Will it be problem (App rejection) if manufacturer puts this in packet and app reads it?
Related
Is there any way for a Peripheral to get a Central device's name when establishing a bluetooth connection (BLE)? I'm unsure if Bleno has the tools necessary to get this.
Just read the Device Name in the remote GATT server. The peripheral must support GATT client in order to be able to read the device name.
I am amateur for GATT and ble.
I am using Linkit one board as central device and Nrf51 board as peripheral device. Central device successfully connecting with peripheral device, able to seach all Services UUID, Characteristic UUID, but it fails to read the characteristic value. Value which display on Linkit side it is not same as mentioned in nordic side.
I am able to get the characteristic value in nordic app and as well as nordic board as an peripheral device.
Linkitone as central device fails to read TX characteristic value of nordic uart service from any peripheral device. Even when I tried Linkitone as peripheral device and try to read the Nordic uart service value by nordic app, it fails. App get hanged every time.
Below I mentioned the value which gave to tx characteristic the value which is getting on central side. So is there any problem with Linkitone board with ble UART service or there is any different reason for this?
My requirement is as follows:
I need to send Proximity Sensor (Reed Switches/Magnetic Sensor) reading (On/Off) from two Input Pins to a central PC.
I need to use coin cell. So basically the app should be in sleep mode and once there is any interrupt on any of these two pins it should wake up to send its state to the central PC.
I have DA18450 chip and development board (murata ZY type) with me.
Dialog Semiconductor 18450
Murata Bluetooth Smart Development Board
I am a beginner to bluetooth technology and started reading about it just a week back.
Could someone guide me about the most apt Profile/Service suitable for my application?
If you want the device to actually sleep then it'd probably be best for it to just transmit data via advertising packets when the device awakens. Otherwise you have to maintain a connection which requires staying awake at some level. However, advertising packets are broadcast and the device can't know if anything received those packets (you could have it broadcast several times for a fixed period of time or have it constantly broadcast while the proximity alert is valid). Also, on the receiving end, with no connection there's no way of knowing the transmitting device is even there when nothing is being transmitted.
The advertising packets have a section for limited information and that's where you'd transmit data if you don't want to establish a connection.
I’m building an application in which a smartphone needs to communicate with a peripheral over Bluetooth Low Energy but I’m having a hard time coming up with the right GATT service/characteristic structure for this communication. The phone and peripheral need to communicate with each other over a “custom protocol” containing multiple send/receive messages. What I mean with this is that he phone will send something to the peripheral (step 1 of the protocol), which will respond to this by sending a message to the phone (step 2 of the protocol), which will respond to this by sending the next message to the peripheral (step 3 of the protocol), etc. until the protocol completes (after let’s say 10 steps).
Should I make a new attribute for every step of the protocol I want to execute, i.e. have the phone write to an attribute “protocol1” and have the peripheral notify the phone with an attribute “protocol2” after which the phone writes “protocol3”, etc. Or should I use only 2 attributes for this: one for the phone to write to (TX), and another one for the phone to read (RX) through notifications? It seems that BLE (instead of Bluetooth 3.0) wasn’t really made for this kind of RX/TX communication, or am I wrong?
Two Characteristics, one for TX and one for RX should be enough.
Use Characteristic Write for TX and Characteristic Indication for RX.
I want to know a method in Win32 to get the device manufacturer name attached with the serial port.
I have already tried the SetupDiGetDeviceRegistryProperty API with the SPDRP_MFG
option but getting manufacturer name which is mentioned by the driver. What I want manufacturer name associated with the device not with the driver.
My Device is a USB device and appearing as a USB Serial Port(COM4) in the device manager.
Thanks
A serial device does not send this type of meta data to the computer. There is no hand-shaking done like in a USB connection where the device identifies itself. With a serial device, the computer just starts sending or receiving data.
Run the USBView sample which comes with the WDK to get the manufacturer name and other information about the USB devices.