tkds30xx doesn't recognize TDS 3032B

[meverest]

I'm using LV 6.1 and the tkds30xx drivers for that version to control a TDS 3032B scope. Everything works fine, but the initialize vi always gives an error if the "ID query" is set to true. Did someone forget to include this particular scope in the driver or am I doing something wrong?

[Labviewguru]

The driver may have been created before Textronix released the 3032B, which may have a different command for the ID Query.) Try using MAX to communicate directly to the scope to test the ID inquiry.

Also, check your manual (you do have a programming manual for the scope of course) and see what the command is. You may have to open the Initialize.vi and see what command is being sent.

[DougD]

Often times this is not really a big deal to fix. Don't let it scare
you that the VI didn't recognize your unit.

The command which initializes the connection will send an *IDN? to
your instrument to which it will respond with an ID string that
includes TDS3032B or something similar. The VI will then try to parse
that string and compare it to an array of known valid units at the
time that the original VI developer coded the VI.

If your model is not in that array but otherwise the commands are more
or less the same between your newer unit and the older models, all you
will have to do is add your model to the array that the original
programmer put into the VI to get it to recognize the unit.

If additional functionality has been added to your newer model (very
likely) then you will need to write code to support that functionality
IF you are using that new functionality. If you aren't going to use
the new functions, then you don't care and you can use the VI's that
support the old functionality.

If some functionality has been changed between the new and old models,
then you will need to carefully compare the back panels of the VI's to
the programmers command manual which generally uses the SCPI protocol
but not always.

Often times because of the SCPI protocol, you can start with the
drivers from an older unit or a similar unit and leverage these VI's
to create the functions that you need for a new unit.


Douglas De Clue
LabVIEW developer
ddeclue@bellsouth.net


Labviewguru wrote in message news:<506500000005000000F88A0000-1023576873000@exchange.ni.com>...
> The driver may have been created before Textronix released the 3032B,
> which may have a different command for the ID Query.) Try using MAX
> to communicate directly to the scope to test the ID inquiry.
>
> Also, check your manual (you do have a programming manual for the
> scope of course) and see what the command is. You may have to open
> the Initialize.vi and see what command is being sent.

[btejani]

meverest,

Please make sure you have the latest version of the tkds30xx driver, since it has been updated multiple times in the last few months.

If you do have the latest version, then please use NI-Spy to log the I/O between the computer & instrument while you run tkds30xx Initialize or tkds30xx Initialize With Options. Then either post that log file here on Developer Exchange, or send it to instrument.driver@ni.com. That will help us isolate the problem.

Thanks,
--Bankim

Bankim Tejani
National Instruments

[wha@atmel]

Hi,

I had the same problem with TDS 7054 - no driver available; I took the one from tds7xx. Look in attached program, how I solved your specific problem....

regards
wha