Elset

Possibly related to this?

FYI Discussion continues on the next page of that thread as well.

A CAR has been issued regarding the changed behavior

http://forums.ni.com/t5/LabVIEW/right-click-menu-selection/td-p/2133354

I disagree with the idea of dual development (Java and LabVIEW). Like I mentioned earlier, your test time on the competition robot will be very short. Testing two different programs will be difficult and it will take away practice time from your drivers.

We built two robots. Between the time the first one is (mostly) complete and tested and the first bagging we build the second one. This allows us not only to refine the mechanics, but gives software more time to develop, and plenty of time for the drivers to practice as well.

Having spoken with a mentor of the HOT team (67) just before St. Louis 2011, they do this as well (2 robots, 2 languages). If memory serves, the main team featured in The New Cool also builds a second robot, though only one programming language is used. (That season anyway)

Again, this depends a lot on resources. Both students, mentors, and of course, funds.

If your team has the resources to do both, do both. The team I mentored did both a C++ and LabVIEW robot. They would alternate which code base they used each competition. Additionally, depending again on resources, develop some side projects using each language. For instance, if you're stronger in Java, use that for the main robot, but develop a separate robot (a t-shirt launcher is what we did) using the alternative.

The obvious upshoot of either of these is that you get more students involved, which is what FIRST is about.

That only had 9 Kudos and it got implemented? I guess there's hope for any feature request.

I think it got implemented independent of Ravens' idea. It seems unrecognized by NI. Usually they will mark ideas as completed, but this has been untouched.

I don't have any real answer for you, but if you add a wait of a couple of seconds between opening the FP and running the VI the error doesn't occur.

Thanks a lot!

Hey everyone. I made a post a few days ago on the NI Forums (here) because I am having some trouble creating my first XControl.

I decided to come here to see if any LAVA specific users have any insight

Here's my progress so far:

I've simplified the actual implementation to the XControl so you can test it if you please.

Show Plot is the VI you want to run. It will call Plot dynamically, which is where the XControl is. There are directions on Show Plot's front panel. I don't think I've left any subvi's out.

XControl Test.zip

Could you use an UNC path of the form \\ComputerName\SharedFolder\Resource

Something like:

 \\192.168.1.1\LabVIEW\temp.txt

I think you can also do

 \\ComputerName\LabVIEW\temp.txt