--- title: "Check camera positions" canonical: "https://help.vicon.com/space/Evoke14/10159257/Check%20camera%20positions" format: markdown --- Evoke enables you to check whether any cameras have moved by comparing the current camera positions with a snapshot (baseline) of camera LEDs from the previous Evoke session. It also provides information on when a re-calibration is required. When you first start using your Origin system, it is advisable to run a calibration assessment daily, before use. When you have become familiar with how much the rig shifts or cameras get knocked, you may be able to reduce the frequency of this check. > Macro (scroll-only) > > > Macro (toc) > Macro (scroll-pagebreak) ## Generate baseline > Macro (excerpt-include) To generate information on the cameras' current positions: - On the **Calibration Assessment** tab, click **Generate Baseline**.Blue marks are displayed next to most cameras. Each mark represents the LEDs of the other cameras that can be seen by the camera. ## Assess current calibration After you have generated a baseline from which the camera positions can be assessed, you check for camera movement. To do this: - On the **Calibration Assessment** tab, click **Assess Calibration**. On the **Calibration Assessment** tab,most or all of the blue marks turn green. Green marks indicate that the camera position is unchanged since the last calibration. Red marks indicate that something has changed in the calibration, either due to a bump or knock, or because of environmental drift. ![image](media://d8a6cbf4-7965-4041-8ff6-0116d4e12d2b) > Macro (scroll-pagebreak) Depending on whether you have automatic bump healing selected (the default), you may need to take action to correct any changes. > Macro (scroll-only) > > > Macro (toc) See also [Enable automatic bump healing in passive systems](#autoBumpHealPassive). ### Enable automatic recovery of moved cameras When you run **Assess Calibration**, Evoke may indicate that a camera has been moved. If a camera has been bumped enough to move its position, the move is detected, so the LEDs flash red on the camera, and the **System** pane and **Cameras** view display a bump icon to the right of the camera name. **To enable the recovery of a moved camera:** 1. On the **Processing** tab, scroll to the **Camera Healing** section and make sure **Enable Auto Bump Healing ** is selected (it is selected by default). 2. In the volume, have someone wave two of the Pulsars used to set the floor plane in front of the camera until its status light turns blue (or magenta if selected). 3. To generate a new baseline, on the **Calibration Assessment** tab click **Generate Baseline**. This creates a baseline that contains the updated information about the camera positions. If auto-healing doesn't seem to be recognizing or recovering cameras that have moved, see [Understand automatic recovery of moved cameras](#UnderstandAutoHeal). > Macro (scroll-pagebreak) > Macro (anchor) ### Enable automatic bump healing in passive systems Auto-healing in systems with passive reflective markers is turned off by default. To turn it on, in the **Camera Healing** section, select **Enable Healing With Strobes**. ![image](media://d5b1aa67-32aa-4dea-b284-da8256153318) > ❌ **Caution** > ❌ If the environment has many infra-red sources or reflective surfaces that interfere with data that is being processed by the camera, auto-healing can adversely affect the calibration rather than rectifying it. > Macro (scroll-pagebreak) ### Manually recover moved cameras When you run **Assess Calibration**, Evoke may indicate that a camera has been moved. On the moved camera, the LEDs to flash red and on the **System** tab and **Cameras** view, the bump icon is displayed to the right of the camera name. If **Enable Auto Bump Healing ** (see above) is not selected, you can recover a moved camera by using Evoke's **Recover Camera Position** option. **To recover a moved camera:** 1. In the **Tools** pane, on the **Camera Calibration** tab, click **Start ****Recover Camera Position** and in the volume, wave two of the Pulsars in front of the affected camera. In the **3D Scene** and **Cameras** view, orange trails are displayed as the system determines the offset between the camera and the rest of the calibration. 2. When enough of the view has been covered (indicated by orange trails that thickly cover the affected camera view), click **Recover Camera Position**. 3. In the **Cameras** view, zoom in and check that the centroids are now green, and the red icon to the right of the camera names have gone. 4. To generate a new baseline, on the **Calibration Assessment** tab click **Generate Baseline** . This creates a baseline that contains the updated information about the camera positions. > Macro (scroll-pagebreak) > Macro (anchor) ## Understand automatic recovery of moved cameras When **Enable Auto Bump Healing ** is selected, the system detects cameras that have stopped contributing centroids to the tracked objects in the volume if: - The system health connection score for the camera is below 25% (to check this, at the top of the **Cameras** view, hover the mouse pointer over the Connection score icon > Macro (inline-media-image) ). - Enough centroids are visible to this camera. > ⚠️ **Important** > ⚠️ For Enable Auto Bump Healing to work, at least 50% of the enabled objects must currently be tracked by the cameras. > ⚠️ For this reason, disable any objects that can't be tracked (ie, any Pulsars that are charging, powered off or out of the volume). If these criteria are met, the system attempts to bump-heal (recover the position of) the camera. It collects data for a short time and if there is sufficient coverage in the cameras view and the system can find a solution, it applies a new calibration for this camera. This causes the system calibration file, to be re-saved to the following default location: *C:\ProgramData\Vicon\Calibrations\LatestCalibration.xcp* > Macro (scroll-pagebreak) For successful automatic recovery of moved cameras, ensure that your system meets the following criteria: - The cameras’ internal parameters (focal length, radial distortion, etc) do not change. - The cameras have achieved a stable operating temperature before calibration and before starting an experience. - Objects are being tracked by a majority cameras. The easiest way to check this is to select all cameras (or no cameras), look in the **Cameras** view and in **View Filters** ensure **Centroids** is selected. Check that the centroids are green and that no calibration warning icons are displayed. - The bumped camera(s) can see objects and they are generating 2D tracks. - No unmasked camera strobes or reflective objects are present in the system. These may cause the system health of the camera to remain low and to trigger further recalibration. If you need further information about which camera has moved, what may be causing an issue and whether it has been successfully recovered, check the Log (if it isn't displayed, on the **View** menu, select **Log**). The errors, warnings and messages will look similar to this: ![image](media://9324eb88-4c8c-4d53-87d9-ebcf97a22896) ![image](media://d5fa6250-fd61-4dfe-b22b-4bb8c86c3c44) ![image](media://a939c341-e6f2-4ee1-9089-877093c934bb) In the above examples, the camera's Device ID is highlighted. To find a camera's Device ID, on the **System** tab, select the camera, click **Show Advanced** in the **General** section, scroll to **Device ID**.