To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.robotics.spyboticsOpen lugnet.robotics.spybotics in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / Spybotics / 302
301  |  303
Subject: 
Re: NQC's future
Newsgroups: 
lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics
Date: 
Mon, 12 Jan 2004 21:41:40 GMT
Viewed: 
578 times
  
"Brian Davis" <brdavis@iusb.edu> wrote in message
news:HrB87H.17p1@lugnet.com...
<<snip>> is it possible (either in the current > incarnation or a • future one) for NQC
to use FastTimer() as a source for events?
Timer() works, but not (it seems) FastTimer().

I think your question probably meant "can I use FastTimer in defining
events because I want better resolution than is possible with using
Timer"? Unfortunately, this is not possible. Standard firmware checks
for new timer events immediately after a tick of the 100 millisecond
counter that drives the timers. There is no way to improve the
resolution.

At alternative implementation  is to bypass the use of an event timer
and use 'wait' opcode. This does provide 10-millisecond resolution.



Message is in Reply To:
  Re: NQC's future
 
(...) Here's a suggestion/question: is it possible (either in the current incarnation or a future one) for NQC to use FastTimer() as a source for events? Timer() works, but not (it seems) FastTimer(). (21 years ago, 11-Jan-04, to lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)

29 Messages in This Thread:











Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR