 | | Re: Brickworld Announcement - Area Attractions and baseball
|
|
(...) Although a robot pitcher and robot hitter would be very very kewl, just a robot pitcher and wireless remote control hitter would be very kewl. Like those old baseball machines at the beach. One would have to anticipate the lag and the speed of (...) (18 years ago, 15-Mar-07, to lugnet.events.brickworld, lugnet.robotics.nxt)
|
| |
| | Re: Brickworld Announcement - Area Attractions and baseball
|
|
(...) Unfortunately the ultrasonic sensor can't even detect the red and blue balls when stationary. (Unless you're REAL close: within an inch or two.) Their surface doesn't reflect much sound (perhaps something to do with the index of refraction), (...) (18 years ago, 15-Mar-07, to lugnet.events.brickworld, lugnet.robotics.nxt)
|
| |
| | re: Baseball
|
|
(...) Yes, that could work. We just need someone to design a "standard" pitching machine that can toss balls a foot or two. Then, we need a "regulation" bat size. We could do the whole base-ball, but I doubt very many people could field a whole (...) (18 years ago, 15-Mar-07, to lugnet.events.brickworld, lugnet.robotics.nxt)
|
| |
| | Re: Brickworld Announcement - Area Attractions and baseball
|
|
(...) Ok, thinking out loud now: Well, what about a home run derby or the like? Maybe a machine that pitches and a machine that hits... We could use those red and blue spheres that come with the nxt... Would ultrasonic sensor work for detecting the (...) (18 years ago, 15-Mar-07, to lugnet.events.brickworld, lugnet.robotics.nxt)
|
| |
| | Re: GCC vs. IAR compiler: Could GCC be tweaked to generate code as tight as IAR?
|
|
(...) OK. This is good info!!! It is hard to guess that this was the way to do it. It also makes some sense for LEGO to use their file manager to do this rather than having a second tool replicate a filemanager on the host and insert it at compile (...) (18 years ago, 15-Mar-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: GCC vs. IAR compiler: Could GCC be tweaked to generate code as tight as IAR?
|
|
(...) Hi Dick Swan, That is a nice flexible way of doing it. I will see if I can figure it out in gcc. Thanks for the idea. (...) Well...I have -=Os on, which are all size reducing features. The actual "problem" can also be this packed stuff that we (...) (18 years ago, 15-Mar-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: NeXT-A-Sketch - My second program/first Dave-built NXT 'bot(ish...)
|
|
(...) Or do what I did. Change the program so you only have to tap the button to clear the screen so you can easily reset it while shaking upside down. (18 years ago, 15-Mar-07, to lugnet.org.ca.rtltoronto, lugnet.robotics.nxt)
|
| |
| | Re: GCC vs. IAR compiler: Could GCC be tweaked to generate code as tight as IAR?
|
|
(...) LEGO is using a slightly older version of IAR Embedded Workbench. Maybe that explains it. Or maybe its a 1.03 vs 1.04 source code difference. (...) I have been told that the following is the standard operating procedure for generating the (...) (18 years ago, 15-Mar-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: GCC vs. IAR compiler: Could GCC be tweaked to generate code as tight as IAR?
|
|
Regarrding overwriting the flash system. I encountered the problem of flash file system overwriting user code as well. It's because it is hard coded in the code the starting address of the file system. There's a constant named "STARTOFUSERFLASH" (...) (18 years ago, 14-Mar-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: GCC vs. IAR compiler: Could GCC be tweaked to generate code as tight as IAR?
|
|
... (...) I have not done that. Well, just a little bit:-). The best one (not surprisingly) is the "-Os" optimization, which does this "Optimize for size. -Os enables all -O2 optimizations that do not typically increase code size." (...) I tried (...) (18 years ago, 14-Mar-07, to lugnet.robotics.nxt.nxthacking)
|
