COMMENTS
Test is a must to check if there is no errors in a particular output or devices, that's why a test instrument is important in making this task convenient.
In your manuals, I noticed that there is not SCPI command support for uploading binary block data -- such as a waveform. The documentation mentions using "C" APIs from ZBIND.dll in combination with SCPI. Is this true? Or is there messaged based solution for loading a custom waveform that I am not seeing?
Yes, it is true that there is not a SCPI command upload for block data. Block data is instead uploaded through block transfers which differ depending on the instrument's platform. For instance, PCI transfers are done through direct memory access (DMA). These transfers provide much higher bandwidth than command based transfers.
To hide these differences and avoid the need to know specific transfer details, we provide the ZTEC Backplane Binding Layer (zbind). Through this C driver, all block transfers can be done using zbind_blkin() and zbind_blkout(). These are used in conjunction with SCPI commands that let the instrument know where to transfer uploaded data, or to return the data address for downloads to the host machine.
To use the zbind block transfer functions, the user needs to be aware of limitations such as buffer size, buffer address, and waveform data types. While these values are available though other zbind functions, it is generally easiest to use the provided instrument drivers, which have built-in functions (ex: ztscopeM_load_waveform) to support waveform transfer. The instrument drivers are also available for other interfaces, such as COM, IVI and LabVIEW.
To transfer waveforms without any programming, use the graphical user interface (GUI) specific to the instrument. The GUIs allow waveform transfer to and from comma separated value (csv) text files.