 | | Re: Textbook
|
|
[Joe Kopena] spake unto the ether: (...) Wait for Fred Martin's book (it's due out in the fall, isn't it?) My self-taught practical engineer's take on robotics is that you can't separate the brain from the body, so to speak. Computer scientists tend (...) (27 years ago, 10-Apr-00, to lugnet.robotics.handyboard)
|
| |
 | | Re: Textbook
|
|
Hi. Here's a recommendation: Artificial Intelligence and Mobile Robots Edited by: D. Kortenkamp (NASA), P. Bonasso (NASA), and R. Murphy (U. South Florida) MIT Press (1998) This book is a collection of research papers and editorial essays. It is not (...) (27 years ago, 10-Apr-00, to lugnet.robotics.handyboard)
|
| |
 | | Re: Textbook
|
|
(...) How about the Joe Jones/ Anita Flynn book "Mobile Robots" ? That has alot of good intro materials and it's not too ridiculously expensive. Supports Interactive C too. Either that or the new Karl Lunt book, which I haven't yet seen. Heard it (...) (27 years ago, 10-Apr-00, to lugnet.robotics.handyboard)
|
| |
 | | WTB:handyboard
|
|
hi, i would like to buy a handyboard or borrow one(i'll pay for usage) for a week from someone on this dlist. my partner and i were going to use a HP calculator as a controller for a robot, but we haven't been able to get the compiler to work on the (...) (27 years ago, 10-Apr-00, to lugnet.robotics.handyboard)
|
| |
 | | Textbook
|
|
Can anyone on here reccomend a good textbook for a robotics class? The class is intended for upperclass and graduate computer science students who have already taken classes in artifical intelligence. We're going to be using LEGO kits and (...) (27 years ago, 10-Apr-00, to lugnet.robotics.handyboard)
|
| |
 | | servos
|
|
Hi, Could someone tell me what the advantages of the servo_a7.icb over the servo.icb are?? thanks (27 years ago, 10-Apr-00, to lugnet.robotics.handyboard)
|
| |
 | | Re: About HAndy board and PIC
|
|
Hi there Just saw your message and thought I could give you a few tips... I also live in SA and have built a HandyBoard. From my experience so far, a robot built around the HandyBoard is very easy to get going, has a wide range of posiblities and is (...) (27 years ago, 10-Apr-00, to lugnet.robotics.handyboard)
|
| |
 | | Re: micro scout programming?
|
|
in article dbaum-BB4367.1519470...ugnet.com, Dave Baum at dbaum@spambgoneenteract.com wrote on 4/9/00 1:19 PM: (...) [snip] (...) On that LugNet page I found a link to Ben Jackson's page where he described his implementation of VLL from legOS: (URL) (...) (27 years ago, 10-Apr-00, to lugnet.robotics)
|
| |
 | | About HAndy board and PIC
|
|
I have read od a newsgroup of robotics that you have build a robot with the Handy Board with a PIC. What advcie can you give me . I have to start from scrath . What I need to buy Handy Board + (what componets+tools??) to build a soccer player (...) (27 years ago, 10-Apr-00, to lugnet.robotics.handyboard)
|
| |
 | | brushless motors
|
|
has anyone had any success hooking up brushless motors to a handyboard? basically, the problem i'm having is there is only one gnd pin on the motor, which is both for the internal digital logic and to sink the current through the motor. it's a (...) (27 years ago, 10-Apr-00, to lugnet.robotics.handyboard)
|
| |
 | | Re: micro scout programming?
|
|
(...) Yes, to a limited extent. (...) The 'P' program just plays back a 'script' that you've programmed in. Programming is done via VLL (visible light link), which is supported by the Scout. There are a bunch of commands you can send over VLL from (...) (27 years ago, 9-Apr-00, to lugnet.robotics)
|
| |
 | | micro scout programming?
|
|
Hi! I recently purchased a micro scout kit (Droid Developers Kit) for my son. Does anyone have information on it? Specifically: 1) can it be programmed 2) what is the undocumented 'P' program? 3) can it be used in conjunction with an RCX unit? (...) (27 years ago, 9-Apr-00, to lugnet.robotics)
|
| |
 | | Re: location of NQC group?
|
|
(...) Safest thing is a multi-step process: 1. Announce that a new group/list lugnet.robotics.nqc will soon be replacing lugnet.robotics.nqc (i.e., a "heads-up"). 2. [A day or so later] Create lugnet.robotics.nqc and associated web areas and mailing (...) (27 years ago, 9-Apr-00, to lugnet.admin.general, lugnet.robotics.rcx.nqc)
|
| |
 | | Re: NQC Ignores based on your pbrink
|
|
(...) Yep, you can #ifdef however you want, and NQC supports -D and -U options on the command line that allow you to define (or undefine) symbols before the compile takes place. This is handy if you're using Makefiles, but even in an ordinary shell (...) (27 years ago, 9-Apr-00, to lugnet.robotics.rcx.nqc)
|
| |
 | | Re: NQC Ignores based on your pbrink
|
|
I definitely intended to mean portable source. And that the "__FIRMWARE" would be used in compiler directives rather than in the code. It is a simple matter for me to define my own __FIRMWARE (or anything else, right?) and do #ifdef's to my heart's (...) (27 years ago, 9-Apr-00, to lugnet.robotics.rcx.nqc)
|
| |
 | | Re: location of NQC group?
|
|
(...) Personally I like the move to robotics.nqc I don't like the idea of splitting it up. Cross posting would make reading the groups very annoying. I'd say make the current one archive only putting a LARGE message like the rules pop up to new (...) (27 years ago, 9-Apr-00, to lugnet.admin.general, lugnet.robotics.rcx.nqc)
|
| |
 | | Re: NQC Ignores based on your pbrink
|
|
(...) I agree wholeheartedly. I don't want to see people selling their bot code. It's all about sharing and learning. Dean -- Coin-Op's For Sale!: (URL) Lego Workshop: (URL) Lego Club: (URL) (27 years ago, 9-Apr-00, to lugnet.robotics.rcx.nqc)
|
| |
 | | Another makefile suggestion
|
|
This particular change would be useful in the lib directories. Instead of using this: SOURCES=memset.c strcmp.c ..... etc. Use this: SOURCES := $(wildcard *.c) Note the use of ':=', not '='. This will pick up ALL .c files in the current directory. (...) (27 years ago, 9-Apr-00, to lugnet.robotics.rcx.legos)
|
| |
 | | Re: NQC Ignores based on your pbrink
|
|
(...) This seems reasonable to me. Plus, it has the added benefit of being inherently open: source is all about "here's how to do this"; binaries are "here's a thing that does this". It's nice to encourage the first attitude. (27 years ago, 9-Apr-00, to lugnet.robotics.rcx.nqc)
|
| |
 | | Re: NQC Ignores based on your pbrink
|
|
(...) This first define (__RCX = 2) will happen automatically in NQC when you select RCX 2.0 as the target for compilation. Selecting an RCX 1.0 target will cause the symbol to be defined as 1. (...) I hope I don't have to add a __FIRMWARE symbol... (...) (27 years ago, 9-Apr-00, to lugnet.robotics.rcx.nqc)
|