
Harmonic distortion from nonlinear loads: heat, trips, and confused meters
Drives, LED drivers and IT supplies draw current in pulses. Harmonics heat neutrals and transformers, and a 60 Hz clamp can hide the thermal story.
Articles, guides and engineering notes — technical writing from the studio.
Technical articles — view all

Harmonic distortion from nonlinear loads: heat, trips, and confused meters
Drives, LED drivers and IT supplies draw current in pulses. Harmonics heat neutrals and transformers, and a 60 Hz clamp can hide the thermal story.

Electrical thermography as evidence, not a colourful gallery
A hot spot is a temperature difference under a named load and emissivity. The question is why it is hot and what fails next — not the prettiest palette.

UPS behaviour under the load you actually have
Ride-through, bypass and transfer follow the load shape you run. A factory resistor bank does not prove what the process will see in a sag.

Packet loss, latency and jitter: three numbers, three different jobs
Loss drops frames. Latency is path delay. Jitter is how that delay moves. Calling the network slow hides which of the three the process actually feels.

EMI, SNR and communications: when the cable is a poor antenna
Signal-to-noise is why a link that certified last year throws errors beside a drive. Treat the electrical environment as part of the channel, not folklore.

OT and IT on industrial Ethernet: two definitions of “up”
IT counts tickets and pings. OT counts completed cycles. The same switch can satisfy one team and starve the other unless queues and ownership are written.

What Division 25 actually coordinates on a project
Division 25 is the integration spec: who owns points, networks, sequences and interfaces among mechanical, electrical and communications — not a second.

From sequence of operation to control architecture
A written sequence is intent. Architecture decides which controller executes which clause, what happens on network loss, and which alarm requires an operator.

BAS, OT and network coordination in a shared closet
Building automation, plant Ethernet and corporate IT often share a rack without sharing rules. The closet is an interface. Treat it as one, or the quietest.

When an engineering automation is worth building
If an engineer repeats the same transformation every week, a small tool can earn its keep. If the rule changes every job, a spreadsheet and a checklist stay.

When the network problem is electrical
CRC on a switch is not always a cable. Sag, bonding, noise and a shared tray can raise a network ticket. Split the file: packets, then volts, then the coupling.

Engineering at system interfaces: where the drawing stops being true
Persistent faults live on a seam: power and control, OT and IT, Divisions 23 and 25, CAD and model. Name the seam, the owner and the test, or both sides look.
Next
Have a technical problem that crosses systems?