[Aaron.Graeve]

Originally Posted by Fletch1373

As a CSA at champs, I had plenty of opportunities to play with the roboRIO that NI had set up. One of these tests was a boot time test. With a stopwatch app, we discovered that it still takes approximately 22 secs to boot to a state where the networking process is running, and an additional 3-4 seconds(totalling ~25s) for user code to finish loading. This was done with 2014 cRIO firmware ported to the roboRIO, and as such, isnt a perfect representation of how it will work next year.

Was this test run with the roboRIO powering up or was it already on (i.e. hard reboot vs soft reboot)? Did the test you see require a full reboot after loading code? My message was more directed at the time to load and run code after the roboRIO is already running and was based on what I have heard. I wanted to be at Champs this year so I could talk to some of the alpha testing teams in person, but college work prevented me.

Even considering, a ~25 seconds from boot to code running is very nice and better than what we have now. I have hope the roboRIO firmware will reduce this time even further. (Keeping my fingers crossed for user code in user space)