• Cameras are beeping / low pitch
    • This is usually happening only on cameras that have touchscreen enabled. Simply turn off that feature.
  • Cameras are beeping / high pitch (when using a trigger cable)
    • You either have a defect audio cable in the loop, or you are chaining too many cameras using audio cables. Never connect more than 6 cameras on a single cable loop. We highly recommend using solid solutions like Esper triggerboxes boxes to trigger your cameras
  • Some cameras are not syncing the settings
    • Settings are always in sync with all cameras. If you get an error message saying that one camera can’t change iso, f-stop or any other value, make sure it is set to manual (M) mode on the top dial.
    • Another problem that can happen is that if you are mixing two different models of lenses, you might have different f-stop ranges. Typically, a 18-55mm lens can either be f3.5 to f5.6 or f4 to f5.6. If you try to go at f3.5 and there is one lense in your kit that is limited to f4, you’ll get an error message. Same thing goes if you have one lens that is zoomed to a point where a higher f-stop value is not available
  • Some cameras are missing (not all)
    • Make sure that your computer sees the cameras from Windows Explorer. If you don't see them all, you might have to perform the tricks explained in this article: https://www.thewindowsclub.com/fix-not-enough-usb-controller-resources-error-on-windows-10
  • All cameras are missing
    • Restart Xangle Camera Server
    • Restart the computer
    • Make sure that no other apps taking the control of the cameras on your PC (EOS Utility, etc)
    • (Pi) Restart the Raspberry Pi’s
    • (Pi) Make sure that the microSD cards are flashed with Xangle Client
    • (Pi) Check your DHCP table to figure out if the Pi’s are visible on the network (see troubleshooting Raspberry Pis)
  • Camera shows an f-stop value of 0
    • Make sure that your lens is properly attached to the body
  • A camera doesn’t power on after switching it from off to on, even when it’s connected
    • You might need more power. This is a typical symptom that happens when you start to have too many cameras / computers / lights on a single drop. Try to add additional power drops
  • Cameras keep going off
    • Make sure that “auto-power-off” is disabled from the camera settings
    • If you're using USB-hubs, make sure that they are powered
    • Over the years, we've had numerous problems using the USB-cables that come with the Canon cameras. We've been using Startech cables for a few years and it solved the problem for us
    • Try to avoid to have your usb cables too close to the power ones. We usually run two sets of cables with at least 6" between the two (usb, power)
    • If your rig is underpowered, it is very likely that the system is going to be unstable
  • All cameras are connected, but some files are missing after triggering
    • This is a typical symptom of an under-powered system. Try to separate your rig into multiple drops. We’ve seen this happen a lot with systems running with strobes. By simply having the strobes on a different power drop than the cameras, the problem is usually fixed
    • It’s been reported to us that this happens sometimes when using a USB-2 port
  • One camera is missing
    • Check if the missing camera is powered (disconnect usb and press the shutter button)
    • Try with another USB cable
    • Make sure the USB hubs are delivering enough power
    • Make sure the Raspberry Pi is running properly (lights blinking, proper image version, sd card inserted)In any case, switching cables from one camera to another is very insightful to determine what's causing the issue