Book a consultation

Cognex In-Sight Smart Cameras: Families, Selection and Failure Modes

In-Sight EasyBuilder vs Spreadsheet: Which Programming Mode to Use

In-Sight spreadsheet vs EasyBuilder: the two Cognex programming modes, when each fits, and which is easier for plant technicians to maintain.

Vladimir Romanov


Should an In-Sight job be built in EasyBuilder or in the spreadsheet? For most inspections, EasyBuilder is the better first choice: it is guided, it produces a consistent job, and a technician who did not build it can follow it. The In-Sight spreadsheet is the right choice when the job needs custom logic, unusual result handling or functions EasyBuilder does not expose. Both are environments inside In-Sight Vision Suite, and they can describe the same job. This page compares the two, shows when each fits and addresses the question a plant cares about after commissioning: who can keep it running. It sits under the In-Sight overview and the Cognex hub.

The two modes

EasyBuilder is the guided environment. In Cognex’s In-Sight Explorer 5.8.1 documentation a job is built in application steps: Get Connected, Set Up Image, Locate Part, Inspect Part, Inputs/Outputs, Communication, Filmstrip, Save Job and Run Job. The steps are meant to be followed in order on a new job and can be revisited in any order afterwards. You drag tool regions onto the image and read the outcome in a results table.

The spreadsheet is the older, classic environment. Each tool and calculation is a cell with a function, laid out in a grid with the image overlay, and Cognex describes it as the most comprehensive set of vision and communication functions. A cell can locate a part, another can measure it, another can format the result for the PLC.

They are views of one job. Cognex documentation, for an older Explorer release that carries the same concept into Vision Suite, says EasyBuilder auto-populates a spreadsheet with functions matching its application steps. You can look at that spreadsheet. Cognex adds that editing EasyBuilder parameters in the spreadsheet needs advanced knowledge.

How EasyBuilder steps relate to spreadsheet cells in one In-Sight job On the left, the five EasyBuilder application steps in order: Get Connected, Set Up Image, Locate Part, Inspect Part, Communication. An arrow labelled auto-populates leads to a spreadsheet grid on the right in which each step has matching function cells: acquisition settings, a location function, inspection functions, and result formatting and writing functions. A bracket marks that EasyBuilder and the spreadsheet describe the same job file. A caution at the bottom notes that editing EasyBuilder-generated cells directly needs advanced knowledge and may stop EasyBuilder from presenting the step as designed. One job, two views: guided steps and the cells behind them 1 · Get Connected 2 · Set Up Image 3 · Locate Part 4 · Inspect Part 5 · Communication fills The spreadsheet behind the steps Connection and acquisition settings: trigger, exposure Location function: finds the part, sets the fixture Inspection functions: measure, read, classify Result formatting and writing to the PLC buffer Extra cells you add: custom logic, filters, image writes, anything outside the steps Cognex warns that editing EasyBuilder parameters in the spreadsheet needs advanced knowledge.
EasyBuilder is a guided front end to a spreadsheet job. The risk is in the dashed box: cells added by hand sit outside the steps, and only the person who wrote them knows they exist.

When each mode fits

The Limited and Fits calls for EasyBuilder follow Cognex’s own guidance for its two environments, from an older release’s documentation that carries the same concept. The Spreadsheet column for simple jobs, including the word Overkill, is our judgement. Confirm that the tool you need exists on your camera, because Cognex states that not all tools are available on every vision system.

JobEasyBuilderSpreadsheet
Presence or absence, countingFitsOverkill
Product verification: read a code, find a pattern, check colourFitsFits
Gauging with distance and angleFitsFits
High-contrast character reading and verificationFitsFits for harder cases
Simple defect detection with blob, brightness, contrast or pixel countFitsFits
Hard defect detection that needs image filteringLimitedFits
Heavily customised code verification or complex result logicLimitedFits
Sorting several randomly oriented objects, or an unknown numberLimitedFits
Edge AI tools such as Anomaly Detect or ClassifyFits, in an Edge AI groupFits, under the ViDiEL function names in the release notes

The Edge AI row shows a naming trap. The release history documents the spreadsheet functions under their older ViDiEL names, while Vision Suite 26.1.0 renamed the tool family Edge AI. A technician reading older notes needs both names.

Which mode can a technician maintain

This is the question that outlasts commissioning. The comparison below is our view, based on how the two modes are described, and not a Cognex statement.

FactorEasyBuilderSpreadsheet
Learning curve for a new technicianGuided steps, results tableNeeds knowledge of the functions and cell references
Consistency between jobsHigh: same steps each timeDepends on the author
Depends on one authorLowHigh if heavily customised
Custom logicLimitedFull
Change controlSame job file either waySame job file either way
Close-up of printed rows of numbers on white paper, shallow focus
A spreadsheet job reads like rows of formulas: obvious to its author, opaque to a technician who inherits it without a written description.

Our recommendation. Build in EasyBuilder unless a requirement forces the spreadsheet, and when it does, confine the custom logic to clearly labelled cells and document them. Change control does not depend on the mode, since both save the same job. Cognex’s release history lists features that help: Backup and Restore utilities and a Compare Jobs function, a Job Validation step, audit logging, jobs that can be saved and backed up while the camera is online since release 25.2.0, and an Elevated access level added in 25.1.0 alongside Full, Protected and Locked. Use them, and store a dated backup with the software and firmware version.

