 | | Re: TIME STAMP for a LNP distributed robot
|
|
Thanks Mark for your idea, it's better to have a different global time than the one of the kernel. Best Regards, CarlosLuis Rendon M. "Mark Riley" <markril@hotmail.com> wrote in message news:HEIyDt.16s5@lugnet.com... (...) (22 years ago, 7-May-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: TIME STAMP for a LNP distributed robot
|
|
BTW, make sure you include: #include <time.h> Otherwise, get_system_up_time() will only return 16 bits! Mark (22 years ago, 7-May-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: TIME STAMP for a LNP distributed robot
|
|
Hi, The sys_time variable is the basic timekeeper for BrickOS. It is a 32-bit integer that is incremented every millisecond by the kernel. In older versions of the kernel you could access the variable directly, however, in 0.2.6.10 and later you (...) (22 years ago, 7-May-03, to lugnet.robotics.rcx.legos)
|
| |
| | TIME STAMP for a LNP distributed robot
|
|
Hi, I'd like to make a basic implementation of a time stamp on a distributed schame, using Lamport's algorithm. It states basically that when a node receives a message, it get the time stamp that's contained on it, and compares with it's own, if the (...) (22 years ago, 7-May-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: brickos-0.2.6.10 .text is not within region ram
|
|
(...) Dear Mark I will check the demo programs and more stuff. If i'm not wrong it looks to me that now we have 16K for the kernel ( c000-b000) = 4Kb more. If i got the results, i'm coming back to the forum. best regards Bernhard (22 years ago, 7-May-03, to lugnet.robotics.rcx.legos)
|
