[Rusttree]

We are having the identical problem that the OP described. Here's how I describe the sequence.

Setup:
Using the same laptop running Labview for code development and for running the driver station. I believe we had the dashboard application closed. Both Labview and the driver station application are actively running on the computer. The laptop is directly wired into the D-Link to eliminate the possibility of wireless issues.

1. Power up robot and wait for the cRio to come online.
2. Open Robot Main.vi and click the white arrow to "run" the code.
3. Wait for the (slow) initial deployment to complete. No errors. Click the "Close" button on the deployment dialog box.
4. Click "Enable" on the driver station and operate the robot. All user controls work (joystick, etc). The robot behaves perfectly according to the latest code changes.
5. Click "Finish" on Robot Main.vi and click "Disable" on the driver station.
6. Make some minor code change in Labview, save it, and click the white arrow in Robot Main again.
7. Wait for the very fast re-deployment to occur, as it only updates the changed parts of the program in memory. This re-deployment appears to occur without error. Click the "Close" button on the deployment dialog box.
8. Immediately followed by a pop error saying communication with the target has been lost.

This sequence, after one night of troubleshooting, appears to be very repeatable and consistent. We will try enabling the netconsole feature and seeing if we get similar errors as the OP. Has there been any further progress with troubleshooting this problem?