sensornetwork
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
sensornetwork [2013-01-30 01:56] – tim | sensornetwork [2019-05-21 16:02] (current) – removed tim | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | The proposal is to replace wall-e with a distributed network of sensor and output devices. | ||
- | |||
- | * in/out switch with LCD message | ||
- | * RFID swipe | ||
- | * temperature | ||
- | * light levels | ||
- | * PIR proximity sensor | ||
- | * IR remote control gateway | ||
- | * 13A socket switches | ||
- | * speaker | ||
- | * Club Mate counter | ||
- | * Fridge door sensor | ||
- | * Web-based dashboards | ||
- | * RRD-style graphs | ||
- | * laser cutter sensors: on/off, water in/out temperatures | ||
- | * LAN data: devices active, Internet bandwidth usage | ||
- | * ... | ||
- | |||
- | Sensors can be connected using wifi, ethernet or radio modules (XBee or RFM12B). Tim favours the Jeenode architecture, | ||
- | |||
- | Tim proposes the use of an AMQP or Redis messaging bus to handle all the sensor data. This would allow other Hacklab users to integrate their own sensors easily, and enable anyone to write scripts to consume the data created by the lab. | ||
- | |||
- | A Raspberry Pi could be used to host the messaging bus, and to mediate between RFM12B and TCP/IP protocols. | ||
- | |||
- | Interested parties: Aaron, Tim | ||
sensornetwork.1359510973.txt.gz · Last modified: 2015-10-05 15:55 (external edit)