Camera attributes greyed out: why controls lock and the fix

You open the camera's page in your acquisition software and nearly every attribute is greyed out. The trigger edits; a raw exposure slider sometimes survives; gain, white balance, ROI and pixel format sit disabled and refuse every click. This page is for anyone integrating a camera — most often an older IEEE 1394 DCAM model, but the same symptom appears on GigE and USB3 cameras after a tool or firmware change. You will find the six causes in order of probability, a quick test for each, the fix that works for each, and the documented last resort when the camera itself is the limit.

What a greyed-out control actually means

The configuration tool does not decide which controls to offer. It renders what the camera declares, through one of two mechanisms.

An IEEE 1394 camera speaks the DCAM (IIDC) protocol. The standard reserves a camera-control register block and gives each feature — brightness, gain, shutter, trigger and the rest — its own register pair with a presence-inquiry bit. Firmware that never sets that bit leaves the tool nothing to draw: the control renders greyed, or not at all.

A GigE Vision or USB3 Vision camera serves a GenICam feature description instead: an XML description read from the camera's own firmware, listing every feature with an access mode. Absent from the description means absent from the tool; read-only in the description means visible but not writable.

So a greyed control is a message from the camera, not a fault in the software: this feature is not declared, or it is not writable from your current session. The six causes below cover both.

The causes, in order of probability

1. The feature is not in the declared map

Most common on 1394 cameras whose firmware declares only the trigger block: the camera streams, the trigger edits, everything else is stone grey.

Test: open the feature-list view of your tool and count the writable entries against the control list on the camera's data sheet. Two writable entries against a sheet that lists eight controls is a declared-map problem, not a settings problem.

Fix: ask the camera maker whether a firmware release exposes the missing features in a DCAM-compliant way, or whether it documents a register-level utility for the model. If neither exists, the map is the limit — no reinstall of the tool or driver will grow it, and the honest fix is a newer camera, covered below.

Modern cameras hide the same trap in reverse: the feature exists in the description under a name you did not expect. Exposure has shipped as ExposureTime, Exposure and Shutter across camera families, so run a discovery pass before you conclude a feature is absent — GenICam exposure feature discovery for missing attributes shows the sweep. If the one editable control is the trigger and you need it live, hardware trigger source not detected: check GenICam line settings is the companion check.

2. Another application holds the camera

A GenICam device grants write access to one client at a time; a second session connects read-only, which the tool paints grey. The holder can be obvious — a running inspection — or invisible: a service, a hung process after a tool crash, or the settings window's own live preview, which holds the device like any other client would.

Test: close every program that can touch the camera, then re-enumerate. Controls that turn editable under a single client were an access-state lock, and check the camera access state walks the diagnosis when the holder is less obvious.

Fix: keep exactly one write client for the camera and give it a machine of its own — a vision controller on the line rather than a shared office bench PC.

3. The acquisition is running

Many features accept writes only while the stream is stopped. Pixel format, ROI, packet size and frame rate are the usual suspects; exposure and gain usually write live.

Test: stop acquisition and look again. Entries that turn editable only while stopped were stream-state locks, not broken drivers.

Fix: order every set-up as stop, configure, start, and reserve live tuning for exposure and gain. Runtime camera parameter control: exposure and white balance live shows what a live session can reach.

4. Driver or feature-description mismatch

After a firmware update or a tool reinstall, the software can read the camera through a stale feature description or a driver built for a different family. The symptoms are greyed features, features that error on write, and reads that fail outright.

Test: read the firmware version and the feature-description version from the camera and compare both against the vendor's release notes. A description version that lags the firmware explains controls that vanished after an update.

Fix: install the driver and firmware from the camera vendor or its distributor, and pair the versions as the release notes state. GigE camera failed to read parameter: fix the driver mismatch covers the failed-read variant; the camera firmware update workflow is the safe update path.

5. Firmware older than the feature set

Vendors add features in firmware without a hardware change: the camera can do the control, but the shipped map predates it.

Test: compare your firmware version against the release notes for the model. A note that adds a feature in a version higher than yours is the answer.

