Date   

Re: Error Msg #503

Bob
 

I suppose it would be more accurate to say something like this:

NOTE: It is recommended you NOT backup directly to a cloud/remote drive. Create a \Backup directory on a local drive, change file path on your Logger32 backup window to point to this directory. Then after the backup is completed, move the complete \Backup directory to the cloud drive. 

After making several backups, you will notice that Logger32 maintains the 10 most recent backup - files named <whatever>-001.zip, -002.zip, etc. 010 is the most recent. When you have the full compliment of 10 backups and you make another one, it is temporarily called 011. Then the fun starts that often causes the cloud to Chernobyl ... 001 is deleted, 002 is renamed 001, 003 is renamed 002, 004 is renamed 003, etc. until 011 is renamed 010 and we once again have out 10 most recent backups. SeventyThree(s).

On November 5, 2019 at 2:31 PM Bob <k4cy@...> wrote:

"I:\LOGBOOKBACKUP_FULL_001.ZIP" does not exist

If the error really is  does not exist, then is the I drive a cloud or remote drive? If so, see this from the help file. SeventyThree(s).


On November 5, 2019 at 1:31 PM ROBERT JURISH <k9dt@...> wrote:

Gary,
I keep getting the following error #503 msg.
"I:\LOGBOOKBACKUP_FULL_001.ZIP" does not exist.

Program works just fine otherwise.

Any suggestions?

Thanks,

Bob K9DT
On November 5, 2019 at 11:35 AM Gary Hinson <Gary@...> wrote:

You’re welcome Dave.  I hope it works out OK for you.

 

GL!

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Dave Hobro
Sent: 05 November 2019 23:12
To: hamlogger@groups.io
Subject: Re: [hamlogger] ADIF Editing

 

Thanks Gary for the 'tutorial'.

Because I had the issues with Clublog reassigning countries, I had never looked any further into the ClubLog validations.  Armed with your information I will run a validation and see what it throws up, might not be for a week or two.  With a direct email address I will get in touch with ClubLog again which may help them to resolve any issues with deleted countries etc.

73's
Dave, G4IDF

 



 

 

 


Re: Error Msg #503

Bob
 

"I:\LOGBOOKBACKUP_FULL_001.ZIP" does not exist

If the error really is  does not exist, then is the I drive a cloud or remote drive? If so, see this from the help file. SeventyThree(s).


On November 5, 2019 at 1:31 PM ROBERT JURISH <k9dt@...> wrote:

Gary,
I keep getting the following error #503 msg.
"I:\LOGBOOKBACKUP_FULL_001.ZIP" does not exist.

Program works just fine otherwise.

Any suggestions?

Thanks,

Bob K9DT
On November 5, 2019 at 11:35 AM Gary Hinson <Gary@...> wrote:

You’re welcome Dave.  I hope it works out OK for you.

 

GL!

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Dave Hobro
Sent: 05 November 2019 23:12
To: hamlogger@groups.io
Subject: Re: [hamlogger] ADIF Editing

 

Thanks Gary for the 'tutorial'.

Because I had the issues with Clublog reassigning countries, I had never looked any further into the ClubLog validations.  Armed with your information I will run a validation and see what it throws up, might not be for a week or two.  With a direct email address I will get in touch with ClubLog again which may help them to resolve any issues with deleted countries etc.

73's
Dave, G4IDF

 



 

 


Re: Error Msg #503

Bob
 

"I:\LOGBOOKBACKUP_FULL_001.ZIP" does not exist.

If the message was Cannot open zip file, then your problem is that Logger32 can not see the I drive. SeventyThree(s)

On November 5, 2019 at 1:31 PM ROBERT JURISH <k9dt@...> wrote:

Gary,
I keep getting the following error #503 msg.
"I:\LOGBOOKBACKUP_FULL_001.ZIP" does not exist.

Program works just fine otherwise.

Any suggestions?

Thanks,

Bob K9DT
On November 5, 2019 at 11:35 AM Gary Hinson <Gary@...> wrote:

You’re welcome Dave.  I hope it works out OK for you.

 

GL!

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Dave Hobro
Sent: 05 November 2019 23:12
To: hamlogger@groups.io
Subject: Re: [hamlogger] ADIF Editing

 

Thanks Gary for the 'tutorial'.

Because I had the issues with Clublog reassigning countries, I had never looked any further into the ClubLog validations.  Armed with your information I will run a validation and see what it throws up, might not be for a week or two.  With a direct email address I will get in touch with ClubLog again which may help them to resolve any issues with deleted countries etc.

73's
Dave, G4IDF

 



 

 


Re: Error Msg #503

ROBERT JURISH <k9dt@...>
 

Gary,
I keep getting the following error #503 msg.
"I:\LOGBOOKBACKUP_FULL_001.ZIP" does not exist.

Program works just fine otherwise.

Any suggestions?

Thanks,

Bob K9DT

On November 5, 2019 at 11:35 AM Gary Hinson <Gary@...> wrote:

You’re welcome Dave.  I hope it works out OK for you.

 

GL!

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Dave Hobro
Sent: 05 November 2019 23:12
To: hamlogger@groups.io
Subject: Re: [hamlogger] ADIF Editing

 

Thanks Gary for the 'tutorial'.

Because I had the issues with Clublog reassigning countries, I had never looked any further into the ClubLog validations.  Armed with your information I will run a validation and see what it throws up, might not be for a week or two.  With a direct email address I will get in touch with ClubLog again which may help them to resolve any issues with deleted countries etc.

73's
Dave, G4IDF

 



 


Re: ADIF Editing

Gary Hinson
 

You’re welcome Dave.  I hope it works out OK for you.

 

GL!

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Dave Hobro
Sent: 05 November 2019 23:12
To: hamlogger@groups.io
Subject: Re: [hamlogger] ADIF Editing

 

Thanks Gary for the 'tutorial'.

Because I had the issues with Clublog reassigning countries, I had never looked any further into the ClubLog validations.  Armed with your information I will run a validation and see what it throws up, might not be for a week or two.  With a direct email address I will get in touch with ClubLog again which may help them to resolve any issues with deleted countries etc.

73's
Dave, G4IDF


Re: New version 3.50.399 and FT4/FT8 - how obtain QSL_Via and windows Worked/Confirmed

Jerzy Smietanski SP9AUV
 

Hello Bob !
Thank you for a help and detailed description of cooperation with Logger32 on FT4 / FT8 emissions

                          73 de Jerzy SP9AUV
                        http://sp9auv.com/EN

W dniu 2019-11-04 o 22:07, Bob pisze:
Many questions in one message ... In this picture the cherry-picker has just made a QSO with K8MU and it is logged automatically. If I want to make a DX Spot, than I click on the Cherry-picking event viewer SPOT menu. Nothing else to do.



Now in this picture I need additional information about K8MU to decide if I want to QSL and how. In my example I use HamQTH, but it is the same if you use QRZ.com. All I do is left click the mouse on K8MU on the Logbook Page window and I see this:



With this additional information, I can decide what I want to do. SeventyThree(s).

On November 4, 2019 at 3:47 PM Jerzy Smietanski SP9AUV <sp9auv@...> wrote:

Hello Bob !

You are do a new version 3.50.399
Support added to allow DX Spots from FT4/FT8 Event viewer windows

Can you more describing this update .
I' m look for a version to obtain personal data from a QRZ.COM via my external lookup , especially
for a QSL_Via data , also when working on FT4/FT8 . Then I can determine , if I need send QSL and if I need send it via DIRECT .
Also is very usefull will be then window Worked/Confirmed with filling proper data .
Based on this data I can determine if  I need do this QSO , because it is a new country for me .

                                               Best regards de Jerzy SP9AUV


Wolny od wirusów. www.avast.com

 



Wolny od wirusów. www.avast.com


Re: ADIF Editing

Dave Hobro
 

Thanks Gary for the 'tutorial'.

