1.) No, there is no way to limit the callback to react on "Additional Results". But as you get the reference to the step which "triggered" the callback, you can check if Additional Results are present. If there are none, skip the rest of the callback.
2.) There are three ways to solve this in a good manner:
2.a) Log the data directly in the code module. This is somehow against modularity (as acquisition and logging are part of the same code module), but the advantage is that you don't need to pass the whole data to TS. This can improve runtime performance. Please note that i assume that only certain specific parameters of that raw data (e.g. frequency, maximum amplitude) are important for evaluating the UUT.
2.b) Log the data by a second code module. This implements recommendations on modularity, but data has to be passed to TS for this by the acquisition module (unless you do some "hack" to transfer it internal between code modules like using an FGV). The logging module can be part of the SequenceFilePostStepResultEntry callback or, even better, a (post step) substep module in a custom step type.
2.c) Leave the data in the ResultList (that means: make sure that it gets into that list by e.g. Additional Result) and use custom report generation to write the data into a file as part of the reporting mechanism.
Depending on the requirements, you should use one of these three options. As we don't know your requirements, there is not much of a recommendation we can give you.
Norbert
Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
