DSPower®-Block Diagram Software

DSPower-Block Diagram v2.0 is a DSP product, system, and algorithm design software package that runs under Microsoft Windows 9x, Windows ME and Windows XP. The package presents an integrated user-interface which offers block diagram design, numerous DSP and math functions, user-defined functions, and source code generation. In addition, DSPower-Block Diagram provides interactive data visualization displays and instruments blocks, allowing users to debug designs, perform in-depth analysis, and make measurements.

DSPower-Block Diagram is the first block diagram DSP package to seamlessly combine simulation, interactive measurement, and multiple types of source code generation under a unified graphical user-interface. DSPower-Block Diagram can generate two types of source code: MATLAB® .m files, and Hypersignal® macro language. An optional C/C++ language generator is also available. Generated MATLAB and Hypersignal source code can be used to perform algorithm or system simulation, and generated C/C++ language source code can be downloaded for real-time execution on a supported DSP board. Block equivalence is maintained across source code types, allowing a diagram first to be simulated with MATLAB m files or Hypersignal macro language, and then regenerated as C source code for real-time execution.

Creating user-defined functions is well-supported, and possible in many ways; several methods do not require programming knowledge. Block diagram execution is data-driven by default; however, all blocks contain optional control connections that can be used to explicitly specify execution sequences.

Block Diagram Interface

• User-Interface. The DSPower-Block Diagram user-interface is a graphical, object-oriented interface implemented under the Microsoft Windows operating system.

• Worksheet Objects. Worksheet objects include block selector, toolbars, multiple-diagram control, DSP/analog hardware setup and configuration, DSP Engine setup and configuration, and waveform file locator.

• Block Selector. DSPower diagrams can contain code, control, function, display, filter, instrument, or utility blocks.

• Interactive Display and Instrument Blocks. Display and instrument blocks can be shown and arrayed in various sizes; maximize and automatic tiling options can be used to temporarily utilize worksheet area for detailed display/instrument analysis and measurement.

• Setup Parameters. In many instances, blocks contain both standard and "Ex" setup parameters. These parameters can be set prior to diagram operation or interactive operation. For example, a typical FFT block contains input, output, and FFT size as standard parameters; additional Ex parameters would include window type, overlap, and analysis framesize (zero-fill). If Ex parameters are not specified, default values are used. Setup parameters for individual blocks are saved according to block type and/or waveform file input.

• Fly-Over Help. The majority of controls and objects in the DSPower-Block Diagram environment present fly-over help when the cursor is stabilized over the control. Additionally, in many cases an additional "small help" button is present inside the fly-over box which can be used to elicit standard display of relevant online help documentation sections.

Algorithm, System, and Product Simulation

• Diagram Execution. Source code generation and subsequent diagram execution are data-driven. Control flow may also be specified for ambiguous situations. Blocks can be run isolated or in partial diagrams, without disturbing the overall diagram.

• Waveform File Mode. In waveform file mode, all intermediate results are stored in time/frequency/wavelet domain waveform files, allowing post-simulation analysis and debug of any point in the diagram.

• Frame Mode. In frame mode, the diagram is run without default storage of intermediate results (unless specific waveform file utility functions are inserted in the diagram). This mode is used when creating and testing a system for real-time execution.

• Procedure Blocks. Groups of blocks can be "procedurized" to form one block, which can be added to the system or user libraries and becomes re-usable. Procedurized blocks can be combined to any level, and can be "exploded" at any time for inspection.

Interactive Operation

• Instant Access to Waveform Analysis and Function Results. Blocks can be run individually and as partial diagrams. Each block contains a "Run" button, which activates the function or display/instrument using the currently entered setup parameters.

• User Control Objects. Display and instrument blocks include a wide and rich assortment of interactive controls. Examples include:

  • zoom, pan, amplitude offset and control

  • waveform editing (cut-paste and rubberband)

  • D/A output to supported DSP/analog hardware

  • multitrace and overlay options

  • 256-color contour frequency domain displays, with fast update, control over dB range and step, time-spanned, and zoom/pan

  • linear and log amplitude formats; linear and log axes in frequency domain displays

  • cursor readout and measurement

  • display format, axes, grid, plot style, and many other options

  • context-sensitive online help

DSP Engines

• Hypersignal®-Macro, MATLAB , or DSP/Analog Hardware. At least one of these engine types are required for effective use of DSPower-Block Diagram. The Hypersignal®-Macro/Acoustic and MATLAB software packages provide a wide range of DSP and math functions and displays, which appear as blocks in the system and user libraries. Hypersignal®-Macro and Hypersignal-Acoustic software offers built-in device driver support for a wide range of DSP/analog hardware types, which enables diagram simulations based on acquisition and measurement of real-world data.

• Native Source Code and User Objects. When diagrams or individual blocks are executed, native source code for DSP Engine software packages or hardware is automatically generated and interactive control objects are created.

User-Defined Expansion

• Adding blocks. Blocks can be easily added in the DSPower system by specifying a template file and one or more function files.

• Template Files. Each block is "registered" in the DSPower system by specifying a template file which includes attributes, symbolic references, input/outputs, parameters, attributes, data types supported, and any interactive user-interface controls. All aspects of block registration are data-driven and may be user-defined, including the type and layout of interactive control toolbars, dialog boxes, and other user-interface objects.

• Block Selector Representation. Blocks can easily be listed and unlisted from the current block selector (onscreen) display, and easily transported between systems. The block selector provides a convenient means to organize and locate functions, displays, and instruments.

• Function Files. Each block must have associated with it one or more function files. Function files can be in source or object form.

Source Code Generation

• Block diagrams are saved in source code (text) format.

• Macro Language and .m File Source Code. The base-level DSPower-Block Diagram package generates Hypersignal macro language and MATLAB .m source code.

• C Source Code. See separate DSPower-Real Time Code Generator (RTCG) software datasheets. When using the RTCG, diagrams in correct format are downloadable to supported DSP/analog boards for real-time execution.

Central to the design of DSPower is the concept of "DSP engines". This concept creates a division of labor which makes DSPower both easier for the vendor to maintain and extend, and easier for the user to understand and operate. User-interface and source code generation are performed by DSPower, while at least one or more DSP engines and various support tools are invoked remotely and transparently to achieve compilation and execution of generated code, as well as interactive operation. Several system simplifications also result from the DSPower architecture; for example, block-diagrams are saved and retrieved in source code form. Currently there are three (3) DSP engine possibilities: MATLAB (version 4.x for Windows, available from The MathWorks), Hypersignal®-Macro, Hypersignal-Macro EX, or Hypersignal-Acoustic (version 4.x for DOS, available from Hyperception or Signalogic), and a supported PC-compatible DSP/Analog board from one of several manufacturers. Both MATLAB and Hypersignal®-Macro offer superb simulation, by virtue of their rich procedural languages containing many functions and displays, and built-in compilers.

When Hypersignal®-Macro is used as a DSP engine, access to over 60 types of off-the-shelf DSP/analog hardware--including data acquisition, multichannel, and multimedia--is available in the DSPower environment. Several instruments and displays utilize hardware directly, DSP and math functions can be accelerated, and generated C/C++ source code can be compiled and downloaded to onboard DSPs for real-time execution. When Hypersignal-Macro is used in conjunction with MATLAB, mixed block-diagrams are possible, allowing, for instance, data acquisition to occur in a Hypersignal block, followed by processing in a MATLAB block.

The DSPower-Block Diagram package requires Win9x, WinME, or for some supported boards, WinXP and at least a 450 Mhz Pentium P3 with 128 Mbyte RAM.