Replacing Scaled Waveform with Custom Processing

In many circumstances, we may want our custom device to generate a new waveform as a result of its processing. For this purpose, the Waveform Processing Custom Device example already generates scaled waveforms as outputs. If you want to have your own type of processing, it is recommended that you replace this Scaled Waveform functionality with yours instead of recreating many of the functionalities that already exist.

The Waveform Processing Custom Device has been documented with bookmarks to indicate the places where changes will need to be made. To open the bookmark manager, navigate to View>>Bookmark Manager while the project is open to display a Window like the one below. The bookmark used to document these changes is #ReplaceScaledWaveform.

From this window, you can double click in any of the bookmarks to take you to the specific location where the change needs to be made. Most of the changes imply simply renaming elements with something that is representative for your custom processing as it will happen in the global Constants.vi for many of its elements. The image below shows an example of how the Contants Tab of this global would look like after making all your changes. As it can be seen, 'Scaled' has been replaced with 'myProcessing'.

Some of the globals are called from more than one place, which means that the name needs to be changed only once and then just do the re-linking to the correct variable from the rest of the places.

As you apply each of the changes, change the bookmark to something like #ReplaceScaledWaveformDone for that specific section. In this way you can track the changes that were already made and the ones that are still pending.