 | | Re: Lejos discussion archives
|
|
(...) Could be, I see the same. (...) I don't think so. You could use the sourceforge archive at (URL) Jürgen Stuber <stuber@loria.fr> (URL) (22 years ago, 16-Jul-02, to lugnet.robotics.rcx.java)
|
| |
| | Re: is it possible to remove lnp_handler while running ?
|
|
"kenneth johansen" <kennethj@stud.cs.uit.no> wrote in message news:3D343FAA.172476....uit.no... (...) I imagine you could just do something like lnp_addressing_set_handler( PORT, (lnp_addressing_handler_t) NULL ); I'm also curious as to why (...) (22 years ago, 16-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Announcing BricxCC release 3.3.5.7
|
|
I've just uploaded another revision of BricxCC (version 3.3.5.7). This release removes the 2.0 SDK DLLs since I do not have a license to redistribute those DLLs. This release fixes more Graphing issues. Users can optionally have the graph maintain (...) (22 years ago, 16-Jul-02, to lugnet.robotics.rcx.nqc)
|
| |
| | is it possible to remove lnp_handler while running ?
|
|
another dumb question about lnp:) i was wondering if it possible to do something like lnp_addressing_remov...,handler); as opposed to lnp_addressing_set_h...,handler); after much debugging i think i have traced my problem to the fact that (...) (22 years ago, 16-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Re: Scheduler patch
|
|
I have been thinking (and toying with some ideas) concerning tthe wakeup checking. It might be possible to do wakeup checking more often then between each timeslice. This would make msleep more accurate and provide better sensor handling. I know (...) (22 years ago, 16-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Re: Scheduler patch
|
|
(...) Yea you're right. I wasn't thinking. /Joel (22 years ago, 16-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Breaking from infinite loops
|
|
(...) Hi, if you just want to stop your "own" program use the Forth word ABORT or ABORT" : TEST 1000 0 DO \ do something run-button-down? ABORT" Aborted by user!" LOOP ; or if you want what looks like a "reset" use COLD: run-button-down? IF (...) (22 years ago, 16-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Aborting from ISR
|
|
Ah I see... intriguing idea :) Rereading your original post it should have been quite clear what you wanted. Unfortunately (as far as I know) Mario is right, there doesn't seem to be a clean solution other than manipulating the return stack. I've (...) (22 years ago, 16-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Breaking from infinite loops
|
|
This feels vaguely similar to a question just recently posed, almost. I need a way to get out of a user program that intentionally defines an infinite loop. My best attempt so far at an exit word : exit POWER_OFF LCD_4TH LCD_REFRESH ; in the context (...) (22 years ago, 16-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: detecting memory leaks
|
|
I've been experimenting with memory leak detection in the wake of recent discussions, and have some additional thoughts, including a potential kernel patch issue. This msg is a bit long, appologies. The proposed method of checking for memory leaks (...) (22 years ago, 16-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Lejos discussion archives
|
|
The last message I find is dated July 7,2002 using the link (URL) there a problem with geocrawler? or is my link out of date? Roger (22 years ago, 16-Jul-02, to lugnet.robotics.rcx.java)
|
| |
| | Re: Aborting from ISR
|
|
(...) I see. Tired of re-booting hey? :o)) There's no way already available that I know of. I think that Mr. Hempel is looking into this. Maybe if we play with the return stack... (...) The way Forth works is that it is running the program. If you (...) (22 years ago, 15-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Light sensor question
|
|
Hi Matt, I'll try to help. :o) First, you have to specify the type of sensor that is hooked on the port. You do that with: type port SENSOR_TYPE Let me know if you need to know the different values for 'type'. 3 is a light sensor. Ports are numbered (...) (22 years ago, 15-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Aborting from ISR
|
|
Hi, (...) My questions were a bit ambiguous. I don't want to abort the routine running on the ISR; I want (from the ISR routine) to abort a currently running user routine - eg abort something started from the console. So, for example, if a program (...) (22 years ago, 15-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Light sensor question
|
|
(...) With obvious mappings, of course. (...) Put another way, at no point does the red LED on the light sensor light up, and I consistently read the same value from the light sensor, regardless of whether I set the mode to RAW or percent value. In (...) (22 years ago, 15-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | yet another question about lnp
|
|
thanx to mark falco and albert huang for helping me out with lnp_init. But now i have another problem. if i execute lnp_addressing_write at approximately the same time as i recieve data on the serial port, lnp_addressing_write does not return.. the (...) (22 years ago, 15-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: whats up with lnp_init?
|
|
(...) I ran into this when using the LNP library to emulate LNP in the RCX as part of emuLegOS (URL) emuLegOS contains a thread safe wrapper for the LNP library. It should be fairly simple to extract that code into your own library for use in non (...) (22 years ago, 15-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Light sensor question
|
|
I want to expand the Scheme procedure (get-light-value <sym | num>) where <sym> is one of 'PORT1, 'PORT2, 'PORT3 and num is either 0, 1, or 2 to the FORTH code 128 <port> SENSOR_MODE <port> SENSOR_CLEAR <port> SENSOR_READ <port> SENSOR_VALUE So, if (...) (22 years ago, 15-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: whats up with lnp_init?
|
|
"kenneth johansen" <kennethj@stud.cs.uit.no> wrote in message news:3D31CF01.37F981....uit.no... (...) Kenneth, I'm not sure if I remember correctly, but lnpd as it is right now might not fare so well with reentrant code (i.e. pthreads) because the (...) (22 years ago, 15-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: RCX to RCX communication
|
|
"Luke Ma" <Luke_Ma@brown.edu> wrote in message news:Gz83nF.7D9@lugnet.com... (...) and (...) outputs. (...) eep. erm... we never posted RCX-RCX sample code up. never gave any of the students two bricks. and the LNP code up on our website has our own (...) (22 years ago, 15-Jul-02, to lugnet.robotics.rcx.legos)
|
