 | | Re: Problems with if-close with phantom.dll
|
|
Hi Valeria, (...) I can't understand the language you are using, but, as far as I know, in many other languages for the RCX you have to wait for the PlayTone to complete before exiting the task. Probably you need to insert a Wait instruction, your (...) (23 years ago, 28-Jan-04, to lugnet.robotics.rcx)
|
| |
| | Problems with if-close with phantom.dll
|
|
Hi to everyone, it's the first time for me on lugnet newsgroup. I was wandering wether you can help me!! I have troubles with "If" function... maybe it's my fault, but when I write a very very simple task (made so simple in order to understand where (...) (23 years ago, 26-Jan-04, to lugnet.robotics.rcx)
|
| |
| | Re: BricxCC release 3.3.7.7
|
|
(...) Unfortunately, BricxCC is still not downloading the brickOS firmware correctly. I will look into this problem and try to fix it. In the mean time, you can use firmdl3 which works correctly. John Hansen (23 years ago, 23-Jan-04, to lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.legos, lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
|
| |
| | BricxCC release 3.3.7.7
|
|
I've released version 3.3.7.7 of BricxCC today. It adds a Spybot EEPROM tool window. It adds a new configurable watch tool window. It adds a new generic set source value tool window. It adds a hot key (F2) for the pbForth console. The position of (...) (23 years ago, 22-Jan-04, to lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.legos, lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
|
| |
| | Re: PIC-RCX half-duplex IR receive and transmit
|
|
(URL) forgot my website with the documentation, sorry! (23 years ago, 16-Jan-04, to lugnet.robotics.rcx)
|
| |
| | PIC-RCX half-duplex IR receive and transmit
|
|
I just finished a PIC16F84A application which receives IR commands from the RCX or RCX remote control, saves them and transmits another command back again. You can put your own command(s) in EEPROM for transmission. The firmware is commented (well, (...) (23 years ago, 16-Jan-04, to lugnet.robotics.rcx)
|
| |
| | Re: BricxCC release 3.3.7.6
|
|
Hi John, Thanks to your pre-built BrickOS tools, I have finally installed it on my Windows 2000 machine (I tried several times in the past... no luck !). The installation was really fast and easy, the only problem I got was that the default BrickOS (...) (23 years ago, 15-Jan-04, to lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.legos, lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
|
| |
| | Re: BricxCC release 3.3.7.6
|
|
(...) I will make this change. Thanks for the report! John Hansen (23 years ago, 12-Jan-04, to lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.legos, lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
|
| |
| | Re: BricxCC release 3.3.7.6
|
|
small suggestion: when you've a syntax error in NQC, it goes like this - error is reported - you correct the error - recompile the source - code is downloaded - error message disappears In my opinion, the last 2 actions should be the other way (...) (23 years ago, 11-Jan-04, to lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.legos, lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
|
| |
| | Re: installing Robolab under Mac OS X
|
|
(...) Great news for MAC/OSX fans this is not a rumor according to the PITSCO 2004 catalog there will be Native OSX CD version available JUNE 2004. You will need ROBOLAB 2.5 software with training missions. If you have the 2.5 ROBOLAB RIS you can (...) (23 years ago, 11-Jan-04, to lugnet.robotics.rcx, FTX)
|
| |
| | Re: motor repair
|
|
hi Philippe, (...) Sorry, I don't know any translator , (with 1 Europe there should be one :-) but it's no problem for me to translate a few pages, tell me what pages you're interested in. Btw, Nice work, your laser target finder ! cheers, Stef (...) (23 years ago, 11-Jan-04, to lugnet.robotics.rcx, lugnet.technic, lugnet.robotics)
|
| |
| | Re: Design by Contract (long post)
|
|
Thanks, Tim. I haven't used the #x idiom myself - I like it. Your implementation with the boolean: (...) Will need an extra level of parenthesis surrounding the bool so that its declaration scope is made local. You can certainly go to town with this (...) (23 years ago, 10-Jan-04, to lugnet.robotics.rcx, FTX)
|
| |
| | Re: Design by Contract (long post)
|
|
(...) For more fun with asserts: See if your compiler supports the FILE and LINE macros (or something equivilant). #ifdef NDEBUG #define assert(x) ((void)0) #else #define assert(x) if (x) else assertfail(FILE,LINE); #endif your assert_fail function (...) (23 years ago, 9-Jan-04, to lugnet.robotics.rcx, FTX)
|
| |
| | Re: Implementation of Installable Timers
|
|
Iain McInnes wrote: [snip] (...) Great idea! (...) In your implementation, would it be possible for the client task to be killed (in the case of a run-away task)... causing the struct to be deallocated... while the struct is still in the linked (...) (23 years ago, 8-Jan-04, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
| |
| | Re: Design by Contract (long post)
|
|
(...) I agree it seems to be the wrong way round. That's the standard implementation. NDEBUG seems to stand for "No debug". One advantage of making it negative, is that you get the assert()s if you don't do anything (ie dont define NDEBUG). BTW, (...) (23 years ago, 8-Jan-04, to lugnet.robotics.rcx, FTX)
|
| |
| | Re: Design by Contract (long post)
|
|
(...) D'oH! Thanks, Tim. I was very careful composing the original post, but added the example in as an after thought - Well spotted. Iain. (23 years ago, 8-Jan-04, to lugnet.robotics.rcx, FTX)
|
| |
| | Re: Design by Contract (long post)
|
|
(...) <delurk> The first definition of assert is the correct, standard definition. However there is a slight boo boo in the original post in the line: assert (myptr = malloc (sizeof (mystruct)); Which will delete the malloc when NDEBUG is defined. (...) (23 years ago, 8-Jan-04, to lugnet.robotics.rcx, FTX)
|
| |
| | USB Tower range
|
|
Hi, I recently bought the RCX2.0 and I am a little disappointed at the range for the USB tower. Though configured to be at long range I doubt I can implement a range greater then 5 or 6 feet. Is this normal.? Am I missing something.? Paul Reedman (23 years ago, 7-Jan-04, to lugnet.robotics.rcx)
|
| |
| | Re: Design by Contract (long post)
|
|
(...) Hi Iain! (...) Cool! (...) I have a question about this: If NDEBUG is defined, shouldn't it still execute x? That is, shouldn't the code in assert.h (or wherever) be: #ifdef NDEBUG #define assert(x) (x) #else #define assert(x) if (x) else (...) (23 years ago, 8-Jan-04, to lugnet.robotics.rcx, FTX)
|
| |
| | Design by Contract (long post)
|
|
Hi, people. The reason for the flood of posts is that I've been trying to get authenticated on LUGNET for the last week :( But as you can see, I'm authenticated now :) On to the topic of this post (sorry for such a long post): I have created an (...) (23 years ago, 8-Jan-04, to lugnet.robotics.rcx, FTX)
|
