Date   

Re: DXView SUN window restoration

Dave AA6YQ
 

+ AA6YQ comments below
Dave, most of the windows auto restore when the programs are brought up. I usually have the sun window of DXView up but it does not auto restore and I have not found anything to configure its restoration
+ That's intentional, Larry: neither the Sun nor Translation windows are automatically restored when you direct the Launcher to restore DXView. Each can be restored with one mouse click on the Main window.

        73,

             Dave, AA6YQ


Re: DXLab support for remotely controlling a FlexRadio Signature transceiver via SmartLink

Dave AA6YQ
 

+ AA6YQ comments below
FWIW, I have been able to successfully connect DX Commander to a 6600 using SmartCAT. It controls and reports as expected.  I haven't explored any possibilities beyond that yet but I'm keen to get some current feedback.

+ Commander is designed to control Flex Signature radios via their network API, not via SmartCAT. See

https://www.dxlabsuite.com/dxlabwiki/FlexSignature

+ Among other benefits, this enables the display of active callsign on the SmartSDR panadaptor:

https://www.dxlabsuite.com/dxlabwiki/FlexSignatureDisplayCallsigns

        73,

            Dave, AA6YQ

 

 


Re: DXKeeper Questions

Scott Stembaugh
 

Dave,

I hate to jump into the fray with this, but this happened to me when on 30M FT8 just now.  I double clicked on DP1POL in WSJT-X Band Activity window and JTAlert (2.16.16) directed DXKeeper to do a previous QSO lookup and a pop-up box came up:

"Changed QSO_Begin item with DP1POL at 2018-12-19 00:00:00 on 40M FT8 in FT8

after completing and saving changes, resubmit this QSO to both eQSL.cc and LOTW"


When I restored my log from a previous backup the QSO date/time actually was 2018-12-19 00:00:00, so nothing was changed.  When I search for and find the log record the pop-up displayed again.

I understand I can disable the pop-up.  This is just another data point for you.

73,
--scott




On Fri, Mar 12, 2021 at 1:25 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

I was reconciling DXCC verified credits this week and saw the same behavior. When I filtered the log on a DXCC country prefix, if the selected QSO in the filtered list had 00:00:00 as the begin time, the "Changed item in QSO already uploaded to LoTW" appeared immediately. It also appeared every time I selected that QSO again, i.e. when I pushed the |< or >| buttons to move to the top or bottom of the list. DXKeeper v15.9.9.

+ Thanks, Mike. Until I track down and correct the responsible defect, you can uncheck the "Prompt on change to logged QSO already uploaded to eQSL.cc and/or LoTW" option on the "QSL Configuration window's General tab.

      73,

               Dave, AA6YQ







DXView SUN window restoration

Larry Knain
 

Dave, most of the windows auto restore when the programs are brought up. I usually have the sun window of DXView up but it does not auto restore and I have not found anything to configure its restoration. I may have looked right at it and just didn't recognize it. Possibly when you run out of other things to do (???!) it could be configured to restore unless I am missing some other reason why it is not advisable to restore. Obviously a very low priority if any.

73, Larry W6NWS


Re: DXLab support for remotely controlling a FlexRadio Signature transceiver via SmartLink

Andrew Mitchell
 

Thanks Dave!

FWIW, I have been able to successfully connect DX Commander to a 6600 using SmartCAT. It controls and reports as expected.  I haven't explored any possibilities beyond that yet but I'm keen to get some current feedback.

Tks/73
Andy

VA3CW 


Re: DXLab support for remotely controlling a FlexRadio Signature transceiver via SmartLink

Dave AA6YQ
 

+ AA6YQ comments below
A little late to the party but...

Has anyone successfully created a remote connection between DX Commander and a remote 6xxx?

+ I requested a technical description of SmartLink from Flex more than a year ago. Still waiting.

     73,

            Dave, AA6YQ

 


Re: DXLab support for remotely controlling a FlexRadio Signature transceiver via SmartLink

