Guide/How to test and debug your Miniscope V4

Last reviewed	2026-06-29
Reviewer	User:DAharoni
Next review due	2027-06-29
Review interval	12 months

Review history

2026-06-29 — User:DAharoni — Passed

Overview

This guide walks through bringing up a freshly assembled Miniscope V4 for the first time and verifying that every subsystem (electronics, optics, the electrowetting lens, and the data path) is working before the device is used in an experiment. It also collects common failure modes seen across day-to-day use, with quick checks to localize the problem.

The procedure is organized into two phases that should be performed in order:

Phase I, Pre-Connection Inspection: static, power-off checks of mechanical and electrical integrity. These catch faults that could damage the device or the DAQ if you powered up first.
Phase II, Powered Testing: functional validation of the LED, image sensor, electrowetting lens, and data recording once the device is safely powered.

A new build should pass every step here before it is taken into a recording session. For an existing scope that has stopped working, you can jump straight to the relevant subsystem check, but when in doubt restart from Phase I, since a surprising number of "software" problems trace back to a marginal cable or connector. As you become more comfortable building and using Miniscopes, some of the sections below can be safely skipped for routine builds.

Before You Begin: Safety & Handling

The excitation LED produces bright blue light. Do not look directly into the objective while the LED is driven at high intensity, and keep intensity low while bench-testing.
The Miniscope and DAQ contain exposed, ESD-sensitive electronics. Handle by the housing, work on a clean surface, and avoid touching the image sensor PCB or optics directly.
Keep the objective and filter surfaces clean. If you must clean optics, use lens tissue and an appropriate solvent, never a dry wipe or your finger.
Power the DAQ off before connecting or disconnecting the coaxial cable (see Phase II).

Required Materials & Equipment

1) Device Under Test (DUT): an assembled Miniscope V4:

2) USB 3.0 Micro-B.: We prefer braided cables like this one from Ugreen.

The Miniscope V4 streams uncompressed image data continuously, which is more than a USB 2.0 link can carry reliably, so a USB 3.0 connection is required. (The scope uses only a fraction of USB 3.0's headroom; the point is that USB 2.0 cannot sustain the stream without dropping frames.) To ensure maximum data reliability, avoid using USB hubs, as they can cause intermittent connectivity or dropped frames. It is highly recommended to connect the Miniscope DAQ directly to a dedicated USB 3.0 port on the host computer using a high-quality USB-A or USB-C cable. A few practical notes:

Confirm you are using a true USB 3.0 port; these are usually marked with an "SS" (SuperSpeed) logo or a blue insert. Plugging into a USB 2.0 port is a very common cause of dropped frames.
On laptops and docking stations, ports that share a single internal controller can starve the link under load. A directly connected rear port on a desktop is the most reliable.
If you observe intermittent drops, swapping the cable is one of the fastest things to rule out, since cables fail far more often than DAQs.

3) Miniscope Data Acquisition (DAQ) Box

4) Host computer with the latest Miniscope Software installed.

Keep the DAQ software up to date, since firmware/software mismatches can produce confusing symptoms (no device, garbled frames, or unavailable controls). If you recently updated one, check that the other is current as well.

Phase I: Pre-Connection Inspection (Static Validation)

Before applying power to the Miniscope, ensure mechanical and electrical integrity. Performing these checks first prevents a wiring fault from damaging the DAQ or the scope when power is applied.

Visual & Mechanical Inspection

To avoid light leakage, check that the image sensor PCB and the emission module are thoroughly glued.

To ensure that the focusing works properly, check that there is no gap between the objective module and the emission module.

Light leakage is one of the most common causes of a "washed-out" or high-background image later on, so it is worth being thorough here. While inspecting:

Look for any unfilled seams or pinholes between modules, especially where the emission filter housing meets the sensor PCB. Even a small gap admits ambient or excitation light.
Confirm the optical modules are seated square and fully bottomed-out, with no visible tilt.
Check that no glue has wicked onto an optical surface (objective, filters, or sensor cover glass).
Verify the housing screws are present and snug, but do not overtighten, since the V4 housing is plastic and can crack or distort the optical alignment.

Continuity Check

In our experience, the coaxial cable connection (either to the Rigid-Flex PCB or the SMA connector) is by far the most common point of failure when building a Miniscope system, so it is worth checking carefully. To prevent damage to the PCB and the DAQ, verify that the coaxial cable is properly soldered by testing for a short circuit between the cable shielding and the inner conductor. Use a multimeter in continuity mode for this check:

