Jump To: FAQs
Welcome Whitebox Owners,
Happy to have you here, and without further ado, let’s get started! Below you’ll find two User Guides that will take you through the process of getting your Whitebox up and running:
- Whitebox User’s Guide – This User Guide will give you step by step instructions on how to safely get your WB operational.
- Whitebox Developer’s Guide – This Developer Guide goes into more depth because it is for those who want to experiment.
- Whitebox Code
- Whitebox Tutorial Video – If you need a little extra assistance, Kyle will walk you through the needed steps to get your Whitebox operational.
And remember, SAFETY FIRST! This is a new technology that’s still in early development. Of course we want you to thoroughly enjoy your prototype Whitebox, however, please be respectful in this stage of early development.
Frequently Asked Questions | Whitebox
The maximum rated weight of the Whitebox is 2.5lbs (1.1kg). When 2.5lbs is on the Whitebox, it will only last around 2 minutes before the fuse blows. See “Runtime vs Payload” under the “Whitebox Operation” section to better understand loading the Whitebox.
The maximum runtime of the Whitebox is 5 minutes due to the timer that comes programmed on the device. This runtime can decrease drastically depending on the payload on the Whitebox.
The simplest solution we have found is using a loop of tape that is attached to the inside of the lid.
Yes. Since the Whitebox is an experimental device, it is not optimized for perfect stability. Since the Whitebox hovers, any mass imbalance or speed differential of the individual Hover Engines can cause the Whitebox to spin. If your Whitebox is spinning really quickly (i.e. 360 degrees in less than 1 second) then one of your Hover Engines is probably wired incorrectly. See “ESC Wiring” under the “Troubleshooting” section of the User Guide.
The battery that comes with the Whitebox should have a piece of Velcro that matches the Velcro on the inside of the lid. After securing the battery to the lid, you need it connect it to the ESC in the Whitebox. Make sure that it is not making contact with any of the internal components or having its wires pinched by the lid.
The fuse is there to protect the battery. The Whitebox comes with a LiPo battery which can catch fire if it overheats or over-discharges.
The Hover Engines create a primary magnetic field, which induce eddy currents in the hover surface. By Lenz’s Law, these eddy currents create a secondary magnetic field that repels the first and creates lift. The eddy currents can also create a lot of heat, especially when the Whitebox is hovering in the same position for a long time. For this reason, we recommend continuously moving the Whitebox.
Increasing the distance between the Hover Engines and the thing its stuck to will drastically decrease the force required to remove the Whitebox. Tools such as shims are useful for aiding separation. When trying to remove the Whitebox, sliding instead of pulling should also help dramatically. Once the Whitebox is removed, check the bottom for damage. If you see cracked or bulging Hover Engine bottoms, DO NOT operate your Whitebox until they are repaired.
Although the top seems like it can be put on any direction, the magnets are paired such that only one orientation is correct. Use the match arrows on the inside of the lid and the inside of the Whitebox to ensure proper alignment.
The slot in the front of the Whitebox allows access to the Teensy LC Microcontroller. This is only meant for those that are following the Whitebox Developer’s Guide.
Hovering off the ground can require a lot of power depending on various parameters (hover surface conductivity, payload, Hover Engine efficiency just to name a few). The battery can get warm (120°F or 50°C) under normal operation. The purpose of the timer and fuse should prevent the battery from getting dangerously hot.
The green square is called magnetic viewing film, which is a powerful tool that can help visualize magnetic field. It helped us better understand magnetism and discover Magnetic Field Architecture (MFA™). For more information, see the appendix on Understanding MFA in the User Guide.