Date   

Re: SOTA activation Logging

Gary/W7EE
 

Thank you Dave!


Re: SOTA activation Logging

Dave AA6YQ
 

+ AA6YQ comments below
I worked my first SOTA activation today.  I loaded my log into the SOTA site and then downloaded it to a CVS file.  I am trying to convert it to Tab-Delimited file.   Any thoughts on what type of program will do this?  Am I doing it wrong by uploading to SOTA first? 

+ DXKeeper can generate a SOTA submission directly; see

<https://www.dxlabsuite.com/dxkeeper/Help/Progress.htm#SOTA>

       73,

            Dave, AA6YQ


SOTA activation Logging

Gary/W7EE
 

Hi 
I worked my first SOTA activation today.  I loaded my log into the SOTA site and then downloaded it to a CVS file.  I am trying to convert it to Tab-Delimited file.   Any thoughts on what type of program will do this?  Am I doing it wrong by uploading to SOTA first? 

How do you activators handle this?

Thanks
Gary/W7EE


Re: DX Keeper tx band not showing regular bands

Dave AA6YQ
 

+ AA6YQ comments below

No joy.

+ Please do the following:

1. on the Launcher's Configuration window, check the "Log debugging info" box

2. direct the Launcher to upgrade DXView

3. on the Launcher's Configuration window, uncheck the "Log debugging info" box

4. attach the errorlog.txt file to an email message, and send the message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ


Re: DX Keeper tx band not showing regular bands

Grover Cleveland <k7tp@...>
 

No joy.


Re: DX Keeper tx band not showing regular bands

Dave AA6YQ
 

+ AA6YQ comments below
One slight remaining issue is not of major concern; DXView is currently at 2.6.8 but launcher won't update to 4.75  (just a slight flash of a window).

+ DXView 2.6.8 is ancient.

+ As a first step, reboot Windows, and then direct the Launcher to update DXView. Any joy?

     73,

          Dave, AA6YQ


Re: DX Keeper tx band not showing regular bands

Grover Cleveland <k7tp@...>
 

Dave,

I did in fact do a complete re-install of all the applications, before I saw your message, and it did solve all the problems with DXKeeper.

One slight remaining issue is not of major concern; DXView is currently at 2.6.8 but launcher won't update to 4.75  (just a slight flash of a window).

Other than that, all is hunky-dory and thanks for your help.

Grover K7TP


Re: MSK144 logging and time keeping

Dave AA6YQ
 

Thanks to all for the comments on this topic.

I'm not planning to make changes to DXKeeper unless LoTW changes its policy, which as I've already posted would be very unlikely. The constructive online venue in which to continue the discussion is here:

<https://groups.arrl.org/g/ARRL-LoTW/messages>

73,

Dave, AA6YQ


Re: DX Keeper tx band not showing regular bands

Dave AA6YQ
 

+ AA6YQ comments below


On Thu, Aug 20, 2020 at 06:47 AM, Grover Cleveland wrote:

I think it will be easier if I remove the software and reinstall, saving my log and setting files of course

+ That's unlikely to correct whatever caused your Windows Registry to be corrupted, and whatever is preventing DXKeeper from generating an errorlog.txt file. Did you check the Windows event logs?

        73,

                Dave, AA6YQ


Re: IOTA Update Issue

Dave AA6YQ
 

+ AA6YQ comments below
I recently uploaded my IOTA QSOs from DxKeeper to the IOTA website, that went fine and all QSOs were approved for credit. 
Today I  downloaded the .csv file with the approved QSOs from the IOTA website and attempted to update DxKeeper to recognize the approved QSOs. Upon attempting the update in DxKeeper I received the following:
 
"The selected IOTA status file does not begin with a header row"
 
If, by a header file, it is referring to the row that contains the column headings I am confused because the file does, in fact, contain those headings.
 
Any ideas?

+ Resolution: After downloading the status file from IOTA, Paul opened the file, widened a column, and then saved the result before directing DXKeeper to process the file. This edit should have been innocuous, but stripped all the double-quotes from the file, preventing DXKeeper from being able to process it.

+ I mistakenly thought that the IOTA team had changed the file format; thanks to Johan PA3EXX of IOTA for patiently identifying the root cause.

        73,

              Dave, AA6YQ
        

 

 


Re: WinWarbler Setup

Dave AA6YQ
 

