ping talk
This is a subject where you can get help, share ideas, and talk about the ping sensor.· We have a lot of random stuff about ping sensors, so why dont we put it in one subject?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
To make something work one must build, test, and verify bfore proceding.· -- myself
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
To make something work one must build, test, and verify bfore proceding.· -- myself
Comments
Jax
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
If a robot has a screw then it must be romoved and hacked into..
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
To make something work one must build, test, and verify bfore proceding.· -- myself
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
To make something work one must build, test, and verify bfore proceding.· -- myself
Jax
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
If a robot has a screw then it must be romoved and hacked into..
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
To make something work one must build, test, and verify bfore proceding.· -- myself
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Chris Savage
Parallax Engineering
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
To make something work one must build, test, and verify bfore proceding.· -- myself
Here are my Ping questions
- How far does a ping sensor have to be from a parallel surface, and at what distance? How wide is the cone of sensitivity and at what angle does it open up at?
- Some have said that it helps to have a sound dampening surface behind the ping sensor? Is that true?
- How much motion can a Ping sensor handle while it is working? How fast could a servo with a ping pivot and be expected to work? What about a less smooth motion like a motor vibrating or the gait of a walking robot?
- What about other forms of electrical interference. I know you should put a capacitor across motor lines, but should you take other precautions?
I would love to just spend a few days running tests, and perhaps I will, but in the meantime I would like to see what I can get out of this great knowledge base.
www.youtube.com/watch?v=lI6ACgbyUj8
2) Supposedly, yes.
3) I've had the ping take about two 180 degree sweeps with a servo per second, and 18 points each time.
4) Separate the motor power supply from the electronics.
Jax
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
If a robot has a screw then it must be romoved and hacked into..
http://uk.youtube.com/watch?v=L6SGsV9uHfs
two pitfalls -
- If you try to take readings too close together they get confused by echoes still bouncing around.
- Things you wouldn't think of can produce ultrasonic noise that confuses the sensor, like keys jangling.
/John
I am working on a BS2 project to rejuvenate an old Tomy Omnibot and want to have two Ping))) sensors in operation in the front as bump sensors.· I have been using one for awhile on a standard Boe-Bot chassis and have no issue with that.· When I started playing with hooking two units up near each other (8 inches apart) I am finding it difficult to program to even test if it will work correctly... The difficulty is in my head not the Ping))) sensor! [noparse]:)[/noparse]
I am looking for PBasic assistance in the correct way to read one Ping))) store the value and quickly read the second Ping))) and then I will do some·(as yet undecided) decision making on movement and further action.
1. So I am wondering what is the proper time to pause between Ping#1 read and Ping#2 read?
2. I need 2 variables... right? to store the seperate reads and from that I will then be able to make "turn X direction" decisions.
3. Looking for input and suggestions as a broad topic and did not find any examples while browsing/searching
Thanks!
Jeff·
PS I wish the old Omnibot chassis would work with the servo mounted Ping that scans back and forth... I love that and it works great, but would not look "good" on the old robot chassis.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
"Twenty years from now you will be more disappointed by the things you didn't do than by the ones you did do. So throw off the bowlines. Sail away from the safe harbor. Catch the trade winds in your sails. Explore. Dream. Discover." - Mark Twain
Post Edited (The Hero Flag) : 1/12/2009 6:46:26 AM GMT
2. You need two variables if you don't do any processing between readings of one ping and the other.
The easiest thing to do (as is the case in general programming) is to break things up into functions. So, put the ping stuff in one function, put the decision making stuff in another, and put the calls to both in a main loop. Just a suggestion, but it works well.
On another note I finally got the motorized base of the Omnibot working via the stamp and can chase the cat around the room (with wires dangling) so that is progress!
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Currently working on Omnibot v2 - A "rejuvinated" Tomy Robot
"Twenty years from now you will be more disappointed by the things you didn't do than by the ones you did do. So throw off the bowlines. Sail away from the safe harbor. Catch the trade winds in your sails. Explore. Dream. Discover." - Mark Twain
John Williams March 2005 Nuts&Volts article "nz119.pdf"- Also called PingISeeYou.pdf elswhere
Camp L. Peavy, Jr. "Ultimate TABLEBot" - "Ultimate.pdf" that has 3 Ping units.
Good resources!
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Currently working on "Omnibot v2" - A "rejuvenated" 1980's Tomy Omnibot 2000 Robot
"Twenty years from now you will be more disappointed by the things you didn't do than by the ones you did do. So throw off the bowlines. Sail away from the safe harbor. Catch the trade winds in your sails. Explore. Dream. Discover." - Mark Twain
I setup my sonar subroutines so the the PIN and assigned space in RAM (arrays) are set by the main program, and then any Ping can be triggered, read, adjusted and stored in RAM for use elsewhere, e.g.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
When the going gets weird, the weird turn pro. -- HST
1uffakind.com/robots/povBitMapBuilder.php
1uffakind.com/robots/resistorLadder.php
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Currently working on "Omnibot v2" - A "rejuvenated" 1980's Tomy Omnibot 2000 Robot
"Twenty years from now you will be more disappointed by the things you didn't do than by the ones you did do. So throw off the bowlines. Sail away from the safe harbor. Catch the trade winds in your sails. Explore. Dream. Discover." - Mark Twain