// The following are various 7k messaging scenarios that may be anticipated based on information provided // by Patrik Moberg. Notation is (set/get, reply) and [ ] means optional. For example, scenario d) // we have: volatile settings ([7500], 7001). This means message 7500 may be used to solicit the volatile // settings via message 7001 or 7001 may be an unsolicited message. // // a) Setup: // // Query Config -> (7500, 7001) // Set sonar settings -> (7503, 7501 | 7502) // Setup trigger scheme -> (73xx, TBD) // Query specific settings -> TBD // Stop pinging -> TBD // // b) Normal survey runtime: // // Set various parameters -> (7500, 7501 | 7502) // Start pinging -> TBD // Change trigger sequencing -> (73xx, TBD) // Query vaious parameters -> (7500, 7001) // Monitor alarms status -> ([7500], 7051) // Stop pining -> TBD // Shutdown -> (7500, 7051) // // c) General data collection: // // Raw -> (, 7008) // Beamform data -> (, 7008) // Bottom detected bathy -> (, 7006) // Snippets -> (, 7008) // SSS Imagery -> (, 7007) // // d) Misc: // // Volatile settings -> ([7500], 7001) // Config -> ([7500], 7001) // Matched filter -> (7500, 7002) + others TBD. // Beam geometry -> ([7500], 7004) // // Note: there exists other messages to (e.g., 7000 to 7011) that may result. Above is not necessarily // a complete list. //