Date   

Re: E.Mail / SMS message

Bob
 

Open HELP. Select the SEARCH Tab. Type SMS. Click LIST TOPICS. This points you to the DX Spot Window.  Open the DX Spot Window Help. Scroll down to 2.10.6  SeventyThree(s).

On January 2, 2020 at 2:48 PM Svein Henriksen <la3pu@...> wrote:

Hi all,

 

In UDP Bandmap Configuration there is an option to set up e-mail / SMS message.

However, I do not seem to be able to find where to set the telephone number to send SMS to.

I cannot find it in the help file and have looked in all the settings....I think.

Any assistance would be appreciated.

 

73 de LA3PU


 


Re: E.Mail / SMS message

Bob
 

Right click anywhere on the DX Spots Window. Click SETUP | SETUP DX SPOT ALERTS (EMAIL/SMS/SCRATCHPAD). SeventyThree(s).

On January 2, 2020 at 2:48 PM Svein Henriksen <la3pu@...> wrote:

Hi all,

 

In UDP Bandmap Configuration there is an option to set up e-mail / SMS message.

However, I do not seem to be able to find where to set the telephone number to send SMS to.

I cannot find it in the help file and have looked in all the settings....I think.

Any assistance would be appreciated.

 

73 de LA3PU


 


E.Mail / SMS message

Svein Henriksen
 

Hi all,

 

In UDP Bandmap Configuration there is an option to set up e-mail / SMS message.

However, I do not seem to be able to find where to set the telephone number to send SMS to.

I cannot find it in the help file and have looked in all the settings....I think.

Any assistance would be appreciated.

 

73 de LA3PU


ODP: [hamlogger] How to record RX frequency instead of TX?

Andy VA3PL
 

Thanks a lot Bob...been trying to figure it out for years...RYFM

Thanks
Andy SP9KR


Od: hamlogger@groups.io <hamlogger@groups.io> w imieniu użytkownika Bob <k4cy@...>
Wysłane: czwartek, 2 stycznia 2020 18:54
Do: hamlogger@groups.io <hamlogger@groups.io>
Temat: Re: [hamlogger] How to record RX frequency instead of TX?
 
Open the Radio control Panel. Right click on the vertical bar at the right (to show the menus). Click LOGGING FREQUENCY SETUP. There should be enough options there to satisfy even the most fastidious. SeventyThree(s).

On January 2, 2020 at 12:38 PM Andy VA3PL <va3pl@...> wrote:

When working split transmitting frequency is recorded.
Is there somewhere setting that receiving frequency will be recorded.

Andy SP9KR

 


ODP: [hamlogger] How to record RX frequency instead of TX?

Andy VA3PL
 

Thanks David...believe it or not I have been trying to figure it out for quite some time...hi hi
Hat off to you
Thanks a lot.

Andy SP9KR


Od: hamlogger@groups.io <hamlogger@groups.io> w imieniu użytkownika David G3YYD via Groups.Io <g3yyd2@...>
Wysłane: czwartek, 2 stycznia 2020 18:42
Do: hamlogger@groups.io <hamlogger@groups.io>
Temat: Re: [hamlogger] How to record RX frequency instead of TX?
 

Yep in main log it is headed FREQ RX but you have to enable it on grid layout to see it.

 

73 David G3YYD

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Andy VA3PL
Sent: 02 January 2020 17:39
To: hamlogger@groups.io
Subject: [hamlogger] How to record RX frequency instead of TX?

 

When working split transmitting frequency is recorded.

Is there somewhere setting that receiving frequency will be recorded.

 

Andy SP9KR


Re: How to record RX frequency instead of TX?

Bob
 

Open the Radio control Panel. Right click on the vertical bar at the right (to show the menus). Click LOGGING FREQUENCY SETUP. There should be enough options there to satisfy even the most fastidious. SeventyThree(s).

On January 2, 2020 at 12:38 PM Andy VA3PL <va3pl@...> wrote:

When working split transmitting frequency is recorded.
Is there somewhere setting that receiving frequency will be recorded.

Andy SP9KR

 


Re: How to record RX frequency instead of TX?

David G3YYD
 

Yep in main log it is headed FREQ RX but you have to enable it on grid layout to see it.

 

