Skip to content
Snippets Groups Projects

Compare revisions

Changes are shown as if the source revision was being merged into the target revision. Learn more about comparing revisions.

Source

Select target project
No results found
Select Git revision
  • master
1 result

Target

Select target project
  • card10/logix
  • annejan/logix
  • kgz/logix
  • pink/logix
  • mot/logix
  • 9R/logix
  • melle/logix
  • jspricke/logix
  • sjn/logix
  • marble/logix
  • audionerd/logix
  • astro/logix
  • genotest/logix
  • _luc/logix
  • C-Tim/logix
  • Superwallah/logix
  • nitram/logix
  • Pixtxa/logix
  • royrobotiks/logix
  • deusfigendi/logix
  • arist/logix
  • LordBonzi/logix
  • Stormwind/logix
  • dag/logix
24 results
Select Git revision
  • master
  • prototype-distribution-formatting
2 results
Show changes
Commits on Source (584)
*.mp4 filter=lfs diff=lfs merge=lfs -text
stages:
- trigger
trigger build:
stage: trigger
image: python:alpine
variables:
GIT_CLONE_STRATEGY: none
TRIGGER_URL: https://git.flow3r.garden/api/v4/projects/2/trigger/pipeline
TRIGGER_REF: master
script:
- |
python <<EOF
from os import getenv
from urllib import request, parse
import json
url = getenv("TRIGGER_URL")
ref = getenv("TRIGGER_REF", "master")
token = getenv("TOKEN")
req = request.Request(url)
data = { "token": token, "ref": ref, "variables[TRIGGER]": "automatic" }
dataEncoded = parse.urlencode(data).encode()
req.data = dataEncoded
response = request.urlopen(req)
jsonMessage = response.read().decode()
message = json.loads(jsonMessage)
print(message.get("web_url"))
EOF
only:
- master
_index.md
\ No newline at end of file
---
title: logo placeholder
---
{{< rawhtml >}}
<a class="baselink" href="/">card10</a>
{{< /rawhtml >}}
--- ---
title: Home title: Home
--- ---
{{< figure src="/media/watchface.jpg" link="/media/watchface.jpg" title="The card10 with its default watch face" width="300px" class="floatright">}}
# card10 # card10
**card10** (From Ancient Greek καρδία (kardía, "heart")) is the name of the badge for the 2019 [Chaos Communication Camp](https://events.ccc.de/camp/2019/wiki/Main_Page).
It features an ECG sensor, Bluetooth Low Energy, an optical pulse sensor, a complete IMU with magnetometer and an environmental sensor.
# News
## Firmware Update: Queer Quinoa (as of 2021-12-25)
It is very easy to [update your card10 firmware](/firmware/firmwareupdate) with just a USB-C cable. The update instructions
also contain a list of the existing firmware releases.
## Virtual card10 Workout
We'll meet up again, still in virtual space, on 2021-09-19 at <https://meet.ffmuc.net/card10-workout>. Hope to see you there!
## card10 meetup at rc3
Day 4 (2020-12-30) 14:00 to 16:00 CET. muccc villag cellar. Jitsi: https://jitsi.rc3.world/card10-0b37c
## rC3 is coming!
What role(s) can play card10 in a distributed, remote conference? Brainstorming about connectivity, functionalities, interactions: [card10 at rC3](/events/card10_at_rc3)
### [Getting started](/tutorials/gettingstarted)
You just received your card10, what now? The [Getting started](/tutorials/gettingstarted) page has some advice how to assemble and use the card10.
### [First interhacktions](/interhacktions/firstinterhacktions)
After playing around with card10 a bit, you want to learn how to write your own software. Even if you have never programmed before, it is super easy to make some LEDs blink on card10 :)
### [tl;dr](/faq/tldr)
Spare me the details just give me the links to the docs!
### Community
You can reach us via our chat room (libera IRC and Matrix), Twitter, Mastodon and our GitLab instance.
Please check out the [community page](/community) on how to do that.
### [FAQ](/faq)
Welcome to card10 Wiki. You can browse this wiki source [here](https://git.card10.badge.events.ccc.de/card10/logix). ### Events
- Events [archive](/events).
## Announcements ### News Archive
### New GitLab Server 2019-06-04
We moved from our [Hamburg GitLab](https://gitlab.hamburg.ccc.de/card10/) to: ## Hello 36C3
> [`https://git.card10.badge.events.ccc.de`](https://git.card10.badge.events.ccc.de/explore/groups/) Our assembly is here: [c3nav](https://36c3.c3nav.de/l/card10/@0,491.08,374.33,5)
1. Please be aware this hosting is a work in progress. If you encounter any issues please let us know on Matrix or IRC (see below). Please stop by at any time :)
2. We are aware and working on GDPR compliance, for progress you can track this [issue](https://git.card10.badge.events.ccc.de/card10/meta/issues/1)
3. Social-Sign-On (Twitter, Github, ...) is coming soon
## Overview
> <img class="center" alt="Photo of the card10 badge" src="/media/frontpage-nice-image.jpg" width="420" height="auto" align="center"> We are working on a workshop schedule and post it on the [workshop page](/events/workshops/)
>
> Hello, my name is card10
## Camp was wonderful, see you at 36C3
if you still have a voucher (white or blue), bring it to congress and you might be able to redeem it against one of the card10s we are reparing in the meantime.
- Community No sale of card10s!
- at [Matrix](https://en.wikipedia.org/wiki/Matrix_(protocol)): [`#card10badge:asra.gr`](https://matrix.to/#/#card10badge:asra.gr)
- or [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) (mirror): [`freenode.com#card10badge`](ircs://chat.freenode.net:6697/card10badge)
- or [GitLab: `https://git.card10.badge.events.ccc.de`](https://git.card10.badge.events.ccc.de/explore/groups/)
- Social Media
- [`@card10badge@chaos.social`](https://chaos.social/@card10badge)
- [`twitter.com/card10badge`](https://twitter.com/card10badge)
- [FAQ](/en/faq)
- Events
- Upcoming:
- Card10 meetup in Berlin: xHain 14.06. 19:00
- Previous
- CCCamp 2019 Badge at #eh19 (easterhegg2019): [Description](https://conference.c3w.at/eh19/talk/DA7KTT/), [Recording](https://media.ccc.de/search/?q=CCCamp+Badge+Talk)
- CCCamp2019 Badge Workshop at #eh19: [Description](https://conference.c3w.at/eh19/talk/VHFMJ7/), 2019-04-21, 14:30–15:30
- Card10 at the [GPN19](https://entropia.de/GPN19:There_will_have_been_a_camp_badge:_We%27re_reconstructing_future_technology_and_you_can_help_us_with_this_mission)
- [Prototypes and prototype ambassadors](/en/prototype_distribution)
## Components ## Got a card10 you don't use or need one for your next project?
The card10 exchange point is [here](/other/card10exchange)
**!Caution!** Card10 is still in the prototyping phase, bear in mind that hardware and PCB layout changes may still occur.
- [Hardware](http://gitlab.hamburg.ccc.de/card10/hardware)
- [LogBook](/en/logbook)
- [Interhacktions](/en/interhacktions)
- [Fundamental board](/en/fundamental-board-overview)
- [usb-c](/en/usbc)
---
title: Companion App
---
{{< rawhtml >}}
<div class="p-notification--caution">
<p class="p-notification__response">
<span class="p-notification__status">Warning:</span>
We are still in developing the Companion App for iOS and Android
</p>
</div>
{{< /rawhtml >}}
## We need really help, please follow us [here](developing)
## Android / F-Droid releases
You can find the latest release of the Companion App in the F-Droid repository:
[Companion App for the card10 Chaos Communication Camp badge](https://f-droid.org/app/de.ccc.events.badge.card10)
## iOS Testflight builds
**[https://testflight.apple.com/join/oqZhY70M](https://testflight.apple.com/join/oqZhY70M)**
⚠️ Please note ⚠️ We've got a lot of trouble pairing with the card10. If your want to connect to the card10, follow the instructions on the [development page](developing).
[![https://testflight.apple.com/join/oqZhY70M](http://api.qrserver.com/v1/create-qr-code/?color=000000&bgcolor=FFFFFF&data=https%3A%2F%2Ftestflight.apple.com%2Fjoin%2FoqZhY70M&qzone=1&margin=0&size=400x400&ecc=L)](https://testflight.apple.com/join/oqZhY70M)
File added
---
title: Developing
---
You can find the repositories for the apps here:
* [git.card10.badge.events.ccc.de/card10/companion-app-android](https://git.card10.badge.events.ccc.de/card10/companion-app-android/)
* [git.card10.badge.events.ccc.de/card10/companion-app-ios](https://git.card10.badge.events.ccc.de/card10/companion-app-ios/)
Please join the channel [`#freenode_#card10companion:matrix.org`](https://riot.im/app/#/room/#freenode_#card10companion:matrix.org)
### Android / F-Droid nightly
The GitLab delivere a (unsafe) Android Debug Build of Companion App by a F-Droid repository.
If you are able to create debug logs and create Issues feel free to subscribe this repository.
[![https://git.card10.badge.events.ccc.de/card10/companion-app-android-nightly/raw/master/fdroid/repo](https://git.card10.badge.events.ccc.de/card10/companion-app-android-nightly/raw/master/icon.png)](https://git.card10.badge.events.ccc.de/card10/companion-app-android-nightly/raw/master/fdroid/repo)
### iOS Testflight builds
**[https://testflight.apple.com/join/oqZhY70M](https://testflight.apple.com/join/oqZhY70M)**
⚠️ Please note ⚠️ We've got a lot of trouble pairing with the card10. If your want to connect to the card10:
* checkout the [ios-workarounds branch](https://git.card10.badge.events.ccc.de/card10/firmware/commits/plaetzchen/ios-workaround) of the firmware repository
* rebase the branch on the current firmware master
* build a firmware image
* flash that image on the card10
* The ios-workarounds branch basically exposes all characteristics publicly, so everybody can connect to your card10 and read / write characteristic, so this is clearly only a development helper and not ment for day-to-day usage
**OR**
* Use [this file](https://git.card10.badge.events.ccc.de/card10/logix/blob/master/app/card10-ios-branch.bin) and transfer it as *card10.bin* over USB to your card10
[![https://testflight.apple.com/join/oqZhY70M](http://api.qrserver.com/v1/create-qr-code/?color=000000&bgcolor=FFFFFF&data=https%3A%2F%2Ftestflight.apple.com%2Fjoin%2FoqZhY70M&qzone=1&margin=0&size=400x400&ecc=L)](https://testflight.apple.com/join/oqZhY70M)
---
title: Community
weight: 10
---
Please get in touch with us. We are always happy to help out and get your card10 in shape!
## Chat
- [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat): [`libera.chat#card10badge`](https://web.libera.chat/#card10badge)
- mirrored to [Matrix](https://en.wikipedia.org/wiki/Matrix_(protocol)) (mirror): [`#card10badge:libera.chat`](https://matrix.to/#/#card10badge:libra.chat)
- If you can please join via IRC directly. Bridging IRC channels to Matrix is unreliable at best.
## Social Media
- [`@card10badge@chaos.social`](https://chaos.social/@card10badge)
- [`twitter.com/card10badge`](https://twitter.com/card10badge)
## Bug reports and development
- [GitLab: `https://git.card10.badge.events.ccc.de`](https://git.card10.badge.events.ccc.de/explore/groups/)
You can [browse](https://git.card10.badge.events.ccc.de/card10/logix) this wiki's source and [read more](/firmware/gitlab) about our GitLab instance.
---
title: Events
---
# Events
## Upcoming Events
30.05. - 02.06. - GPN Karlsruhe (Workshop tbd)
## Past Events
19.04. - 22.04. - Easterhegg Vienna
---
title: FAQ
---
## What can I contribute?
Generally, there is a wide range of contributions that can be made to the firmware, the IOs and Android apps, the various methods of BLE communication, the user interface, the documentation, by reviewing existing work, and of course by creating your own [interhacktions](/en/interhacktions)!
If you don't know where to get started you can also have a look at some of the ideas for contributions we outlined [here](https://gitlab.hamburg.ccc.de/card10/logix/issues). If you have questions on the issue, please don't hesitate to comment or get in touch to the creator of the issue through [Matrix Chat or IRC](/).
## I can't fork any of the repositories!?
Sadly with the current gitlab setup this key feature is not available. We are setting up a new server to solve this problem. In the meantime, you can get in touch via [Matrix Chat or IRC](/).
## How does the so-called wiki work?
Not as well as it should ;) To keep things easier to maintain (the r0ket wiki has been going for 8 years now!), we decided on a git/markdown based wiki for this year. Whilst we are still setting up a gitlab with easy editing access, in the meantime please create a user account for gitlab.hamburg.ccc.de, and contact lilafisch on [Matrix Chat or IRC](/) to get write access to the wiki repo.
Currently, it is easiest to edit the 'wiki' by cloning the git repo, and editing the markdown files. If you are using figures, please place them in media folder. The [fundamental board](/en/fundamental-board-overview) page is an example including image links and page links.
## What components are on card10?
Have a look at the pdf export of the [schematics for the prototype](https://gitlab.hamburg.ccc.de/card10/hardware/blob/master/badge/Badge_Bottom-PCB/Printing_Drucke_Schaltplan__1_.pdf) (note: no promises that this is final!).
## Is there a recommended dev board?
Since the BLE chip is very new, none of the card10 researches and travelers have found a suitable dev boards to recommend. We will try to share the research prototypes as widely as possible through hackerspaces. If you want to get your hands on a card10 prototype (we expect to start circulating them mid-May), first see if a hackerspace near you already has a card10logy department. If this is not the case, please get in touch via [Matrix Chat or IRC](/) to suggest opening a new card10logy department.
## How can I get a prototype?
You can find out if there's an ambassador in your city or a city near you. If there isn't maybe you want to become an ambassador yourself and help with the card10logix community.
More detailed info you can find [here](/en/prototype_distribution)
## What should I bring to cccamp 2019 so I can enjoy card10?
*I have noticed that the card10 needs some maintenance; most people carrying a card10 have brought their own tools for maintaining their card10, making it more individual, or adding functionality. In some places, maintenance stations are available, where card10's can be recharged, and tools and knowledge is shared*
According to current research, it is recommended to carry the following:
* A USB-C cable for charging and programming
* A screwdriver for assembling card10 (more details following soon)
* A needle for sewing to the card10 wristband
* A device capable of communicating via [Bluetooth Low Energy](/en/ble) (BLE)
---
title: Fundamental board overview
---
The fundamental board is located just above the wristband; above it come the battery, the harmonic board, and the display. The harmonic board is connected to the fundamental board via the TOP board connector.
Several interfaces for [interhacktions](/en/interhacktions) are included on the fundamental board. The travelers can be alerted to an event using the vibration motor. Screws through the EKG contacts are used both for attaching the wristband and for making contact with your skin for EKG measurements. Besides its use for interhacktions, the [usbC](/en/usbc) connector is also used for charging the battery and for updating the firmware.
A pdf version of the prototype fundamental board is available [here](https://gitlab.hamburg.ccc.de/card10/hardware/blob/master/badge/Badge_Bottom-PCB/Printing_Drucke_Schaltplan__1_.pdf)
![landmarks](/media/landmarks.png)
---
title: Distribution of prototypes
---
# Distribution of prototypes
**Hello fellow researcher,**
so you want to become part of the card10 research team and help us find out how it will have improved everyone's experience at Chaos Communication Camp 2019?
Here's what you have to know:
* we have around 20 prototypes which we are trying to share with as many interested card10logists as possible. and there are many people interested in working with it.
* there's documentation in our [wiki](https://gitlab.hamburg.ccc.de/card10/logix/)
* we're trying to find out how the badge will have interacted (?) with used BLE to interface with other installations at camp the camp surroundings
* cities with hackspaces can get a prototype if there's a volunteer for being an ambassador who takes care of the prototype (trying to avoid too much idle time)
### Here's what you can do:
* think about how you want to contribute/what you want to do with the prototype
* join our [Matrix](https://en.wikipedia.org/wiki/Matrix_(protocol)):( [`#card10badge:asra.gr`](https://matrix.to/#/#card10badge:asra.gr))/[IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) ( [`freenode.com#card10badge`](ircs://chat.freenode.net:6697/card10badge))
channel and tell us what you want to do
* talk to your city's ambassador
* become an ambassador yourself
* we'll try to find a timeslot for you to work with the prototype
* we send it to you and after the time we agreed upon you send it back to us/the next person
### How to be a great card10logy department ambassador:
* get more people involved to help with 'ambassadoring' ;P
* invite others to chat about the card10
* organise meetups to play with card10
* invite related groups (wagenburg, fab labs, ...)
* contact and encourage people who might have great ideas but are not aware of the project/too shy to ask
* share your research in the card10logix wiki, matrix/irc and @card10badge
## Cities that already have ambassadors
* Berlin: 2 prototypes, bi-weekly meeting at the [xHain](https://x-hain.de); ambassador: miriamino contact via matrix/irc chat)
* Munich
* Bremen: location: ccchb; ambassador: lilafisch (contact via card10 matrix/irc chat, in [ccchb irc](http://ccchb.de/wiki/Chat))
* Amsterdam / Den Haag: location: [badge.team](https://badge.team/); ambassador: the_JinX (contact via card10 matrix/irc chat)
\ No newline at end of file
---
title: USB-C
---
# General use
You will need a USB-C cable to charge your badge. You can also update the firmware, mount it as a storage device to read files and flash software. We plan to provide most of these functions via ble as well, but a wired connection might still come handy.
The general USB-C use will work whichever way round the USB-C cable is plugged in.
# Full I/O
Traveler reports agree that the badge uses USB-C, the assumption is that this was chosen over USB-micro for the available range of extra pins. The reconstruction thus has some extra pins available, which would explain several observations of hardware interHacktions using USB-C.
**!Caution!** Most USB-C cables available for sale do not connect all pins of the connector. Whilst this is not a problem for general use, if you want to access the full available I/O contacts, it might be best to choose a cable from the suggestions listed at the bottom of the page.
**!Caution!** Card10 is still in the prototyping phase, bear in mind that hardware changes may still occur.
To use full I/O, there is a 'correct side up' for the USB-C cable. If the cable is plugged in the wrong way round, serial RX and TX are shorted together. So if you find yourself unsure, try sending some characters via serial console and see if you get them returned immediately; in that case the 'wrong' side is up.
## I2C
I2C ("i-squared-c" or "i-two-c") is a two wire protocol used for communication between
## UART
## EKG
## 'confirmed' full pin cable options
Whilst this list does not guarantee you anything, these cables have been bought before and were found to have all contacts connected:
* TODO
---
title: Events
weight: 50
---
<!-- Please keep ongoing and current events in sync with _index.md -->
- Upcoming:
- virtual card10 workout: 2021-09-19 at https://meet.ffmuc.net/card10-workout
<!-- past events, please remove any events you move here from _index.md to keep the home page clean -->
- Previous
- DiVOC R2R: 2021-04-04 Bluetooth LE in MicroPython (auf der card10 badge) https://meet.ffmuc.net/card10-mp-ble
- card10 [workout in Berlin](/events/workouts/berlin-2019-11-09): xHain, Sat-Sun, November 9th to 10th, 2019
- **card10 reworking/soldering/firmware/etc.**: card10 village (R8); for firmware work, please bring your laptop with a clone of the firmware git and the [toolchain](https://firmware.card10.badge.events.ccc.de/how-to-build.html)
- card10 Soldering Session in Berlin: xHain Wed-Thurs 14&15. August starting at 10 am
- card10 Soldering Session in Berlin: xHain Sat-Sun 10.-11. August starting at 10 am
- card10 meetup in Berlin: xHain 06.08. ~~19:00~~ => 20:00
- card10 meetup in Berlin: xHain 05.06. 20:00
- card10 meetup in Berlin: afra 21.06. 19:00
- card10 meetup in Berlin: xHain 14.06. 19:00
- card10 at the [GPN19](https://entropia.de/GPN19:There_will_have_been_a_camp_badge:_We%27re_reconstructing_future_technology_and_you_can_help_us_with_this_mission)
- CCCamp2019 Badge Workshop at #eh19: [Description](https://conference.c3w.at/eh19/talk/VHFMJ7/), 2019-04-21, 14:30–15:30
- CCCamp 2019 Badge at #eh19 (easterhegg2019): [Description](https://conference.c3w.at/eh19/talk/DA7KTT/), [Recording](https://media.ccc.de/search/?q=CCCamp+Badge+Talk)
- **card10 [talk](https://fahrplan.events.ccc.de/camp/2019/Fahrplan/events/10365.html)**: Curie Wed 21.08. 12:00
- **card10 firmware workshop**: card10 village (R8), Sun 18.08. 16:00
- card10 [workout in Berlin](/events/workouts/berlin-2019-10-03): xHain, Thurs-Sun, October 3rd to 6th, 2019
---
title: Awards
---
Idea: From time to time hold small award ceremonies to keep people motivated to contribute
to the card10 project
## 36C3
We will host a small awards ceremony at 36C3.
### Categories
- Best documented project
- Best use of a sensor (ECG, Accelerometer, etc...)
- Best LED application (e.g. POV)
- Best accessibility contribution
- Best interaction with 36C3
### Submitting a contribution
You submit a contribution (be it an app, project, documentation, etc..) by entering it in the list of contributions at the end of this section.
You can also reach out to us via twitter, mastodon, matrix and IRC. We will add your contribution for you if needed.
### Date and Time
Unless otherwise noted the ceremony will take place Day 3, 20:00 at the card10 assembly.
Entries have to be made until Day 3, 18:00.
### Judging
Judging will be done by original contributors to the card10 project. For the accessibility category we will approach relevant teams at 36C3.
### Prizes
We are still collecting, but at least there will be a few r0kets and rad1os available.
### Contributions
- Pixtxa
- [36C3 Clock](https://badge.team/projects/36c3_clock)
- [Cyberband](https://badge.team/projects/cyberband)
- [Monster++](https://badge.team/projects/monster)
- [Timer](https://badge.team/projects/timer)
- Royrobotiks
- [Control Center](https://badge.team/projects/control_center)
- [Tiny Typer](https://badge.team/projects/tiny_typer)
- [Magnetometer](https://badge.team/projects/magnetometer)
- [Micromarble](https://badge.team/projects/micromarble)
- Your contribution
---
title: card10 at rC3
---
## Brainstorming
Instead of the regular 37C3, we will have the first ever remote congress end of this year, which is dubbed "rC3"
How can card10 interact with a remote and distributed chaos event?
How can card10 connect to other card10s anywhere on the globe?
What services could it provide, what services could it make use of?
### PTT or mute/unmute input device
Connect to the local PC via bluetooth LE, display via RGB LEDs the (un)mute and (un)deafen status of
- the OS communications device
- the application that uses the communications device
- there might be multiple and changing applications, especially for speakers, heralds, VOC and other angels (e.g. mumble, BBB, OBS, discord, teamspeak etc...)
- different OS's will handle audio differently. Audio routing is a pain. Reliable indication of the current state would improve the situation a lot
### virtual applause
- detect if the wearer is clapping their hands via one of the accelerometers
- push this info to a central server
- somehow show in an overlay in the live stream or via an indicator next to the streaming window how many card10 wearers are clapping in real time
### Tools for speakers, heralds, VOC angels
Timing and handing over who is speaking is challenging to coordinate due to the latency of video conference tools. can card10 help here by e.g.
Notifications who is
- ready to talk
- waiting to talk
- wanting to ask a question from the audience and waiting for the speaker to finish their sentence
- having a problem and needs help from the team
- presentation timer
Providing real time feedback from the audience to the speaker
- showing on the LED bargraph how many people are applauding virtually (see above)
- pulsing the vibration alarm with increasing intensity the more people are clapping
Pushing info about the current state, like the typical online status or the state app at camp (yes, that is potentially sensitive information that the wearer should be able to have control over who is allowed to see it, like with basically any messenging app)
- online and available
- online but afk (taking a break, eating,...)
- not online (connection problems, blackout, sleeping,...)
### Pager
display short texts on the LCD that can be sent via
- the compantion app
- via the POC? Possible to subscribe the compantion app to the EVPN, registering an extension that can receive text messages or can be paged?
- IRC, matrix, twitter, rocket chat, whatever
- display the sender and if they want to be called via DECT/SIP asap/soonish/when convenient/...
### Fahrplan interaction
#### Show on the display which segments are up next
probably best if requested by presisng a button pull the info required via an API from the fahrplan app that needs to be installed on the same phone as the card10 companion app
#### Notification when a favourite segment is about to start
The fahrplan app allows flagging talks as favourites.
Pull those flags and notify the wearer by a configurable alarm (e.g. pulse the vibration alarm, flash LEDs, show the name of the upcoming talk on the display for a few seconds or until the alarm is dismissed by pressing a button)
#### Notification for self organized sessions
same for the database that contains the SOS's (afaik that calendar has been in the congress wiki until now)
---
title: card10 rC3 Assembly
---
We will have an assembly in the cellar of the muccc at rC3:
## Location and Time
- Location: [rc3 cellar](https://test.visit.at.wa-test.rc3.cccv.de/_/global/raw.githubusercontent.com/muccc/rc3test/master/main.json) Attention: Link subject to change
- Times: Day 1 - Day 4
- Capacity: virtual
Meetup: Day 4 (2020-12-30) 14:00 to 16:00 CET