Quote:
Originally Posted by oddjob
Has anyone considered contributing to this:
WPILib test harness
For most all teams, there is one or maybe two cRIO's and limited access to the hardware in the final weeks as the robot is approaching fully constructed. Access to a virtual cRIO platform would be very useful.
Investigating cheaper hardware options, there's nothing bad about that.
If the code runs on Windows, Linux or OS/2 or whatever, I couldn't care less as long as there is the C++/Labview/Java programmers environment and robot comms interface. |
As the original author of the WPILib Test Harness, a lot of the stuff that is being discussed in this thread was my motivation for writing it originally. In particular, I was highly annoyed that I couldn't do any code development outside of the cRio. However, I haven't had the time to actually do any work on it this season -- but maybe this summer or something.
The WPILib Test Harness is currently C++ specific. I thought I saw someone mention that the Java code can be ran outside of the cRio, but don't quote me on that. Running LabVIEW outside of the cRio without NI support would be an exercise in futility.
One of the lessons learned from working on this, was that WPILib is *very* platform specific underneath the hood. Trying to port it in its existing state without some major rewrites would be very time consuming.
As far as OS primitives and multithreading, I've elected to use the boost threading libraries for that. It's a bit more than what some people like using, but it works pretty well and is quite cross-platform. It would be really nice to see FRC ship boost by default with the development environment.. but of course, there are a lot of caveats there.