73 David G3YYD

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Andy VA3PL
Sent: 02 January 2020 17:39
To: hamlogger@groups.io
Subject: [hamlogger] How to record RX frequency instead of TX?

 

When working split transmitting frequency is recorded.

Is there somewhere setting that receiving frequency will be recorded.

 

Andy SP9KR


How to record RX frequency instead of TX?

Andy VA3PL
 

When working split transmitting frequency is recorded.
Is there somewhere setting that receiving frequency will be recorded.

Andy SP9KR


Re: question about dxcc-table

Bob
 

Now you know why no DXCC information is being logged. Logger32 doesn't know where you are. Click SETUP | UPDATES | COUNTRY DATABASE EXCEPTIONS FROM CLUB LOG | LOOK FOR UPDATES NOW. When updates have finished downloading/installing, try entering DK4WD id the Logbook Entry Window again. Does Logger32 know you are in Germany now? SeventyThree(s).

On January 2, 2020 at 11:17 AM Matthias Bellmann <Dk4wd@...> wrote:

instead of dl eu14 it shows "** ?? ??"


Am 02.01.2020 um 17:05 schrieb Bob:
... and if you type DK4WD in the Logbook Entry Window, what Country does Logger32 say that is? 73.




On January 2, 2020 at 10:41 AM Matthias Bellmann < Dk4wd@...> wrote:


I enter my qso in the (normal ?) way into the nput window. Usually cw,
but sometimes ft8 and ssb. by pressing the enter key the just logged
qsdo is transferred into logbool page, but dxcc column contains "not
accepted". When a former qso with the station is alread logged the dxcc
is displayed correctly.


Am 02.01.2020 um 16:05 schrieb Bob:
So, how are you entering the QSO in the logbook, What mode are you operating? SeventyThree(s).


On January 2, 2020 at 9:51 AM Matthias Bellmann < Dk4wd@...> wrote:


When qsoing a new statioin the dxcc column in the logbook page remains
empty. This column is filled only after using updates menue. This is
pretty inconvenient, because the worked/confirmed window also remains
empty. So when i qso a new station i can not check whether the
appropriate country is already in my log.

I remember that in former versions of logger32 there has been a
dxcc-table. Is it still available or must i carry out the above
mentioned update?

By the way: Happy new year to all of you

73 Matthias








 


 


Re: question about dxcc-table

Matthias Bellmann
 

instead of dl eu14 it shows "** ?? ??"


Am 02.01.2020 um 17:05 schrieb Bob:

... and if you type DK4WD in the Logbook Entry Window, what Country does Logger32 say that is? 73.




On January 2, 2020 at 10:41 AM Matthias Bellmann < Dk4wd@...> wrote:


I enter my qso in the (normal ?) way into the nput window. Usually cw,
but sometimes ft8 and ssb. by pressing the enter key the just logged
qsdo is transferred into logbool page, but dxcc column contains "not
accepted". When a former qso with the station is alread logged the dxcc
is displayed correctly.


Am 02.01.2020 um 16:05 schrieb Bob:
So, how are you entering the QSO in the logbook, What mode are you operating? SeventyThree(s).


On January 2, 2020 at 9:51 AM Matthias Bellmann < Dk4wd@...> wrote:


When qsoing a new statioin the dxcc column in the logbook page remains
empty. This column is filled only after using updates menue. This is
pretty inconvenient, because the worked/confirmed window also remains
empty. So when i qso a new station i can not check whether the
appropriate country is already in my log.

I remember that in former versions of logger32 there has been a
dxcc-table. Is it still available or must i carry out the above
mentioned update?

By the way: Happy new year to all of you

73 Matthias










Re: question about dxcc-table

Bob
 

... and if you type DK4WD in the Logbook Entry Window, what Country does Logger32 say that is? 73.




On January 2, 2020 at 10:41 AM Matthias Bellmann < Dk4wd@...> wrote:


I enter my qso in the (normal ?) way into the nput window. Usually cw,
but sometimes ft8 and ssb. by pressing the enter key the just logged
qsdo is transferred into logbool page, but dxcc column contains "not
accepted". When a former qso with the station is alread logged the dxcc
is displayed correctly.


Am 02.01.2020 um 16:05 schrieb Bob:
So, how are you entering the QSO in the logbook, What mode are you operating? SeventyThree(s).