To measure continuity, place one probe on the inner conductor and the other on the outer shell. If the multimeter beeps, the cable is shorted and must be inspected. If it does not beep, there is no short circuit, and the cable is ready for use.

A short between the inner conductor and the shield is the most damaging fault, which is why it is checked before power. A couple of additional notes:

A short most often comes from a stray solder bridge or a frayed shield strand at the connector. If you get a beep, inspect the SMA termination under magnification before assuming the cable is bad.
The check above confirms there is no short. It does not confirm continuity along each conductor. If you suspect a break (for example, after the LED or data link behaves intermittently with cable movement), also verify end-to-end continuity of the center conductor and of the shield with the probes on opposite ends of the cable.

Strain relief (during assembly). Most cable failures originate at the solder joint, where repeated cable movement fatigues the connection. To take the strain off the joint, cover the solder joint as well as roughly the first ~5 mm of coax extending from it in a semi-flexible epoxy, silicone, or glue (hot glue works well). If you are using the U.FL miniature coax connector to attach to the Rigid-Flex PCB, epoxy the cable to the PCB so that no strain is transferred to the connector itself; these connectors are robust but are not designed to rotate once connected.

Device Manager entry

The DAQ must be loaded with the Miniscope firmware to function. While DAQs typically arrive pre-programmed, you can verify proper operation by connecting the device to the computer and checking its entry under the Cameras tab:

If a 'Westbridge' entry appears, the DAQ must be programmed by following these firmware flashing instructions.

A 'Westbridge' entry means the USB controller has enumerated but the Miniscope firmware has not been loaded, so the device cannot stream. If no entry appears at all under the Cameras tab, the problem is upstream of firmware:

Try a different USB 3.0 port and a known-good cable.
Confirm the DAQ is receiving power.
On a fresh machine, allow a moment for the OS to install its generic USB driver before the device appears.

Host Computer Available Video Codecs

To save recorded video, the host computer must have the appropriate video codecs installed, preferably FFV1 for lossless compression or GREY for uncompressed data. To verify their availability, open the Miniscope DAQ software and inspect the codec selection menu:

If these codecs are unavailable, they can be installed by downloading the K-Lite Codec Pack.

Guidance on choosing a codec:

FFV1 (lossless): the recommended default for most experiments. It preserves pixel values exactly while substantially reducing file size, which matters for the data volumes the V4 generates.
GREY (uncompressed): use when you need the lowest possible CPU load during acquisition, or when a downstream tool requires raw frames. Expect significantly larger files.
After installing codecs, restart the DAQ software so the new options appear in the menu. If recordings still fail to save, confirm the host has enough free disk space and write throughput to keep up with the data rate.

Phase II: Powered Testing & Functional Validation

For this phase, connect the Miniscope to the DAQ. Ensure the DAQ power is turned off, then plug the coaxial cable into the 'Miniscope' SMA receptacle. Once securely connected, power on the DAQ; if the system initializes correctly, three status LEDs will illuminate.

Always connect the coaxial cable with DAQ power off, then power up, as hot-plugging can stress the electronics. The three status LEDs are your first end-to-end indication that the scope, cable, and DAQ are all communicating. An intermittent or flickering Data Link light indicates an unstable connection; inspect, repair, or replace the coaxial cable. If the lights do not come on at all, return to the Phase I continuity and connector checks before proceeding, and confirm the SMA connector is fully seated and finger-tight.

Cable stress test. With video streaming from the scope (open the DAQ software and connect to the Miniscope), move, twist, and wiggle the coaxial cable with greater intensity than you would expect an animal to apply, paying particular attention to the ends of the cable near the solder joints. If the cable is soldered and strain-relieved correctly, the video stream should not drop out or freeze even under excessive movement and twisting. Any dropout under this test points to a marginal connection that will fail during an experiment, so repair or replace the cable before continuing.

Excitation Light Source (LED)

To verify excitation LED functionality, adjust the intensity slider in the Miniscope DAQ software and confirm that blue light is emitted from the objective lens.

The output should track the slider smoothly across its range. If the LED does not light:

Confirm the three status LEDs are on and the Data Link is stable, as no link means no LED control.
Check the cable continuity, as a marginal center conductor can power the device enough to enumerate but not drive the LED reliably.
If the LED flickers as you move or flex the cable, treat it as a connection fault rather than an LED failure.

