View Single Post
  #57   Spotlight this post!  
Unread 31-03-2012, 11:10
RufflesRidge RufflesRidge is offline
Registered User
no team
 
Join Date: Jan 2012
Location: USA
Posts: 989
RufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant future
Re: 2012 Field Comm. Issue Logs

Quote:
Originally Posted by Tristan Lall View Post
Firstly, what would happen if the WPA key given in the kiosk and the one from the FMS were inconsistent? Would we see red indications for code and communications on the dashboard?
With an incorrect WPA key, the bridge could never link to the field and you would see red for code and communications and red for Bridge on the diagnostics tab

Quote:
Secondly, wasn't there something in the LV code (and maybe C++) where you could run code from the laptop, but it wouldn't be installed on the cRIO? I haven't seen that in a while, but maybe the team has an incorrect build option set? (I don't think this is it, though, because the robot flash codes seem to indicate it's running code.)
You can do that for both LabVIEW and C++ but in both cases you would see green for the Communication light and red for Robot Code.
Reply With Quote