On January 2, 2020 at 9:51 AM Matthias Bellmann < Dk4wd@...> wrote:


When qsoing a new statioin the dxcc column in the logbook page remains
empty. This column is filled only after using updates menue. This is
pretty inconvenient, because the worked/confirmed window also remains
empty. So when i qso a new station i can not check whether the
appropriate country is already in my log.

I remember that in former versions of logger32 there has been a
dxcc-table. Is it still available or must i carry out the above
mentioned update?

By the way: Happy new year to all of you

73 Matthias









Re: question about dxcc-table

Bob
 

Sorry, that was not meant for you. 73.

On January 2, 2020 at 11:02 AM Kenneth Hansen <khansen@...> wrote:

Germany only

On Thu, Jan 2, 2020 at 11:01 AM Bob < k4cy@...> wrote:
... and if you type DK4WD in the Logbook Entry Window, what Country does Logger32 say that is? 73.



On January 2, 2020 at 10:41 AM Matthias Bellmann < Dk4wd@...> wrote:


I enter my qso in the (normal ?) way into the nput window. Usually cw,
but sometimes ft8 and ssb. by pressing the enter key the just logged
qsdo is transferred into logbool page, but dxcc column contains "not
accepted". When a former qso with the station is alread logged the dxcc
is displayed correctly.


Am 02.01.2020 um 16:05 schrieb Bob:
So, how are you entering the QSO in the logbook, What mode are you operating? SeventyThree(s).


On January 2, 2020 at 9:51 AM Matthias Bellmann < Dk4wd@...> wrote:


When qsoing a new statioin the dxcc column in the logbook page remains
empty. This column is filled only after using updates menue. This is
pretty inconvenient, because the worked/confirmed window also remains
empty. So when i qso a new station i can not check whether the
appropriate country is already in my log.

I remember that in former versions of logger32 there has been a
dxcc-table. Is it still available or must i carry out the above
mentioned update?

By the way: Happy new year to all of you

73 Matthias








 

 

 

--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC

 


Re: Run-time error 52

Bob
 

Please send the file to me, I will try. 73.

On January 2, 2020 at 10:59 AM Kenneth Hansen <khansen@...> wrote:

Just tried to import the same file on a Win7 laptop running Logger32 as Administrator, same error message

On Thu, Jan 2, 2020 at 10:27 AM Bob < k4cy@...> wrote:
Ken, Running as Administrator an running a program (in this case Logger32) are two different things. You must run Logger32 as an Administrator ... like this: Right click on the Logger32.exe icon, click properties. Select the compatibility tab and set the option to run Logger32 as an administrator.



The Jan2020 file is an ADIF formatted file? Are there security settings on your laptop that are preventing you from opening Jan2020.adif, or writing to the logbook? SeventyThree(s).


On January 2, 2020 at 10:10 AM Kenneth Hansen < khansen@...> wrote:

Yes I’m running as Administrator
I just named the export fine Jan2020

On Thu, Jan 2, 2020 at 10:01 AM Bob < k4cy@...> wrote:
Ken, you are running Logger32 on the laptop with Admin Privileges. Right? What is the file name you are trying to open/import on the laptop? SeventyThree(s).
On January 2, 2020 at 9:29 AM Kenneth Hansen < khansen@...> wrote:

Happy New Year
I am trying to update my logbook on my laptop running Win10
I used Export Log on the desktop running Win7
Logger32 version on both computers are 3.50.403
Importing the logbook on the laptop gives me Run-time error 52.  Bad file name or number.
Clicking on OK closes Logger32.

Any help will be Appreciated

de KB2SSE- Ken
--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC

 
 

 

 

--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC

 
 

 

 

--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC

 


Re: question about dxcc-table

Kenneth Hansen
 

Germany only

On Thu, Jan 2, 2020 at 11:01 AM Bob <k4cy@...> wrote:
... and if you type DK4WD in the Logbook Entry Window, what Country does Logger32 say that is? 73.



On January 2, 2020 at 10:41 AM Matthias Bellmann < Dk4wd@...> wrote:


