> For the complete documentation index, see [llms.txt](https://docs.velogicfit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.velogicfit.com/section-01-getting-started/femto-mega-troubleshooting.md). # Troubleshooting Orbbec Femto Mega camera Velogic Studio Essentials and Velogic Studio Pro can utilize the Femto Mega camera from Orbbec, which looks like this: ![Orbbec Femto Mega camera device showing its compact design with front-facing sensors and indicator lights](/files/Bbz8Amnz6fSoDGuaE77C) You can think of this camera as a miniaturized version of the Kinect, with an on-board CPU. It is connected to your PC via an Ethernet cable, which also supplies the power to the camera. If you have more than one Femto Mega camera, you'll also have a second Ethernet cable which provides the sync signal to the camera. ## Indicator lights You can check the indicator lights to help determine whether the camera is functioning properly. ### Front LED ![Close-up view of Femto Mega camera front LED indicator light used for status monitoring](/files/ppaES7t34g6YfxJlVuBe) | LED status | Meaning | | --------------- | ----------------------- | | Solid white | On and ready | | Off | Off (or booting up) | | Blinking orange | Waiting for sync signal | Note that "Solid white" means that the device has power and the onboard CPU is running; it does not necessarily mean that the sensors in the camera are active and streaming. You can check the front laser (below) to see if the sensors are active. If the indicator is "Blinking orange", that means that the camera is configured to be a Secondary camera (in the Sync settings in Velogic Studio). As a Secondary camera, it will only run when it receives a Sync signal from the Primary camera. Steps to troubleshoot this: * Check that you have the Primary camera configured as a Primary in Velogic Studio * Check that the Primary camera is running (Front LED is on, and Velogic Studio is receiving frames from it) * Check that you have sync cables from both the Primary and Secondary camera going to the Sync Hub * Check that the Sync Hub has power (via USB-C adaptor) * Check that the Primary camera's sync cable is going into the front of the sync hub (the side with only 1 RJ45 jack) * Check that the Secondary camera's sync cable is going to one of the 8 ports in the "Secondary" group on the back of the sync hub ### Front laser This is not strictly speaking an indicator LED; it's the actual laser that the camera uses to emit the light pulses which are then received onto the depth sensor to determine depth in the scene. ![Front laser emitter on Femto Mega camera showing the structured light pattern used for depth sensing](/files/9vFOOd2WqSno02ygBZIx) You'll be able to see this laser as a red light that appears to have "structure". The laser should only be on when the camera is active and streaming data to Velogic Studio. We recommend that you turn the power to the whole camera off overnight, just in case the camera gets into a state where the laser is running when not needed. ### Rear LED The light at the rear of the camera will be the first one to give any indication as the device boots up. | LED status | Meaning | | -------------- | ------------------ | | Solid white | On and ready | | Off | No power to device | | Blinking white | Booting | ## If the camera regularly disconnects and reconnects ... the most likely cause is the sync system, either because the sync cables aren't high quality OR the sync hub isn't getting USB power. **Quick fixes:** * The voltage switch on the Sync Hub should be set to 5V, and you should see a blue light beside the voltage switch. If you don't see the blue light, try a different USB power adaptor (make sure it **isn't** marked as "PD") and/or USB-C cord. * Try a higher-quality and/or shorter cable for the primary and secondary sync cables. * If you have one cable that's longer than the others, make that a secondary camera. The sync pulse which is output from the Sync Hub seems better able to travel longer distances than the sync pulse from the camera itself. If those quick fixes don't work, here's a longer procedure to confirm that the sync system is actually the cause of the problem: 1. Watch the light on the right-hand side of the face of the camera. * If it is consistently blinking orange, that means it's configured as a Secondary (so it's waiting for a sync pulse) but it's not getting the sync pulse * If it starts out white, but then blinks orange, and then repeats that cycle: this means the camera gets an inconsistent or poor-quality sync signal. This causes an internal error in the camera, so it reboots and tries again. 2. Unplug the Sync cable from the pigtail adaptor at the camera * The camera should now stop the disconnect/reconnect cycle in Velogic Studio (or at least, the disconnects should be less frequent and take only a second or two each time). * You should see the configuration options, but no video feed from the camera: ![Velogic Studio camera card showing configuration options but no video preview when sync cable disconnected](/files/v9kQYyLuMXIbT4Qr4cVq) * The light on the front of the camera should be blinking orange, because it can't get any sync signal at all. 3. Change the Sync settings to make the camera Standalone (so it's not waiting for a Sync signal anymore): ![Camera sync settings panel with Standalone mode selected to disable sync signal dependency](/files/QNv7uPEasMYkdpRVC2b5) * The camera will restart, and after about 30 seconds you should get a solid video feed from the camera. If you do now get a solid video feed from the camera, after switching it to Standalone mode, **you've successfully confirmed that the Sync system is the issue**. You can use Velogic Studio in this state; there is a small chance that the cameras will interfere with each other (because the sync system is not working), but the chance is small and the system will still be useable while you are fixing the sync system. ### How to fix the sync system * Check that all of the cables used in the sync system are high-quality **Cat6 or Cat6a** cables. This includes the cable from the primary camera to the sync hub, and from the sync hub to all secondary cameras. * Try shorter cables, even if that means running a cable directly across the floor rather than routed through the walls * Check that the sync hub voltage switch is set to 5V * Check that the sync hub has 5v power (the sync hub doesn't ship with a USB-C power adaptor, but it needs one). To check this, you can temporarily set the voltage switch to 5V, and the LED light next to the switch should turn on. If the LED light does not turn on, double-check the USB-C power adaptor or try another one. Note that USB-C power adaptors marked as PD (Power Delivery) will not work with the sync hub. ## Low frame rate There are several possible causes of low frame rate from an Orbbec Femto Mega camera. Work through the following list to identify and resolve the issue. ### Power-cycle the camera As a first step, power-cycle the camera by unplugging it from its Ethernet cable, waiting about 10 seconds, and plugging it back in. Wait about 30 seconds for the camera to boot and reconnect to Velogic Studio. This clears any temporary state that may have caused the camera to misbehave. ### Bad network cable The Ethernet cable connecting the camera to your network switch may be too long or of insufficient quality. This can cause dropped frames or inconsistent data transfer. **Diagnosis:** Replace the cable with a shorter, higher-quality Cat6 or Cat6a cable and see if the frame rate improves. If you have more than one camera and only one has low frame rate, try physically swapping the two cameras so that each camera uses the other's cabling. If the problem follows the cabling (i.e. the other camera now has low frame rate), the cable is the issue. ### Sync system If the camera with low frame rate is configured as a Secondary, it waits for sync pulses from the Primary camera via the Sync Hub before firing its own laser. If those pulses don't arrive reliably, the camera can't maintain a steady frame rate. **Diagnosis:** Change the camera's Sync setting to **Standalone**, and wait for it to reconnect. If the frame rate is now good, the sync system is the cause. To fix the sync system: * Use shorter, higher-quality **Cat6 or Cat6a** cables for all sync connections * Check that the Sync Hub voltage switch is set to **5V** and the LED beside the switch is on * Check that the Primary camera's sync cable goes to the front of the Sync Hub (the side with only 1 RJ45 jack) * Check that Secondary cameras' sync cables go to the "Secondary" group on the back of the Sync Hub * Make sure the Sync Hub's USB-C power adaptor is **not** marked as "PD" (Power Delivery) ### Network switch Not all network switches can handle the volume of data from Orbbec Femto Mega cameras, especially when running multiple cameras simultaneously. We recommend the Ubiquiti UniFi switch because it is known to reliably handle the full traffic from up to 3 cameras. Other switches may claim compliance with the required network standards but fail to cope under sustained load. If you are using a different switch and experiencing frame rate issues, try replacing it with the recommended [Ubiquiti 8-port switch](https://www.amazon.com/Ubiquiti-Switch-Gigabit-802-3at-USW-Lite-8-PoE/dp/B08KC6KT1F). ### Shared network port Each Orbbec Femto Mega camera generates a large amount of network traffic. If your cameras share a network port with other traffic (such as your office LAN), this is not a supported configuration and will likely cause frame rate issues. Make sure your cameras are connected to a dedicated Ethernet port on your computer. If you don't have a spare port, you can add one using a [USB-to-Ethernet adaptor](https://www.amazon.com/USB-Ethernet-Adapter-Gigabit-Switch/dp/B09GRL3VCN) — it must be **Gigabit** (1 Gbps) rated. ### Computer performance If your computer doesn't have enough processing power — particularly when running 3 cameras — it will drop frames. **Diagnosis:** Open Task Manager while Velogic Studio is running (press **Ctrl+Shift+Esc**), and click the **Performance** tab. Watch the CPU usage graph. If CPU usage is consistently above about 70%, the computer is likely struggling to keep up. Another sign is if frame rate is fine with one or two cameras, but degrades when you add a third. **Quick fix:** In Velogic Studio, go to the camera configuration panel (Step 1) and check whether **Create 3D view** is turned on. If so, turn it off — this option uses significant CPU and is not needed during normal fitting sessions. **Solution:** If CPU usage is still too high after turning off the 3D view, upgrade to a higher-spec PC. See our [PC System Requirements and Compatibility Guide](/section-01-getting-started/pc-system-requirements.md) for minimum and recommended specifications. ### Third-party antivirus with network protection Some third-party antivirus software includes network protection features that attempt to scan all network traffic. The high volume of data from Orbbec cameras can overwhelm this scanning, causing frame drops. McAfee is a known example. The built-in Windows Defender does not cause this issue. **Solution:** Uninstall the third-party antivirus software. Windows Defender provides sufficient protection and does not interfere with camera traffic. ## Getting help If you've tried the troubleshooting steps above and are still experiencing issues, you can [book a remote support session](/section-01-getting-started/sharing-with-support.md#sharing-your-screen-so-we-can-help-you-in-a-live-support-session) with our technical team. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.velogicfit.com/section-01-getting-started/femto-mega-troubleshooting.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.