Device Name
UUID: FFAC0C52-C9FB-41A0-B063-CC76282EB89C
Send a device name to the camera (max. 32 characters).
The camera will display this name in the Bluetooth Setup Menu.
Protocol Version
UUID: 8F1FD018-B508-456F-8F82-3D392BEE2706
Read this value to determine the camera's supported CCU protocol version.
NOTE Encrypted characteristics can only be used once a device has successfully
bonded or paired with the Blackmagic Camera. Once a connection has been
established, any attempt to write to an encrypted characteristic will initiate bonding.
For example, writing a 'Camera Power On' (0x01) message to the Camera Status
characteristic.
Once bonding is initiated, the camera will display a 6-digit pin in the Bluetooth Setup
Menu. Enter this pin on your device to establish an encrypted connection. The device
will now be able to read, write and receive notifications from encrypted characteristics.
Blackmagic SDI and Bluetooth Camera Control Protocol
Version 1.5
If you are a software developer you can use the Blackmagic SDI and Bluetooth Camera Control
Protocol to construct devices that integrate with our products. Here at Blackmagic Design, our
approach is to open up our protocols and we eagerly look forward to seeing what you come up with!
Overview
This document describes an extensible protocol for sending a unidirectional stream of small control
messages embedded in the non-active picture region of a digital video stream. The video stream
containing the protocol stream may be broadcast to a number of devices. Device addressing is used
to allow the sender to specify which device each message is directed to.
Assumptions
Alignment and padding constraints are explicitly described in the protocol document. Bit fields are
packed from LSB first. Message groups, individual messages and command headers are defined as,
and can be assumed to be, 32 bit aligned.
Blanking Encoding
A message group is encoded into a SMPTE 291M packet with DID/SDID x51/x53 in the active region
of VANC line 16.
Message Grouping
Up to 32 messages may be concatenated and transmitted in one blanking packet up to a maximum
of 255 bytes payload. Under most circumstances, this should allow all messages to be sent with a
maximum of one frame latency.
If the transmitting device queues more bytes of message packets than can be sent in a single frame,
it should use heuristics to determine which packets to prioritize and send immediately. Lower priority
messages can be delayed to later frames, or dropped entirely as appropriate.
Developer Information
145