Turbos
Routers for your Voodoo Robotics Cloud Display Devices — connecting devices to the Internet and extending radio coverage across your facility.
What Is a Turbo?
Turbos act like routers by connecting Cloud Display Devices to the Internet. Install one or more Turbos on the ceiling, the wall, or the side of your racks to extend radio range and improve response times.
WiFi / Ethernet
A WiFi or Ethernet connection is needed to connect the Turbo to the Internet and facilitate communication between the cloud and the devices.
Range
Turbos can communicate with devices within approximately 75–100 feet, depending on surroundings.
Extending Range
Multiple Turbos extend the coverage of devices. Turbos are designed for overlapping coverage areas.
Speed
More Turbos increase speed, causing devices to light up faster by distributing the radio load.
Turbo POE-T (Power over Ethernet with Touch Display)
The Turbo POE-T obtains power directly from your Ethernet and enables you to view and edit configuration information on a built-in touchscreen.
Specifications
| Product Dimensions | 7.5" Width × 2.0" Depth × 4.5" Height |
| Radio Range | Approximately 75–100 feet. Depends on surroundings. |
| Required Power | AC adapter or POE (IEEE802.3af/t-Isolated 3kV) |
| Required Connectivity | Ethernet or WiFi (DHCP) |
| Adapter Included | 100–240 Volts, 50–60 Hz Input with USB-C output (cord length 5') |
| Display | Built-in touchscreen |
| Wall Mounting | Can be mounted with screws spaced 3" apart horizontally |
Turbo (Standard)
The standard Turbo can be connected to a monitor to view configuration information. You may also configure it from the server.
Turbo POE Adapter
Use a Power Over Ethernet Splitter Adapter to split your Ethernet connection into power and data, allowing your Turbo to obtain power over the Ethernet. This is a lower-cost option if you want to use Ethernet for power but do not need the Turbo POE-T touchscreen.
Placement Guidance
Proper Turbo placement is critical for reliable device communication:
- Height: Install Turbos on a wall, pillar, or ceiling at a height that's out of reach but not out of range—typically 8–12 feet. Extremely high ceilings (e.g., 50 ft) can put devices out of radio range.
- Spacing: Optimal spacing is one Turbo every 75–100 feet depending on surroundings. Metal shelving, concrete walls, and cold storage environments may require closer spacing.
- Overlap: Turbos are designed for overlapping coverage areas. Overlapping coverage improves reliability and reduces latency.
- Line of sight: While not strictly required, line-of-sight between Turbos and devices improves signal quality.
Placement Best Practice
Power Options
| Option | Model | Details |
|---|---|---|
| AC Adapter | All Turbos | 100–240V, 50–60 Hz, USB-C output (included) |
| Power over Ethernet | Turbo POE-T | IEEE802.3af/t — power delivered via Ethernet cable |
| POE Splitter Adapter | Standard Turbo | External adapter splits Ethernet into power + data |
Operational Tips
- Name your Turbos: Assign a location name to each Turbo in Big Block Server. Nobody wants to refer to a Turbo by its serial number.
- Monitor health: Use Big Block Server to track uptime, temperature, IP addresses, and signal strength for all Turbos.
- Remote diagnostics: Request immediate data from any Turbo without dismounting — check dynamic signal strength to any device or get real-time reported voltage.
- Latency monitoring: Big Block Server provides latency graphs for devices broken down by Turbo, and latency graphs for Turbos broken down by device. Use these to evaluate and optimize your setup.
Note
/api/turbo/ endpoint. See the REST API Overview for details.Network Considerations
Turbos require network access to communicate with the Voodoo Robotics server (either www.voodoodevices.com or your own Big Block Server):
- DHCP: Turbos use DHCP for IP address assignment. Ensure your DHCP server has available addresses.
- Firewall: If using www.voodoodevices.com, Turbos need outbound HTTPS access. If using an on-premise Big Block Server, Turbos only need access to your internal network.
- WiFi vs Ethernet: Ethernet is preferred for reliability, but WiFi works well in most environments.
Static IPs for Turbos
Troubleshooting
Boot Messages Tell You Where the Failure Is
| Boot Message | What It Usually Means | What to Check |
|---|---|---|
| IP address? | The Turbo is still waiting for DHCP to assign an IP address. | Check Ethernet or WiFi connectivity and make sure the Turbo can reach the DHCP server. |
| Server? | The Turbo has an IP address but cannot reach the configured API endpoint, or the login details are wrong. | Check the server URL, username, password, DNS settings, DHCP route, and outbound access on port 443. |
| DB Connect? | The Turbo still cannot complete its connection to the server. | This often points to a firewall or reachability problem between the Turbo and the server over outbound HTTPS. |
Common Reasons a Turbo Will Not Connect
- The PoE cable run is too long or the cable quality is poor. Use Cat5e or, preferably, Cat6.
- Both PoE and the AC adapter are connected at the same time. Use only one power source.
- The Turbo was given an IP address that is already in use by another device.
- The DHCP response does not include a usable network route.
- The DHCP response does not include a DNS server, so the Turbo cannot resolve the server name.
- The Big Block or API endpoint entered on the touchscreen has a typo.
- The username or password entered on the touchscreen is incorrect.
- A firewall rule is blocking the Turbo from making its outbound HTTPS connection to the server on port 443.
Devices not responding
Check that the Turbo is powered on and connected to your network. Verify the Turbo appears in Big Block Server. Ensure devices are within 75–100 feet of a Turbo.
Slow response times
Add more Turbos to reduce radio congestion. Check the latency graphs in Big Block Server to identify bottlenecks. Consider switching to Ethernet if using WiFi.
Turbo not appearing in server
Start with the message shown on the Turbo screen. IP address? usually means a DHCP or basic network problem. Server? usually means the server URL, login details, DNS, route, or outbound access is wrong. DB Connect? often points to a firewall problem between the Turbo and the server. After correcting the issue, power-cycle the Turbo and try again.