No. Orbit Pro and Orbit Air are designed to operate outside your institution’s existing network infrastructure. The wireless link happens between the camera and receiver, while the host device sees Orbit as a standard USB UVC camera or direct HDMI source. No proprietary networking driver or network-based camera connection is required on the host device.

Most competing wireless document cameras rely on a network-style connection model at the host device, often through a vendor app, proprietary networking workflow, or a secondary NIC-style dongle. That means added IT review burden, added software complexity, and a less direct compatibility path than a standard USB camera workflow. Orbit is different because it is built around a wired-wireless hybrid architecture that lets the host device see the camera as a standard USB UVC device or HDMI source instead of a network camera. That preserves plug-and-play simplicity, broad compatibility, and a much cleaner deployment model.

Orbit Pro adds another major differentiator: to our knowledge, it is the only wireless document camera using 60 GHz mmWave technology, which does not pass through classroom walls and requires line of sight between camera and receiver.

No. There are no SSIDs to configure, no passwords to enter, no access points to provision, and no network settings to change. Orbit Pro and Orbit Air are designed to work independently of your school’s existing network infrastructure.

No. Orbit is designed for true plug-and-play use. In USB mode, the receiver presents Orbit to the host as a standard USB UVC camera, so no proprietary driver is required. Optional HoverCam Flex software is available for annotation, whiteboarding, recording, scanning, and other advanced features, but it is not required for basic camera use.

Typically less than a minute. In most cases, setup is simply: connect the receiver, power on the camera, open your preferred camera app, and select “HoverCam Orbit” if needed. Initial connection may take a short moment while the camera and receiver establish the wireless link.

Initial connection usually takes around 30 seconds.

Yes. Orbit is designed to work with Windows, macOS, ChromeOS, and Android-based interactive flat panels through USB UVC, as well as with displays through HDMI. Because the receiver presents Orbit like a standard USB camera or HDMI source, compatibility is much broader than with app-dependent network camera systems.

No. Orbit Pro uses 60 GHz mmWave technology for its wireless link. Orbit Air uses a dedicated private 5 GHz wireless link, but it does not connect to your institution’s Wi-Fi network, nor does it appear to the host device as a network client. In both cases, Orbit connects to the host device simply as a USB UVC camera or HDMI feed, not as a network device.

A WiFi or IP camera uses a network-based connection model. That means video is transported through a network stack, typically requiring software, app-based discovery, or a proprietary workflow to receive and display the image.

A Wireless USB camera works differently. It preserves the behavior of a normal USB camera on the host side, so the receiving device sees standard USB UVC and/or UAC data just as if the camera were plugged in directly by cable. That is what enables broad compatibility and true plug-and-play operation across common operating systems and camera-enabled applications.

That distinction is the heart of Orbit’s design. To our knowledge, Orbit Pro and Orbit Air are the only wireless document cameras built around this Wireless USB approach.

Orbit Pro operates in the 60 GHz band rather than standard Wi-Fi bands, so it does not interfere with classroom Wi-Fi. Orbit Air uses a dedicated private 5 GHz link and remains separate from your existing network infrastructure, though like any product operating in 5 GHz spectrum, it can be more sensitive in extremely crowded RF environments.

No. Orbit Pro uses a dedicated private 60 GHz mmWave wireless link, and Orbit Air uses a dedicated private 5 GHz wireless link.

Orbit Pro has been tested beyond 100 feet with clear line of sight maintained. Orbit Air uses standard 5 GHz range (typically up to 100 feet or more in typical classroom conditions) and does not require line of sight.

To our knowledge, Orbit Pro and Orbit Air are the only wireless document cameras built around this true Wireless USB approach, where the host device sees the camera as a standard local USB UVC device rather than a network camera.

No. Orbit is not designed around Miracast, AirPlay, Chromecast, or browser-based casting protocols. Orbit uses its own direct wireless link and outputs through the included receiver as USB UVC or HDMI.

It’s simple and plug-and-play.

Step 1) Connect the receiver to a PC, Mac, Chromebook, or Android interactive flat panel via USB, or to a display via HDMI.

Step 2) Turn on the camera.

Then open any camera app and select “HoverCam Orbit” if needed. The camera and receiver are factory paired and automatically search for one another. USB-A and USB-C cables are included for flexible computer connectivity.

Orbit is designed to minimize deployment effort. There is no network provisioning, no SSID setup, no passwords, no driver rollout, and no need to install proprietary networking software on teacher devices. Because the units are factory paired and plug-and-play, rollout is much simpler than with network-dependent wireless camera systems.

Orbit supports both wireless and wired output options. Wirelessly, the included receiver can connect by USB to a host device or by HDMI to a display. Wired, the camera can connect directly by HDMI. Orbit can also support simultaneous wireless USB and HDMI output through the receiver workflow.

Yes. Orbit can support wireless USB output to a host device and HDMI output to a display at the same time through the included receiver workflow.

Yes. Orbit includes a wireless receiver for wireless USB or HDMI use.

If you are using Orbit wirelessly, yes. The included receiver is required. Orbit may also be used wired through a direct HDMI connection from the camera.

Yes. You can connect the receiver to a projector’s HDMI input and power the receiver appropriately. The projector will display Orbit just like any other HDMI source.

Yes. You can connect the receiver to a TV’s HDMI input and power the receiver appropriately. The TV will display Orbit like any other HDMI source.

Yes. Orbit is recognized by macOS as a standard USB camera in USB mode, and our optional Flex software is available for added features.

Yes. Orbit is designed to work with Chromebooks that support standard USB webcam functionality. We also offer Chromebook-compatible software options for added functionality. As with any USB camera, experience can vary with the capabilities and policies of the specific device.

Yes. The receiver can connect directly to many Android-based interactive flat panels through USB for camera use or through HDMI for direct display output. Some panel vendors may restrict camera access inside certain apps, so compatibility can depend on the panel’s USB camera support and software policies.

Yes. In USB mode, Orbit appears as a standard USB UVC camera, so it can be used by video conferencing, recording, and classroom software that supports USB cameras. Our optional Flex software adds more document camera features, but it is not required for basic compatibility.

Yes. Orbit appears as a standard USB webcam, so it works natively with Zoom, Microsoft Teams, Webex, Google Meet, and other video conferencing platforms that support USB cameras.

We include both USB-A and USB-C cables so Orbit can work with laptops that do not have USB-C, provided the port meets data and power supply requirements for the receiver.

Yes, though USB 3.0 or higher is recommended for the best experience. USB 2.0 may limit overall performance compared with higher-throughput ports.

Very little. In most environments, teachers simply connect the receiver, turn on the camera, and open their preferred camera app or classroom software. Because Orbit behaves like a standard USB camera or HDMI source, the learning curve is far lower than with network-dependent wireless camera systems.

The biggest difference is the wireless technology. Orbit Pro uses 60 GHz mmWave and requires clear line of sight between the camera and receiver, which helps avoid traditional Wi-Fi-band interference. Orbit Air uses a dedicated private 5 GHz wireless link, which offers more flexible placement while still staying separate from your institution’s network infrastructure.

Orbit Pro: Up to 6 hours with normal use.

Orbit Air: Up to 8 hours with normal use.

Charging takes approximately 3 hours using the included DC 12V power adapter. We recommend charging the camera overnight and during the day while not in use.

Yes. Orbit includes a built-in microphone for video and audio recording.

Yes. Orbit includes a five-year parts and labor warranty against manufacturer defects. The warranty does not cover normal battery depreciation or general wear from use.