 | | Og Needs More Inputs
|
|
-So, I'm building an RCX-based robot that already has - and needs - a light sensor, a rotation sensor, and a touch sensor. I've discovered I can include another touch sensor on the same input as the light sensor. (Thanks to (URL) Can the same be (...) (28 years ago, 27-Apr-99, to lugnet.robotics)
|
| |
 | | Re: Og Needs More Inputs
|
|
(...) There isn't any way to "double up" a rotation sensor. It needs to be connected 100% of the time to prevent it from missing counts. There are ways to build mulitplexers and input expanders on my web page, but they all require non-standard LEGO (...) (28 years ago, 27-Apr-99, to lugnet.robotics)
|
| |
 | | Re: Og Needs More Inputs
|
|
(...) You mean a touch sensor and a rotation sensor? This does not work. The two sensors confuse one another. Also, pairing up a light sensor and a touch sensor only works if the lights are not very bright. Pointing the light sensor at a bright (...) (28 years ago, 27-Apr-99, to lugnet.robotics)
|
| |
 | | A robot who knows his position
|
|
I had some success in my first experiment with odometry. My goal was to build and program a bot that at every moment knows where he is. My creature uses a very simple and standard differential-drive: two large independent driving wheels on the left (...) (28 years ago, 27-Apr-99, to lugnet.robotics)
|
| |
 | | Re: Og Needs More Inputs (fwd)
|
|
----- Forwarded message from Kekoa Proudfoot ----- From: kekoa@pixel.Stanford.EDU (Kekoa Proudfoot) Subject: Re: Og Needs More Inputs Date: Tue, 27 Apr 1999 21:57:41 GMT Also, pairing up a light sensor and a touch sensor only works if the lights are (...) (28 years ago, 27-Apr-99, to lugnet.robotics)
|
| |
 | | Re: Og Needs More Inputs (fwd)
|
|
----- Forwarded message from Michael Gasperi ----- From: "Michael Gasperi" <gasperi@alynk.com> Subject: Re: Og Needs More Inputs Posted-Date: Tue, 27 Apr 1999 20:57:31 GMT Date: Tue, 27 Apr 1999 20:57:31 GMT Organization: Alynk Message-ID: (...) (28 years ago, 27-Apr-99, to lugnet.robotics)
|
| |
 | | A robot who knows his position (fwd)
|
|
----- Forwarded message from Mario Ferrari ----- From: "Mario Ferrari" <mario.ferrari@edis.it> Date: Tue, 27 Apr 1999 22:12:25 GMT I had some success in my first experiment with odometry. My goal was to build and program a bot that at every moment (...) (28 years ago, 28-Apr-99, to lugnet.robotics)
|
| |
 | | Re: A robot who knows his position
|
|
(...) Actually, software floating point is quite doable on the H8. In fact, at least egcs 1.1.[1,2] includes FP emulation (config/fp-bit.c), which gets put into libgcc2.a, which get merged into libgcc.a. You don't have to do anything special to use (...) (28 years ago, 27-Apr-99, to lugnet.robotics)
|
| |
 | | Re: A robot who knows his position
|
|
(...) This is great! I thought it was possible, but my knowledge of C isn't simply enough to figure out HOW TO. (...) Yes, when you have floats you can use/adapt standard math libraries. I'll try this. (...) This would be of great help (not only to (...) (28 years ago, 28-Apr-99, to lugnet.robotics)
|
| |
 | | Re: A robot who knows his position (fwd)
|
|
(...) up (...) possible. (...) That's true and clear. I'm not actually interested in such a precision, but as you know very well the problem with odometry is that errors accumulates very fast so I used four decimal digits in any computation to keep (...) (28 years ago, 28-Apr-99, to lugnet.robotics)
|
| |
 | | Re: A robot who knows his position (fwd)
|
|
(...) [ talk of Dead Reckoning ] (...) That's a useful idea; I'll take note of that. (...) I've been doing some robot building aimed at dead reckoning and have found that even the home or flat environment is enough to f*&k things up; the bumpy (...) (28 years ago, 28-Apr-99, to lugnet.robotics)
|
| |
 | | Re: Og Needs More Inputs (fwd)
|
|
(...) connected (...) Let's assume it is the LEGO rotation sensor. Which is not an 8-bit sensor. It is an incremental encoder that sends values back as 4 analog values. If a touch sensor is put in parallel with a rotation sensor the analog values (...) (28 years ago, 28-Apr-99, to lugnet.robotics)
|
| |
 | | Re: A robot who knows his position (fwd)
|
|
(...) Looking forward to seeing them :) (...) Dead-reckoning should be used BETWEEN two consecutive (artificial) landmark sensing. When you get any external reference point you can zero your accumulated errors. (...) moving (...) Seems interesting. (...) (28 years ago, 28-Apr-99, to lugnet.robotics)
|
| |
 | | Re: A robot who knows his position (fwd)
|
|
(...) I have been thinking about a different approach. I have not actually built anything to use it yet, but I believe it should work reasonably well. The basic idea is similar to the old optical mouse pads -- draw horizontal and vertical lines on (...) (28 years ago, 28-Apr-99, to lugnet.robotics)
|
| |
 | | Inverting the robot position problem...
|
|
(...) This brings out a VERY interesting application. Most bots have trouble navigating a real maze because of obvious slippage problems and generally poor resolution of sensors. What about inverting the problem and printing (using your favorite (...) (28 years ago, 28-Apr-99, to lugnet.robotics)
|
| |
 | | Re: Inverting the robot position problem...
|
|
(...) You are right about the limitations of image based maze followers, but with you don't even need to get that complicated- any bot that can follow a wall using touch sensors can do a maze reasonably well. Picture a blind man walking along a (...) (28 years ago, 28-Apr-99, to lugnet.robotics)
|
| |
 | | Re: Og Needs More Inputs (fwd)
|
|
(...) To add to this, the effect of placing a touch sensor in parallel with a rotation sensor is as follows: When touch sensor is not pressed, rotation sensor works fine When touch sensor is pressed repeatedly, rotation sensor drifts When touch (...) (28 years ago, 28-Apr-99, to lugnet.robotics)
|
| |
 | | Re: Inverting the robot position problem...
|
|
(...) That was what I had intended to use -- 1/8" tape spaced at 1" centers on a white background. I was thinking black and red should be sufficiently distinguishable from each other, but that will probably take experimentation. John A. Tamplin (...) (28 years ago, 28-Apr-99, to lugnet.robotics)
|
| |
 | | Re: Inverting the robot position problem...
|
|
(...) When one color tape overlaps the other color it may be possible for the sensor to miss the bottom color when it passes over the intersection. Maybe you could use a square piece of tape of a third color at the intersection? Like you said, this (...) (28 years ago, 28-Apr-99, to lugnet.robotics)
|
| |
 | | Re: Og Needs More Inputs (fwd)
|
|
(...) Actually, I retract what I said about the light sensor and the touch sensor, but not on the grounds you stated, or at least on clearer grounds than you seemed to explain. (That you can configure the touch sensor or bias the photodetector seems (...) (28 years ago, 28-Apr-99, to lugnet.robotics)
|
| |
 | | RE: A robot who knows his position (fwd)
|
|
(...) Just for reference: The optical mouse pads made by Mouse Systems, and shipped with Sun workstations for a long time, used two detectors in the mouse. One used a red LED, and the other one looked the same, but was dark. I suspect it was an IR (...) (28 years ago, 28-Apr-99, to lugnet.robotics)
|
| |
 | | RE: A robot who knows his position (fwd)
|
|
(...) Wow- sounds really interesting. Keep us all up to date... Luis ###...### "They call the faithful to their knees to hear the softly spoken magic spell:" "There's no place like home... There's no place like home... There's no place like home." (...) (28 years ago, 28-Apr-99, to lugnet.robotics)
|
| |
 | | NQC 1.3 has been released
|
|
I just posted NQC 1.3 to the main web site: (URL) an excerpt from the readme... version 1.3 ---...--- Calls to inline function may now be made before their definition. abs() and sign() operators added. SetWatch() added to rcx.nqh. Toggle() added to (...) (28 years ago, 28-Apr-99, to lugnet.robotics.rcx.nqc, lugnet.robotics)
|
| |
 | | Re: Compiling NQC
|
|
(...) fyi - NQC 1.3 builds and runs fine on LinuxPPC. It also builds under about half a dozen flavors of Unix without any #ifdefs, so MacOSX Server shouldn't be a problem. About the only thing you'll have to "port" is filling in the name of your C++ (...) (28 years ago, 29-Apr-99, to lugnet.robotics)
|
| |
 | | Re: A robot who knows his position (fwd)
|
|
(...) I like John's idea. You could combine it with odometry and get a very affordable and precise positioning system. I'm quite happy with the results of odometry in the short range, I mean until you accumulate too many small errors. My robot (...) (28 years ago, 29-Apr-99, to lugnet.robotics)
|
| |
 | | Re: Og Needs More Inputs (fwd)
|
|
----- Forwarded message from Kekoa Proudfoot ----- From: kekoa@pixel.Stanford.EDU (Kekoa Proudfoot) Subject: Re: Og Needs More Inputs (fwd) Date: Wed, 28 Apr 1999 22:11:18 GMT Actually, I retract what I said about the light sensor and the touch (...) (28 years ago, 29-Apr-99, to lugnet.robotics)
|
| |
 | | Re: Compiling NQC
|
|
(...) Of course, I did not mean to imply she is off course. (...) > > (...) (28 years ago, 29-Apr-99, to lugnet.robotics, lugnet.robotics.rcx.nqc)
|
| |
 | | Upcoming eunuch mouse technology from Microsoft
|
|
Does anyone understand the technology underneath the new eunuch mouse from Microsoft and how that could possibly be applied to mobile robots with regards to robot positioning and knowing where your robot is located? A couple of links for more (...) (28 years ago, 29-Apr-99, to lugnet.robotics)
|
| |
 | | Re: Og Needs More Inputs (fwd)
|
|
(...) The LEGO light sensor does not work this way. The voltage output of the sensor goes down with brighter light. A touch sensor in parallel with a light sensor when touched will cause a light reading of 100. You cant tell that from a bright (...) (28 years ago, 29-Apr-99, to lugnet.robotics)
|
| |
 | | Re: Og Needs More Inputs (fwd)
|
|
It works if you use the raw values. Then the brightest light is about 400 (these are off the top of my head, the exact numbers are different) and pushed touch sensor is about 50. -chris -----Original Message----- From: Michael Gasperi (...) (28 years ago, 29-Apr-99, to lugnet.robotics)
|
| |
 | | Re: Og Needs More Inputs (fwd)
|
|
(...) Good point. The best way is to use the RAW mode. Then you can tell the difference between a touch and a bright light. That is what Keoka was talking about a few messages ago in this thread. (28 years ago, 29-Apr-99, to lugnet.robotics)
|
| |
 | | Re: Og Needs More Inputs (fwd)
|
|
On Thu, 29 Apr 1999, Jim Choate wrote: ----- Forwarded message from Michael Gasperi ----- From: "Michael Gasperi" <gasperi@alynk.com> Subject: Re: Og Needs More Inputs (fwd) Date: Wed, 28 Apr 1999 12:52:54 GMT >----- Forwarded message from Michael (...) (28 years ago, 30-Apr-99, to lugnet.robotics)
|
| |
 | | Re: Og Needs More Inputs (fwd)
|
|
(...) It is an optical (I think) incremental encoder where the 2 quadrature bits are converted to analog values. There is a pretty good description of the LEGO rotation sensor on my web page and also plans for a homebrew version that works about the (...) (28 years ago, 30-Apr-99, to lugnet.robotics)
|
| |
 | | Re: A robot who knows his position (fwd)
|
|
(...) [ ... ] (...) Well, I know this, I was just seeing how far I could get without landmarks. An idea Richard Franks and I had was to use black and white approx. A4 size printed markers. These markers would contain a pattern that was detectable by (...) (28 years ago, 30-Apr-99, to lugnet.robotics)
|
| |
 | | Re: A robot who knows his position (fwd)
|
|
<cut> (...) I have not tried this yet as I have not figured it all out yet but.... The dive compass I have (which is relativly large) has a window visible from the side this has degree markings and lines for every degree. The lines are reasonably (...) (28 years ago, 30-Apr-99, to lugnet.robotics)
|
| |
 | | Re: A robot who knows his position (fwd)
|
|
(...) around (...) disk (...) for (...) Well, I was just going to place the light sensor statically relative to the case of the compass, and overhead. It would simple note whenever the head of the arrow went past. This is pretty useless, which is (...) (28 years ago, 30-Apr-99, to lugnet.robotics)
|
| |
 | | Re: LEGO light sensor schematic
|
|
(...) thing. We have an OpAmp connected to nothing that is set to oscillate for no reason, diode pairs that won't supply power to the circuit, an optical sensor that is biased backwards and lots of transistors set to act as diodes. I think he needs (...) (28 years ago, 30-Apr-99, to lugnet.robotics)
|
| |
 | | Re: A robot who knows his position (fwd)
|
|
For people that don't mind non-lego solutions, how about the Dinsmore compass: (URL) haven't personally used one yet, but it seems like with a bit of processing, you could get it to return a value like a light sensor. Also, the price is pretty good (...) (28 years ago, 30-Apr-99, to lugnet.robotics)
|
| |
 | | Re: A robot who knows his position (fwd)
|
|
(...) [snip] (...) I'm currently looking at an RCX interface to a Dinsmore compass module that uses Hall-Effect sensors to detect N-S-E-W and triggers two of them when dead-center between two cardinal points, so you get N-NE-E-SE... Not that great (...) (28 years ago, 30-Apr-99, to lugnet.robotics)
|
| |
 | | Re: A robot who knows his position (fwd)
|
|
On Fri, 30 Apr 1999, Mike Moran wrote: . . . (...) Yes. It is unnecessarily clumsy and heavy and would require considerable computer attention to track rotation successfully. I believe digital encoding would be better. Anyone know how one determines (...) (28 years ago, 30-Apr-99, to lugnet.robotics)
|
| |
 | | RE: LEGO light sensor schematic
|
|
(...) Hmmm, Michael is usually pretty careful about what he posts and he has just a little experience with this kind of thing :-). In fact, Michael's own powered sensors look a lot like this one. From left to right: The diode pairs that don't do (...) (28 years ago, 30-Apr-99, to lugnet.robotics)
|
| |
 | | Re: A robot who knows his position (fwd)
|
|
(...) moves (...) right (...) knows (...) That sounds like a challenge to me! ;-) I may just try and build something to prove it can be done or can't be done easily. I believe the attention required from the computer could be minimal. A first go at (...) (28 years ago, 30-Apr-99, to lugnet.robotics)
|
| |
 | | Lego Network Protocol questions
|
|
Hi all. I came to the discussions on the LNP a bit late and was wondering if the following questions had been discussed (I flipped through an old Communications course book and noted some thoughts): - Can we do Carrier Sense *whilst* we are (...) (28 years ago, 30-Apr-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
 | | Re: LEGO light sensor schematic
|
|
In lugnet.robotics, Ralph Hempel writes: (I wrote) (...) [snip] (...) I've done a few myself, but I'll admit I'm not an analog guru. (...) Except all of the anodes go to the wires out, in 2/3 of the pairs this is correct, but one of those pairs (...) (28 years ago, 30-Apr-99, to lugnet.robotics)
|
| |
 | | RCX Challenge
|
|
We've got someone who has made some great progress on the challenge. Chris Phillips has built a robot that can search for, identify and pick up cans. Way to go Chris! I've updated the challenge web site. It now contains the updated rules with the (...) (28 years ago, 30-Apr-99, to lugnet.robotics)
|
| |
 | | RCX Challenge Site
|
|
Oh yeah, the URL is: http:\\home.connect....lenge.html (...) -- Did you check the web site first?: (URL) (28 years ago, 30-Apr-99, to lugnet.robotics)
|
| |
 | | RE: LEGO light sensor schematic
|
|
(...) This is the leftmost pair? That's where the current gets drawn out of the RCX. They both go the same way so you can connect the sensor any way you want - which is why the other two are connected as a bridge to supply power to the circuit... (...) (28 years ago, 30-Apr-99, to lugnet.robotics)
|
| |
 | | Re: LEGO light sensor schematic
|
|
(...) Thanks for your confidence in me, but I didn't say I thought it was the circuit. In fact I can't figure out how it could work this way either. I think probably most of the parts are identified correctly and probably most of the connections. I (...) (28 years ago, 30-Apr-99, to lugnet.robotics)
|
| |
 | | Re: RCX Challenge Site
|
|
(...) (28 years ago, 30-Apr-99, to lugnet.robotics)
|
| |
 | | RE: LEGO light sensor schematic
|
|
(...) OK. I'll take a closer look - my previous description was a broadbrush attempt. Cheers, Ralph Hempel - P.Eng ---...--- A picture is worth a thousand words, but very few sets of a thousand words can be adequately described by a picture... (...) (28 years ago, 30-Apr-99, to lugnet.robotics)
|
| |
 | | Re: Lego Network Protocol questions
|
|
(...) Transmit whenever you feel like it and hope you didn't obliterate data coming from the other direction. Rudimentary, but still quite effective given the typical use pattern with is host driven command/response. With RCX to RCX communication (...) (28 years ago, 30-Apr-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
 | | Re: Lego Network Protocol questions
|
|
(...) Dave, did you catch the crosspost from lugnet.robotics.rcx.legos? I think there were details discussed there that may or may not have amounted to a fairly specific proposal for a protocol for LegOS. Anybody care to summarize whatever was (...) (28 years ago, 1-May-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
 | | RE: Lego Network Protocol questions
|
|
With all of the talk about networking and IP embedding and such, and since I'm working on a proprietary '485 master/slave protocol for a client, I had to dust off a GREAT university text on networks. It devotes an entire chapter to ALOHA and slotted (...) (28 years ago, 1-May-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
 | | Re: Og Needs More Inputs (fwd)
|
|
----- Forwarded message from Michael Gasperi ----- From: "Michael Gasperi" <gasperi@alynk.com> Subject: Re: Og Needs More Inputs (fwd) Date: Fri, 30 Apr 1999 12:43:52 GMT (...) It is an optical (I think) incremental encoder where the 2 quadrature (...) (28 years ago, 1-May-99, to lugnet.robotics)
|
| |
 | | Reliable PC<->RCX Comms
|
|
I'm developing a Spirit.ocx (VC++) program that cooperates with a NQC program to accomplish some tasks, but I'm having some problems creating a reliable method for maintaining contact with the RCX. I wonder if any of you have found good ways for (...) (28 years ago, 1-May-99, to lugnet.robotics)
|
| |
 | | Re: LEGO light sensor schematic
|
|
(...) wrong with it for me so I wouldn't have to. Well I couldn't wait. I broke down and broke into my Light sensor. All I can say is don't do it! The guy that figured out how to package this thing must wear a straight jacket. You will break things (...) (28 years ago, 1-May-99, to lugnet.robotics)
|
| |
 | | RE: LEGO light sensor schematic
|
|
(...) HaHa, I was so busy getting the next release of pbFORTH out that Michael beat me to it. Anyways, good work! I have a little fix to extend the range of the light sensor in % mode that involves blocking the light that comes from the emitter. (...) (28 years ago, 2-May-99, to lugnet.robotics)
|
| |
 | | (canceled)
|
|
|
| |
 | | See my Tidal Wave Disaster!
|
|
Come and see my new Tidal Wave. It can do nearly everything a tidal wave does. I have worked hard to make this new robot. I think that Lego should make an RIS expansion set called "Cool Weather". I have posted two pages with the Tidal Wave and one (...) (28 years ago, 2-May-99, to lugnet.robotics)
|
| |
 | | Something else is needed, I think...
|
|
I'm just wondering how many people agree with me on this point... I think that another code development system is needed for the RCX. Why? Well, it seems like everything that's already out there is either overkill (legos, pbforth for rcx), or (...) (28 years ago, 2-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) Sorry to disagree, but I think we already have a very good range of developing systems: (1) The LEGO software for newbies, (2) RcxCC + NQC + Spirit.ocx for the large majority of the projects, and (3) LegOS for those who want to go beyond the (...) (28 years ago, 2-May-99, to lugnet.robotics)
|
| |
 | | Re: Reliable PC<->RCX Comms
|
|
At 22:38 01/05/99 Saturday , you wrote: [...] (...) [...] Oh yeah, and there's another one: (6) While both programs running, someone turned the unit off and back on again, and pressed the Run button once again. I think the communications should not (...) (28 years ago, 2-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
I think this was only mentioned on the legos mailing list, but there are now two web-based compilers for LegOS. Write the code on whatever text based system you have, cut and paste it into a form on the web, and voila! Get a .srec file mailed back (...) (28 years ago, 2-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) ^^^...^^^ That is exactly the point that I was trying to make. (...) Again, though, such a system would bear the incredible weight of having a full-blown C/C++ cross-compiler and linking system as being part of the package. Making legos (...) (28 years ago, 2-May-99, to lugnet.robotics)
|
| |
 | | RE: Something else is needed, I think...(long)
|
|
(...) I think there IS a bridge, and it's pbFORTH (and since I wrote it I like it :) Here is why I think the current pbFORTH is like the bridge you describe: 1. You don't need the GNU compiler set up to use pbFORTH. I used it to originally write (...) (28 years ago, 2-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) Well, that was what I thought, and I set out to do such a thing way back at the beginning. But the lack of enthusiasm was amazing (possibly not for the basic concept; the alternative hypothesis is that, since I'm a programming language (...) (28 years ago, 2-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) The point is that you still need some OS running on the bare hardware. The standard firmware isn't going to let you do what you need, and you still need something like LegOS anyway. Unless you want to recreate an OS from scratch (which is a (...) (28 years ago, 2-May-99, to lugnet.robotics)
|
| |
 | | Re: Lego Network Protocol questions
|
|
(...) Oops, I must've just caught the tail end of the conversation. I assumed the standard [lame] lego protocol was being discussed, not a custom protocol. Sorry. Dave (28 years ago, 2-May-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) two radically different premises -- the former requiring nothing beyond the hardware, the latter requiring the hardware and an acknowledgeably limited firmware. It would seem to me that what lies exactly in the middle is something which (...) (28 years ago, 2-May-99, to lugnet.robotics)
|
| |
 | | Re: A robot who knows his position (fwd)
|
|
Mike Moran <mm@ee.ed.ac.uk> wrote in response to a compass query from rajackson@qnx.com: (...) Now if you can get the compass manufacturer to vary the degree markings so that the black lines have a grey line next to them before the white in one (...) (28 years ago, 30-Apr-99, to lugnet.robotics)
|
| |
 | | LegOS HOWTO
|
|
Considering the recent discussion on this list, I figure this is as good a time as any to point out that my LegOS HOWTO is now posted at (URL) don't be intimidated! I have aimed this page squarely at anyone with a bare minimum of C or C++ (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) I agree on this point. I've been forced to move to legOS not by intrinsic NQC limitations but by those imposed by the RCX firmware. I still prefer to use RcxCC/NQC when I don't need legOS: programs load much faster, it's a pleasant and (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) I don't know if you guys realize this but if anything like this is ever done we must definitely remain compatible (at least partially) with Spirit.ocx protocols. The Spirit.ocx control is a HUGE bonus we must not throw away!! It makes possible (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) we must definitely remain compatible (at least partially) with Spirit.ocx protocols. (...) outside world with endless possibilities, and processing power that it will never be able to match! (...) already been done for us. And please, do not (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: LEGO light sensor schematic
|
|
(...) Ah... much better, I figured one or two components were backwards. Just to clean up the schematic a bit you could flip R1 (75R) to the right side of the Q4. I would also bring R8 (12R) in line with the LED. This would then be a more standard (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: LEGO light sensor schematic
|
|
(...) OK, I fixed that and in the process discovered they should be PNPs. 3Hp83 is a BC857 GP PNP from Philips. Looks better now. (...) I think photo diode used in photovoltaic mode. It looks like it pushes the voltage down from that established by (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...(long)
|
|
In article <000101be94cb$a8fd58...a@pro150>, Ralph Hempel <rhempel@bmts.com> writes (...) My QBasic program available from www.phesk.demon.co.uk/lego/ can download the Lego firmware from DOS - where can I find your new firmware to test it with, (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) I am not sure how much you can extend the capabilities of the firmware while maintaining its basic dispatch loop. There are some very basic design constraints that would be difficult to change without redoing all of the firmware. If you (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) If you believe you have good ideas for a language, my opinion is that you should propose something to the list, find people who want to work with you on this (assuming you don't want to work alone), ignore the people who say you know nothing (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
I think that a good solution would be to have Legos work as a true operating system that stayed loaded in the brick and would accept downloading compiled programs for it to run. Maybe the firmware replacement idea that has been tossed around could (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) I think new firmware is a good way to go. I would vote for a completely new byte code, perhaps similar in spirit to the original, but designed fresh from the ground up. There is no source for the current firmware, although there is pseudocode (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) If you really want to design a new bytecode that is completely flexible, I suggest using the millions of manhours put into the Java Virtual Machine would be worthwhile. I looked at the idea of porting JVM to the RCX briefly before, but decided (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | RE: Something else is needed, I think...
|
|
(...) If we are going to the trouble of new bytecode, then we need a new compiler. If we design a new compiler, then what language will it be? Yes, we could use C as the base and compile to pcode which is essentially what NQC does if I'm not (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: LEGO light sensor schematic
|
|
(...) [snip] I'm happy to see that some of my concerns have been born out with these changes, it looks more like a happy little circuit now. (...) Are we sure that the photodiode is located in the schematic correctly? It doesn't look like its biased (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) My thoughts on the JVM: - too complicated for what we need or want - no direct support for interfacing with the RCX I envision the new byte code being specific to the RCX, and as simple as possible to get the job done, which is the exact (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) C may be the best choice for a base language to start with simply because its well known. Quite frankly, if the bytecode is written reasonably well, different compilers for different base languages should be very feasible - compilers based on (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) I agree, that would make pbForth much more appealing if the source could be compiled on a pc in a nice gui environment and then the bytecode loaded into the rcx. Not only could someone enhance the gui front end as Mark has suggested, but (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) I guess that depends on who you talk to. Personally, I want an object oriented language with multithreading support. I want to be able to write generic code that can be reused in multiple applications (ie, here is a module that follows a line, (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | RE: Something else is needed, I think...
|
|
(...) Do NOT underestimate the amount of work we are talking about. I took a working version of hFORTH for the PC and ported a few machine specific definitions and rewrote the IO drivers and debugged and tested using GNU tools, and I have 80 hours (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | RE: Something else is needed, I think...
|
|
(...) Once you get around the idea that the RCX does the compiling which makes it platform independent, you will see the light... (...) This is a good plan. You have my full support :-) Cheers, Ralph Hempel - P.Eng ---...--- Check out pbFORTH for (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | RE: Something else is needed, I think...
|
|
Maybe we could write a program that compiles c source code into forth :) just joking Joel Shafer joel@connect.net -- Did you check the web site first?: (URL) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) Thank you. Kekoa. I was starting to think I was completely alone in my attitudes. Just a couple of comments on what I think a new byte code should do or be 1) It should resemble machine language. The commands in the bytecode should be (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) I don't deny that these are reasonable things to want. But you don't need the JVM to get these. The problem with the JVM is that there is so much extra fluff associated with Java. You mentioned 64-bit floats and ints, security, etc. Why start (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) Basically what you are talking about at this level is an interpreted machine language. The only benefit you get from interpreting it rather than running directly on the hardware is that you can catch errors. However, if the bytecodes are (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) All I am saying is that there will be no existing product that does exactly what everyone wants. However, I think it is worth considering JVM as a starting point close to what we want since it represents a huge body of solid code. (...) (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) I don't think I am underestimating the amount of work, actually.Just because a language has a GUI toolkit does NOT make it user friendly or portable. (...) Then it's not self contained on TWO counts. One, as you mentioned, you need NQC to get (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) Yes. (...) Wrong. Because we could design the instruction set from scratch ourselves, a small set of instructions could be included in the entire instruction set which do things require a great deal of regular machine instructions to do. (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) Q: How large are the compiled FP emulation routines for the RCX? -Kekoa (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | RE: Something else is needed, I think...
|
|
Kekoa wrote: <actually he wrote stuff here that I snipped out> (...) Ah, a refreshing viewpoint :-) Getting concrete ideas and proposals out makes sense. If you don't have the time to propose a CONCRETE idea or plan, then you sure don't have time to (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) Well, having a bytecode for turning on a motor seems little benefit compared to calling a library function to do it. From the user's point of view, the effort and the result are similar. (...) Actually, you need to have a call stack and a (...) (28 years ago, 3-May-99, to lugnet.robotics)
|