Results 321 – 340 of about 800.
|
Search took 0.01 CPU seconds.
|
|
| |
|  
event
(score: 0.925)
|
|
 | | Mindstorms mall tour
|
| Hi Does anyone know anything about this "event"? It's coming to Newton this weekend and I wanted to know if it was worth the trip. (24 years ago, 12-Oct-00, to lugnet.robotics)
| |
|
event
(score: 0.925)
|
|
| | Re: Scout poweroff time out?
|
| (...) Possible, yes, but I'd prefer not to. The command line is already too complex. I might consider adding the information as part of the regular program download message (with the battery level). For devices other than Scout, there isn't a fixed (...) (24 years ago, 30-Sep-00, to lugnet.robotics.rcx.nqc, lugnet.robotics.scout)
| |
|
event
(score: 0.925)
|
|
| | Re: NQC versus Lego RCX Code Speed
|
| (...) With regards to your comment about sensor watchers, yes they are slow. If I remember correctly, they are implemented by a task that loops forever polling the sensors and starting other tasks whenever an event of the proper type occurs. Tasks (...) (24 years ago, 6-Oct-00, to lugnet.robotics)
| |
|
event
(score: 0.924)
|
|
| | Re: IRPD sensors and LegOS (long)
|
| OK, the IRPD rover just smarter. I had an error in the comments in the previously posted version, references in the initial comments about the Right Side Motor being hooked up to Output B were incorrect, it is actually hooked up to Output C. This (...) (24 years ago, 4-Oct-00, to lugnet.robotics.rcx.legos)
| |
|
event
(score: 0.924)
|
|
| | Re: Mindstorms mall tour
|
| same thing as another poster. I'd hardly call it an event. The one here in chicago had a wall climber, two of the new droid robots, and some p.c.'s set up running lego ads. That was it. The wall climber is neat to see, but hardly worth a trip. hope (...) (24 years ago, 18-Oct-00, to lugnet.robotics)
| |
|
event
(score: 0.924)
|
|
| | Re: Is Scout powerful?
|
| I also think Scout is very good, and it has some new features that not in RCX but will be in new RCX2, like event monitor and so on. NQC 2.2 r1 supports scout in NQC language, so you can write software like for RCX, if you like to use IDE (...) (24 years ago, 19-Oct-00, to lugnet.robotics)
| |
|
event
(score: 0.923)
|
|
| |
|
event
(score: 0.922)
|
|
| |
|
event
(score: 0.922)
|
|
| | Re: RCX2
|
| Bill, If you go to (URL) then follow the 'Tips and Tricks' link, the RCX2 beta SDK is under the 'Master Coders' section. A quick quote from the site: <quote> RCX 2.0 BETA SDK Since we made a few small changes and additions to the firmware after we (...) (24 years ago, 30-Oct-00, to lugnet.robotics)
| |
|
event
(score: 0.921)
|
|
| |
|
event
(score: 0.921)
|
|
| |
|
event
(score: 0.921)
|
|
| | Vision Command capabilities revised
|
| The Vision Command set has been on shelves for two months already. Did it meet general expectations? My opinion is that the Lego company did a pioneering work when introduced a computer cam as a children toy. Maybe it was not so revolutionary step (...) (24 years ago, 7-Nov-00, to lugnet.robotics.vc)
| |
|
event
(score: 0.920)
|
|
| | Re: code
|
| yego, The wait_event function takes an event function as the first parameter, not a sensor number. You need something like (forgive any errors - I don't have LegOS available at work) int rotation_event_3(wakeup_t data) { if (SENSOR_3 == data) return (...) (24 years ago, 26-Mar-01, to lugnet.robotics.rcx.legos)
| |
|
event
(score: 0.920)
|
|
| |
|
event
(score: 0.920)
|
|
| | Re: Event dispatch
|
| (...) Meanwhile I found this out too. (...) I think I never would have found this feature. (...) I like the new features in 2.3a1! (I'll try them tonight). TZS (24 years ago, 18-Dec-00, to lugnet.robotics.rcx.nqc)
| |
|
event
(score: 0.918)
|
|
| |
|
event
(score: 0.918)
|
|
| | Announcing the Seattle Mindstorms and Robotic Techies
|
| After the November 6th "Workshop 3D LEGO RCX Challenge" in Seattle, Gus Jansson and I decided it was time to start a LEGO Robot specific group in this area. Well, it's about a month later, and we're through talking, time for some action! So this is (...) (24 years ago, 12-Dec-00, to lugnet.announce, lugnet.robotics, lugnet.general, lugnet.loc.us.wa, lugnet.loc.us.wa.sea, lugnet.loc.us.wa.tac, lugnet.org.us.sealug, lugnet.robotics.events, lugnet.technic) !
| |
|
event
(score: 0.917)
|
|
| | Re: sleep efficientcy
|
| (...) value (...) There are two issues: 1 do you want to do anything while waiting, 2 how quick do you want to respond to the event. In both cases using an event is better. You can do something else until the event happens (synchronization issuses (...) (24 years ago, 25-Jan-01, to lugnet.robotics.rcx.legos)
| |
|
event
(score: 0.916)
|
|
| | Re: sleep efficientcy
|
| (...) value (...) Ross, I can't speak about efficiency - I dont know enogh about embedded programming, but I've had better results using wait_event. I've tried both msleep() and yield() in a loop, and just calling wait_event with a function that (...) (24 years ago, 25-Jan-01, to lugnet.robotics.rcx.legos)
| |
|
event
(score: 0.914)
|
More: Next Page >>
|
