in [https://www.sparkfun.com/datasheets/RF/BlueRadios_ATMP_Commands_Rev_3.5.2.1.4.0.pdf][1]
You might be refer the following sentences.
First your arduino boards' UART TX/RX/GND pin to BlueRadio's RX/TX/GND connect.
and you programming the arduino board uart to 9600 baud, 8bit,N (no parity)
It's HW setup. also, You can first setup your BlueRadio module with PC UART.
Blockquote
Embedded testing:
For the DB9 (RS-232) connector, connect the TX(2), RX(3) and GND(5) to the embedded computer or micro
controller. If you are not using hardware flow control, connect RTS(7) to CTS(8) on the DB-9 connector. When
connecting the TX and RX from the DB9 connector, you cannot connect/short the CTS and RTS at terminal J4
these are two different circuits.
Blockquote
And in your arduino or in your PC Serial program,
UART.send("ATFRST\r\n");
// and wait "OK" or "ERR"
UART.recv(buf);
if (strstr(buf, "OK") )
{
// ok factory reset
}
do like this way , you refer the following document's AT command lists.
The advertisement packet your beacons send can contain custom data. However the space is very limited, around 31 bytes. About 16bytes of it goes to the 128bit "service UUID" of your beacon. The structure of the packet is defined by the bluetooth spec and it does have some overhead, so I'm not sure how much is actually available for the custom data.
The service UUID is an identifier which your iphone app will search for. The idea that each service has a unique identifier, so if an app wants to find heart rate monitors, it will scan for the heart rate monitor uuid. In iOS you can even do a wildcard scan, and it will return any ble advertisements it can find, regardless of the services it has. It is however recommended by Apple guidelines that you specify the service UUID.
There is no requirement for pairing in order to receive the advertisment packets from the beacon. There is also no theoretical limit that would prevent that the beacons couldn't be found, given an infinite amount of time.
I haven't heard anyone putting 500 advertising BLE beacons in the range of an iPhone to see how many it can detect. With 500 beacons advertising simultaneously there will be a lot of collisions between packets. This could theoretically be calculated with knowing the advertisement interval.
The iPhone scan window (how long the channels are actively listened to) and scan interval (how often the scanning window is entered) cannot be adjusted, isn't documented and cannot be relied to remain the same between versions. This means that there isn't a way to really calculate how the advertisements will be found.
There's some recommendations published by Apple about advertising: https://developer.apple.com/hardwaredrivers/BluetoothDesignGuidelines.pdf
Oh, and by default iOS will filter the results so you get one notification per scan session, per beacon. You can set the "allow duplicates" option in the scan to get multiple notifications per scan session for each beacon if this is needed, but again, apple doesn't recommend it.
If you end up testing this with 500 beacons, or even > 10, I thin a lot of people would be interested in your results. I personally would also appreciate hearing about your experiences.
Best Answer
Well since both products are manufactured by the same company, you should ask them.
However, using my experience, albeit with a different set of products, from a different manufacturer, this is exactly how I did initial testing.
Perhaps they have a development board you can try out first, before committing a custom design to a PCB?
The complex libraries are the results of someone else's hard word. If you want to use this product, then dig into, and understand them the best you can. Spending some time and effort learning the existing libraries will almost always save you more time and effort in the long run. It will often also open up new pathways for future development of your system, perhaps in ways that you did not anticipate.
There are times when you will find that it's better to re-create the wheel. It's my opinion that it's better to learn the existing tools first, so one can then make an informed decision.
Often times the module manufacturer will have a set of libraries for uC's that require minor adjusting for your platform of choice. You should contact them.
Good luck!
Some hacked test code below (python), where I'm searching for specific Bluetooth devices from a desktop computer using the manufacturer's Bluetooth development dongle connected via a virtual com port: