Date   

locked Re: Unique CallSigns RX/TX per Band Issue

HamApps Support (VK3AMA)
 

On 1/02/2018 5:43 AM, Brian Kassel wrote:
For some reason, my Unique CallSigns RX/TX per Band
window is not updating.  There are no filters checked.
It was working previously.
I have checked the Open Hamspots (F7) underVew.
I have also opened Hamspots and logged in separately.

Brian K7RE
Brian,

What version of JTAlert? I suspect it is not current.

Recent Hardware/Software changes on the HamSpots server broke BandActvity data collection for older JTAlert versions.
Upgrade to 2.10.12 and you will be good.

Also, looking on PSKReporter, you appear to be running an old WSJT-X beta, 1.8.0-rc1. There were three release cadidates before the general release. Your running the first of those three. There were many changes and enhancements made to WSJT-X during the release candidate testing period. You really need to upgrade WSJT-X also, IMHO.

de Laurie VK3AMA
   


locked Unique CallSigns RX/TX per Band Issue

Brian Kassel K7RE
 

For some reason, my Unique CallSigns RX/TX per Band
window is not updating.  There are no filters checked.
It was working previously.
I have checked the Open Hamspots (F7) underVew.
I have also opened Hamspots and logged in separately.

--
Sent by my Raspberry PI3
Brian K7RE


locked Abbreviations

Michael Black
 

Would it be possible to abbreviate all "direction" adjectives for countries? i.e. North/Northern, South/Southern/, East/Eastern, West/Western.

N Ireland
N Cook Islands
S Cook Islands
E Malaysia
E Kiribati
etc....

I think it would fit better in the call slots.

de Mike W9MDB


locked Re: No modulation

Brad Rich <brad.rich@...>
 

Never mind.  Found the problem.  The audio was muted in the control panel.

 

Thanks,

 

Brad

 

From: Brad Rich [mailto:brad.rich@...]
Sent: Wednesday, January 31, 2018 9:16 AM
To: 'Support@HamApps.groups.io'
Subject: No modulation

 

My modulation does not operate.  Receives is fine. The test cat and PTT buttons work fine, everything seems fine but no modulation and thus no power.  In the settings window for radio, there is an transmit audio source button.  Mine is greyed out and set to front mic.  I use a Time wave and thought it should be Rear/Data as is the Mode.

 

Thanks for your help.

 

Brad

N6GR


locked No modulation

Brad Rich <brad.rich@...>
 

My modulation does not operate.  Receives is fine. The test cat and PTT buttons work fine, everything seems fine but no modulation and thus no power.  In the settings window for radio, there is an transmit audio source button.  Mine is greyed out and set to front mic.  I use a Time wave and thought it should be Rear/Data as is the Mode.

 

Thanks for your help.

 

Brad

N6GR


locked Re: Callsign History Window Misses Prior QSOs

Hasan Schiers N0AN
 

Mike,

TNX! That's a relief. I really like the feature, and I hope it gets applied to MSK144.

73, N0AN

Hasan

On Wed, Jan 31, 2018 at 8:50 AM, Michael Black via Groups.Io <mdblack98@...> wrote:
JTAlert does not support MSK144.  JT65/JT9/FT8 only.
Not sure what Laurie has planned for the new version...Laurie?

de Mike W9MDB


On Wednesday, January 31, 2018, 8:35:57 AM CST, Hasan Schiers N0AN <hbasri.schiers6@...> wrote:


Further info:

I can go to my WSJT-X DX Call window and type in a call. Doing nothing else will fill in the QSO History window.

If I type in any station I have worked b4, AND I have the mode set to FT8 ....the window fills in properly. I used WB2REM in this example and it shows worked on 4 bands FT8

When I go to 6 meters FT8, it shows I have worked K0TPP: five times on 2 bands (6m and 20m). 

HOWEVER...if I switch to mode MSK144 , the QSO History window shows: K0TPP: MSK144 QSOs - None

Nothing could  be further from the truth...we have worked dozens of times!

