Gocator Snapshot Sensors: User Manual
• 488
kFramework.exe is only loaded after a user selects a scenario and starts the emulator
session.
Debugging Entry Functions
VStart, VProcess, and VStop are called whenever a data record is played back in the emulator (that is,
when a user clicks on the Next button or types the frame number in the frame field) with at least one
tool instance. For more information on playback controls, see Recording, Playback, and Measurement
Simulation in the Gocator user manual.
VDescribe however is called when the DLL loads, before the debugger can attached to the
kFramework.exe process. To debug VDescribe, we recommend testing the function calls by putting
them in VInit.
For information on building targets for testing in the emulator, see the GDK class reference
documentation.
Tips
The following sections provide useful information for creating custom measurement tools.
Backward Compatibility with Older Versions of Tools
When loading a recording or job file that contains a custom measurement tool, the parameters in the
loaded recording or job file must match those in the firmware.
By default, if declared parameters are missing from the configuration, a job file or a recording will fail to
load.
There are two ways to provide backward compatibility with older parameter sets.
Define new parameters as optional
Mark a parameter as optional with the function GdkParamInfo_SetIsOptional. When a parameter is
marked as optional, parameter parsing functions succeed even if the parameter is missing from the
configuration. The missing parameter is initialized with default value.
Configuration Versioning
Over the lifetime of a tool, you may need to make changes to its interface (for example, changing or
removing parameters). The user-defined aspects of a tool interface—its parameters and
To Next Page
Loading...
Need help?
General
