As kdoelling1919 notes in this github issue, sending multiple serial port triggers in the same routine fails on all but the first trigger. I am confirming this is also the case for the parallel port (I’m using Parallel port PCIe card).
In that issue, TEParsons notes that the new Device Manager should provide a way to handle this. In my PsychoPy Device Manager, however, the parallel port is not listed as an available device (despite the fact that the Parallel Out component can communicate with the port).
Is the Device Manager not yet ready for managing ports? Or is there something I should do to add a port to the list?
(I also have access to Serial Port, but have not yet tried if this works with Device Manager – but please let me know if I should.)
To send triggers right now, I’m using a work around via code components, wherein I reset the status of the trigger component immediately after sending the trigger, so it doesn’t block subsequent triggers.
Have you tried this, I spent a LONG time figuring out the issues with parallel ports and psychopy. In windows 10 and earlier, the same steps need to be taken.
I am currently running parallel ports triggers in a routine, multiple times with no issues using psychopy 2024.2.4 and 2025.2.3.
yes I did see your post originally – it helped me get the parallel port communication working. Thank you!
For posterity, not long after posting my previous message, I realized I could not actually reproduce the issue with parallel ports – so, false alarm there. However the serial port was still subject to the issue with multiple triggers. I’ve switched entirely to parallel port (thanks in part to @stanley101’s workflow)