> For the complete documentation index, see [llms.txt](https://yall.yassrobotics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://yall.yassrobotics.com/documentation/how-to-guides/how-do-i-use-multiple-limelights.md).

# How do I use multiple Limelights?

## Give each camera a unique NT name

Rename each camera in its web UI (Settings tab → team number/name) so their NetworkTables tables don't collide — e.g. `limelight-front` and `limelight-back`.

## Create one Limelight object per camera

```java
Limelight front = new Limelight("limelight-front");
Limelight back  = new Limelight("limelight-back");
```

Each `Limelight`, `LimelightSettings`, `LimelightPoseEstimator`, and `PoseEstimate` instance is bound to its own camera — nothing is shared or global, so there's no special coordination needed beyond keeping the objects around (usually as subsystem fields).

## Fusing pose estimates from multiple cameras

Feed every camera's filtered `PoseEstimate` into the same drivetrain pose estimator — WPILib's pose estimators accept multiple `addVisionMeasurement` calls per loop from different sources:

```java
for (Limelight ll : List.of(front, back)) {
    ll.getSettings().withRobotOrientation(currentOrientation).save();
    ll.createPoseEstimator(EstimationMode.MEGATAG2).getPoseEstimate().ifPresent(estimate -> {
        if (estimate.tagCount > 0 && estimate.getMinTagAmbiguity() < 0.3) {
            poseEstimator.addVisionMeasurement(estimate.pose.toPose2d(), estimate.timestampSeconds);
        }
    });
}
```

Give each camera an accurate, distinct `withCameraOffset` — this is what lets pose estimates from physically different mounting points agree with each other once fused.

## See Also

* [AprilTag Pose Estimation tutorial](/documentation/tutorials/apriltag-pose-estimation.md)
* [Pose Estimation & Ambiguity](/documentation/understanding/pose-estimation-and-ambiguity.md)


---

# 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, and the optional `goal` query parameter:

```
GET https://yall.yassrobotics.com/documentation/how-to-guides/how-do-i-use-multiple-limelights.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.