[DavidGitz]

We are using all 1208 equipment. The Driver Station ip address per the rules is 10.12.8.5 The cRIO target per the rules is 10.12.8.2 Which I can ping all the way through. Apparently the LV on our driver station was expired, so I'm renewing it tonight. I did find something interesting though, after you image the cRIO and reboot it (again, assuming all the network configuration is correct, and this follows with a wired/wireless/DS-crossover-cRIO connection) the robot communications light on the DS comes on but the Robot Code doesn't. I assumed it wouldn't since there isn't any code deployed on the cRIO (since it times out) but per the Control System Rules Section 2.6.1 (4) and 2.7.1 (2.f) the Robot Code light should turn on. If anyone can actually confirm this I would appreciate it but I don't think it should.

Tried at our meeting though with our laptop direct connected (ip address 10.12.8.7) to port 1 of the cRIO via a crossover, again was able to image it but couldn't connect to it using labview. This error exists in the Control Systems Rules Section 2.8.1 (2nd #2). Will try at next meeting with the actual DS.

Again, just so everyone is on the same page, everything is configured per the Control Systems Section 2. All wired/wireless communications are pingable, all led's turn on the robot correctly and all on the driver station turn on correctly (with the exception of the above).