Peli de Halleux
|
1d47b4de0d
|
Lightmonster (#346)
* fixed boardname issues
* refactored servo info
* coffee cup monster lesson skeleton
* display event source id / value in advanced section
* normalized project structure
* updated project name
* Update projects.md
|
2017-01-31 08:29:25 -08:00 |
|
Peli de Halleux
|
46281c3cd0
|
fixing broken links in docs
|
2017-01-06 06:12:39 -08:00 |
|
Peli de Halleux
|
a59394646c
|
fixed docs
|
2017-01-05 07:37:46 -08:00 |
|
Peli de Halleux
|
2da0cf1178
|
support for buffer signature (#325)
|
2016-12-23 08:58:38 -08:00 |
|
Peli de Halleux
|
96d354a8a8
|
Merge pull request #316 from OwenBrotherwood/patch-1
Correction for max. length of advertised url to 17
|
2016-12-09 15:13:12 -08:00 |
|
Peli de Halleux
|
3469ad6f8d
|
Added note about protocol encoding.
|
2016-12-08 12:01:35 -08:00 |
|
Peli de Halleux
|
03c0339e9a
|
fixing docs snippets
|
2016-12-08 09:16:27 -08:00 |
|
Owen Brotherwood
|
30211aa006
|
Correction for max. length of advertised url to 17
https://github.com/google/eddystone/tree/master/eddystone-url#frame-specification states 1-17
When one makes a general google for the max length, some have written 18 and some 17 :(
The difference could lie in the https://github.com/google/eddystone/tree/master/eddystone-url#url-scheme-prefix which adds an extra byte but it's use is to in someway allow for more bytes in the 1-17.
The implementation in the micro:bit Lancaster is unknown as to how the url-scheme-prefix is or is not used: there does not seem to be a scheme for "Just take the 1-17" for the url.
At the moment, "play it safe" and write 17 ?
|
2016-12-06 20:51:44 +01:00 |
|
Peli de Halleux
|
adef3a6487
|
updated docs
|
2016-11-30 04:19:17 -08:00 |
|
Peli de Halleux
|
be0984cc4a
|
integrating eddystone into bluetooth package
|
2016-11-30 04:06:15 -08:00 |
|