Comments/Complaints on NI control system

[Greg McKaskle]

That's not what I was talking about...

Consider that the boot times of the cRIO are very similar to last year. The build times for LV at least are smaller, and often significantly less. A new language was added and a new DS was added. With change comes the potential for unforeseen issues.

At this point it seems like the dropout of USB devices may be related to connecting the devices through the hub in a way that draws more power than USB can supply. I thought the documentation recommended that the Cypress FT board be plugged directly into one USB port and the hub and other devices into the other. Can anyone verify if that is in the documentation? Whatever the cause, this is the top issue being investigated.

There are also reports of the Cypress board not working after a suspend or when booted on the field. This is probably the next highest priority issue. Data on the driver being used as well as the steps to reproduce would be very helpful as I personally have not been able to reproduce this.

If other issues arise, they will be compared and investigated as well. Unless a performance issue has a dumb-simple solution, it really isn't feasible to change it at this point in the season. I'd love to be able to ride in on a white horse and explain how you can now boot in negative 5 seconds, deploy code without having to turn the controller on, etc. That isn't going to happen no matter how many times you repeat your points.

Knowing what you'd like to see improved in the system is very useful. Thanks. It would also be useful to use the correct name of the system -- once again, it isn't the NI control system.

Greg McKaskle