 | | 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, (...) (21 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 (...) (21 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 (21 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 (...) (21 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 (...) (21 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 (...) (21 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 (...) (21 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 (...) (21 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 (...) (21 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, (...) (21 years ago, 8-Jan-04, to lugnet.robotics.rcx, FTX)
|
