OpenEPaperLink notes: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
| Line 16: | Line 16: | ||
--> | --> | ||
<!-- | <!-- | ||
===Tag AP=== | |||
This project's idea seems to be that, | This project's idea seems to be that, | ||
since every tag has a 802.15.4 radio (its own protocol?), | since every tag has a 802.15.4 radio (its own protocol?), | ||
if you add an | if you add an microcontroller to just one of these tags (with a specific connection - the tags have a debug header), | ||
you now have a tag that can ''be'' that central checkin point of the tags, saving one more device to buy. | that takes control of it, you now have a tag that can ''be'' that central checkin point of the tags, saving one more device to buy. | ||
And since ESP32s have WiFi, you can now talk to that AP-Tag via WiFi, while ''it'' talks to the rest of the tags over 802.15.4. | And since ESP32s have WiFi, you can now talk to that AP-Tag via WiFi, while ''it'' talks to the rest of the tags over 802.15.4. | ||
| Line 46: | Line 48: | ||
===Tags=== | |||
| Line 55: | Line 58: | ||
'''Firmware''' | |||
https://github.com/jjwbruijn/OpenEPaperLink/wiki/Firmware-Updates | |||
You can do OTA tag updates from the AP's filesystem. | |||
(how do you get them there?) | |||
===See also=== | |||
https://openepaperlink.de/ | https://openepaperlink.de/ | ||
https://github.com/jjwbruijn/OpenEPaperLink/wiki | https://github.com/jjwbruijn/OpenEPaperLink/wiki | ||
--> | --> | ||
Revision as of 09:28, 30 April 2024