Problems deploying code

[ArzaanK]

I did re-image the cRio to Windriver Workbench C++. On the note of undefined symbols, I don't have access to the robot, so I don't think I can check that.

You can run the utility program "nmppc <object module name>"

I am a little confused what you mean by this string of text. Is this "utility program" something I have to open up in Windows Explorer, is it something I have to put into my code?

Is it possible for my code to have undefined symbols even though the exact same code was able to be deployed onto the robot from another students laptop?

Would it help if you saw my code?

[wireties]

Originally Posted by ArzaanK

I did re-image the cRio to Windriver Workbench C++. On the note of undefined symbols, I don't have access to the robot, so I don't think I can check that.

I am a little confused what you mean by this string of text. Is this "utility program" something I have to open up in Windows Explorer, is it something I have to put into my code?

Is it possible for my code to have undefined symbols even though the exact same code was able to be deployed onto the robot from another students laptop?

Would it help if you saw my code?

In your case you would run the nmppc program from a command line like this:

nmppc C:\WindRiver\workspace\SimpleTemplate\PPC603gnu\Si mpleTemplate\Debug\SimpleTemplate.out

The program nmppc is in the VxWorks directories. I apologize for not having the exact location for you - I'm in the Caribbean on vacation. But the easiest thing to do is open the VxWorks Development Shell (from the program menus). It is a command line window (on your laptop) that has the PATH and other environment variables set you can use nmppc and other utility programs (.exe, .com, .bat in Windows) from Wind River.

If the exact same code deploys from another robot, something else is wrong. But you could have the same code and not be linking it in the same manner. For example, are you linking to the WPI libraries? Are you using a copy of the same project? Do both robots have the same types of cRIOs? Did you load the WPI stuff on your laptop?

You can send me your code and I'll look at it. Please send the .out file.

[wireties]

I can't see anything obviously wrong with your example code. Here is a sample of the output of nmppc:

...
U taskRestart
U taskResume
U taskSpawn
U taskSuspend
U time
U tolower
U toupper
U trcStack
U unldByModuleId
U vsprintf
00000154 D wpi_error_s_CommandIllegalUse
00000118 D wpi_error_s_CompressorUndefined
0000010c D wpi_error_s_DriveUninitialized
U write
...


But there are a lot of symbols in there to go through manually. Since you have two laptops with the same Wind River and NI install I would look for reasons that the FTP session might fail (which is what the download really does). Do you have any way to monitor network traffic to see the FTP session (on the wire) when start the download? Is it possible you have firewall settings stopping the FTP session?

[ArzaanK]

I have the standard windows firewall enabled, could that be stopping the deployment process. I won't have access to the robot until later tomorrow, but when I do, I will disable my firewall, and see if that helps at all.

Also, is it possible for me to somehow take the .out file of the program, and transfer it to the FTP? I've read about doing it before, but I'm wondering if the process can still be done manually.

[wireties]

Originally Posted by ArzaanK

I have the standard windows firewall enabled, could that be stopping the deployment process. I won't have access to the robot until later tomorrow, but when I do, I will disable my firewall, and see if that helps at all.

Also, is it possible for me to somehow take the .out file of the program, and transfer it to the FTP? I've read about doing it before, but I'm wondering if the process can still be done manually.

Sure, you can ftp to the robot (the user name and password are 'user' and 'password') and put the file in the login directory (so no need to change directories on the robot) - our autonomous code runs scripts that we download to the robot via ftp prior to each match

Hey - the name of the file might be important on the robot, it will not be SimpleTemplate.out. I can't remember what it is and have no way to check it right now. Log in to the robot and do a directory listing, the name is kinda obvious looking.

[ArzaanK]

I found out why I was having the problem. My Windows firewall must have been denying me access to deploy the code to the robot. I probably messed up on the permissions when I installed the program. All I had to do was disable the firewall, and I was able to deploy code.

Thank you all for your help,

[wireties]

No problem - good luck to you and 1325 this year!

[garyk]

Originally Posted by ArzaanK

I found out why I was having the problem. My Windows firewall must have been denying me access to deploy the code to the robot. I probably messed up on the permissions when I installed the program. All I had to do was disable the firewall, and I was able to deploy code.

Thank you all for your help,

Thanks for posting what you did to solve the problem! A question, though - was this the same computer with which you wrote and downloaded LabView code? I'm wondering if LV uses a different mechanism than FTP to deploy code to the cRio.

[ArzaanK]

Originally Posted by garyk

Thanks for posting what you did to solve the problem! A question, though - was this the same computer with which you wrote and downloaded LabView code? I'm wondering if LV uses a different mechanism than FTP to deploy code to the cRio.

I'm not sure exactly how LabVIEW deploys code onto the robot, but I have read somewhere that some teams have had success finding the raw executable and then performing an FTP transfer. I don't exactly remember where the thread is unfortunately.

Also, the computer that I am using is the exact same computer that I wrote and downloaded LabVIEW code with.

[garyk]

Originally Posted by ArzaanK

I'm not sure exactly how LabVIEW deploys code onto the robot, but I have read somewhere that some teams have had success finding the raw executable and then performing an FTP transfer. I don't exactly remember where the thread is unfortunately.

Also, the computer that I am using is the exact same computer that I wrote and downloaded LabVIEW code with.

OK, that tells us that LV and WindRiver use different mechanisms to download/deploy the code to the cRIO - handy to know for troubleshooting.