 | | RE: Logging sensor data
|
|
Win 98 and Cygwin Thanks, Allen (...) (21 years ago, 9-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Logging sensor data
|
|
(...) What OS do you use ? nanobapt (21 years ago, 9-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | RE: Logging sensor data
|
|
Hi nanobapt, Thanks for your help, I was sort of thinking along these lines. I know very little about LNP so apologies if I come across as a little ignorant. Is there an LNP server I can run on my machine to collect the data sent to the RCX tower? (...) (21 years ago, 9-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Logging sensor data
|
|
(...) You can combine both solutions ... Storage in the RCX memory and then send it by lnp (after 10 data for example) You need to test :) nanobapt (21 years ago, 9-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | RE: Logging sensor data
|
|
Hi nanobapt, What I tend to do is sample a sensor every say 20ms and log the data over a period of upto about 5 seconds. In your opinion what would be the best method, local storage or realtime streaming via LNP?, can LNP stream at this speed? (...) (21 years ago, 9-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Linux legos install help me please
|
|
(...) Hmm rellay difficult to solve .... For your mandrake : make in a term "make > error" and send me (to my personnal mail) the file call error What version of brickOS do you use ? I know that there are error with the gcc 3.X so try (like you (...) (21 years ago, 9-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Logging sensor data
|
|
(...) How many time do you want to log it ? you can stock it to the RAM or send it by lnp .... nanobapt (21 years ago, 9-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Linux legos install help me please
|
|
Please help me install legos on Mandrake or help me fix my debian legos and add math.h I am a complete linux novice. 1 I have been enjoying the ease of use of Debian and the apt-get functions and friends with that distribution. For a beginner in (...) (21 years ago, 9-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Strange RCX startup issues
|
|
(...) This was only a problem when using certain firmware downloaders. If you use firmdl3, then you should be fine. (...) As far as I can tell, I don't think there is any provision in BrickOS to call the constructors and destructors of globals & (...) (21 years ago, 9-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: NQC's future
|
|
(...) Dear John, Even if it requires a firmware replacement, please add: - more variables, - float type variables, - string type variables, - certain math library (sin, cos, exp, ...) - at least good approximations, - more subs, - functions with (...) (21 years ago, 9-Dec-03, to lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
|
| |
| | Re: Help w/install _or_ It all went so well
|
|
(...) You can do make fontdesign in the util directory to create fontdesign.exe I have managed to get brickos-0.2.6.10 working using gcc 3.3.1 on win98 under cygwin, though I had a few problems along the way. At this stage I have only tried a few of (...) (21 years ago, 9-Dec-03, to lugnet.robotics.rcx.legos, FTX)
|
| |
| | Strange RCX startup issues
|
|
Hello, using brickOS v0.2.6.10... When I declare an object of type Motor and assign it a port outside of main() the RCX does not run the program at all, I have to remove batteries and reload firmware to get it back to normal. Is this related to the (...) (21 years ago, 9-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Remote Message Buttons
|
|
That doesn't seem to help, doing things that way actually made the Stop and Beep buttons function as Stop and Beep. I was hoping to have all the buttons "raw" messages available to remap their functionality. I think I know how to modify the kernel (...) (21 years ago, 9-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Logging sensor data
|
|
Hi there, I'm quite new to the Mindstorms and LegOS/BrickOS scene but have recently begun using the kits for robotics purposes in University. They have been a revelation to me and speed up prototyping projects to no end. My question though concerns (...) (21 years ago, 9-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Remote Message Buttons
|
|
(...) I just use the standard IR message stuff from BrickOS. They are normal messages, so this works just fine. Here are some lines of code: (I think it's in lnp.h) #include <sys/lnp.h> ... clear_msg(); ... if (msg_received != 0) my_message_value = (...) (21 years ago, 8-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Remote Message Buttons
|
|
Hello, Anyone had problems getting the message 1,2,3 buttons working with brickOS? All other remote buttons are working. I am using v0.2.6.10. I looked through the kernel and includes, it looks like in lr_process(), the lr_keys gets checked vs. (...) (21 years ago, 8-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: failure in communicaton between RCX & IR Tower
|
|
Just to verify the verdict... yes, it did work with w2kpro installed on this laptop. One note is that w2k vanilla does not support wireless 802.1g device, which is what comes with this toshiba satellite p25. It requires service pack 4. -- emabrey (21 years ago, 8-Dec-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c
|
|
(...) Yes, your summary is correct. Good luck with the rest of your project, Mark (21 years ago, 7-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c
|
|
(...) Mark, Thanks again thanks for the reply. Yes, my main comcern is that the OS tasks move around only after the first power off & on, no time else. And also it was just a typo, the blocks are in order I was looking at the wrong copy of my layout (...) (21 years ago, 7-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c
|
|
(...) So, if I understand you correctly, your concern is that the OS tasks move around the first time you power off & on, but not anytime thereafter? Assuming this to be the case, then: 1) When you first download BrickOS, there is a large chunk of (...) (21 years ago, 7-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: NQC's future
|
|
(...) and what about this : (URL) <- my legnoppix project nanobapt (21 years ago, 7-Dec-03, to lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
|
| |
| | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c
|
|
(...) Mark, Thanks for the reply, and sorry I forgot to include some more details I have results from 2 memory scans (the values may be a bit off from each other (i.e. starting addresses, but that is becuase they are from 2 times I ran it, and I (...) (21 years ago, 7-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c
|
|
(...) Hi Mike, It would be helpful to see each of the memory block dumps and some notation as to what actions you took between each dump (i.e. RCX on/off, program downloaded, etc...) Mark (21 years ago, 7-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c
|
|
Well, I have another problem - this time with Worst Fit. It may be becuase I have been looking at this code for so much time over the past few months, but I have encountered this problem with my implementation and my mind is boggled (as well as (...) (21 years ago, 7-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Editing Makefile (adding comman line arguements)
|
|
(...) Ed, Thanks for the reply, I will look at that manual, I never knew to look there. I bet it will help me out. Thanks Mike (21 years ago, 7-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Editing Makefile (adding comman line arguements)
|
|
(...) Mike, You might start off by checking the manual for GNU Make at (URL) just look within the various makefiles within the brickOS code. Try Makefile.commom at brickOS root. Ed (21 years ago, 7-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: NQC's future
|
|
(...) By the way, people who have a CD-booting Windows-compatible PC have free Linux too, via a boot CD that works without repartitioning (or even writing) the boot HDD: (URL) I think I specifically remember seeing rcx serial port tools work there, (...) (21 years ago, 6-Dec-03, to lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
|
| |
| | Editing Makefile (adding comman line arguements)
|
|
I am trying to edit Makefile in the main brickos dir so that I can access the arguements on the command line when I enter "make _____" to compile the directory. I need to do so because I need to have a certain command execute when the arguements are (...) (21 years ago, 6-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c
|
|
(...) Yeah, very true. Those lines where in there becuase of the error I originally had in my code, but since my code changed (and is correct) those lines are not needed). Thanks Mike (21 years ago, 6-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: NQC's future
|
|
(...) I think you are the victim of too much snippage... :-) If you reread the original message, there is indeed mention of adding various Spybot related features but the "non-standard firmware support" was in reference to NQC in general. I assume (...) (21 years ago, 6-Dec-03, to lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
|
| |
| | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c
|
|
(...) BTW, you can delete these two lines of intialization (i.e. lines 12 & 15 in the above function) as the intialized value gets clobbered on finding the first suitable sized block: 12) mm_best_free=ptr; 15) mm_best_free++; //this must point to (...) (21 years ago, 6-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c
|
|
(...) Sure thing sorry, the problem was that I had the wrong variable in one of the if statement, I copied it over wrong from my hand-written notes I made of the Alg ===...=== void *malloc(size_t size) { size_t *ptr,*next, bestSize, *mm_best_free; (...) (21 years ago, 6-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: NQC's future
|
|
(...) All, I thought that the spybot could not have the firmware replaced. Am I wrong? -Andrea (21 years ago, 6-Dec-03, to lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
|
| |
| | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c
|
|
(...) Fine. Could you please post the solution? I don't like unsolved riddles :) Regards, Michael (21 years ago, 6-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Complete instructions for Linux?
|
|
(...) Rich, Those patches were created for optimizing some legOS code. I believe it was some interupt code. The legOS code and brickOS code have internal work arounds. I have some emails concerning this somewhere. But you don't need these patches (...) (21 years ago, 6-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Complete instructions for Linux?
|
|
From: Rich Warren <rikiwarren@mac.com> Subject: Re: Complete instructions for Linux? Date: December 5, 2003 6:57:12 PM MST To: nanobapt <nanobapt@wanadoo.fr> (...) Correct me if I'm wrong, but my understanding is that this would build the BrickOS (...) (21 years ago, 6-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c
|
|
Nevermind, I figured out the error after I posted and reviewed my code again. Thanks anyway... (21 years ago, 6-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | My problems with adding a Best Fit algorithm for memory management to kernel/mm.c
|
|
Well, my senior project is almost due (Monday) and I am having problems with one of the last algorithms to be added. My senior project is adding the 3 other algorithms to the memory management facitlity (mm.c), the algorithsm are best, worst, and (...) (21 years ago, 6-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Complete instructions for Linux?
|
|
(...) $ tar xvzf brickos.tar.gz $ make or $ apt-get install brickos #for debian user ;-) nanobapt (21 years ago, 4-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Complete instructions for Linux?
|
|
Is there a complete instruction for installing BrickOS on Linux? I'm particularly interested in details involving creating a cross-compiler and getting the USB tower to work. I've looked at the windows instructions, and have tried to work from them, (...) (21 years ago, 4-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Strange BrickOS Timing
|
|
Hi Dietmar, (...) Of course :-) Ciao, Guido (21 years ago, 3-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Strange BrickOS Timing
|
|
Hi Guido, (...) That patch referes to an older transfer-protocol. The one we are using now, does not need SUCH a stable timing. But the Output from BrickOS is a lot worse than it was in older versions. I thing Gunther can explain this better, but I (...) (21 years ago, 3-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Strange BrickOS Timing
|
|
Hi Gunther, (...) have (...) After some investigation I found this page on YOUR site: (URL) YOU state: Using Lepomux requires a stable timing on the motor port because it is used as a serial data port. Since brickOS does a lot of stuff (...) (21 years ago, 3-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Strange BrickOS Timing
|
|
Hi Gunther, (...) have (...) I'm NOT really an expert in brickOS, but these are the sources of delay and msleep: void delay(unsigned ms) { unsigned i; while (ms-- > 0) for (i = 0; i < 600; i++) // not well calibrated. ; } //! delay execution (...) (21 years ago, 3-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: NQC's future
|
|
I would like functions to be able to return something other than zero. (If there's a way to do this (other than global variables) already, please let me know!) (...) (21 years ago, 3-Dec-03, to lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
|
| |
| | Strange BrickOS Timing
|
|
Hello out there, maybe someone can explain to me why the current brickOS release seems to have msleep()-amnesia ;-) We've been testing the data transfer to our Lepomux device. For some strange reason we were still using kernel 0.2.6.07nmChg with a (...) (21 years ago, 2-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: GP2D12 Please help
|
|
Hi Sebastian, (...) I don't know the schematics of that sensor interface, but I think it's basically a bad idea to drive a device that needs 30 to 50 mA from a powersource that can only output about 10 mA. I've experienced similar effects while (...) (21 years ago, 2-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: NQC's future
|
|
(...) I am happy to help out as best I can. Unfortunately, there is little chance that I will do as good a job as Dave Baum has done over the years. But I'll try my best. (...) Yes. When I can find the time. I'm also trying to find the time to do a (...) (21 years ago, 2-Dec-03, to lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
|
| |
| | Re: Broken Mindstorms motors
|
|
(...) Call "LEGO Shop at Home" and get four replacement motors. I just called them about a broken motor and a broken "pneumatic double acting cylinder". I called them pistons, but when she finally found them in 8455, she made sure I knew they were (...) (21 years ago, 2-Dec-03, to lugnet.robotics.rcx)
|
| |
| | Re: NQC's future
|
|
In lugnet.robotics.rcx.nqc, John Hansen wrote: John, thanks for taking on the maintenance and improvement of NQC. (...) I'd definitely like to see this one implemented, when you can find the time. :-) Mark (21 years ago, 2-Dec-03, to lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
|
| |
| | NQC's future
|
|
I'm very interested in hearing from NQC users what their needs/wishes are for future enhancements. Here's my current list of updates/enhancements that I am working on. 1. Built-in and documented Spybot API. 2. Fast firmware download via USB tower (...) (21 years ago, 2-Dec-03, to lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
|
| |
| | Broken Mindstorms motors
|
|
We have several broken mindstorms motors. Tw got the shafts broken. Two just stopped turning. So, we decided to steal the shafts from one set to fix the other set. However, putting them back together has stopped the working but shaftless ones from (...) (21 years ago, 2-Dec-03, to lugnet.robotics.rcx)
|
| |
| | Re: failure in communicaton between RCX & IR Tower
|
|
Nathan, I have done this trouble shooting step, ie. changing the timing. Unfortunately, it did not work. But, thank you though. Well, the a W2Kpro virtual machine approach did not work either... I guess my only alternative will be getting the (...) (21 years ago, 1-Dec-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Opening COM port error
|
|
(...) Tyler, Happy to be of help! Regarding Garbage Collection, I'm not usually one to criticise without being able to suggest a better alternative. In this case, I think most GC systems could be improved by mimicking the concept of "smart pointers" (...) (21 years ago, 30-Nov-03, to lugnet.robotics.rcx.java, lugnet.off-topic.geek)
|
| |
| | Re: "Non-Robolab" LabView functions
|
|
(...) Disagree. It's a matter of habitudes. Once you're familiar with the whole environment, you may write extremely complex programs without getting lost. For example, in our recent "Mars-mission" telerobotics project the complete programming -the (...) (21 years ago, 30-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
(...) They do work! But they are usually used with two quadrature outputs (hence the name), while on RCX only one wire is used and the 4 states are encoded as 4 voltages levels. (URL) (Image courtesy Michael Gasperi) The sequence (clockwise) is (...) (21 years ago, 30-Nov-03, to lugnet.robotics, lugnet.robotics.rcx.robolab, FTX)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
(...) The way I understand it, it's really not the sensor's fault. The RCX and firmware together either can't or doesn't deal with the ambiguous voltage levels sometimes returned during two of the four transitions. If the RCX were fast enough that (...) (21 years ago, 30-Nov-03, to lugnet.robotics, lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
Could someone explain to me technically why this sort of of problem with the rotation sensor occurs? I know how quadrature shaft encoders are _supposed_ to work, and I can't see why this sort of thing should happen in the first place. >> Mark (21 years ago, 30-Nov-03, to lugnet.robotics, lugnet.robotics.rcx.robolab)
|
| |
| | Re: "Non-Robolab" LabView functions
|
|
(...) Still waiting to hear from Dick about that. (...) I disagree that it's easier to understand and use. Possibly easier to learn or figure out without documentation, up to a point. But ease of learning is not the same as ease of use. Graphical (...) (21 years ago, 30-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: "Non-Robolab" LabView functions
|
|
(...) ---...--->snip I've not had the time yet to analyze the patch. Seems that you replace the first firmware handler. In Robolab the firmware is found under ..ROBOLAB\Engine\RCX1\Text. They simply have changed the extension .lgo to .txt and call (...) (21 years ago, 30-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | WTF: Broken RCX units
|
|
Anyone have or know where I can find broken RCX units for parts? Thanks, Rand (21 years ago, 30-Nov-03, to lugnet.robotics.rcx)
|
| |
| | Re: Opening COM port error
|
|
In lugnet.robotics.rcx.java, Chris Phillips wrote: Hahaha, Your passionate condemnation of GC makes entertaining reading in light of the amount of work I have to do with lejos,Java,C++, etc for my final year undergraduate project. I will certainly (...) (21 years ago, 30-Nov-03, to lugnet.robotics.rcx.java)
|
| |
| | Re: Patched firmware to improve rotation sensor, was Re: Robolab, byte codes and assembler
|
|
(...) It took me some time to figure out why, but you are right, the ambiguous transitions occur only while counting up. What you could do though would be to count +1 while going from state3 to state2_ambiguous, and correct "phantom transition" by (...) (21 years ago, 30-Nov-03, to lugnet.robotics, lugnet.robotics.rcx.robolab)
|
| |
| | math library
|
|
Hello all. About a year ago I researched math functions so I could write some for the RCX. I found some power series functions that work really well. I see another message here posted by "nanobapt" has also posted some functions so I tested his (...) (21 years ago, 29-Nov-03, to lugnet.robotics.rcx.legos)
|
| |
| | "Non-Robolab" LabView functions
|
|
I've been experimenting with some of the LabView icons available in "Investigator" mode in Robolab (under the "hourglass" item on the outermost menu). They seem to cause some odd behavior sometimes. It seems like it's especially a problem if one of (...) (21 years ago, 30-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Patched firmware to improve rotation sensor, was Re: Robolab, byte codes and assembler
|
|
(...) Doesn't that mean that at any given count, you could still be off by 1, but now the odds of having an incorrect count are 50-50 instead of about one in 500? (...) There has been some discussion about whether this patch will work with Robolab, (...) (21 years ago, 30-Nov-03, to lugnet.robotics, lugnet.robotics.rcx.robolab)
|
| |
| | Re: Patched firmware to improve rotation sensor, was Re: Robolab, byte codes and assembler
|
|
"Philippe Hurbain" <philohome@free.fr> wrote in message news:Hp4JAs.oK8@lugnet.com... (...) Much to my embarassment, I have to agree with Philippe that the patch doesn't work very well. I try to figure out what went wrong. (...) This is the expected (...) (21 years ago, 29-Nov-03, to lugnet.robotics, lugnet.robotics.rcx.robolab)
|
| |
| | Re: Patched firmware to improve rotation sensor, was Re: Robolab, byte codes and assembler
|
|
(...) <snip> That would be disappointing! I discarded the RIS software very early on. Dick, can you clarify this issue? (21 years ago, 30-Nov-03, to lugnet.robotics, lugnet.robotics.rcx.robolab)
|
| |
| | Re: Patched firmware to improve rotation sensor, was Re: Robolab, byte codes and assembler
|
|
(...) I think RoboLab uses its own firmware, so patching FIRM0328.LGO won't help you unless you use the RIS programming environment. (Or NQC, but that apparently isn't allowed by FIRST?) (...) I've used FIRM0328.LGO with older (version 1.0) RCXes (...) (21 years ago, 29-Nov-03, to lugnet.robotics, lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
(...) Should be legal, perhaps. But I was just suggesting that before sending him off to try to patch the firmware, he might want to make sure it was legal to do so. Although RIS and RoboLab may not use the same identical firmware, that doesn't (...) (21 years ago, 29-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Patched firmware to improve rotation sensor, was Re: Robolab, byte codes and assembler
|
|
Hello Don, (...) firm0309.lgo is firmware from RIS 1.5, while firm0328.lgo comes from RIS 2.0. Maybe RIS 1.5 can't download 2.0 firmware, never tried that... (...) I suggest you download BricxCC from (URL) and use its download utility (located in (...) (21 years ago, 29-Nov-03, to lugnet.robotics, lugnet.robotics.rcx.robolab)
|
| |
| | Re: Patched firmware to improve rotation sensor, was Re: Robolab, byte codes and assembler
|
|
(...) I'm having trouble downloading the patched firmware. Robolab doesn't have a .lgo file anywhere in the program directory structure, so I don't have a filename to replace with the patched file. Downloading in Robolab seems to work, but I see no (...) (21 years ago, 29-Nov-03, to lugnet.robotics, lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
(...) Wow, that's far more than I expected! And thanks for the detailed explanation. I may have to look at it tomorrow - my daughter's birthday is today. <snip> (21 years ago, 29-Nov-03, to lugnet.robotics, lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
(...) My arguments would be: 1. The firmware/sensor arrangement is _broken_. Fixing it should be legal. 2. The FIRST rules permit using different firmware implicitly, because they permit using RIS or Robolab, which requires different firmware. 3. (...) (21 years ago, 29-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Patched firmware to improve rotation sensor, was Re: Robolab, byte codes and assembler
|
|
Hello Dick, Looks great, but it doesn't seem to work well here: - counts up 2 by 2, but counts down correctly one by one - loses count, especially when counting up. My tests were done with a brand new, unmodified rotation sensor. I mounted a wheel (...) (21 years ago, 29-Nov-03, to lugnet.robotics, lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
Following up from my earlier post, I have completed a firmware patch for the rotation sensors. This post contains the patch with installation instructions followed by a technical description. A long post but hopefully more than made up by the value (...) (21 years ago, 29-Nov-03, to lugnet.robotics, lugnet.robotics.rcx.robolab)
|
| |
| | Re: Opening COM port error
|
|
(...) Ahh, Garbage Collection. <rant soapbox="on" eyes="glazed" dinosaur="true"> In my mind the worst thing that has happened to modern compiler languages is excessive reliance on Garbage Collection. This is analogous to leaving half-empty soda cans (...) (21 years ago, 29-Nov-03, to lugnet.robotics.rcx.java)
|
| |
| | GP2D12 Please help
|
|
Please help. I just recently got a Sharp GP2D12 ir distance ranger plus RCX interface device from mindsensors. It is pretty cool, however I am getting alot of flucuation in the readings and in turn I think that i am losing out on range. The maximum (...) (21 years ago, 29-Nov-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Opening COM port error
|
|
(...) Hi Chris, Thanks for your reply. You're reply confirmed my suspicion about leaving the port object lying around. I think I'll try your first suggestion of 'deleting' the port object at the end of each routine. I hope you dont mind me asking (...) (21 years ago, 29-Nov-03, to lugnet.robotics.rcx.java)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
(...) All this talk of patching firmware to correct for problems in rotation sensor readings is very interesting, but I think you may be approaching the problem a bit too directly. First, if the competition rules specify the programming environments (...) (21 years ago, 28-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
In lugnet.robotics.rcx.robolab, Claude Baumann wrote: <snip> (...) The main need is to return to the starting point after completing various challenges. I think the challenges also involve objects at known positions compared to the starting point (...) (21 years ago, 28-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Opening COM port error
|
|
(...) This probably is an issue of leaving your Port object around after you're done using it. You have a memory leak in each routine, because you call 'new RCXPort();' without ever calling 'delete port;' on the object. You should definitely call (...) (21 years ago, 28-Nov-03, to lugnet.robotics.rcx.java)
|
| |
| | Opening COM port error
|
|
Hi guys, First of all, thanx Brian, but I managed to solve the weird firmdl.bat problem by fooling around with different batteries and IR range levels. Secondly,I'm trying to send data packets to the RCX through java methods called from a C++ (...) (21 years ago, 28-Nov-03, to lugnet.robotics.rcx.java)
|
| |
| | 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)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
(...) <snip> (...) I'm quite interested in the alternative firmware for myself. However, for this particular problem, if a correct rotation count is my "Apollo 13's needed filter", then Robolab is the "cover of the flight manual" - it's what I have (...) (21 years ago, 28-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
(...) It really is. I do think somebody made a mistake specific to the rotation sensor, though. I haven't decided yet whether it's the firmware, the sensor, or just the overall mechanism. I can understand how it got past quality control - sometimes (...) (21 years ago, 27-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
(...) Unfortunately, I fear the comparison is all too true! So, is my robot going to blow up? ;) (...) I'd appreciate some specifics. So far, I have not been able to find a way to do this in Robolab. I wrote some code to test raw sensor values and (...) (21 years ago, 27-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: multiple motors
|
|
(...) hmm. see rule #1: (URL) my BIGGEST piece of advice for your sumo robot: make SURE it does not leave the sumo area on it's own." :) Steve (21 years ago, 27-Nov-03, to lugnet.robotics.rcx)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
OK You do something great, and all the world is looking at it, finding the finest detail one could have made much better. That's the power of internet-exchange. Don't take this personally. I only wanted to remind the great job they did at LEGO's (...) (21 years ago, 27-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
(...) Please don't take my post as a criticism of the original firmware, I merely wanted to point out alternatives. I agree, the 3ms sample rate is more than adequate for most applications. (...) Yes, the RCX is rugged in many respects, but I think (...) (21 years ago, 27-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
(...) We should not forget that the RCX has initially been designed for kids. So the standard firmware should be considered according to the initial aims, which were to provide a really great tool - toy for children. Therefore the firmware designers (...) (21 years ago, 27-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
(...) By contrast, BrickOS continuously samples each sensor at a rate of about 6.7 samples per millisecond. This is 20 times more often than the standard firmware. It's no wonder it's more accurate at higher rotation rates. Of course, it also (...) (21 years ago, 27-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
---...--->snip (...) Welcome to LEGO Mindstorms robotics: do great things in real world with imperfect tools and objects. That's what makes it so interesting. It's always the Apollo 13 challenge: "Here guys, that's what they have on bord! Come on (...) (21 years ago, 27-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
(...) That may be another problem to be solved; haven't got there yet because simply counting rotations has been unreliable. I mean with a motor shaft connected to a rotation sensor - no wheels, no robot! Can't even count rotations correctly. (21 years ago, 27-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
(...) I tend to think that positionning errors are more a problem of slip/skid than a problem of lost counts... Philo (21 years ago, 27-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
Thanks for the response. (...) It seems to me it's a design flaw in the entire method of counting rotations, which relies on the theoretical ideal of "instantaneous" voltage changes, which can't be produced. You can't go from 2V to 5V without (...) (21 years ago, 27-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
(...) Yes, I did read your information. It was very helpful - the best stuff I found on the subject. But as you said, modifying the sensor would probably disqualify. But, that does make me think again about the recent unavailability of the part . . (...) (21 years ago, 27-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: multiple motors
|
|
(...) Rather well... (...) ...but it was beaten by a simpler but slightly heavier 'bot! And it sometimes committed suicide too :-(( Philo (21 years ago, 27-Nov-03, to lugnet.robotics.rcx)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
"Don Stauffer" <BrainChild@Skyler.com> wrote in message news:Hoz4Gp.1zto@lugnet.com... (...) <<SNIP>> (...) The rotation sensor bad counts cannot be fixed at the byte-code level. The problem is "native" to implementation in the underlying firmware (...) (21 years ago, 27-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
Hello Don, Did you had a look to my analysis of this problem ((URL) But unfortunately I don't think that my modification is "competition-legal"... I agree that sampling can occur at the wrong time, but this should not occur more often at low (...) (21 years ago, 27-Nov-03, to lugnet.robotics.rcx.robolab)
|
