|
|
 | | line follower?
|
| Bryan: made any progress on that line follower? (19 years ago, 12-Oct-05, to lugnet.org.us.laflrc)
| | | | | Re: Identify a zig
|
| (...) consider it a favour returned from my DCC post. as to your problem... blow off your straigh line of 7 sensors, and instead, angle them to make a V then look for center point of V and most others on one side to "fire" Chris (19 years ago, 11-Oct-05, to lugnet.org.us.laflrc)
| | | | | Re: Identify a zig
|
| (...) As usual, Chris, you are no help. :) Thanks Steve (19 years ago, 11-Oct-05, to lugnet.org.us.laflrc)
| | | | | Re: Identify a zig
|
| (...) ummm steve... a zig zag looks like this. /\/\/\/\/\/\/\ hope that helps. Chris (19 years ago, 11-Oct-05, to lugnet.org.us.laflrc)
| | | | | Re: Identify a zig
|
| (...) With my current program, I really can't treat it like a broken line, because it's NOT a broken line. :) As long as the line is under the row of seven light sensors, the robot knows how it needs to adjust. When it passes an intersection, the (...) (19 years ago, 11-Oct-05, to lugnet.org.us.laflrc)
| | | | | Re: Identify a zig
|
| (...) Could you treat it as a broken line? That is, only 'see' the part of the line that is on a straight path through the zigzag. I assume you have to program the robot to ignore the cross line of the loop in the course pictured: (URL) the (...) (19 years ago, 11-Oct-05, to lugnet.org.us.laflrc)
| | | | | Re: Identify a zig
|
| (...) True, but this is not what I was thinking of. If you could follow the line, and correlate it with the map you have, you could realize that you were approaching the zig-zag, and just go straight..... Kev (19 years ago, 11-Oct-05, to lugnet.org.us.laflrc)
| | | | | Re: Identify a zig
|
| (...) Actually, I think if someone could design a robot that would "appear" to follow a memorized line, that would be encouraged, because it's all about advancing robotics. However, wouldn't that be like going though a line-maze, without looking at (...) (19 years ago, 11-Oct-05, to lugnet.org.us.laflrc)
| | | | | Re: Identify a zig
|
| (...) Probably, but (a) the organizers have said they would use the same course, (b) the "zig zag" portion is a very specific barrier. While memorizing the course ahead of time might not be the intent, in the event description they encourage folks (...) (19 years ago, 11-Oct-05, to lugnet.org.us.laflrc)
| | | | | Re: Identify a zig
|
| (...) Is it considered cheating if the robot has the course memorized before the first run? Kev (19 years ago, 11-Oct-05, to lugnet.org.us.laflrc)
| | | | | Re: Identify a zig
|
| (...) Steve, Well you know how bad I am at programming and all, but my first thought on this was something like this... light sensor (LS)1 goes black then LS! & LS@ go black then LS1, LS2, and LS3 go black (depending on thickness and orientation of (...) (19 years ago, 11-Oct-05, to lugnet.org.us.laflrc)
| | | | | Identify a zig
|
| So, I was looking at the Chibots Advanced Line Following course. BTW, they are using the same course as last time. If you want to see it, you can go to their web site ((URL) go to events, and watch at the May '05 video. The pictures posted are from (...) (19 years ago, 11-Oct-05, to lugnet.org.us.laflrc)
| | | | | GBC @ GTX
|
| I just posted a new picture of the GBC layout for the GTX show this weekend. (URL) you click on the image, it will show the whole layout. Everyone should be able to identify their modules. Steve (19 years ago, 10-Oct-05, to lugnet.org.us.laflrc)
| | | | | Re: #define-ing stuff for Chibots
|
| (...) Or a different way #define BLACKLINE 1 #if BLACKLINE #define SEELINE(reading,threshold) reading < threshold #else #define SEELINE(reading,threshold) reading > threshold #endif if (SEELINE(s1,threshold1)) { // s1 is on the line } else { // s1 (...) (19 years ago, 8-Oct-05, to lugnet.org.us.laflrc)
| | | | | GBC at Indy
|
| We're getting together tomorrow (Sunday) to set-up and test the GBC we're going to have at the IndyLUG layout for GTX. I just spoke with Greg. He's working on a ball-counting & display module. I have a corner module that works as a timer/regulator, (...) (19 years ago, 8-Oct-05, to lugnet.org.us.laflrc)
| | | | | Re: #define-ing stuff for Chibots
|
| (...) I have, and it helps a lot. For instance, when comparing the raw light sensor values to some limit, I #define "<" to be "LIGHTER_THAN", for instance. That makes switching all those points very easy in the code, I need only change two #defines (...) (19 years ago, 3-Oct-05, to lugnet.org.us.laflrc)
| | | | | #define-ing stuff for Chibots
|
| (...) I'm not totally sure about this, but try playing around with #define In one language I use, the compiler will totally take out the variable, and put in the defined value, before compiling the program. I assume that's how it should work in C (...) (19 years ago, 3-Oct-05, to lugnet.org.us.laflrc)
| | | | | LafLRC @ GTX
|
| For those working on the train show GBC, here are the showtimes: Friday: 2:30-7:30pm Saturday: 7:30-10am (setup) 10am-4pm Sunday 10am-4pm 4pm-?(tear down) I think we'll be OK getting there Saturday morning, around 8 to set-up. Kerby will be there (...) (19 years ago, 3-Oct-05, to lugnet.org.us.laflrc)
| | | | | Re: Tic-Tac-Toe-bot
|
| 3T - good name... 32x32 plate for the game sounds exceptional...you could break it into 10x10 squares with a 1 stud width divider...no edge markers (would add a little to the challenge maybe) Size of the cube: Using odd size cubes (3x3, 5x5, 7x7) is (...) (19 years ago, 30-Sep-05, to lugnet.org.us.laflrc, FTX)
| | | | | Re: Schedule of events
|
| (...) See, that's why you are so much more efficient than me at this stuff. I usually have *everything* at the planning stage... (...) Something GBCish (probably not new, but we'll see) Trellis (old line-follower; maze, basic & advanced(?) line (...) (19 years ago, 29-Sep-05, to lugnet.org.us.laflrc)
|
|
