|
 | | Re: frame RCX reply how
|
| (...) Yes helpful framing rules thanks. (...) Thanks in particular for pointing out the before & after rubbish. Me, just now I began quoting this rule in a fog, somehow not immediately appreciating that: The receive framing in bricxcc withstands (...) (22 years ago, 2-Feb-03, to lugnet.robotics.rcx)
| |
|  
ir
(score: 1.889)
|
|
| |
|
ir
(score: 1.889)
|
|
| | Robot Ant and Data logging
|
| HI, I am building a robot ant and using a light sensor to detect lines to follow. However, the algorithm I am using must not be deterministic; i.e. I need to do a sensor sweep and build a graph of the relative light levels at the left, front and (...) (23 years ago, 4-Apr-02, to lugnet.robotics.rcx.robolab)
| |
|
ir
(score: 1.889)
|
|
| |
|
ir
(score: 1.889)
|
|
| | Re: avoid messaging
|
| (...) If you have an event waiting for a message, I doubt it will have much impact on the speed of the rest of the program. However, this will not catch the messages you're looking for. You can't use the "mail" function to receive op-code, such as (...) (19 years ago, 5-Dec-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.889)
|
|
| | Proximity detector routines
|
| Hello, i've written a proximity sensor for legOS 0.2.3 I hope, it'll be usefull to someone. Carsten ---...---SNIP HERE ---...--- /***...*** * Filename: ProximityLib.c * * * * Proximity Driver for legOS 0.2.3 * * the LightSensor is connected PORT 2 * (...) (25 years ago, 20-Jan-00, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.889)
|
|
| | Re: Very strange problems
|
| (...) I was afraid so. (...) We haven't reached the GA part yet. Right now the idea is to work out a communication protocol and then send a information back and fourth. And since the RCXs locked up we thought that there must be something wrong in (...) (24 years ago, 21-May-00, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.889)
|
|
| | Re: LegOS 0.2.5 and LNP
|
| (...) Btw. README is (...) Ooops... :-) Changed to 0.2.5 version inside. (...) transport (...) packets of (...) mainly as way for (...) collisions, lost (...) which works as (...) write code to (...) To cut time (...) code that (...) directives (...) (24 years ago, 17-Jan-01, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.889)
|
|
| |
|
ir
(score: 1.889)
|
|
| | Re: Debugging
|
| (...) However, last night, I wrote a brute force (spin loop) msleep which works fine in the scheduler. I found that 800 iterations of an empty for loop with a 16 bit index comes pretty close to 1ms. Granted, I cheated a little, knowing that the (...) (26 years ago, 17-Mar-99, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.889)
|
|
| | Piggybacking sensors, but in a different way
|
| Is it possible to piggyback 1 sensor onto two rcx's? For instance, have one light sensor connected to port 1 of two different rcx's at the same time. The purpose would be for one rcx to control chassis movement, and another to control manipulator (...) (20 years ago, 26-Oct-04, to lugnet.robotics.rcx)
| |
|
ir
(score: 1.889)
|
|
| | pbFORTH enhancements soon
|
| Thanks to all of the mail I have received, I am going to try to get the next version of pbFORTH out this weekend. Charles Anderson pointed out a rather embarassing flaw in the LCD_SHOW and LCD_HIDE routines, thanks. I have been using Dave Baum's NQC (...) (26 years ago, 5-Mar-99, to lugnet.robotics.rcx.pbforth)
| |
|
ir
(score: 1.889)
|
|
| | reliability of quad speed LNP
|
| Does anyone have any data on the reliability of quad speed LNP? I've been using quad speed LNP for downloading programs to my 1.0 RCX for some time, and never had a problem. Recently I'd bowored a friends 1.0 RCX so that my bot could have two RCXs. (...) (23 years ago, 25-Feb-02, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.889)
|
|
| | RE: Multitasking questions
|
| (...) Ummm, I'm in the process of verifying all of the old scripts I package with pbForth. It looks like HAT is what actually works, and I've managed to change the documentation and not the code. HAT is in the origianl hForth implementation but I (...) (24 years ago, 3-May-00, to lugnet.robotics.rcx.pbforth)
| |
|
ir
(score: 1.889)
|
|
| | Remote control RCX by mobile phone
|
| I try to make a appli that executed in mobile phone, it can control RCX. The mobile phone's SDK provides class RemoteControlData with some methods as below: setPulse(int leader_on, int leader_off, int trailer_on) leader_on: start bit High period (...) (16 years ago, 27-May-08, to lugnet.robotics.rcx)
| |
|
ir
(score: 1.889)
|
|
| |
|
ir
(score: 1.889)
|
|
| |
|
ir
(score: 1.889)
|
|
| | Idle Powerdown
|
| I've successfully implemented an idle powerdown into the legOS kernel. On more than one occasion I have left my RCX on overnight, resulting in the need to buy a new set of batteries. The tricky part was doing a successful powerdown from within the (...) (24 years ago, 13-Aug-00, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.889)
|
|
| | RE: New pbForth GUI
|
| This is a great idea, Ralph. I've wanted to just fool around in pbForth, but have been intimidated by the apparent front-end learning curve. I'm a mechanical guy, I don't do TclTk, Gnu, etc., I've been spoiled by GUI front ends and install programs. (...) (24 years ago, 16-May-00, to lugnet.robotics.rcx.pbforth)
| |
|
ir
(score: 1.889)
|
|
| | Re: Robolab, byte codes and assembler
|
| ---...--->snip (...) I guess the competition asks you to run a certain distance as precisely as possible, or/and do some precise turns. We often experienced this kind of challenges in our school. The best way seemed to be to collect statistical (...) (21 years ago, 28-Nov-03, to lugnet.robotics.rcx.robolab)
| |
|
ir
(score: 1.889)
|
