 | | Re: Robolab - lejOS communication
|
|
(...) Mario, Lejos supports communication using the original firmware opcodes via the Serial class, but, apart from program download, this is designed for executing opcodes, not downloading data. F7Handler and F7DeliveryHandler are part of and (...) (22 years ago, 1-Dec-02, to lugnet.robotics.rcx, lugnet.robotics, lugnet.robotics.rcx.java, lugnet.robotics.rcx.robolab)
|
| |
| | Re: Motor Control Register (0xf000)
|
|
The lugnet registration takes forever :) After reading this post a light went on in my head. A few weeks ago I wrote a multi-threaded program for the RCX (about 7 threads, each running an endless loop). When I added one more thread, the robot (...) (22 years ago, 27-Nov-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
| |
| | Robolab - lejOS communication
|
|
Hi all, we are working on our final thesis using lego mindstorms. Our goal is to implement a neural network using the backpropagation algorithm. This neural network will then be used with a webcam for pattern recognition and classification. The (...) (22 years ago, 28-Nov-02, to lugnet.robotics.rcx, lugnet.robotics, lugnet.robotics.rcx.java, lugnet.robotics.rcx.robolab)
|
| |
| | PANIC !!!!!
|
|
Hallo I´ve just heart that the Mindstorm Series will be stoped for the sake of the spybot? Is this true, if yes we just have to start a fight for the survival of our RCX Sascha (22 years ago, 23-Nov-02, to lugnet.robotics.rcx)
|
| |
| | Re: Motor Control Register (0xf000)
|
|
(...) It's the one I meant, thanks. Jürgen (22 years ago, 21-Nov-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
| |
| | Re: Motor Control Register (0xf000)
|
|
(...) Yeah, I missed that, I'll add that to the notes. (...) Too bad they didn't document the hole well enough to make it obvious to the people at Lego, who apparently had no idea. They use "mov.w rx,@0xf000:16" all over the place instead of the (...) (22 years ago, 20-Nov-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
| |
| | Re: Motor Control Register (0xf000)
|
|
(...) Thanks for the suggestion... I think the change I made a few days ago included a note here also, but we might be talking about different spots. Let me know if not... kekoa@stanford.edu. -Kekoa (22 years ago, 20-Nov-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
| |
| | Re: Motor Control Register (0xf000)
|
|
(...) As it is, it seems[1] that two of the three NAND gates in the 74HC10 are being used as a driver for speaker output (it's odd that it's two, not one though). So, this leaves one three input NAND gate to do the decoding. Now that I think about (...) (22 years ago, 14-Nov-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
| |
| | Re: Motor Control Register (0xf000)
|
|
<snip> (...) Ok, thank you for the explaination! I am thinking that the Memory Manager would need some rework to support this, since the start of memory is currently established at compile time. I will have to take a look at this (time allowing). (...) (22 years ago, 14-Nov-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
| |
| | Re: Motor Control Register (0xf000)
|
|
(...) While you are at it you could also make a remark near the explanation of the f000 motor control register, and make it clear that this is a hardware function. When I started to use this extra memory in leJOS I missed the remark at the very end (...) (22 years ago, 14-Nov-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
