> For the complete documentation index, see [llms.txt](https://docs.theiamarkerless.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.theiamarkerless.com/apollo-v2024/troubleshooting/sony-troubleshooting/initialization-issues.md).

# Initialization issues

Initialization issues come up occasionally. This process may need to be repeated if there is more than one camera that is having this issue.

1. Place all cameras on Standby.
2. Disconnect all cameras from the network switch.
3. Turn the control box for the problematic camera to OFF and MASTER.
4. Connect the problematic camera to the network switch.
5. Turn the control box to ON.
6. Connect to the browser GUI, and attempt to initialize. Give this some time, and try a few times if necessary.
7. If initialization is successful, put the camera on Standby from the browser GUI and close the browser once the camera is on Standby.
8. Turn the control box to OFF, then switch to CLIENT.
9. Now, connect the original MASTER camera to the network switch (check that it is OFF first).
10. Turn the problematic control box to ON.
11. Turn the master control box to ON.
12. With only these two cameras connected, launch the browser GUI and allow it some time to load. Do not initialize.
13. If the cameras connect successfully, slowly add the other cameras to the system one by one, allowing time for each camera to appear and the system to stabilize before adding the next camera.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.theiamarkerless.com/apollo-v2024/troubleshooting/sony-troubleshooting/initialization-issues.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.