Topic: FMC-104 Trigger Input Questions  (Read 43982 times)

norume February 04, 2015, 05:51 PM

  • Member
  • *
  • Posts: 13
I have some FMC-104 modules that I'm using to measure the charge in the Advanced Light Source storage ring bunches.  This is working well, but I'd now like to use the trigger input as well.  I can see the signal making it on to the board by looking at the connector solder point with an oscilloscope.  But the signal read by the ML-605 FPGA is always 1.  Is the FMC-104 documentation showing the trigger to FPGA on LPC connector pin G37 correct?

iklink February 05, 2015, 05:32 AM (#1)

  • 4DSP Staff (EU)
  • Member
  • *
  • Posts: 153
Dear,


I double checked the trigger connection to the FMC connector and it connects indeed to G37. Probably your ML605 sets VADJ to 2.5V? For this voltage level, trigger input Vih > 1.7V and Vil < 0.7V, with a input voltage range of 0V to +5V. Could you double check that you apply to correct voltage? Is the FMC104 plugged onto the LPC or HPC connector of the ML605?


Best regards,
Ingmar van Klink
4DSP




norume February 05, 2015, 01:45 PM (#2)

  • Member
  • *
  • Posts: 13
Yes, the FPGA I/O pins are configured as:
NET TRIGGER_FROM_FMC LOC = "K31" | IOSTANDARD = "LVCMOS25";
The signal at the printed circuit board pin of the "TR" SSMC connector is a pulse starting from <0.1V, going to 2.5V for about 100 ns, then returning to <0.1V.
I am using the ML-605 LPC connector (J63).
Perhaps I have a broken ML-605 or FMC-104.....

norume February 05, 2015, 03:55 PM (#3)

  • Member
  • *
  • Posts: 13
Tried a different ML-605.  I see triggers.  Must have been a bad unit.
Sorry for the bother.
    and thanks for the quick reply!

arnaudNL February 06, 2015, 05:54 AM (#4)

  • 4DSP Staff (EU)
  • Administrator
  • Member
  • *****
  • Posts: 7110
Dear Sir,


Thank you for the feedback! Feel free to create new topics when you need to do so.


Best Regards,
Arnaud

arnaudNL February 06, 2015, 05:54 AM (#5)

  • 4DSP Staff (EU)
  • Administrator
  • Member
  • *****
  • Posts: 7110
This topic is being closed because the issue is considered as resolved by 4DSP. Feel free to create a new topic for any further inquiries.