Work with the real system.
Wire the hardware, write the code, and make something respond.
About C Labs
Engineering makes more sense when you can touch it.
C Labs makes the systems behind modern technology visible, practical, and understandable.
Why C Labs exists
Start with the thing.
A lot of engineering education starts with the explanation. C Labs starts with the thing itself.
Read the sensor. Move it. Watch the numbers change. Build something with them. Find out where it breaks. Then understand why.
The aim is not simply to know what an accelerometer, PID controller, or ultrasonic sensor does. It is to have built with one and seen the engineering for yourself.
Make the invisible visible.
Turn measurements and behaviour into something you can observe.
Figure out why it behaves that way.
Use the theory to explain what you have already seen for yourself.
Behind C Labs
Hi, I’m Fred.
I’m a software developer and engineering student based in Heilbronn, Germany.
C Labs grew out of the projects I was already building and trying to understand myself: sensors, embedded systems, control, electronics, and robotics.
I started documenting those projects online. That eventually turned into teaching them in person too.
The first C Labs-style workshop took an IMU orientation tracker and turned it into something other people could build and understand for themselves. C Labs is my attempt to do much more of that.
- 42 Heilbronn
- Software development
- C Labs
- Engineering education
- Hands-on
- Sensing · control · robotics
The principle
You shouldn’t have to wait until you’re an expert to start building things.
C Labs is built around curiosity first. Start with a question, get your hands on the system, make mistakes, see what happens, and use the theory when you need it.
The goal isn’t to make engineering look easy. It is to make complicated things approachable enough that you can start figuring them out yourself.
Ready to build something?