Sensor Gain

To verify CMOS image sensor functionality, perform a gain check. Place the Miniscope over a test target (such as a piece of paper inside a small box) to block ambient light, and turn on the excitation LED. Gradually increase the gain in the software; the live image should become uniformly brighter.

What "healthy" looks like: the whole frame brightens evenly and smoothly as gain increases, with no large dead regions, fixed bright/dark columns, or heavy banding. Things to watch for:

Non-uniform brightening or dark blotches can indicate light leakage (revisit the Phase I gluing check) or a contaminated optical surface.
Frozen, garbled, or banded frames point to a data-path problem (USB port, cable, or hub) rather than the sensor itself.
A completely black image even at high gain, with the LED confirmed working, suggests the sensor or its connection is faulty.

Light Leakage Check (Powered)

When a scope is assembled correctly, no excitation light from the LED should reach the CMOS imaging sensor directly. This powered test complements the Phase I visual inspection and quantifies any leak. With the scope connected and streaming in the DAQ software, place the opening in the base of the scope against a black surface that will not fluoresce. You may be surprised how many materials weakly fluoresce green under blue excitation, so black electrical tape is a reliable choice. Turn the gain to its maximum value, then slowly raise the excitation LED power from 0 to maximum while watching the video stream. What to look for:

A small overall rise of ~20 in pixel value (on the 0–255 scale) as the LED ramps up is expected and acceptable.
Large, broad increases in brightness across big regions of the image indicate light leakage. The most common causes are an excitation or emission filter that is scratched, installed in the wrong orientation, or significantly misaligned, so inspect the filters before continuing.
At maximum gain you may also notice that some individual pixels become noisy. This is normal; in experiments, minimize it by limiting the gain, or correct these hot pixels during offline processing.

Imaging Everyday Objects

A working scope can image many everyday objects that fluoresce. Bring the scope to within about 1 mm of an object and turn on the excitation LED. Good test targets include white paper, clothing, and hair; you can also image objects that emit green light directly, such as a computer monitor. This is a quick, qualitative confirmation that the LED, optics, and sensor are all working together before you move on to focus calibration.

Electrowetting Lens (EWL) & Focus

One of the most critical steps in completing a Miniscope assembly is validating the Electrowetting Lens (EWL). To test this, hold the Miniscope stable against the computer monitor. While maintaining its position, adjust the EWL slider in the software to confirm that the display's subpixel grid smoothly shifts in and out of focus:

If the focus plane does not shift, verify that the EWL is correctly seated and aligned within the objective module, and check that the EWL flex cable connection is properly seated, since repositioning this connection resolves many "no focus change" cases. If the mechanical positioning and flex cable are correct, the EWL driver IC on the PCB may be damaged, requiring a replacement of the Miniscope PCB.

Additional tips for this test:

Use the monitor's subpixel grid as your target, since it is fine and high-contrast, which makes the focus sweep easy to see. Keep the scope pressed flat and steady so you are observing focus change, not motion.
The transition should be smooth and continuous across the slider. Jumpy, partial, or one-directional focus change can indicate a marginally seated EWL or a driver problem.
If focus shifts but cannot reach a sharp plane, double-check that the objective and emission modules are fully seated (Phase I), since a small gap there shows up as an inability to focus.

DAQ Software & Host Stability

When running a Miniscope system on a new computer, it is worth confirming that the host can hold a stable stream and keep up with the data rate before relying on it for an experiment. These are live checks performed in the DAQ software (connect the scope to the DAQ, the DAQ to the computer, then connect to the Miniscope in software).

Stream stability. Some combinations of USB drivers, computer hardware, and Windows OS can cause the video stream to fail a few minutes after the software connects. This is historically most associated with older Windows versions, and is independent of whether you are recording to disk. Because new DAQ software has not been validated across every possible configuration, it is still good practice to assume an unexpected issue could arise. To test: leave the system streaming for 5 minutes without clicking record. If the stream is still present and has not frozen or crashed, the host should be free of driver/OS issues.

Live frame rate. The default frame rate is 30 FPS, adjustable with the 'FPS' slidebox in the DAQ software. Observe the current frame rate displayed at the top-center of the video window; it should hold within about 1 FPS of the expected value. This live readout is approximate; the recorded video's frame rate is far more stable (see below). If you connect a behavioral camera to add load, expect somewhat larger fluctuations in its displayed rate.

