A GenICam driver keeps its start-up configuration in an INI file, and the tools on one PC do not always agree about where that file lives. One tool reads a registry value that points at a directory you chose. Another resolves an environment variable to the driver's installed data folder. Set your exposure, packet size and trigger defaults in the first tool, and the second tool opens the camera without them. This guide is for engineers who commission GigE and CoaXPress cameras on Windows acquisition PCs and ship one machine image per line. It shows you how to find which mechanism your stack uses, how to point every tool at one portable path, and what the backup arithmetic says about which mechanism to standardize on.
Two mechanisms, one file
A GenICam camera — GigE Vision, USB3 Vision or CoaXPress — exposes its features through the standard, and the driver stack on the PC loads a GenTL producer to talk to it. That stack keeps its own housekeeping in a small INI file; call it genicam.ini in the examples here. The file records stack-level defaults: which producer to load for a device, which device to open, saved connection filters.
Two mechanisms decide where a tool looks for it:
- A registry value pointing at a file you choose. A string value in the registry holds a full path to the INI, and the stack's management console reads and writes settings there. Because you pick the directory, the file can sit in your site data folder next to your recipes.
- An environment variable naming a data folder. The installer sets a variable that resolves to the driver's data folder, and the browser-style tool looks for its INI inside it. Your stack may use one mechanism, or both.
The same split causes file-location trouble elsewhere in a GenTL stack: producer XML and CTI paths fail the same way, with a program searching one folder while the file sits in another. That class of error is covered in GenTL XML file location errors: diagnose camera description file paths.
Choosing a pointer you control over a path the installer owns is not a vision-specific question. The same trade-off decides where controllers and SCADA servers keep their configuration, as this environment variables versus file storage comparison for controller configuration shows.
How to find which one your stack uses
The registry side
Open the Registry Editor and search for a value whose name combines your SDK's short name with "INI". The value you want is a string (REG_SZ) whose data is a full path ending in .ini. Right-click the parent key, choose Export, and save the .reg file into your data directory: it re-applies the path on a fresh PC with one double-click.
The environment side
Open a command prompt and run set, then look for any variable whose name contains the SDK's short name. Its value is a folder path — the data root the browser-style tool searches for its INI. Compare that folder with the path in your registry value. If the two differ, your tools are reading two different files, and that is the problem the next section explains.
Why two tools disagree
Each program hard-codes its own resolution. The console resolves the registry value; the browser resolves the environment variable; neither reads the other's copy. The symptoms are consistent:
- You set exposure, gain, packet size or trigger defaults in the management console, and the browser tool opens the camera with factory defaults.
- You change settings in the browser tool, and the console shows yesterday's values on the next shift.
- The INI in your data directory carries a fresh timestamp, yet a program ignores it.
- A driver reinstall or service pack resets one path but not the other.
At least one vendor has shipped a service release that makes its tools read the same place. If your build has that fix, the tools already agree; if it does not, the sync steps below are mandatory, and they cost little either way. When settings vanish across a reboot rather than between tools, the cause is usually the same resolution split — see GenICam driver fails after restart: fix the camera configuration.
Per-product values belong in your own code and recipe files, not in the driver INI. Exposure and gain set at run time through the GenICam API are the pattern, shown in Setting camera exposure time through a GenICam API in Python. The INI's job is the stack-level defaults that make every camera open the same way on every PC.
The arithmetic that decides it
The decision comes down to one question: does your nightly backup capture the file?
Take an illustrative line: one acquisition PC, four GigE cameras, each commissioned with about 25 settings you care about — IP address, packet size, inter-packet delay, exposure, gain, black level, ROI window, trigger source, trigger delay, strobe timing. Lose the PC and the INI with it, and the recovery cost is:
The 3 minutes per setting is the realistic cost of looking up the intended value, entering it and exercising one trigger cycle. A scripted recovery tool cuts it, but most lines do not have one ready on commissioning day. Scale moves the total linearly: a twelve-camera line at the same 25 settings each is 300 settings, about 15 hours.
With the registry mechanism and the INI in your data directory, the nightly image already captures the file, and a replacement PC costs the ten minutes. With the environment mechanism and the file in the install folder, the backup captures nothing: the fresh image boots with factory defaults and the five hours start. Five hours against ten minutes is the whole argument — standardize on the mechanism your backup already captures.
One case flips it. If your application keeps every per-product value in its own recipe files and the INI only carries discovery defaults, the loss shrinks to minutes either way. Pick a mechanism, document it, and skip the sync plumbing.
Point every tool at one path
- Pick one directory your backup already covers — a site data volume such as D:\VisionData, not a folder under the SDK's install path.
- Set the registry value's data to the full INI path in that directory, and export the key as a .reg file into the same directory.
- Check the environment variable. If your stack accepts a full folder path there, point it at the same directory. If it only names an install-time data root, leave it and add a copy step to the image-build script: copy the INI from your data directory into that root after every settings change and before every image capture.
- Prove it: open both tools, change one value in each, and watch both copies' timestamps move together. If only one timestamp moves, a program is still reading its own file.
- Write the mechanism into the site file — directory, registry value name, variable name, copy step — so the next engineer does not rediscover it.
The whole procedure is about half an hour once, and step 3's copy line is a one-liner in any build script. If the stack then cannot find its producer at all after the move, that is the separate CTI-path failure covered in Camera node cannot acquire system instance: fix the CTI path.
When the usual answer is wrong
- Linux acquisition PCs. No registry exists, so the same stacks use environment variables and per-user configuration files. Set the variable in a start-up script or service definition rather than an interactive shell, keep the INI in a backed-up directory, and expect one copy per account that runs the tools.
- Several Windows accounts on one PC. Registry values can live per user or per machine. If the commissioning account differs from the operator account, confirm which profile holds the value before you call one path "the" path.
- Cloned images. The data directory travels with the image; the registry value may not, if it sat in a hive your imaging excludes. The exported .reg file exists for exactly this case.
- Controller-side INI files. PLCs and controllers parse their own INI files with their own path traps. Different ecosystem, same failure class; INI parser path errors on PLC SD cards walks through one such fix.
Before you ship the image
- INI in the data directory your nightly backup covers — the backup is the only thing that survives a dead PC.
- Registry value exported as a .reg into the same directory — a fresh image then restores the path in one double-click.
- Timestamp test passed on both tools — a configuration you have not exercised is a guess.
- Variable name and value written into the site file — the variable is invisible until someone looks for it.
- Copy step, if needed, running inside the image-build script — a manual copy is forgotten on the second PC.
- One rehearsed restore on a spare PC, timed — the first real restore is the wrong moment to learn the .reg file is missing.
Where the stack lives
Every mechanism above runs on the acquisition PC, so the parts around the driver belong in the same plan. A GigE Vision stack needs a network card in that PC, one with PoE if each camera should run on a single cable. The MV-GE2002P is a dual-port PoE GigE network card, the transport under the stack. GigE Vision cameras such as the MV-CU020-90GC, a 2.5 MP GigE model, are GenICam devices, so the driver, the producer and this INI sit between your software and the camera.
- Interface
- GigE
- Ports
- 2 ports
- Sensor format
- 1/1.7"
- Lens mount
- C-mount
- Interface
- GigE
- Resolution
- Up to 3 MP
Configure the camera side from the camera configurator or the camera finder, and pick the network hardware under frame grabbers. More driver-side failure modes are collected on the systems topic page, and integration help comes with every order — start at the contact page if you want a second pair of eyes on the sync step.
Questions
How do I re-apply the driver path after imaging a new PC?
Export the registry key while the path is still correct: right-click the key that holds the INI-file value in the Registry Editor and choose Export, saving a .reg file into the same data directory as the INI itself. After imaging, one double-click on that file restores the value. Keep the export in the nightly backup so the .reg and the INI can never drift apart.
Can I redirect the environment variable to my own data directory?
Sometimes. If the tool reads the variable as a full folder path, pointing it at your data directory moves its INI search there. If the variable only names the SDK's data root and the tool appends a fixed file name, redirecting it can break the SDK's other data files, so a copy step in the build script is the safer route. Test by changing one setting and watching which file's timestamp moves.
What actually gets stored in the driver INI?
Mostly housekeeping, not image data: which GenTL producer or driver to load for a device, the last device opened, saved connection filters such as IP address ranges or serial numbers, and any presets the browser-style tool offers. Per-product inspection settings belong in your own recipe files; the INI only has to make each camera open the same way on every PC.
Does any of this apply on Linux?
The registry half does not exist there. The same stacks fall back to environment variables and per-user configuration files, so set the variable in a start-up script or service definition, keep the INI in a backed-up directory, and expect one copy for every account that runs the tools. The timestamp test still proves which file each tool actually reads.
Can I edit genicam.ini in a text editor?
It is plain text, so yes, but treat it as a file the tools own. A program that manages the configuration may rewrite the whole file when it saves, discarding hand edits silently. Close the tools before editing, keep a dated copy before each change, and prefer making the change in the management console so every copy stays in step.

