Work

The devices are running. Can they hear each other?

A powered-on machine does not guarantee its data reaches the right place. I find where the connection breaks and make communication between devices, networks and applications understandable again.

Different devices, one conversation.

A switch sends data to the right port within a network. Sensors, controllers and displays share that conversation. When one falls silent, I check the cable, port and device settings in order, rather than change everything at once.

My part: trace the silent connection.

Illustrative explanation, not a customer network or a verified field outcome.

Connection interrupted

Look into the field. Keep the door controlled.

A router connects different networks. Remote support needs a secure path with only the necessary access. When it fails, I separate the field side from the remote side and check addresses, access rules and the session.

My part: narrow the access path and locate the broken step.

Illustrative explanation, not a customer network or a verified field outcome.

Connection interrupted

Both sides speak. Different languages.

One device’s data may not match the format another system expects. A gateway translates between them. I map what goes where and in which order, checking that a number keeps its meaning on both sides.

My part: verify that both systems understand the same data.

Illustrative explanation, not a customer network or a verified field outcome.

Connection interrupted

Follow the evidence. Then change something.

The cause may be a cable, a setting or a layer above. I reproduce the symptom, break the path into smaller checks and compare findings. After a change, I check communication again and explain what happened clearly.

My part: choose the next check, rather than the next guess.

Illustrative explanation, not a customer network or a verified field outcome.

Connection interrupted

Open the technical detail

01 / Representative technical scenario

Modbus RTU / TCP integration

Context

Connecting a serial Modbus device to an IP-based system.

Approach

Check electrical interfaces, communication settings, device addresses and register maps.

Technical considerations

RS-485 wiring, client/server roles, TCP sessions, timing and exception responses.

02 / Representative technical scenario

PROFINET gateway diagnostics

Context

Investigating communication between an industrial network and a protocol gateway.

Approach

Review topology, device naming, addressing and the gateway configuration.

Technical considerations

Layer-by-layer checks and protocol compatibility before changing settings.

03 / Representative technical scenario

Secure industrial remote access

Context

Maintenance and diagnostics without exposing control devices directly to the public internet.

Approach

Define the access path, permitted users and devices, VPN endpoint and management flows.

Technical considerations

Segmentation, least privilege, firewall principles, authentication and access approval.

04 / Representative technical scenario

Serial devices over Ethernet

Context

Making a serial device reachable through an IP network.

Approach

Match the electrical interface, serial parameters, connection mode and expected TCP behavior.

Technical considerations

RS-232/422/485, pinout, speed, parity, two/four-wire operation and idle timeouts.

The problem can be complicated. The explanation doesn’t have to be.

Let’s find out what happened. Restarting is still an option.