Andrew Mitchell
 

A little late to the party but...

Has anyone successfully created a remote connection between DX Commander and a remote 6xxx?

Tks/73

Andy

VA3CW


Re: DXKeeper Questions

Dave AA6YQ
 

+ AA6YQ comments below

I was reconciling DXCC verified credits this week and saw the same behavior. When I filtered the log on a DXCC country prefix, if the selected QSO in the filtered list had 00:00:00 as the begin time, the "Changed item in QSO already uploaded to LoTW" appeared immediately. It also appeared every time I selected that QSO again, i.e. when I pushed the |< or >| buttons to move to the top or bottom of the list. DXKeeper v15.9.9.

+ Thanks, Mike. Until I track down and correct the responsible defect, you can uncheck the "Prompt on change to logged QSO already uploaded to eQSL.cc and/or LoTW" option on the "QSL Configuration window's General tab.

73,

Dave, AA6YQ


Re: DXKeeper Questions

Dave AA6YQ
 

+ AA6YQ comments below

The QSO was not uploaded to LoTW when I logged it with WW.

In WW config on the Log tab "Upload to LoTW when logging" was not checked.

To upload the QSO to LoTW I right clicked the QSO in DXK and selected "Add entry to QSL Queue (Lotw)" along with several other QSO's
(not logged at 00:00:00) then in the DXK QSL tab I clicked the "Upload to LotW" radio button. That produced the screen shot I
previously uploaded.

Additionally if I now click on the subject QSO in DXK I get the popup " Changed item in QSO already uploaded to LoTW, changed
QSO_Begin item in QSO with N1STB at 2021-03-11 00:00:00 on 40M in CW, after completing and saving changes, resubmit this QSO to
LoTW" despite having made no changes to the QSO.

+ Thanks, Dale!

73,

Dave, AA6YQ


Re: DXKeeper Questions

N6MZ Michael Mraz
 
Edited

I was reconciling DXCC verified credits this week and saw the same behavior. When I filtered the log on a DXCC country prefix, if the selected QSO in the filtered list had 00:00:00 as the begin time, the "Changed item in QSO already uploaded to LoTW" appeared immediately. It also appeared every time I selected that QSO again, i.e. when I pushed the |< or >| buttons to move to the top or bottom of the list. DXKeeper v15.9.9.


Re: DXKeeper Questions

Dale Drake
 

The QSO was not uploaded to LoTW when I logged it with WW. 

 

In WW config on the Log tab “Upload to LoTW when logging” was not checked.

 

To upload the QSO to LoTW I right clicked the QSO in DXK and selected “Add entry to QSL Queue (Lotw)” along with several other QSO’s (not logged at 00:00:00) then in the DXK QSL tab I clicked the “Upload to LotW” radio button.  That produced the screen shot I previously uploaded.

 

Additionally if I now click on the subject QSO in DXK I get the popup “ Changed item in QSO already uploaded to LoTW, changed QSO_Begin item in QSO with N1STB at 2021-03-11 00:00:00 on 40M in CW, after completing and saving changes, resubmit this QSO to LoTW”  despite having made no changes to the QSO.

 

 

Dale AA1QD


Re: Satellite Modes

Dave AA6YQ
 

+ AA6YQ comments below

Newer satellite mode-names do use a combination of two letters, representing the up- and down-link band.

As there are: H 15m, T 10m, V 2m, U 70cm, L 23cm, S 13cm, C 6cm, X 3cm, K 1,2cm, Q 6mm

Maybe it might be a good idea to give the user an editable list, if this is not to much to change. This might be a good way to be prepared for any future changes. Of course you might fill a default list as a starter.

+ I have sent you a new version of DXKeeper that if on startup finds a file named SatelliteModes.txt in its Databases folder, loads its Satellite Mode selectors from the satellite modes specified in this file, one line per mode. Otherwise, the Satellite Mode selectors are loaded with the default Satellite Modes made provided in previous versions of DXKeeper.

