Sending triggers via serial

Builder
1

I am having some issues sending triggers via serial port

I am connected to a Lumo fNIR using their supplied USB serial port cable. I have the FTDI drivers installed for the cable to work. I have checked the device manager, and it registers the cable as COM3 and recognizes it as a serial device.

I have followed the instructions on the PsychoPy page for the serial port device (both using the component or just code) and it doesn’t send a trigger. I have the Lumo device set to record, and it apparently marks the triggers with a white line. I have been unable to make this line appear.

Some questions to help me:

Is there a way to test that a serial trigger is sending from one PC to another?

Which “parity” option should I be using?

Is there a serial trigger demo I can use to test?

Any help would be great.

Thank you

3

Hi There, are you using tghe new “serial” :serial: component?

Becca

4

I tried with the serial component and also with code and I’ve been unable to send a trigger

5

Hi @Jdigg,

The parity setting is an error checking procedure, in this case setting it to None or Off is fine. You can read more about it here (other articles are available - this is just one I found that seems to explain it well!).

As you’re receiving no errors, what is usually happening here is an address error. But it sounds like you have the correct address from what you’ve said here. I’ve not worked with a Lumo device before, but are there certain bytes it’s expecting to receive as a trigger? For example a string, character or an integer within a certain range? This information should be provided within the documentation for the device somewhere.

Also, how long are you setting the pulse for? By that I mean what is the stop duration in the Basic tab of your serial port component?

There is a demo here (attached), but this has the default address and start/stop values etc., you can just change these to match your address. It might be worth trying different USB slots if you have them available, and also checking that the baudrate value is correct (again this should be in the documentation for your device).

So sorry that I’m not being more specific here, every device and set-up is slightly different so it’s difficult to say what could be happening!

Thanks,

Kim
trigger_test.psyexp (13.4 KB)

6

Hi all,

So I tried the various means here and unfortunately I’ve had no luck. I did find a way to send serial triggers via command prompt, to see if I could eliminate it being a PsychoPy issue. This also didn’t work, so I’m not sure if it’s a sending issue with the experiment PC or a receiving issue with the Lumo PC.

Does anyone know of any programs or scripts I could run which can display sent trigger codes for the receiving end?

7

Okay so this was a huge user error on my part in the end! I am so used to parallel ports, where all of the settings are the same.

I was setting both computers to COM3, however the LUMO PC was actually COM5.

8

Hi @Jdigg,

Oh phew, I’m so pleased that you’ve solved the issue! I’ve been digging around looking at this in the background but could not figure out what was going on!

If you do need any further help with anything now that you have the triggers coming through, do let us know!

Thanks,

Kim

9

Hi,

I’m currently in the process of setting up an experiment using LUMO, and I was wondering if your experiment was successful. If it was and you’re comfortable sharing, would you mind providing any insights or details from your setup? I believe it would be incredibly helpful as I work on my own setup.

Thank you very much for considering.
Best