Leaderboard

...if I'm lucky I'll get to keep my man card. I just received a cRIO and miscellaneous hardware for a new project I'm starting for a client. Included several strain relief kits were included for 2 and 4 position screw terminals. Simple little two piece plastic shells to go around the terminal blocks, right? Yeah... it took me 15 minutes of fiddling around to figure out how they mate up.

Don't you mean "Beautifully Admirable Sadistic Tendencies And Radical Diatribes"?

"Barely imperceptible sadistic tendencies."

This should be item #1 in your list. The other two are possible because you do this first. Dependency Management: For larger applications this is the most important requirement few people ever consider. [Note to Elijah: Time to write another article.]

For the Discovery Channel Telescope software, we make extensive use of libraries and classes. We never have this issue when editing classes. Perhaps what helps make this possible is 1. Programming to an interface, not an implementation: Abstract classes with pure virtual methods separate almost every call layer. 2. For each software component we do development work within several small lvprojs (with few dependencies), then only one large project from which we do builds but typically no development work. 3. Architect to avoid overly-complicated dependencies.

The stock controls don't have the capability you're looking for. Other options: trap the value change event, and if you see the "rollaround", change the value back. Hide the up/down arrows and place your own buttons on there to increment/decrement the value I am, of course, assuming you're using an event structure.

In the simplest of solutions, you could use a matrix switch to route your four USB lines to each DUT. NI has some Ethernet-based hardware that you could use to pull this off, I think. We have had to do USB switching before, and used the J-Works SSB118. However, it doesn't fulfill your Ethernet requirement. As for 1-to-all versus 1-to-1, I don't think the former would work because each host (your DUT) expects that only one host will be on the bus - there would probably be a mess of collisions if you plug x DUTs into one dongle.