range discrepancies between visual and sonar in TMO

BGrey · 04-08-11, 11:49 PM

Even then it still doesnt make sense and only increases the difference between the two readings. Using the scope to get a rough range makes me feel that the visual report is correct but I still cant make sense of the number im getting from the sonar.

Edit: to be clear this is the number reported when using the report range button. When done manually and counting time and calculating i get roughly the correct values which makes me think that maybe an oversight was made and they are reporting the range in yards that the ping traveled and not dividing by 2 as they should for the range to target.

Edit 2 : Got a bit closer and I tried again and this time got a range of 9900 yards ( 29700 ft) on sonar and 31000 ft from visually so all I can guess is that this problem is somehow related to taking measurements from sonar when far from the target

04-08-11, 11:49 PM	#3
BGrey Watch Join Date: Dec 2009 Posts: 27 Downloads: 45 Uploads: 0	Even then it still doesnt make sense and only increases the difference between the two readings. Using the scope to get a rough range makes me feel that the visual report is correct but I still cant make sense of the number im getting from the sonar. Edit: to be clear this is the number reported when using the report range button. When done manually and counting time and calculating i get roughly the correct values which makes me think that maybe an oversight was made and they are reporting the range in yards that the ping traveled and not dividing by 2 as they should for the range to target. Edit 2 : Got a bit closer and I tried again and this time got a range of 9900 yards ( 29700 ft) on sonar and 31000 ft from visually so all I can guess is that this problem is somehow related to taking measurements from sonar when far from the target Last edited by BGrey; 04-09-11 at 12:09 AM.