Driver or setting telemetry type for Range finders

Hi Randy,

Please can you let me know if there is a range finder type that has been created for Echotext.txt under the echologger brand out put of

Dual_200kHz_id_128_txt12.log

INFO:447000,10000,0.3,50,0.0,12,10,0.20,0,400,40,0,1507.0
#DeviceID 128 D24 Type RS232
#TimeWork 507.270
#Ping 3808
#Altitude 0.0000
#Temperature 24.04
#NSamples 1360
#Resolution,mm 7.535
#Sampling_Frequency,Hz 100000
#SoundSpeed,mps 1507.00
#---------------Parameters---------------
#Tx_Frequency,Hz 450000
#Range,m 10.0
#Interval,sec 0.250
#Threshold,% 40
#Offset,m 0.000
#Deadzone,m 0.400
#PulseLength,uks 50
#TxPower,dB 0.000
#TVG_Gain 12.000
#TVG_Slope 1.000
#TVG_Mode 1
#OutputMode 4
#Pitch,deg -0.400
#Roll,deg -1.600

##DataStart
4074
4074
4075
4065
4070
4073
4078
4081
4080
4077
4076
4077
4062
3228
3036
4070
4081
4072
4072
4071
4077
4078
4080
4080
4078
4077
4076
4077
4078
4078
4078
3908
3390
2979
2576
2070
1506
1058
950
1266
1559
1522
1284
1040
941
1411
2166
2707
2917
2726
2226
1487
797
563
721
914
988
945
819
722
654
537
368
261
329
436
434
326
214
262

@Judd_McCann,

We don’t have a driver that accepts this text format but TBH, this doesn’t look like a good format for system-to-system communication because it is very verbose and it lacks a crc for error checking. This format looks like it was designed for human consumption.

Which echologger product are you looking at? I think they mostly all support the NMEA format but maybe you are looking for a way for AP to consume multiple depths returned in a single ping? or maybe this is a scanning lidar?