2 issues in one possibly related (cRIO/ Camera)

[j.cole]

As for the cRIO it won't hold new code. I've changed PCs, ethernet cables (one that has worked for sure before and one new one), and the code being deployed. I have built deployed and ran as startup but I still can't get the new code to take.

Regarding the camera it won't display an image. I've set it up using the tool both ways (cRIO port and dlink port) and within those two setups I've switched to 2 cables (one that worked last year and a new one) and tried switching the boolean in the begin vi (but that doesn't do anything because the cRIO won't take code).

[Alan Anderson]

You don't by any chance have the cRIO's "NO APP" switch turned on, do you?

[j.cole]

I must have been doing something wrong because I came in the next day and tried it again (doing something the same and expect a different result isn't stupid after all) and it worked. But the camera is still not working so I don't know whats wrong with it.

[Alan Anderson]

You won't see the camera view on the default Dashboard unless you set the camera's IP address to 10.te.am.11 and connect it to the D-Link. You also have to give it 5 volt power; there's a dedicated output for that on the Power Distribution Board.

Does the light around the camera lens turn green when you try it?

[RufflesRidge]

Originally Posted by j.cole

and within those two setups I've switched to 2 cables (one that worked last year and a new one)

Adding on to Alan's post, when you connect the camera to the D-Link you should be using a regular patch cable not a crossover cable. If you plugged the camera into the cRIO last year you used a crossover cable.