- Use fldigi for general logging manual#
- Use fldigi for general logging software#
- Use fldigi for general logging download#
It does decode better (actually much better) than the other versions of JT65-HF, and it handles JT9 in addition. I have given WSJT-X a try and like it! I was not aware that there was the "X" version designed for HF. If you do this you have always a fine ALC and not a wide signal 20 watts for JT65 is QROOOO When i used JT65 or JT9 (meanwhile back to CW only) my max power was 5 w with indoor antennas and i rock the world 20 w is not a problem but if you use "high" power and you have a "modern" Transceiver with power settings by menu please use the 100w option and drop the power down by audio level of the soundcard. After doing this you klick at the "Update" button and all marked entries will be change to JT65.ī.t.w. Now you mark all QSO and go to "Field Update". To change older JT65A enties go to the QSO Manager, then check "Enable updates", in "Search Parameters" you select Mode and let serch for MODE equals JT65A. LotW is using only JT65/JT9 and if you have JT65A ot JT9-1 in the log i would´t be confirmed.
Use fldigi for general logging software#
That software logs correctly (JT65 and JT9 without extensions). It displays previously worked stations, but different band in Yellow, and has notations for new countries and grids, similar in effect to JT alert.Īnyway, I would still like to hear other's thoughts on the different flavors of JT65-HF.įor JT65/JT9 i use WSJT-X from K1JT togehther with JT-AlertX.
The software also keeps a separate log, and displays calls from previously worked station and band in RED. Also, HB9HQX edition somewhat addresses my question #1 above, in that when you double click on a decoded call, the software displays the short path bearing to the station, based on the grid location embedded in the call. It also connects to my rig with OmniRig, and with the HB9HQX version of JT-Alert it auto logs to Log4OM. It seems to decode more signals with less fussing of the incoming audio gain than either the original HF version, but especially the Comfort version. I have spent the last two days with the HB9HQX edition of the JT65-HF software and I really it. What is the general thought (Terry?) on which flavor of JT65-HF to use? The original, the Comfort derivative, or the HB9HQX edition? Is there a way to have JT Alert log the contacts as JT65?
Use fldigi for general logging download#
If I change those qso's mode in Log4OM from JT65A mode to JT65 mode, then download again, no error and the qso's are matched up. When I download verified QSO's from LotW from within Log4OM, I get errors on many JT65 contacts which says the QSO can't be found. When logging a qso in JT, that qso is transfered to JT-Alert, then on to Log4Om seamlessly. When double clicking on a CQ Call on JT, is there any way for that call sign to be passed on to Log4OM, for info lookup including Short Path, Long Path and name prior to completing and logging the contract? I do have a couple of questions regarding the integration of JT65-HF and Log4OM, maybe more seeking advice than a request. African station with 20 watts from Washington State. I have especially been enjoying JT65-HF and JT-Alert.
How often does that happen!? And it does not happen by chance! Lots of work and thought went in to that integration. I was able in short order to get both software packages working well with Log4OM.
Use fldigi for general logging manual#
And secondly, how well that implementation has been documented in the wonderful manual which Terry and others have written. First, how well Log4OM integrates with Fldigi and JT65-HF/JT-Alert. I would like to compliment the Log4OM team on two things.
0 kommentar(er)
