View Single Post
  #2   Spotlight this post!  
Unread 03-01-2012, 12:00
Mark McLeod's Avatar
Mark McLeod Mark McLeod is offline
Just Itinerant
AKA: Hey dad...Father...MARK
FRC #0358 (Robotic Eagles)
Team Role: Engineer
 
Join Date: Mar 2003
Rookie Year: 2002
Location: Hauppauge, Long Island, NY
Posts: 8,801
Mark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond repute
Re: Problem with a cRIO project

Errors often report Robot Main just because it calls everybody else. Robot Main is essentially your program that's made up of a bunch of sub-vi's. Take a look at the vi's you've modified from the default baseline to see if any of those front panel arrows are broken. The most likely candidates are: Begin.vi and Teleop.vi.


Are you using the Run arrow from the Robot Main.vi front panel?
or
Are you using Build/Run as Startup

Perhaps a screen shot of the particular error message or posting a zip of the project so we can help you find the error...

Break (as opposed to "The VI is broken") might refer to a program breakpoint in execution accidentally inserted into a sub vi like Teleop, but that's only effective when using the Run arrow. Breakpoints show up in the code as a red dot on a data flow wire as in the attached (red dot on the axis 2 (y) output wire).
Attached Thumbnails
Click image for larger version

Name:	Breakpoint.jpg
Views:	21
Size:	12.9 KB
ID:	11270  
__________________
"Rationality is our distinguishing characteristic - it's what sets us apart from the beasts." - Aristotle

Last edited by Mark McLeod : 03-01-2012 at 13:24.