Cognex In-Sight Vision Suite or In-Sight Explorer: which one your camera actually needs

The question I get most about Cognex cameras isn't about lenses or lighting. Somebody downloads Cognex In-Sight Vision Suite, because that's the program Cognex pushes now, plugs in a camera pulled from stock, clicks Refresh, and the device list stays empty. Most of the time nothing is broken. The camera just belongs to the other program.

Cognex runs two programs for In-Sight cameras, and the camera family decides which one you need. Below: the split by part number, what each program wants from the PC, what I check on a used camera, and the order I chase one that won't show up.

Which program opens which In-Sight camera

The older families (Micro, 2000, 5000, 7000, 8000, 9000) are In-Sight Explorer cameras. Cognex In-Sight Vision Suite covers the 2800, the D900 and the newer families at the bottom of the table. Explorer carries the firmware for its cameras inside the installer, so the last column shows which build your camera ends up on.

Camera family	Part number looks like	Program	Firmware build in Explorer 6.5.1
In-Sight Micro 1000	ISM1xxx	In-Sight Explorer	4.10.5 PR1
In-Sight 5000	IS51xx, IS54xx, IS56xx	In-Sight Explorer	4.10.5 PR1
In-Sight 5705, 5705C	IS5705	In-Sight Explorer	5.9.2
In-Sight 7000 Gen1	IS7010 to IS7432	In-Sight Explorer	4.10.5 PR1
In-Sight 7000 Gen2	IS7500 and up	In-Sight Explorer	6.5.1
In-Sight 8000	IS8100 to IS8505	In-Sight Explorer	6.5.1
In-Sight 9000	IS9xxx	In-Sight Explorer	6.5.1
In-Sight 2000 vision sensors	IS2000	In-Sight Explorer	not one of the three bundled builds, check it in Explorer once connected
In-Sight 2800, 3800, 3900, 8900, 6900, L38	IS28xx, IS38xx and the rest of these families	Cognex In-Sight Vision Suite	does not apply
In-Sight D900	ISD9xx	Cognex In-Sight Vision Suite with the ViDi adapter, plus a Cognex Security Dongle	does not apply

 

Two pairs of part numbers fool people. An IS2000 sensor and an IS2801 camera both start with a 2, and only the second one belongs in Vision Suite. Same story with an IS8402 (8000 series, Explorer) and anything from the 8900. Read the whole number, not the first digit.

Why Cognex doesn't make this obvious

Cognex markets Vision Suite as one platform for the entire In-Sight line. In practice the families it supports are the newer half of the table above, and a 9000 still gets set up in Explorer.

Then in September 2025 a batch of security findings came out against Explorer and four of its camera families. Cognex didn't answer with a new Explorer. It called Explorer-based systems legacy, not intended for new applications, and pointed at the 2800, 3800 and 8900. So Explorer still runs your existing line, it just won't get new camera families. The newest build I know of is still 6.5.1.

What each program needs on the PC

	In-Sight Explorer 6.5.1	Cognex In-Sight Vision Suite 26.2.1
Released	October 14, 2024	October 5, 2026
Download	ZIP, about 1.1 GB	ZIP, about 6.3 GB
Windows	Windows 10 Pro 64-bit or Windows Server 2016 (Windows 7: use Explorer 5.9.2)	Windows 10 64-bit, version 1809 or newer in the versions I've used; check the requirements of the one you download
Also needs	.NET Framework 4.5.2 (the installer fetches it), display at 96 DPI	Google Chrome; for the ViDi adapter, an NVIDIA GPU and a Cognex Security Dongle
Job editors	EasyBuilder and Spreadsheet	EasyBuilder and Spreadsheet
License	free for registered users, no time limit, as long as an In-Sight camera sits on the same network	same terms
Emulator with no camera	Offline Programming Key	key only for 2800 and 3800 models; Edge Learning tools also need a cloud credential and a live internet connection

 

