To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.robotics.rcx.legosOpen lugnet.robotics.rcx.legos in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / RCX / legOS / 1618
1617  |  1619
Subject: 
LNP handler timings
Newsgroups: 
lugnet.robotics.rcx.legos
Date: 
Sat, 13 Jan 2001 03:19:33 GMT
Viewed: 
1572 times
  
I'm writing a program that use LNP.  My addressing handler function is big,
so I measured the mean time requiered for executing that function (with a
call in for loop, so having sub-ms precision).  Mean time: 2.5 ms, with
packets of ca. 250 bytes.

I measured the time requiered to copy a region of 251 bytes: ca. 2 ms.  So
my handler is not too bad, but I wonder if there exists some limit to the
time taken by an LNP handler.  Perhaps the limit is LNP_BYTE_TIME? or
LNP_BYTE_SAFE? or something else?  Does anyone know what this limit is?

In `kernel/systime.c' there is an interrupt handler that makes calls
to the functions that handle sensor reading, sound output, time keeping,
and other things.  The interrupt fires every 1 ms.  Do the LNP handlers
interfere with this interrupt or they are simply sospended to execute its
handler?

I've not found such things discussed in the documentation.

bye
Bernardo



1 Message 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