Page tree
Skip to end of metadata
Go to start of metadata

Frequently Asked Questions (FAQs) about octoBox Testbed

Q: Do you have the octoScope documentation online?

A: Yes, please see it here: Documentation

Q: Do you have any octoScope device Rest API information online?

A: Yes, please see it here: Rest API

Q: How do I measure MU-MIMO gains?

A: Please see slides 25-27 in the octoBox presentation below, and watch the video by following the link on slide 25. The MU-MIMO content starts at 6 minutes 10 seconds into the video.

The Pal can be your partner device for MU testing, vastly simplifying the testbed.  The Pal can be a station or an AP.  

Q: Can you provide some examples of how best to orient Dipole antennas?

A: Please review this slide for some examples and diagrams:

Q: What are the best ways to setup the antennas for OTA-OTA (Over The Air) reception?

A: Please review this short PowerPoint for some tips:

Q: What does the octoBox testbed do and how is it used?

A: octoBox is a small stackable semi-anechoic testbed used for testing wireless devices and systems, including phones, access points, sensors and other such devices. It isolates the devices under test from the outside interference and creates a stable environment for achieving repeatable measurements.
Inside the octoBox testbed you can emulate real life conditions, including path loss, multipath and interference.
The building blocks of the testbed include the octoBox small anechoic chambers, the MPE (multipath emulator) module, quadAtten programmable attenuator module and iGen interference generator module.

Q: What measurements can you perform in the octoBox testbed?

A: Engineers most often use octoBox to measure throughput of the new 802.11ac or LTE MIMO devices.
octoBox testbed can also be configured for mesh testing (self-forming, self-healing functions of a mesh), high speed roaming and other wireless tests.

Q: What is the supported bandwidth? And what kind of devices can be tested?

A: octoBox is used for testing Wi-Fi, 2G/3G/LTE, Bluetooth GPS and other devices.
It offers ideal conditions for multi-stream MIMO throughput and supports the operating frequencies from 700 MHz to 6 GHz.

Q: Can you inject interference?

A: Yes. Each octoBox comes equipped with 8 RF ports (SMA or N-connector). Typically 4 of the 8 ports are used for 4x4 MIMO signal. The other 4 ports can be used to inject interference or for monitoring.
For example, you can use 2 of the RF ports to inject traffic interference on the adjacent channels, one of the ports to inject co-channel interference and the remaining port for interference waveforms emulating other common sources of interference, such as radar, wireless phones, baby monitors, etc.
The octoBox iGen module serves to provide programmable sources of traffic and waveform interference.

Q: Can you capture and replay interference in a typical home?

A: You can capture traffic using a Wireshark sniffer and replay it inside the octoBox using the iGen module.

Q: How does the MPE module work?

A: Multipath emulator uses long RF cables to emulate multipath reflections in a typical house. Instead of bouncing from wall to wall, the signal bounces between a discontinuity and the shorted end of the cable. The MPE implements the IEEE standard 802.11 models of a typical house (model B) and of a typical office (model C).

Q: What kind of antennas can be used for MIMO-OTA testing?

A: We recommend the octoBox High Gain log-periodic antennas, OBS-14.

Q: What are the programmable attenuators and how are they used?

A: octoBox quadAtten modules are digitally programmable solid state attenuators. Each of the 4 attenuators in a module can be independently programmed via USB or Ethernet.
The attenuator modules are completely isolated from external interference with all copper cables (power, USB and Ethernet) entering the module through filters.

Q: What is the frequency and attenuation range of the attenuators?

A: The attenuator frequency range of near DC to 6 GHz covers most of the wireless services of interest, including 2G/3G/4G, Bluetooth and dual band Wi-Fi. The attenuation range of 0 to 63 dB with 0.5 dB steps provides an accurate and broad sweep of the receiver dynamic range down to the lowest levels.

Q: You mentioned that attenuators have filtered Ethernet and USB ports. Why is it important to filter data and control interfaces?

A: Any copper wires, such as power, Ethernet, USB, HDMI, etc. can act as antennas coupling interference between the outside and the test environment. Any copper cables entering octoBox are coupled through filters.
Power and ventilation are also filtered. Vents are made of honeycomb waveguide structure to provide isolation at the frequencies of operation.

Q: How does the test automation software work and what does it produce for test results?

A: The throughput test automation software controls the turntable, attenuators and traffic generation between devices in the testbed and produces and Excel based plot that engineers can easily manipulate.

Q: Is octoBox based testbed extensible to multi-device test networks?

A: Yes – multi-chamber stackable testbeds can be constructed to emulate multi-room homes, mesh networks and high mobility multi-node robotic networks. The stackable extensible octoBox architecture has been optimized for constructing large testbeds.

Q: Do you have sample test results?

A: Sure, please take a look here:

‘How we test’:


Q: How do I do a firmware update on the quadAtten Device?

A: Call Support!

octoScope recommends that you contact our support team if you need to do a firmware update of a quadAtten device.
Failure to update the firmware properly could render the device inoperable. 

The latest version of the quadAtten firmware can be found here, and you'll need a windows machine:

And these are the instructions:

Q: What radar signals does our OB-iGen support?

A:  The iGen supports the "Short Pulse Radar Test Waveforms", as described in section 6.1 of the FCC document:  


For your convenience, you can download this document here:

Each Radar Type specifies a range of possible acceptable parameters. 

Below are the values we chose for our implementation:

FCC RADAR TypePulse Width (μsec)  PRI (μsec)Number of Pulses

Each pulse pattern above is generated once per second in a continuous loop.

  • No labels
Write a comment…