Windows 11 isn't on Explorer's list. For Vision Suite, check the system requirements of the exact version you download before you plan around Windows 11.

The 96 DPI line in that table is not trivia. On a laptop with display scaling above 100 percent, Explorer's IP address boxes only take two digits per field. Looks like a bug, it's scaling. Set the display to 100 percent and reboot.

Vision Suite also brings CodeMeter onto the PC, since the Edge Learning credential gets imported through CodeMeter Control Center. If the same laptop holds FactoryTalk activations, read my CodeMeter article before you install, because the Cognex and Rockwell licensing can step on each other.

Buying a used In-Sight camera: four checks before it goes on the line

Most In-Sight cameras I deal with now are replacements. The station runs an Explorer job, the camera died, and nobody wants to rebuild it around a 2800 and Cognex In-Sight Vision Suite just to get a picture back. Fine reason to buy the same model again.

1.    Match the full part number on the label against the table. Mind the 2000/2800 and 8000/8900 pairs.

2.    Expect someone else's IP address. DHCP is the factory default, but a camera that came off a working line usually carries a static address from that plant. With no DHCP server on your bench, Explorer's Add Sensor/Device to Network dialog sets a new address. Careful with the option to reset the camera to factory defaults in that dialog: it overwrites the camera's proc.set settings file.

3.    Check the firmware. A camera on older firmware may still work, but some features aren't supported or fully tested on it, so update unless the job ties you to an old version. Each model also has a floor: a 7050 or 7210 needs at least 4.9.0, an 8402 needs 5.2.0, a 5705 needs 5.1.0.

4.    If the old camera still boots, pull the job and settings off it before you touch firmware on either one. Cheap insurance.

When the camera doesn't show up

The order I work through when a camera is missing from the list. The left column is for Explorer cameras, the right one for Cognex In-Sight Vision Suite cameras.

 

In-Sight Explorer

Start dumb: the 24VDC and ENET LEDs on the back should both be lit. Most 5000 series cameras autosense a direct cable to the laptop, not every model does, so put a switch in between and stop guessing.

Then ping it. "Request timed out" means nothing answers at that address. Power the camera down and ping again: if something still answers, you have a duplicate IP on the network.

Subnet is the one that gets most people. With a 255.255.255.0 mask the first three numbers have to match on the PC and the camera, the last one is free. A PC at 192.168.1.24 will never list a camera at 192.168.0.98, because the third number differs.

The third number differs, so Explorer never lists this camera, even though the cable is fine.

Two ways out: move the PC onto the camera's subnet, or readdress the camera with Add Sensor/Device to Network. Moving a whole set of cameras to a new network? Readdress them while the PC is still on the old one, then move the PC. And a camera that sits on another subnet on purpose, behind a router, needs its host name and IP in the Explorer Host Table. Until then it never appears in the In-Sight Network pane.

A few less obvious ones:

·       Explorer takes the IP of the network card at the top of the binding order. On a laptop that's often Wi-Fi. Turn Wi-Fi off while you commission. If the laptop's adapter is a USB one, I covered its own quirks in the USB C to Ethernet adapter article.

·       Firewall and antivirus off while you commission. Cognex puts most failed firmware updates down to a firewall.

·       On Windows 10, if the camera or emulator won't open in Spreadsheet View, look in Region settings for "Beta: Use Unicode UTF-8 for worldwide language support" and uncheck it.

·       File transfers fail while something else holds port 21. Usually that's IIS running an FTP site. netstat -a shows it.

The strange one: the camera pings fine and never shows up in the network pane. Check the host name. A garbled one hides the camera, and the fix goes through FTP and Telnet:

1.    FTP into the camera and pull proc.set.

2.    Find the _sNet line. If the host name between the quotes is readable, this isn't your problem, stop here.

3.    Replace it with a clean name, ideally in the usual model_MAC pattern, and copy the whole edited line.

4.    Telnet in, log in, type "ev " (with the space) and paste the line.

