ABB IRC5 integrated vision camera setup: ports, IPs and I/O errors

An IRC5 compact, a vision camera, a DSQC1030 I/O unit and four Ethernet ports on top of the controller: the hardware list is short, but the manual spends little time on those ports, the camera login dialog wants credentials nobody printed on the device, and the first output write comes back as "could not set I/O value. C0048407: Operation rejected by the controller safety access restrictions mechanism." None of that is broken hardware. This guide covers the whole first integration: which port each device uses, where every address comes from, what the login wants, how to clear C0048407 in a few minutes, and the standalone smart-camera route when Add Sensor will not list your camera.

Which of the four ports each device uses

Four RJ45 sockets sit on the controller's connectivity panel, and each has exactly one job. The camera and the DSQC1030 both belong on the WAN network, your laptop on the service port, the plant on the LAN port, and nothing at all on the axis port.

The WAN port is the one that matters for this job. At delivery the controller holds 192.168.0.80 with mask 255.255.255.0 on that port and runs a DHCP server for whatever plugs into it — which is why the DSQC1030 was recognized the moment you connected it. The camera joins the same network and is addressed the same way, so you never type an address into either device.

The service port is fixed at 192.168.125.1 with the same mask; give your laptop 192.168.125.100 and RobotStudio finds the controller over that lead. The LAN port is the plant-facing side and carries whatever subnet your PLC expects, set as described below.

Wire the camera and I/O module in five steps

You need a five-port industrial Ethernet switch, three Cat5e patch leads and a 24 V feed. The DSQC1030 and most integrated vision cameras run from the same 24 V rail as the valve island.

1. Main switch off. Mount the switch near the controller and run one patch lead from the WAN port to it.
2. Connect the DSQC1030 and the camera to the switch, and power both from 24 V.
3. Main switch on. Wait for the boot to finish; the controller detects the DSQC1030 on the WAN network by itself.
4. On the pendant, open the configuration editor and define the digital signals on the unit — DSQC1030 I/O configuration in RobotStudio walks the same dialogs from a desk PC.
5. Open the vision tab, press Add Sensor, and pick the camera once it appears in the list.

Where every IP address comes from

Three networks, three rules:

• Service: fixed at 192.168.125.1 by the system; your laptop takes 192.168.125.100.
• WAN: the controller at 192.168.0.80 is the DHCP server, and it hands the DSQC1030 and the camera their addresses. Write the addresses down from the sensor list once Add Sensor finishes.
• LAN: the controller's plant address, set in Control Panel → Configuration → Communication → IP Setting. That is where the robot gets the address your PLC expects — not on the service port, which you cannot change.

The camera address is the only one you may want to move. The Network Settings dialog on the camera changes it, and Add Sensor re-finds the camera after the change.

The Add Sensor username and password

The login is the camera's, not the controller's. Every camera for this option ships with three accounts — admin, operator and monitor — and the factory admin password sits on the same page as the account list, in the Application manual – Integrated Vision (3HAC044251). Log in as admin with that password once, then change it in the camera's own user administration before the cell ships. Write the new one in the cabinet documentation pocket; a camera you cannot log in to is a camera you cannot re-aim.

One limit to know before you type anything: Add Sensor lists only the camera families the Integrated Vision option supports, and that list is in the same manual. A general-purpose smart camera on the correct network still will not appear in it, and no password changes that. That is the moment to take the standalone route below.

Clear the C0048407 safety access rejection

The module was recognized instantly, so the wiring and the network are fine — the write was refused, not lost. The safety access mechanism gates signal writes from the pendant by user access level and operating mode, and on a fresh controller both gates are closed. Open them in this order:

1. Log in on the pendant with an account in the engineer group; your integrator set that password at delivery.
2. Grant write access when the pendant asks for it after login.
3. Turn the mode selector to auto and press motors on.
4. If the write still bounces, a running RAPID task owns the signal. Stop the task, write the value, then restart the task.

The same mechanism also refuses some configuration edits, which is why the error text names safety rather than the network. A DSQC1030 that reports an internal error after a RobotWare upgrade is a different problem; the DSQC1030 internal error fix after a RobotWare change page covers that one.

Do you need to configure the fieldbus adapter?

