I assume this in reference to a 2d sonar 60* beam. In that case, your 20fow would be covered by a cone, that at it's widest bottom coverage would be 20ft in diameter. Or in other words, 10' away from the center point of the circle on the bottom, in every direction; with the center point being a line directly underneath the transducer, going all the way to the bottom.
Figuring "where" within the sonar's cone shaped beam your objects are ... difficult to do, since your unit is rendering a 2d image, on a flat screen, of 3d objects within the confines of the cone. The cone shape of the sonar beam, plus the fact that the sonar ping only tells you how far away the signal reflecting object is from your transducer, means basically that it has to be "somewhere" within the cone's influence or it wouldn't show up ... and doesn't really specify where it's entering the cone's influence. It could just as easily be something right in front of you, that the cone is encountering, as it could be something coming into the cone from any other angle.
A 60deg cone angle shows, roughly, a circle of approximately 1ft wide for every 1ft of depth. So, in 20fow that'd be a 20ft wide circle on the bottom ... at 10ft deep it would be a 10ft wide circle ... at 1ft below the transducer, the circle would be 1ft wide. And you have to understand that these measurements are of a cone shape (slanted outward as you go deeper). Anything entering the cone, that reflects some of the sonar ping, will show on your screen as a return signal, rendered as a pixel or multiple pixels (depending on the number/size of pixels your unit is capable of showing). Since your screen image is flat (2d), it can only show you "when" the object enters the cone & how far away the object is from the transducer. It cannot interpret where the object is, in relation to direction of entry.
Down Image can't tell you, either. Side Image & the 360deg scanning technology units can show you the direction the objects are in relation to your unit's transducer.
This is just how I understand it, and I could be mistaken in some points.
... cp![]()


Likes:
Thanks:
HaHa: 
Reply With Quote


















