Is there a maximum number of triggers allowed in E-Prime 2.0 Professional?
136 views
Skip to first unread message
Jenna Luque
Sep 10, 2015, 2:52:15 PM9/10/15
to E-Prime
Hello: I am a PhD student about to conduct my first ERP experiment using E-Prime. I originally set up my experiment using E-Prime 1, but then we got new lab space with new software, and I am currently changing it over to E-Prime 2.0 Professional. I have a lot of triggers (1-72, 101-112, 201-212, 301-312, 401-412, 501-512). In E-Prime 1 this was not a problem. However, in E-Prime 2, only triggers below 212 show up; the others get changed into some other number (that seems random to me) below 300. Is there an upper limit in terms of how high triggers can go in E-Prime 2? I changed my numbers above 301 to single digits, and then they were correct in the ERP output. It seems like the problem must be tied to the numbers I used, but I cannot seem to find a limit online. Thanks for any help you can give! - Jen
Ben Robinson
Sep 10, 2015, 3:17:28 PM9/10/15
to eprime
How are you sending these triggers? My experience sending them through parallel port was always that you couldn't send any trigger with a value greater than 255.
On Thu, Sep 10, 2015 at 2:52 PM, Jenna Luque <slpj...@gmail.com> wrote:
Hello: I am a PhD student about to conduct my first ERP experiment using E-Prime. I originally set up my experiment using E-Prime 1, but then we got new lab space with new software, and I am currently changing it over to E-Prime 2.0 Professional. I have a lot of triggers (1-72, 101-112, 201-212, 301-312, 401-412, 501-512). In E-Prime 1 this was not a problem. However, in E-Prime 2, only triggers below 212 show up; the others get changed into some other number (that seems random to me) below 300. Is there an upper limit in terms of how high triggers can go in E-Prime 2? I changed my numbers above 301 to single digits, and then they were correct in the ERP output. It seems like the problem must be tied to the numbers I used, but I cannot seem to find a limit online. Thanks for any help you can give! - Jen
--
You received this message because you are subscribed to the Google Groups "E-Prime" group.
To unsubscribe from this group and stop receiving emails from it, send an email to e-prime+u...@googlegroups.com.
To post to this group, send email to e-p...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/e-prime/da7d1b45-ee0f-4724-bdaa-ccafd7e5b862%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
David McFarlane
Sep 10, 2015, 4:47:44 PM9/10/15
to e-p...@googlegroups.com
Jen,
I second Ben's reply. Here's a bit more explanation ...
Typically, trigger values are sent through an 8-bit port, which
allows values from 0 to 255 (&h00 to &hFF). If you were successfully
outputting higher trigger values, then you must have been using a
special port that outputs, say, 16 bits (values 0 to 65,535, or
&h0000 to &hFFFF). If you try to output 16-bit values through only 8
bits, you will only get the lower 8 bits, which may explain your
"random" output values.
So first we need to know what hardware you used for outputting those values.
Then we need to know how you program those triggers. WritePort in
inline code? stimulus.OnsetSignalData? According to the E-Basic
Help for EP1, WritePort takes Integer (16-bit) values, but it is not
clear whether it will output all 16 bits; OnsetSignalData takes Long
(32-bit) values, but only outputs the lower 8 bits.
Finally, if you are upgrading to a recent version of EP2 *Pro*
(2.0.10 or later), and if your output port is fully supported, then
you should think about revising your program to use the new Task
Events feature, which will almost certainly do a better job than how
your old EP1 program works. In that case, make sure that you set the
Data Type to Integer or Long (not Byte) in order to allow more than 8
bit values.
-----
David McFarlane
E-Prime training
online: http://psychology.msu.edu/Workshops_Courses/eprime.aspx
Twitter: @EPrimeMaster (https://twitter.com/EPrimeMaster)
I second Ben's reply. Here's a bit more explanation ...
Typically, trigger values are sent through an 8-bit port, which
allows values from 0 to 255 (&h00 to &hFF). If you were successfully
outputting higher trigger values, then you must have been using a
special port that outputs, say, 16 bits (values 0 to 65,535, or
&h0000 to &hFFFF). If you try to output 16-bit values through only 8
bits, you will only get the lower 8 bits, which may explain your
"random" output values.
So first we need to know what hardware you used for outputting those values.
Then we need to know how you program those triggers. WritePort in
inline code? stimulus.OnsetSignalData? According to the E-Basic
Help for EP1, WritePort takes Integer (16-bit) values, but it is not
clear whether it will output all 16 bits; OnsetSignalData takes Long
(32-bit) values, but only outputs the lower 8 bits.
Finally, if you are upgrading to a recent version of EP2 *Pro*
(2.0.10 or later), and if your output port is fully supported, then
you should think about revising your program to use the new Task
Events feature, which will almost certainly do a better job than how
your old EP1 program works. In that case, make sure that you set the
Data Type to Integer or Long (not Byte) in order to allow more than 8
bit values.
-----
David McFarlane
E-Prime training
online: http://psychology.msu.edu/Workshops_Courses/eprime.aspx
Twitter: @EPrimeMaster (https://twitter.com/EPrimeMaster)
Jenna Luque
Sep 10, 2015, 6:58:55 PM9/10/15
to E-Prime
Thanks to both Ben and David. I am super great at computers, but my advisor suggested the triggers were being sent through a USB drive. Not sure if that is an option. I will lower my numbers to 255 since that seems to be agreed upon as more normal. I appreciate both of your responses very much. Thanks again!
-Jen
Reply all
Reply to author
Forward
0 new messages