EEVblog Electronics Community Forum

Products => Test Equipment => Topic started by: lylavoie on February 09, 2015, 02:46:24 am

Title: ATTEN ADS1102CAL USBTMC, Does it actually work
Post by: lylavoie on February 09, 2015, 02:46:24 am

Hello All,

Does anyone have the USBTMC interface working on this scope?  It seems like it only responds to the *IDN? command only.  All other commands don't seem to return anything correctly.  I've been testing this in Linux, using both the Agilent open source usbtmc driver and the National Instruments NI-VISA drivers, same behavior in both cases.

I am using the commands from the Siglent programming manual, which should be the same between the two scopes.  There doesn't seem to be a ATTEN programming manual anywhere on the net.

Cheers,
Lincoln

Title: Re: ATTEN ADS1102CAL USBTMC, Does it actually work
Post by: tautech on February 09, 2015, 03:23:54 am

Welcome to the forum.

I have some ADS software kicking around, PM me and I'll have a rat through my archives.

Title: Re: ATTEN ADS1102CAL USBTMC, Does it actually work
Post by: tautech on February 10, 2015, 08:09:39 am

Looking through my old stuff, the drivers are very different to that used by Siglent today.
There has also been a change in HW, older DSO's need Easyscope 3 and later Easyscope X.

I no longer have any Atten DSO's so can't test anything for you.

I also remember there where Easyscope connection problems with the English version but the Chinese worked fine.
The DSO would not connect to show the green button when connected.
Solution was to edit the "Lang=" line in IIRC the .ini file from CN to EN in the Chinese software.

The last versions I have also include 32 & 64 bit USB drivers as attached below.

I'll send you the driver files as you have PM'ed your email.

Edit
Well you bloody Gmail won't accept inf, sys or rar files so I'll post them here....stand by.

Title: Re: ATTEN ADS1102CAL USBTMC, Does it actually work
Post by: lylavoie on February 17, 2015, 04:49:48 am

Hi All,

So, I finally found a combination of windows drivers and Easy Scope X that seem to work with the scope.  However, using the USB sniffer, I can see the standard commands are being modified in strange ways.  I've confirmed this in using the Linux USBTMC interface and sending the commands (to which the scope responds).  See below for the list of commands I've pulled so far.

So, the question is, does anyone have any idea why/what the "magic" bytes are before each command or where they come from?

Cheers,
Lincoln

============================================
Below are the commands with the "extra" bytes in front.
These are as sent to the scope via USBTMC.
============================================
D9F9FFFFSTOP
2AFAFFFFRUN
FCF9FFFF*RST
D8F7FFFFC1: PAVA? RMS
94F7FFFFC1: PAVA? PKPK
F1F7FFFFC1: PAVA? ALL
D7F7FFFFC2: PAVA? RMS
93F7FFFFC2: PAVA? PKPK
F0F7FFFFC2: PAVA? ALL
F2F9FFFFASET
51F9FFFFACAL ON
13F9FFFFACAL OFF
CFF9FFFFACAL?
9BF9FFFFWFSU?
2FF8FFFFWFSU NP,1000
BBF8FFFFWFSU SP,0
B7F8FFFFWFSU SP,4
75F9FFFFC1: WF?
74F9FFFFC2: WF?