This seems to fix both my problem and yours.
Index: packjt.f90
===================================================================---
packjt.f90 (revision 7634)+++ packjt.f90 (working copy)@@ -754,7 +754,7 @@
enddo endif
- 10 if(islash.ne.0 .and.k.eq.0) then+ 10 if(islash.ne.0 .and.k.ne.0) then !
Original JT65 would force this compound callsign to be treated as ! plain
text. In JT65v2, we will encode the prefix or suffix into nc1. ! The task
here is to compute the proper value of k.
(JTSDK-QT 5.8 ) C:\JTSDK\wsjtx\devel\qt55\1.7.1\Debug\install\bin)jt65code "DE
G4WJS/P" Message Decoded Err?
Type--------------------------------------------------------------------------
1. DE G4WJS/P DE G4WJS/P 5: Type 2 sfx
Packed message, 6-bit symbols 63 54 3 5 23 54 23 36 61 55 58 17
Information-carrying channel symbols 56 20 58 50 43 59 20 62 45 17 27 59 42
44 28 31 13 28 1 23 37 27 29 60 14 32 54 53 44 35 55 51 1 48 45 35 3 13 33
18 18 47 41 2 44 9 25 42 44 35 53 21 7 39 60 39 47 49 32 59 12 28 25
(JTSDK-QT 5.8 ) C:\JTSDK\wsjtx\devel\qt55\1.7.1\Debug\install\bin)jt65code "DE
W9MDB/QRP 2W" Message Decoded Err?
Type--------------------------------------------------------------------------
1. DE W9MDB/QRP 2W DE W9MDB/QRP * 6: Free text
Packed message, 6-bit symbols 19 52 8 27 14 4 28 48 15 11 57 10
Information-carrying channel symbols 1 29 18 27 58 18 39 14 6 56 33 34 45
61 40 56 17 18 44 33 8 53 14 23 14 26 40 59 19 26 61 13 45 23 46 8 23 23 30
57 19 47 38 12 14 8 39 32 26 45 58 2 22 37 10 44 55 25 8 26 40 9 15
de Mike W9MDB
From: Bill Somerville <[email protected]>
To: [email protected]
Sent: Tuesday, April 11, 2017 7:43 AM
Subject: Re: [wsjt-devel] Watts in message
On 11/04/2017 13:16, Black Michael wrote:
There have been a few asking what power I was running so wanted to add that to
the last message. Was running 5W intially but now running 2W on my attic
dipole. I've had two -01 reports at 2W from my QTH (Illinois) to NC and VA.
Only 73 contacts so far.
I'll poke around the packing routines to see how to fix this.
Hi Mike, I'm not sure why you are quoting rules to me? You send several
messages during a QSO and have other opportunities to state you are QRP if you
wish. There is no need to add the /QRP suffix to your call for every instance,
in fact by adding when stating you are running 2W you are stating you are both
running 5W or less and running 2W in the same message, that is unnecessary.
Personally I never run more that 3W on HF with JT65 or JT9 but have never seen
the need to sign as /QRP, I simply use a free text sign off like "3W 4EL TU 73"
or "3W DPL TU 73" which says it all as far as I can see. I have had a brief
look at the encoding routines and can see a few issues that need addressing,
with care as they cover a host of formats and also support some historical
variants. I can see the immediate issue you reported but I first need to look
at why the jt65code test program is not dealing with type 1 suffixes correctly
for example "DE G4WJS/P" is not being fully decoded.
73
Bill/QRO (IEEE 802.11 2.4GHz @ 100dBm EIRP)
G4WJS.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!
http://sdm.link/slashdot_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
