Possible bug in "Tektronix DPO MSO 2000 4000 Series" driver package (5.0.2)

[Stinus Olsen]

Hi

I'm currently developing a custom steptype for the DPO4034 model for TestStand use and noticed some inconsistencies in the way the channels in the driver VIs are handled.

More specifically this happens in the "Fetch Waveform Measurement.vi" which passes it's text ring input "Channel" on to the subVI "Is Channel Enabled.vi".

However, the two text rings doesn't quite match in values, and so I get an error if trying to perform a measurement where the "Channel" input's value is > 5 ..

Is this a bug, or is there an explanation as to why these inputs have not been typedef'd ??

Best Regards

Stinus Olsen

[Albert.Geven]

It is not a bug, it is chosen this way that in instrument drivers no typedefs are present.

The long ago history about this, I have lost from memory but I don't like it.

My remedy is to write a LVOOP layer between a scope driver an my usage. We already did this for scopes before LVOOP existed with a lot of administration.

Now it should be easier todo. I could supply the interface we designed, but I'm missing the time to implement it myself.