 | | Re: What should be in the next version of RcxCC
|
|
Hi! well, I am missing something in an otherwise great RcxCC... Variable values display in dec/hex/binary would be great, as converting by hand every time is tedious. thanks /Vlad (25 years ago, 22-Nov-99, to lugnet.robotics.rcx.nqc)
|
| |
| | NQC wishlist
|
|
I am not sure if there is such a wishlist... I remember there was a "call for wishes" for RxCC... The biggest problem with the standard firmware is the small amount of variables. Since not every use of a variable will use all 16 bits, I think it (...) (25 years ago, 22-Nov-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: sending files to pbForth - results
|
|
(...) think (...) Also, try the places like www.forth.org or www.taygeta.com (...) com port (...) I'm afraid there is no any good way. Seems this "garbage" appears due to some design problems in IR tower scheme. Usually it happened whenever the (...) (25 years ago, 22-Nov-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Battery Status ?
|
|
Has anybody figured out the meaning of values got from the BATTERY sensor ? Currently, my little testproggy "cputw(BATTERY>>6);" displays F9, and i guess my batteries are close to their end of life. BTW, if you read this, Markus: The new rotation (...) (25 years ago, 22-Nov-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Help - RCX sensor port failure
|
|
(...) I should tell my wife about that ;-) Anyway, in the LEGO supplied software there is a little test window that you can pull out that lets you configure sensors without writting and running programs. You can also see the values that the RCX is (...) (25 years ago, 22-Nov-99, to lugnet.robotics.rcx)
|
| |
| | Re: sending files to pbForth - results
|
|
Hello. I became acquainted with pbforth via Jonathan Knudsen's (O'Reilly) books and think that it's a terrific place to learn forth. I am using CRT with line delay=100 and char delay=20, but if I wait between carriage returns, I get "garbage" I (...) (25 years ago, 21-Nov-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Help - RCX sensor port failure
|
|
(...) "Stuck" was the magic word. It was (of course) somehow only stuck thinking it was a touch sensor port. I used the Mindstorms RCX code to re-program all sensor ports as light sensors downloaded and then - nothing - still the same error (no (...) (25 years ago, 21-Nov-99, to lugnet.robotics.rcx)
|
| |
| | Re: Help - RCX sensor port failure
|
|
Franz-Michael S. Mellbin <fischer-mellbin@fis...llbin.com> wrote in message news:FLK4xM.F86@lugnet.com... (...) and (...) is (...) Reading 0 or 1 means the port is configured for touch type input. I don't see anyway it can get stuck in this mode. (...) (25 years ago, 21-Nov-99, to lugnet.robotics.rcx)
|
| |
| | Help - RCX sensor port failure
|
|
Our first RCX has a sensor port failure on port 3 (Aaaarghhh...). The sensor port will read 0 and 1 only. It can react with the touch, light and rotation sensors (showing 0 or 1), so it somehow still senses if a sensor is present. We have no idea (...) (25 years ago, 21-Nov-99, to lugnet.robotics.rcx)
|
| |
| | Re: Lego s/w and spirit.ocx
|
|
(...) NQC doesn't use spirit.ocx, so if you're just using the command line version of NQC, don't worry about spirit.ocx. However, if you're using RcxCC, then you'll need to make sure spirit.ocx is installed. Dave Baum (25 years ago, 21-Nov-99, to lugnet.robotics.rcx.nqc)
|
