Guide · Canon
Canon Camera Connect troubleshooting, and what CCAPI is
Canon’s wireless setup is the odd one out. Besides the official app, there’s a published HTTP interface called CCAPI and a proprietary EOS channel that’s been around for years. Knowing which one you’re on speeds things up.
Check these three first
The connection slots may be full
Canon bodies save every pairing as a connection setting, and there are only so many slots. A new phone, a reinstalled app or a friend trying the camera each takes one.
Once they’re full, new connections just fail, and the camera won’t say why. Delete old entries in the wireless menu or reset the communication settings. On Canon, start here.
Bands and hotspots
The EOS M series and EOS RP only broadcast on 2.4 GHz. Some newer R bodies offer 5 GHz if you pick it in the menu. A phone locked to 5 GHz may not see the camera at all.
The camera’s hotspot has no internet, so Android will drift back to mobile data. Tell it to stay connected, and turn off VPN and Private DNS.
Original or resized
Camera Connect asks about size when you transfer, and the default is usually a compressed JPEG. Original size and CR2 or CR3 files have to be chosen by hand, and not every body offers RAW. Check before you send a batch, not after.
What CCAPI is
CCAPI, short for Camera Control API, is Canon’s published camera-control interface over HTTP. Third-party apps can use it to pull live view, change settings and fetch files.
Which bodies have CCAPI, and how you switch it on, depends on the model and firmware. Check the menu on yours.
The other route is Canon’s proprietary EOS channel, which EOS Utility tethering uses. It reaches more bodies, especially DSLRs and EOS M cameras that came out before CCAPI.
So newer bodies may work either way, and older ones usually only over the EOS channel. Zlens carries both on Canon and follows the model profile to the one that works.
Supported cameras
Zlens has 18 Canon model profiles.
- EOS R5 Mark II, EOS R5, EOS R6 Mark II, EOS R6
- EOS R7, EOS R8, EOS R10, EOS R, EOS RP
- EOS 5D Mark IV, EOS 5D Mark III, EOS 5DS R
- EOS 6D Mark II, EOS 7D Mark II, EOS 90D, EOS 80D
- EOS M50 Mark II, EOS M6 Mark II
A profile describes what the protocol allows. It isn’t a hands-on test, and per-model results will be published at launch.
Checklist
- Delete unused connection settings on the camera, or reset the communication settings, to free a slot.
- Forget the camera’s Wi-Fi on the phone and remove the old camera from the app, then pair once from scratch.
- Grant location and Nearby devices. Without them Android can’t scan for the hotspot or open a Bluetooth link.
- Set Camera Connect’s battery use to unrestricted so it isn’t frozen when the screen locks.
- Confirm the band, and set that network to stay connected without internet.
- Turn off VPN and Private DNS. On some routers, turn off MAC address randomisation as well.
- Turn off auto power-off on the camera, especially for long transfers.
- Update the firmware. Canon ships a fair share of wireless fixes that way.
How Zlens handles it
On Canon, Zlens carries both the CCAPI and EOS Wi-Fi paths and picks the one the model profile says will work. Canon menus run deep, so on first connection Zlens shows the menu path for your model.
RAW files come across shot by shot or in batches, even with the screen locked. Zlens talks to the camera over published protocols. It doesn’t break encryption or touch the firmware.
Zlens isn’t out yet. The download link will go on the home page once it’s ready. Menus in the official apps change with firmware and app versions, so go by the menu on your camera.