Project:IRC Terminal: Difference between revisions
(→How?) |
(→What?) |
||
Line 23: | Line 23: | ||
==What?== | ==What?== | ||
Make a freestanding (ish) IRC terminal for general use. | Make a freestanding (ish) IRC terminal for general use. | ||
If we had a serial tikitag reader, and connected it to another port of the same machine (or the passthrough printer port if that terminal has one), then maybe the user could get his irc nick set automgically. | |||
==Where?== | ==Where?== |
Revision as of 23:43, 8 January 2011
IRC Terminal | |
---|---|
Created | 05/01/2010 |
Members | naxxfish, |
QR code |
Aim
Retro serial terminal IRC awesomeness.
Stephen Blomley brought in a VT520 terminal
Who?
What?
Make a freestanding (ish) IRC terminal for general use.
If we had a serial tikitag reader, and connected it to another port of the same machine (or the passthrough printer port if that terminal has one), then maybe the user could get his irc nick set automgically.
Where?
Why?
How?
Recently donated was a mostly dead Toshiba lappy (dead drives, dead screen) which has a serial port. This is now redundant as I have the same terminal working with a usb to serial adaptor. We can hook the serial terminal up to any computer run something like "exec /sbin/getty -L 56700 ttyUSB0" from /etc/init/ttyUSB0.conf. I would suggest the doorbot because that is always running. It's now booting Ubuntu over PXE successfully. We're looking to hook it up to the vt520.
I think we're meant to leave doorbot as is because it's a critical system. Could a microcontroller with serial + ethernet do the job - we have an mbed sitting around that has ethernet. --Elliot
Er, why not babbage? It's always on, and designed for general server use. --Jonty
Signal | 9-Pin | 25-Pin |
---|---|---|
Carrier Detect | 1 | 8 |
Receive Data | 2 | 3 |
Transmit Data | 3 | 2 |
Data Terminal Ready | 4 | 20 |
System Ground | 5 | 7 |
Data Set Ready | 6 | 6 |
Request to Send | 7 | 4 |
Clear to Send | 8 | 5 |
Ring Indicator | 9 | 22 |
Signal | 9-Pin | 25-Pin |
---|---|---|
Receive Data | 2 | 3 |
Transmit Data | 3 | 2 |
System Ground | 5 | 7 |
Roadmap:
Where?
Why?
- 1.
- 2.