ping_count and max_range problem

[philippetournevase-spec]

ping mapper give ping_count and max_range are not always in accordance with the range selected for the acquisition with a sonar

for example, humminbird sonar record with a range of (2x) 20 m.
in the B001_ds_highfreq_meta.csv file where there are 297 valid pings (duplicated pings eliminated)
pings 1 to 6 -> ping_count 526 max_range 9,87 <- not good
pings 7 to 295 -> ping_count 1052 max_range 19,74 <- good
pings 296 to 297 -> ping_count 526 max_range 9,87 <- not good
note : the width of the sonograms is 1052 pixels <- good

with other acquisitions, the situation is the same

i can't join files as example - .DAT, .SON and .IDX are not accepted

[CameronBodine]

My guess is that the sonar is set to automatically adjust the range. This is the default (annoyingly). It is designed to adjust the range up and down with changes in the depth to maximize the "zoom" of the image on the sonar screen. I highly recommend turning off this feature when collecting data to ensure the range set during the survey is maintained. I don't think there is any other feature that would cause this change in ping count. PINGMapper reports the count stored in the sonar log and makes no additional changes to this value.

[CameronBodine]

Did this answer your issue? Can I close the issue?