Asee peer logo

Enhancing The Dsp Toolkit Of Labview

Download Paper |

Conference

2002 Annual Conference

Location

Montreal, Canada

Publication Date

June 16, 2002

Start Date

June 16, 2002

End Date

June 19, 2002

ISSN

2153-5965

Conference Session

Programming and DSP Potpourri

Page Count

15

Page Numbers

7.513.1 - 7.513.15

DOI

10.18260/1-2--10298

Permanent URL

https://peer.asee.org/10298

Download Count

229

Request a correction

Paper Authors

author page

Murat Tanyel

Download Paper |

Abstract
NOTE: The first page of text has been automatically extracted and included below in lieu of an abstract

Main Menu

Session 3220

Enhancing the DSP Toolkit of LabVIEW

Murat Tanyel Dordt College

Abstract

Most Digital Signal Processing (DSP) courses rely heavily on MATLAB and/or C, representing the state of the art in textual programming, for their standard computer tools. Many textbooks are published containing examples, if not sections, devoted to these textual languages. We have argued, in a previous paper, that whereas this environment may be efficient in manipulating equations, textual implementation of processes best described by block diagrams loses its intuitive substance and gave examples in LabVIEW of implementations that are better left graphical. However, the standard DSP toolkit of LabVIEW is aimed at the practicing engineer/scientist who needs to process acquired data to reach other ends in contrast to a student whose aim is to learn about signal processing. LabVIEW’s DSP toolkit is rich with high level algorithms but needs to be enhanced in order to serve the pedagogical needs of students of DSP. Having decided to teach DSP with LabVIEW a year ago, I have found myself writing many routines to complement the standard DSP toolkit as I have tried to demonstrate basic concepts. This paper will describe this additional toolkit that has been growing to make LabVIEW a better teaching tool in a DSP class.

I. Introduction

When I started teaching DSP last year, I chose LabVIEW as the computer tool for hands-on experiences and demos. The decision was against the common trend, for MATLAB has become the de facto standard for numerical computation in signal processing 1. This uncommon decision was taken because of two major reasons: i) My previous experience with LabVIEW 2-6 has been very rewarding and I would like my students to have LabVIEW programming skills in addition to MATLAB programming skills they acquire in their Introduction to Engineering class at the freshman level and in Linear Systems at the sophomore level. ii) It was my contention that “processes that [are best] describe[d in terms of] what happens to various inputs to achieve an output, so easily depicted by block diagrams in control systems, communication systems and DSP, are better candidates for simulation and/or realization in a graphical programming environment than in a textual environment.”7 My personal preference, as given in (i) above was not adequate to justify this choice, while reason (ii) could be addressed by other choices, such as MATLAB’s SIMULINK and HP’s VEE. SIMULINK has provided an effective graphical environment and thus ‘valuable additional simulation capability’ for control systems8. HP’s VEE is another contender in the graphical programming realm which is also aimed at data acquisition and instrument control9. In the end, the ready availability of LabVIEW’s full development system in

Proceedings of the 2002 American Society for Engineering Education Annual Conference & Exposition Copyright Ó 2002, American Society for Engineering Education

Main Menu

Tanyel, M. (2002, June), Enhancing The Dsp Toolkit Of Labview Paper presented at 2002 Annual Conference, Montreal, Canada. 10.18260/1-2--10298

ASEE holds the copyright on this document. It may be read by the public free of charge. Authors may archive their work on personal websites or in institutional repositories with the following citation: © 2002 American Society for Engineering Education. Other scholars may excerpt or quote from these materials with the same citation. When excerpting or quoting from Conference Proceedings, authors should, in addition to noting the ASEE copyright, list all the original authors and their institutions and name the host city of the conference. - Last updated April 1, 2015