Re: [wsjt-devel] WSJTX wont accept 3DA callsign

2019-07-11 Thread Tom Ramberg via wsjt-devel
I actually decoded you yesterday, Vincent. De OH6VDA @ OH2K. Sendt fra min iPhone > 11. jul. 2019 kl. 00:47 skrev Black Michael via wsjt-devel > : > > Just an example...used my own grid. > It's in Illinois > > de Mike W9MDB > > > > > On Wednesday, July 10, 2019, 04:44:54 PM CDT, Topher

Re: [wsjt-devel] WSJTX wont accept 3DA callsign

2019-07-10 Thread Black Michael via wsjt-devel
Just an example...used my own grid.It's in Illinois de Mike W9MDB On Wednesday, July 10, 2019, 04:44:54 PM CDT, Topher Petty wrote: Isn't EM49 in Louisiana or Mississippi somewhere? On Tue, Jul 9, 2019 at 12:04 PM Philip Gladstone wrote: I suspect that the root cause is that he

Re: [wsjt-devel] WSJTX wont accept 3DA callsign

2019-07-10 Thread Topher Petty
Isn't EM49 in Louisiana or Mississippi somewhere? On Tue, Jul 9, 2019 at 12:04 PM Philip Gladstone < pjsg-w...@nospam.gladstonefamily.net> wrote: > I suspect that the root cause is that he can't see any reports on psk > reporter. This is probably for two reasons -- there is no locator in the CQ

Re: [wsjt-devel] WSJTX wont accept 3DA callsign

2019-07-09 Thread Philip Gladstone
I suspect that the root cause is that he can't see any reports on psk reporter. This is probably for two reasons -- there is no locator in the CQ message (and so no psk report) and for other systems which do report this type of message, there is no locator in psk reporter database and so it cannot

Re: [wsjt-devel] WSJTX wont accept 3DA callsign

2019-07-09 Thread Black Michael via wsjt-devel
Oopsso no disconnect...so now we have to find out what problem he's having specifically. C:\WSJT\wsjtxrc7\bin>ft8code "CQ 3DA0VV EM49"    Message                               Decoded                             Err

Re: [wsjt-devel] WSJTX wont accept 3DA callsign

2019-07-09 Thread Joe Taylor
Hi Vincent, On 7/9/2019 3:30 AM, Vincent Molloy 3DA0VV wrote: WSJTX v2 will not accept my 3DA0VV callsign?? The full licence for The "Kindom of Eswatini" (The countries name has changed, make sure you get the country name right) is 3DA0(Zero)##  for unrestricted licence and 3DA1## for

Re: [wsjt-devel] WSJTX wont accept 3DA callsign

2019-07-09 Thread Bill Somerville
On 09/07/2019 08:30, Vincent Molloy wrote: Hi there WSJTX v2 will not accept my 3DA0VV callsign?? The full licence for The "Kindom of Eswatini" (The countries name has changed, make sure you get the country name right) is 3DA0(Zero)##  for unrestricted licence and 3DA1## for restricted

Re: [wsjt-devel] WSJTX wont accept 3DA callsign

2019-07-09 Thread Bill Somerville
On 09/07/2019 16:13, Black Michael via wsjt-devel wrote: There does seem to be a disconnect between the GUI and the coding software. This is with RC7. Inline image But looks good here C:\WSJT\wsjtxrc7\bin>jt9code "CQ 3DA0VV EM49"     Message                Decoded              Err? Type       

Re: [wsjt-devel] WSJTX wont accept 3DA callsign

2019-07-09 Thread Black Michael via wsjt-devel
There does seem to be a disconnect between the GUI and the coding software.This is with RC7. But looks good hereC:\WSJT\wsjtxrc7\bin>jt9code "CQ 3DA0VV EM49"    Message                Decoded              Err? Type         

[wsjt-devel] WSJTX wont accept 3DA callsign

2019-07-09 Thread Vincent Molloy
Hi there WSJTX v2 will not accept my 3DA0VV callsign?? The full licence for The "Kindom of Eswatini" (The countries name has changed, make sure you get the country name right) is 3DA0(Zero)## for unrestricted licence and 3DA1## for restricted license. This is why no on is hearing 3DA on FT8.