Can a RoboRIO be imaged with Labview and Java?

[amstrudy]

I was just wondering if the RoboRIO could be imaged with both Labview and Java because whenever I re-image it, it seems like you can only do one or the other.
Thanks!

[Joey1939]

The old cRIO had to be specially imaged for each language, but the roboRIO has just one universal image. As I understand it you can just deploy code from either LabView or Java or C++ and it will run the last code deployed.

[FlamingSpork]

You will have to install Java on the RoboRIO if you want to run Java code.
http://wpilib.screenstepslive.com/s/...ller-java-only

I know that if you install Java you can still run C++ code, and I haven't tested with LabView.

[Greg McKaskle]

LabVIEW runtime, vision libs, and C runtime is on the default image.

Greg McKaskle

[HolyHacker335]

Originally Posted by Greg McKaskle

LabVIEW runtime, vision libs, and C runtime is on the default image.

Greg McKaskle

But, if Java image is installed on roboRIO, will that overwrite the LabVIEW image? Or will they coexist? The main question: Can LabVIEW be used on a roboRIO that has the default image? Thanks.

- Dave

[nickbrickmaster]

As others have said, it's not language specific. The roboRIO runs a more versatile OS than the cRIO did, and so can run any type of compiled code, provided it knows how. It's a bit like asking "Since I have LabVIEW installed, can I still run Eclipse?".

For Java, you must have the JRE installed, but LabVIEW and C++ can be run natively/with the provided image.

[Greg McKaskle]

They will coexist.

Yes. By default, LV can be used and the runtime engine is running waiting for VIs to be loaded.

I think that Java would also be installed if the licensing issues could have been worked out.

Greg McKaskle

[jds2001]

Originally Posted by Greg McKaskle

They will coexist.
I think that Java would also be installed if the licensing issues could have been worked out.

<rant>
That will never be the case since Oracle is an evil company that doesn't have the best interests of their customers in mind. If they could have fully reversed the work that Sun did on opening up Java, I think they would have. They effectively killed any open source Solaris efforts, thereby rendering Solaris totally irrelevant, and leading many of the lead engineers to go work for someone to continue to innovate on the existing quasi-open (the CDDL is incompatible with the GPL, so no Solaris code can be integrated into, say, the Linux kernel) code base, but without any real resources to do so.
</rant>

Yeah, not having to download Java separately would be awesome! In view of the rant above, however, it's not going to happen unless an alternative Java implementation is used (OpenJDK anyone?) or NI negotiates some license with Oracle, likely for an absurd amount of money.