NEW UPDATE X WSJT SW

Software

NEW UPDATE X WSJT SW

Messaggioda IW4EHZ » mer gen 19, 2005 10:59 pm

Latest news frm Joe :shock:

The latest update is WSJT Version 4.9.0. Like Version 4.7.0, it is able to run simultaneously with the latest version of Spectran (by I2PHD and IK2CZL), which is included in the WSJT distribution. This combination of programs provides an excellent real-time spectral display in addition to all the features of WSJT.

http://pulsar.princeton.edu/~joe/K1JT/
Avatar utente
IW4EHZ
Site Admin
 
Messaggi: 241
Iscritto il: gio dic 30, 2004 10:40 pm
Località: Vignola (MO) Italy JN54ml

Re: NEW UPDATE X WSJT SW

Messaggioda ik4pmb » mer gen 19, 2005 11:48 pm

Interessante!!! come solito manca solo il sistema di antenne hehehe
Voglio fare altre prove prima sempre con una sola antenna, la prox volta metterò in serie alla ricezione anche una cavità.
Lunedì sera non riuscivo a decodificare molti periodi a causa del rumore, sullo spectran spariva proprio il segnale.
Alla prox
ciao Anto

IW4EHZ ha scritto:Latest news frm Joe :shock:

The latest update is WSJT Version 4.9.0. Like Version 4.7.0, it is able to run simultaneously with the latest version of Spectran (by I2PHD and IK2CZL), which is included in the WSJT distribution. This combination of programs provides an excellent real-time spectral display in addition to all the features of WSJT.

http://pulsar.princeton.edu/~joe/K1JT/
Avatar utente
ik4pmb
 
Messaggi: 757
Iscritto il: lun gen 03, 2005 7:18 am
Località: JN54MM

