Not able to use classmate PC as driver station !

[NI-Bob]

Hello Murthy,

I agree with the above post of making sure that you have reimaged the cRIO after installing the updates.

However, recently I ran into a similar issue with someone over the phone.  It was definitely a strange issue but turned out to be a relatively easy fix.  Basically what was happening is the team was logged into their Classmate as the Driver at the same time they were logged into the Developer account.  So the Driver account was already automatically running the Driver Station Application and so when they tried to run the Application in the Developer account they were not able to communicate because the Driver account already had the connection.

My recommendation is to make sure that you are only logged into one account on the Classmate and make sure there is only one Driver Station Application running.

I am working on putting together a short tutorial to address this issue and I hopefully have it posted in the near future.

Please let me know if this does not solve the issues that you are seeing and I will make sure that I get R&D to help me dive deeper into this.  I hope this helps!  Have a great day!

Thanks!

Bob H

NI FIRST Support

[murthyz]

Hello Sciencewhiz,

                                 I did reimage the cRIO after the updates.

Thanks,

Murthy

[murthyz]

Hello Bob,

                I tried using  only Driverstation account  and still  have the same problem.The Robot code and communications led are still red.Do we have to use the I/O module also  to get this thing right?. I also tried building the  default basic framework of 2010 with no user code in it and run as start up.I'm also able to get the response when I ping the cRIO,bridge and router

Thanks,

Murthy

[murthyz]

Hello Bob !

                I got my problem solved this time.Actually we had the firewall "ON" I had to disable the wireless and firewall to get the driverstation communicate with the cRIO. I actually found this info in the following post .

http://decibel.ni.com/content/thread/5603?tstart=0

Hope this helps everyone ! Thanks a ton for your support !

Regards,

Murthy

[NI-Bob]

Hello Murthy,

Just curious, but did you manually turn on the firewall on the Classmate PC.  It was my understanding that the firewall was not enabled by default on the Classmate.  I am just wondering if this is something that could be an issue with the image for the Classmate and want to make sure we are all completely aware of it to assist teams down the road.

Thank you very much for your patience on this and helping to spread the word of your experience and solution.  This is where the spirit of FIRST starts to shine through!  Have a great day!

Thanks!

Bob H

NI FIRST Support

[NI-Bob]

Hello Murthy,

Actually now that I looked into it a little bit I do believe that the firewall is enabled by default.  It may be possible that the firewall had something to do with it but I am thinking it was most likely not the firewall.  I do know that communicating with a Distributed System like a cRIO when there are dual network cards installed can occasionally present issues.  Either way I do know that these communication issues are currently being looked into.

Thank you again for all of the information you have helped provide.

Thanks!

Bob H

NI FIRST Support

[murthyz]

Hello Bob,

                I actually think we had an option to on setting it ON or OFF while setting up the classmate PC for the FIRST time i.e Windows installation stage.

I think we enabled it.So that could have caused this problem.Now we tried some small code for robot drive and it worked perfectly !

But we have a problem in building the last year's code in 2010 FRC.As a result we were not able to run last year's code with 2010 FRC labview.However we  have a built version of last year's code.I really would like to know how to deploy the already built code i.e Last year's code !!!!!!!!

Thanks,

Murthy

[nathand]

You cannot use last year's compiled code, because it's built for an older version of the LabVIEW run-time and you can only have one version of the run-time on your cRIO (this isn't a problem for compiled applications on Windows).  What error are you getting when you attempt to build last year's code with this year's LabVIEW?