Let's Make Robots!

LDR Cyclops - holding, scanning, seeking, recalling

Continuation from here.

Video straight from the camera to Youtube (Sorry Oddbot).

scans.gif

 Continued here.

AttachmentSize
ldr_eye_telescope_scanning.bas3.38 KB

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Let me ask you this:

If your robot already knew what room he was in, how close to aligning himself to the room do you think you could get using your system. --No comparing rooms now, just aligning to the direction of the prerecorded fingerprint in one given room.

Dunno. That would require (on higher lever cognition levels) that the system recognised two (or more) points in the room that it also correctly identifies in its stored pattern. Say two bright windows in the room, or two black holes in the universe.

There's gotta be a dumber/faster method than that. Read: lower level cognition.

Awesome post my friend...

I am already gleaning a ton of info from it. First off, I finally know what the 13,10 is at the end of all these sertxd commands are! 

Questions:

How did you, if you did, determine the focal distance for your lens?

Is this a true telescope or is it just the one lens?

What are you using for a spreadsheet program and what are you using to spit-out your graphs, like the one above?

Have you tried to or had any problems with storing multiple bytes to a single eeprom address (write command)?

Does fire have mass?

What is the average flight speed of an unladen swallow?

True in the sense that the tube is telescopic.

Just one lens. I considered two, hoping it would shorten the focal length of the total system. But when I found the toilet roll fitted so darn snug, I decided it was plenty light weight for my servo. Two lenses are also a headache to align and focus well.

Ask that smartypants son of yours! Or Puff.

For those just tuning in: fire indeed has mass, but not as much as the same volume of plain cool air has. At any given pressure of course.

I did not try to store more than one 8-bit byte into a single address. I happened not to need that. Lemme check TFM....

"When word variables are used (with the keyword WORD) the two bytes of the word are saved/retrieved in a little endian manner (ie low byte at address, high byte at address + 1)"

Forget about the politically incorrect word joke (it pre-dates the invention of PC'ness and in fact, the invention of The PC). It explains that storing two bytes in eeprom requires you to store one byte at one address and storing the other byte at the next address.

The write command is apparantly able to do this for you when storing a word value for you. The endian (written with an intentional e) just determines which half-word (or bytes) takes the front seat.

I use (an old version of) MS Excel, I am embarrased to admit. Occupational hazard. I know it so well, because I use it mainly to produce graphs like this one at work. Mostly server performance analysis and reporting.

160 mm give or take a yard.

I burned some hairs of my left hand while also trying to hold a ruler. Later I adjusted the focal length of my telescope (it's two cylinders sliding in/out of each other, I think it's called "telescopic"), while reading the resistance on my multithingey or reading the debug data from my Picaxe. Until it indicated the brightest reading I could get by sliding alone.

Remember; I did not try to get a crisp, 1x1 pixel, picture. There is no such thing. I tried to optimize for most light received.

Mike stole my line!