A way to decide, and an illustrative case

Before opening either mode, answer four questions in order.

  1. Can the requirement be met by the standard tools? Locate the part, measure, read or classify, and report a pass or fail. If yes, start in EasyBuilder.
  2. Does anything need logic between the tools and the output? Sorting several objects, combining results by custom rules or formatting an unusual output buffer points to the spreadsheet.
  3. Who will maintain it? If the answer is plant technicians with a day of training, keep the job inside the guided steps wherever possible.
  4. What does the licence on the camera allow? Check before you design around a spreadsheet feature.

An illustrative case. A line inspects a printed lot code and a seal. The code read and the seal presence are standard tools, and the PLC needs only a pass or fail and a job number. That job belongs in EasyBuilder. A second station on the same line must count an unknown number of products in a tray and report each one’s position to a robot, which needs logic the guided steps do not offer. That job is a spreadsheet job, and it deserves a written description and a named owner from day one. Mixing the two on one plant is normal. The mistake is choosing the spreadsheet for every job because one job needed it.

Where it gets hard

  • The licence is not a clean rule. The 23.1.0 notes refer to a Spreadsheet Editor on Spreadsheet-licensed cameras, and 3800 ordering material shows EasyBuilder and spreadsheet toolsets. We could not confirm which models ship with which, so the part number decides what you can do.
  • The documentation we relied on is older. The clearest description of when to use each mode comes from an In-Sight Explorer 5.8.1 page. The concept carries into Vision Suite, but menu names and details may differ in 26.x.
  • Custom cells leave no trace in the guided view. A technician working only in EasyBuilder may never see the logic that sets a result bit.
  • The job file format is unverified. Search summaries suggest current jobs are single files with a newer extension, but we did not confirm it, so check the saved file on your camera.
  • A rewrite is a rebuild. Moving a spreadsheet-heavy job to a different camera family is a project, not a conversion, as discussed on the Vision Suite versus Explorer page.

Related: In-Sight overview · Choosing an In-Sight camera · Vision Suite versus Explorer · Cognex hub

Frequently asked questions

What is the In-Sight spreadsheet?

The In-Sight spreadsheet is the classic Cognex programming environment in which vision tools, logic and communication are cells in a grid laid over the image. Cognex describes it as having the most comprehensive set of vision and communication functions. It is one of the two environments in In-Sight Vision Suite, the other being the guided EasyBuilder.

What is the difference between EasyBuilder and the spreadsheet?

EasyBuilder is guided: you work through application steps, drag tool regions on the image and read results in a table. The spreadsheet is free-form and offers more functions. Cognex documentation says EasyBuilder fills a spreadsheet with functions that match its steps, so one job can be seen both ways, though editing EasyBuilder parameters in the spreadsheet needs advanced knowledge.

Can I switch a job between EasyBuilder and the spreadsheet?

Partly. Cognex documentation says EasyBuilder auto-populates a spreadsheet matching its steps, which you can view. Cognex also warns that editing those EasyBuilder parameters in the spreadsheet needs advanced knowledge, and that not every In-Sight system can access the spreadsheet. We have not verified the current behaviour on every camera, so test on your model.

Which mode is easier for plant technicians to maintain?

In our view EasyBuilder, because the steps are guided and the result is the same each time, so a technician who has not seen the job before can follow it. A heavily customised spreadsheet is powerful but depends on whoever wrote it. Whichever mode you use, keep dated backups and a written description of every job.

Do I need a special licence for the spreadsheet?

Possibly. Vision Suite release 23.1.0 notes list a Spreadsheet Editor on Spreadsheet-licensed cameras, and 3800 ordering tables show EasyBuilder and spreadsheet toolsets. We could not confirm which models ship with which licence, so check the part number and ask Cognex or your distributor before you plan on custom spreadsheet logic.

References and further reading

  1. In-Sight Vision Suite EasyBuilder release history · Cognex documentationSpreadsheet Editor on licensed cameras, Job Validation, backup and audit features by release.
  2. In-Sight Explorer 5.8.1: development environments · Cognex documentationCognex's own description of when to use each environment; an older release, same concept.
  3. In-Sight 3800 Reference Manual (Vision Suite 25.3) · Cognex documentation
  4. WriteImage tool (Vision Suite 25.3 spreadsheet help) · Cognex documentationAn example of a spreadsheet function that sends images to FTP or SFTP.
  5. Edge AI Anomaly Detect tool · Cognex documentation
  6. In-Sight Explorer 5.8.1: application steps · Cognex documentation

← In-Sight

Have a project that needs technical ownership?

Send us the situation. If it is not something we should take on, we will say so.

The Plant-Side Brief

The weekly brief for the people who own a plant’s control systems.

One email every Wednesday for engineering and operations leaders responsible for controls, SCADA, MES and OT networks. Skim the top in two minutes; read the Deep Dive when you have fifteen.

  • One modernization problem, worked through to cost, risk and a schedule you can defend. The Deep Dive.
  • End-of-support dates before they reach your plant Windows, servers, controllers and HMI software. Lifecycle Watch.
  • A checklist your engineers can run that week not a framework to admire. Field Kit.
  • Every number sourced, no vendor agenda we are paid by plants, never by vendors.