Write speed. Confirm the computer can write data to disk at least as fast as it is acquired, ideally much faster. Slow or encrypted drives are a common bottleneck. Click 'record' and watch the "Filled Buffer" display at the top-right of the video window: this shows how full the circular frame buffer becomes before data is flushed to disk. It should stay at or near '0' with only minor fluctuations into single digits. If the value climbs, turns red, or approaches the maximum buffer size, you will begin to lose frames during recording, so move to a faster/unencrypted drive or reduce the data rate.

Frame Rate Stability

As a final quality check, verify that data is saving correctly by recording a brief video and inspecting the generated timestamp file. The expected interval depends on the frame rate you selected (the default is 30 FPS). In the example below, recorded at 20 FPS, the interval between successive timestamps should be approximately 50 ms:

In general, the expected interval is 1000 / FPS milliseconds (20 FPS → 50 ms, 30 FPS → ~33 ms). When reviewing the timestamps:

Intervals should be tightly clustered around the expected value. Occasional large gaps or a frame count lower than expected indicate dropped frames, almost always a data-path issue (USB 2.0 port, hub, marginal cable, or a host that cannot keep up with disk writes).
Confirm the recorded frame count matches the expected count for the recording duration.
If you see drops, re-check that you are on a dedicated USB 3.0 port with no hub, try a known-good cable, and consider a lower frame rate or the GREY codec to reduce host load while you isolate the cause.

Troubleshooting Quick Reference

Symptom	Likely cause	What to check
No device under Cameras tab	No power, bad cable/port, or USB enumeration failure	DAQ power; swap USB 3.0 port and cable; allow OS to install driver
'Westbridge' entry appears	DAQ firmware not loaded	Flash firmware per the linked instructions
Status LEDs do not illuminate	Cable/connector fault or power	SMA fully seated; Phase I continuity check; DAQ power
Data Link light flickers	Unstable coaxial connection	Inspect, repair, or replace the coaxial cable
Excitation LED won't turn on	No data link or marginal cable	Confirm stable link; continuity of center conductor
Image stays black at high gain	Sensor or connection fault (LED confirmed on)	Cable continuity; sensor seating; PCB
Uneven brightness / dark blotches	Light leak or dirty optics	Phase I gluing/gaps; clean optical surfaces
Garbled / banded / frozen frames	Data-path bandwidth problem	Use true USB 3.0 port, no hub; swap cable
Focus won't shift with EWL slider	EWL misseated, flex cable, or driver IC damaged	Reseat/align EWL; reseat EWL flex cable connection; if mechanically correct, replace PCB
Video stream drops when cable is moved	Marginal solder joint / poor strain relief	Cable stress test; re-solder and epoxy joint + first ~5 mm
Stream freezes/crashes minutes after connecting	USB driver / OS incompatibility (esp. older Windows)	5-minute no-record stability test; try another machine / driver
"Filled Buffer" climbs or turns red	Disk too slow / encrypted to keep up	Use faster, unencrypted SSD; lower FPS / data rate
Broad brightening at max gain as LED ramps	Light leak (filter scratched, misoriented, or misaligned)	Inspect excitation/emission filters; check orientation and alignment
Dropped frames in timestamp file	Insufficient USB bandwidth or host throughput	Dedicated USB 3.0 port; no hub; lower FPS / GREY codec; disk speed

Imaging Reference Samples

Before moving to freely behaving animals, it is helpful to image a few known samples to confirm image quality and to give yourself a reference for focus and resolution. Good choices include:

Brain slices expressing green fluorescence (e.g., GFP/GCaMP), which most closely resemble the in-vivo target.
A resolution test slide with a piece of green-fluorescing tape placed underneath it, which lets you assess the scope's spatial resolution and check focus uniformity across the field of view.

Next Steps After Validation

Once the device passes every check above, it is ready to move from the bench into use:

Record a short reference video and archive it with the device's ID so you have a known-good baseline to compare against if problems appear later.
Note any borderline observations (e.g., a cable that had to be replaced, an LED that needed a higher-than-usual drive) in the device's records.
Proceed to in-vivo focusing and experiment setup per your lab's imaging protocol.

If a device fails a check that cannot be resolved by reseating, cleaning, or swapping the cable, document the failing step and consult the relevant assembly or repair guide before returning it to service.