+ AA6YQ comments below

Dave, I played some more, and see extFSK64 and MMTTY Engine is supported, and config settings, but I cannot get it to FSK key.

I see the shift activity in the Engine screen, but it is not fsk keying radio.


I am trying to find the MMTTY Engine comport config with RTS DTR options , which shows in the native MMTTY version ?

I don't think it is tickling the rts as needed for extFSK keying. I have TX and just a mark key line.

MMTTY on the other hand works great using extFSK64 method, so not sure what I am missing?

+ WinWarbler uses MMTTY as an "engine" for RTTY reception and transmission. If you start the instance of MMTTY in your WinWarbler folder, is it able to transmit RTTY? Make sure EXTFSK64 is correctly configured.

73,

Dave, AA6YQ


Re: DX Keeper tx band not showing regular bands

Grover Cleveland <k7tp@...>
 

I think it will be easier if I remove the software and reinstall, saving my log and setting files of course. I'll report back.
73
K7TP


Re: WinWarbler Setup

Adrian Fewster <vk4tux@...>
 

Thanks very much Joe and Dave.
I had enabled the MMTTY Engine with which the extfsk64 gui had no port setup etc,, , just assumed it was needed...
Once I disabled that, the rest of my setup was already good, and it played nice ;

https://youtu.be/E0lfzoHplW0

Adrian Fewster

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Joe Subich, W4TV
Sent: Thursday, 20 August 2020 11:06 PM
To: DXLab@groups.io
Subject: Re: [DXLab] WinWarbler Setup


I am trying to find the MMTTY Engine comport config with RTS DTR
options , which shows in the native MMTTY version ?
When using EXTFSK/EXTFSK64 in WinWarbler (as would be required when using the USB interface of modern rigs) you must set FSK Control in the WinWarbler Config -> RTTY tab to EXTFSK/EXTFSK64 (at the bottom of the ports pick list) and set the port to be used in the separate EXTFSK/EXTFSK64 window.

73,

... Joe, W4TV


On 2020-08-20 6:19 AM, Adrian Fewster wrote:
Dave, I played some more, and see extFSK64 and MMTTY Engine is
supported, and config settings, but I cannot get it to FSK key.

I see the shift activity in the Engine screen, but it is not fsk
keying radio.

I am trying to find the MMTTY Engine comport config with RTS DTR
options , which shows in the native MMTTY version ?

I don't think it is tickling the rts as needed for extFSK keying. I
have TX and just a mark key line.

MMTTY on the other hand works great using extFSK64 method, so not sure
what I am missing?


Thankyou


Adrian Fewster


Adrian Fewster

On 20/8/20 7:04 pm, Dave AA6YQ wrote:
+ AA6YQ comments below

Dave the FTDX101MP ( I use) works fine with MMTTY with extFSK64
via RTS, with DTR ptt on the standard CP2105 comport (no soundcard
afsk involved) (enhanced CP2105 comport used for CAT).

Is this possible in Winwarbler ?

+ Yes: configure WinWarbler for FSK operation, as described in the
"Configuring WinWarbler for FSK operation" section of

<https://www.dxlabsuite.com/dxlabwiki/FSKConnection>
<https://www.dxlabsuite.com/dxlabwiki/FSKConnection>

73,

Dave, AA6YQ


Re: WinWarbler Setup

Joe Subich, W4TV
 

I am trying to find the MMTTY Engine comport config with RTS DTR
options , which shows in the native MMTTY version ?
When using EXTFSK/EXTFSK64 in WinWarbler (as would be required when
using the USB interface of modern rigs) you must set FSK Control
in the WinWarbler Config -> RTTY tab to EXTFSK/EXTFSK64 (at the
bottom of the ports pick list) and set the port to be used in the
separate EXTFSK/EXTFSK64 window.

73,

... Joe, W4TV


On 2020-08-20 6:19 AM, Adrian Fewster wrote:
Dave, I played some more, and see extFSK64 and MMTTY Engine is supported, and config settings, but I cannot get it to FSK key.
I see the shift activity in the Engine screen, but it is not fsk keying radio.
I am trying to find the MMTTY Engine comport config with RTS DTR options , which shows in the native MMTTY version ?
I don't think it is tickling the rts as needed for extFSK keying. I have TX and just a mark key line.
MMTTY on the other hand works great using extFSK64 method, so not sure what I am missing?
Thankyou
Adrian Fewster
Adrian Fewster
On 20/8/20 7:04 pm, Dave AA6YQ wrote:
+ AA6YQ comments below