+ Please let me know now it goes...

73,

Dave, AA6YQ


Re: DXKeeper Questions

Dave AA6YQ
 

+ AA6YQ comments below

I was able to reproduce the similar behavior (QSO logged as 0000z begin & end time) I saw b4. I uploaded a screen shot. I created a fake QSO and logged it with WW.

+ When you logged the QSO with WinWarbler, was the QSO uploaded to LoTW?

73,

Dave, AA6YQ


Re: ErrorLog file regarding: [DXLab] Error Logging from JTAlert to DXKeeper

Dave AA6YQ
 

+ AA6YQ comments below

It doesn't. It only ever sends one instruction, no repeats ever.

A zombie JTAlert process running perhaps?

I suggest the OP restarts his PC and see if that corrects the behavior.
FWIW, there have been no other reports of duplicate logging to DXKeeper in the 3 months since JTAlert 2.16.17 was released.

+ Nor have I, Laurie.

+ Another possibility: the same message conveyed by TCP being delivered more than once. I've never encountered that either, but...

        73,

             Dave, AA6YQ

 


Re: ErrorLog file regarding: [DXLab] Error Logging from JTAlert to DXKeeper

Russ Ravella
 

Ok Dave,

Thanks very much.  I contacted you since I was hearing about the problem from DXK but this is obviously a JTA issue. I’ll contact Laurie and see what he thinks.  Thanks again for diagnosing this !

Have a great evening!
Russ


On Mar 11, 2021, at 7:04 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 12/03/2021 12:45 pm, Dave AA6YQ wrote:
I do not know why JTAlert is sending two "Log QSO" directives to DXKeeper. 
It doesn't. It only ever sends one instruction, no repeats ever.

A zombie JTAlert process running perhaps?

I suggest the OP restarts his PC and see if that corrects the behavior.
FWIW, there have been no other reports of duplicate logging to DXKeeper in the 3 months since JTAlert 2.16.17 was released.

de Laurie VK3AMA




Re: ErrorLog file regarding: [DXLab] Error Logging from JTAlert to DXKeeper

HamApps Support (VK3AMA)
 

On 12/03/2021 12:45 pm, Dave AA6YQ wrote:
I do not know why JTAlert is sending two "Log QSO" directives to DXKeeper. 
It doesn't. It only ever sends one instruction, no repeats ever.

A zombie JTAlert process running perhaps?

I suggest the OP restarts his PC and see if that corrects the behavior.
FWIW, there have been no other reports of duplicate logging to DXKeeper in the 3 months since JTAlert 2.16.17 was released.

de Laurie VK3AMA




Re: ErrorLog file regarding: [DXLab] Error Logging from JTAlert to DXKeeper

Dave AA6YQ
 

Thanks for the errorlog, Russ. It shows that DXKeeper received a directive from JTAlert log a QSO with KG5HTH and submit it to eQSL and LoTW.

2021-03-12 01:15:44.900 > TCPServerModule.DataArrival, ByteCount = 744
2021-03-12 01:15:44.902 > Request = <command:11>eqsllotwlog<parameters:705><CALL:6>KG5HTH<QSO_DATE:8>20210312<TIME_ON:6>011415<TIME_OFF:6>011515<FREQ:9>10.138186<FREQ_RX:9>10.138186<MODE:3>FT8<RST_SENT:3>+13<RST_RCVD:3>+02<GRIDSQUARE:6>EM02wi<LAT:11>N032 21.250<LON:11>W098 07.500<DISTANCE:4>1216<TX_PWR:2>12<COMMENT:49>Test QSO for Dave to debug DXK double log problem<NAME:18>PHILIP R FLINN, II<QTH:11>Morgan Mill<STATE:2>TX<CNTY:8>TX,Erath<ADDRESS:68>Philip R Flinn, II
PO BOX 96
Morgan Mill
TX, 76465
UnitedStates<ANT_AZ:2>85<DXCC:3>291<CQZ:1>4<ITUZ:1>7<CONT:2>NA<APP_DXKeeper_LOTW_MEMBER:1>Y<APP_DXKeeper_EQSL_MEMBER:1>A<SFI:2>78<A_INDEX:1>4<K_INDEX:1>3<APP_DXKEEPER_USER_DEFINED_1:1>Y<MY_GRIDSQUARE:6>DM41LX<OPERATOR:4>KR6W<STATION_CALLSIGN:4>KR6W<QSO_COMPLETE:1>Y<EOR>

