Save camera settings to PC
Download the camera’s current settings to a file on the host PC.
The file is written to a camera_settings/ directory relative to the
server’s working directory — not a caller-supplied path. There is no
save_path for this endpoint (unlike the SD card endpoints); the optional
filename only names the file. The response data.path reports where it
landed. A typical file is CUMSET.DAT, around 180 KB.
Completion also emits a downloadComplete SSE event.
Requires the camera to allow it
The SDK only permits this when the camera reports
camera-setting-save-enable as 1 and camera-setting-save-read-state
as 0 (Idle). Read those via getAllProperties before calling — a 400
here usually means the camera is refusing, not that the request was
malformed.
The camera will not enable it without recording media present. On bodies
with two card slots this means slot 1 specifically: an ILCE-7M4 with a
card in slot 2 only reports camera-setting-save-enable: 0 and rejects
the call.
Path Parameters
Camera identifier (e.g. D10F60149B0C)
Body
Settings filename (e.g. CUMSET.DAT)
Response
Settings file saved
Generic envelope returned by most camera operations. The shape of
data varies per endpoint — most operations return an empty or
null data; operations that return structured data document a
specific shape. SDK-generated types can treat data as an opaque
map for generic endpoints.

