DIO for laser enable signals

[JustinLangridge]

We have now got the lasers configured to work with a 5V laser enable signal, but the laser enable signals are coming out of the wrong cards. Please could they be changed to the following to match up with the hardware:

CRD Red laser output: 6225(2), P1.5 CRD blue laser 0: 6225(2), P1.6 CRD blue laser 1: 6225(2), P1.7

The PAS laser enables for cells 0-4 should run on the 7842R (1) on DIO5-9.

[lo-co]

Sent an email on this regarding switch states. I think that Dave or Stuart should have no problem updating this. Remember to do the following:

• Export the current MAX config file and place the .nce file either in support or the main directory (currently resides in main directory bu this is a bad place to be).
• Check the current one into the repo and reference this issue.
• Update the MAX config file and export again
• Update the signals file
• Check this new one into the repo and tag the commit message with Closes #117

[lo-co]

Something about this isn't right. The signals in MAX are properly routed. From the manual:

• Ctr 0 Out is PFI 12 or pin 2; this is P2.4
• Ctr 1 Out is PFI 13 or pin 40; this P2.5

Two points that are important that I outlined a long time ago:

1. The signals must come from the counters defined above. They require this because of gating and some signal connections that are made across the backplane of the PXI. If you all want to change this in software, go ahead. But this is far beyond the scope of the work outlined and goes against the original plan (I have this outlined in the signals list)
2. The two blues are tied to one output. I have been saying this from the beginning and it was agreed to a long time ago. Once again, you can change this but this is beyond the scope of the current work.

Look at MAX and notice that the card the outputs are tied to is called CRD_HK - this is exactly why I named them this. I am closing this issue as it is neither a bug nor within the scope of the present work to change this. This is a hardware issue, not a software issue. PLEASE DO NOT ATTEMPT TO "FIX" THIS ISSUE AS YOU WILL BREAK A LOT OF STUFF!" (as has happened with the CRD AI which I can not figure out what you all did with this to cause havok with the return)

[lo-co]

I realize that this looks like that this only is related to a simple output, but I route these timers so that we gate the signals appropriately for the AI and don't have to take 2.5-4 MS/s/ch. This would be a killer, even on the machine that you all have.

[lo-co]

OK. Forget everything that I have said above. This is the enable, not the DIO for the actual laser driving. Will fix this.