RevSpace - Gebruikersbijdragen [nl]

WishList

2011-10-01T23:26:52Z

10.42.42.9: Created page with " Things we would like to have as Revspace. == Hardware == * Ip revcams * Beamers * Infra red stuff * Plasma cuter * Barbwire * Lockpickgear"

Things we would like to have as Revspace.

== Hardware ==
* Ip revcams
* Beamers
* Infra red stuff
* Plasma cuter
* Barbwire
* Lockpickgear

WirelessBelgiumLetterOfIntent

2011-10-01T23:26:51Z

10.42.42.9: Created page with " = Wireless Belgie en Nederland = Wireless Belgie is een ad-hoc netwerk opgezet door vrijwilligers dat met draadloze verbindingen (WIFI) over lange afstanden een netwerk reali..."

= Wireless Belgie en Nederland =

Wireless Belgie is een ad-hoc netwerk opgezet door vrijwilligers dat met draadloze verbindingen (WIFI) over lange afstanden een netwerk realiseert voor electronische communicatie. Het netwerk biedt gratis en vrije toegang aan iedereen in het bezit van een standaard WIFI adapter, en is op enkele plaatsen verbonden met het bestaande Internet. Revelation Space en ... insert organisations ... hebben zich bij dit initiatief aangesloten om ook in Nederland dekking van dit netwerk te realiseren. Hiertoe worden locaties in, in eerste instantie, Rotterdam, Den Haag en Delft gezocht om routers te installeren. Een router heeft niet meer nodig dan zichtlijnen naar andere routers op 30 tot 60 kilometer afstand, alsmede een bescheiden hoeveelheid stroom. Er is geen noodzaak voor een internetverbinding.

= Installatie van een node =

De nodes in het netwerk bestaan uit tenminste twee wireless transceivers voor verbindingen met nodes op lange afstand. Dit vormt de backbone van het netwerk. Hier wordt meestal nog een derde transceiver (of eventueel meer) aan toegevoegd om fijnmazige distributie in de directe omgeving van de node te verzorgen. Idealiter beschikt een stads-regio over meerdere backbone nodes en een fijnmazig netwerk van nodes waar gebruikers mee kunnen verbinden.

De volgende stappen worden doorlopen bij het plaatsen van een nieuwe backbone node:

1 Controleren van zichtlijnen naar potentiele partner backbone nodes
2 Schouw op lokatie
** inventarisatie van ophangpunten, benodigde materialen
** inventarisatie 220V stroombron
3 Aanschaf en bouw benodigde apparatuur en bevestigingsmaterialen
4 Installatie
5 Ingebruikname

Voor de stappen 2 en 5 is, in overleg met de gebouwbeheerder, toegang tot het dak nodig. Hierna kan de node volledig autonoom werken en op afstand worden geconfigureerd en beheerd. Mogelijkerwijs zal na ingebruikname incidenteel een extra antenne worden bijgeplaatst als dit voor de uitbreiding van het netwerk nodig is.

= Implicaties voor de lokatie =

De backbone node maakt gebruik van sterk gebundelde radio-verbindingen.Er is derhalve geen interferentie naar andere radio-apparatuur die eventueel al aanwezig is.

== Historie en overzicht ==

Het project begon in 19??/20?? als 'Wireless Antwerpen'. De inspiratie hiervoor was Wireless Leiden. Dankzij de inzet van een groep gemotiveerde vrijwilligers groeide dit project al snel uit tot een netwerk dat op veel plaatsen in Antwerpen gratis toegang tot internet leverde aan iedereen die een WIFI adapter bezit. De belangstelling beperkte zich echter niet tot Antwerpen, en al snel werden langere afstanden overbrugt naar andere Belgische steden zoals Brussel en Gent.

Het netwerk omvat op dit moment #### nodes. Het netwerk brijdt zich uit met ### nodes per maand. Hoewel er geen formele organisatie is, wordt het initiatief gedragen door de nationale en internationale hackerspace gemeenschap, en gesteund door organisaties die zich inzetten voor een vrije internet infrastructuur zoals ......

Soortgelijke initiatieven vinden we wereldwijd. Enkele toonaangevende voorbeelde in Europa zijn het duitse Freifunk en het Spaanse Guifi.net. De ambitie voor de middellange toekomst is het verbinden van al deze netwerken. - einddoel vrijheid van informatie, corps/govs

=== .. andere organisatie .. ===

=== Revelation Space ===

Revelation Space is de hackerspace gevestigd in Den Haag. Het is een plek waar technisch en creatief gemotiveerde personen een gezamelijke werkplaats en ontmoetingsplek in hebben. Binnen de 400 vierkante meter oppervlakte aan de Binckhorstlaan vinden zij een electronica werkplaats, een klein-mechanische werkplaats, een netwerk- en computer hacklab, een radio studio, keuken en ontspanningsruimte. Activiteiten die worden ontplooit zijn bijvoorbeeld visuele installaties, malware analysis, telemetrie en domotica, muzikale experimenten, rapid prototyping en kennis-overdracht in de vorm van workshops en lezingen.

=== The Free Network Foundation ===

= Referenties =

1 http://wirelessbelgie.be/
2 http://andereorganisatie.nl/
3 https://revspace.nl/
4 http://thefnf.org/
5 http://www.hackerspaces.org/
6 freifunk
7 http://guifi.net/

-- Main.KoenMartens - 11 Sep 2011

WirelessBelgium

2011-10-01T23:26:49Z

10.42.42.9: Created page with " [httphttp://wirelessbelgium.be/ Wireless Belgium] started as Wireless Antwerp and is realizing a vast network of long- and short-distance wifi connectivity to form a network fo..."

