Date   

locked Re: DX Atlas

Dave Garber
 

I was kind of wondering what fhis had to do with hamapps or dxatlas


On Mon., Mar. 15, 2021, 2:38 p.m. Larry Banks via groups.io, <larryb.w1dyj=verizon.net@groups.io> wrote:
I assume you were discussing DXMaps.

73 -- Larry -- W1DYJ

 
From: Craig
Sent: Monday, March 15, 2021 14:07
Subject: Re: [HamApps] DX Atlas
 
Hi Larry - where is that specific  "Select Options" located? Which App?
Thanks,

Craig
NZ4CW


locked Re: DX Atlas

Larry Banks
 

I assume you were discussing DXMaps.

73 -- Larry -- W1DYJ

 

From: Craig
Sent: Monday, March 15, 2021 14:07
Subject: Re: [HamApps] DX Atlas
 
Hi Larry - where is that specific  "Select Options" located? Which App?
Thanks,

Craig
NZ4CW


locked Re: DX Atlas

Craig
 

Hi Larry - where is that specific  "Select Options" located? Which App?
Thanks,

Craig
NZ4CW


locked Re: DX Atlas

Larry Banks
 

Hi Craig, (call?),
 
Do you have Select Options >> Only last 15 minutes selected?

73 -- Larry -- W1DYJ

 
 
 

From: Craig
Sent: Monday, March 15, 2021 13:48
Subject: [HamApps] DX Atlas
 
The DX Atlas map is showing a huge number of QSO paths as backdrop to a current plot that I have selected from DXKeeper.  How can I remove the large number of prior QSO's that are showing on the map?  Selecting Plot on DXKeeper plots the current QSO with all of the others showing.


locked Re: Double Logging Issue

Duncan Campbell
 

I found that if I have the JTAlert sending my spots to spot collector AND having JTAlert doing my logging to DXKeeper, I also got the double logging.  I turned off the spot collector dump and it corrected the problem for me.

73 de duncan, KF6ILA


locked Re: problem decoding with Flex 6400M

JoAnn Donaldson <joannplano2005@...>
 

The 6400M front panel is Maestro. So I turned off SmartSDR, switched DAX Control to Maestro, SmartSDR CAT to Maestro and WSJT started decoding. I have now made 1/2 dozen contacts. i am going to report this problem to Flex Support Team.

JoAnn Donaldson
AB8YZ

On Sunday, March 14, 2021, 6:38:51 PM CDT, Bill Barrett <billbarrett174@...> wrote:


Open a browser and type in "Time.IS" in the url

On Sun, Mar 14, 2021 at 3:30 PM AB8WD-Willie via groups.io <AB8WD=yahoo.com@groups.io> wrote:
check time sync on pc to time is on internet



--
Bill Barrett
352-437-4758


locked Re: problem decoding with Flex 6400M

Bill Barrett
 

Open a browser and type in "Time.IS" in the url


On Sun, Mar 14, 2021 at 3:30 PM AB8WD-Willie via groups.io <AB8WD=yahoo.com@groups.io> wrote:
check time sync on pc to time is on internet



--
Bill Barrett
352-437-4758


locked Re: problem decoding with Flex 6400M

Craig
 

Make sure your DAX setting align in your slice and DAX. C


On Mar 14, 2021, at 2:50 PM, JoAnn Donaldson via groups.io <joannplano2005@...> wrote:

I got WSJT-X to interface with my Flex 6400M. The Cat Test Button turns Green and the PTT Button turns Red and the Radio goes into Transmit. I have Incoming Audio set to RX1 and outgoing audio set to TX. I see signals on the WSJT-X waterfall but nothing gets decoded.


locked Re: problem decoding with Flex 6400M

AB8WD-Willie
 

check time sync on pc to time is on internet


locked problem decoding with Flex 6400M

JoAnn Donaldson <joannplano2005@...>
 

I got WSJT-X to interface with my Flex 6400M. The Cat Test Button turns Green and the PTT Button turns Red and the Radio goes into Transmit. I have Incoming Audio set to RX1 and outgoing audio set to TX. I see signals on the WSJT-X waterfall but nothing gets decoded.


locked Re: Double Logging Issue

