Thread: Problem with LabView Update 3.2 #2
View Single Post
  #12   Spotlight this post!  
Unread 22-02-2011, 22:25
DavidGitz's Avatar
DavidGitz DavidGitz is offline
Lead Technical Advisor
FRC #1208 (MeTool Brigade)
Team Role: Coach
  
Join Date: Dec 2006
Rookie Year: 1996
Location: O'Fallon, IL
Posts: 341
DavidGitz has much to be proud ofDavidGitz has much to be proud ofDavidGitz has much to be proud ofDavidGitz has much to be proud ofDavidGitz has much to be proud ofDavidGitz has much to be proud ofDavidGitz has much to be proud ofDavidGitz has much to be proud of
Send a message via AIM to DavidGitz Send a message via MSN to DavidGitz Send a message via Yahoo to DavidGitz
Re: Problem with LabView Update 3.2 #2
Quote:
Originally Posted by Joe Ross View Post
Or, did you download the pre-release v28 image that Joe Hershberger posted, and want to know if that is the same image that was installed the the LabVIEW update 3.2?
This is what I was asking about, although I assume that the v28 image that was released by Joe Hershberger is no different than the one that is included with LV update 3.2 We updated the cRIO to v28 before LV update 3.2 came out (due to the stack overflow issue and my (incorrect) guess that FIRST would not come out with a mandatory update a week before ship date), then updated the Classmate to LV 3.2, would it be necessary for the FMS or any other reason to re-image the cRIO to v28 (again).

I understand this is confusing, but thanks Greg for the clarification.
__________________
Reply With Quote