Hi Anne,
You might not need to worry about much of this. From what I understand, you would like to the number of inputs in a given period of time so you can graph the output. Let me know if I'm wrong, but you want to how many of your pulses fall into a small period of time and you want to be able to graph a continuous spectrum of these values. So for example, you can measure the number of pulses that occur every 1ms so that you can graph an output with a resolution of 1ms. Lets say you get 15 pulses in the first 1ms interval and then 27 in the next and so on... you can build a graph from these data points. Is this correct?
What is the period of time you want to measure photons (1ms, 10ms etc.)? Because this should be the rate at which your first pulse train generates at. The second issue is that you want to read all this data every 10s. This means you would need a counter buffer larger enough to store roughly 20s worth of data. You would also need to change the "counts to read at a time" terminal to 10s/1ms = 10,000 counts (if your period of sampling the number of photons in a period is 1ms). That being said, the only 3 things you really need to change is your buffer size (instead of 1000 use 20s/1ms = 20000), your counts to read at a time (instead of 1 use 10000) and finally, add a wait until next ms multiple VI in your buffer read loop that will wait almost 10s. This is to prevent your system from locking on the Counter Read Buffer.vi.
A more efficient way to do this is to wait 100ms in your buffer loop and use 2 Counter Read Buffer VIs. The first one will read 0 counts to read at a time. You will want to monitor the "scan backlog" terminal to see if it is greater than 10,000 (10s worth of data). If it is, then use the 2nd Counter Read Buffer.vi to read 10000 points. But if it is not greater, you will not want to read points from the buffer yet. You can use a case statement to accomplish this task (if true read 10000 points, if false don't do anything).
Anyway, I hope that helps you out. Have a good day.
Ron