|
 | | RE: Incorrect result
|
| <snipped code> (...) Robert, this is a classic problem with ranges of singed numbers in C rx = (long)(a->magnitude * TA_costable[a->direction]) >> 7; I don't have an RCX in frot of me, but I think you need to cast a->magnitude to long before the (...) (23 years ago, 30-Jan-02, to lugnet.robotics.rcx.legos)
| |
|  
long
(score: 1.083)
|
|
| | threads
|
| Hi, I'm struggling to get threads working (in a simple motor speed matching program), the code just keeps hanging up. I've isolated the problem to when I restart the threads after killing them if a bumper is hit in the bumper_task() function. The (...) (23 years ago, 14-Jan-02, to lugnet.robotics.rcx.legos)
| |
|
long
(score: 1.083)
|
|
| | Re: threads - bug in the firmware?
|
| Hi again I have now totally stripped down my code to a minimum and I am still having problems with the code hanging up. I can see nowhere where there can be a fault. I am a long way from being an expert, but is it possible there is a bug in the (...) (23 years ago, 16-Jan-02, to lugnet.robotics.rcx.legos)
| |
|
long
(score: 1.083)
|
|
| | Re: More on threads
|
| (...) I recall that legOS's priority model is pretty rigid. If a thread with a higher priority never yields, threads with lower priority will never get any time. When I write legOS programs, I generally just have everything run at PRIO_NORMAL. That (...) (23 years ago, 19-Jan-02, to lugnet.robotics.rcx.legos)
| |
|
long
(score: 1.082)
|
|
| | Incorrect result
|
| This problem, unlike the other, is definitely not a result of my eyes/brain being tired or something. I thoroughly displayed every value before and after evaluation and the result is ***WRONG***. Here is the code and the values: typedef struct { int (...) (23 years ago, 30-Jan-02, to lugnet.robotics.rcx.legos)
| |
|
long
(score: 1.082)
|
|
| | Re: Incorrect result
|
| (...) Yes, this is what happens when one is used to just making everything long and not considering overflows. Even worse was that I was doing the math on the computer's calculator, but not looking at the intermediate result, just typing in the (...) (23 years ago, 30-Jan-02, to lugnet.robotics.rcx.legos)
| |
|
long
(score: 1.082)
|
|
| | Re: true tcp/ip on the RCX
|
| (...) The C64 server survived the "Slashdot attack" without problems, even though it served tenths of thousands of pages over a period of only a few hours. Since it is configured to allow only 10 simultaneous connections, it could more or less serve (...) (23 years ago, 4-Feb-02, to lugnet.robotics.rcx.legos)
| |
|
long
(score: 1.080)
|
|
| | Re: multiplexor and legOS
|
| (...) Thanks, I'd suspected that msleep might not be very accurate but never considered that it's true granularity could be so large. I did a quick test with my current configuration and when I asked msleep to sleep for 12ms it slept for 20. This (...) (23 years ago, 4-Feb-02, to lugnet.robotics.rcx.legos)
| |
|
long
(score: 1.080)
|
|
| | Re: multiplexor and legOS
|
| (...) I don't know about this 20ms granularity and how delay() is going to be any better. Here's the code for each function: //! delay execution allowing other tasks to run. /*! \param msec sleep duration in milliseconds \return number of (...) (23 years ago, 4-Feb-02, to lugnet.robotics.rcx.legos)
| |
|
long
(score: 1.080)
|
|
| | Re: multiplexor and legOS
|
| (...) Actually, something like this has been documented and done by Pedersen, Christensen, Rasmussen ("Prioritized Interrupts in LegOS"). They actually document the problem of sensor misses related to task management, significantly reducing the (...) (23 years ago, 5-Feb-02, to lugnet.robotics.rcx.legos)
| |
|
long
(score: 1.080)
|
|
| | Re: RFC: Creation of Version 0.2.6
|
| It appears that the time has come for 0.2.6; it has been more than 18 months now since 0.2.5. I still lurk here, but my work with Free Software has consumed my time- even when I'm not paid, I'm pretty much a slave to bugzilla.gnome.org and (...) (23 years ago, 9-Feb-02, to lugnet.robotics.rcx.legos)
| |
|
long
(score: 1.079)
|
|
| | Re: Power to RCX
|
| There is a difference between a voltage regulator (which limits the maximum voltage applied to a circuit) and a rectifier (which turns AC into pulsed DC - to be smothed out by a capacitor - it also ensures that you can't connect a DC power source (...) (23 years ago, 12-Feb-02, to lugnet.robotics.rcx)
| |
|
long
(score: 1.079)
|
|
| | LeJos threads / sleep() takes too long
|
| Experimenting with Lejos, two 'major' problems: memory (cleaning up platform & lang: Math.class is huge!) and... threads. I have the impression my "try { sleep(nnn) }" takes a somewhat arbitrary time. It's 'at least' nnn milisec, but often much (...) (23 years ago, 6-Mar-02, to lugnet.robotics.rcx.java)
| |
|
long
(score: 1.078)
|
|
| | Re: LeJos threads / sleep() takes too long
|
| Hi Bart, (...) if you mean LISTENER_THREAD then that sounds plausible. (...) Yes, LISTENER_THREAD has maximum priority, so it runs before any threads of lower priority, even yield doesn't help. (...) Yes, I think we'll have to fix that somehow. (...) (23 years ago, 6-Mar-02, to lugnet.robotics.rcx.java)
| |
|
long
(score: 1.078)
|
|
| | problems with communications
|
| I'm trying to get started with pbforth, but not finding it easy. While I know no forth, I'm happy with RPN (long-time HP calculator user) and stacks, dictionaries and defining words (ex-Postscript programmer). What I'm struggling with is getting as (...) (23 years ago, 25-Feb-02, to lugnet.robotics.rcx.pbforth)
| |
|
long
(score: 1.078)
|
|
| | Re: Support for pbForth in BricxCC
|
| (...) I'm also playing with interfaces to pbforth at the moment. What you're doing and I'm not is syntax highlighting. I'm not actually sure how well that works in pbforth, since I'm not sure how the editor knows which words have been defined (...) (23 years ago, 3-Mar-02, to lugnet.robotics.rcx.pbforth)
| |
|
long
(score: 1.077)
|
|
| | Re: RCX as a PGP engine
|
| (...) It really isn't that limited when you consider other platforms that run full PK systems, such as the Dallas Semiconductor iButton. It has a much more limited processors, more limited RAM, and you write your code in Java so it has to be (...) (23 years ago, 9-Mar-02, to lugnet.robotics.rcx.legos)
| |
|
long
(score: 1.076)
|
|
| | Re: LeJos threads / sleep() takes too long
|
| The priority mechanism used in lejos is the same as that specified in the Real Time Specification for Java (RTSJ): Threads of a higher priority will absolutely block threads of a lower priority as long as they remain runnable. The sensor listener (...) (23 years ago, 1-Apr-02, to lugnet.robotics.rcx.java)
| |
|
long
(score: 1.075)
|
|
| | Re: motors are stuck...
|
| According to a book by Ferrari brothers ("Building Robots With Lego Mindstorms") here's what you can try: --- How to release a Jammed Micromotor A micromotor jams so easily, you should know what to do when it occurs. The following list should help: (...) (23 years ago, 18-Mar-02, to lugnet.robotics.rcx.legos)
| |
|
long
(score: 1.075)
|
|
| |
|
long
(score: 1.074)
|
