View Single Post
  #3   Spotlight this post!  
Unread 14-01-2006, 22:56
Chris_Elston's Avatar
Chris_Elston Chris_Elston is offline
Controls Engineer
AKA: chakorules
FRC #1501 (Team THRUST)
Team Role: Engineer
 
Join Date: Feb 2004
Rookie Year: 2001
Location: Huntington, Indiana
Posts: 751
Chris_Elston has a reputation beyond reputeChris_Elston has a reputation beyond reputeChris_Elston has a reputation beyond reputeChris_Elston has a reputation beyond reputeChris_Elston has a reputation beyond reputeChris_Elston has a reputation beyond reputeChris_Elston has a reputation beyond reputeChris_Elston has a reputation beyond reputeChris_Elston has a reputation beyond reputeChris_Elston has a reputation beyond reputeChris_Elston has a reputation beyond repute
Re: Loop time for OperatorControl function? Debug blows...

I tried that to, in the HELP FILE it list the directives:

Using directives with Print to screen
Directive
Variable
PrintToScreen Output

%ld
long x = 2000000
2000000

%d
int x = -100
-100

%u
unsigned int x = 100
100

%x
int x = 255
ff

%X
int x = 255
FF

%lx
int x = 255
0ff

%b
int x = 100
1100100


I used:

Code:
PrintToScreen ( "Loop Count = %ld\n" , (long)count ) ;
Shouldn't that work? It doesn't seem to work for me.....
The reason I changed it to:

Code:
PrintToScreen ( "Loop Count = %d\n" , (int)count ) ;
Was because I seen a tutorial or sample code of the EasyC, they used a long varible, then used a %d and an INT to print it to screen, so I followed suit but no matter which way, the printing of my count varible to screen is wacky....I can't possiblily debug like this...why or why don't these PICs support online debugging?

Yes, that is EASYC code. I printed the operatorcontrol function to PDF in the zip file.
__________________
Team T.H.R.U.S.T. 1501
Download all of our past robot's source code here:Repository

Favorite CD quote:
"That can't be their 'bot. not nearly enough (if any) rivets to be a 1501 machine." ~RogerR: Team #1369