2009 Control System Feature Wishlist

[Daniel_LaFleur]

Originally Posted by jhersh

The primary reason that the cRIO doesn't have USB is that, for industrial automation and control (the primary market), USB is rarely used. If a USB interface is needed, then a solution like I described above must be employed.
<<SNIP>>
-Joe

This actually surprises me, considering the number of USB DAQ devices ( like this, and this) entering the market. Attaching a simple driver circuit (either voltage or current) to one of the USB DAQ DOs allows for control of most pneumatic systems and some DC motors (single directional / single speed) while the limited AOs can control many of the more sophisticated motor systems.

Not to mention the sheer number of other USB devices that the cRio could control (Enviromental control and monitoring, control feedback through DAQs, Logic instrumentation, ocilliscope signals, etc) and all through a common port (latency, timing, and bandwidth would be an issue on the higher end devices).

This would seem to me to be an easy way to expand the cRio's capabilities while keeping the cost to the end user down.

JMHO