/camera add

/camera add <save_as> [camera_model] [sensor_preset] [pixel_pitch] [read_noise]

Saves a named camera profile (pixel pitch, resolution, and optionally read noise) for reuse with /maxexposure and /subexposure, so you don’t have to look up or retype it every time — especially handy if you own more than one camera body.

Recommended: keep the first save simple, then finish with /camera edit. Discord submits this command the instant you press Enter — save_as is the only required field, so hitting Enter partway through picking a camera_model or typing specs submits immediately with just that name, not what you meant to enter next. The reliable flow: /camera add save_as: "My ASI533" camera_model: [pick from autocomplete] (just those two — this alone fills in verified pixel pitch and resolution), then use /camera edit to add read noise or adjust anything else. Its dropdown-then-form flow can’t accidentally half-submit the way a slash command with several optional fields can.

Usage: /camera add save_as: "My ASI533" camera_model: [pick from autocomplete] for a known camera body — this fills in verified pixel pitch and resolution (needed for a future field-of-view feature) in one step, more precise than a generic sensor_preset, and for the three ZWO astro cameras currently listed, also fills in a documented read noise figure at a specific high-gain setting — the confirmation message after saving says which. If your exact model isn’t listed, use sensor_preset: [pick from autocomplete] for a quick approximate pixel pitch instead, or pixel_pitch: 5.94 if you know the exact value yourself — precedence is pixel_pitch > camera_model > sensor_preset when more than one is given, and the same read_noise > camera_model precedence applies for read noise. Add read_noise: 1.5 yourself (in electrons, from your camera’s own spec sheet, SharpCap’s sensor analysis, or your own measurements at your usual gain) to override the camera_model figure or provide one where none exists — the three consumer DSLR/mirrorless bodies in camera_model have no read noise figure at all, since manufacturers don’t publish one the way dedicated astro camera makers do.

Both camera_model and sensor_preset autocomplete as you type, pulling from a shared database rather than a fixed list — so new camera models or presets added there show up immediately, without needing a bot update.

save_as autocompletes your existing saved cameras as you type — picking one updates that profile in place rather than creating a duplicate, no need to delete and re-add it — and only touches the fields you actually provide: leaving out any field on a later save keeps whatever was already saved for it, so you can add or change one thing without needing to re-state everything else.

Also see /camera edit for a guided, dropdown-and-form way to update an existing profile (including its resolution), showing its current values instead of requiring you to know or retype them.

Focal length and aperture stay as fresh inputs on /maxexposure each time, since those change with whatever lens you’re using far more often than the camera body itself does.

Parameters

Name	Required	Description
save_as	Yes	A label to save this camera under, e.g. 'Canon R6' or 'Wide-field rig'
camera_model	No	Pick a known camera body for verified pixel pitch + resolution (overrides sensor_preset)
sensor_preset	No	Pick a generic sensor type (approximate pixel pitch shown in the label)
pixel_pitch	No	Exact pixel pitch in microns, if you know it (overrides camera_model/sensor_preset)
read_noise	No	Camera's read noise in electrons at your usual gain, for /subexposure's precise mode