Closed samueleforconi closed 9 years ago
Great! Have you used the Validator App to make sure the beacon follows the spec?
Hi, we are planning to carry out the tests within the next days because we are currently lacking an Android phone with BT4.0. We have already tested our UriBeacon FW implementation with the Physical Web app and with other iOS apps available on the App Store. I hope we can make tests with the Android Validator App in the next days. I'll post our test report as soon as we carried out tests with the Android Validator App.
Great! Let us know if you have any problems.
On Thu, May 7, 2015 at 12:55 AM Samuele Forconi notifications@github.com wrote:
Hi, we are planning to carry out the tests within the next days because we are currently lacking an Android phone with BT4.0. We have already tested our UriBeacon FW implementation with the Physical Web app and with other iOS apps available on the App Store. I hope we can make tests with the Android Validator App in the next days. I'll post our test report as soon as we carried out tests with the Android Validator App.
— Reply to this email directly or view it on GitHub https://github.com/google/uribeacon/issues/237#issuecomment-99759793.
Hi, we are trying to run the UriBeacon-Validator app on a Samsung Galaxy S4 phone running Android 4.4.2 but we the app stops immediately as soon as it is launched. Is there a special procedure to run this app? I have also tried to download the source code, recompile and run, but with no luck.
Sadly the validator app only works on Lollipop.
On Wed, May 13, 2015, 9:05 AM Samuele Forconi notifications@github.com wrote:
Hi, we are trying to run the UriBeacon-Validator app on a Samsung Galaxy S4 phone running Android 4.4.2 but we the app stops immediately as soon as it is launched. Is there a special procedure to run this app? I have also tried to download the source code, recompile and run, but with no luck.
— Reply to this email directly or view it on GitHub https://github.com/google/uribeacon/issues/237#issuecomment-101726047.
Hi, we have tested our beacons using the Validator App and the Nordic nRF Master Control Panel. The Validator App fails the last 3 tests, but I can't figure out why...
With the nRF Master Control Panel we are able to detect the URI Beacon, read and write its characteristics values correctly.
FYI & Open Source: http://www.embeda.com.tw/ucxpresso/?article=2-3-google-uribeacon-project
It seems that the problem isn't with configuring the beacon, but rather with the adv packet. From the screenshot it seems that the values written are not being broadcasted. The Validator wrote "0" for flags and was expecting to read a "0" from the adv packet but instead got a "1". Same for the rest of the fields.
Those numbers that are being output in the last test on the validator app spell out "http://www.blue-up.it" which I suspect the validator isn't expecting. So I wonder if it is the write that is failing.
Yeah. The values the validator wrote in the previous steps are not being broadcasted.
Ok, but why if I write those values using the Nordic nRF Master Control Panel or other apps (i.e. LightBlue for iOS), the values are correctly written and broadcasted in the advertising packet? I have just tried to configure the beacon with a different URI, TxPower Mode, Period, etc... and the advertising data is correctly set in the advertising packet (I checked the new URI with Physical Web app).
In my understanding, the Validator is trying to set URI Flags to "1" and receives "0", then for Tx Power Level it tries to set "0" and receives "-28", the same for the URI data.
With other apps the beacon configuration works correctly, what kind of write operations does the Validator app perform?
Do you have to update the adv. data after to configure your beacon? If yes, and How to?
Interesting. If I had to guess either Lock/Unlock or Reset is not implemented correctly. The other option is that you have beacons with the same address around so the validator gets confused.
You could try the following to see if you still fail the tests:
This should skip Lock/Unlock and Reset.
Hi, I've finally solved the issue with our UriBeacons and the UriBeacon Validator App. The problem was caused by the Reset characteristic that in our implementation was applied after the disconnection with the Central. Now our UriBeacons seem to be compliant with the specification. We hope to become part of your UriBeacon suppliers list. :)
That's great! Do you have a link to your website where one could find UriBeacons?
You can find on this page all our beacons for sale: http://www.blueupbeacons.com/index.php?page=products
Done :smiley:
Closing this issue. Let us know if any part is unresolved. Thanks!
Hi, I'm the co-founder of an italian company, BlueUp ( http://www.blueupbeacons.com ), that is involved in BLE Beacons development and production. We already have a catalogue of iBeacons devices (entirely designed and made in Italy) and now we are about to launch also some UriBeacons products. We have completed the development of the firmware for our device, so within a few days we should have the BlueUp UriBeacons in our catalogue. I wonder if it's possible to use the UriBeacon logo on our web site and link the UriBeacon Specification.
Would it be possible for you to include our company in the list of the UriBeacons manufacturers on the main GitHub UriBeacon page?
Thanks.
Regards, Samuele.