Is it possible to send TTL triggers (different numbers for different conditions) from Experiment Builder to Lab View? how can i read this info in the .cnt file?

[josherr]

I am sending TTL triggers from Experiment Builder (EB) to Lab View (LV). I am sending TTL 1 for condition 1, TTL 2 for condtion 2, etc. This is no problem from EB side but i cant see this info in the .cnt file. The only way i have so far to code different conditions is to send TTLs of different length (cond 1 is 5ms long pulse , and cond 2 is 10ms long pulse). Anybody knows how to send numbers from EB to LV such that i can access that info in the .cnt file for example?

[Mockingbird]

Hi,

I was wondering if you could give me a bit more information about your application. First of, I can't seem to find the program that you are trying to use. Can you give me a bit more information about what Experiment Builder (EB) is? Also, what information are you trying to find in the *.cnt file? As far as I know, that is a windows help contents file extension. Are you trying to read in DIO lines into LabVIEW (for the TTL signals) or are you trying to do something more?

[josherr]

Hi Gabriel,

EB is from SR Research (www.sr-support.com).

Yes, I am trying to read in DIO lines into LabVIEW for the TTL signals. I'm sending TTLs from EB but the only thing i managed to read succesfully is the lenght of the trigger pulse. That is when I add the .cnt extenxion to the LV file and I read it into matlab using eeg_load_scan_cnt function , I can see the length of the TTLs triggers. However, when i send numbers for each TTL (rather than length of TTL), i am not  able to see it. I've noticed that LV can produce @v files with addtional info. How can i do that?

thanks 

[Mockingbird]

Hi,

unfortunately I'm not quite sure what you are talking about. Where have you seen an @v file before? Also, what do you mean by adding the .cnt extention to the LabVIEW file. If this is a MATLAB issue then you may be better served posting on their forums.

MATLAB® is a registered trademark of The MathWorks, Inc.

[Dennis_Knutson]

josherr,

First, your link is bad and once that is fixed, you go to a site that requires a login and hence, no one can read what is there. You then mention a file extension that has nothing to do with LabVIEW. Prior to your post, there has never been any reference to this ' Experiment Builder'. Your post is extremely confusing. Are you talking about some sort of hardware that is generating the triggers? Are you attempting to use LabVIEW and other hardware to detect them?