|
 | | RE: H8/300 Assembler/C interface
|
| (...) Sorry, looks like I need sleep too! (...) Hmm, looks like r2 is a copy of the high byte of the second long, but the complete long is pushed onto the stack! So the thing about GCC NOT splitting is true, it just keeps a copy of the higher order (...) (23 years ago, 21-Apr-01, to lugnet.robotics.rcx)
| |
|  
long
(score: 1.121)
|
|
| | Re: Neural network for legOS... ??
|
| (...) Sorry Niels, but I would say just try it yourself, they're not that hard to do, failing that if you can find the source for a small ANN, then that stands a good chance of working, I'm running quite a powerful evolutionary algorithm on mine, (...) (24 years ago, 27-Mar-01, to lugnet.robotics.rcx.legos)
| |
|
long
(score: 1.121)
|
|
| | Re: Electrical Data Link between 2 RCXs
|
| Thanks for the info on the electric datalink. It's a clever idea that I never would have thought of myself. It seems to me that you could cut down on your transmission time if you changed the shape of your pulse train. The pauses between bits don't (...) (24 years ago, 26-Mar-01, to lugnet.robotics.rcx.nqc)
| |
|
long
(score: 1.121)
|
|
| |
|
long
(score: 1.121)
|
|
| | Re: Electrical Data Link between 2 RCXs
|
| (...) Hi Dean, meanwhile I followed your suggestions and implemented a scheme that uses a pulse scheme like this: ______ ______ ______ __ ______ ______ ___...___ Start Bit3 Bit2 Bit1 Bit0 A bit value of 1 results in a long pulse, a bit value of 0 in (...) (24 years ago, 3-Apr-01, to lugnet.robotics.rcx.nqc)
| |
|
long
(score: 1.120)
|
|
| | RoboLab prg size limit?
|
| I'm using robolab 1.5 for a school project, and i'm encountering some difficulty. I think i'm a pretty profiencent programmer if i think abotu it long enough, but right now i'm baffeled. I'm pretty sure the program is crashing in the RCX, so maybe (...) (24 years ago, 9-Apr-01, to lugnet.robotics.rcx.robolab)
| |
|
long
(score: 1.120)
|
|
| | Re: H8/300 Assembler/C interface
|
| (...) Not my GCC: 00000016 <_main>: 16: 6d f6 mov.w r6,@-e7 <-- save frame pointer 18: 0d 76 mov.w r7,r6 <-- new frame pointer 1a: 6b 00 00 00 mov.w @0x0:16,r0 <-- r0r1 is 1st long param 1e: 6b 01 00 00 mov.w @0x0:16,r1 22: 6b 02 00 00 mov.w (...) (23 years ago, 21-Apr-01, to lugnet.robotics.rcx)
| |
|
long
(score: 1.119)
|
|
| | Re: New RcxCC revision posted
|
| (...) Okay, another round of fixes/modifications. Sorry I'm making these changes so fast. I am *really* interested in hearing from anyone who is trying out my revised RcxCC, by the way. :-) Anyway, this version (available from the link above) (...) (24 years ago, 13-Apr-01, to lugnet.robotics.rcx.nqc)
| |
|
long
(score: 1.119)
|
|
| | RE: H8/300 Assembler/C interface
|
| (...) Not to be too obtuse, but your first message says that long and float are never split across r2 and stack. So you're saying that they ARE split? That's fine, because it makes things a lot easier - not that any of my functions actually need to (...) (23 years ago, 20-Apr-01, to lugnet.robotics.rcx)
| |
|
long
(score: 1.119)
|
|
| |
|
long
(score: 1.119)
|
|
| | RE: H8/300 Assembler/C interface
|
| (...) I've just done some more browsing and found this tidbit: (URL) It seems to indicate that tghe registers are always filled and that a long may be split across r2 and the stack. Comments? Cheers, Ralph (23 years ago, 20-Apr-01, to lugnet.robotics.rcx)
| |
|
long
(score: 1.118)
|
|
| | Re: Revisions to RcxCC
|
| (...) Scout support still has a long way to go in many ways, imho. A lot works but I still haven't implemented correct scout support in several of the dialogs. I've tried the command line option for Scout (/RCX=2) and it definitely works on my (...) (23 years ago, 7-May-01, to lugnet.robotics.rcx.nqc)
| |
|
long
(score: 1.117)
|
|
| | Re: RCXCC or Visual NQC 2001?
|
| (...) I'm currently updating/modifying/developing RcxCC and plan on doing so for a very long time to come. If you haven't tried my revised version you should definitely do so. (URL) in the middle of some major revisions that I think will be of (...) (23 years ago, 3-May-01, to lugnet.robotics.rcx.nqc)
| |
|
long
(score: 1.117)
|
|
| | Re: RCXCC or Visual NQC 2001?
|
| I haven't tried Visual NQC, neither have I tried the new version of RCXcc of John Hansen. I'm still using the old Mark Overmars RCXcc and I'm quiet happy with it. The reason for not trying al those new ones is the long term expectations. Neither of (...) (23 years ago, 3-May-01, to lugnet.robotics.rcx.nqc)
| |
|
long
(score: 1.116)
|
|
| | Re: NQC vs Spirit communication speed
|
| (...) Correct - dynamic timing is turned off when predictive is being used (which is the default). Predictive is relatively new, and I wasn't sure which code you started with (or how you ported/used it), so that's why I explained the dynamic timing. (...) (23 years ago, 11-May-01, to lugnet.robotics.rcx.nqc)
| |
|
long
(score: 1.115)
|
|
| | Re: Dead RCX
|
| Completely dead? no response of any kind when you push the ON/OFF button? I ask because if battery power is off for too long, the firmware evaporates and the RCX is pretty non -responsive. But the LCD is not blank. If this is the case, download the (...) (23 years ago, 17-May-01, to lugnet.robotics.rcx)
| |
|
long
(score: 1.115)
|
|
| | Re: lcd display on RCX 1.0
|
| (...) If you load RCX2 firmware in a RCX1 brick (they are fully compatible*), you'll have acces to this function (and all other RCX2 specific possibilities) Philo *Except for some minor differences in IR hardware. (17 years ago, 25-Jun-07, to lugnet.robotics.rcx.nqc)
| |
|
ir
(score: 1.111)
|
|
| | Non Robot uses of the RCX
|
| Hello, Over in k12.ed.science a poster wanted to perform an experiment where he would time how long it took various objects to fall when dropped inside a long tube. He was looking for information regarding timing circuits, how to build one, where to (...) (23 years ago, 19-Aug-01, to lugnet.robotics.rcx)
| |
|
long
(score: 1.104)
|
|
| | Re: Sign of center pin on power adaptor
|
| (...) You must be dealing with a different release of the battery pack than I am, since the only portion of the US instructions that mentions numbers states the output of the battery pack (10VAC, 7VA) and the approximate charge time (4 hours). There (...) (17 years ago, 12-Jul-07, to lugnet.robotics.rcx)
| |
|
range
(score: 1.103)
|
|
| | tweaking around dlcd_show( )
|
| Hi all legOS users, need help about dlcd_* utilities I'd like to display on the lcd a sequence of digits: something like : dlcd_show (LCD_4_BOTL); lcd_refresh(); msleep(250); lcd_clear(); dlcd_show (LCD_4_TOPL); lcd_refresh(); msleep(250); (...) (23 years ago, 25-Aug-01, to lugnet.robotics.rcx.legos)
| |
|
long
(score: 1.102)
|