Checking other calls that I work nearly every day on 6m MSK144....they all show that every qso is a "First MS144 QSO"

It appears that the Mode MSK144 is not being processed correctly for either Worked B4 or QSO History. Looking at the Main JTA screen, KB7IJ shows as First QSO (in red). ...again, we have worked scores of times.

Hopefully this additional info will  help.

73, N0AN 

Something is wrong. Please help.





Hasan

On Wed, Jan 31, 2018 at 8:17 AM, Hasan Schiers N0AN <hbasri.schiers6@...> wrote:
I can't imagine what setting I have wrong, but stations that show up as B4 in the main window, do not show up in the QSO History window as worked b4....showing band and mode (which is a great feature). This does seem to work in HF with mode FT8, but it does not work on 6 meters with MSK144.

I'm baffled. 

Settings:

No Filters
Last QSO API Enabled under Logging
Log is Standard ADIF Log, path is set to JTalert

Ideas? Suggestions?

Tnx, 73


Hasan




locked Re: Callsign History Window Misses Prior QSOs

Michael Black
 

JTAlert does not support MSK144.  JT65/JT9/FT8 only.
Not sure what Laurie has planned for the new version...Laurie?

de Mike W9MDB


On Wednesday, January 31, 2018, 8:35:57 AM CST, Hasan Schiers N0AN <hbasri.schiers6@...> wrote:


Further info:

I can go to my WSJT-X DX Call window and type in a call. Doing nothing else will fill in the QSO History window.

If I type in any station I have worked b4, AND I have the mode set to FT8 ....the window fills in properly. I used WB2REM in this example and it shows worked on 4 bands FT8

When I go to 6 meters FT8, it shows I have worked K0TPP: five times on 2 bands (6m and 20m). 

HOWEVER...if I switch to mode MSK144 , the QSO History window shows: K0TPP: MSK144 QSOs - None

Nothing could  be further from the truth...we have worked dozens of times!

Checking other calls that I work nearly every day on 6m MSK144....they all show that every qso is a "First MS144 QSO"

It appears that the Mode MSK144 is not being processed correctly for either Worked B4 or QSO History. Looking at the Main JTA screen, KB7IJ shows as First QSO (in red). ...again, we have worked scores of times.

Hopefully this additional info will  help.

73, N0AN 

Something is wrong. Please help.





Hasan

On Wed, Jan 31, 2018 at 8:17 AM, Hasan Schiers N0AN <hbasri.schiers6@...> wrote:
I can't imagine what setting I have wrong, but stations that show up as B4 in the main window, do not show up in the QSO History window as worked b4....showing band and mode (which is a great feature). This does seem to work in HF with mode FT8, but it does not work on 6 meters with MSK144.

I'm baffled. 

Settings:

No Filters
Last QSO API Enabled under Logging
Log is Standard ADIF Log, path is set to JTalert

Ideas? Suggestions?

Tnx, 73


Hasan



locked Re: Callsign History Window Misses Prior QSOs

Hasan Schiers N0AN
 

Further info:

I can go to my WSJT-X DX Call window and type in a call. Doing nothing else will fill in the QSO History window.

If I type in any station I have worked b4, AND I have the mode set to FT8 ....the window fills in properly. I used WB2REM in this example and it shows worked on 4 bands FT8

When I go to 6 meters FT8, it shows I have worked K0TPP: five times on 2 bands (6m and 20m). 

HOWEVER...if I switch to mode MSK144 , the QSO History window shows: K0TPP: MSK144 QSOs - None

Nothing could  be further from the truth...we have worked dozens of times!

Checking other calls that I work nearly every day on 6m MSK144....they all show that every qso is a "First MS144 QSO"

It appears that the Mode MSK144 is not being processed correctly for either Worked B4 or QSO History. Looking at the Main JTA screen, KB7IJ shows as First QSO (in red). ...again, we have worked scores of times.

Hopefully this additional info will  help.

73, N0AN 

Something is wrong. Please help.





Hasan

