Comments/Complaints on NI control system

[apalrd]

Originally Posted by Schnabel

Issues!!! Last time I checked, the best way to solve issues was to try to find a fix, not complain about them until someone else tried to find a solution. This is great experience to trying to solve the issues ourselves.

As most of my problems are on the Classmate end, I have exactly no control over it. It has bugs, but I have no source code to modify and fix it. The fixes I have take too long to implement (e.g. rebooting twice when loosing Cypress IO), or are way more difficult than they should be (e.g. tearing apart a USB joystick that dosen't have an auto-centering axis and soldering all of my IO to that) As for the NI controller, other than the long times I like it very much. Most of the problems with it (ejecting modules) can be fixed with duck tape and such, and I really like the ability to probe things while they are running. The cRio is not the majority of the problem, it is the rest of the system implemented to make it work. Many of my complaints are on the Classmate end.

@Greg: That thing I mentioned about probes, it isn't a problem to have a probe open while the code loads, but it is a problem to place a probe while waiting for code. It seems to be a bug in LabVIEW RT, not the FRC specific software.