The use case for Type 2 or 3 messages includes pico-ballooning. Because balloons travel and reach new receivers, they send both a Type 1 and a Type 2 or 3 message so the later can be decoded.
The additional packet sends two characters of grid square plus some bits to encode altitude and other data. Maybe there's a better way. 73 Martin W6MRR On Sat, Aug 14, 2021 at 7:40 AM Bill Somerville via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > On 14/08/2021 15:23, Stefan HB9TMC via wsjt-devel wrote: > > On 14.08.21 00:36, Phil Karn via wsjt-devel wrote: > > > > > > Has anyone seen a collision in practice? > > > > There was a hash collision between KB8OIS and VK3KCX (Hash 17637): > > https://wsprnet.org/drupal/node/8466 > > > > And between WX4BK and OZ0RF (Hash 3245): > > https://wsprnet.org/drupal/node/8014 > > > > > > 73 > > Stefan > > Hi Stefan, > > since neither has a non-standard callsign they could avoid that > happening by checking the "Prefer type 1 messages" option, unless they > have some pressing desire to transmit 6-character grid locators. > > 73 > Bill > G4WJS. > > > > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel >
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
