Error when deploying to RoboRio

[edong4273]

When I try to deploy code from LabVIEW, I get the following error and cannot deploy onto the RoboRio. After a day of Googling, I can't seem to find a solution to the problem, any suggestions?

Errors were detected in the target log when connecting to the target:

LabVIEW:  (Hex 0x661) The LabVIEW Real-Time process encountered an unexpected error and restarted automatically.

LabVIEW:  (Hex 0x63B) The RT target does not have enough memory to load the startup application.


Select "Apply" to ignore these errors and continue with deployment.

[Greg McKaskle]

I'd recommend typing the name into a browser and looking at the memory usage on the web page. You can also see this on the diagnostics page. If you have puTTY or a similar tool, you can see what applications are using memory and even kill the processes.

Can you give more input on what customization or packages were installed on the roboRIO?

Greg McKaskle

[edong4273]

Originally Posted by Greg McKaskle

I'd recommend typing the name into a browser and looking at the memory usage on the web page. You can also see this on the diagnostics page. If you have puTTY or a similar tool, you can see what applications are using memory and even kill the processes.

Can you give more input on what customization or packages were installed on the roboRIO?

Greg McKaskle

The RoboRIO just has a RoboRIO image (I can check and get back to you with specifics) and some previous robot code that we deployed a couple days ago on a different computer. The RoboRIO shouldn't contain anything else.
After a while last night, I did just reimage the RoboRIO and that seems to have solved the issue, or at least, allows me to deploy the robot code. Is it necessary to reimage the RoboRIO for every update of the robot code?
Thank you for the reply.

[RadhikaTheFish]

We called customer support and they found out what was wrong with it. Apparently, our host name was just roboRIO-3815.local instead of roboRIO-3815-FRC.local

[edong4273]

Originally Posted by RadhikaTheFish

We called customer support and they found out what was wrong with it. Apparently, our host name was just roboRIO-3815.local instead of roboRIO-3815-FRC.local

Hmm.. Interesting. I'll make sure to look at target names the next time I run into this problem. Thanks!