Project Prototyping Lessons from Max Imagination

Project prototyping sounds like the sensible thing everyone claims to do, right up until a drone arm snaps, a robot leg refuses to behave, or a 3D-printed submarine starts teaching you about water pressure the hard way. In this short clip, Max Imagination uses his own drones, ESP32-based underwater vehicle, and unfinished walking robot to show why testing small pieces first is not optional fiddling. Readers who saw his earlier Elektor discussion on drones, DIY, and 3D printing will recognize the theme: Clever projects survive because their weakest assumptions are tested early.

Material Choices That Survive Real Projects

Max starts with a familiar maker lesson: PLA is easy, neat, and convenient, but that does not make it the right material for every job. For drone arms and outdoor mechanical parts, he found PETG more forgiving because it can flex under impact while still offering useful rigidity. That kind of practical observation lines up with the broader lesson from filament material guides: As max says below, there is no magic “best” plastic, only a better match between the material and the job.

For impact-prone parts, a little toughness can matter more than simple stiffness. PLA may print beautifully, but a crash or sharp load can expose its brittleness. PETG gives the part more give. Carbon-fiber-reinforced nylon, which Max mentions as a possible upgrade, can bring higher stiffness and strength, although it also brings more demanding printing requirements. The point is not to worship exotic filament. It is to prototype with the failure mode in mind.

Project Prototyping Underwater

The strongest example in the clip is Max’s ESP32-based RC submarine. The finished ESP-DIVE project combines a waterproof body, camera, propulsion, buoyancy control, wiring seals, and a floating antenna buoy. That is a lot of ways to fail before the electronics even get a fair chance.

Max explains that his earlier choice of PLA forced him to compensate by coating water-exposed parts with superglue. In hindsight, he says PETG would have been a better material for water resistance. He also points to smaller details that are easy to underestimate, such as adding dielectric grease to O-rings and sealing wire and tube pass-throughs properly. Anyone who has watched a project die from one lazy gasket will feel that one in the wallet.

The more useful lesson is how he broke the system apart. Before building the full submarine, he tested the pipe and end caps for leaks. Then he tested the RF link and the antenna buoy. Then he tested the syringe-plunger buoyancy mechanism separately. Only after those individual functions made sense did the whole machine deserve to become one project.

A Failed Robot Still Teaches Something

Max also shows Hexoscout, a six-legged walking robot that never reached the same level of success. His diagnosis is blunt: he rushed into mechanisms before making a proper prototype. Instead of using specialized servos with position encoders, he used brushed motors and custom position feedback. That may sound resourceful, but in a legged robot, position control is not a decorative feature. It is the difference between a walking mechanism and a table ornament with ambitions.

This is where project prototyping becomes research, not just assembly. Testing one subsystem at a time tells you whether a component choice is merely possible, or actually sensible. It also prevents the classic maker trap: building a beautiful full-scale machine around one untested assumption. Once the full system is assembled, every fault becomes harder to isolate.

Max’s advice is simple enough to sound obvious, but it is worth repeating because most of us ignore it when the idea is exciting: break the project down first. Test the material. Test the seal. Test the RF link. Test the actuator. Then build the thing. A prototype is not a delay before success; it is often the cheapest way to find out what success would even require.