ttl signals vs. sending receiving serial data (case 15992)

[jason_reed]

If you want to send a ttl signal with a virtual port, you might be able to by using DirectRT 2014. It has the feature of using a comport.txt function like that of MediaLab that might be compatible with virtual ports.

If you can use DirectRT 2014, I would be happy to give you more information about the details of the process.

[atran]

Hi Jason,

Thanks for your reply! If that is possible that would be great. I am guessing we would have to purchase a license for the 2014 version?

If you want to send a ttl signal with a virtual port, you might be able to by using DirectRT 2014. It has the feature of using a comport.txt function like that of MediaLab that might be compatible with virtual ports.

If you can use DirectRT 2014, I would be happy to give you more information about the details of the process.

[jason_reed]

You could download and install a trial copy of DirectRT 2014 first to see if this works. Just download a copy from the Empirisoft download page here: http://empirisoft.com/Download.aspx?index=4. Send the 14-character D-code to me at support@empirisoft.com and I can get you a free 21-day trial code.

Using DirectRT 2014, you can set up a DirectRT .csv input file to send ttl signals as normal (see http://www.empirisoft.com/directrt/h...tl_signals.htm). It doesn't matter what you type for the port address in the loc cell or the number in the time cell after the stim cell with ttl: in it.

This is because you will include a .txt file named comport.txt in the same folder as the .csv input file you create. DirectRT 2014 will ignore the values in the loc and time cells as long as the comport.txt file is in the same file folder as the .csv input file that wants to send ttl signals.

When you create your comport.txt file, you will need to define the the proper number to reflect the comport you want the computer to use to send the ttl signal. This is based off of the same functionality in MediaLab used for sending and receiving data over serial ports (for an explanation and example of the comport.txt file see http://www.empirisoft.com/medialab/h...s_features.htm).

[atran]

Hi Jason,

Thanks so much for this! So far, the TTLs are being sent using the comport file through DirectRT so this is fantastic news. One issue I am having, is that DRT also seems to continuously send the TTL 240 along with the TTL I put into the stim column of my .csv- any reason why you think that might be happening? That is, every time it sends the ttl in the stim, it also sends a ttl of 240.

Also I was hoping to use the ttlecho functionality as well, but again we have this issue with me being unable to put in an actual "loc" line. So if I am correct, I believe that if I create a ttlecho.txt file with "loc","time" it will send a TTL to that location for that time when a correct key response is pressed during a trial? Is there someway to create response-locked ttls in the .csv file instead? Or someway to manipulate the echottl.txt file to send to a COM1 address instead of actual DEC locations? Let me know! Again your help is valued and much appreciated!!

Alex

You could download and install a trial copy of DirectRT 2014 first to see if this works. Just download a copy from the Empirisoft download page here: http://empirisoft.com/Download.aspx?index=4. Send the 14-character D-code to me at support@empirisoft.com and I can get you a free 21-day trial code.

Using DirectRT 2014, you can set up a DirectRT .csv input file to send ttl signals as normal (see http://www.empirisoft.com/directrt/h...tl_signals.htm). It doesn't matter what you type for the port address in the loc cell or the number in the time cell after the stim cell with ttl: in it.

This is because you will include a .txt file named comport.txt in the same folder as the .csv input file you create. DirectRT 2014 will ignore the values in the loc and time cells as long as the comport.txt file is in the same file folder as the .csv input file that wants to send ttl signals.

When you create your comport.txt file, you will need to define the the proper number to reflect the comport you want the computer to use to send the ttl signal. This is based off of the same functionality in MediaLab used for sending and receiving data over serial ports (for an explanation and example of the comport.txt file see http://www.empirisoft.com/medialab/h...s_features.htm).

[atran]

Disregard that last post! The ttlecho.txt file works fine, I was pressing the numpad keys and it wasn't registering the stroke! Sorry, thanks again for your time!

Alex

[jason_reed]

Alex,

Will do. Let us know if you have any other questions.