To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.robotics.rcxOpen lugnet.robotics.rcx in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / RCX / *8215 (-20)
  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)


Next Page:  5 more | 10 more | 20 more

Redisplay Messages:  All | Compact

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR