What Happened to NH Research — and What It Means If You Still Run a 9300

Replacing an instrument · 3 min read · 12 cited facts

If you have searched for an NH Research model number recently, you will have noticed something odd: the manufacturer is barely in the results. Type in a 9300 and you get resellers, rental houses and secondary-market listings. The brand's own domain redirects to a general NI page that does not name the model at all.

This is not a search problem. It is what an acquisition looks like from the outside, and it has practical consequences for anyone still running the hardware.

The short version

• NH Research was acquired by National Instruments, which was subsequently acquired by Emerson
• nhresearch.com now redirects to a general ni.com electric-vehicle test page
• That page markets EV test broadly and does not list the 9300, 9200 or 4700 by model
• Searches for those model numbers surface resellers and rental firms above the manufacturer
• For the 9200 and 4700 in particular, the manufacturer is effectively absent from results

If you are still running the hardware

Nothing has stopped working. But two things are worth doing now rather than at failure: archive whatever documentation you already hold locally, because it is easier to keep a PDF than to find one later; and establish what your support and calibration path actually is, in writing, rather than assuming continuity through two acquisitions.

If you are planning a replacement

The trap in replacing a battery test system is matching total system power and missing the channel architecture. Pack and module programmes are usually throughput-bound rather than power-bound — a replacement with identical kW and half the channels does not deliver the same lab. Current hardware makes the distinction concrete: an eight-channel CTS4000 puts Max. 21kVA behind channels running 0V to 110V and 0A to 3000A, while a pack-scale Procyon runs 40V to 1500V at up to 8,000A across 5kW – 480kW. Same catalogue, two different laboratories. Check per-channel current and channel count before headline power, and audit your existing test code for command coverage before assuming any swap is a drop-in.

It is also worth being clear-eyed about why this happens. Acquisitions consolidate web properties long before they consolidate product lines, so the documentation vanishes while the installed base is still very much in service. It is not a signal about the hardware's quality. It is a signal about who is now responsible for supporting it.