ADC12D1800RFRB Usb Interface packet Info

Jim,

We have a similar requirement to collect data from a WaveVision supported board. In our case we could work via the WaveVision API.  What is the procedure for obtaining the documentation?

Thanks,

    -keith

Hi Keith

I have created a short Design Note here http://e2e.ti.com/support/data_converters/high_speed_data_converters/w/design_notes/1783.aspx with the information you are looking for.

Best regards,

Jim B

Hi Jim,

Thanks very much.  This sounds like exactly what is needed. Both zip files in the design note however give me access errors (403).

Regards,

    -keith

Hi Keith

Try again now. I think I have fixed the file links.

Jim B

Jim,

Not making any progress getting this to work. Is there any possibility of getting code that will build a working example?  The framework in the docs isn't getting me there.

Thanks,

     -keith

Keith

Can you give us details of how you are using the DLL:

- what language are you building your project in?

- What operating system?

- What errors are you experiencing?

Regards,

Josh

Josh,
I am building the project in C under Windows 7 x64.  I started with the example code in Section 6 of the Programmers Guide. I am seeing a failure in the call to WvBoardEnum but haven't been able to determine what the cause of the failure is.  Wavevision runs and finds the board without any problems.
At this point I am considering loading Windows 7 x86 just to simplify the environment.
A sample program that is known to build/run and that does what the example code in the manual is showing would be a big help.

Thanks,
    -keith

Keith,

I had a similar issue, and solved it this morning.  Be sure there is a copy of the 'hardware' folder from the WaveVision application in the directory from which you launch your custom application.  The DLL has a very strong dependency on the existence of this folder, but the error message provided in the log file was not exactly helpful.  I ended up comparing DLL log files with those created by the WaveVision software, and deduced the only difference was the 'hardware' folder.  Sometimes the obvious is hard to find.

Hope that helps solve your problem.  Good luck!

Best regards,

--Ken

Ken,

Thanks very much for the pointer!  That was the problem.

    -keith

Keith,

Glad I could help!

As it turns out, that may only be the tip of the iceberg.  As long as you are running under Windows XP and using WaveVision v 5.0.5.284, you should be okay.  If you migrate to Windows 7, you'll need to get WaveVision 5.0.6.465.  If you use the wvdll.dll file from that version, you're in for a real treat.  First, the 'WvDUTInfo' structure found in 'wvdll_defs.h' has changed, and has two new members -- you can find them in the sample Python code.  Without the change, you'll get a corrupted stack because of the extra data being written.  Next, the members of the 'WvCaptureSetup' structure have changed.  What used to be placeholders are now variables that control acquisition; the default values of zero used in the old version will keep the new one from acquiring data.  Now I'm finding out that the DLL is rather slow in effecting a waveform capture, taking about 100ms each.  That doesn't bode well for my requirement of 2kHz operation, but hopefully I'll figure something out.  The aforementioned 'WvCaptureSetup' changes seem to lend themselves to multiple successive captures, but the documentation is non-existent, and the sample Python code doesn't address it.

I'll keep an eye on this thread, just in case you run into more headaches as well.  Perhaps someone at TI (NS) familiar with the DLL will jump into this thread and provide some much needed updates to the support files.  I understand it isn't a supported application, but at least having current interfaces would help avoid trial-by-fire debugging.

--KenS

Hi,

I have the same problem with my own data capture application. I'm using win7 64bit. I have copied hardware folder to my application root folder but it's still not working. In a log file there is no errors, but number of founded board equals 0.  Can anybody help me or send apllication?

Mark,

First the easy one... what version of Wave Vision do you have installed?  If it is not the latest greatest (5.0.6.x) it will not work with Win7.  The way USB drivers work in Win7 changed, and required a new DLL for the Wave Vision software.  If that's not it, perhaps you can post a skeleton of your code, showing just the essential calls; perhaps myself or another forum member can take a peek and see what's going on.

--KenS

Ken,

Thank you for your answer. I use WV5 version 5.0.6.465.

I tried to run my application with WinXP and the latest WV, but its also not working. I was looking for older version of WaveVision (5.0.4) but I couldn't find it.

My application code is the same as this in chapter 6 at Programmers' Guide to WV5_DLL API r0p9.pdf.

MarkD

Mark,

If the driver is telling you there are no devices, it makes me wonder whether the driver for your evaluation board is properly installed.  When you plug in the USB cable to your Windows PC, do you get the usual "ba-doomp" sound?  If so, everything should work; if not, something is amiss.  Also, is Wave Vision able to talk to your evaluation board?  If not, could be the driver; if so, bit of a head-scratcher.

--KenS

I think that driver is properly installed, becouse data caputring with WaveVision(5.0.6) software works fine. I get "ba-doomp" sound when I'm  plugging USB. So if I use WInXp and the lastest WV(5.0.6) everythink should work properly?

MarkD

Hi Ken, 

I am compiling code in visual studio to use DLL. I met a bunch of error LNK2001 caused by on definition member functions of Wv_API class defined in wvdllh. The thing is that I find Wv_API is defined as following, but I am unable to find the definition of __stdcall. Please kindly let me know if you met these errors before too. Thank you.

-Bridget

Hi Ken, 

In the document of DLL, Firmware: mm_fpga.c is described in Hared Boot Process, however, I am unable to find it other .c files such as usb.c. I wonder if you know where they should be ?

Thank you very much!

-Bridget

two questions about the previous concern. 

1) 

Based on Software_come.py, it looks like the member function, WvDebugModuleSetOutputFilename()  are supported in wvdll.dll, but which has been included in property/linker/general/Additional library dependencies/F:\wv5 in Visual Studio. F:\wv5 is my folder including all these files. I am using Windows 7 32-bit.  I wonder if there is any other place to include wvdll.dll? 

2) In the DLL document, there is two file, wv5.sys and wv5.inf, are required to be installed using the standard procedure for installing Windows driver. I am unable to find where wv5.sys and wv5.inf are. 

Thank you!

-Bridget