I enter my qso in the (normal ?) way into the nput window. Usually cw,
but sometimes ft8 and ssb. by pressing the enter key the just logged
qsdo is transferred into logbool page, but dxcc column contains "not
accepted". When a former qso with the station is alread logged the dxcc
is displayed correctly.


Am 02.01.2020 um 16:05 schrieb Bob:
So, how are you entering the QSO in the logbook, What mode are you operating? SeventyThree(s).


On January 2, 2020 at 9:51 AM Matthias Bellmann < Dk4wd@...> wrote:


When qsoing a new statioin the dxcc column in the logbook page remains
empty. This column is filled only after using updates menue. This is
pretty inconvenient, because the worked/confirmed window also remains
empty. So when i qso a new station i can not check whether the
appropriate country is already in my log.

I remember that in former versions of logger32 there has been a
dxcc-table. Is it still available or must i carry out the above
mentioned update?

By the way: Happy new year to all of you

73 Matthias








--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC


Re: question about dxcc-table

Bob
 

... and if you type DK4WD in the Logbook Entry Window, what Country does Logger32 say that is? 73.



On January 2, 2020 at 10:41 AM Matthias Bellmann < Dk4wd@...> wrote:


I enter my qso in the (normal ?) way into the nput window. Usually cw,
but sometimes ft8 and ssb. by pressing the enter key the just logged
qsdo is transferred into logbool page, but dxcc column contains "not
accepted". When a former qso with the station is alread logged the dxcc
is displayed correctly.


Am 02.01.2020 um 16:05 schrieb Bob:
So, how are you entering the QSO in the logbook, What mode are you operating? SeventyThree(s).


On January 2, 2020 at 9:51 AM Matthias Bellmann < Dk4wd@...> wrote:


When qsoing a new statioin the dxcc column in the logbook page remains
empty. This column is filled only after using updates menue. This is
pretty inconvenient, because the worked/confirmed window also remains
empty. So when i qso a new station i can not check whether the
appropriate country is already in my log.

I remember that in former versions of logger32 there has been a
dxcc-table. Is it still available or must i carry out the above
mentioned update?

By the way: Happy new year to all of you

73 Matthias









Re: Run-time error 52

Kenneth Hansen
 

Just tried to import the same file on a Win7 laptop running Logger32 as Administrator, same error message

On Thu, Jan 2, 2020 at 10:27 AM Bob <k4cy@...> wrote:
Ken, Running as Administrator an running a program (in this case Logger32) are two different things. You must run Logger32 as an Administrator ... like this: Right click on the Logger32.exe icon, click properties. Select the compatibility tab and set the option to run Logger32 as an administrator.



The Jan2020 file is an ADIF formatted file? Are there security settings on your laptop that are preventing you from opening Jan2020.adif, or writing to the logbook? SeventyThree(s).


On January 2, 2020 at 10:10 AM Kenneth Hansen <khansen@...> wrote:

Yes I’m running as Administrator
I just named the export fine Jan2020

On Thu, Jan 2, 2020 at 10:01 AM Bob < k4cy@...> wrote:
Ken, you are running Logger32 on the laptop with Admin Privileges. Right? What is the file name you are trying to open/import on the laptop? SeventyThree(s).
On January 2, 2020 at 9:29 AM Kenneth Hansen < khansen@...> wrote:

Happy New Year
I am trying to update my logbook on my laptop running Win10
I used Export Log on the desktop running Win7
Logger32 version on both computers are 3.50.403
Importing the logbook on the laptop gives me Run-time error 52.  Bad file name or number.
Clicking on OK closes Logger32.

Any help will be Appreciated

de KB2SSE- Ken
--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC

 
 

 

 

--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC

 

--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC


Re: Run-time error 52

Kenneth Hansen
 

I am running Logger32 as administrator otherwise the updates will not work either. The file is created by Logger32 File/Export Logs/ADIF (.adi) file.
I can open/edit the file with Notepad+

On Thu, Jan 2, 2020 at 10:27 AM Bob <k4cy@...> wrote:
Ken, Running as Administrator an running a program (in this case Logger32) are two different things. You must run Logger32 as an Administrator ... like this: Right click on the Logger32.exe icon, click properties. Select the compatibility tab and set the option to run Logger32 as an administrator.



The Jan2020 file is an ADIF formatted file? Are there security settings on your laptop that are preventing you from opening Jan2020.adif, or writing to the logbook? SeventyThree(s).