5.    Type "ev GetNetwork" and confirm the HostName, then "ts" to save and "rt" to reboot.

Cognex In-Sight Vision Suite

Cognex lists five causes for a device missing from the Network tab: no In-Sight EasyBuilder adapter installed, a firewall blocking the connection, no admin rights for the user, network ports taken by another application, and "Discover Misconfigured Devices" left unchecked. On a secondhand camera still carrying another plant's address, that checkbox is the first thing I tick.

An In-Sight 3800 has two Ethernet ports, and Cognex In-Sight Vision Suite connects on one at a time. The web HMI can use both at once, Vision Suite can't.

The D900 runs in Cognex In-Sight Vision Suite through the ViDi adapter and has its own rules. It has to sit on the same subnet as the PC, Cognex recommends a Gigabit switch and a power supply rated for at least 5 A continuous, and the Cognex Security Dongle has to stay plugged into the PC through programming, training and testing.

Moving an Explorer job to a Cognex In-Sight Vision Suite camera

Cognex has a separate download, the In-Sight Spreadsheet Job Converter, that turns Explorer Spreadsheet jobs into the Vision Suite spreadsheet format. It won't convert everything. It gives you a start and a report of what didn't come across.

Check what sits around the camera too. The 3800 doesn't support the old In-Sight SDK (the replacement is a WebSDK), and a VisionView 900 panel doesn't support the 3800 either, that job moves to VisionView Web. Custom software plus the panel on the door can turn a camera swap into a small project.

My rule: if the station works and a like-for-like camera exists, swap like for like. Migrate when you're rebuilding the station anyway.

Keep Explorer cameras off the office network

The 2025 findings came down to how these cameras get managed. Firmware upgrades and reboots go through a Telnet service on port 23, and user names and passwords cross TCP 1069 in a proprietary protocol with no encryption. Affected: firmware 5.x through 6.5.1 on the 2000, 7000, 8000 and 9000 series, and Explorer 5.x through 6.5.1.

No firmware fix came with it. Long term, Cognex wants you on a Cognex In-Sight Vision Suite camera. Short term, the protection is the network. Keep the cameras away from the internet, behind a firewall and away from the business network, and use a VPN when somebody needs remote access.

FAQ

Is Cognex In-Sight Vision Suite free?

Yes, if you're a registered Cognex user with at least one In-Sight camera on the PC's network. No time limit, and the same goes for Explorer. The catch is working without a camera: the Vision Suite emulator key only covers 2800 and 3800 models, and its Edge Learning tools stop working once the PC loses internet. For a closed network, Cognex sells an offline license dongle.

Can Cognex In-Sight Vision Suite open an In-Sight 5000 or 7000 camera?

No. Neither family is on the list Vision Suite supports. Use In-Sight Explorer 6.5.1, which has the firmware for both built in.

Does In-Sight Explorer run on Windows 11?

It may install and run, but it isn't supported there. Explorer 6.5.1 is supported on Windows 10 Pro 64-bit and Windows Server 2016 only. Still on Windows 7? Explorer 5.9.2 is the version for it.

Do I need a dongle for Cognex In-Sight Vision Suite?

For the D900 and anything running on the ViDi adapter, yes, and it has to stay in the PC the whole time. For a 2800, setup is install, connect the camera, click Refresh, then Connect. No dongle in that list.

Replacing an In-Sight camera on an Explorer line

If the station runs Explorer and you just need the camera back, we carry the older families as new surplus: the IS5100-C10 from the 5000 series, the IS7050-01 and IS7802MP-373-50 from the 7000, the IS8402M-363-50 from the 8000, the IS9912M-363-50 from the 9000 and the ISM1400-11 from the Micro 1000. For a Cognex In-Sight Vision Suite station there's the IS2801M-EC and the D900 ISD905M-61-3709. We don't sell software or firmware licenses; both programs come from Cognex. Every camera carries our two-year warranty.