View Single Post
  #5   Spotlight this post!  
Unread 14-01-2006, 23:24
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 figured something like this was happing in the PrintF statement. Seems "weird" to me that you have to be a printF expert just to get your varible out. I see what you mean now. I know my bits and btyes and binary.

I wonder if EasyC supports the "%ld" directive. Why would they put it in the help file if it doesn't?

%ld
long x = 2000000
200000

I'll play around with my print-to-screen function, (thank you Joel)m but back to my main question.....does anyone know the loop time of the operatorcontrol function block in EasyC?

I guess I'll find out soon enough myself if I ever get my varible out and formatted correctly to a terminal window....sigh....

I did look at the online debugger last year, I never got it to work. Since I don't use PICs everyday, outside my normal job, I just didn't get how to make it work in MPLAB. I found myself in the same frustrating boat last year with terminal debugging with varibles that don't seem right being printed to screen.....
__________________
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