On January 2, 2020 at 10:10 AM Kenneth Hansen <khansen@...> wrote:

Yes I’m running as Administrator
I just named the export fine Jan2020

On Thu, Jan 2, 2020 at 10:01 AM Bob < k4cy@...> wrote:
Ken, you are running Logger32 on the laptop with Admin Privileges. Right? What is the file name you are trying to open/import on the laptop? SeventyThree(s).
On January 2, 2020 at 9:29 AM Kenneth Hansen < khansen@...> wrote:

Happy New Year
I am trying to update my logbook on my laptop running Win10
I used Export Log on the desktop running Win7
Logger32 version on both computers are 3.50.403
Importing the logbook on the laptop gives me Run-time error 52.  Bad file name or number.
Clicking on OK closes Logger32.

Any help will be Appreciated

de KB2SSE- Ken
--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC

 
 

 

 

--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC

 

--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC


Re: question about dxcc-table

Matthias Bellmann
 

I enter my qso in the (normal ?) way into the nput window. Usually cw,
but sometimes ft8 and ssb. by pressing the enter key the just logged
qsdo is transferred into logbool page, but dxcc column contains "not
accepted". When a former qso with the station is alread logged the dxcc
is displayed correctly.


Am 02.01.2020 um 16:05 schrieb Bob:

So, how are you entering the QSO in the logbook, What mode are you operating? SeventyThree(s).


On January 2, 2020 at 9:51 AM Matthias Bellmann <Dk4wd@...> wrote:


When qsoing a new statioin the dxcc column in the logbook page remains
empty. This column is filled only after using updates menue. This is
pretty inconvenient, because the worked/confirmed window also remains
empty. So when i qso a new station i can not check whether the
appropriate country is already in my log.

I remember that in former versions of logger32 there has been a
dxcc-table. Is it still available or must i carry out the above
mentioned update?

By the way: Happy new year to all of you

73 Matthias




Re: Run-time error 52

Bob
 

Ken, Running as Administrator an running a program (in this case Logger32) are two different things. You must run Logger32 as an Administrator ... like this: Right click on the Logger32.exe icon, click properties. Select the compatibility tab and set the option to run Logger32 as an administrator.



The Jan2020 file is an ADIF formatted file? Are there security settings on your laptop that are preventing you from opening Jan2020.adif, or writing to the logbook? SeventyThree(s).


On January 2, 2020 at 10:10 AM Kenneth Hansen <khansen@...> wrote:

Yes I’m running as Administrator
I just named the export fine Jan2020

On Thu, Jan 2, 2020 at 10:01 AM Bob < k4cy@...> wrote:
Ken, you are running Logger32 on the laptop with Admin Privileges. Right? What is the file name you are trying to open/import on the laptop? SeventyThree(s).
On January 2, 2020 at 9:29 AM Kenneth Hansen < khansen@...> wrote:

Happy New Year
I am trying to update my logbook on my laptop running Win10
I used Export Log on the desktop running Win7
Logger32 version on both computers are 3.50.403
Importing the logbook on the laptop gives me Run-time error 52.  Bad file name or number.
Clicking on OK closes Logger32.

Any help will be Appreciated

de KB2SSE- Ken
--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC

 
 

 

 

--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC

 


Re: Run-time error 52

Kenneth Hansen
 

File

On Thu, Jan 2, 2020 at 10:10 AM Kenneth Hansen <khansen@...> wrote:
Yes I’m running as Administrator
I just named the export fine Jan2020

On Thu, Jan 2, 2020 at 10:01 AM Bob <k4cy@...> wrote:
Ken, you are running Logger32 on the laptop with Admin Privileges. Right? What is the file name you are trying to open/import on the laptop? SeventyThree(s).
On January 2, 2020 at 9:29 AM Kenneth Hansen <khansen@...> wrote:

Happy New Year
I am trying to update my logbook on my laptop running Win10
I used Export Log on the desktop running Win7
Logger32 version on both computers are 3.50.403
Importing the logbook on the laptop gives me Run-time error 52.  Bad file name or number.
Clicking on OK closes Logger32.

Any help will be Appreciated

de KB2SSE- Ken
--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC

 

--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC
--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC