how to display EEG signal with labview

[Dennis_Knutson]

The purpose of USB RAW is to provide much of the same functionality as the dll's you got. In some cases, the USB hardware is something designed in-house and a VISA driver is written in LabVIEW instead of in C. Sometimes, you can wring out a bit more control or performance if you write your own driver.

I think your NI-USB devices would refer to the USB-6008 you said you have.

Message Edited by Dennis Knutson on 07-09-2008 09:16 PM

[orchid]

About the NI-USB devices, it is refer tu TT-USB because when I double click it at device manager, the TT-USB Driver appear. And, I did not connect the USB 6009 to my PC. Can you teach me regarding to the VI built using wether VISA or API? I really need help

[orchid]

I am trying to do an example interruptub.vi. This error message pop up

Possible reason(s):

VISA:  (Hex 0xBFFF003A) Unable to start operation because setup is invalid (due to attributes being set to an inconsistent state).

What is it means? I have choose the USBRAW at the VISA resource name.

Then, when I try to do example USBRawControl.vi, this message pop up

Possible reason(s):

VISA:  (Hex 0xBFFF003E) Could not perform operation because of I/O error.

Also, how to setting the communication API ?

What should I do first to built my own vi? 

[orchid]

Hi there,

I am trying to do a VISA before I start with API. I have built my VI but I don't know how to see the output.Also I do not know if my VI is valid or not. Please somebody give me an idea.Here  I attach the file.

Message Edited by orchid on 07-17-2008 04:52 PM

[Dennis_Knutson]

Doubtful but possible I suppose that it supports that query. In general, it is mostly GPIB instruments that you can use the *IDN? command. Is it listed in the programming manual? Did you also create the VISA inf file with the Driver Wizard?

Message Edited by Dennis Knutson on 07-17-2008 07:37 AM

[orchid]

I am not sure about the *IDN? command is suitable with usb or not. Yes,  I have create the VISA inf with the Driver Wizard.

[Dennis_Knutson]

The command has nothing at all to do with USB. It is a command that would be documented in a programming manual for the instrument (along with all of the other commands for the instrument). You cannot just make things up to write to it.

You've never mentioned whether you have any documentation on the instrument command set beyond having the dll api. In that case, I would recomend that you look at this excellent thread on USB communication. Download a sniffer to monitor the USB communication when you use the application program from the vendor and see what else is involved in trying to use VISA to communicate with it.

I'm afraid that you might be pretty much on your own with this instrument. No one has responded as having experience with it and you have not provided any information on the api or why you have decided to take the VISA route. I looked at the vendor's web site and could not get much myself except the fact that it states the instrument is only available to licensed physicians.

[orchid]

Hi all,

I am  trying to acquire the raw data using DLL provided by the company.but he said that " for the BioGraphSpy.dll to work you need to be running BioGraph. Your application uses BioGraphSpy to get information out of it. This method allows you to use BioGraph's data recording and signal analysis functions so you don't have to write your own. The only DLL we have that bypasses BioGraph altogether is the API." What is the difference between DLL and API? Is it the same? Can you all explain what is that means?  I think the statement means that when I want to acquire the data using LabVIEW, I have to run the BioGraph software too. Am I right? I got an error when I try to do these. Can anyone give me an idea? If you want me to attach the vi that I have made, I can attach it later.

Thanks 

[Dennis_Knutson]

Everyone is still working in the dark because you still have not provided any information from the vendor. Sure, it's possible to have tow different types of dll's. It sounds like one may actually be an ActiveX interface to their software. Their api sounds like the low level communication to the device and is probably what the vendor used to create this BioGraph program. You are going to have to decide which is easier to implement since, as I said before, it does not appear anyone as used this instrument before and we have no real information on either of the two options.

[orchid]

Here I attach the dll file and the documentation provided by the vendor. Also, I attach the vi that I created. Please give me an idea how to solve this problem.

Thanks