The QSO was successfully logged

2021-03-12 01:15:46.104 > ADIF.ImportRecord complete

and then successfully submitted to TQSL for uploading to LoTW:

2021-03-12 01:15:47.840 > TQSL Version 2.5.7 [v2.5.7]
2021-03-12 01:15:47.841 > Signing using Callsign KR6W, DXCC Entity UNITED STATES OF AMERICA
2021-03-12 01:15:47.841 >
2021-03-12 01:15:47.842 > Attempting to upload one QSO
2021-03-12 01:15:47.843 > C:\DXLab\DXKeeper\LotWUpload.ADI: Log uploaded successfully with result:
2021-03-12 01:15:47.843 >
2021-03-12 01:15:47.844 > File queued for processing
2021-03-12 01:15:47.844 > After reading this message, you may close this program.
2021-03-12 01:15:47.845 > Final Status: Success(0)
.

5 seconds later, DXKeeper received a second directive from JTAlert to log the same QSO with KG5HTH, and submit it to eQSL and LoTW:

2021-03-12 01:15:53.395 > TCPServerModule.DataArrival, ByteCount = 744
2021-03-12 01:15:53.395 > Request = <command:11>eqsllotwlog<parameters:705><CALL:6>KG5HTH<QSO_DATE:8>20210312<TIME_ON:6>011415<TIME_OFF:6>011515<FREQ:9>10.138186<FREQ_RX:9>10.138186<MODE:3>FT8<RST_SENT:3>+13<RST_RCVD:3>+02<GRIDSQUARE:6>EM02wi<LAT:11>N032 21.250<LON:11>W098 07.500<DISTANCE:4>1216<TX_PWR:2>12<COMMENT:49>Test QSO for Dave to debug DXK double log problem<NAME:18>PHILIP R FLINN, II<QTH:11>Morgan Mill<STATE:2>TX<CNTY:8>TX,Erath<ADDRESS:68>Philip R Flinn, II
PO BOX 96
Morgan Mill
TX, 76465
United States<ANT_AZ:2>85<DXCC:3>291<CQZ:1>4<ITUZ:1>7<CONT:2>NA<APP_DXKeeper_LOTW_MEMBER:1>Y<APP_DXKeeper_EQSL_MEMBER:1>A<SFI:2>78<A_INDEX:1>4<K_INDEX:1>3<APP_DXKEEPER_USER_DEFINED_1:1>Y<MY_GRIDSQUARE:6>DM41LX<OPERATOR:4>KR6W<STATION_CALLSIGN:4>KR6W<QSO_COMPLETE:1>Y<EOR>

The attempt to submit this QSO to LoTW failed, since it had already been uploaded:

2021-03-12 01:15:55.098 > TQSL Version 2.5.7 [v2.5.7]
2021-03-12 01:15:55.098 > Signing using Callsign KR6W, DXCC Entity UNITED STATES OF AMERICA
2021-03-12 01:15:55.099 > Already Uploaded QSO suppressed on line 5
2021-03-12 01:15:55.099 > CALL: KG5HTH
2021-03-12 01:15:55.100 > TIME_ON: 011415
2021-03-12 01:15:55.100 > QSO_DATE: 20210312
2021-03-12 01:15:55.101 > MODE: FT8
2021-03-12 01:15:55.101 > BAND: 30M
2021-03-12 01:15:55.102 > FREQ: 10.138186
2021-03-12 01:15:55.102 > BAND_RX: 30M
2021-03-12 01:15:55.103 > FREQ_RX: 10.138186
2021-03-12 01:15:55.104 > PROP_MODE: F2
2021-03-12 01:15:55.105 > Signing aborted
2021-03-12 01:15:55.106 > All QSOs are already uploaded; aborted
2021-03-12 01:15:55.106 > No records to upload
2021-03-12 01:15:55.107 > Final Status: No QSOs written(8)

