Difference between revisions of "Ledslie"

From Technologia Incognita
Jump to: navigation, search
 
(18 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
{{Project
 
{{Project
 +
|picture=23c6c9d3ff88b3f8-cut.jpg
 +
|ProjectSkills=electronics, microcontrollers, linux, mqtt, webservices, python, twisted, ansible
 
|ProjectStatus=Active
 
|ProjectStatus=Active
 
|ProjectNiche=Electronics
 
|ProjectNiche=Electronics
 
|ProjectPurpose=Infrastructure
 
|ProjectPurpose=Infrastructure
 
}}
 
}}
 +
= Interface to display information =
  
= Interface to display information =
+
* It is a Grayscale display of 144x24 pixels that displays information.
* Via HTTP Upload 144x24 bit monochrome (animated) gifs see the content display on the display.  
+
* It lives at http://ledslie.ti/ and is accessible at the space via a website and MQTT.  
  
An example to send the test1.gif file with via curl.  
+
= Interfaces =
 +
* At http://ledslie.ti/ you to submit content, such as animated GIFs, from your browser.
 +
* You can publish content by posting content to the web-service.
 +
* You can publish content directly to the mqtt broker that lives on ledslie.ti:1883.  
  
$ curl -H "Content-Type: image/gif" --data-binary @images/test1.gif http://<device-ip> --verbose
+
= Known issues (and their solution) =
 +
* Symptoms: The screens network dependent screens are missing, time might be incorrect. http://ledslie.ti is not available.
 +
* Problem: The DHCP server was not available when Ledslie started up, and is now in network-less mode. Likely there was a space  power failure. 
 +
* Solution: Once the network is stable again, cycle the power of Ledslie, it should restart properly.
  
= Content ideas (in no order) =
+
= Content ideas (in no specific order) =
* Spacealert
+
* (Done-ish) Spacealert with message. Still missing working shardik code.
 
* IRC integration via shardik: .display [message]
 
* IRC integration via shardik: .display [message]
* Indicio audio: What are we listening to?
+
* (Done) MPD songs: What are we listening to?
* Foutmeldingen van het koffiezet apparaat.
+
* Wifi SSIDs being broadcast / MAC count stats
* Next and last tram / metro / nightbuses
+
** https://arstechnica.com/information-technology/2014/11/where-have-you-been-your-smartphones-wi-fi-is-telling-everyone/
* Incoming rain alerts
+
** https://www.hak5.org/episodes/haktip-23
* World clocks
+
* (Done) Next and tram / metro / nightbuses
* API/Interface voor countdowns.  
+
* (Done)  Incoming rain alerts (https://www.buienradar.nl/overbuienradar/gratis-weerdata, https://br-gpsgadget-new.azurewebsites.net/data/raintext/?lat=52.35&lon=4.83)
** Next TI events
+
* (Done) Clock
** TI ALVs
+
* (Done) Midnights ("Midnight in «City»")
 +
* Days until Brexit
 +
* Drama stats
 +
** Parse the ML archives, get stats from there --- https://techinc.nl/cgi-bin/mailman/listinfo/ + https://techinc.nl/cgi-bin/mailman/listinfo/discuss
 +
** Keep track of IRC stats --- https://gist.github.com/habnabit/5823693
 +
* API/Interface for countdowns.  
 +
* (Done) Next TI events
 +
* Space events
 
** Next interesting rocket launch (SpaceX, Soyuz, etc...)  
 
** Next interesting rocket launch (SpaceX, Soyuz, etc...)  
** Space dates / launches
 
 
** ISS flyovers
 
** ISS flyovers
** Zonsopkomst en -ondergang tijden
+
* (Done) Zonsopkomst en -ondergang tijden
** Maan standen. volle maan, nieuwe, etc.
+
* (Done) Maan standen. volle maan, nieuwe, etc.
** http://www.apiblog.nl/
 
 
* External content
 
* External content
 +
** (Done) Btc/Eth values --- https://www.cryptocompare.com/
 +
** https://radar.squat.net --- https://0xacab.org/radar/drupal-make/wikis/api/1.1/notes
 
** Security.nl
 
** Security.nl
 +
** http://www.apiblog.nl/
 
** Theregister.co.uk
 
** Theregister.co.uk
 
** hackernews.
 
** hackernews.
 
** Radio Yerevan Jokes: https://duckduckgo.com/Radio_Yerevan_jokes?iax=1&ia=about
 
** Radio Yerevan Jokes: https://duckduckgo.com/Radio_Yerevan_jokes?iax=1&ia=about
** Jargon file
+
** Random Jargon file entries
** Btc/Eth values
 
* Wifi SSIDs being broadcast.
 
  
 
= How it works =
 
= How it works =
  
ESP32 <-> Arduino <-> Led-pannel
+
Wifi --RF> Getchip --USB2> Teensy --[data,clock,latch]> Led-pannel
 +
 
 +
The led-panel takes 20V DC as input. At full output it's pulling about 4A, or about 80W. There's a small switcher-board that supplies the 5v the the getchip and Teensy from those 20V.
 +
 
 +
The Teensy drive code is here: https://github.com/techinc/ledmatrix/tree/master/ledmatrix144x24
 +
 
 +
The Ledslie code can be found here: https://github.com/techinc/ledslie
 +
 
 +
= Software =
 +
 
 +
The system's software is available at https://github.com/techinc/ledslie , this repo contains code that's running on the Display.
  
# ESP 32 has simple a HTTP server that receives and decodes the GIFs send to it as images.
+
= Possible Hardware expansions =
# Via the UART ports the ESP32 sends the decoded gif frame as images to the Arudino.
+
* Add another panel by adding a USB2 hub, and modding another of the led panels with the teensy taking over the driving logic.  
# Once the Arduino has received the whole image, it transforms it into the leddisplay's format and will start refreshing that image into the led display while receiving the next image. 
 
# To indicate the start of a new frame the ESP will pull a pin of the Arduino high. On the Low-edge, a new image is being send.
 
  
The led-panel has a 20V DC input, reducing it to the 5v we need for the Arduino and ESP, we use a small power switcher board.
+
= FAQ =
 +
* Q: What's that noise? A: The panel is being driven at rates way beyond the original design and we're well in the audible frequencies with the refresh-rates and some components are merrily humming along.
 +
* Q: Why are some points brighter then others? A: Turns out that LEDs do wear. In their previous life some LEDs were on for years, while others were always off. There's plans to compensate for this in software.

Latest revision as of 17:17, 9 April 2018

Projects
23c6c9d3ff88b3f8-cut.jpg
Participants Chotee, Thijs
Skills electronics, microcontrollers, linux, mqtt, webservices, python, twisted, ansible
Status Active
Niche Electronics
Purpose Infrastructure

Interface to display information

  • It is a Grayscale display of 144x24 pixels that displays information.
  • It lives at http://ledslie.ti/ and is accessible at the space via a website and MQTT.

Interfaces

  • At http://ledslie.ti/ you to submit content, such as animated GIFs, from your browser.
  • You can publish content by posting content to the web-service.
  • You can publish content directly to the mqtt broker that lives on ledslie.ti:1883.

Known issues (and their solution)

  • Symptoms: The screens network dependent screens are missing, time might be incorrect. http://ledslie.ti is not available.
  • Problem: The DHCP server was not available when Ledslie started up, and is now in network-less mode. Likely there was a space power failure.
  • Solution: Once the network is stable again, cycle the power of Ledslie, it should restart properly.

Content ideas (in no specific order)

How it works

Wifi --RF> Getchip --USB2> Teensy --[data,clock,latch]> Led-pannel

The led-panel takes 20V DC as input. At full output it's pulling about 4A, or about 80W. There's a small switcher-board that supplies the 5v the the getchip and Teensy from those 20V.

The Teensy drive code is here: https://github.com/techinc/ledmatrix/tree/master/ledmatrix144x24

The Ledslie code can be found here: https://github.com/techinc/ledslie

Software

The system's software is available at https://github.com/techinc/ledslie , this repo contains code that's running on the Display.

Possible Hardware expansions

  • Add another panel by adding a USB2 hub, and modding another of the led panels with the teensy taking over the driving logic.

FAQ

  • Q: What's that noise? A: The panel is being driven at rates way beyond the original design and we're well in the audible frequencies with the refresh-rates and some components are merrily humming along.
  • Q: Why are some points brighter then others? A: Turns out that LEDs do wear. In their previous life some LEDs were on for years, while others were always off. There's plans to compensate for this in software.