 | | Re: now normally baumfamily != enteract
|
|
(...) Email to update crynwyr? Yes I hope so, yes I've tried, yes we're staying tuned, sorry I was unclear, that's what I meant when I mentioned I had seen a mailto channel work there before. But Lego I don't know how to reach. Do you mean to say (...) (22 years ago, 2-Feb-03, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Is there a NQC HowTo out there someplace?
|
|
I was in the same situation as you when I started out with NQC and I found the following resources helpful... Programming Lego Robots using NQC by Mark Overmars is a good tutorial...I probably used it the most to learn the basics of NQC... (...) (22 years ago, 2-Feb-03, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: IR header how optional
|
|
(...) Whether serial transmission is as simple as start:data:parity:stop repeated, or not, I still have no idea. But I'm posting again to say in those calculations I was off a whole order of magnitude, sorry. I imagine the calculator I used reported (...) (22 years ago, 2-Feb-03, to lugnet.robotics.rcx)
|
| |
| | Re: now normally baumfamily != enteract
|
|
(...) Email them perhaps? (22 years ago, 2-Feb-03, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Problems with NQC and math operations
|
|
Jeff, Your problem is with the 16 bit integer size that NQC uses. All integers are in the range -32768 to 32767. Using 10000 to simulate fixed point math operations is killing you. Everything works when you replace theta and D with constants because (...) (22 years ago, 2-Feb-03, to lugnet.robotics.rcx.nqc)
|
| |
| | Problems with NQC and math operations
|
|
Hi- I'm currently working on a project to get a dead-reckoning navigation system to work with NQC and the RCX. Right now I have a compass sensor and a rotation sensor hooked up and the idea is that with an angle and a distance, I can get an x and y (...) (22 years ago, 2-Feb-03, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: LNP problem
|
|
(...) You need to compile remote.c for the RCX, that's the part running on the RCX. rcx.c and rcx.h define an interface for your application to use the functions provided in remote.h. Namely to turn on/of/break/reverse the motor ports and to read (...) (22 years ago, 2-Feb-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Is there a NQC HowTo out there someplace?
|
|
(...) Well there are books called "Teach yourself C in 5 days", 21 days and so on... try amazon books. NQC is not actually a full C compiler, it has been simplified a great deal and if you learn the basics from a book, you'd be ready to go with NQC (...) (22 years ago, 2-Feb-03, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: IR header how optional
|
|
(...) I doubt anything (short of a 2MV Lightning Flash) will warm anything in 1 msec. ;) Also, the receiver won't warm up until the header has been read in completion and decoded. So I doubt it's used for that. Normally, in any communication, you'd (...) (22 years ago, 2-Feb-03, to lugnet.robotics.rcx)
|
| |
| | IR header how optional
|
|
(...) Yep. But via our solid new reply framing code, thanks again, now I can see ... (...) Nope. At least not here: now that I look, I see my RCX often doesn't require the PC to send x 55:FF:00. IR command packets like x 10:FE 10:FE PBAliveOrNot and (...) (22 years ago, 2-Feb-03, to lugnet.robotics.rcx)
|
| |
| | Re: command framing as seen from kernel/program.lrkey_handler
|
|
(...) Just to be more certain we're understanding each other, if that's ok, I'll mention that ... 1) Newbie that I am, I have no clue how frequently brickos switches on bit masks. I wonder if only to decode xD2 RemoteCommand. 2) Using log2(xx & -xx) (...) (22 years ago, 2-Feb-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: frame RCX reply how
|
|
(...) Yes helpful framing rules thanks. (...) Thanks in particular for pointing out the before & after rubbish. Me, just now I began quoting this rule in a fog, somehow not immediately appreciating that: The receive framing in bricxcc withstands (...) (22 years ago, 2-Feb-03, to lugnet.robotics.rcx)
|
| |
| | Is there a NQC HowTo out there someplace?
|
|
Hello, I have reached the limits of what Mindstorm 2.0 software can do a long time ago and now want to go further. I think I would try the NQC. My problem is that I do not know anything about C or NQC. I have learned Pascal and Basic language (and (...) (22 years ago, 1-Feb-03, to lugnet.robotics.rcx.nqc)
|
| |
| | now normally baumfamily != enteract
|
|
Perhaps this is not normal? (URL) don't have permission to access /~dbaum/lego/nqc/index.html on this server. Apache/1.3.26 Server at www.enteract.com Port 80 Yet I'm taken there from: (URL) such famous links as: (URL) wonder if the update to these (...) (22 years ago, 2-Feb-03, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: frame RCX reply how
|
|
"Pat LaVarre" <ppaatt@aol.com> wrote in message news:H9nAFD.7v@lugnet.com... (...) like x (...) byte x (...) course (...) the 4 (...) find (...) 10 EF? I follow you now (helps to look at the actual code ;-)... I would expect that raw byte sequence (...) (22 years ago, 1-Feb-03, to lugnet.robotics.rcx)
|
| |
| | Re: frame RCX reply how
|
|
Concerning the parsing of LEGO packets, I've found these bits to be useful in coming up with a parsing algorithm: * Packets start with 0x55 * Individual bytes of a packet are sent with little or no delay in between bytes * Packets may or may not (...) (22 years ago, 1-Feb-03, to lugnet.robotics.rcx)
|
| |
| | Re: frame RCX reply how
|
|
(...) ... (...) Corrected/ elaborated in [square brackets]. I found my error by comparing bricxcc to a delightfully inaccurate summary of ~kekoa on replies that I built some time ago. Except again, op 63/6B UploadRam I find only in in "LASM Byte (...) (22 years ago, 1-Feb-03, to lugnet.robotics.rcx)
|
| |
| | Re: frame RCX reply how
|
|
(...) Ouch, we may be framing the hex differently here, sorry. The only x10 Ping known to me is the x10/18 command op that gets embedded inside of a packet like x 55 FF 00 10 EF 10 EF to provoke a reply packet like x 55 FF 00 18 E7 18 E7, or vice (...) (22 years ago, 1-Feb-03, to lugnet.robotics.rcx)
|
| |
| | Re: frame RCX reply how
|
|
(...) can be (...) This is the PBAliveOrNot (or ping) packet type. It has the side- effect of reinitializing the toggle bit used to determine repeat packets. Do you have the Minsdstorms SDK? It covers all the standard LEGO packet types in detail: (...) (22 years ago, 1-Feb-03, to lugnet.robotics.rcx)
|
| |
| | Re: frame RCX reply how
|
|
(...) (URL) bytes Accordingly I'd now guess the firmdl3/rcx_comm.c algorithm for framing standard RCX replies is: (...) 1) Send the bytes of the command packet. 2) Loop to receive up to equally many bytes echoed. If 100ms elapses twice without (...) (22 years ago, 1-Feb-03, to lugnet.robotics.rcx)
|
