Re: [wsjt-devel] bug in 77-bit message packing

2018-12-23 Thread Bill Somerville
On 24/12/2018 02:34, Bill Somerville wrote: The change is attached as a diff for your review. Hi Igor, that patch has a defect, the attached needs to be applied as well to fix that. 73 Bill G4WJS. commit de9990bb60f3cefcefa5a994ade9fa60d3a1d2a4 Author: Bill Somerville Date: Mon Dec 24 0

Re: [wsjt-devel] bug in 77-bit message packing

2018-12-23 Thread Bill Somerville
On 22/12/2018 18:45, Joe Taylor wrote: i3.n3 Err Message to be encoded Decoded message  1.   *   DU6/VA3AAA K9ABC RRR  VA3AAA K9ABC RRR  2.   *   DU6/PA3AAA K9ABC RRR   

Re: [wsjt-devel] bug in 77-bit message packing

2018-12-22 Thread David M. Boyter
Merry Christmas Joe de AE5SB From: Joe Taylor Sent: Saturday, December 22, 2018 12:45 PM To: Игорь Ч; WSJT software development Subject: Re: [wsjt-devel] bug in 77-bit message packing Hi Igor, On 12/22/2018 05:10, Игорь Ч UA3DJY via wsjt-devel wrote: > He

Re: [wsjt-devel] bug in 77-bit message packing

2018-12-22 Thread Joe Taylor
Hi Igor, On 12/22/2018 05:10, Игорь Ч UA3DJY via wsjt-devel wrote: Hello Joe, . There is a bug in packjt77 module observed when first character of the base call is 'P' in the compound callsign. It can be seen in ft8apset.f90 code, where message with user's callsign DU6/VA3AAA is packed as 'VA3

Re: [wsjt-devel] bug in 77-bit message packing

2018-12-22 Thread Игорь Ч via wsjt-devel
Hello Joe, . This behaviour is triggered by this code in the subroutine pack77_1: . if(index(w(1),'/P').ge.4 .or. index(w(2),'/P').ge.4) i3=2  !Type 2, with "/P" ...   if(index(w(1),'/P').ge.4 .or. index(w(1),'/R').ge.4) ipa=1   if(index(w(2),'/P').ge.4 .or. index(w(2),'/R').ge.4) ipb=1 . Compоund