Installation

1. Unbox your kit

Voodoo Robotics CEO Trevor Blumenau goes through each item you might have received. The Starter Kit page lists what is in the kit.

2. Insert batteries and try demo mode

Each Cloud Display Device runs on two AAA alkaline batteries. Batteries are not included, so have a bulk pack ready. The battery compartment is on the bottom of the device. Put the batteries in before you mount anything.

Your DeviceID is on the display

Every device has a unique DeviceID, such as E8D008:619874. By default the device shows its DeviceID on its display. The display is e-ink, which keeps its image without power, so the DeviceID stays readable even when the device is off. Your software uses the DeviceID to light a device, so you can read each one straight off the display when you mount it.

Sneak peek: demo mode

Every device has a built-in demo mode, so you can see it work before anything else is set up.

• With the batteries in, hold down the front button for about four seconds to start demo mode.
• To leave demo mode, restart the device by holding the button down again. A device also leaves demo mode on its own as soon as it receives any communication.
• Devices that have a static message or an assigned location will not go into demo mode. Holding the button sends a “call” to the server instead.

3. Set your Big Block password

Big Block Server is the software your devices and Turbos talk to. We have already created an account for you on our hosted Big Block Server at www.voodoodevices.com and registered your new devices in it.

• Look for an email from support@voodoorobotics.com asking you to log in and create a password. If you can't find it, check your spam folder.
• Once you are in, you can use your account to create other accounts, including a dedicated API-User account for your Turbos and software.

The hosted server works for up to 50 devices. Larger deployments need their own Big Block Server, in the cloud or on premises behind your firewall. See Big Block Server and Server & Deployment for the options.

4. Set up your Turbo

A Turbo is the radio router that connects your devices to the server. It needs your network information and a username and password. The Turbo POE-T has a built-in touchscreen, so you don't need a monitor, mouse, or keyboard.

1. Power it on. Use the USB-C wall adapter, or, if your switch or router supplies PoE (Power over Ethernet), just plug in the Ethernet cable. Never use both at once.
2. Connect WiFi (optional; skip this if you are using Ethernet). Tap Connect WiFi, pick your network, and enter its password.
3. Connect to the server. Tap Connect Server and enter the username and password from step 3, or those of a dedicated API-User account.
4. Leave Server Endpoint blank unless you run your own Big Block Server. If you do, enter your server's endpoint, for example https://bblock.yourcompany.com/api.
5. Check the status. After connecting, Status and DB Status should both read okay. If DB Status is not okay, a firewall is probably blocking the Turbo. Contact us and we will help.

Once it is running, the Turbo shows its idle screen. The top line shows two numbers, active devices and visible devices (for example 0-47). The bottom line is the number of devices in your account. The video below shows the rest of the Turbo's features.

5. Test communication

With the Turbo running, you can light a device straight from your web browser:

1. Log in to www.voodoodevices.com and open the Devices tab.
2. Select a device.
3. At the bottom of the device's Info tab, click Identify.

Within about a second, the device should light up with a message. If it doesn't, check that the device is in range of the Turbo and that the Turbo shows okay for both statuses.

6. Mount your Turbos and devices

Turbos

• For best performance, every device should be within 50–75 feet of a Turbo.
• In production, every device should be able to reach more than one Turbo.
• Mount a single Turbo in a central spot, generally 8–10 feet up, with a clear path to the devices. Spread multiple Turbos apart for good coverage.
• The Turbo POE-T's mounting holes are 3″ (76.2 mm) apart horizontally. Use screws with a head between ¼″ (6 mm) and ⅜″ (9.5 mm); #10 pan-head screws are typical.

More placement guidance is on the Turbos page.

Devices

Every device ships in a ruggedized cover. Devices mount to totes, carts, or racking in several ways:

• Magnets. The cover has four N52 neodymium magnets. They are strong but only stick to ferrous (iron or steel) surfaces.
• Steel brackets. For non-ferrous surfaces, Voodoo Robotics sells steel brackets the magnets can hold onto.
• Machine screws. Hole spacing is 1¾″ (45 mm) for single-button devices and 3″ (76.2 mm) for multi-button devices. Use screws with a head between ⅛″ (3 mm) and 0.2″ (5.5 mm); #4 pan-head screws are typical.
• Tape or hook-and-loop. Industrial double-sided tape (3M, Gorilla, or EZlifego) or a strong Velcro such as Alfa-lok also works.

However you mount them, leave the battery compartment easy to reach. As you mount each device, write down which DeviceID is at which location. That list becomes your DeviceID-to-location mapping.

7. Battery life

Devices are designed to run on two AAA alkaline batteries to keep running costs low. Please talk to us before using any other type of battery or power source. Unapproved batteries can be hazardous and can cause a fire or even an explosion.

Big Block Server shows each device's voltage over time. Here is what to expect:

• To estimate battery life for your own pick rates and settings, use the battery life calculator.
• In Big Block Server you can set a warning voltage. You will get a daily email listing every device below that level and its location.
• Batteries change from the bottom of the device, so you don't have to take it down. When a device powers back up it re-synchronizes with the server, so nothing on the display is lost.

8. Connect your software

With the hardware running, the next step is to have your WMS, ERP, or other software light the devices. The rest of this site covers that:

• Getting Started — light your first device with a single API call.
• REST API — the full reference for device commands.
• Integration Examples — code samples you can copy.