Open a camera-power dossier before drawing branches
A camera symbol is not yet a power requirement. Start a dossier with the exact camera, interface and frame-grabber identities. Attach the document that identifies the selected power path, including its revision and configuration. If that path is undecided, keep the entry open instead of assigning an assumed supply input.
El A3 Camera Link description [1] identifies Camera Link as a hardware connection specification between cameras and frame grabbers. It also describes Power over Camera Link as allowing a frame grabber to power a camera through the Camera Link cable. Neither statement means every camera uses that arrangement or that any two selected devices are compatible.
Does this camera belong in the independent 24V load list?
Answer from the selected-device documents. If an interface supplies camera power, show that relationship beside the relevant upstream load entry. If a separate supply input is used, retain the requirement for that input. When multiple arrangements are possible, record which one the project actually proposes.
The following is an original inventory aid, not a connection instruction:
| Documented camera-power situation | Inventory treatment to verify | Evidence still needed |
|---|---|---|
| Separate camera input selected | Give that input its own requirement entry | Exact input specification and selected operating mode |
| Interface-powered arrangement selected | Link the camera to the supplying device entry | Both device documents and the supported arrangement |
| Several supported arrangements listed | Identify the selected option before totaling anything | Controlled project configuration |
| Supply path unknown | Keep the camera requirement unresolved | Equipment identification and responsible supplier response |
The objective is one traceable accounting path for each device. The table deliberately supplies no connector pins, cable rating or camera demand.
Put the inspection event beside the power path
Ask the controls team to describe one real inspection cycle: image acquisition, illumination, result handling and any commanded movement. Keep those events beside the camera dossier. A list of four equipment classes cannot show whether the selected modes overlap; the actual sequence can.
Attach the lighting controller, I/O and motion-device references to the events they serve. Do not label an item “pulsed,” “noise-sensitive” or “high inrush” without a supporting device record. An unknown behavior remains a question for that exact equipment, not an allowance borrowed from a similar machine.
What if lighting coincides with image acquisition?
Record the commanded overlap and the relevant operating modes. If an image defect is reported, preserve the camera settings, acquisition event, lighting command and machine state together. That record is an investigation starting point; it does not establish that the power supply caused the defect.
For the electrical review, ask where load-end voltage will be observed, during which event, and against which documented equipment criterion. Record the source-to-load route and the project-authorized return and grounding concept. Noise or voltage-drop questions need identified observations and equipment limits; this article provides no universal wiring change, filter selection or numeric limit.
Keep image-quality evidence separate from power acceptance
EMVA’s introduction [2] identifies EMVA 1288 as a standard for measuring and presenting machine-vision sensor and camera specifications. That is measurement context, not approval of a 24V cell topology.
Maintain two linked records: the image-quality requirement and the electrical operating requirement. They can refer to the same inspection event while answering different questions. A camera specification does not determine another device’s supply demand. An acceptable electrical observation does not by itself accept the inspection algorithm or the image result.
When the records disagree, preserve the equipment revision and test condition rather than rewriting the requirement to match a convenient outcome. This keeps a later camera or lighting change from inheriting an acceptance result collected under a different configuration.
Place service boundaries around the actual equipment
Only now discuss which items can be reviewed together. Use a boundary note to say whether a group is merely an accounting group, a proposed physical branch or an acceptance-test group. Those are different decisions.
For each candidate boundary, resolve four questions:
- Which camera and interface must remain identifiable during service?
- Which device document owns the cable, connector and return requirements at the boundary?
- Which startup or reset event requires a new acceptance record?
- Which process action must remain inhibited while a required condition is unresolved?
The result may be a revised branch proposal, a different service procedure or an additional acceptance record. A qualified project team must approve the physical implementation and protective measures. Do not disconnect protective earth or improvise live wiring to investigate an image problem.
Related sizing guide: 24V DIN rail power supplies for automation panels
Use this guide for adjacent sizing context once the actual device inventory and events are defined. It cannot supply missing camera-specific inputs.
Bring one complete dossier to the supply enquiry
The WEHO catalogue identifies the Fuente de alimentación conmutada de salida única NDR dinrail 240W CA a CC as product 1514. Treat it as a candidate to investigate, not an already-qualified machine-vision supply.
Send the camera-power inventory, event relationships, enclosure conditions, required documents and unresolved requirements together. Request an answer tied to the proposed model and actual configuration. The catalogue identity does not establish transient performance, grounding arrangements, certification coverage or compatibility with the chosen camera and lighting hardware.
Can one supply serve all four review groups?
The four equipment groups do not imply four supplies. Nor does a combined wattage settle their architecture. Evaluate the documented power paths, operating conditions, service expectations and acceptance requirements of the proposed configuration. Keep a proposed shared arrangement provisional until those questions are closed.
What changes when a replacement camera is introduced?
Reopen its power-path entry and interface assumptions, then compare the relevant operating events and acceptance conditions. Do not inherit a Power over Camera Link assumption merely because the outgoing camera used it. Keep the before-and-after equipment references with the disposition of every changed requirement.
Close the dossier at the inspection result
A reviewer should be able to trace a physical camera to its documented source of power, the associated illumination event, the functional acceptance record and its service boundary. Use matching equipment identities across the device list, controlled drawing and test records.
Related controls guide: 24V DIN rail power-supply sizing for PLC control panels
This guide adds adjacent controls-sizing context. The cell-specific decision remains in its dossier: no assumed camera power path, no duplicate load entry and no unresolved event hidden by a tidy block diagram.
Reference URLs
Exact source addresses for the attributed statements above:
- https://www.automate.org/vision/vision-standards/vision-standards-camera-link
- https://www.emva.org/standards-technology/iso-24942/introduction/