Dave the FTDX101MP ( I use) works fine with MMTTY with extFSK64
via RTS, with DTR ptt on the standard CP2105 comport (no soundcard
afsk involved) (enhanced CP2105 comport used for CAT).

Is this possible in Winwarbler ?

+ Yes: configure WinWarbler for FSK operation, as described in the "Configuring WinWarbler for FSK operation" section of

<https://www.dxlabsuite.com/dxlabwiki/FSKConnection> <https://www.dxlabsuite.com/dxlabwiki/FSKConnection>

      73,

            Dave, AA6YQ


Re: MSK144 logging and time keeping

Joe Subich, W4TV
 

On 2020-08-20 1:42 AM, David A92GE wrote:

At least one logging program (Logger 32) has a check box option to
force the log book to log start time as end time:
That is *completely wrong*. Using "force start time equals QSO end
time" will *cause* this problem!

This option is contrary to the intent of ADIF and violates the LotW
rule which is to always log the start time.

73,

... Joe, W4TV


On 2020-08-20 1:42 AM, David A92GE wrote:
[Edited Message Follows]
As I mentioned in a previous thread this situation is made worse by the fact that WSJT/JTDX both will log the start time of an incompleted QSO when a subsequent QSO is completed. I believe this is a bug but has not been acknowledged. I have had FT8 QSO's which typically take a minute with start and end times of 18 hours difference. Thanks to Dave's SQL script I now check my log for QSO's over 15 mins length before uploading. It saves issues.
As Iain has rightly said the start time of a QSO is indeterminate unless scheduled. The end time is usually much more likely to be closer for both stations.
At least one logging program (Logger 32) has a check box option to force the log book to log start time as end time:
/*Hi*,/
//
/FYI,/
/Logger32 users can find remedy to the problem, checking the following option:
Force QSO start time equals QSO end time/
*Best regards*,
Alec
73 David


Re: MSK144 logging and time keeping

Hasan Schiers N0AN
 

I agree with Joe. In how many cases do two stations start a meteor scatter with 30 minutes different from each other? Almost never. 

This is a solution in search of a problem. Start time logging is just fine. I've been running MS for many years and never have had a LOTW problem with confirmations.

Worst case, and very, very rare, IMO that two stations even running random meteors, have > 30 min starting time differential. It should also be noted that there is considerably ambiguity in ending times for an MS qso, although again, 30 minutes would be pretty odd.

What has already been established works just fine. 

73, N0AN

Hasan


On Wed, Aug 19, 2020 at 6:25 PM Joe Subich, W4TV <lists@...> wrote:

LotW does not recognize "end time".  There is only one time involved in
the QSO entry and by the LotW specification that is the start time.

*ANY ONE OR ANY LOGGING PROGRAM* that uses "end time" is violating the
LotW documentation.  Note: this can be a significant problem with
meteor scatter (MSK144, ISCAT-A, ISCAT-B) and EME QSOs as they are
generally schedules that can last up to an hour with the stations
receiving their reports at widely spaced times.

73,

    ... Joe, W4TV


On 2020-08-19 5:10 PM, Dave AA6YQ wrote:
> + AA6YQ comments below
>
> On Wed, Aug 19, 2020 at 01:14 PM, Sidney Shusterman wrote:
>
>>
>> Thanks for this information. The QSO in question was 42 minutes from start
>> to finish.
>
> + That would explain the lack of a confirmation. I suggest that you contact your QSO partner and ask him or her to resubmit the QSO with the correct start time; that will result in a confirmation.
>
> 73,
>
> Dave, AA6YQ
>
>
>
>




Re: WinWarbler Setup

Adrian Fewster <vk4tux@...>
 

Dave, I played some more, and see extFSK64 and MMTTY Engine is supported, and config settings, but I cannot get it to FSK key.

I see the shift activity in the Engine screen, but it is not fsk keying radio.

I am trying to find the MMTTY Engine comport config with RTS DTR options , which shows in the native MMTTY version ?

I don't think it is tickling the rts as needed for extFSK keying. I have TX and just a mark key line.

MMTTY on the other hand works great using extFSK64 method, so not sure what I am missing?


Thankyou


Adrian Fewster


Adrian Fewster

On 20/8/20 7:04 pm, Dave AA6YQ wrote:
+ AA6YQ comments below
Dave the FTDX101MP ( I use) works fine with MMTTY with extFSK64 via RTS, with DTR ptt on the standard CP2105 comport (no soundcard afsk involved) (enhanced CP2105 comport used for CAT).

Is this possible in Winwarbler ?

+ Yes: configure WinWarbler for FSK operation, as described in the "Configuring WinWarbler for FSK operation" section of

<https://www.dxlabsuite.com/dxlabwiki/FSKConnection>

      73,

            Dave, AA6YQ

 


Re: MSK144 logging and time keeping

g4wjs
 

Hi Dave and David,

when logging a QSO in WSJT-X the date and times of the start and end of the QSO are presented to the user to check and can be modified before committing the QSO details to the log. There can be some ambiguity as to exactly when a QSO starts, particularly when a prior QSO has failed, the user should confirm that a QSO has been abandoned by hitting the ESC key before stating a new QSO.

73
Bill
G4WJS.

On 20/08/2020 07:22, Dave AA6YQ wrote:

Bill G4WJS, what's your reaction to the MSK144 time logging situation being discussed in this thread?

       73,

              Dave, AA6YQ

As I mentioned in a previous thread this situation is made worse by the fact that WSJT/JTDX both will log the start time of an incompleted QSO when a subsequent QSO is completed. I believe this is a bug but has not been acknowledged. I have had FT8 QSO's which typically take a minute with start and end times of 18 hours difference. Thanks to Dave's SQL script I now check my log for QSO's over 15 mins length before uploading. It saves issues.

As Iain has rightly said the start time of a QSO is indeterminate unless scheduled. The end time is usually much more likely to be closer for both stations.

          73 David A92GE



--
73

Bill

G4WJS.


Re: WinWarbler Setup

Dave AA6YQ
 

+ AA6YQ comments below
Dave the FTDX101MP ( I use) works fine with MMTTY with extFSK64 via RTS, with DTR ptt on the standard CP2105 comport (no soundcard afsk involved) (enhanced CP2105 comport used for CAT).

Is this possible in Winwarbler ?

+ Yes: configure WinWarbler for FSK operation, as described in the "Configuring WinWarbler for FSK operation" section of

<https://www.dxlabsuite.com/dxlabwiki/FSKConnection>

      73,

            Dave, AA6YQ

 


Re: WinWarbler Setup

Adrian Fewster <vk4tux@...>
 

Dave the FTDX101MP ( I use) works fine with MMTTY with extFSK64 via RTS, with DTR ptt on the standard CP2105 comport (no soundcard afsk involved) (enhanced CP2105 comport used for CAT).

Is this possible in Winwarbler ?


Adrian Fewster

On 20/8/20 9:51 am, Dave AA6YQ wrote:
+ AA6YQ comments below

I am trying to set up WinWarbler on a Yaesu FTDX101MP. MMTY is working well as a stand alone and I am making RTTY contacts. Commander is working fine with both TX and RX Mode and freq all interacting with the transceiver. In WinWarbler RTTY config I get to MMTY SETUP button works.

When I transmit RTTY in WinWarbler with macros or typed in text I transmit a solid carrier wave and the text goes into the top screen in white but is obviously not transmitting.

+ That's the classic symptom of configuring WinWarbler for RTTY FSK operation, but not providing an FSK signal to the transceiver's backpanel input - in the case of the FTDX-101, the SHIFT signal on pin 4 of the backpanel RTTY/DATA jack, as shown on page 62 of your FTDX-101 Operation Manual. As described in

<https://www.dxlabsuite.com/dxlabwiki/AFSKFSK>

+ this requires an external circuit to generate the FSK signal from a serial port modem control signal:

<https://www.dxlabsuite.com/dxlabwiki/FSKConnection>

+ You say you are making RTTY QSOs with MMTTY, so you evidently have MMTTY configured for AFSK transmission. You can configure WinWarbler to transmit RTTY via AFSK as well: see the RTTY portion of the "General Setup Instructions" in

<https://www.dxlabsuite.com/dxlabwiki/Multimode_Setup>

73,

Dave, AA6YQ

14461 - 14480 of 210317