Because I had the issues with Clublog reassigning countries, I had never looked any further into the ClubLog validations.  Armed with your information I will run a validation and see what it throws up, might not be for a week or two.  With a direct email address I will get in touch with ClubLog again which may help them to resolve any issues with deleted countries etc.

73's
Dave, G4IDF


Re: Odg: Odg: [hamlogger] LOTW files export

sp5ewx
 

If you find any solution pls let  me know
73’s Mike sp5ewx

On Tue, 5 Nov 2019 at 10:04, gabor.s57wj@... <gabor.s57wj@...> wrote:
I did not have time yesterday to deal with this problem... 

73! Gabor, S57WJ 

Sent from Huawei mobile device. 


-------- Izvirno sporočilo --------
Zadeva: Re: Odg: [hamlogger] LOTW files export
Od: sp5ewx
Za: hamlogger@groups.io
Kp:

Hi Gabor 
Did you resolve the problem ...Mine still exist ..I made the back up of log and reinstaled it ..The roblem still exist ...I tried to write down new QSOs under any call sign I use in this logger i/e sp5ewx/1 ..sp5ewx/7 etc ...These QSOs also cant be send into log files I ask Bob for help and sent him part of my log ...On his comp everything going correctly ...I have no idea what could be the reason ..I copied the log into my laptop ...The same problem 
regards 
Mike sp5ewx


Odg: Odg: [hamlogger] LOTW files export

gabor.s57wj@gmail.com
 

I did not have time yesterday to deal with this problem... 

73! Gabor, S57WJ 

Sent from Huawei mobile device. 


-------- Izvirno sporočilo --------
Zadeva: Re: Odg: [hamlogger] LOTW files export
Od: sp5ewx
Za: hamlogger@groups.io
Kp:

Hi Gabor 
Did you resolve the problem ...Mine still exist ..I made the back up of log and reinstaled it ..The roblem still exist ...I tried to write down new QSOs under any call sign I use in this logger i/e sp5ewx/1 ..sp5ewx/7 etc ...These QSOs also cant be send into log files I ask Bob for help and sent him part of my log ...On his comp everything going correctly ...I have no idea what could be the reason ..I copied the log into my laptop ...The same problem 
regards 
Mike sp5ewx


Re: Odg: [hamlogger] LOTW files export

sp5ewx
 

Hi Gabor 
Did you resolve the problem ...Mine still exist ..I made the back up of log and reinstaled it ..The roblem still exist ...I tried to write down new QSOs under any call sign I use in this logger i/e sp5ewx/1 ..sp5ewx/7 etc ...These QSOs also cant be send into log files I ask Bob for help and sent him part of my log ...On his comp everything going correctly ...I have no idea what could be the reason ..I copied the log into my laptop ...The same problem 
regards 
Mike sp5ewx


Re: New version 3.50.399 and FT4/FT8 - how obtain QSL_Via and windows Worked/Confirmed

Bob
 

Many questions in one message ... In this picture the cherry-picker has just made a QSO with K8MU and it is logged automatically. If I want to make a DX Spot, than I click on the Cherry-picking event viewer SPOT menu. Nothing else to do.



Now in this picture I need additional information about K8MU to decide if I want to QSL and how. In my example I use HamQTH, but it is the same if you use QRZ.com. All I do is left click the mouse on K8MU on the Logbook Page window and I see this:



With this additional information, I can decide what I want to do. SeventyThree(s).

On November 4, 2019 at 3:47 PM Jerzy Smietanski SP9AUV <sp9auv@...> wrote:

Hello Bob !

You are do a new version 3.50.399
Support added to allow DX Spots from FT4/FT8 Event viewer windows

Can you more describing this update .
I' m look for a version to obtain personal data from a QRZ.COM via my external lookup , especially
for a QSL_Via data , also when working on FT4/FT8 . Then I can determine , if I need send QSL and if I need send it via DIRECT .
Also is very usefull will be then window Worked/Confirmed with filling proper data .
Based on this data I can determine if  I need do this QSO , because it is a new country for me .

                                               Best regards de Jerzy SP9AUV


Wolny od wirusów. www.avast.com

 


New version 3.50.399 and FT4/FT8 - how obtain QSL_Via and windows Worked/Confirmed

Jerzy Smietanski SP9AUV
 

Hello Bob !

You are do a new version 3.50.399
Support added to allow DX Spots from FT4/FT8 Event viewer windows

Can you more describing this update .
I' m look for a version to obtain personal data from a QRZ.COM via my external lookup , especially
for a QSL_Via data , also when working on FT4/FT8 . Then I can determine , if I need send QSL and if I need send it via DIRECT .
Also is very usefull will be then window Worked/Confirmed with filling proper data .
Based on this data I can determine if  I need do this QSO , because it is a new country for me .

                                               Best regards de Jerzy SP9AUV


Wolny od wirusów. www.avast.com


Re: FT-101D and FT-101MP

nikkarkav
 

Me, please.Thanks one more time for the nice logging software u did.
SV3BSF Nikos.

On Mon, Nov 4, 2019 at 9:25 PM Bob <k4cy@...> wrote:
Anyone else need the modified version with BS command (Band Stacking) antenna switching? 73.


Re: ADIF Editing

Gary Hinson
 

Hi Dave.

 

It’s unusual to get no response from the Club Log team: maybe the emails are going astray?  Anyway, the best Club Log contact for DXCC info is Alan 5B4AHJ   g3pmr@...   Alan does a fantastic job checking details and maintaining the DXCC database in Club Log.  He’s keen to make corrections based on reliable info such as those QSL cards you mentioned.

 

Meanwhile, using Setup à Updates à “Validate your logbook DXCC country codes from Club Log”, the manual option (“Manual confirmation of changes”) gives you the chance to consider then accept or reject the individual corrections suggested by Club Log e.g.:

 

 

You have control.  It doesn’t make changes unless you agree them.

 

Admittedly, it would be more useful if Logger32 gave us the chance to review the QSO records in question (including any notes in our log and QSL info) so what I do is scribble down each callsign on a scrap of paper, select “No” to the change, then after all the checks are done, look up the QSOs in my log one-by-one for further consideration.  [Periodically re-uploading my whole log to Club Log achieves the same thing, except it emails me a report showing all the dubious QSOs: again, it only points out possible issues.  It doesn’t change my log.]

73 GL

Gary  ZL2iFB

 

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Dave Hobro
Sent: 04 November 2019 23:50
To: hamlogger@groups.io
Subject: Re: [hamlogger] ADIF Editing

 

Hi Ken, Gary
I have emailed Michael, G7VJR twice, and raised a ticket about this issue but not a single reply to date (approx 2 years ago).  I have got an on-line DXCC application on the ARRL website, this is correctly identifying all of the ClubLog "errors" as deleted countries.  My LoTW, on-line DXCC and Logger32 DXCC totals agree with each other regarding deleted countries - it is the ARRL that run the DXCC countries list so at least LoTW and an on-line DXCC should be correct. As the QSL card was originated by the DX station, I am quite happy to go with the information on the card rather than risk the integrity of my logbook by importing a third party file which may imbalance the totals.  I may be the exception to the rule over this but for me ClubLog is a non-starter.

73's
Dave, G4IDF


FT-101D and FT-101MP

Bob
 

Anyone else need the modified version with BS command (Band Stacking) antenna switching? 73.


Re: CAT Control of FTDX101 via Logger 32

Vince Shirley
 

Thanks Bob....


Vince G0ORC

On Mon, 4 Nov 2019 at 18:39, Bob <k4cy@...> wrote:
Yep, the BS command works too. I'll leave it that way. thanks, 73.
On November 4, 2019 at 11:45 AM Vince Shirley <vince.g0orc@...> wrote:

Sorry, the fourth line should read..

Then, when I clicked on a spot the radio would remember the antenna and Logger32 would move the radio to the commanded frequency.  

On Mon, 4 Nov 2019 at 16:38, Vince Shirley via Groups.Io <vince.g0orc= gmail.com@groups.io> wrote:
Bob,

Yes, that's exactly what I'm saying.

Logger32 can't know what antenna is used by the individual operator for each band, but if its set manually the radio will remember it.

So, what I used to do with the 5000 was manually go through each band and select the appropriate antenna for each band

Then, when I clicked on a spot the radio would remember the band and Logger32 would move the radio to the commanded frequency.

Logger32 to move to 14018 needs to send something like this.

BS05;FA014018000;MD03;NA01;FA014018000;

The BS command needs to correspond with the band of the spot in the syntax BSxx;

where xx is as follows.

00 1.8MHz      01  3.5MHz      02  5.0MHz
03 7.0MHz      04  10MHz       05  14MHz
06 18MHz       07  21MHz       08  24.5MHz
09  28MHz      10  50MHz       11  GEN
17 70MHz



Vince G0ORC




On Mon, 4 Nov 2019 at 16:06, Bob < k4cy@...> wrote:
Vince, are you saying I need to do all that BS stuff (no pun intended) with the FT-101s, and not worry about sending actual antenna switching commands with set frequency commands from Logger32?  73
On November 4, 2019 at 10:58 AM Vince Shirley < vince.g0orc@...> wrote:

Bob,

What Darren has suggested is correct...

Vince

On Mon, 4 Nov 2019 at 13:31, Darren Collins (G0TSM) < daz@...> wrote:
When the FTDX5000 came out Bob corrected the same issue ( I think)
Logger32 needs to send the band command first and then the mode and frequency.

Sending the BS command will put the rig on the right band and the band stack registers select the antenna, ipo, att, etc. This should be immediately followed by the mode and freq. I think that’s right.

Sorry I’m away from the shack this week so can’t check at home, but I did have a glance through the pdf for the 101’s CAT commands, and it appears to be similar.

73 Darren G0TSM





On 4 Nov 2019, at 13:05, Bob < k4cy@...> wrote:

Dave, I see that, but how does Logger32 know when to use P1=0 or P1=1? SeventyThree(s).
On November 4, 2019 at 7:57 AM Dave Colliau < n8dc-8@...> wrote:

p1=0 p2=1 that would be main band antenna 1
Dave N8DC
On November 4, 2019 at 7:54 AM Bob < k4cy@...> wrote:

I see this in the Yaesu destructions:



What is main/sub band? What do I use for the P1 value? SeventyThree(s)
On November 4, 2019 at 7:21 AM Bob < k4cy@...> wrote:

Phil, looking at the code, I see antenna switching CAT is coded for Icom and the  FT-2000, FT-9000 and FT-5000. But not the FT-991 (I have no idea if it has that capability. If it does, no one has whined yet). In Logger32 the FT-101D and FT-101MP is actually the FT-991 code (it's all smoke and mirrors). So it follows that there 'ain't any antenna commands being sent to either the 101D or 101MP. So, what are the appropriate CAT commands? I'll add them (and probably add the FT-101MP radio type while I'm in there mucking around). Then I'll send you a test version just in time for Guy Fawkes ... SeventyThree(s).
On November 4, 2019 at 3:51 AM "Philip (G4OBK) Catterall" < cq@...> wrote:

HI Bob / All

I've just moved over from using the Yaesu FTDX5000 to the FTDX101MP. I configured the CAT for the FTDX101MP within Logger 32 via RS232 using the same microHam Keyer virtual COM port for the CAT connections as I used on the FTDX5000. In Setup Radio 1 I chose Radio FT-101D Com 7, 9600 baud, Datbits 8, Stop bits 1, Parity None. DTR & RTS High, polling interval 100 ms, use narrow CW filter.  The FT-991 radio if selected will also work. The CAT works - however: 

Whilst the CAT works as it should in terms of clicking on a DX spot from the Logger DX Spots window which puts the FT-101 on to the correct frequency and mode, the antenna does not switch to the correct one for the specific band as it did on the FTDX5000. The antenna remains fixed and does not switch.  i.e. There are 3 antenna inputs on the FT-101 for different bands.  If I manually change bands on the FT-101 with the band switches on the radio the antenna changes to the appropriate one for that band as it should, but it doesn't switch as it should using CAT via Logger 32, yet it did with the FTDX5000 setup! 

Could it be that there are differences between the software in Logger 32 that controls the CAT settings relating to antenna switching between the FTDX5000 and the FT-101D? Maybe some code is missing? 

73 and thanks de Phil G4OBK 

 

 

 

 

 

 


 

 

 

 

 


 


Re: CAT Control of FTDX101 via Logger 32

Bob
 

Yep, the BS command works too. I'll leave it that way. thanks, 73.

On November 4, 2019 at 11:45 AM Vince Shirley <vince.g0orc@...> wrote:

Sorry, the fourth line should read..

Then, when I clicked on a spot the radio would remember the antenna and Logger32 would move the radio to the commanded frequency.  

On Mon, 4 Nov 2019 at 16:38, Vince Shirley via Groups.Io <vince.g0orc= gmail.com@groups.io> wrote:
Bob,

Yes, that's exactly what I'm saying.

Logger32 can't know what antenna is used by the individual operator for each band, but if its set manually the radio will remember it.

So, what I used to do with the 5000 was manually go through each band and select the appropriate antenna for each band

Then, when I clicked on a spot the radio would remember the band and Logger32 would move the radio to the commanded frequency.

Logger32 to move to 14018 needs to send something like this.

BS05;FA014018000;MD03;NA01;FA014018000;

The BS command needs to correspond with the band of the spot in the syntax BSxx;

where xx is as follows.

00 1.8MHz      01  3.5MHz      02  5.0MHz
03 7.0MHz      04  10MHz       05  14MHz
06 18MHz       07  21MHz       08  24.5MHz
09  28MHz      10  50MHz       11  GEN
17 70MHz



Vince G0ORC




On Mon, 4 Nov 2019 at 16:06, Bob < k4cy@...> wrote:
Vince, are you saying I need to do all that BS stuff (no pun intended) with the FT-101s, and not worry about sending actual antenna switching commands with set frequency commands from Logger32?  73
On November 4, 2019 at 10:58 AM Vince Shirley < vince.g0orc@...> wrote:

Bob,

What Darren has suggested is correct...

Vince

On Mon, 4 Nov 2019 at 13:31, Darren Collins (G0TSM) < daz@...> wrote:
When the FTDX5000 came out Bob corrected the same issue ( I think)
Logger32 needs to send the band command first and then the mode and frequency.

Sending the BS command will put the rig on the right band and the band stack registers select the antenna, ipo, att, etc. This should be immediately followed by the mode and freq. I think that’s right.

Sorry I’m away from the shack this week so can’t check at home, but I did have a glance through the pdf for the 101’s CAT commands, and it appears to be similar.

73 Darren G0TSM





On 4 Nov 2019, at 13:05, Bob < k4cy@...> wrote:

Dave, I see that, but how does Logger32 know when to use P1=0 or P1=1? SeventyThree(s).
On November 4, 2019 at 7:57 AM Dave Colliau < n8dc-8@...> wrote:

p1=0 p2=1 that would be main band antenna 1
Dave N8DC
On November 4, 2019 at 7:54 AM Bob < k4cy@...> wrote:

I see this in the Yaesu destructions:



What is main/sub band? What do I use for the P1 value? SeventyThree(s)
On November 4, 2019 at 7:21 AM Bob < k4cy@...> wrote:

Phil, looking at the code, I see antenna switching CAT is coded for Icom and the  FT-2000, FT-9000 and FT-5000. But not the FT-991 (I have no idea if it has that capability. If it does, no one has whined yet). In Logger32 the FT-101D and FT-101MP is actually the FT-991 code (it's all smoke and mirrors). So it follows that there 'ain't any antenna commands being sent to either the 101D or 101MP. So, what are the appropriate CAT commands? I'll add them (and probably add the FT-101MP radio type while I'm in there mucking around). Then I'll send you a test version just in time for Guy Fawkes ... SeventyThree(s).
On November 4, 2019 at 3:51 AM "Philip (G4OBK) Catterall" < cq@...> wrote:

HI Bob / All

I've just moved over from using the Yaesu FTDX5000 to the FTDX101MP. I configured the CAT for the FTDX101MP within Logger 32 via RS232 using the same microHam Keyer virtual COM port for the CAT connections as I used on the FTDX5000. In Setup Radio 1 I chose Radio FT-101D Com 7, 9600 baud, Datbits 8, Stop bits 1, Parity None. DTR & RTS High, polling interval 100 ms, use narrow CW filter.  The FT-991 radio if selected will also work. The CAT works - however: 

Whilst the CAT works as it should in terms of clicking on a DX spot from the Logger DX Spots window which puts the FT-101 on to the correct frequency and mode, the antenna does not switch to the correct one for the specific band as it did on the FTDX5000. The antenna remains fixed and does not switch.  i.e. There are 3 antenna inputs on the FT-101 for different bands.  If I manually change bands on the FT-101 with the band switches on the radio the antenna changes to the appropriate one for that band as it should, but it doesn't switch as it should using CAT via Logger 32, yet it did with the FTDX5000 setup! 

Could it be that there are differences between the software in Logger 32 that controls the CAT settings relating to antenna switching between the FTDX5000 and the FT-101D? Maybe some code is missing? 

73 and thanks de Phil G4OBK 

 

 

 

 

 

 


 

 

 

 

 


 


Re: Odg: [hamlogger] LOTW files export

sp5ewx
 

Hi Bob 
May I send you the part of my log which I cant export for LOTW??
Mike sp5ewx


Re: Odg: [hamlogger] LOTW files export

Bob
 

Mike, I don't see this. Logging from JTDX to Logger32 by UDP message sets the LOTWSend flag regardless of the Logbook Page Window being open. Likewise exporting the flagged QSOs from the logbook works regardless of the Logbook Page window being open. Please double check your observations. SeventyThree(s).

On November 4, 2019 at 12:03 PM "Michael Harris via Groups.Io" <mike.harris=horizon.co.fk@groups.io> wrote:


I had a similar problem. I was using a profile for FT8 which included
the logbook entry window. Logged contacts were broadcast by wsjt-x to
L32 and the entry was flagged to export to LoTW.

I decided to close the Logbook entry window and expand the Log window.
Subsequently the contacts were not flagged to upload to LoTW. So, quite
reasonably, it seems that the setup option to flag the contact to upload
the LoTW is specific to the Logbook entry window being active, albeit
unused.

I now launch the Logbook entry window and immediately cover it with the
expanded Logbook window and all is now as before, contacts are flagged
the upload to LoTW.

Regards,

Mike VP8NO




On 04/11/2019 13:11, gabor.s57wj@gmail.com wrote:
Hello,
I had the same problem yesterday.
By the LoTW file export I can't find my callsign and I cannot export the
file.

73! Gabor, S57WJ

Sent from Huawei mobile device.


-------- Izvirno sporočilo --------
Zadeva: [hamlogger] LOTW files export
Od: sp5ewx
Za: hamlogger@groups.io
Kp:

Hello
I'm using win 10 ..after 16 Oct I cant export files for LOTW
..Logger cant see my call sign on the operator list.Before 16th
Oct everything was OK .Everything seems to be OK , ie "Send QSO
to LOTW is checked .,the field of operator is correct .When I
transfered this part of log into computer with Win7, problem
dissapeared .I tried to change operator callsign for another one
, system also  coudnt see the change.It happened after 16Oct
QSOs...Any idea ??
Mike sp5ewx



Re: Auto-update 3.50.399 is on-line ...

Larry Fravel
 

Sorry ignore.  Wrong group.

Larry K8YYY

--
Today is a good day to have a GREAT Day!

7281 - 7300 of 85258