Chapter 6 postview, Data file accessibility, Postview – Measurement Computing WaveBook rev.3.0 User Manual
Page 115
WaveBook User’s Manual,
5-20-99
PostView 6-1
PostView
6
Data File Accessibility ……6-1
Starting PostView ……6-3
Toolbar ……6-4
Channel Information Region ……6-5
Menu Items ……6-6
Understanding Groups, Charts, and Channels ……6-7
Chart Setup Wizard ……6-8
Introduction ……6-8
Automatic Display Creation ……6-9
Display Configuration ……6-10
Editing a Display ……6-10
Manually Creating a Display ……6-12
PostView Timebase ……6-15
Data File Accessibility
PostView post-data-acquisition software supports several programs, including: ChartView, DaqView,
LogView, Personal DaqView, TempView, and WaveView. These six acquisition programs create data files
that can be viewed and analyzed in PostView after the acquisition has been completed.
PostView makes use of ASCII (
.txt
) or PostView Binary (
.iot
) files. However, most acquisition
programs create the data files in raw binary format (
.bin
) during the acquisition. For these programs, a
conversion of the file format must be completed before PostView can access the data. A further explanation
follows:
• Personal DaqView, DaqView, LogView, and WaveView create raw binary (
.bin
) formatted
files during the data acquisition. After the acquisition is complete, these programs convert the
.bin
formats to
.iot
or
.txt
formats (as determined by the user). PostView can then
access the re-formatted data.
• ChartView and TempView create
.iot
or
.txt
formatted data files during the acquisition.
Since PostView makes direct use of these formats, charts can be updated in “real-time” while
the acquisition is in progress.
Reference Note:
Refer to PostView's Help file for data file information relating to specific data acquisition
programs. Note that some data acquisition programs can convert data formats to
.sma
format
for Snap-Master or
.dat
for DADiSP.
This chapter is based on PostView version 3.4. PostView 3.x versions are used in 32-bit
applications, whereas PostView 2.x versions are used in 16-bit applications. The
significant differences between 2.x and 3.x versions exist at the program level and are
not visible to the user.