 | | Re: NXT Newbie "Is it possible" question —Brian Davis
| | | | (...) Well, just for diversity here's a slightly different approach. Make the first block a "Reset Timer" block, then split the program into four sequences. Each is simply a "Wait for Touch Sensor", followed by "Read Timer" block with the result (...) (14 years ago, 24-Aug-10, to lugnet.robotics.nxt)
| | | | | | | | | | Re: NXT Newbie "Is it possible" question —Kevin L. Clague
| | | | | (...) I like it! As they say "There's more than one way to skin a cat". I work on computer servers that have 128 CPUs per chip and 512 CPUs per pizza sized box, and I knew that there is no true parallelism here with the NXT :) I like your design, (...) (14 years ago, 26-Aug-10, to lugnet.robotics, lugnet.technic)
| | | | | | | | | | | | Re: NXT Newbie "Is it possible" question —Chris Eyerly
| | | | | (...) Well, I've built a 2 sensor version of Brian's idea using parallel sequence bars (I tried your idea Kevin, got stuck, then Brian chimed in). I just did some testing by building a rig to press the 2 sensors "simultaneously." I was able to get (...) (14 years ago, 26-Aug-10, to lugnet.robotics, lugnet.technic)
| | | | | | | | | | | | Re: NXT Newbie "Is it possible" question —Brian Davis
| | | | | (...) *NOW* you're thinking like a Mindstorms person ;). Seriously, I'm glad it's working. The 1 ms difference could be due to a lot of things... but if it's not that critical, then it's not a problem. (14 years ago, 27-Aug-10, to lugnet.robotics, lugnet.technic)
| | | | | | |
