For the spring course, we provide a separate wireless network (IP range: 172.30.0.0/20) called "RoboLab Playground" with the following password:
someobviouspass2025
The Bricks auto-connect to this network, but your own device must always be connected in order to connect via SSH.
Please note, that you cannot reach any device inside the RoboLab Playground Wi-Fi from the outside, e.g. eduroam or VPN.
In most modern terminals, the character '~' (tilde) is replaced with the absolut path to your home directory.
This feature ist called Tilde Expansion and works in powershell (Windows), zsh (macOS) and bash (Linux).
Instead of the tilde, you can always type the absolut path to your home directory, which is:
C:\Users\<user> # Windows
/Users/<user> # macOS
/home/<user> # Linux
You can always switch to your home directory by simply running
cdwithout an argument.
Windows Search > "environment" > Open "Edit environment variables for your account" > New
echo '<NAME>=<DATA>' >> .zshrc # zsh (macOS, Arch)
echo '<NAME>=<DATA>' >> .bashrc # bash (default on most Linux distros)
set -Ux <NAME> <DATA> # fish
Restart your Terminal (or your whole IDE if you use an integrated terminal) afterwards!
View your current PATH:
echo $env:PATH # Windows - Powershell
echo $PATH # macOS, Linux
Windows Search > "environment" > Open "Edit environment variables for your account" > "Path" > Edit > New
echo 'PATH="$PATH:<NEW ENTRY>"' >> .zshrc # zsh (macOS, Arch)
echo 'PATH="$PATH:<NEW ENTRY>"' >> .bashrc # bash (default on most Linux distros)
set -Ux PATH <NEW ENTRY> $PATH # fish
Restart your Terminal (or your whole IDE if you use an integrated terminal) afterwards!
~/.cargo/bin is in your PATH (> FAQ)Check if the Environment Variable CARGO_TARGET_DIR is set:
echo $env:CARGO_TARGET_DIR # Windows (Powershell)
echo $CARGO_TARGET_DIR # macOS, Linux
If yes, find the place where it is set and remove it.
First, make sure you try to add your private key (no ending) instead of your public key (.pub).
If the issue persists, adjust the permissions for the keyfile of your private key:
chmod 700 <path-to-keyfile>
On Windows, right-click keyfile > Properties > Security > Edit > Remove everyone except your own user and make sure inheritence is disabled
Disable Microsoft Defender's new AI-based Virus detection:
Windows-Security > App & browser Control > Smart App Control settings > Off
Windows-Sicherheit > App- und Browsersteuerung > Einstellungen für Smart App Control > Deaktiviert
Check if the path of your current folder includes a whitespace, e.g. C:\Users\User\Uni\1. Semester.
If yes, move the project to a location without a whitespace.
Check if your user folder includes a whitespace, e.g. C:\Users\First Last\.
If yes, please create a new Windows User without a whitespace and use this for the robolab, or install and use the WSL
Try in the following order with re-opening your terminal after each command:
%USERPOFILE%\AppData\Local\Microsoft\WindowsApps is in your PATH (> FAQ)C:\Users\<Name>\AppData\Local\Microsoft\WinGet\Links is in your PATH (> FAQ)Try the commands from this StackOverflow Thread:
Register-PSRepository -Default
Get-PSRepository
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
[Net.ServicePointManager]::ServerCertificateValidationCallback = {$true};
Install-Module PowerShellGet -Force
Open the Microsoft Store and search for Updates.
Open the Registry editor, navigate to HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and delete the entry of the broken package.
wsl --updateapt updateping 9.9.9.9, if not:
ping dns9.quad9.net, if not:echo "[network]\ngenerateResolvConf = false" | sudo tee /etc/wsl.conf
echo "nameserver 9.9.9.9" | sudo tee /etc/resolv.conf
If this comes up when cross-compiling and you are sure you installed your target with rustup target add <target>, check if your cargo comes from homebrew:
which cargo
> /opt/homebrew/bin/cargo
If yes, you previously installed your rust-toolchain via homebrew. While this works fine for your host target (compiling for your own machine), brew doesn't ship cross-compilation-targets.
As toolchains installed via brew and rustup are independent from each other, we need to use the cargo from your rustup toolchain to use the previously installed cross-compilation-target.
The easiest way is to uninstall homebrew's rust and re-create the command-symlinks to rustup:
brew uninstall rust && rustup-init
which cargo
> /Users/<user>/.cargo/bin/cargo
Alternatively, follow the advice given in brew info rust and brew info rustup.
TODO Artur
https://docs.brew.sh/Support-Tiers -> Future macOS Support
https://ports.macports.org/port/zig
https://ports.macports.org/port/just
This error could occure if you installed VSCode/VSCodium with flatpak/snap, as it is sandboxed and can't access your Config.toml.
Please uninstall your flatpak version and install the .deb version or any other native version using your corresponding package manager.