<!DOCTYPE html><html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /></head><body><div data-html-editor-font-wrapper="true" style="font-family: arial, sans-serif; font-size: 13px;">Hi All<br><br>Grant and others have been doing some great work recently.<br><br><a target="_blank" rel="noopener noreferrer" href="https://github.com/sudomesh/disaster-radio">https://github.com/sudomesh/disaster-radio</a><br><br>There's been a code refactor and a bunch of new features added<br><br>* Routing table is printed beneath the webapp<br>* HistorySD records history to SD card<br>* OLEDClient: displays messages on the screen<br>* You can set a WIFI_SSID and WIFI_PASSWORD to try to connect to, and if it fails it falls back to AP mode<br><br>There is some experimental, and I think largely untested support for new boards:<br><a target="_blank" rel="noopener noreferrer" href="https://github.com/sudomesh/disaster-radio/blob/master/platformio.ini#L33">https://github.com/sudomesh/disaster-radio/blob/master/platformio.ini#L33</a><br><br>* Tbeam (with GPS) <a target="_blank" rel="noopener noreferrer" href="https://www.aliexpress.com/item/33046632533.html">https://www.aliexpress.com/item/33046632533.html</a><br><br>* Heltec V2 <a target="_blank" rel="noopener noreferrer" href="https://www.aliexpress.com/item/32909141441.html">https://www.aliexpress.com/item/32909141441.html</a><br><br>* Lopy <a target="_blank" rel="noopener noreferrer" href="https://pycom.io/product/lopy4/">https://pycom.io/product/lopy4</a> - Which should be compatible with <a target="_blank" rel="noopener noreferrer" href="https://pycom.io/product/pygo1/">https://pycom.io/product/pygo1</a> once released<br><br>I'm going to have a go with getting it running on <a target="_blank" rel="noopener noreferrer" href="https://m5stack.com/collections/m5-core/products/face">https://m5stack.com/collections/m5-core/products/face</a><br><br>Of course, there remain plenty of meaty bugs to get stuck into;<br><a target="_blank" rel="noopener noreferrer" href="https://github.com/sudomesh/disaster-radio/issues">https://github.com/sudomesh/disaster-radio/issues</a><br><br>If anyone was up for testing some of the new boards that would be interesting..<br><br>Thanks<br><br>Sam<br><br><br><br><br>November 30, 2019 3:15 AM, "grant" <<a target="_blank" rel="noopener noreferrer" href="mailto:ggallo102@gmail.com">ggallo102@gmail.com</a>> wrote:<br> <blockquote>fyi...<br><br><a target="_blank" rel="noopener noreferrer" href="https://github.com/sudomesh/disaster-radio/releases/tag/0.1.0">https://github.com/sudomesh/disaster-radio/releases/tag/0.1.0</a><br><br>The aforementioned workflow is now a reality, just download `disaster-radio-0.1.0.zip` from the<br>releases page and follow the instructions in the README.<br><br>I encourage anyone with an ESP32 TTGO board to give it a try and let me know if there are any<br>issues.<br><br>Good luck!<br><br>-grant<br><br>On Tue, Nov 26, 2019 at 3:55 PM grant <<a target="_blank" rel="noopener noreferrer" href="mailto:ggallo102@gmail.com">ggallo102@gmail.com</a>> wrote:<br> <blockquote>It is not difficult to create binaries, I have to create them every time I test a change to the<br>firmware. And yes, providing binaries could make it easier. It means that you wouldn't have to<br>install the entire toolchain and compile the firmware from scratch. You would just need to install<br>esptool (or another serial flashing tool) and upload the binary to the ESP.<br>You are correct that the `web/static` files created are the same every time (assuming that you did<br>not make local changes before creating them). However, it is not typical to track `bundle.js` in<br>github commits because it is an auto-generated file and would dirty the commit history will lots of<br>redundant, unreadable diffs.<br><br>The proper way of providing a both the binaries and the `web/static` files is to upload them with a<br>release. Then someone who purchases a TGGO board (or LILYGO before they ship the boards) would<br>download the latest realease as a zip file containing the necessary files and a README with easy to<br>follow instructions of how to put them on your ESP.<br><br>I'll work on making this work flow a reality.<br><br>And, I like the idea of a message ticker. Or at least some sort of notification when a message is<br>received?<br><br>-grant<br><br>On Mon, Nov 25, 2019 at 5:37 PM <<a target="_blank" rel="noopener noreferrer" href="mailto:samuk@disroot.org">samuk@disroot.org</a>> wrote:</blockquote><br>Thanks Grant<br><br>I would like to tag a release (0.0.1?) and provide them binaries so that they are shipping it<br>with firmware from a<br>particular commit. They should also be able to flash the SPIFFs with the web app, we could<br>provide<br>binaries for that as well. Then, you wouldn't necessarily need an SD card.<br><br>Sounds great, would it be a lot of work to create the binaries? Would make for an easier install<br>whether or not we decide to allow Lilygo to sell directly.<br><br>then copy the contents of<br>web/static (`index.htm` and `bundle.js`) to the SD card. It's a fairly straightforward process,<br>but<br>I should create instructions.<br><br>Presumably these files are the same each time they are created? So we could just upload the<br>compiled versions to Github for users to drag/drop onto a SD?<br><br>This group generally operates on a consensus basis, so I'd be interested to hear what other<br>people<br>who have been involved in its development think.<br><br>Great, would be good to hear from anyone who has concerns. The way I see it is that this wouldn't<br>slow down or hinder efforts to create open hardware, but I realise others may have a different<br>view.<br><br>p.s. I would also be cool to display something on the OLED screen when it ships, haven't gotten<br>around to that idea though.<br><br>A scrolling ticker of the most recent messages would make the device usable without an additional<br>device. Probably over complicated for now though..<br><br>2p<br><br>Sam<br><br><br>-grant<br>On Sun, Nov 24, 2019 at 9:23 AM <<a target="_blank" rel="noopener noreferrer" href="mailto:samuk@disroot.org">samuk@disroot.org</a>> wrote:<br><br>Hi all<br><br>Yesterday I emailed TTGO/ Lily to see if in principle they could install the disaster radio<br>boards<br>they ship. After a bit of linguistic miscommunication they went ahead and did it.<br><br>So it's now possible to order the boards pre-flashed here:<br><br><a target="_blank" rel="noopener noreferrer" href="https://www.aliexpress.com/item/4000396836096.html">https://www.aliexpress.com/item/4000396836096.html</a><br><br>I didn't intend to do this without asking the list, so apologies if I've overstepped.<br><br>If you really don't want to do this, then I can ask them to remove the listing. I realise that<br>fully open hardware is needed in the medium term.<br><br>They are willing to donate a $1 for every board sold:<br><a target="_blank" rel="noopener noreferrer" href="https://ae01.alicdn.com/kf/H856d5793d514415187b910e3fd4a3139w.jpg">https://ae01.alicdn.com/kf/H856d5793d514415187b910e3fd4a3139w.jpg</a><br><br>Assuming you're happy to leave the listing up, where should we send this trickle of donations?<br>Do<br>you have a bank?<br><br>This does leave the task for the users to configure their SD card, is that as easy as formatting<br>to<br>ext2 and copying index.html to it?<br><a target="_blank" rel="noopener noreferrer" href="https://github.com/sudomesh/disaster-radio/tree/master/web/static">https://github.com/sudomesh/disaster-radio/tree/master/web/static</a> or is it more involved than<br>that?<br><br>Let me know what you want to do about the listing, and if it stays up, where to send the money.<br><br>Thanks<br><br>Sam<br>_______________________________________________<br>DisasterRadio mailing list<br><a target="_blank" rel="noopener noreferrer" href="mailto:DisasterRadio@lists.sudoroom.org">DisasterRadio@lists.sudoroom.org</a><br><a target="_blank" rel="noopener noreferrer" href="https://sudoroom.org/lists/listinfo/disasterradio">https://sudoroom.org/lists/listinfo/disasterradio</a></blockquote></div></body></html>