On Wed, Jan 31, 2018 at 8:17 AM, Hasan Schiers N0AN <hbasri.schiers6@...> wrote:
I can't imagine what setting I have wrong, but stations that show up as B4 in the main window, do not show up in the QSO History window as worked b4....showing band and mode (which is a great feature). This does seem to work in HF with mode FT8, but it does not work on 6 meters with MSK144.

I'm baffled. 

Settings:

No Filters
Last QSO API Enabled under Logging
Log is Standard ADIF Log, path is set to JTalert

Ideas? Suggestions?

Tnx, 73


Hasan



locked Callsign History Window Misses Prior QSOs

Hasan Schiers N0AN
 

I can't imagine what setting I have wrong, but stations that show up as B4 in the main window, do not show up in the QSO History window as worked b4....showing band and mode (which is a great feature). This does seem to work in HF with mode FT8, but it does not work on 6 meters with MSK144.

I'm baffled. 

Settings:

No Filters
Last QSO API Enabled under Logging
Log is Standard ADIF Log, path is set to JTalert

Ideas? Suggestions?

Tnx, 73


Hasan


locked Re: Setup Issues

neil_zampella
 

Also .. update to the final version of WSJT-X ... https://physics.princeton.edu/pulsar/k1jt/wsjtx.html


locked Re: Decode Delay?

 

Yes, I realize a new PC is needed.  But I also "need" an Elecraft KX2 for when I travel.  Then there is that HexBeam I've been admiring.  So many "needs", so little money :).

73, Greg, KM5GT


locked Re: Decode Delay?

HamApps Support (VK3AMA)
 

On 31/01/2018 10:27 AM, Michael Black via Groups.Io wrote:
Actually WSJT-X does know when decodes are finished.
Question is would the message really help anything?

Mike
Probably not.

Waiting for a "finished decoding" packet will likely cause user frustration with JTAlert appearing to take excessive time to alert on the WSJT-X decodes.

For example, analysing the JTAlert activity relating the 38 decode wave file you recently sent, there was a 4 second delay between receiving the first 35 decodes and a final 3 decodes. JTAlert sitting there doing nothing waiting for the "finished decoding" packet would be unacceptable.

I would rather see JTAlert do decode processing and alerting as soon as possible and live with the callsign-frequency shuffle that can occur when a late batch of decodes is received rather than have these periods of JTAlert inactivity and late decoding.

de Laurie VK3AMA
   


locked Re: Decode Delay?

Michael Black
 

Actually WSJT-X does know when decodes are finished.
Question is would the message really help anything?

Mike


On Tuesday, January 30, 2018, 4:20:08 PM CST, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 31/01/2018 4:23 AM, Michael Black via Groups.Io wrote:
Would having a "Decodes end" message from WSJT-X help things at all?  Waiting for that end message?

A 2nd thought...is it possible to "replace" a decode with a higher valued one instead of delete/insert so sorting or a 2nd pass would not be needed?

Sorting really doesn't put he list in the same order as WSJT-X since 2nd pass can restart the frequencies again.  Isn't the order preserved between the WSJT-X display and the UDP packets?  It should be.

de Mike W9MDB
Mike,

The JTAlert sorting is not meant to match the decodes list order, it is a frequency (DF) sort so that JTAlert Callsigns are displayed left-to-right following the Waterfall display order.

A "decodes end" notification from WSJT-X may help, but I suspect that WSJT-X like JTAlert doesn't know if there will be further decodes coming.

Replacing a low db decode with the higher db decode for the same callsign will break the frequency display order of JTAlert.

de Laurie VK3AMA
   


locked Re: Decode Delay?

HamApps Support (VK3AMA)
 

On 31/01/2018 9:40 AM, Wendell Broome via Groups.Io wrote:
I find that Decode “fast” eliminates reordering and faster JTAlert display than does Decode “deep”. And of course, proper filtering really helps JTAlert display.

Laurie, let me take this opportunity to thank you for your software that has really added to my ham radio experience and pleasure. My 73 year old eyes thank you as well.
Wendell, K8OO
Wendell,

It is my understanding, but I am open to correction, that WSJT-X will do a single decoding pass of the decoded signals when set to "Fast", while when set to "Deep" there is a second pass to try and extract additional decodes and it is this second pass that results in the UDP decodes being received by JTAlert coming in more than one batch, resulting in the callsign shuffling seen in JTAlert.

Thanks for your words or support. It is always good to hear that people find the software useful.

de Laurie VK3AMA
   


locked Re: Decode Delay?

Wendell Broome
 

I find that Decode “fast” eliminates reordering and faster JTAlert display than does Decode “deep”. And of course, proper filtering really helps JTAlert display.

Laurie, let me take this opportunity to thank you for your software that has really added to my ham radio experience and pleasure. My 73 year old eyes thank you as well.
Wendell, K8OO

Sent from my iPad


locked Re: Decode Delay?

HamApps Support (VK3AMA)
 

On 30/01/2018 8:32 AM, HamApps Support (VK3AMA) wrote:
decodes are sorted by frequency, lowest to highest so that the Callsigns follow the left-to-right (lowest to highest DF) display of the WSJT-X waterfall as an aid in locating an alerted callsign in WSJT-X.

In addition to the above statement, frequency order sorting is used by the Decodes History display with decodes for a given T/R period displayed lowest to highest DF top to bottom.

de Laurie VK3AMA
   



locked Re: decodes history problem?

HamApps Support (VK3AMA)
 

On 31/01/2018 9:22 AM, Michael Black via Groups.Io wrote:
Laurie,
Debugging a problem seen with the decodes history window.

It seems that the # of decodes per decode period is limited to 32.

Working with Eric WA1SXK and he was looking for a DX decode that he heard but it did not show up in the decodes history.
It was a high offset (2695) so was one of the last decoded.
He had 38 decodes in that period but only 32 show up in the decode history.


de Mike W9MDB
Mike,

There is a finite limit, but that is 36 decodes (4 lines x 9 calls). Any decodes after #36 are ignored.

I can't find any fault on a first visual scan of the code.
Do you have a wav file for a very high decode count period I can test against? The only file I have contains 27 decodes.

de Laurie VK3AMA
    


locked Re: Decode Delay?

ars.k0vc@...
 

Greg--I had the same problem on an older Windows 7 laptop. Sometimes JT65 would still be decoding when the next cycle began! I also tried elevating priorities with little success.  Then I bit the bullet and bought a new PC with an i7 processor and everything decodes immediately---like within a second or less.  I hate to be the bearer of bad news but you're probably going to have to either live with the issue or upgrade your computer.

73
Rick K0VC


locked decodes history problem?

Michael Black
 

Laurie,
Debugging a problem seen with the decodes history window.

It seems that the # of decodes per decode period is limited to 32.

Working with Eric WA1SXK and he was looking for a DX decode that he heard but it did not show up in the decodes history.
It was a high offset (2695) so was one of the last decoded.
He had 38 decodes in that period but only 32 show up in the decode history.


de Mike W9MDB


locked Re: Decode Delay?

HamApps Support (VK3AMA)
 

On 31/01/2018 4:23 AM, Michael Black via Groups.Io wrote:
Would having a "Decodes end" message from WSJT-X help things at all?  Waiting for that end message?

A 2nd thought...is it possible to "replace" a decode with a higher valued one instead of delete/insert so sorting or a 2nd pass would not be needed?

Sorting really doesn't put he list in the same order as WSJT-X since 2nd pass can restart the frequencies again.  Isn't the order preserved between the WSJT-X display and the UDP packets?  It should be.

de Mike W9MDB
Mike,

The JTAlert sorting is not meant to match the decodes list order, it is a frequency (DF) sort so that JTAlert Callsigns are displayed left-to-right following the Waterfall display order.

A "decodes end" notification from WSJT-X may help, but I suspect that WSJT-X like JTAlert doesn't know if there will be further decodes coming.

Replacing a low db decode with the higher db decode for the same callsign will break the frequency display order of JTAlert.

de Laurie VK3AMA
   

18301 - 18320 of 36990