No. The DSQC1030 talks to the controller across the WAN network with no fieldbus setup, and a vision-only cell needs nothing more from that adapter. Configure it only when a plant PLC or an MES must read the same signals; then define it under Industrial Network in the same configuration editor. Until then, an unused adapter can stay exactly as delivered.

When Add Sensor will not list your camera

If the camera in your hand is not one of the supported families, stop fighting Add Sensor and run the camera standalone: it does its own inspection and hands the robot a verdict. The cleanest bridge is digital I/O — a DSQC1030 output triggers the camera, an input reads pass or fail, and the robot never parses an image. In multi-part cells, stream over Modbus/TCP instead: the vision controller Modbus communication guide shows the register pattern, and machine vision for PLC programmers covers the ladder side. For the wider architecture, building a robot vision system for object location and gripping is the companion piece.

Two details carry most of these cells: the trigger wiring, settled in do I need a camera GPIO cable for image acquisition?, and the ready handshake that stops the robot grabbing before the camera is warm — the failure mode behind smart camera misses first images after load.

For a tray-sized field of view at arm's reach, a compact smart camera with its own lens does the whole job:

The MV-SC5060XM-08M-WBN is a 6 MP mono smart camera with an 8 mm focal length lens on an M12 mount and a GigE interface. Two lighter options cover smaller parts and color checks:

The LS-SMC-0063 is a 1.6 MP smart camera at 60 fps with a 16 mm lens and built-in white light. The MV-SC6050C-08M-XBN is a 5 MP color model with a multi-color light source and an 8 mm focal length. On Fast Ethernet, the MV-SC3050XC-16M-ATN-H is the 5 MP color vision sensor of the same class. Both Fast Ethernet and GigE reach 100 m per run, so cabinet distance stays a cabling choice, not a camera choice. Browse the smart cameras category or the smart camera finder to pair one with lens and stand.

Worked example: stand height, lens and pixels for a pick tray

Say the robot picks from a 300 × 240 mm tray with ±1 mm tolerance. Plan the camera before the lens order:

• Pixels: ±1 mm picking wants about 0.25 mm per pixel, so sub-pixel edge finding keeps the center error near a pixel. Across 330 mm of view that is 330 / 0.25 = 1320 pixels; a 1.6 MP camera (1440 × 1080) clears it.
• Sensor: a 1/2.9-inch format works out to a 5.5 mm diagonal, about 4.4 × 3.3 mm of silicon — close enough for lens math.
• Lens: focal length = working distance × sensor width / field of view. At 650 mm: 650 × 4.4 / 330 = 8.7 mm, so an 8 mm lens. Coverage at 8 mm: 4.4 × 650 / 8 = 358 mm, the tray plus margin, and 358 / 1440 = 0.25 mm per pixel, right on target.

The mount window matters more than the exact lens: between 550 and 700 mm the 8 mm lens covers 4.4 × 550 / 8 = 303 mm up to 4.4 × 700 / 8 = 385 mm, staying at or under 0.27 mm per pixel. The LS-MNT-0040 is a machine vision camera stand with a 700 mm height and a 400 × 450 mm base. A 650 mm camera height sits inside that window with room for the bracket.

A 16 mm focal length at the same height covers 4.4 × 650 / 16 = 179 mm at 179 / 1440 = 0.12 mm per pixel — four times finer, under half the tray. That is the trade: coverage against accuracy.

For parts on a belt rather than a fixed tray, conveyor tracking camera placement relative to the robot settles where this camera should sit. After the first picks, expect one frame-alignment pass: when parts land rotated or mirrored, fixing rotated camera axes in RAPID names the frame swap, and robot cell vision recalibration with one reference target is the routine that keeps the cell honest over weeks.

Checks before you run the cell

• Write an output on the pendant and read 24 V on the matching DSQC1030 terminal with a meter — that proves the whole I/O path, not just the software write.
• Add Sensor shows a live image, and the camera host name matches the RAPID sensor name.
• The camera admin password no longer matches the manual, and the new one is in the cabinet documentation pocket.
• Camera and motor cable runs sit in separate trunking; the WAN switch is not in the motor loom.
• One image per trigger at production speed, before the first automatic cycle.

When the cell grows past one camera and one tray, start the camera step of the configurator to line up camera, lens and stand together, or ask us through the contact page about the layout.