We sucessfully developed a test for a Fire Control Radar Transmitter from the ground up using TestStand in only 3 months. This was rebuild to replace a tester and program written in C. The original took close to 3 years to build because of the nature of text programming. I've noticed that it's very hard to convince engineers to move away from text programming and I feel that it's mainly because the way code is written is different and they're very convinced that text is the only way to go. If you either disable the tracing function, or move the tracing sliding bar to full speed, the sequence runs very quickly on a decent machine. The only slowdowns that I've noticed happen when communicating with some instruments, and that's because it's waiting for status byte returns from the instrument, so it's the instrument slowing the sequence, not TestStand.
Why do geeks think Halloween and Christmas occur on the same day?
Because 31oct = 25dec!
