Quote:
Originally Posted by davidc10
Thank you for checking. When certain features don't work - (as they would on a standard system) - it's hard to tell if it's a problem or by FRC design.
|
This is probably due to one of the several services we removed to free up resources that were being used on the controller that are typically unused in the FRC environment. For FRC, we essentially ignore the existance of MAX... you should too.
Quote:
Originally Posted by davidc10
Another example is Debugging a Stand-Alone Real-Time Application. I've never been able to get a connection to the cRIO to debug our code once it's been deployed as a start-up application. The connection is refused on the cRIO side.
I can do this on a PC that's set up as a Real-Time PC target, but not on the FRC cRIO. If this is by design also, (NI FRC support couldn't tell me at the time), it would be helpful to have documentation about it so as not to waste time trying to troubleshoot it.
|
We intended for this to work, but a bug crept in somewhere late in the game and we were unable to address it in time for Kickoff. I belive we intend to make it work for next year.
Quote:
Originally Posted by davidc10
Have you been able to get the Web Server up on the cRIO?
|
We had this installed and enabled on the controller during beta, but it was removed due to the resources it consumed. It was decided that there should be more available to the team code and libraries they might use. It did work well, though.
-Joe