Re: cRIO Emulator?
 

bakketti,
Thanks for the reply.
Could you expand on how you imported the GRTRobot project files into your new Java Application?

I searched the help files and Google for Netbean import capabilities but am not proficient in Netbeans or Java to understand the approach. Considered copying the source files to the new product but this seemed wrong.

Thanks,
Dave Frederick

Re: cRIO Emulator?
 

Hey sorry for the slow response. Just to be clear, I was speaking originally about the frcjcss project, not GRTFramework. I haven't messed with GRTFramework at all yet. But for frcjcss, I believe I copied the java files directly into the package folder on my C drive. Netbeans will automatically recognize the files and they will show up in your project. Hope this helps.

Re: cRIO Emulator?
 

We've been a little swamped with the kick off event and all.
I decided to wander back in here and found this post.

I'm going to direct this to the attention of the lead student.

Sorry for not catching it sooner.

Documentation is everything ::rtm:: :yikes:

Re: cRIO Emulator?
 

If you guys have the time, can you also please explain the classes in the networking package? It seems like they're some sort of info communication between your dashboard computer and the robot.

However, I don't see it being implemented anywhere else in your project. I would appreciate a quick example of how I could implement it (or how you implemented it last year) if I wanted to build a custom Dashboard. (which I'm assuming it's for, right?)

Thanks!

Re: cRIO Emulator?
 

Has anyone taken a serious look at the Java Emulated Robot Tutorial provided with SunSPOT? If I recall correctly there is a mention of an option specifically for FIRST.

Re: cRIO Emulator?
 

No, the emulator that was written by these students does not interact with the dashboard or simulate the dashboard at all. I can't speak for any other project in this regard.

What it does do is produce a series of graphical objects that are used to take input in place of actual joysticks and display output results without actual electronic speed controllers like the Victors. Hence it needs no additional hardware besides the most basic computer with a mouse and keyboard.

So while there is a graphical component to it, and they even have graphing, those graphics are entirely unrelated to anything that goes on with the dashboard computer in the real world with the cRIO and the LabView control dashboard.

It's more an emulator than a simulator because while the code is very similar to the actual code for the robot in Java, it doesn't consider details like the WiFi bridges, some of the idiosyncrasies of the cRIO and it certainly doesn't have any underlying physics, kinematics or graphical simulation itself.

Its basic value is testing the processing of information from the input to the output and some very basic scenario mock up. It will never replace entirely the raw value of actual testing. However, from an educational perspective it lacks the daunting aspects of testing with real hardware. So someone can sit and tinker with it harmlessly and learn how their ideas will interact in a more controlled setting.

Re: cRIO Emulator?
 

I have seen this mentioned several times and while I can't deny that it does emulate robotics, it doesn't apparently specifically emulate the experience of programming the cRIO.

There are many packages out there that can simulate or emulate robotics within a virtual environment. Some even capable of some physics and kinematics.

Where the emulator differs with the work of these students is that it doesn't really simulate or emulate the robotics, it emulates the effort of programming the cRIO. Though currently what is available lacks the ability to simulate feedback so it is somewhat limited currently. This limitation is currently being explored because of the limits of real time operations in Java itself on most platforms. For those curious about the limitations of Java and timing please review the various issues of high resolution timers and Java game programming. The issues we have with this emulator are closely if not precisely the same.

Re: cRIO Emulator?
 

FIRST step: remove all calls to wpi libs (DigitalPin, Jaguar, Victor, etc..), and remove the libraries

then get the Sunpot sdk
Add sunspot libs (squawk_*.jar, spotlib_*.jar, etc)
start solariam, make a new emulated spot, deploy your code, and run.

Re: cRIO Emulator?
 

i've been working on one if anyone is interested...
jRIO Thread