[httphttp://wirelessbelgium.be/ Wireless Belgium] started as Wireless Antwerp and is realizing a vast network of long- and short-distance wifi connectivity to form a network for electronic communication. Started in Antwerp, it has rapidly expanded to [httphttp://nodedb.wirelessantwerpen cover the north of Belgium and is now expanding into The Netherlands].

We want to connect at least The Hague (!RevSpace), Rotterdam and Delft and then look ahead to complete a loop east-wards and then back to Belgium again. Current locations include:

* Red Apple - Rotterdam
* EWI building - Delft

In order to make our case to the owners of said buildings, we are drafting a [WirelessBelgiumLetterOfIntent|letter of intent].

WipeandDefrag

2011-10-01T23:26:48Z

10.42.42.9: Created page with " = Introducing "Wipe and Defrag" = Every last sunday of the month is cleaning time. In the revolationspace no stone remains unturned. From 13.00 until 15.00 hours cleane..."

= Introducing "Wipe and Defrag" =
Every last sunday of the month is cleaning time.
In the revolationspace no stone remains unturned.

From 13.00 until 15.00 hours cleaned up, vacuumed, cleaned, beaten and disposed of entropy a trick.

== What needs were to be done: ==

* Kitchen
** Vacuuming
** Cleaning the table and fridge.
** Use diswhasher

* Toilets

* Bar
** Vacuuming
** Cleaning bar, tables and fridge's

* Handwerkhok
** Vacuuming
** Cleaning tables

* Studio
** Vacuuming
** Cleaning tables

* Room 101
** Vacuuming

WinSCaP

2011-10-01T23:26:46Z

10.42.42.9: Created page with " -- Main.WinSCaP - 13 Apr 2011 Fuck no, it's a WinSCaP"

-- Main.WinSCaP - 13 Apr 2011

Fuck no, it's a WinSCaP

WebTopicList

2011-10-01T23:26:45Z

10.42.42.9: Created page with " %INCLUDE{"%SYSTEMWEB%.%TOPIC%"}%"

%INCLUDE{"%SYSTEMWEB%.%TOPIC%"}%

WebSearchAdvanced

2011-10-01T23:26:42Z

10.42.42.9: Created page with " %INCLUDE{"%SYSTEMWEB%.%TOPIC%"}%"

%INCLUDE{"%SYSTEMWEB%.%TOPIC%"}%

WebSearch

2011-10-01T23:26:40Z

10.42.42.9: Created page with " %INCLUDE{"%SYSTEMWEB%.%TOPIC%"}%"

%INCLUDE{"%SYSTEMWEB%.%TOPIC%"}%

WebIndex

2011-10-01T23:26:33Z

10.42.42.9: Created page with " %INCLUDE{"%SYSTEMWEB%.%TOPIC%"}%"

%INCLUDE{"%SYSTEMWEB%.%TOPIC%"}%

WebHome

2011-10-01T23:26:32Z

10.42.42.9: Created page with " Revelation space: the [httphttp://www.hackerspaces.org hackerspace] in Den Haag, NL (also servicing Zoetermeer, Delft, Voorburg, Rijswijk, Rotterdam, Pijnacker and the rest of ..."

Revelation space: the [httphttp://www.hackerspaces.org hackerspace] in Den Haag, NL (also servicing Zoetermeer, Delft, Voorburg, Rijswijk, Rotterdam, Pijnacker and the rest of the world).
<div style="float: right; width: 20%; border-left: 1em solid black;">
= Recent tweets =
%INCLUDE{"LatestTweets"}%</div>
<div style="width: 80%;">
= Upcoming events =
%CALENDAR{aslist="1" topic="RevelationSpace.AgendaEvents" days="30"}%
= The latest news =
(<a href="%SCRIPTURL{"view"}%/%WEB%/LatestNews?num=all">all news</a>):
%INCLUDE{"LatestNews"}%
</div>

WebHackingWorkshop

2011-10-01T23:26:30Z

10.42.42.9: Created page with " A lot of people ask how to become a hacker (and break into computer systems). One of the easiest ways to learn about this topic is by investigating web applications. Of course ..."

A lot of people ask how to become a hacker (and break into computer systems). One of the easiest ways to learn about this topic is by investigating web applications. Of course it should be made clear what the current legal situation surrounding this topic is and how one should responsibly investigate computer security. Note that all information that will be taught can easily be found by anybody and that this project in no way tries to encourage cybercrime (on the contrary!).

WebCreateNewTopic

2011-10-01T23:26:29Z

10.42.42.9: Created page with " "

WebChanges

2011-10-01T23:26:28Z

10.42.42.9: Created page with " %INCLUDE{"%SYSTEMWEB%.%TOPIC%"}%"

%INCLUDE{"%SYSTEMWEB%.%TOPIC%"}%

VoipRadioPanel

2011-10-01T23:26:23Z

10.42.42.9: Created page with " = %NOTOC%Goal = Have max. 6 participants dial on to an asterisk pbx, make each of their voices individually available as a mono output. Each participant should hear the other ..."

= %NOTOC%Goal =

Have max. 6 participants dial on to an asterisk pbx, make each of their voices individually available as a mono output. Each participant should hear the other participants plus an external input from the mixing desk (studio mics / music), but not hear themselves back.

Documentation should be provider for common platforms (linux, macosx, ms windows). Pick one voip client on each platform, and document every step from installation, configuration to connecting to the conference pbx and joining.

__FORCETOC__

= Todo =

Needs a lot of testing in the field:

* get a bunch of typical users to give up a few hours of their time, explain they will need to be patient and do exactly as we say
* set up a conference bridge with different types of connections: pots, voip, skype to sip gateway
* documentation
* create sample set to guide users in joining the conf

= Setup =

* ESI u46xl sound card (6 out, 4 in, sponsored by Hxx)
* Mixing desk with at least 6 line-ins, one aux or sub out
* linphone instances to connect to the pbx
* asterisk with custom extensions and scripts
* siptosis skype gateway

== ESI u46xl ==

Linux has crappy support for this device. To initialize the device properly, send the following to the usb mixer with 'amixer -c 1 -s':

<pre>
cset numid=1 on,on
cset numid=2 on
cset numid=3 0,0,0,0
cset numid=4 on,on
cset numid=1 off,off
cset numid=5 off
cset numid=1 on,on
cset numid=7 on,on,on,on
cset numid=8 on
cset numid=6 0,0,0,0
cset numid=9 31,31,31,31,31,31
</pre>

(yes, we turn 1 on, of and on again, needed to properly load 5, which disables monitor)

This .asoundrc makes the channels individually adressable and creates some fake input/output for linphone:

<pre>
// Copyright (c) Koen Martens, gmc@sonologic.nl
// licensed under GPLv3

pcm.u46xl_play {
type dmix
ipc_key 2048
slave {
pcm "hw:1,0"
rate 44100
period_time 0
period_size 1024
buffer_size 8192
channels 6
}
bindings {
0 0
1 1
2 2
3 3
4 4
5 5
}
}

pcm.out1 {
type plug
slave {
pcm "u46xl_play"
channels 6
rate 44100
}
ttable.0.0 1
}
pcm.out2 {
type plug
slave {
pcm "u46xl_play"
channels 6
}
ttable.0.1 1
}
pcm.out3 {
type plug
slave {
pcm "u46xl_play"
channels 6
}
ttable.0.2 1
}
pcm.out4 {
type plug
slave {
pcm "u46xl_play"
channels 6
}
ttable.0.3 1
}
pcm.out5 {
type plug
slave {
pcm "u46xl_play"
channels 6
}
ttable.0.4 1
}
pcm.out6 {
type plug
slave {
pcm "u46xl_play"
channels 6
}
ttable.0.5 1
}

pcm.u46xl_record {
type dsnoop
ipc_key 1647
slave {
pcm "hw:1,0"
period_size 0
buffer_size 65536
rate 44100
channels 4
}
bindings {
0 0
1 1
}
}

pcm.in1 {
type plug
ttable.0.0 1.0
slave.pcm pcm.u46xl_record
}

pcm.in2 {
type plug
ttable.0.1 1.0
slave.pcm pcm.u46xl_record
}

pcm.in3 {
type plug
ttable.0.2 1.0
slave.pcm pcm.u46xl_record
}

pcm.in4 {
type plug
ttable.0.3 1.0
slave.pcm pcm.u46xl_record
}
pcm.dummy {
type plug
slave {
pcm default
channels 1
rate 44100
}
ttable.0.0 0
}

pcm.mynull {
type null
}

pcm.channel1 {
type asym
playback.pcm "out1"
capture.pcm "dummy"
}

pcm.channel2 {
type asym
playback.pcm "out2"
capture.pcm "dummy"
}

pcm.channel3 {
type asym
playback.pcm "out3"
capture.pcm "dummy"
}

pcm.channel4 {
type asym
playback.pcm "out4"
capture.pcm "dummy"
}
pcm.channel5 {
type asym
playback.pcm "out5"
capture.pcm "dummy"
}

pcm.channel6 {
type asym
playback.pcm "out6"
capture.pcm "dummy"
}

pcm.feedback {
type asym
playback.pcm "null"
capture.pcm "in1"
}

</pre>

== linphone ==

Use linphonec -c configfile -s 'spyext@voip.host', eg:

<pre>
linphonec -c linphone1.cfg -s '1@pbx.sonologic.net'
</pre>

Here is linphone1.cfg:

<pre>
[sound]
alsadev=channel1
playback_dev_id=ALSA: channel1
ringer_dev_id=ALSA: channel1
capture_dev_id=ALSA: channel1
remote_ring=/usr/share/sounds/linphone/ringback.wav

[GtkUi]
advanced_ui=1

[video]
device=V4L2: /dev/video0
size=cif
enabled=0
display=0
capture=0
show_local=0
self_view=0

[net]
download_bw=0
upload_bw=0
firewall_policy=2
mtu=0
stun_server=pbx.sonologic.net

[sip]
sip_port=5071
guess_hostname=1
inc_timeout=15
use_info=0
use_rfc2833=0
use_ipv6=0
register_only_when_network_is_up=1
default_proxy=-1
contact=<sip:spy@localhost:5071>

[rtp]
audio_rtp_port=7081
video_rtp_port=9078
audio_jitt_comp=60
video_jitt_comp=0
nortp_timeout=30

[audio_codec_0]
mime=speex
rate=32000
enabled=1

[audio_codec_1]
mime=speex
rate=16000
enabled=1

[audio_codec_2]
mime=speex
rate=8000
enabled=1

[audio_codec_3]
mime=GSM
rate=8000
enabled=1

[audio_codec_4]
mime=PCMU
rate=8000
enabled=1

[audio_codec_5]
mime=PCMA
rate=8000
enabled=1

[video_codec_0]
mime=MP4V-ES
rate=90000
enabled=1
recv_fmtp=profile-level-id=3

[video_codec_1]
mime=theora
rate=90000
enabled=1

[video_codec_2]
mime=H263-1998
rate=90000
enabled=1
recv_fmtp=CIF=1;QCIF=1

[video_codec_3]
mime=H263
rate=90000
enabled=1

[video_codec_4]
mime=x-snow
rate=90000
enabled=1

[auth_info_0]
username=spyuser
userid=spyuser
passwd=secret
realm="asterisk"
</pre>

Be sure to use different alsa devices and different sip/rtp ports for additional spying clients.

For feedback (audio from the mixing desk sub out to the conference):

<pre>
linphonec -c feedback.cfg -s 'feedback@pbx.sonologic.net'
</pre>

Here is the config:

<pre>
[sound]
alsadev=feedback
playback_dev_id=ALSA: feedback
ringer_dev_id=ALSA: feedback
capture_dev_id=ALSA: feedback
remote_ring=/usr/share/sounds/linphone/ringback.wav

[GtkUi]
advanced_ui=1

[video]
device=V4L2: /dev/video0
size=cif
enabled=0
display=0
capture=0
show_local=0
self_view=0

[net]
download_bw=0
upload_bw=0
firewall_policy=2
mtu=0
stun_server=p��

[sip]
sip_port=5080
guess_hostname=1
inc_timeout=15
use_info=0
use_rfc2833=0
use_ipv6=0
register_only_when_network_is_up=1
default_proxy=-1
contact=<sip:spy@localhost:5070>

[rtp]
audio_rtp_port=7090
video_rtp_port=9078
audio_jitt_comp=60
video_jitt_comp=0
nortp_timeout=30

[audio_codec_0]
mime=speex
rate=32000
enabled=1

[audio_codec_1]
mime=speex
rate=16000
enabled=1

[audio_codec_2]
mime=speex
rate=8000
enabled=1

[audio_codec_3]
mime=GSM
rate=8000
enabled=1

[audio_codec_4]
mime=PCMU
rate=8000
enabled=1

[audio_codec_5]
mime=PCMA
rate=8000
enabled=1

[video_codec_0]
mime=MP4V-ES
rate=90000
enabled=1
recv_fmtp=profile-level-id=3

[video_codec_1]
mime=theora
rate=90000
enabled=1

[video_codec_2]
mime=H263-1998
rate=90000
enabled=1
recv_fmtp=CIF=1;QCIF=1

[video_codec_3]
mime=H263
rate=90000
enabled=1

[video_codec_4]
mime=x-snow
rate=90000
enabled=1

[auth_info_0]
username=spy
passwd=secret
realm="asterisk"
</pre>

== extensions.ael ==

You need a sip.conf with a spy user and a feedback user, which both are in context spy.

You may want to create sip accounts for the panel members. Dump them in context panel.

You might want to make an extension 'panel' in your public sip context, which goes to panel|s|1.

<pre>
// Copyright (c) 2011, Koen Martens <gmc@sonologic.nl>
// licensed under GPLv3

context panel {
s => {
Answer(500);
BackGround(auth-incorrect);
WaitExten;
};
t => {
Hangup();
};
_XXXX => {
if (${DB_EXISTS(PANEL_ACCOUNT/${EXTEN})}) {
Set(participantno=${DB(PANEL_ACCOUNT/${EXTEN})});
jump s@panel_join;
} else {
Playback(auth-incorrect);
jump s;
}
};
h => {
NoOp(${DB_DELETE(PANEL_CHANNELS/${participantno})});
};
};

context panel_join {
s => {
// expects participantno to be set
if (${DB_EXISTS(PANEL_CHANNELS/${participantno})}) {
// Warn about participant already existing
}
Set(DB(PANEL_CHANNELS/${participantno})=${CHANNEL});
// ConfBridge(0,1q);
MeetMe(0,1q);
}
}

context spy {
_X => {
Answer(500);
while (1) {
if (${DB_EXISTS(PANEL_CHANNELS/${EXTEN})}) {
Set(channeltospy=${DB(PANEL_CHANNELS/${EXTEN})});
//ChanSpy(${channeltospy},oqXS);
ChanSpy(${channeltospy},oXSv(4));
}
Wait(5);
}
};
_feedback => {
Answer(500);
// ConfBridge(0,1qs);
MeetMe(0,1q);
}
echo => {
Answer(500);
Echo();
Hangup();
}
};

context moderator {
// Moderator for conference
1337 => {
Answer(2000);
// Warn about being joined as a moderator
// ConfBridge(0,1qsa);
MeetMe(0,1qsa);
};
// Dial out
_0X. => {
Set(outboundno=${EXTEN:1});
jump s@outboundtie;
}
};

context outboundtie {
s => {
Dial(SIP/moderator,60,T);
NoOp();
};
_X => {
Set(participantno=${EXTEN});
jump s@panel_join;
}
}
</pre>

== siptosis ==

Get the gateway software [httphttp://www.mhspot.com/sts/siptosis_download.php here].

Some useful documents:
* http://www.mhspot.com/sts/siptosis_config_issues.html
* http://www.mhspot.com/sts/siptosis_skype_trunk_howto.html

I am not pretending I know exactly what is going on here, but something like this should do the trick (supposing there is a sip account panel2 on your pbx):

<pre>
# siptosis.cfg
debug_level=3

# SipToSis configuration file

# ___________________________________________

#

#how opften in minutes to check for configuration changes (0=disable)

configWatchInterval=0

#Set to log_debug.properties for full debugging

logConfigFile=log.properties

#Files containing Authorization rules

siptoskypeauthfile=SipToSkypeAuth.props

skypetosipauthfile=SkypeToSipAuth.props

#Files containing dialing transforms

SkypeOutDialingRulesFile=SkypeOutDialingRules.props

SipOutDialingRulesFile=SipOutDialingRules.props

#location of ua.jar file

ua_jar=ua.jar

#increase audio threads processing priority (0-2) 0=normal

audioPriorityIncrease=0

#jitter enable and size (0=disable,1=small,2=medium,3=large,4=extra large)

jitterLevel=2

#Set to skype_connect=no to disable connection to skype client - for testing purposes

skype_connect=yes

#Following ports are used by skype to transfer audio to/from siptosis

# - use any unused ports - uses 2 ports per connection

skype_audioportbase=64432

#Set to yes to enable skype DTMF support - uses more cpu

enableSkypeDtmfDetector=no

SkypeDtmfDetectorHitThreshold=90

SkypeDtmfDetectorSilenceThreshold=6

#Set to yes to regenerate SIP DTMF to Skype

sendSipDtmfToSkype=yes

#Set to yes to regenerate Skype DTMF to Sip

sendSkypeDtmfToSip=yes

#If using inband detectors, no to detect dtmf only during authentication (saves cpu)

inbandFullTimeDtmfDetection=no

#special mode if using skype client manually and an outbound skype call is made, it will attempt a sip call and link the two

JoinManualSkypeOutboundCallToSip=no

#refuse,voicemail,ignore,transferto:skypeid

# If you are using a PBX with multiple clients/ids you probably want to use ignore

# or possibly transferto:nextskypeid to the next skypeclient in the chain

# then refuse on the last one

SkypeInboundAllChannelsBusyAction=refuse

#If an incoming skype call and sip destination is not available for any reason, what to do with skype call.

#Allowed options: ring or refuse - ring allows the skype client to continue ringing and be answered manually.

SkypeInboundSipDestUnavailableAction=refuse

#busy,transferto:sipurl

# If you want multiple outbound channels (AsteriskWin32 does not like this)

# use transferto:sipurl to the next SipToSis channel in the chain then busy on the last one

SipInboundAllChannelsBusyAction=busy

#enable if skype client can support multiple active calls at same time - trying to lie here won't work

#I have yet to find a client that can do this

skypeclientsupportsmulticalls=no

#For an ATA/SIP Phone set to 2 - this allows two total calls - one will be on hold.

#For a PBX - depending on if the skype client supports multi calls - if not set it to 1

# otherwise set based on your hardware/bandwidth limitations

concurrentcalllimit=2

#specify in 5 minute increments, 0=disable auto shutdown - siptosis will auto shutdown in x minutes when idle

autoShutdownMinutes=0

#Seconds caller has to enter the pin number

pintimeout=8

#Number of pin entry attempts before auto hangup

pinretrylimit=3

#Seconds caller has to enter the destination number

destinationtimeout=12

#Number of destination entry attempts before auto hangup

destinationretrylimit=3

#SIP authorization system recordings - make your own if you like (wav 16k 16bit mono).

pinFile=clips/enterPin.wav

destinationFile=clips/enterDest.wav

dialingFile=clips/dialing.wav

invalidPinFile=clips/invalidPin.wav

invalidDestFile=clips/invalidDest.wav

#Skype authorization system recordings - make your own if you like (wav 16k 16bit mono).

skypePinFile=clips/enterPin.wav

skypeDestinationFile=clips/enterDest.wav

skypeDialingFile=clips/dialing.wav

skypeInvalidPinFile=clips/invalidPin.wav

skypeInvalidDestFile=clips/invalidDest.wav

#Used for Skypeout only - transmit skype feedback sound during PSTN call attempt

handleEarlyMedia=yes

#Send Skype IM when calling skype users - not used for skypeout

sendSkypeIM=no

skypeimmessage=You are about to receive a Skype Voice call from [callerid].

#delay between the IM and the actual skype call in seconds.

sendSkypeImDelay=2

#transport_protocols=udp tcp

transport_protocols=udp

via_addr=10.1.3.20

host_ifaddr=ALL-INTERFACES

enableNatTranslate=yes

#outbound_proxy=127.0.0.2:5060

#Sample AUTO config with NO registration

# username and password not important in this mode

#Set to available port to transport SIP messages on siptosis computer

#host_port=5070

#username=skypests

#passwd=unimportantpassword

# --- end of NO registration example ---

#Sample config with NO registration - use if above auto config doesn't work - change 127.0.0.1 to ip address of computer running siptosis

# username and password not important in this mode

#Set to available port to transport SIP messages on siptosis computer

#host_port=5070

#contact_url=sip:skypests@127.0.0.1:5070

#from_url="skypests" <sip:5611111111@127.0.0.1:5070>

#username=skypests

#passwd=unimportantpassword

#realm=127.0.0.1

# --- end of NO registration example ---

#Sample config WITH registration to GizmoProject - comment out NO registration info above first and uncomment the following

#contact_url=sip:studiorevspace@127.0.0.1:5070

#from_url="panel2" <sip:panel2@pbx.sonologic.net:5060>

#username=panel2

#passwd=secret
#realm=asterisk

#expires=120

#minregrenewtime=60

#regfailretrytime=15

#do_register=yes

#outbound_proxy=pbx.sonologic.net:5060

# --- end of WITH registration example ---

#sample FWD reg example - note the outbound proxy

#host_port=5070

#contact_url=sip:8?????@SipToSisIpAddress:SipToSisHostPort

#from_url="8?????" <sip:8?????@fwd.pulver.com:5060>

#username=8?????

#realm=fwd.pulver.com

#passwd=????

#expires=240

#do_register=yes

#minregrenewtime=120

#regfailretrytime=15

#outbound_proxy=fwdnat2.pulver.com:5060

# --- end of FWD registration example ---

#sample pennytel reg example

#host_port=5070

#contact_url=sip:8?????@SipToSisIpAddress:SipToSisHostPort

#from_url="8?????" <sip:8?????@sip.pennytel.com:5060>

#username=8?????

#realm=sip.pennytel.com

#passwd=123456

#expires=320

#do_register=yes

#minregrenewtime=120

#regfailretrytime=15

# --- end of pennytel registration example ---

#Sample Asterisk registration example - comment out NO registration info above first and uncomment the following.

#host_port=5070

#contact_url=sip:skypetestuser@SipToSisIpAddress:SipToSisHostPort

#from_url="skypetestuser" <sip:skypetestuser@asteriSkipAddress:asteriskHostPort>

#username=skypetestuser

#realm=asterisk

#passwd=skypetest

#expires=3600

#do_register=yes

#minregrenewtime=120

#regfailretrytime=15

# --- end of Asterisk Reg example ---

#Sample Asterisk registration example - comment out NO registration info above first and uncomment the following.

host_port=5070

contact_url=sip:studiorevspace@10.1.3.20:5070

from_url="panel2" <sip:panel2@pbx.sonologic.net:5060>

username=panel2

realm=asterisk

passwd=geheim
expires=3600

do_register=yes

minregrenewtime=120

regfailretrytime=15

# --- end of Asterisk Reg example ---

#Sample FreeSwitch regisration - can't use 5070 like others

#host_port=5077

#contact_url=sip:skypetestuser@SipToSisIpAddress:SipToSisHostPort

#from_url="skypetestuser" <sip:skypetestuser@freeswitchIPAddress:freeswitchHostPort>

#username=skypetestuser

#realm=freeswitchDeterminedRealm

#passwd=skypetest

#expires=3600

#do_register=yes

#minregrenewtime=160

#regfailretrytime=15

# --- end of FreeSwitch Reg example ---

#do_unregister=yes

#do_unregister_all=yes

#keepalive_time - set to zero to disable keep alives

keepalive_time=45000

audio=yes

#following is the SIP RTP port base - use an even port number

audio_port=63200

#auto hangup after no rtp packets received for ? seconds

noRtpReceivedAutoHangupSeconds=30

#only PCMU,PCMA,GSM (jmf lib),GSMTRI (tritonus libs) codecs currently supported - first one is the preferred codec

#You can append RW to the codec name to disable sample averaging - use need to use filter with those.

#Speex doesn't not work well at all - mass cpu usage

audio_codec=PCMU,PCMA,GSMTRI,ILBC,SPEEX

#PCMU/PCMA allow 160,240,320 - GSM allows 160 - ILBC allows 240, Speex allows 160, Speex16k allows 320 - need one size for each codec specified

audio_frame_size=240,240,160,240,160

#if using dynamic payload types (speex and ilbc) you must specify the payload number (asterisk uses 98,97), if not you can remove this parameter

audio_avp=-1,-1,-1,98,97

#Audio volume gains - 1 for each codec - (decimal number) 1=flat no gain, higher=louder, too high will clip or distort

#volume sip->skype

skype_audiooutgain=1,1,1,1,1

#volume skype->sip

skype_audioingain=1.5,1.5,1.5,1.5,1.5

#Filter skype audio before being downsampled and sent to SIP device.

#No Filtering

FilterParams=NONE

#RC lowpass filter

#RC,delay time (lower lowers cutoff),RC constant (higher lowers cutoff) - 50,40 is a good starting point

#FilterParams=RC,50,40

#FIR filter

#FIR,Order (higher sharper cutoff and more cpu),window type (RECTANGULAR,HANNING,HAMMING,BLACKMAN),filter type (LP,HP,BP),minFreq,maxFreq

#FilterParams=FIR,100,HANNING,LP,0,3200

#FilterParams=FIR,100,HANNING,HP,300,3200

#FilterParams=FIR,100,HANNING,BP,300,3200

#If yes, will send RTP packets to address received from the otherside

# instead of what was received in the session descriptor.

# This may help with one way audio problems.

enableSendRTPtoReceivedAddress=yes

#works with above setting - sending of rtpPackets can be redirected until receiving this number of packets. After that the address is locked.

lockRtpSendAddressAfterPackets=1

#Set to -1 to disable rfc2833 some providers use 96 most use 101

dtmf2833payloadtype=101

#Use these for SIP INFO msg support - first is the most common type

#dtmfinfotype=application/dtmf-relay

#dtmfinfotype=application/dtmf

#Use only if rfc2833 and INFO are not supported - uses more cpu

enableSIPInbandDtmfDetector=no

SipDtmfDetectorHitThreshold=30

SipDtmfDetectorSilenceThreshold=6

#params to control sip response address handling

useViaRport=yes

useViaReceived=yes

#send all responses using outbound proxy - outbound proxy must be set up

sendResponseUsingOutboundProxy=no

#sip response for any uncovered reason

baseFailureResponse=403

#sip response if remote skype user refused call

skypeRefusedResponse=603

#sip response if skype call failed, invalid skype user, or no skype credit

skypeFailedResponse=404

#sip response if skype returned unplaced status

skypeUnPlacedResponse=408

#sip response if called party is busy

skypeBusyResponse=600

#network buffers for skype api audio transport (0=leave at OS default)

TcpRxBufferSize=8192

TcpTxBufferSize=8192

#network buffers for RTP audio transport (0=leave at OS default)

RtpRxBufferSize=8192

RtpTxBufferSize=8192

#*** register server settings below *** not required if registration is not needed for phone

#set to yes to turn on server registrar or no to disable

is_registrar=yes

#set to yes to allow register of users not already in registar database (users.db)

register_new_users=yes

#set to domains of server - see mjsip doc

#domain_names=192.168.0.4 somedomain.com

allowMultiContactsPerUser=no
</pre>

And you will need something like this in your SkypeToSipAuth.props:

<pre>
*,sip:panel@pbx.sonologic.net:5060
</pre>

Somehow it seems to dial the sip uri without registering, so panel must be in the public incoming SIP context.

== Known issues ==

* siptosis - spy output is very choppy, is this for all sip channels?? needs testing, spy works perfect when spying on iax channels
* killing siptoskype without hanging up the incoming skype call will result in odd lingering channels in asterisk, messing with your head

VacuumFluorescentDisplays

2011-10-01T23:26:18Z

10.42.42.9: Created page with " This is mostly a page to collect information about the VFD's we acquired from Stuut&Bruin, which will ultimately be used in the air-hockey scoreboard replacement. http://hem.p..."

This is mostly a page to collect information about the VFD's we acquired from Stuut&Bruin, which will ultimately be used in the air-hockey scoreboard replacement.

http://hem.passagen.se/communication/vfd.html

They have been manufactured by Futuba, type numbers 5-LT-02 and 4-LT-16.

* Video of 4-LT-16 being driven by arduino: http://www.twitvid.com/WJBR8

* Pinout Futuba 4-LT-16 VFD: 
<img src="/old/IMG_2239.JPG" alt="IMG_2239.JPG" width='640' />

* Driving a Futuba 4-LT-16 with TTL output (Arduino): 
NOTE: THE 10K RESISTORS NEED TO BE PULL-UPS (AND THUS CONNECT TO +12V INSTEAD OF GROUND) 
<img src="/old/IMG_2240.JPG" alt="IMG_2240.JPG" width='640' />

* Futuba 5-LT-02 (top) and 4-LT-16 (bottom) VFD: 
<img src="/old/IMG_2249.JPG" alt="IMG_2249.JPG" width='640' />

UsbProtoReverseEngineeringWS

2011-10-01T23:26:16Z

10.42.42.9: Created page with " = USB protocol reverse engineering workshop = Friday July 22 we're organizing a workshop on reverse engineering USB protocols of devices with proprietary protocols.<br ..."

= USB protocol reverse engineering workshop =

Friday July 22 we're organizing a workshop on reverse engineering USB protocols of devices with proprietary protocols. Reverse engineering protocols is fun! It's like a puzzle, and if there's software out there that can solve the puzzle, your brain can do it too. We'll be taking a look at reverse engineering the protocols on USB-connected devices. Too many of these devices still come with windows drivers only, and use an undocumented protocol. Figuring out those protocols is often a lot easier than you might think, and so is writing a simple driver. If you want to participate in this workshop, bring a Linux laptop, preferably with a virtual machine with a Windows guest OS. If you have an exotic USB device that only has a Windows driver, please bring that too. This workshop will be given by Bert Vermeulen and Hans de Goede. Bert has reverse engineered and written drivers for various USB logic analyzers for sigrok: http://sigrok.org . Hans has reverse engineered and written drivers for various USB webcams for the Linux kernel and for digital photoframes for libgphoto2.
== Program ==
* 19:00: Welcome, drinks
* 19:30: Start of the workshop Bert & Hans give a short intro on USB protocol principles and a short demo of sniffing and interpreting usb traffic
* 20:15: Time to get your hands dirty, start reverse engineering your own USB device, or one of the devices provided. Your hosts will be walking around to answer questions and help you pass any speedbumps you encounter.
* late: Time to go home?
* really late: Chances are your hosts will want to go home at this time, hint hint.
== Registration ==
Registration is not mandatory, but in order to have an idea of how many people will be coming we kindly request you to send an email to hdegoede@redhat.com if you're going to attend.
-- Main.HansDeGoede - 23 Jun 2011

TwinklingBar

2011-10-01T23:26:15Z

10.42.42.9: Created page with " On a stormy sunday night on #revspace, fenrir saw the [httphttp://www.leds-buy.nl/led-terrenhemel-42-leds-1629.html led starry sky] at leds-buy, and tought it would be neat to ..."

On a stormy sunday night on #revspace, fenrir saw the [httphttp://www.leds-buy.nl/led-terrenhemel-42-leds-1629.html led starry sky] at leds-buy, and tought it would be neat to have this in the hxx/eth0 bar. Some discussion ensued, and it was decided: we will build one.

The basic gest of the design: some microcontroller to drive the whole-shebang, a bunch of PWM controllers to take input from the microcontroller and drive the leds and presto. Aiming for about 100 RGB leds.

| *Part* | *Pieces* | *Price* | *Besteld* | *Real price* |
| [httphttp://nl.mouser.com/ProductDetail/Texas-Instruments/TLC5941NT/?qs=sGAEpiMZZMtEZf%252bBk5%2f8xwZiHP6816qs TLC5941 28pdip (pwm controller)] | 20 | 54.75 | 2010-01-31 | 65.70 |
| [httphttp://www.leds-buy.nl/standaard-leds/full-color-leds/fading-full-color-led-90-graden-5mm-ca.html rgb led CA, 5mm 90 graden] | 100 | 98.77 | 2010-01-31 | 84.79 |
| Arduino | 1 | 30.00 | | |
| Flat-cables | 1 | 50.00 | 2010-01-31 | 12.68 |
| connectors between controller boards [httphttp://nl.farnell.com/harting/09-18-506-7803/socket-idc-w-o-s-relief-6way/dp/1106769 female] + male headers | 40 | 80 | 2010-01-31 | 30.50 |
| connectors between controller boards [httphttp://nl.farnell.com/harting/09-18-506-7803/socket-idc-w-o-s-relief-6way/dp/1106769 female] + male headers | 40 | 80 | 2010-01-31 | 8.25 |
| arduino proto shield | 1 | 5.00 | | |
| montagedraad | 1 rol | 10.00 | 2010-01-31 | 2.07 |
| [httphttp://www1.conrad.nl/scripts/wgate/zcop_nl3/~flN0YXRlPTQzMDI0NzE2NQ==?~template=pcat_area_s_browse&perform_special_action=DirektContentTemplate&template=Z_STICHWORTVERZEICHNIS&p_page_to_display= printplaten] | 20 | 70.20 | | |
| misc (resistors, transistors, ..) | x | 20.00 | | |
| 4-aderige kabel | 1 rol | 40.00 | | |
| hout + verf | 1 | 50.00 | | |
| Total | | %CALC{"$SUM( $ABOVE() )"}% | | %CALC{"$SUM( $ABOVE() )"}% |

PWM controllers:
* [httphttp://focus.ti.com/docs/prod/folders/print/tlc5940.html TLC5940] - pretty neat, individual control
* [httphttp://nl.farnell.com/on-semiconductor/cat9532wi/led-driver-16bit-program-24soic/dp/1656134 CAT9532WI] - cheaper but less control

Some wild ideas:
* make it sensitive and react to E/M or perhaps light/IR sensors
* sensitive to sound
* web-interface

Winkelwagentje
HACKER SAFE certified sites prevent over 99.9% of hacker crime.

Mouser-onderdeel # OF fabrikantonderdeel# Uw onderdeelnr. * Aantal

* Uw onderdeelnr. is een optioneel veld.

*

Om deze bestelling op te slaan als een project,
Aanmelden of een My Mouser-account aanmaken

Alles selecteren
Dit winkelwagentje opslaan Dit winkelwagentje delen met een collega

Verwijderen Productdetail
Klantonderdeelnr.

Besteld aantal

Prijs
(EUR)

Toestel
(EUR)

Mouser-nr. 517-929836-01-03-RK
Fabrikantnr: 929836-01-03-RK
Fabrikant: 3M
Omschr.: Headers & Wire Housings 6P PIN STRIP HEADER STRAIGHT, TIN, 2ROW
RoHS: RoHS-conformiteit

Een asterisk, '*', is geen geldig teken voor het klantonderdeelnummer. Niet-ondersteunde tekens: {0}

Beschikbaarheid
50 Wordt nu verzonden
� 0,165 � 8,25

Mouser-nr. 517-3365/06-100
Fabrikantnr: 3365/06-100
Fabrikant: 3M
Omschr.: Flat Cable .050 6C ROUND 28AWG GRAY STRANDED WIRE
RoHS: RoHS-conformiteit

Een asterisk, '*', is geen geldig teken voor het klantonderdeelnummer. Niet-ondersteunde tekens: {0}

Beschikbaarheid
1 Wordt nu verzonden
� 12,68 � 12,68

Mouser-nr. 595-TLC5941NT
Fabrikantnr: TLC5941NT
Fabrikant: Texas Instruments
Omschr.: LED Drivers 16ch LED driver with DC 12bitG/S
RoHS: RoHS-conformiteit

Een asterisk, '*', is geen geldig teken voor het klantonderdeelnummer. Niet-ondersteunde tekens: {0}

Beschikbaarheid
30 Wordt nu verzonden
� 2,19 � 65,70

* [%ATTACHURL%/pwm-double-duo.ps|pwm-double-duo.ps]: Iteration 4 of the pcb

TopicType

2011-10-01T23:26:13Z

ToiletDetect

2011-10-01T23:26:12Z

10.42.42.9: Created page with " -- Main.JoeriJungschlager - 13 Sep 2010 Main INFO: Just idea we brought on a evening. So just for fun if it exactly got working cool, the main goal is too detect when out of t..."

-- Main.JoeriJungschlager - 13 Sep 2010

Main INFO:
Just idea we brought on a evening.
So just for fun if it exactly got working cool, the main goal is too detect when out of toilet paper.

Documentation:

-NONE

So far build:

LED (yellow) on wooden block Wiring basic electro, building for digital.

NEED TO BUILD

Same kind block with same formats for holding toiletpaper Light detection with red led

NEED TO BUILD (digital progame App that sends too

NOTE:
-If you have read this wiki page feel free too research and costumize on this project.
-Edit the wiki what you've done with a link if software is included
-Light brightness between the toiletpaper and the roll is too thin too calute.

Discussion:
-Make a light bridge to detect
* Done a yellow light what is close too white, go for an blue or yellow on the other sight and detect with the yellow light the other

TikiTagOrder

2011-10-01T23:26:11Z

10.42.42.9: Created page with " = Tikitag mass order = To aid research into RFID (most specifically the mifare classic family of chips) a suitable RFID reader/writer is unbearable. We're planning on ordering..."

TestPage

2011-10-01T23:26:09Z

10.42.42.9: Created page with " Test topic -- Main.KoenMartens - 23 Aug 2009 * Set VIEW_TEMPLATE = View"

Test topic

-- Main.KoenMartens - 23 Aug 2009

* Set VIEW_TEMPLATE = View

TerrabyteDinnerDevice

2011-10-01T23:26:08Z

10.42.42.9: Created page with " %REDIRECT{"TeraByteDinnerDevice"}%"

%REDIRECT{"TeraByteDinnerDevice"}%

TeraByteDinnerDevice

2011-10-01T23:26:06Z

10.42.42.9: Created page with " = The terabyte dinner device = __FORCETOC__ == Introduction == Remember the sneakernet? Oh those glorious days. But with the advent of the internet, carrying physical media..."

= The terabyte dinner device =

__FORCETOC__

== Introduction ==

Remember the sneakernet? Oh those glorious days. But with the advent of the internet, carrying physical media around has become obsolete. Or so we thought! Various organisations (mostly Hollywood lobbyists) think downloading is something evil, something that should be banned. With their dollars they get governments to prosecute children and fanclubs worldwide. Technology such as bittorrent are painted as illegal practices, and efforts to ban it all together are underway.

Enter the Terabyte Dinner! Invite some friends over for a nice meal, have them bring an external 1TB hard-drive each and hook them up to your Terabyte Dinner Device. Enjoy the food and the company, and when the evening ends each of you will have 750+GB of new content, software or literature. All in crisp digital quality. And without leaving a trace that might implicate you for committing the horrendous crime of exchanging information!

== Funding ==

The idea as well as initial funding was provided by Arjen and Aldert. The prototype will be presented during the [httphttp://eth-0.nl/ eth0 summer event], where we will organise a workshop where participants can build their own terrabyte dinner device, and hopefully the first terabyte dinners will take place.

If you want to fund this project, do contact treasury@revspace.nl. It's not all expensive, but there are some costs.

== Workshop ==

A workshop at revspace will be planned in late April or early May to start building the very first development model and kick off further action. In the time before that, we will discuss possible designs and purchase the first components (not necesarilly focussing on a single design).

== Design goals ==

* Simple to use, just plug in and press the big red button;
* No moving parts;
* Ultra-small form factor;
* Interface:
** 8 USB 2.0 (3.0?) interfaces;
** 8 RGB leds for each USB port, indicating the current status of the attached disk:
*** off - no disk attached;
*** blinking red - disk inserted, mounting / scanning;
*** red - disk failure;
*** blue - disk full;
*** yellow - copying;
*** green - copying complete, disconnect;
*** green blinking - disk mounted, ready for copying.
** one rgb led for general status (on, booting, awaiting disks, in progress, ready);
** an on/off switch and an 'initiate copying' button;
* Easy to build, minimum amount of soldering or mechanical work;
* Use off the shelf components:
** power supply;
** CPU board with i/o and boot storage device;
** casing.
* Provide special parts as kit that people can build or buy
** pcb with rgb leds, switches and interfacing to CPU board;
** power supply;
** USB port risers (if needed).
* Hardware design as well as software completely open;
* Self-powered (battery) for use in pubs, restaurants and other public areas;
* Viral spreading of the blueprints.

Optional:

* Ethernet port for configuration;
* Dot-matrix display for more detailed status reporting;
* Format new devices;
* Crypted filesystems
* Library of what you have at home to prevent duplicate content;
* file-naming standard (StarTrek_TNG_e06s06.avi) and auto-renaming to keep things consistent;
* Personal preferences in xml on your disk, eg. get all sf series with lesbian bondage first, then all other sf, then action movies, then Bach cantates and finally the natgeo documentaries about insects
** directory naming conventions
** tagging
** IMDB/CDBaby
* Software to run on random pc to emulate TBDD

== General operation ==

* tbdd is powered on, and boots;
* Guests arrive and plug in their disks;
* tbdd checks the disks for compatible filesystem (vfat, ext2, ext3, zfs, ...) and free space;
* tbdd copies its own design blueprint onto each connected disk in the /in folder;
* once all guests have arrived, they press 'go' on the device;
* tbdd copies the /out folder from each disk to the /in/XXX folders on all other disks (where XXX could be the disk label of the source disk, or simply the usb port number);
* once completed, guests take their disk out and go home.

In case a newly inserted disk can not be used, it is rejected. The RGB led corresponding to the USB port for that disk indicates this to the users. Circumstances that make a disk unusable: hardware failure, incompatible file-system, not enough space.

Note that the TBDD does not touch anything outside /in and /out, so the disk can be used to carry additional data.

== Feasibility ==

* 8 devices for each of which:
** 100GB needs to be read
** 700GB needs to be written
* With one USB controller, speed is limited to 480Mbps, half duplex.
** We assume read and write speeds to be 480Mbps (very optimistic).
* We assume the source device is only read once.
* We assume each device needs to be addressed separately, i.e. write commands cannot be multiplexed and thus need to be executed 7 times.
* [httphttp://www.google.com/search?q=%288+*+800GB%29+%2F+480Mbps (8 * 800GB) / 480Mbps] = *1.26 days*

* Assuming 1 USB controller per disk (4+ controllers are quite common these days)
** 800GB / 480 Mbps = 2:13 Hours
* Using a more sane disk-speed average:
** 800GB / 35 MB/sec = 6:20 Hours

-- Main.MarkJanssen (praseodym) - 05 Apr 2010
-- Main.FooBar - 06 Apr 2010

== Technical Details ==

CPU board:
* Mini-ITX sized atom board, commodity hardware, easy to use and develop for;
* Suitable SoC, less standard but smaller footprint (space-wise as well as power requirements);
* Repurposed CPU board from commodity hardware such as linksys/sheevaplug/pogoplug;

Power supply:
* Look for kits
* Repurposed power supply

== Shopping list ==
* Atom mainboard with enough USB2: http://www.paradigit.nl/info.php?group=3&art=10022107 130 euro's
** Even has HDMI, so could be connected to HD-TV for progress-info/control and media-viewing ?
* Memory: 30 Euro's for 1GB DDR2 (512 should be more then enough, 256 will probably do?)
* Case: http://tweakers.net/pricewatch/240866/antec-isk-300-65.html (60 euro)
* A small USB-stick, SD-Card or cdrom to boot from (10-25 euro)
Total price: 230 euro

Or

* http://shop.ngxtechnologies.com/product_info.php?cPath=31&products_id=72 (EUR 44)

== Alternatieven: ==
* http://tweakers.net/pricewatch/239369/acer-aspire-revo-r3600-nettop.html (260 euro?)

= Related links =

* http://k0a1a.net/netless
* http://www.deadswap.net/

-- Main.FooBar - 30 Mar 2010
-- Main.KoenMartens - 02 Apr 2010

TegeltjesWijsheden

2011-10-01T23:26:05Z

10.42.42.9: Created page with " = Tegeltjes wijsheden = <img style="float: right;" src="http://www.stepbridge.nl/stepkrant/files/u3/tegeltje-b_0.jpg"/> In The Netherlands we have an old tradition of pu..."

= Tegeltjes wijsheden =

<img style="float: right;" src="http://www.stepbridge.nl/stepkrant/files/u3/tegeltje-b_0.jpg"/> 

In The Netherlands we have an old tradition of putting wise phrases on painted tiles. For examples, just do [httphttp://www.google.com/images?q=tegeltjeswijsheden a google image search].

We want to produce tegeltjeswijsheden with hacky quotes.

== Spreuken ==

Real men do it with hardware!

Als je moet virtualiseren, zijn je jobs te klein.

Na downtime komt uptime.

Na uptime komt downtime.

There is no such thing as too much [ bandwidth | diskspace | cpu-power ]

Al is je PC nog zo snel, Windows vertraagt hem wel

Als er een schaap over de Dam is loopt tie op het Damrak.

TBDDWorkshop

2011-10-01T23:26:03Z

10.42.42.9: Created page with " = Terabyte dinner device workshop = On May 29th, 2010 the terabyte dinner device project invites interested parties to [HowToGetThere|Revelation Space] in The Hague, NL for a..."

= Terabyte dinner device workshop =

On May 29th, 2010 the terabyte dinner device project invites interested parties to [HowToGetThere|Revelation Space] in The Hague, NL for a brainstorming and kick-off workshop to design the citizens answer to ACTA, internet monitoring, content filtering, net neutrality sabotage, criminalization of various behaviour and technology related to downloading and other dangers to the free exchange of content. We are taking the flow of information off-line again, out of reach of the content conglomerates. The return of the [httphttp://en.wikipedia.org/wiki/Sneakernet sneakernet], 2.0 stylee!

Invite some friends over for a nice meal, have them bring an external 1TB hard-drive each and hook them up to your Terabyte Dinner Device. Enjoy the food and the company, and when the evening ends each of you will have at least 750GB of new content, software or literature. All in crisp digital quality. And without leaving a trace that might implicate you for committing the horrendous crime of exchanging information.

At the [httphttp://wiki.eth-0.nl/index.php/Eth0:2010_Summer eth0 summer event in August 2010] participants are invited to built their own TBDD, after which the first terabyte dinners may take place right there and then! Some of the more important design goals: easy to use (even your grandmother should be able to organise a terabyte dinner), using off-the-shelf components, easy to assemble, low energy consumption for terabyte picknicks in the park and a small form factor for maximum portability.

More information about the project, initiated by [httphttp://revspace.nl/ Revelation Space], the [httphttp://hxxfoundation.nl/ Hxx foundation] and [httphttp://www.eth-0.nl/ eth0], can be found on the [TeraByteDinnerDevice|revspace wiki].

If you are into embedded systems, electronics, product design, user interaction or just have a creative mind in general, please come over and join the revolution in content sharing!

When: May 29th, 2010, 14:00 hours. %BR%
Where: [HowToGetThere|Revelation Space], The Hague, NL
Workshop page: %TOPIC%

== Sign up ==

I'll be there:

* gmc
* fenrir
* aloha
* ...

StudioRevSpace

2011-10-01T23:26:02Z

10.42.42.9: Created page with " In order to be able to make live radio for [httphttp://signal.hackerspaces.org/ Signal], and because we can, we have a radio studio in the space. It is sharing a room with the ..."

In order to be able to make live radio for [httphttp://signal.hackerspaces.org/ Signal], and because we can, we have a radio studio in the space. It is sharing a room with the library.

Usually, you should be able to take a peek in the studio on [httphttp://cam2.revspace.nl/ the studiocam].

== Mixing desk ==

* Behringer Xenyx !X2000USB mixer (8 mic inputs w/ compression, 4 line-in, usb out)
* random old dell (2.3GHz celeron) for playing music and streaming from the mixer's usb feed
* crappy old dell for skype
* KVM to switch between DJ and Skype
* Foob's crappy EUR 20 microphone
* Fish_'s cheap headphones

== Host desk ==

* Behringer HA 400 headphone amp, 4 headphone outputs, for host and studio guests
* Sennheiser E845 mike
* line in from mixer desk

== Plans ==

* Voip PBX with multiple outputs sending to the mixer
* Putting the mixing desk + pc's in a flight case for portability
* Extra flatscreen to eliminate KVM

== Mixing desk howto ==

This place left intentionally blank. Will at some point explain how to use the mixing desk to do a show.

Statuten

2011-10-01T23:26:01Z

10.42.42.9: Created page with " * [%ATTACHURL%/statuten_censored.pdf|statuten_censored.pdf]: Statuten Stichting Revelation Space"

* [%ATTACHURL%/statuten_censored.pdf|statuten_censored.pdf]: Statuten Stichting Revelation Space

SpokePov

2011-10-01T23:25:59Z

10.42.42.9: Created page with " http://www.ladyada.net/make/spokepov/ We will build one or two for Brainsmoke's bike!"

http://www.ladyada.net/make/spokepov/

We will build one or two for Brainsmoke's bike!

SpaceStatusOpen

2011-10-01T23:25:58Z

10.42.42.9: Created page with " The space is now open."

The space is now open.

SpaceStatusClosed

2011-10-01T23:25:56Z

10.42.42.9: Created page with " The space is now closed."

The space is now closed.

SpaceStatus

2011-10-01T23:25:55Z

10.42.42.9: Created page with " The space is now open."

The space is now open.

OldSpaceSoundSystem

2011-10-01T23:25:54Z

10.42.42.9: Created page with " __FORCETOC__ = Space Sound System = One server with many soundcards and pulseaudio. One soundcard per room, each with their own amplifier (the amps are also in the server roo..."

__FORCETOC__

= Space Sound System =

One server with many soundcards and pulseaudio. One soundcard per room, each with their own amplifier (the amps are also in the server room, and can be switched off individually when there is no music playing). One MPD per room, but with pulseaudio audio can be routed at will. With the network-capabilities of pulseaudio, one can send audio from ones laptop to any room.

== Turning the system on ==

There is no need to touch the hardware in the server room. It is configured to turn on the amplifier that is assigned to the room as soon as you try to play audio to that room. There might be a slight delay (5-20 seconds) as the amplifier switches on, warms up and enables the speaker output relays, so be patient.

= Playing music from the library =

Each room is assigned a MPD instance, as follows:

* lounge - host 10.42.66.1 port 6600
* handwerklokaal - host 10.42.66.1 port 6601
* hacklab - host 10.42.66.1 port 6602
* studio - host 10.42.66.1 port 6603

== Web front-end ==

Check out the [httphttp://10.42.66.1/ the main page on the sound server].

== Desktop client ==

There exist [httphttp://mpd.wikia.com/wiki/Clients clients for mpd for most operating systems], besides the canonical command-line mpc client.

= Uploading music =

You can mount the music library with something like:

<pre>smbmount -o guest,uid=foo \\\\10.42.66.1\\music /home/foo/mnt/spacemusic</pre>
The above command may be deprecated. The one below is the replacement.
<pre>mount -t cifs -o guest,uid=foo \\\\10.42.66.1\\music /home/foo/mnt/spacemusic</pre>

If you are into GUI's, in your operating systems' network browser find the workgroup REVSPACE, which will show a host 'transformer' that has the share 'guest'.

= Pulseaudio playback =

You can also stream directly to the pulseaudio server using any of these sinks via a pulseaudio tunnel:

* lounge
* handwerklokaal
* hacklab
* studio

== Linux ==

For example, using mplayer:

<pre>mplayer -ao pulse:10.42.66.1:lounge http://85.17.146.164:80/2</pre>

== OSX ==

No clue, i don't use it. If you manage to make it work, please document here.

== Windows ==

No clue, i don't use it. If you manage to make it work, please document here.

= Volume control =

I tend to use pavucontrol from linux:

<pre>PULSE_SERVER=10.42.66.1 pavucontrol</pre>

The web front-ends also have a volume slider.

= System description =

Server (labelled chip, actual hostname is transformer, long story...) is at 10.42.66.1. It runs:

* pulseaudio
* pulsepower (daemon gmc wrote, needs some improvement)
* 4 mpd's at ports 6600 through 6603

A series of amplifiers receives line-level audio from the two surround soundcards which are configured as multiple virtual stereo cards. The amplifiers have been hacked to varying degrees to boot up in the on state and with the right source selected automatically, and power is controlled by a USB power socket with 4 outlets.

* Workshop - use current amplifier (sony mini-set);
* Main room - use amplifier that is on dj table;
* Studio - use mini-set that is in there currently;
* Hacklab - need amp (reuse system that is now on lackbeamermount?);

== Future plans ==

* Enable RTP sinks, for more stable and portable playback from networked devices
* Standardize on Velleman 150 amplifier kits
* Add volume control knobs in all rooms via RS485 space bus
* Add routing of pulseaudio streams, eg play stream to both studio and lounge simultaneously
* Add web front-end to mpd's and routing/volume control
* more...

== Known issues ==

* The AKAI amplifier can not be power-cycled to quickly; it needs to be off for about 10 seconds before turning on again, or the ne555 circuit will fail to turn on the amp
* pulseaudio ip tunnels over wifi are unstable/choppy (needs rtp)
* No security whatsoever, everything is open to everyone

== Software ==

* ajaxMP web interface for mpd - sadly project is discontinued

* [%ATTACHURL%/ajaxmp-0.6.1.tar.gz|ajaxmp-0.6.1.tar.gz]: tarball obtained from das labor

= Advanced topics =

== Loopback ==

load-module module-loopback source=lounge.monitor sink=studio latency_msec=5

== Apps that don't support pulseaudio ==

On your local pulseaudio:

<pre>load-module module-null-sink sink_name=virtual</pre>

Put in .asoundrc:

<pre>
pcm.pulse {
type pulse
device virtual
}
ctl.pulse {
type pulse
device virtual
}
</pre>

Now configure your app to play to alsa device 'pulse'. You now have the audio on a pulseaudio source 'virtual'. You can cat this to the server for eg:

<pre>pacat -v -r -d virtual.monitor | pacat -p -s 10.42.66.1 -d lounge</pre>

SpacePowerMeter

2011-10-01T23:25:52Z

10.42.42.9: Created page with " Since we use quite a bit of power in the space, and this costs a boatload of moneys... it would be handy to have some insight into the powerusage. In the beginning of july, we..."

Since we use quite a bit of power in the space, and this costs a boatload of moneys... it would be handy to have some insight into the powerusage.

In the beginning of july, we received a new power meter in the space, which is of the more modern 'blinky' kind, as opposed to the spinning wheel. By measuring the amount of blinks from the led, we can electronically read-out the amount of power used.

A ATtiny85 is connected to the ttyUSB0 of gateway, and measures the led-blinks coming from the [httphttp://www.ineprometering.com/products-of-inepro-metering-manufacturer-of-electricity-and-water-meters/inepro-metering-standard-line-electricity-meters.html DRM370A] 3-phase power meter using a LDR.
The ATtiny will send 'PULSE' over a 9600 baud serial connection every time the led on the powermeter flashes.

The powermeter flashes it's led 400 times per kWh, so with this information we can calculate our power usage. (We need to figure out X here, one specsheet says 160, the other 400, the other 800, it should be on the meter itself, google-screenshot says 400)

On gateway, a perl-script monitors the serial port, and logs the amount of received pulses in a logfile... later this will also go to rrdtool or something

== Some Observations ==

| *PPM* | *Watts* | *Situation* |
| 3-4 | 600 | Space closed (so only servers, emergency light, cooling, other permanent infra |
| 8 | 1200 | Background usage, space open, lights on in handwerklokaal |
| 16 | 2400 | Space open, lights on in lounge, hallway and handwerklokaal |

== Code for the attiny85 ==

The code for the attiny85 was written using arduino-tiny (arduino addon for attiny family).

<verbatim class="c">
/*
Analog input, serial output
Reads an analog input pin, prints the results to the serial monitor.
*/

#define SAMPLECOUNT 40
#define DEBOUNCE 40
#define SAMPLEDELAY 20

void setup() {
Serial.begin(9600);
}

void loop()
{
unsigned int c = 0; // Sample counter
int value; // Last value read
int high = 980;
int low = 850;
int last;
int ignore = 0;

while( 1 == 1)
{
c++;
// read the analog input into a variable:
value = analogRead(A2);

// print the result:
if ( value > high )
{
last = 1;
ignore = c;
// Serial.print( "Debug high: " );
// Serial.println(value);
}
else if( value < low )
{
// if ( last == 1 )
// {
// Serial.println( "High to low transition..." );
// }
// Serial.print( "Debug LOW: " );
// Serial.println(value);
if ( c > ignore )
{
Serial.println( "PULSE" );
ignore = c + DEBOUNCE;
}
// else
// {
// Serial.println( "Still in debounce..." );
// }
last = 0;
}
// else
// {
// Serial.print( "DEBUG... MIDDLE VALUE ?!?!?!?!");
// Serial.println( value );
// }

// wait X milliseconds for the analog-to-digital converter
// to settle after the last reading:
delay(SAMPLEDELAY);
if ( c > 65500 )
{
c = 0;
}
}
}
</verbatim>

SpaceLoop

2011-10-01T23:25:49Z

10.42.42.9: Created page with " Sensors will be placed on most windows and outside doors, on closing of the space, a sign/bell will alert if there are still opened windows or doors. About half of the windows..."

Sensors will be placed on most windows and outside doors, on closing of the space, a sign/bell will alert if there are still opened windows or doors.

About half of the windows have been done, a bell will ring if the space is closed when the loop is still open.

Ikarus is working on a nice sign... (work in progress)

Todo:

Sign

Put sensors on the remaining windows

SpaceFashion

2011-10-01T23:25:48Z

10.42.42.9: Created page with " = Fashion = There is an increasingly less vague plan to have !RevSpace hoodies, either produced by eg. smlx (Hxx hofleverancier) or DIY at cabfablab. The general plan is to ha..."

= Fashion =

There is an increasingly less vague plan to have !RevSpace hoodies, either produced by eg. smlx (Hxx hofleverancier) or DIY at cabfablab. The general plan is to have them before 26c3, smlx can even fix that for us!

Some designs up at the LogoContest page, if you have additional ideas or strong preferences make them known!

If you are interested, please put nick and requested size down below. Cost will be EUR 40,-. If you put your name down before, without knowing the actual cost, please put a '1' in the column 'order' now to indicate you're ok with the price and indeed want one!

== Interested parties ==

*REGISTRATION CLOSED*

| *nick* | *size* | *order* |
| gmc | xl | 1 |
| larstiq | l |1 |
| H2oS | l | 1|
|Dekkers|s|1|
|brainsmoke| l | 1 |
| Cinder | xl | 1 |
|Blokje| l | 1 |
|Turiphro| l? | 1 |
| Foobar | xl | 1 |
| Knorrie | xl | 1 |
| Fish (Randomdata) | l | 1 |
| praseodym | l | 1 |
| Anykey | L | 1 |
| you? | xxxl | |

*REGISTRATION CLOSED*

-- Main.KoenMartens - 15 Dec 2009

SpaceBusSpecification

2011-10-01T23:25:46Z

10.42.42.9: Created page with " *CONCEPT* = %NOTOC%Table of contents = __FORCETOC__ = Overview = This specification describes the SpaceBus hackerspace bus network. Its objective is to provide a robust ne..."

*CONCEPT*

= %NOTOC%Table of contents =

__FORCETOC__

= Overview =

This specification describes the SpaceBus hackerspace bus network. Its objective is to provide a robust network for simple devices to communicate over.

A layered approach is followed in the design of the protocol. The table below illustrates the layers:

| *Layer* | *Standard* | *Alternative standards* | *Domain* | *Examples* |
| Application | || uC | user input and sensor events, domotic control |
| Logical | openctrl | uberbus, X10, ... |^| events, control channels |
| Link | SBP | ethernet (link part), udp, ... |^| arbiters, bus devices |
| Electrical | EIA-485 | ethernet (physical part), RS-232, radio FM, ... | wiring, transceivers | UTP, rj-45, T-junctions |

Whereas both the electrical and link layer can be interchanged with other existing standards (such as Ethernet or X.25), for the specific purposes of the space bus those layers are as defined in this table.

= Definitions, terminology and notational conventions =

* Numbers:
** 0xNN - a hexadecimal number, digits in decreasing order of significance (example: 0x4A, 0xb6, 0x88);
** bNNNNNNNN - a binary number, digits in decreasing order of significance (example b00101010, b11111111);
** NN - a decimal number, digits in decreasing order of significance (example 66, 2011, 65535);
** 0NN - an octal number, digits in decreasing order of significance (example 044, 071).
* *arbiter* - device combining bus termination, bias circuitry and media access arbitration;
* *bus address* - link layer device address, only valid on a particular bus;
* *SBP* - space bus protocol, the link-level protocol defined in this specification;
* *space bus* - the whole of electrical, link and logical layer as defined in this specification;

= Electrical layer =

For the purpose of the space bus, the electrical layer is as describe below.

Space is interpreted as logical 0, mark as logical 1.

== Wiring & connectors ==

At the lowest level, SpaceBus consists of a length of standard Category 5 UTP cable. Connections on the bus are made with RJ45 (8P8C) connectors. The communications bus itself consists of an EIA-485 connection over one twisted pair of the cable (designated A and B as per the EIA-485 spec). Another twisted pair (A' and B') is used as return for [%TOPIC%#T_junctions|T_45junctions]. The remaining two pairs are used to provide +48VDC power in accordance with the [httphttp://lib.euroinfomedia.com/index.php?mact=DownCnt,m61d78,click,1&m61d78name=802.3at-2009&m61d78link=..%252Ffiles.euroinfomedia%252Fstandarts%252Fieee%252F802.3at-2009.pdf&m61d78returnid=88&page=88 IEEE 802.3at-2009 standard] for Power over Ethernet (pinout alternative B). This will minimise damage to computers should the cable be confused for one carrying Ethernet. The specific pinout is as follows:

| Pin no. | Pair no. | Colour | Name | Description |
| 1 | 3 | white-orange | A' | In T-junction: EIA-485 II. In regular wiring: unused |
| 2 | 3 | orange | B' | ^ |
| 3 | 2 | white-green | A | EIA-485 I |
| 4 | 1 | blue | DC+ | Positive power. Can be lower than 48V due to cable loss. In accordance with PoE spec. |
| 5 | 1 | white-blue | DC+ | ^ |
| 6 | 2 | green | B | EIA-485 I |
| 7 | 4 | white-brown | COM | Both power return and EIA-485 reference. |
| 8 | 4 | brown | COM | ^ |

== Termination and bias ==

The bus is terminated at both ends with a resistor equivalent to the typical resistance of the cable (100ohm for UTP). In addition, a bias is applied to keep the idle level of the line as 'space' (logical low). Termination and bias-circuitry is combined with link-level arbitration of media access as described in [SpaceBusSpecification#Space_bus_flow_control_40sbfc_41|Space bus flow control (sbfc)].

== T-junctions ==

To provide easily accessible bus devices in a room while keeping main wiring overhead and the bus linear (preventing stubs), one pair is designated as a return pair, making T-junctions with one cable possible. A simplified representation of the wiring can be found in figure 1.

<img alt="splitter-wiring.png" height="238" src="%ATTACHURL%/splitter-wiring.png" title="splitter-wiring.png" width="400" />

== Bus power ==

A single bus will be powered by a stand-alone power supply. The power adheres to the PoE standard (

= Link layer =

At the link-level, the space bus protocol (SBP) regulates access to the (shared) bus and specifies adressing of physical devices. Each unit of data transmission on the link level is a _frame_, which consists of a series of bytes. Bytes are sent as logical ones and zeroes as defined in the electrical layer, with the least significant bit first. A further division is made in bytes and words:

* *byte* - 8 bits
* *word* - 16 bits, little endian (least significant byte first, most significant byte last)

A frame of n bits is formatted as:

| 0-47 | 48-(n-8) | (n-8)-(n-1) |
| header | payload | checksum |

== Header ==

The header is further specified as:

| 0-7 | 8-15 | 16-23 | 24-31 | 32-39 | 40-47 |
| sync | type | len LSB | len MSB | dst | src |

| *shorthand* | *type* | *definition* |
| sync | byte | pattern of alternating 1 and 0: b10101010 (note, sent over the wire as space-mark-space-mark-space-mark-space-mark) |
| type | byte | 0x00 - SBP flow control (sbfc) |
|^| byte | 0x01 - openctrl |
| length | word | frame-length expressed in bytes, including header and checksum, len(payload)+7 |
| dst | byte | destination bus address |
| src | byte | source bus address |\

Addresses range from 0-255, with the special address 0 being reserved as the broadcast address.

== Checksum ==

Some way of checking correct transmission.

== Space bus flow control (sbfc) ==

The only frame-type reserved for the link layer is 0x00, which indicates a frame used in SBP flow control. The payload of a single sbfc frame has a length of one byte, and can contain the following values:

* 0x00 - RTS (Request To Send)
* 0x01 - CTS (Clear To Send)
* 0x02 - HELLO
* 0x03 - PR (Pulse Request)
* 0x04 - PAC (Primary Arbiter Pulse)
* 0x05 - SAC (Secondary Arbiter Pulse)

Access to the bus is arbitrated by a special device: the arbiter. To provide redundancy, two arbiters are placed at each end of the bus. A jumper on each arbiter configures one as the primary and the other as the secondary. The primary arbiter listens for RTS frames sent by the attached devices, queues CTS responses and monitors succesfull transmission. The arbiter (nor the entire SBP protocol) makes any guarantee about successful transmission and reception of a given communication. The secondary arbiter will stand by idle under normal circumstances. When it detects that the primary arbiter has gone off-line, it will take over. Arbiters have no bus address and communicate primarily with the broadcast address.

Insertion of a new device results in the following dialogue between the device (D1) and the active arbiter (A):

| D1(1)->B(0) | RTS |
| ... | optionally, other bus traffic occurs as decided by the arbiter |
| A(0)->D1(1) | CTS |
| D1(1)->B(0) | HELLO |

The CTS sequence will enable the device to synchronize with the bus. It knows the exact bitstream that comprises the CTS packet, and can thus scan the bus until it has matched the entire bit-stream. It can not do this relying solely on the sync pattern, as this may also be a valid part of the header or payload. Note that the particular bit-stream can still be part of a payload. *CONCERN*

= Logical layer =

The [httphttp://openctrl.org/ openctrl protocol], which is still under heavy development, forms the logical layer.

= Application layer =

The specification does not define the application layer.

= Raised concerns =

== C1 - synchronisation ==

Relying on the synchronisation frame is not working, since the sync pattern may be a legit part of the payload.

Relying on the CTS packet sent in response to the initial RTS on device insertion is also not safe: the particular CTS packet could be a legit part of a payload.

Proposed solution: add a 9th bith that alternates between 1 and 0, this can help in synhronising up with the bitstream, and enables line-idle detection.

SpaceBus

2011-10-01T23:25:45Z

10.42.42.9: Created page with " github: https://github.com/RevelationSpace/Space-Bus type="parent" web="%WEB%" topic="%TOPIC%" title="See also:" format="$n * $topic$n" }% Due to ..."

github: https://github.com/RevelationSpace/Space-Bus

type="parent"
web="%WEB%"
topic="%TOPIC%"
title="See also:"
format="$n * $topic$n"
}%

Due to increasing numbers of interesting infrastructure projects, and how annoying (i.e. impossible) Ethernet is to implement on a small microcontroller without extra hardware, we've decided to implement a hackerspace-wide low-speed bus system. This will allow devices to communicate, opening up many interesting project interactions (hook up the <a href="AirHockeyScoreBoard" title="Air hockey score board project">air hockey score board</a> to the <a href="SpaceSoundSystem" title="Space sound system project">sound system</a> or what have you), as well as your run-of-the-mill domotics stuff (controlling the lights in a semi-intelligent manner, for example). This page serves to coordinate and document the design (and later, implementation) of this system.

We have completed a first iteration of the link-level protocol design, and intend to use openctrl as the logical-layer protocol. Currently, we are prototyping hardware and implementing a portable C library along with a few platform-dependent drivers.

== Planning/TODO ==

Current work involves:
* Writing of a clean, modular protocol stack for devices. [Main/RoySmeding|smeding] and [Main/KoenMartens|gmc] have started work on the generic SBLP library and an ATTiny85 implementation.
* Developing, building and testing reference hardware

Once a fully working reference implementation has been developed, up to (at least) the SBLP layer, we can begin to wire the space and develop more actual bus hardware.

== Previous meetings ==

The first meeting/brainstorming session was scheduled for the evening of Friday, July 15th 2011.

What was done:
* Everyone formally agreed on the electrical spec, which had already been discussed extensively. For wiring, cat5 & 8p8c were chosen with a pin-out supporting data, power and return for T-junctions (see specification)
* A first draft of the link-layer protocol was thought out, though this has since been revised (see the specification linked above for the current draft)
* A whiteboard simulation of above protocol was done to check for any obvious errors.
* The line drivers gmc ordered were tested (and found to be working adequately) and some rough tests were done to gauge possible transmission speeds. Limits imposed by the electrical layer were found to probably be unattainable in a microcontroller anyway.

== Wishlist ==

These are the general things we're looking for in the protocol:
* Robustness - e.g. powering on a welder in the space should at most cause a transient disturbance of the bus
* Simplicity: implementation should run on an AVR family microcontroller with a minimum of external parts
* Low cost: aforementioned external parts shouldn't cost more than the rest of the project to be connected to the bus, in general
* Possibility for many different underlying networks: its own dedicated electrical bus, Ethernet, wireless, etc. with bridges between them.
* Many-to-many operation: No real master/slave distinction except possibly some simple hardware to keep the bus sane electrically... communications should be possible from any device to any device directly, as well as "event"-type broadcast messages.

== Reference implementation ==

To demonstrate the viability of the bus design and provide a starting point for other projects, it seems like a good idea to develop a reference implementation of several bus devices. This also helps for showing what bugs may exist in the design itself, and what additional features are desirable. I think the reference implementation should consist of:
* A device demonstrating event functionality: this could be something like a spacebus-enabled space-is-open switch
* A device demonstrating analog/digital in/outputs and possibly another device to read them out, e.g. a sensor and/or relay board
* A bridge between the space bus and rs-232 or usb so a computer can be connected and possibly export the bus over tcp/ip

== Bridging and adressing ==

One question to ponder upon is whether the logical layer needs an adressing scheme seperate from the link-layer adressing scheme. Note that 'link-layer' is kind of a vague target here: udp could be used as the link-layer protocol on top of which the logical-layer protocol sits.

Imagine a bridge between a rs485 bus and an ethernet with IP. The bridge would need to know what devices are on the rs485 bus, but also what devices are on the ethernet bus.

The logical addresses provide a uniform adress space for devices on any kind of bus. I'm just brainstorming here, but suppose you take a 16-bit field as the logical address. You can then split this up like so:
* bit 15-12 : network
* bit 11-0 : device

Which would give you 4 bits = 16 possible networks, and 12 bits to address individual devices on the bus (of course, you can play with the exact split point, or even introduce further distinctions).

A simple avr will be able to send simple packets with logical addresses over the rs485 bus. A bridge on the rs485 network can read the packets, see that it is actually destined for a device on another network and will forward the packet. If it is another rs485 bus, nothing special will need to be done. Yet, if it needs to go over ethernet, it will have to get the logical packet out of the link-level frame, and repack it in another link-level frame (eg udp).

You could take the logical address 0xffff to mean 'broadcast', and this would then be forwarded to all busses (mind the loops!).

== Images ==

First experiment: sending 1-0-1-0-1-0 continuously we went up to 1mbit/sec.

%IMAGEGALLERY{}%

== Links to other systems / pointers ==

* http://www.swharden.com/blog/2011-07-09-sound-card-microcontrollerpc-communication/
* http://hackaday.com/2011/07/10/sound-card-microcontrollerpc-communication/

= Sketchbook =

* add 9th bit, alternating between 0 and 1 each byte? enables line-idle detection ??
* prioritizing traffic -> fairness/starvation prevention in arbiters

SpaceBuildingTodo

2011-10-01T23:25:43Z

10.42.42.9: Created page with " %REDIRECT{"GeneralPlanning"}%"

%REDIRECT{"GeneralPlanning"}%

SoundcloudRevmeet2011

2011-10-01T23:25:42Z

10.42.42.9: Created page with " https://revspace.nl/RevelationSpace/SoundcloudRevmeet <- staying page for yearly event Eventpage The Schedule: Doors Open 14:30 15:00 Relax Lounge, Drinks & Food [no..."

https://revspace.nl/RevelationSpace/SoundcloudRevmeet <- staying page for yearly event

Eventpage

The Schedule: Doors Open 14:30

15:00 Relax Lounge, Drinks & Food [not sure for food]

15:00 opening

Acts: 15:05* 15:30* 15:55* 16:05* 16:30* 16:50 --- FOOD ORDER Break!! Choice between Wok (vegan-friendly) or Pizza 17:05* 17:30* 17:45* -- Last lounge act till 18:20

Build up for the next peroid + welcome talk for peroid 2

18:30 DJ's, bands & acts

 Acts: * (DJ) * (first band) * * * * * *

SoundcloudRevmeet

2011-10-01T23:25:40Z

10.42.42.9: Created page with " -- Main.joeridamian - 18 Aug 2011 This meeting is for soundcloud meetups!!! Exactle meeting details will be discussed on: http://www.meetup.com/Soundcloud/s-Gravenhage-NL/325..."

-- Main.joeridamian - 18 Aug 2011

This meeting is for soundcloud meetups!!!

Exactle meeting details will be discussed on: http://www.meetup.com/Soundcloud/s-Gravenhage-NL/325911/

How ever the day details:

Every DJ/Prdocer get's a showcase of 20 minutes up till 40 depens of the amount of participents Every band can get a acoustic show case of 20 minutes.

For something else fully amplified bands can get up till 2 mics untill now breng own amps and drums. So that would need more help. Planned for 40/50 Minutes

The Schedule: Doors Open 14:30

15:00 Relax Lounge, Drinks & Food [not sure for food]

15:00 opening

Acts: 15:05* 15:30* 15:55* 16:05* 16:30* 16:50 --- FOOD ORDER Break!! Choice between Wok (vegan-friendly) or Pizza 17:05* 17:30* 17:45* -- Last lounge act till 18:20

Build up for the next peroid + welcome talk for peroid 2

18:30 DJ's, bands & acts

 Acts: * (DJ) * (first band) * * * * * *

SolderingWorkshop

2011-10-01T23:25:39Z

10.42.42.9: Created page with " Soldering is fun, soldering is elementary and a required skill for some hardware hacking. Let's just have a basic circuit that flashes some leds, provide some PCB and go!"

Soldering is fun, soldering is elementary and a required skill for some hardware hacking. Let's just have a basic circuit that flashes some leds, provide some PCB and go!

Shirts2010

2011-10-01T23:25:38Z

10.42.42.9: Created page with " The design of the RevSpace shirts: Licence: CC-by * [%ATTACHURL%/chicken_shirt_design.svg|chicken_shirt_design.svg]: chicken_shirt_design.svg * [%ATTACHURL%/chicken_shirt_f..."

The design of the RevSpace shirts:

Licence: CC-by

* [%ATTACHURL%/chicken_shirt_design.svg|chicken_shirt_design.svg]: chicken_shirt_design.svg
* [%ATTACHURL%/chicken_shirt_front.svg|chicken_shirt_front.svg]: chicken_shirt_front.svg
* [%ATTACHURL%/chicken_shirt_front_bottom.svg|chicken_shirt_front_bottom.svg]: chicken_shirt_front_bottom.svg

SensingChessboard

2011-10-01T23:25:36Z

10.42.42.9: Created page with " To create a chess-board that can sense the position of the various chess-pieces. Probably based on some form of induction-influencing phenomena such as magnets of different st..."

To create a chess-board that can sense the position of the various chess-pieces.

Probably based on some form of induction-influencing phenomena such as magnets of different strengts or tuned circuits.

Idea: a properly tuned LC-circuit will, once the capacitor is charged, resonate at a precise frequentie determined by inductance and capacity. The LC-circuit is mounted in each chess-piece, with a different resonance frequency for each type of piece/color. A coil under the playfield will charge the capacitor in the LC-circuit by applying a magnetic field for a certain time. Once the magnetic field is removed, the charged capacitor will discharge, generating a magnetic field in the coil. This magnetic field can be sensed by the coil under the playfield. When the magnetic field collapses, part of the energy goes back into the capacitor, which will then discharge again, etc..

* http://en.wikipedia.org/wiki/Tuned_circuit
* http://www.phys.unsw.edu.au/~jw/LCresonance.html
* http://www.crystalradio.net/cal/indcal.shtml
* http://www.crystal-radio.eu/enlckring.htm
* http://www.captain.at/electronics/coils/

SegaNaomiPimping

2011-10-01T23:25:35Z

10.42.42.9: Created page with " Since i bought a incredible Sega Naomi Universal cabinet, the idea is to do a lot of things with it! Create controlboards, build in multiple hardware, pc etc."

Since i bought a incredible Sega Naomi Universal cabinet, the idea is to do a lot of things with it! Create controlboards, build in multiple hardware, pc etc.

SecurityAwarenessAdventureGame

2011-10-01T23:25:33Z

10.42.42.9: Created page with " To make people more aware of the security and privacy implications of new technology, an adventure game is a really cool method. People can experiment freely and explore the co..."

To make people more aware of the security and privacy implications of new technology, an adventure game is a really cool method. People can experiment freely and explore the consequences of their actions and non-actions. This will stimulate them to think about these subjects a little bit more. Think monkey island, think RPG, think Kings Quest.

ScrapMame

2011-10-01T23:25:32Z

10.42.42.9: Created page with " Scrapmame is a project to build a mame cabinet from old scrap-wood. Details on [httphttp://blog.maniac.nl/tag/scrapmame/ fooblog]. Source Code Repository: http://code.sig-io.n..."

Scrapmame is a project to build a mame cabinet from old scrap-wood. Details on [httphttp://blog.maniac.nl/tag/scrapmame/ fooblog].

Source Code Repository: http://code.sig-io.nl/sigio/revmame-hid-joystick/overview

SandB

2011-10-01T23:25:31Z

10.42.42.9: Created page with " -- Main.SandB - 25 Apr 2010"

-- Main.SandB - 25 Apr 2010

RickDeckardt

2011-10-01T23:25:29Z

10.42.42.9: Created page with " \o/ I HAS TOPIC -- Main.RickDeckardt - 27 Apr 2010"

\o/

I HAS TOPIC

-- Main.RickDeckardt - 27 Apr 2010

RfidDay

2011-10-01T23:25:28Z

10.42.42.9: Created page with " = RFID-day = For all those interested in RFID: I want to organize a one day workshop on the subject. Please state your interest in joining the workshop by ..."

= RFID-day =

For all those interested in RFID:

I want to organize a one day workshop on the subject.

Please state your interest in joining the workshop by adding your name to the list below.

These are the most commonly used RFID frequencies:
* 125 KHz (Low Frequency)
* 13.56 MHz (High Frequency)
* 860 - 950 MHz (Ultra High Frequency)
* 2.45GHz (Microwave).
My personal interest is in high frequency RFID. These high frequency cards consist mainly of piece of memory that can only be read when supplying the right cryptographic keys. Some cards even have a small CPU's on board. This is somewhat different then most of the low frequency RFID cards, that operate at 125 Khz, which often only produce a 'unique' bitstream.

== When: ==
Saturday the 20th of March 2010, 13:00 hours

== Where: ==

[HowToGetThere|Here]!

== What: ==
There will be workshops and lectures.
I'll give some basic 101 on RFID.
Roel can give some excellent insight into CRYPTO1 and it's weakness

We will have some fun with:
1 The !ProxMark3
1 !TouchaTag and !LibNFC
1 Custom build hardware
1 ...

== Who: ==
* Tomputer
* Roel V
* gmc
* turiphro
* Cinder
* praseodym
* aaaargh
* Patterns
* Eightdot
* Colin
* pa4wdh
* FooBar
* Gohla
* Carbon XIII
* Dekkers
* Blokje
* varna
* tg
* �

-- Main.TomPuter - 23 Feb 2010

RevelationScience

2011-10-01T23:25:25Z

10.42.42.9: Created page with " = Next event = * 4 October 2011 : 20:00 * [httphttp://envbiz.tau.ac.il/en/project_more.php?id=339&sub=45&cat=29 Dr. Vered Blass], Tel Aviv University, Israel * Title " El..."

= Next event =
* 4 October 2011 : 20:00
* [httphttp://envbiz.tau.ac.il/en/project_more.php?id=339&sub=45&cat=29 Dr. Vered Blass], Tel Aviv University, Israel
* Title " Electronic waste, what? where? who? "
* Background reading:
** [httphttp://www.grid.unep.ch/product/publication/download/ew_ewaste.en.pdf United Nations Environmental Programme report "E-waste, the hidden side of IT equipment's manufacturing and use" (4 pages)]

= What =
An evening, where an invited scientist/engineer talks about the latest/greatest/weirdest topic they work with. Goal is to present a topic or problem so that an an intelligent but lay audience can follow it. After a talk (say 45 mins to 1 hour) an hour long discussion Q&A session will take place, followed by an informal drinks and further discussion. The topics are not set or limited, as long it has a solid scientific base and can be related to things hackers / geeks care about.

= When =
Estimated frequency 12 or 6 times a year.

= For who =
For all RevSpace members plus any other guest that is interested in coming.

= By whom =
Gori will be contacting and inviting scientists from his own network + whoever else gets suggested. Please feel free to suggest a person to invite, or a topic to find a expert for below

= To Do =
* Propose session/setup to the MetaMeet
* Determine the first date
* Start looking for speakers
* Organize a recording setup, video & sound for youtube/web dissemination

= List of potential speakers / topics =
* 4 october - Vered Blass - Tel Aviv University, - E-waste, End of Life networks and you
* [httphttp://wiki.tudelft.nl/bin/view/Main/IgorNikolic Igor Nikolic] TPM/ TU Delft Complex Adaptive Systems theory and how to understand and model the co-evolution between social and technical systems.
* Rene Kleijn from CML Leiden about (rare earth) metal flows through the economy/ecology
* Chris Davis about wikis, open data, social processes and structuring complexity
* Mark de Bruijne TPM/TU Delft about robustness and resilience in infrastructure systems
* Frank Boons, EUR, social systems / industrial systems
* Quantum Computing - Floor Paauw for example
* Nanotechnology : possible contact via diggie
* < please add an idea! >