Solved! Go to Solution.
I am also hanging out for the manual for the 9606!
But with regards to the max freq of the DIO I would assume it would be very high as the DIO is connected directly to the FPGA and hence would be mostly limited by your program and what type of data you are acquiring.
Glad to see that the new SB-RIOs are so hotly anticipated! Since I don't really know off the top of my head, and I'm not sure if we are fully ready to release that info, I'll have to check around before I can give you an answer.
I can take the answer under NDA or restricted circulation as an Alliance member. Confirmation that it's directly tied to the FPGA unlike the existing sbRIO would help too.
@SolarSystemsLLC You don’t need an NDA bro, just read the product overview... http://sine.ni.com/nips/cds/view/p/lang/en/nid/210
"Mezzanine Card connector, which is a high-speed, high-bandwidth connector that provides direct access to the processor and 96 3.3 V digital I/O FPGA lines."
The digital I/O on the RMC (RIO Mezzanine Card) connector is directly connected to the FPGA. DIO signals should be routed with 55 ohm characteristic trace impedance to reduce impedance mismatches and unwanted reflections. The FPGA pins are connected to the connector via a 33 Ohm series termination resistor. Since the RMC connector is directly connected to the FPGA, this means that the DIO's frequency is directly related to what you can compile in your FPGA code. More information on this will become available when the manual is released.
Please bear with us as we are still working through final edits to the manual before we post it to the web. As Andrew mentioned in an earlier post the RMC DIO is directly connected to the FPGA through a 33 ohm series termination resistor and the DIO signals are routed with 55ohm characteristic trace impedance. There is no buffer in line. In regards to a maximum frequency specification, the DIO capabilities are bounded by the components on a RMC board, signal integrity between the FPGA and the RMC, and any application specific timing requirements. In general, a typical SPI based protocol would be able to close timing with a 10MHz interface rate. If the applicaiton does not have timing requirements between lines, than you'll likely be able to toggle or sample the lines at a higher rate. Since the design of RMCs is completely open, the signal integrity and timing for any design should be validated by the designer.
I've made a note to update this post when the manual goes live so you'll be aware that its been published.
sbRIO-9605/9606 Project Manager
We did take into account trace matching the DIO lines. Our final documentation will provide a max channel to channel skew number for timing calculations.