Some trouble affect 4.9.0 Version :(

Messaggioda IW4EHZ » dom gen 23, 2005 9:48 pm

Some trouble affect the last version of WSJT.
On some operation program hang .

In JT65B show many false decode as valid decode
getting string frm callsign database file :?

For return at previous version is necessary unistall WSJT
frm Control Panel /Install Application then reinstal 4.7.0.
Avatar utente
IW4EHZ
Site Admin
 
Messaggi: 241
Iscritto il: gio dic 30, 2004 10:40 pm
Località: Vignola (MO) Italy JN54ml

Re: Some trouble affect 4.9.0 Version :(

Messaggioda ik4pmb » gio gen 27, 2005 7:58 pm

E' stata rilasciata la versione 4.9.1 dove è stato corretto il bug della 4.9
L'aggiornamento è d'obbligo.
ciao
Anto


IW4EHZ ha scritto:Some trouble affect the last version of WSJT.
On some operation program hang .

In JT65B show many false decode as valid decode
getting string frm callsign database file :?

For return at previous version is necessary unistall WSJT
frm Control Panel /Install Application then reinstal 4.7.0.
Avatar utente
ik4pmb
 
Messaggi: 757
Iscritto il: lun gen 03, 2005 7:18 am
Località: JN54MM

4.9.2 UPDATE

Messaggioda admin » mer feb 02, 2005 12:43 am

One more version

Changes in Version 4.9.2
-----------------------------

1. In CW mode you can now set the desired T/R period by using the text box provided. This feature did not work properly in v4.9.1.

2. Under some conditions using the "Add" button to edit information in the file CALL3.TXT would cause a program crash with the message "Run-time Error #53". Fixed.

3. Using the double-mouse-click on a callsign in the decoded text window will now set the active Tx Message to Tx2. I believe this will be most commonly what is desired, and will be an added convenience for random JT65 operation.

4. The "Sked" box remained visible on the EME Echo screen, covering part of the RIT box. Fixed.

5. Two numbers are now made available if you have checked the"Aggressive decoding" option. These numbers appeared without explanation at the end of each decoded text line produced by version 4.9.1, and you may have wondered what they were. The first number is 0 or 1 according to whether the soft-decision Reed Solomon decoder has failed or succeeded. The second number represents a confidence level on a 0-10 scale for messages decoded using the "deep search" algorithm. Anything under 3 is questionable; messages rated 6 and above are unlikely to be wrong, unless you are processing "garbage" data containing strong birdies, QRN, etc. In that case, you are on your own.

6. A bug was introduced when implementing the "Aggressive decoding" check box. This bug caused a stray "OOO" flag to be sometimes displayed even when no signal was present and synchronization had not been achieved. Fixed.
Avatar utente
admin
Site Admin
 
Messaggi: 33
Iscritto il: gio dic 30, 2004 10:11 pm

New update WSJT 4.9.6

Messaggioda IW4EHZ » lun mar 28, 2005 10:32 pm

update here http://pulsar.princeton.edu/%7Ejoe/K1JT/UPD496.EXE

Changes in Version 4.9.6
------------------------

1. WSJT 4.9.5 fails to decode some files that have relatively high S/N
and good Sync level. This is a bug, and has been fixed. For this
reason alone, you should definitely upgrade to Version 4.9.6.

2. New optional message formats are provided for conveying and
responding to signal reports.

It has been permissible for some time to send, for example,

VK7MO K1JT -24
K1JT VK7MO R-27

(The number after the minus sign must have two digits and must be in
the range -01 to -30.)

I plan to implement a quick way of copying the measured strength
of a decoded transmission into TX message #2, when desired. This
is not yet done in v4.9.6, however. You must edit the TX messages
by hand if you use these formats.

Enhancements in version 4.9.6 now allow you to send messages like
the ones listed below. Both stations will need to be running
v4.9.6 in order for these to work:

VK7MO K1JT RO
VK7MO K1JT RRR
VK7MO K1JT 73

3. Decoding by the deep search algorithm has been extended so as to
include messages of the types discussed in item 2.


Changes in Version 4.9.5
------------------------

1. Full support for long callsigns like ZA/PA2CHR and G4ABC/P is now
provided. When using such a callsign prefix or suffix, do not
include a grid locator in your transmitted message. Note that
4.9.5 and 4.9.2 do not handle prefixes in the same way; they are
not compatible. To get the benefit of the expanded capability,
both stations (TX and RX) must use 4.9.5. The correct message
format is "K1JT V5/ZS5Y" or "V5/ZS5Y K1JT". The extended callsign
must be present in CALL3.TXT or in "To Radio" for the deep-search
decoder to be effective.

2. If you double-click on a callsign in the decoded text window, and if
the word preceding the callsign is "CQ", then TX message #1 will be
selected after the messages are updated. Otherwise, TX message #2
will be selected.

3. So that you will be aware of what is happening, the background
color in the TX message box turns red whenever a message you have
entered is "non-standard" and will be sent as 13 characters of
plain text.

4. Items related to decoding have been removed from the Setup |
Options screen and replaced by a new menu labeled Decoding. Here
you may now select "No shorthands" for FSK441 and several options
for JT65 decoding.

5. In case you are upgrading directly from v4.9.0 or earlier to v4.9.5,
a callsign database file has been included as CALL3A.TXT. If you do
not already have a file CALL3.TXT, you should rename the supplied
file to CALL3.TXT. Otherwise, you will probably want to ignore
the supplied file, since you will have made additions to your own
copy.

6. The frequency of program crashes (for example, after a long period
of monitoring) is much reduced, possibly to zero.

Please, if you encounter a received wave file that reproducibly causes
WSJT to crash, send it to me.
Avatar utente
IW4EHZ
Site Admin
 
Messaggi: 241
Iscritto il: gio dic 30, 2004 10:40 pm
Località: Vignola (MO) Italy JN54ml

WSJT Version 4.9.8.

Messaggioda admin » lun giu 27, 2005 9:36 pm

The latest update is WSJT Version 4.9.8. Like Version 4.7.0, it is able to run simultaneously with the latest version of Spectran (by I2PHD and IK2CZL), which is included with the 4.7.0 distribution. This combination of programs provides an excellent real-time spectral display in addition to all the features of WSJT.


A Supplement for Version 4.9 is now available for the WSJT User's Guide. You can download it from the Documentation page.

1. Bug in JT65 decoder could (rarely) cause a correct decoding by the
Reed-Solomon decoder to be "overruled" by an incorrect decoding
from the Deep Search decoder. Fixed.

2. Bug in JT65 Reed-Solomon decoder could cause program to crash under
certain rare conditions. Fixed.

3. The standard "CQ" message generated for a callsign having an extra
prefix or suffix should not include a grid locator. Fixed.

4. Automatically generated CW messages for stations with callsigns longer
than 4 characters were improperly truncated. Fixed.

5. Bug in JT65 decoder could occasionally cause one or two extra
letters to be appended to a correctly decoded callsign. Fixed.

6. Grid locator entered in "Report" box in FSK441 mode (as used by
some in North American meteor scatter contest) would cause a crash
on program restart. Fixed.
Avatar utente
admin
Site Admin
 
Messaggi: 33
Iscritto il: gio dic 30, 2004 10:11 pm


Torna a Software

Chi c’è in linea

Visitano il forum: Nessuno e 1 ospite

cron