Whether you're stuck on a motor driver wiring issue or need advice on local part sourcing, here's how to reach the right people and how fast you can expect a reply.
Prefer to browse first?
Many common build problems already have detailed threads. Check the community FAQ before you post.
Visit the FAQ sectionPost your question in the relevant project category — motor drivers, chassis, code, or battery management. Other builders usually jump in within a few hours.
For account issues, reporting a problematic post, or if you need help finding a specific local supplier. We keep an eye on the inbox during the week.
Every Saturday morning we run a text-based troubleshooting session. Bring your wiring diagrams and code snippets — it's the fastest way to get unstuck.
If you're in the middle of a build and need a quick answer about a component or a safety concern, you can call us during working hours.
Our response promise
We aim to acknowledge every forum post within 6 hours during the day. Email replies go out within 24 hours on business days. Live chat is the quickest route if you're actively building.
Whether you are stuck on a motor driver issue, want to share a build log, or are looking for advice on sourcing parts locally, the forum is the place to reach us. Use the details below to contact the community directly.
Prefer a direct message over a forum thread? These are the channels we check most often.
The forum is open around the clock, but you will get the fastest replies from the community during these times.
For build-specific questions, post directly in the relevant project category. For anything else, email works best and we usually reply within a day.
Straight answers about getting started, choosing parts, and making your build work in local conditions.
Start with a simple two-wheel line follower using an Arduino Nano and an L298N motor driver. It teaches you the core loop: reading sensors, making decisions, and driving motors. You can finish it in a weekend, and it gives you a solid base to add more complex features later.
For most hobby projects with small DC motors, the DRV8833 is a great choice because it's compact and efficient. The L298N is older and runs hot, but it's still fine for learning. If you're using stepper motors, look for a dedicated driver like the A4988. Match the driver to your motor's voltage and current, not the other way around.
For quick orders, local shops like Netram and Mantech are reliable for common modules. For more specialised parts, many of us order from overseas, but you have to factor in import duties and shipping time. Check the community forum for recent experiences with specific suppliers - it changes often.
First, check your wheel type. Soft silicone wheels grip better than hard plastic on smooth floors. Also, make sure your chassis isn't too heavy for the motors you're using. Adding a bit of weight over the drive wheels can help, but you need to balance it. Sometimes it's just a matter of adjusting the motor speed in your code.
PLA is the easiest to print, but it softens in a hot car or direct sunlight. For parts that sit near motors or outside, consider PETG or ASA. Also, design with thicker walls and avoid large flat surfaces that can curl. In our climate, it's often better to print in the evening or in a cooler room.
Work through it step by step. First, check your power supply - a low battery can cause weird behaviour. Then, test each motor separately with a simple sketch. Use the serial monitor to print sensor values and see if they're reading correctly. Isolate the problem to either the electronics, the code, or the mechanics before you change anything.