 | | patch for lnpd ( Collision problem in far-mode )
|
|
(...) i had never seen this interesting effect, because i always had my tower in near mode, where it only happens if you put the tower straight in front of a wall. I suspect it's a little more complex to explain what happens here, because the tower (...) (25 years ago, 12-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | RE: Drive R/C Servos with the RCX and pbForth (long)
|
|
(...) Oops, forgot to answer the main question. Yes, I have thought about making boards...and as soon as I get out from under my current workload I'm going to give it even more thought.... It is just not worth my time and money to make any less than (...) (25 years ago, 12-Feb-00, to lugnet.robotics, lugnet.robotics.rcx.pbforth, lugnet.robotics.rcx)
|
| |
| | RE: Drive R/C Servos with the RCX and pbForth (long)
|
|
(...) I hear you, John. Learning a new language can be a bit tricky, and I won't go into the details of why I think it's a good idea to learn different languages to get the benefit of different ways of thinking about problems...oops, don't get me (...) (25 years ago, 12-Feb-00, to lugnet.robotics, lugnet.robotics.rcx.pbforth, lugnet.robotics.rcx)
|
| |
| | Re: Drive R/C Servos with the RCX and pbForth (long)
|
|
Ralph - I'm interested in the use of servos with the RCX, but I have no interest in learning the quirks of another computer language. I'm already a bit familiar with Visual Basic,and control the RCX with it. Can your pbForth solution be duplicated (...) (25 years ago, 12-Feb-00, to lugnet.robotics, lugnet.robotics.rcx.pbforth, lugnet.robotics.rcx)
|
| |
| | Re: Having trouble with -D option
|
|
One other thing ... when I first made a simple program to demonstrate the problem, I used a lowercase d for my symbol and got this error: # Error: parse error File "rcx.nqh" ; line 118 # void SetDirection(const int o, const int d) { asm { 0xe1, (o) (...) (25 years ago, 12-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Windows NT Success Story!
|
|
Thanks a lot for this really helpful and detailed post! Especially thanks for making the result of your success story available for download. This allowed me to simply download the whole thing and start experimenting with legOS applications rather (...) (25 years ago, 10-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | RE: LNP Example please
|
|
I have observed the same behavior... only by night. I think it must be the tower receiving echoes of its own packets. The sollution: place the tower far away from objects that can reflect light (including yourself). I also changed the tower battery (...) (25 years ago, 12-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | RE: Drive R/C Servos with the RCX and pbForth (long)
|
|
(...) I should add here that no external power source is necessary to drive the servo. This is important since a micro or miniservo and an SMT version of the driver can be made to fit INSIDE a space similar to a worm gear box (6588 in LDraw). I'm (...) (25 years ago, 12-Feb-00, to lugnet.robotics, lugnet.robotics.rcx.pbforth, lugnet.robotics.rcx)
|
| |
| | RE: Drive R/C Servos with the RCX and pbForth (long)
|
|
(...) No, the servo needs power to the + and ground terminals to drive the motor to the setpoint indicated by the signal wire. If I don't invert the signal there is no power for about 30msec and only 1 or 2 msec ov voltage on the motor port. By (...) (25 years ago, 12-Feb-00, to lugnet.robotics, lugnet.robotics.rcx.pbforth, lugnet.robotics.rcx)
|
| |
| | Re: Drive R/C Servos with the RCX and pbForth (long)
|
|
(...) If you're using a custom motor driver in pbForth, why use the inverter circuit at all? Why not just generate the desired waveform directly? Is there not enough current to drive the servo that way? --Ben (25 years ago, 12-Feb-00, to lugnet.robotics, lugnet.robotics.rcx.pbforth, lugnet.robotics.rcx)
|
| |
| | Re: Having trouble with -D option
|
|
Thanks for the quick response. "It's fixed in the next release, which is due in a week or so" qualifies for excellent support, IMHO. :) My workaround is a REXX exec rewritting a small header file on the fly before each compile. -- Mark Haye, haye (...) (25 years ago, 12-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Having trouble with -D option
|
|
Yes, I noticed that too, but I'm trying to program multiple RCXs with the same source, and the symbol is meant to represent the RCX's id, so it must have multiple values. Thanks anyway for the quick response. -- Mark Haye, haye (at) us (dot) ibm (...) (25 years ago, 12-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Drive R/C Servos with the RCX and pbForth (long)
|
|
Hi again everyone! A few days ago I announced that I had developed a nice little circuit using easily available parts that would let you connect servos to the RCX - with no external batteries or microprocessors or anything! At that time, I said that (...) (25 years ago, 12-Feb-00, to lugnet.robotics, lugnet.robotics.rcx.pbforth, lugnet.robotics.rcx)
|
| |
| | Re: scout.nqh no longer necessary?
|
|
(...) Correct. Initially (2.1 b1) I put the Scout support in a separate include file because I wasn't ready to merge all of the changes together. As of b2, the compiler's built-in system include file includes RCX, Cybermaster, and Scout APIs. Dave (25 years ago, 12-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: LNP Example please
|
|
*Embarrased look* sorry I shouldn't of missed that.. Sorry to hassle you but I am stuck yet again. The lnptest program just records collision after collision. I have no other IR devices in the area (as far as I know anyway) It doesn't display any of (...) (25 years ago, 12-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: scout.nqh no longer necessary?
|
|
(...) Yes, this is true as of 2.1.b2. (25 years ago, 11-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | scout.nqh no longer necessary?
|
|
It looks like Scout programs no longer need `#include "scout.nqh"', and the file has been removed from the NQC beta distribution. Is that correct? I've been confusing someone new to NQC because I didn't realize this :( --Ben (25 years ago, 11-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Having trouble with -D option
|
|
You found a bug - NQC is actually defining D to be the tokens =1, which then leads to a lot of confusion later on. Basically I bungled the pointer math. I fixed the source so the next release (2.1 final) should be fine. I'll probably release 2.1 in (...) (25 years ago, 11-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Having trouble with -D option
|
|
(...) Same with 2.1b3. FWIW, #ifdef D task main() {} #endif works as expected. D is getting defined, just not to 1. (Or to any number.) (25 years ago, 11-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Having trouble with -D option
|
|
If I compile this program (named d.nqc): /* nqc program */ #if (D == 1) task main() {} #endif with the command: nqc -DD=1 d.nqc I get the following error: # Error: syntax error in expression File "d.nqc" ; line 2 # #if (D == 1) # ^ #---...--- # 1 (...) (25 years ago, 10-Feb-00, to lugnet.robotics.rcx.nqc)
|
