|
locked
Re: Spotting Blocked
Laurie, VK3AMA
Gary,
toggle quoted messageShow quoted text
I have removed the block for you. The link provided in the warning message didn't work because it was a non SSL link that I had neglected to correct within the code. All access on HamSpots is via secure https and old non-secure http links don't work and will land the user on a warning page. I have now corrected the message for the next JTAlert release. (it was tucked away in the English language definition file) Sorry for the inconvenience. de Laurie VK3AMA
On 21/02/2019 10:02 am, GARY JOHNSON
wrote:
I accidentally sent spots with the wrong band on Tuesday and got the message shown below. I corrected the problem and then logged out and back into Hamspots.net but continue to get the message. I How can I remove the block. I am also unable to go the URL in the message (www.hamspots.net/blocked/). Spotting Blocked at HamSpots.net Reason : 60m spots posted as 12m Please correct the cause of your blocked spots and then Login to HamSpots.net to remove the block (www.hamspots.net/blocked/) Thank you, Gary WYØV
|
|
|
|
locked
Re: Spotting Blocked
Dennis Heaton
I forgot how, but I know it was so much of a pain that on my 2nd lock I just turned off reporting to them. I do not have a newer radio to sync bands with the program. Often I will switch bands to see who I can hear before setting the band and working them, and it will get you flagged every time. There is enough duplication on there already.
On Feb 20, 2019 6:02 PM, "GARY JOHNSON" <garywy0v@...> wrote: I accidentally sent spots with the wrong band on Tuesday and got the
|
|
|
|
locked
Spotting Blocked
GARY JOHNSON
I accidentally sent spots with the wrong band on Tuesday and got the
message shown below. I corrected the problem and then logged out and back into Hamspots.net but continue to get the message. I How can I remove the block. I am also unable to go the URL in the message (www.hamspots.net/blocked/). Spotting Blocked at HamSpots.net Reason : 60m spots posted as 12m Please correct the cause of your blocked spots and then Login to HamSpots.net to remove the block (www.hamspots.net/blocked/) Thank you, Gary WYØV
|
|
|
|
locked
Re: can't seem to get blue "confirmed" checks to work.
JTAlert Support (VK3AMA)
On 21/02/2019 5:33 am, Michael Black
via Groups.Io wrote:
Mike, A Scan wont help in this case, it is only used for updating the Wanted Lists. The Confirmed/Worked Band display check marks are set based on a direct read of the users Log (when the DX Call is changed or set), no Scan involved. de Laurie VK3AMA
|
|
|
|
locked
Re: can't seem to get blue "confirmed" checks to work.
JTAlert Support (VK3AMA)
On 21/02/2019 3:37 am, Charles Hein
wrote:
Hi. I'm logging with Log4OM, automatic updates to LOTW and eQSL, none of the stations I've worked ever seem to come back as confirmed in JTAlertX. What am I doing wrong?Charlie, You mention auto-uploads to LoTW and eQSL, so I am assuming one those services needs to confirm a QSO for you to consider it confirmed in JTAlert. Are you periodically updating your Log4OM log with your LoTW and eQSL confirmations? Uploading a QSO doesn't automatically become a confirmation. JTAlert will show the Blue confirmation mark if it finds a QSO in you log that has been confirmed based on the QSL confirmation type you have set in JTAlert (Settings, Logging section).  de Laurie VK3AMA
|
|
|
|
locked
Re: can't seem to get blue "confirmed" checks to work.
Michael Black
Are you doing the Scan Log and Rebuild in JTAlert? de Mike W9MDB
On Wednesday, February 20, 2019, 12:32:32 PM CST, Charles Hein <chein@...> wrote:
Hi. I'm logging with Log4OM, automatic updates to LOTW and eQSL, none of the stations I've worked ever seem to come back as confirmed in JTAlertX. What am I doing wrong? Charlie (N4NVD)
|
|
|
|
locked
can't seem to get blue "confirmed" checks to work.
Charlie Hein
Hi. I'm logging with Log4OM, automatic updates to LOTW and eQSL, none of the stations I've worked ever seem to come back as confirmed in JTAlertX. What am I doing wrong?
Charlie (N4NVD)
|
|
|
|
locked
Re: Logging Issue
Hi Bill,
Isn't that what I said ? -- 73 Ron, W3RJW
|
|
|
|
locked
Re: Logging Issue
g4wjs
On 20/02/2019 13:11, Bill M wrote:
The HRD pop up box comes up on the received 73 as usual, and a second or so later a JTAlert-X box pops up. Bill, configuring direct logging from WSJT-X to HRD is
counter-productive when you are also using JTAlert to relay logged
QSOs to HRD. You should only do the former if you are not using
JTAlert and should do the latter if you are using JTAlert. -- 73 Bill G4WJS.
|
|
|
|
locked
Re: Logging Issue
Bill,
There are two ways to get your QSO's from WSJT-X into HRD logbook .... one is to enable logging to HRD in JTAert and the other is to log directly from WSJT-X to HRD logbook ... You don't want both, which seems to be what you have ..... A) Two things need to happen to log directly from WSJT-X ... 1) In HRD logbook 'Tools', 'Confgure', 'QSO Forwarding' you would check 'Receive QSO notifications ..... (WSJT-X) .... (Port number from WSJT-X 2) below) 2) In wsjt-x 'Settings', 'reporting' Select 'Enable logged contact ADIF broardcast' Use Port 2333 (default) B) The other way is to simply enable 'Logging', HRD/ V5/V6 I prefer using JTAlert-X because it has so many more alerting features ..... Again A or B ... And also the HRD popup saying the 'QSO was logged' will be after you mouse the Log QSO box which comes from WSJT-X If that's not it, then you will need to explain further -- 73 Ron, W3RJW
|
|
|
|
locked
Logging Issue
Bill M
OK now what have I clicked on? About a week ago
nothing worked as usually happens on occasion. So I went back to
basics and got it all working again, albeit with different
settings like RIG None etc. So its all working. I take a look at
HRD Logbook after a day or so of QSO's, and all the entries are
duplicated. Two of each.
The HRD pop up box comes up on the received 73 as usual, and a second or so later a JTAlert-X box pops up. That wasn't there before. I changed a few colors and activated some other stuff. None of which seemed related to logging...so what in the world did I click on this time that's duplicating entries? IC-7000 Navigator WSJT-X latest vs. HRD latest vs. JTAlert-X I5 PC 16 Gig Ram Bill W2CQ
|
|
|
|
locked
Re: Changing default logbook location
John Petrocelli
I have a simple CMD file
that does something similar. But it puts a date-time stamp in the
copied file's name.
toggle quoted messageShow quoted text
If anyone wishes and it is agreed, I will be happy to post a copy in a message. Anyone is welcome to adapt this as they with. BTW, I also have similar CMD files to copy the INI and ALL.TXT files. John R. Petrocelli - WA2HIP ¶¶¶¶¶¶¶¶¶¶ Primary Home Page: http://wa2hip.com On 2/19/2019 9:06 PM, chas cartmel
wrote:
|
|
|
|
locked
Re: Changing default logbook location
chas cartmel
Robert, What you could do is write a batch file to copy the WSJT X log to your dropbox and then schedule a task using task scheduler to run the batch file on a daily basis
73 Charlie www.G4EST.me.uk Twitter:@ccartmel
From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of g4wjs
Sent: 19 February 2019 20:54 To: Support@HamApps.groups.io Subject: Re: [HamApps] Changing default logbook location
On 19/02/2019 19:57, HamApps Support (VK3AMA) wrote:
Hi Laurie and Robert, on Windows making a hard link is probably preferable since doing so does not require elevated rights whereas creating a symlink does. Use the same mklink command with the correct options. A hard link enters the same file into multiple directories and each entry is indistinguishable from the others. Creating such a hard link in a directory under the Dropbox root will allow Dropbox to automatically synchronize the file to the Cloud. For example, from a CMD window type: mkdir "%Home%\Dropbox\WSJT-X" these commands create a new directory under the Dropbox root called WSJT-X and then create a hard link entry in that directory that is the WSJT-X ADIF log file. 73
|
|
|
|
locked
Re: Changing default logbook location
g4wjs
On 19/02/2019 19:57, HamApps Support
(VK3AMA) wrote:
Hi Laurie and Robert, on Windows making a hard link is probably preferable since doing so does not require elevated rights whereas creating a symlink does. Use the same mklink command with the correct options. A hard link enters the same file into multiple directories and each entry is indistinguishable from the others. Creating such a hard link in a directory under the Dropbox root will allow Dropbox to automatically synchronize the file to the Cloud. For example, from a CMD window type: mkdir "%Home%\Dropbox\WSJT-X" these commands create a new directory under the Dropbox root
called WSJT-X and then create a hard link entry in that directory
that is the WSJT-X ADIF log file. 73 -- 73 Bill G4WJS.
|
|
|
|
locked
Re: Changing default logbook location
JTAlert Support (VK3AMA)
On 19/02/2019 9:46 am, Robert wrote:
Can I change the default WSJT-X logbook location? WSJT-X doesn't provide any mechanism to change the location of its log file. I am not aware of any plans by the WSJT-X developers to alter that behaviour. Perhaps one of them might chime in on this message thread. The only way you can change the location is to use a symbolic link (a Google search will help you), where the WSJT-X log-file becomes a symbolic link pointing to the true physical location of the file which can be anywhere you desire. de Laurie VK3AMA
|
|
|
|
locked
Re: Changing default logbook location
VA7GEM <boat.anchor@...>
On Mon, Feb 18, 2019 at 02:46 PM, Robert wrote:
Hello,Robert I use JTAlert also (great prog). It will Rx the contact details from WSJT-X and log the contact in HRD Log. HRD Log then backs up to Dropbox. Dropbox emails me when it is time to clean up the lod files. Love the way it all integrates. cheers Barry
|
|
|
|
locked
Re: Changing default logbook location
DAVID BERNHEISEL
Ooops sorry - wrong response for this group....
toggle quoted messageShow quoted text
On 2/18/2019 17:35, DAVID BERNHEISEL via Groups.Io wrote:
Check DXKeeper>Config>Log tab - backup file location - second entry on the Log Tab
|
|
|
|
locked
Re: Changing default logbook location
DAVID BERNHEISEL
Check DXKeeper>Config>Log tab - backup file location - second entry on the Log Tab
toggle quoted messageShow quoted text
On 2/18/2019 16:46, Robert wrote:
Hello,
|
|
|
|
locked
Changing default logbook location
Robert <Robert@...>
Hello,
Can I change the default WSJT-X logbook location? I use DropBox to backup my HRD LogBook, and it works fine because I can stipulate where I want my backup logbook file to go. I would like to do the same thing with WSJT-X Logbook. Is there a way? -- Thanks, Robert AC2MM
|
|
|
|
locked
Re: LOTW/EQSL Flags - Resolved
Michael Black
And also the popup on the callsign showed LOTW too so it apparently isn't seeing that time limit flag either. That's what confused me...hover over the callsign and it showed LOTW but no flag. Thanks Laurie. Mike
On Sunday, February 17, 2019, 7:17:08 PM CST, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 18/02/2019 8:43 am, HamApps Support
(VK3AMA) via Groups.Io wrote:
On 17/02/2019 3:34 pm, Michael Black via Groups.Io wrote:Mike, The reason the LoTW flag is not being displayed in the JTAlert main display is due to you having a one year time limit filter set for LoTW flagging and the callsign in question, V47KA, last uploaded to LoTW on 2016-05-03, from the Callsign database, outside that one year limit. I note that he has recently uploaded to LoTW and that will be reflected in the next database update. eQSL flags are not shown because you have them turned off. The Decodes History V3 that your running currently doesn't obey the LoTW flag time limit filtering and thus showed the flag. de Laurie VK3AMA
|
|
|
