|
 | | RCX Communication problem... suggestions?
|
| I got an RIS 2.0 for Xmas, and starting fiddling with it that night. It worked fine. I downloaded the firmware, and was able to download and run programs without problem... the software works fine as far as I can see. I am working with Win98SE on a (...) (23 years ago, 2-Jan-02, to lugnet.robotics)
| |
|  
firmware
(score: 1.375)
|
|
| | Re: RCX Communication problem... suggestions?
|
| (...) You might try watching the IR tower through a CCD device - like a digital camera or an analog or digital video camera. Their CCD chipsets detect IR light, and you'll see it as two additional pulsing LEDs inside the tower - probably green in (...) (23 years ago, 2-Jan-02, to lugnet.robotics)
| |
|
firmware
(score: 1.375)
|
|
| | Re: RCX Communication problem... suggestions?
|
| I have had this problem with one or two of my RCXs. I think the problem is that the CPU/RAM get into a "funny" state as the supply voltage drops after the batteries are removed. Once in this state, re-inserting batteries just brings the power up to (...) (23 years ago, 2-Jan-02, to lugnet.robotics)
| |
|
firmware
(score: 1.375)
|
|
| | remote control using PIC16F877
|
| Hello everyone. I've just developed a remote control for the RCX using the PIC16F877. It's very useful due to the fact that it does not need a computer, but still needs the ir tower (the serial one, sorry I'll try to adapt the project tu use the new (...) (23 years ago, 2-Jan-02, to lugnet.robotics.rcx.legos)
| |
|
firmware
(score: 1.375)
|
|
| | 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)
| |
|
firmware
(score: 1.375)
|
|
| | Re: threads - bug in the firmware?
|
| (...) Note also since bumper_task() is an infinite loop, and you never use pid1, you could save one thread by doing this: int main(int argc, char *argv[]) { pid2 = execi (&left_task, 0, NULL, PRIO_NORMAL+2, DEFAULT_STACK_SIZE); pid3 = execi (...) (23 years ago, 17-Jan-02, to lugnet.robotics.rcx.legos)
| |
|
firmware
(score: 1.375)
|
|
| | Re: Project X and game play
|
| (...) Well, I have put both my RCXs (RCXes? RCXen?) facing each other, 2 studs apart, and then i made a hinged cover for the emitters/receivers. Perhaps we should organize, and give everyone who needs them a specific block of IR message numbers to (...) (23 years ago, 7-Jan-02, to lugnet.org.ca.rtltoronto)
| |
|
firmware
(score: 1.375)
|
|
| | Re: Assembly Language Programming on the RCX
|
| (...) When the RCX 2.0 firmware came out, LEGO released an updated SDK ((URL) to take advantage of all the new stuff. One of the new features they provided was a new language called LEGO Assembler (LASM). This is as close to the hardware as you can (...) (23 years ago, 14-Jan-02, to lugnet.robotics.rcx)
| |
|
firmware
(score: 1.375)
|
|
| | Re: threads - bug in the firmware?
|
| (...) As pointed by Albert Huang, you cannot call kill() with an "invalid" pid. Actually, the comment above kill() in tm.c says: //! kill a process /*! \param pid must be valid process ID, or undefined behaviour will result! The function updates (...) (23 years ago, 16-Jan-02, to lugnet.robotics.rcx.legos)
| |
|
firmware
(score: 1.375)
|
|
| |
|
firmware
(score: 1.375)
|
|
| | Re: rtl10 is SUPER FUN!
|
| (...) Eep! Iain built a Davish 'Bot!!!!!! Whereas Dave built an Iain wannabe 'bot... Hmmmm..... Anyway, I'll try to get pics of my 'bot up this weekend, if I have time. I have 3 mods build for the train show, which are already factored into the (...) (23 years ago, 4-Jan-02, to lugnet.org.ca.rtltoronto)
| |
|
firmware
(score: 1.375)
|
|
| | Re: Programming, NQC and the RCX
|
| (...) the (...) Well RCX 2.0 firmware give you 32 global+16 local variables, according to NQC docs. LegOS should give you a lot more freedom in memory usage, but I haven't try that yet. For the X project, I plan to use bit manipulation to store all (...) (23 years ago, 10-Jan-02, to lugnet.org.ca.rtltoronto)
| |
|
firmware
(score: 1.375)
|
|
| | remote control 4 the RCX using PIC16F877
|
| Hello everyone. I've just developed a remote control for the RCX using the PIC16F877. It's very useful due to the fact that it does not need a computer, but still needs the ir tower (the serial one, sorry I'll try to adapt the project tu use the new (...) (23 years ago, 4-Jan-02, to lugnet.robotics)
| |
|
firmware
(score: 1.375)
|
|
| | Re: threads - bug in the firmware?
|
| Hi Mike, your problem is not because of an error in legOS. But what you do is that you start your subroutines and then you leave main()! Leaving main means that all your allocated memory is freed. The following will do the job: ---...--- cut here (...) (23 years ago, 17-Jan-02, to lugnet.robotics.rcx.legos)
| |
|
firmware
(score: 1.375)
|
|
| | Re: threads - bug in the firmware?
|
| ;-) That worked a treat, thanks Michael. (thanks for the other little corrections in the code too). mike (...) Mike, (...) your subroutines and then you leave main()! Leaving main means (...) memory is freed. The following will do the job: (...) (...) (23 years ago, 17-Jan-02, to lugnet.robotics.rcx.legos)
| |
|
firmware
(score: 1.375)
|
|
| |
|
firmware
(score: 1.375)
|
|
| | Re: Programming, NQC and the RCX
|
| (...) Rememeber to count all local variables, since they are not really local in RCXCC. Total number of usable variables are 32 for RCX 1.x. But I think the compiler will give you error for using more than 32 variables. If it is during download, (...) (23 years ago, 10-Jan-02, to lugnet.org.ca.rtltoronto)
| |
|
firmware
(score: 1.375)
|
|
| | RE: newbie
|
| LegOS is an operation system ( a firmware replacement in itself) It's like a mini UNIX system, that will run true C compiled programs on RCX. NQC on the other hand, all it does is translate a NQC program into LEGO pCode that will be *interpreted* by (...) (23 years ago, 21-Jan-02, to lugnet.robotics.rcx.legos)
| |
|
firmware
(score: 1.374)
|
|
| | Re: threads - bug in the firmware?
|
| (...) Advantage: Less memory used (each thread needs a block of memory in the kernel, I'm at work & can't remember the struct name off hand). In the case under discussion, this doesn't make much difference, but in a large project, memory use can (...) (23 years ago, 21-Jan-02, to lugnet.robotics.rcx.legos)
| |
|
firmware
(score: 1.374)
|
|
| | Re: Programming, NQC and the RCX
|
| The only way I now around these limitations is to use an alternate firmware. LegOS is a true c environment instead of being "not quite c" LeJOS is full featured Java VM. Both of these give you full control over memory usage, so the number of (...) (23 years ago, 10-Jan-02, to lugnet.org.ca.rtltoronto)
| |
|
firmware
(score: 1.374)
|
