Categories

Thermal Tweeter facts and figures FAQ @dangerousproto

Posted on Monday, June 27th, 2011 in web platforms by Ian

A lot of questions are coming through the Thermal Tweeter. Here’s some answers:

  • How many rolls? About 1/day on Thursday, Friday, Saturday. 2.5 on Sunday, and it ran out twice for a few hours. Also, about 2/day of this variety.
  • The printer uses thermal paper in rolls. It doesn’t use ink.
  • Rolls were 5 for a buck, cheaper in bulk. We have to stock up today.
  • The paper has red stripes for a few meters from the end.
  • Average delay from tweet to viewing it print is around 30 seconds.  The printer checks for new @mentions every 30 seconds. There’s about 15 seconds of USTREAM delay too.
  • Only standard ASCII characters will print. Unicode is filtered out by the web platform when it processes the tweets. The printer does support a few extended characters, but not unicode. There’s no direct translation from unicode numbers to the extended characters supported by the printer, it would be a real pain to deal with that.
  • The printer knows when the paper is gone and stops printing.
  • All the tweets are in a pile on the floor, we’ll give some away at end
  • Almost 4 days of non-stop USTREAM using Adobe Flash Media Live app and a Firewire DV camera. As long as we keep the preview window minimized it doesn’t crash…
  • We don’t mind if you want to use a lot of paper or tweet via script, it makes it more interesting for people watching the USTREAM.
  • It cost about $100. The printer was $50 at SparkFun. The Web Platform is $40 at Seeed Studio, but we built our own.

See the design overview, and read the first system update.

This entry was posted on Monday, June 27th, 2011 at 8:51 am and is filed under web platforms. You can follow any responses to this entry through the RSS 2.0 feed. You can skip to the end and leave a response. Pinging is currently not allowed.

3 Responses to “Thermal Tweeter facts and figures FAQ @dangerousproto”

  1. arturo says:

    cool stuff.. sorry for the OT but did you use adobe’s live encoder, or ustream’s?

    • Ian says:

      We’re using the adobe encoder. It works great as long as it is minimized. If the preview is on screen it crashes a lot.

  2. arturo says:

    thanks for the tip =)

Leave a Reply

Notify me of followup comments via e-mail. You can also subscribe without commenting.

Recent Comments

  • Paul Campbell: I'm old enough that I started programming with punched cards .... each card had a sequence number in the last few characters. A friend once...
  • Ian: test comment on /blog/ page
  • ian: No, that's exactly how it should be :) Sorry about missing names on comments, the theme is being reworked as we speak.
  • J. Peterson: Nice writeup. It looks like some of the formatting for your command examples needs some missing newlines?
  • Geert Jordaens: I'm not sure what kind of licensing I have to add since it is a fairly straight forward implementation of the adaptive Huffman Decoding. For...