I do not know why JTAlert is sending two "Log QSO" directives to DXKeeper.

73,

Dave, AA6YQ


Re: Error Logging from JTAlert to DXKeeper

Dave AA6YQ
 

+ AA6YQ comments below

Yeah, it seems like it's suddenly started trying to upload twice but I'm pretty darn sure I haven't touched any settings anywhere. I confirmed the 'Enable' box in SC is unchecked as requested but it would have to always have been unchecked since this has always worked ? What could be going on all of a sudden 1!?!

+ So that I can see what's going on, please do the following

1. on the General tab of DXKeeper's Configuration window, check the "Log debugging info" box

2. terminate DXKeeper

3. start DXKeeper, and wait for it to fully initialize

4. log a QSO with JT-Alert, and wait for this operation to fully complete

5. on the General tab of DXKeeper's Configuration window, uncheck the "Log debugging info" box

6. attach the errorlog.txt file from your DXKeeper folder to an email message, and send the email message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ


Re: Question about spot in FT8

Dave AA6YQ
 

+ AA6YQ comments below

The go QRT response (from me) was an attempt at levity. Sorry you took it literally.

Your problem is that you don't want to see spots of your Callsign from other FT8 users.

You can't force everyone else to turn off their PSKReporter spotting or Cluster spotting, so your only option is to configure
SpotCollector to avoid showing these spots. This is the correct group to get an authoritative answer as to how to do that, assuming
it is possible.

+ If you don't want to Spot Database Entries for your callsign to be created, add your callsign to SpotCollector's "Special
Callsign" list with no tags.

73,

Dave, AA6YQ


Re: Error Logging from JTAlert to DXKeeper

Russ Ravella
 

Hi Dave,

Yeah, it seems like it’s suddenly started trying to upload twice but I’m pretty darn sure I haven’t touched any settings anywhere. I confirmed the “Enable” box in SC is unchecked as requested but it would have to always have been unchecked since this has always worked ? What could be going on all of a sudden 1!?!

Thanks1
Russ

On Mar 11, 2021, at 4:08 PM, Dave AA6YQ <aa6yq@ambersoft.com> wrote:

+ AA6YQ comments below

After about 3 weeks away I just fired things up and there were a couple of s/w updates to DXL and the usual database updates which I installed. Now, when I complete a WSJT-X QSO and log from JTAlert, I receive several error messages/ notifications as follows:

An error box appears saying:
"No QSOs were uploaded to LoTW",
"no QSOs were processed because some QSOs were duplicates or invalid"

Then a Notepad screen appears titled "LoTWResult.txt" with several lines including:
"Already uploaded QSO surpassed on line 5" and further down, "Signing aborted. All QSOs are already uploaded; Aborted", "No records to upload", "Final Status: No QSO written(8)"

Another status box also appears titled "DXKeeper Club Log Upload" which says:
"Upload QSO to Clublog Succeeded: Dupe"

When I click off this later, a second entry for the same QSO is placed in DXKeeper

I checked JTAlert and sure enough there was a newer version which I also installed but it had no effect on the above. I haven changed any settings in any software, or added or deleted any software since before the issue started. I don't see that anyone else has reported this so it must be unique to my configuration. I would very much appreciate some help.

+ I sounds like you have things configured in a way that uploads each new QSO to LoTW and Club Log twice.

+ If you're using JT-Alert, then the Enable box should be unchecked in the WSJT-X panel on the "Spot Sources" tab of SpotCollector's Configuration window. Is that the case?

73,

Dave, AA6YQ






3201 - 3220 of 203497