Laurie, VK3AMA
 

On 14/03/2021 3:29 pm, Russ Ravella via groups.io wrote:
Since sending the request for help, I’ve had to travel to attend to a family issue.  I brought my Flex Maestro and computer to attempt to work the problem remotely and amazing, it doesn’t seem to be happening here.  I’m running the same s/w on the same computer as before, just remotely.  It would seem that either running it remotely breaks whatever the double log condition is, it is intermittent or whatever changed has changed back.

If the issue returns when I get back, I’ll excuse these instructions and send you the files.  Thanks again for you help !
Russ KR6W
Interesting. Sounds like something on your home network may be repeating the TCP instructions that JTAlert is sending to DXKeeper. If that is the case I would expect the problem to resurface once you return home.

de Laurie VK3AMA


locked Re: Disappearing B4's in FT4

HamApps Support (VK3AMA)
 

On 14/03/2021 3:48 pm, Richard Preece wrote:
I have had a good search and can't seem to find reference to my issue but apologies if it's been covered already. I have never had any issues with B4 until I started using FT4, if I make and log a contact it correctly shows as B4, if I then change band and come back the B4 tag disappears. This only happens with Ft4, no other mode. I'm logging with HRD and have latest versions of JT Alert and WSJTX running. All the solutions that have been suggested to me would affect other modes too such as rebuild log, like I said they are all fine.

Thanks

Rich

What version of HRD?

Broken FT4 behavior suggests either an old HRD version, pre 6.7.0.269, or a HRD Log that has not been updated to be ADIF 3.1 compliant.
If your HRD log is ADIF 3.1 compliant (has been upgraded using  the HRD instructions) than likely you have not told JTAlert that the Log has been made compliant. See the JTAlert Help File, "HRD 6.7.0.269, JTAlert Settings" topic at the root level.

de Laurie VK3AMA


locked Re: Disappearing B4's in FT4

neil_zampella
 
Edited

Rich,

and you have 'ignore band' checked or unchecked ?   What about 'ignore mode' ??   

If ignore band is checked, uncheck it.   This 'should' restore B4 by band.   How about ignore mode?   I'm sure you don't want to do that during normal operations.

If that doesn't work, I'd use the 'CONTACT SUPPORT' link on the HELP menu so Laurie will get the JT-Alert files and see what's going on.

Neil, KN3ILZ


locked Disappearing B4's in FT4

Richard Preece
 

Hi

I have had a good search and can't seem to find reference to my issue but apologies if it's been covered already. I have never had any issues with B4 until I started using FT4, if I make and log a contact it correctly shows as B4, if I then change band and come back the B4 tag disappears. This only happens with Ft4, no other mode. I'm logging with HRD and have latest versions of JT Alert and WSJTX running. All the solutions that have been suggested to me would affect other modes too such as rebuild log, like I said they are all fine.

Thanks

Rich


locked Re: Double Logging Issue

Russ Ravella
 

Hi Laurie,

Thanks for the help - much appreciated !

Since sending the request for help, I’ve had to travel to attend to a family issue.  I brought my Flex Maestro and computer to attempt to work the problem remotely and amazing, it doesn’t seem to be happening here.  I’m running the same s/w on the same computer as before, just remotely.  It would seem that either running it remotely breaks whatever the double log condition is, it is intermittent or whatever changed has changed back.

If the issue returns when I get back, I’ll excuse these instructions and send you the files.  Thanks again for you help !
Russ KR6W


On Mar 12, 2021, at 2:58 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:

On 12/03/2021 3:31 pm, Russ Ravella via groups.io wrote:
The only s/w I have running at this point is: SSDR, DXL. FRStack (which has no logging features), WSJT-X (FT8) and JTAlert.  That's it !  And again, I haven't made any setting changes in any of them.  I'm at a total loss.  Any suggestions would be much appreciated.

Thanks,
Russ KR6W

OK, we need to determine if the duplicate logging instruction is coming from JTAlert. Do the following...
  • Enable JTAlert debug recording, via the settings menu.
  • Log a dummy QSO in WSJT-X so that you get the double logging in DXKeeper.
  • Leave JTAlert running for 3 minutes so that it has time to run the capture of your operating environment.
  • Then use the JTAlert "Help" -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis. Include a note of the Callsign logged that produced the double logging and the UTC Time when you logged the QSO.
  • Disable JTAlert debug recording.

Once I get your support request I will be able to identify if JTAlert is the source of the duplicate logging instruction.

de Laurie VK3AMA





locked "Any Digital Mode" and Wanted Zone

Joe Subich, W4TV
 

Laurie,

I think there is an error in "Any Digital Mode" in Wanted Zones.

It appears that "Any Digital Mode" includes RTTY. However, the
rules for CQ WAZ *exclude* RTTY from "Digital" (there is a separate
award for RTTY).

I noticed DXLab/SpotCollector calling out FT8 spots from my own
JTAlert feed on 30 meters but no alerts from JTAlert. I tracked
it down (apparently) to a RTTY confirmation on that band.

73,

... Joe, W4TV


locked Re: Error updating Jtalert

FastWeb
 


After further testing I think that the error reported as due to JTAlert instead depends on SportCollector not connecting with wsjt-x since I mistakenly try to start SportCollector before Wsjt-x.
Changing the boot order the JTAlert error does not appear but the SpotCollector connection failure remains. Two Messages received: "SpotCollector not connected WSJT-X not connected" "SC_WSJTX has reported an error; the WSJT-X spot source has been disabled"


Ivan


locked Re: settings - filters

Michael Black
 

You need to ask on the JTDX forum...it is responsible for filtering such things out.

Mike W9MDB




On Friday, March 12, 2021, 05:22:54 PM CST, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 13/03/2021 6:24 am, Matthias Bellmann wrote:
i am using jtdx for some month, but some days ago jtdx filters dont work.
In register "filters" i can mark "hide messages from continents" and "hide messages from countries" or "show cq messages only" (same with rrr/rr73/73),
but filtering doesn take place. 
All other functions are ok, communication with logger32 via udp, jtaler/logger32 with tcp, loggin etc.
what is my fault? Using 2.2.0-rc155
73 Matthias dk4wd

I don't use JTDX, except for JTAlert testing, so am unable to provide an informed/accurate response, sorry.

If you don't get an answer here from another member of this group try posting this question on the JTDX support group
 https://jtdx.groups.io/g/main.


de Laurie VK3AMA


locked Re: settings - filters

HamApps Support (VK3AMA)
 

On 13/03/2021 6:24 am, Matthias Bellmann wrote:
i am using jtdx for some month, but some days ago jtdx filters dont work.
In register "filters" i can mark "hide messages from continents" and "hide messages from countries" or "show cq messages only" (same with rrr/rr73/73),
but filtering doesn take place. 
All other functions are ok, communication with logger32 via udp, jtaler/logger32 with tcp, loggin etc.
what is my fault? Using 2.2.0-rc155
73 Matthias dk4wd

I don't use JTDX, except for JTAlert testing, so am unable to provide an informed/accurate response, sorry.

If you don't get an answer here from another member of this group try posting this question on the JTDX support group
 https://jtdx.groups.io/g/main.


de Laurie VK3AMA


locked Re: Double Logging Issue

HamApps Support (VK3AMA)
 

On 12/03/2021 3:31 pm, Russ Ravella via groups.io wrote:
The only s/w I have running at this point is: SSDR, DXL. FRStack (which has no logging features), WSJT-X (FT8) and JTAlert.  That's it !  And again, I haven't made any setting changes in any of them.  I'm at a total loss.  Any suggestions would be much appreciated.

Thanks,
Russ KR6W

OK, we need to determine if the duplicate logging instruction is coming from JTAlert. Do the following...
  • Enable JTAlert debug recording, via the settings menu.
  • Log a dummy QSO in WSJT-X so that you get the double logging in DXKeeper.
  • Leave JTAlert running for 3 minutes so that it has time to run the capture of your operating environment.
  • Then use the JTAlert "Help" -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis. Include a note of the Callsign logged that produced the double logging and the UTC Time when you logged the QSO.
  • Disable JTAlert debug recording.

Once I get your support request I will be able to identify if JTAlert is the source of the duplicate logging instruction.

de Laurie VK3AMA



2801 - 2820 of 36179