Fix: run the vendor's documented update once, re-enumerate, and count writable features before and after. Keep both counts — they are your proof the update took, and the after-count feeds the section below.

6. The control exists only at register level

Rarest, and specific to 1394-era hardware: the vendor implemented a feature without declaring it in a DCAM-compliant manner, so the presence bit the tool reads is never set. Only the vendor's own documented register utility can reach such a control; there is no generic map worth writing against.

Worked example: the brightness you can still recover

A locked map rarely leaves you nothing, because exposure stays writable even when the rest is grey. The arithmetic tells you how far exposure alone carries you, and when gain must close the rest.

Setup: an 8-bit mono image with a histogram mean of 31 out of 255 and a target of 235. ExposureTime is writable at 250 µs. The part moves 50 mm/s and the pixel scale is 0.05 mm per pixel, so motion blur must stay under one pixel: exposure below 1 ms.

Check it line by line. Exposure ×4 lifts the mean to 31 × 4 = 124 and the blur to 50 mm/s × 1.0 ms = 0.05 mm, exactly one pixel at the given scale. The remaining factor 7.6 / 4 = 1.9 belongs to gain: 20 × log10(1.9) = 5.6 dB, and 6 dB is a ×2 in any linear analog stage, so the estimate is consistent. The predicted mean 31 × 4 × 1.9 = 235.6 lands on the 235 target, and a 1 ms exposure costs nothing against the 33.3 ms frame period at 30 fps.

Decision: exposure plus gain land the brightness using only the two writable controls; what stays lost is white balance, gamma and ROI, which the locked map does not hand over. If even exposure is locked — a trigger-only camera — skip the arithmetic and go to the next section. Once exposure is writable you can automate the same bounded correction loop; software auto exposure for a raw camera: the bounded loop is that controller in code.

When the honest fix is a different camera

If the declared map lacks controls your inspection needs and no vendor firmware adds them, replacing the camera is the fix, not a workaround. A current camera speaks GigE Vision or USB3 Vision and serves its complete GenICam description, so every declared feature is editable in the tool and scriptable in code — the fault this page describes cannot recur on the control side.

Before ordering, open the feature list and count the writable entries against your control list; we run that check with you as part of the expert support that comes with every order. As a reference point for a small inspection, the MV-CU020-90GC is a 2.5 MP color GigE camera with a 1/1.7-inch global-shutter sensor on a C-mount.

For the bench, USB3 covers a wide span of resolutions: the MV-CH120-11UC is a 12 MP high-speed camera with a 1.1-inch global-shutter sensor on a C-mount, while the MV-CS200-10UM steps up to 20 MP mono on a 1-inch rolling-shutter sensor.

Keep it fixed

Three habits prevent a repeat.

1. One client owns the camera. A dedicated vision controller does that by construction: the MV-VC3301H-128G66, for example, pairs an Intel Core i3 processor with four built-in light channels, five or more LAN ports and 8 GB of memory, and ships with a VM6200Pro license so the acquisition stack and the camera controls live in one place.

2. Pin driver, feature-description and firmware versions together in the build sheet, and move all three as one unit when an update lands.
3. Re-run the writable-feature count after every change to tool, driver or firmware. A count that drops is your earliest warning that a map has closed.

The same symptom outside vision

A locked control is a family of fault, not a vision-only one. On the controller side it appears in why RSLogix 5000 alarm fields grey out and how the edit lock fixes it, and motion axes do the same: Studio 5000 Kinetix 5700 greyed-out motion controls fix. In every case the software renders what the device or project declares, so the fix lives at the declaration or access layer — the same principle as the camera causes above.

Where to go next

Work the causes in order: enumerate the map, free the access state, stop the stream, match driver and description, update firmware from the vendor. If step one shows a map too small for the inspection, choose a camera whose declared map covers your controls: browse the area scan cameras, filter in the camera finder, or configure a camera step by step. The systems topic page collects the rest of the integration checks, and if a legacy 1394 camera is the question, contact us with the model and the writable-feature count you measured — that one number decides between firmware, the vendor's register tool and replacement.