Date   

L32 v.4 Sound card data window wont open mmtty

Borut Gaberscek
 

HI.

Tray to work rtty from a long time.....when I press the sound card button, mmtty it refuses to open. When I press the option in VIEW/show sound card data, l32 switch off completely.

How to fix this? 

73 de Borut s50b


Re: V4. When using WSIT-x Manual Logging

k4cvl
 

I have a question that perhaps one of more members of the group can answer.  I am looking for a logging program that will allow me to use TWO radios at the same time, allowing BOTH access to the logbook, that will log at the same time if necessary.  I am using the Yaesu FTDx101MP now with a Flex 6700.  I was using Logger 32 with my FT-5000 radio, but thought I would try using  Log4OM for logging to see if it will do the trick. A buddy who is really good at IT stuff says that it can work in the way I want it to, but has yet to make it work. I run TWO radios and TWO PCs on my home network.  I want to put the logging software on both and operate with both being able to work as the other.  Does anyone know FOR SURE if Logger 32 or any of the many logging programs out there will do this?  - Mike, K4CVL

 


Logger32 go down when telnet to the cluster is ON

Alex Del Chicca
 

Hi to ALL,

I upgraded from the latest version 3.5 to version 4.0 without any errors.

After doing database maintenance and updating statistics, I updated to ver. 4.0.235 without problems.

 

The open windows are: Operator :, Dx Spots, Worked / Confirmed Logbook page, Previous QSOs and Telnet for IK5PWJ-6 cluster connection,

I also opened the CW Machine window.

Unfortunately after some time, sometimes 30 min. others after an hour the Logger32 program closes, leaving only the window outside

the Logger32 Window of the CW Machine open.

 

In practice the window of Logger32 disappears.

 

I then made several tests, reinstalling the logger32 vers. 4 from vers. 3.5 where I had previously deleted all the log

and then reinstalled the ik5pwj log from the previously saved adif file.

 

Unfortunately, the problem reoccurred by going the Logger32 program down and always remaining the CW Machine -Software window.

 

At this point I did a test and I disabled the connection via telnet to the cluster no longer receiving the spots both

in the Telnet window and in the DX Spot window.

 

Well .... the Logger32 program ran for hours without closing.

I am sure that the block depends on the right spots that the telnet receives and sends to the DX Spots window,

because if I reactivate the telnet connection and the spots start to arrive again, the program goes down again.

 

What's up ? and how can this problem be eliminated?

 

When I use the same configurations on the latest version of the program vers. 3.5 .... everything works,

including telnet and spot-free spots or whatever.

 

Thanks for any Help

73 Alex ik5pwj.


Re: CQWPX

Nicola Favero
 

Same problem here ! 

 

logger 3.250.424 

 

Logger 3_50_424.jpg

 

logger 4.0.235 : stop at 5k pfx

 

Logger 4_0_235.jpg

 

73

 

Nick i3fiy

 

Da: hamlogger@groups.io [mailto:hamlogger@groups.io] Per conto di Preben Dall Larsen
Inviato: venerdì 22 gennaio 2021 06:45
A: hamlogger@groups.io
Oggetto: Re: [hamlogger] CQWPX

 

Hi Gary and Carlo,

v4.0.235
Recalculation done.

I see the same, however, mine stops at UP0
and with a total of 5001 PFXs worked!

 

billede.png


73
Preben OZ5UR


Ver 4 crashes with L32Log Sync.

Chuck Kraly K0XM
 

I have updated to Ver4  completely and noticed that JTDX-TCP to L32 works but every now and then L32 will crash when sending to LOTW, or Clublog, Or QRZ (i run all 3). Has anyone else seen this?
Chuck K0XM


V4. When using WSIT-x Manual Logging

DamianM0BKV
 

I have a change with V4. When using WSIT-x in that the populated Logger32 logbook entry window, that occurs automatically, when 'Enable TX' is activated on the WSIT-x window (so as to start a QSO not call CQ) disappears equally fast when '73' is received from the contact without waiting for the MANUAL LOg the QSO from me. all populated QSO information from QRZ with name is lost unless I manually repopulate the Logger32 logbook window again from the callsign if it's still in the UDP Bandplan Window before I manually log. With V3 this didn't happen. If I set auto Log (with V4) on receive of 73 it probably is OK but I like to manual log.
Otherwise, V4 works great Bob. Damian M0BKV


Re: Callsign not transferring from bandmap to log entry window (WSJT-X).

DamianM0BKV
 

I have a similar change with V4 in that the populated logbook entry window that occurs automatically when 'Enable TX' is activated on the WSIT-x window disappears equally fast when '73' is received from the contact without waiting for the MANUAL LOg QSO from me. all populated QSO information from QRZ with name is lost unless I manually repopulate the Logger32 logbook window again from the callsign if its still in the UDP Bandplan Window before I manually log. With V3 this didn't happen. If I auto Log on 73 it probably is OK. Damian M0BKV


Re: A couple of rotator questions - Version 4

Bob
 

PSTRotatorAz? Never heard of it before, so I can't comment. However, I can comment about the rotor wedge. Before the wedge will appear, Logger32 must be receiving beam headings from the rotator (otherwise it doesn't know where to point the wedge). SeventyThree(s).

On 01/22/2021 3:22 PM John, G4DRS via groups.io <g4drs@...> wrote:
 
 
Firstly, in version 3, I used to use the internal rotator control, and it used to display a wedge representing the rotator beamwidth overlaid on the great circle map. Try as I might, in version 4, I can't get the wedge to show.
Secondly, in version 3, I started to use PSTRotatorAz instead of the internal Logger32 rotator controller. For some reason, I like it. In order to make it work, I had to set the rotator to none and the com port to none and check 'Enable Global Capture of CTRL-A' in Logger32 rotator setup dialogue. All was well. Since moving to version 4, that has ceased to function for some reason. It may be that something within PSTRotatorAz has to be changed to match version 4, I don't know.
Has anything changed, or have I just set something incorrectly? I have followed the instructions in PSTRotatorAz, but maybe they are no longer current in version 4.

John
G4DRS


A couple of rotator questions - Version 4

John, G4DRS
 

Firstly, in version 3, I used to use the internal rotator control, and it used to display a wedge representing the rotator beamwidth overlaid on the great circle map. Try as I might, in version 4, I can't get the wedge to show.
Secondly, in version 3, I started to use PSTRotatorAz instead of the internal Logger32 rotator controller. For some reason, I like it. In order to make it work, I had to set the rotator to none and the com port to none and check 'Enable Global Capture of CTRL-A' in Logger32 rotator setup dialogue. All was well. Since moving to version 4, that has ceased to function for some reason. It may be that something within PSTRotatorAz has to be changed to match version 4, I don't know.
Has anything changed, or have I just set something incorrectly? I have followed the instructions in PSTRotatorAz, but maybe they are no longer current in version 4.

John
G4DRS


Re: Callsign not transferring from bandmap to log entry window (WSJT-X).

Michael Harris
 

Just you or not Phil. It certainly works OK here. wsjtx > L32 UDP bandmap > Klick > Log entry pane. Not a lot of use to me I admit because of wsjtx limitations.

Regards,

Mike VP8NO

On 22/01/2021 15:30, Philip (G4OBK) Catterall wrote:
On Thu, Jan 21, 2021 at 11:49 PM, Bob wrote:
/caveat emptor:/ I use JTDX
The silence is still deafening Bob....  Maybe it is just me with this minor issue?  I also tried running JTDX and found the same - the locator came across to the log entry window but the callsign did not. Its not crucial to the operation of this great program and its integration with other software. I have another Windows 10 PC but it's not interfaced to the transceiver to try comparing results. If I get desperate I could interface it, but at the moment I'm not inclined to want to bugger up my setup which is working very nicely thank you!
73 Phil G4OBK


Re: Callsign not transferring from bandmap to log entry window (WSJT-X).

Bob
 

Phil, is it possible that the callsign field is actually being populated, but being cleared because of the logbook entry window option to 'clear callsign on QSY' (or something equally simple)? 73.

On 01/22/2021 1:30 PM Philip (G4OBK) Catterall <cq@...> wrote:
 
 
On Thu, Jan 21, 2021 at 11:49 PM, Bob wrote:
caveat emptor: I use JTDX
The silence is still deafening Bob....  Maybe it is just me with this minor issue?  I also tried running JTDX and found the same - the locator came across to the log entry window but the callsign did not. Its not crucial to the operation of this great program and its integration with other software. I have another Windows 10 PC but it's not interfaced to the transceiver to try comparing results. If I get desperate I could interface it, but at the moment I'm not inclined to want to bugger up my setup which is working very nicely thank you!

73 Phil G4OBK


Re: Callsign not transferring from bandmap to log entry window (WSJT-X).

Philip (G4OBK) Catterall
 

On Thu, Jan 21, 2021 at 11:49 PM, Bob wrote:
caveat emptor: I use JTDX
The silence is still deafening Bob....  Maybe it is just me with this minor issue?  I also tried running JTDX and found the same - the locator came across to the log entry window but the callsign did not. Its not crucial to the operation of this great program and its integration with other software. I have another Windows 10 PC but it's not interfaced to the transceiver to try comparing results. If I get desperate I could interface it, but at the moment I'm not inclined to want to bugger up my setup which is working very nicely thank you!

73 Phil G4OBK


Re: ADI problems

Bob
 

If it would help, zip and send me direct to k4cy@... any of the two files in question (preferably the 40 QSOs fixed file). SeventyThree(s).

On 01/22/2021 5:28 AM PETER DOUGHTY via groups.io <g3tkk@...> wrote:
 
 

Bob

Thanks,

Yes, that is what I did and I now have around 90 new contacts in Bad.adi, having had around 30 to 40 the first time which, having been fixed, are in the log OK. I cannot see what is going on as I have done this many times over the years.

Peter G3TKK

On 22/01/2021 10:05, Bob wrote:
What you are supposed to do is make corrections to the bad.adi file. Rename it to something like fixed.adi. Then import the fixed.adi file. Is that what you did? SeventyThree(s).
On 01/22/2021 4:58 AM PETER DOUGHTY via groups.io <g3tkk@...> wrote:
 
 

Hi Mike

 

Well, I did a straight upload of a simple adi file of my log and put it in the new setup. All well except about 30 contact data showing the problem in Bad.adi. The majority (c21500) of the QSOs are correct. I corrected them and re-ran the adi upload to find hundreds now showing. I cleared it all out and entered the last backup data as you described but i get the same problem with scores of contacts in Bad.adi.

 

Peter

On 22/01/2021 08:53, Mike wrote:
What if you make backup proper way: "Zip databases and logbook"?
Mike


Re: ADI problems

Bob
 

You might want to review the process you think you followed. You import a file with 40 QSOs. Of those 40 allegedly fixed QSOs 90 are rejected. I'm impressed. SeventyThree(s). 

On 01/22/2021 5:28 AM PETER DOUGHTY via groups.io <g3tkk@...> wrote:
 
 

Bob

Thanks,

Yes, that is what I did and I now have around 90 new contacts in Bad.adi, having had around 30 to 40 the first time which, having been fixed, are in the log OK. I cannot see what is going on as I have done this many times over the years.

Peter G3TKK

On 22/01/2021 10:05, Bob wrote:
What you are supposed to do is make corrections to the bad.adi file. Rename it to something like fixed.adi. Then import the fixed.adi file. Is that what you did? SeventyThree(s).
On 01/22/2021 4:58 AM PETER DOUGHTY via groups.io <g3tkk@...> wrote:
 
 

Hi Mike

 

Well, I did a straight upload of a simple adi file of my log and put it in the new setup. All well except about 30 contact data showing the problem in Bad.adi. The majority (c21500) of the QSOs are correct. I corrected them and re-ran the adi upload to find hundreds now showing. I cleared it all out and entered the last backup data as you described but i get the same problem with scores of contacts in Bad.adi.

 

Peter

On 22/01/2021 08:53, Mike wrote:
What if you make backup proper way: "Zip databases and logbook"?
Mike


Re: ADI problems

PETER DOUGHTY
 

Bob

Thanks,

Yes, that is what I did and I now have around 90 new contacts in Bad.adi, having had around 30 to 40 the first time which, having been fixed, are in the log OK. I cannot see what is going on as I have done this many times over the years.

Peter G3TKK

On 22/01/2021 10:05, Bob wrote:
What you are supposed to do is make corrections to the bad.adi file. Rename it to something like fixed.adi. Then import the fixed.adi file. Is that what you did? SeventyThree(s).
On 01/22/2021 4:58 AM PETER DOUGHTY via groups.io <g3tkk@...> wrote:
 
 

Hi Mike

 

Well, I did a straight upload of a simple adi file of my log and put it in the new setup. All well except about 30 contact data showing the problem in Bad.adi. The majority (c21500) of the QSOs are correct. I corrected them and re-ran the adi upload to find hundreds now showing. I cleared it all out and entered the last backup data as you described but i get the same problem with scores of contacts in Bad.adi.

 

Peter

On 22/01/2021 08:53, Mike wrote:
What if you make backup proper way: "Zip databases and logbook"?
Mike


Re: Import ADI problems

F5bqu
 

 

 

 

DEAR BOB,

 

thank you for the excellent work however and unless I am mistaken, when I importing an adif log of another instance  on my  logbook, the new qso does not increment the existing qso number but it restarts by n ° 1.

Otherwise no major worries thank you again.

 

73 QRO de F5BQU

 

 

 

 

 

Garanti sans virus. www.avast.com


Re: ADI problems

Bob
 

What you are supposed to do is make corrections to the bad.adi file. Rename it to something like fixed.adi. Then import the fixed.adi file. Is that what you did? SeventyThree(s).

On 01/22/2021 4:58 AM PETER DOUGHTY via groups.io <g3tkk@...> wrote:
 
 

Hi Mike

 

Well, I did a straight upload of a simple adi file of my log and put it in the new setup. All well except about 30 contact data showing the problem in Bad.adi. The majority (c21500) of the QSOs are correct. I corrected them and re-ran the adi upload to find hundreds now showing. I cleared it all out and entered the last backup data as you described but i get the same problem with scores of contacts in Bad.adi.

 

Peter

On 22/01/2021 08:53, Mike wrote:
What if you make backup proper way: "Zip databases and logbook"?
Mike


Re: ADI problems

PETER DOUGHTY
 

Hi Mike


Well, I did a straight upload of a simple adi file of my log and put it in the new setup. All well except about 30 contact data showing the problem in Bad.adi. The majority (c21500) of the QSOs are correct. I corrected them and re-ran the adi upload to find hundreds now showing. I cleared it all out and entered the last backup data as you described but i get the same problem with scores of contacts in Bad.adi.


Peter

On 22/01/2021 08:53, Mike wrote:
What if you make backup proper way: "Zip databases and logbook"?
Mike


Re: Import ADI problems

Bob
 

I think you will find that importing an ADIF file made by Logger32 the APP_LOGGER32_QSO_NUMBER is imported. If the ADIF file has no APP_LOGGER32_QSO_NUMBER then a new number is assigned. No change from v3.50. SeventyThree(s).

On 01/22/2021 4:15 AM F5bqu <f5bqu@...> wrote:
 
 

DEAR BOB,

 

thank you for the excellent work however and unless I am mistaken, when I importing an adif log of another instance  on my  logbook, the new qso does not increment the existing qso number but it restarts by n ° 1.

Otherwise no major worries thank you again.

 

73 QRO de F5BQU

 

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Bob
Envoyé : vendredi 22 janvier 2021 09:57
À : hamlogger@groups.io
Objet : Re: [hamlogger] ADI problems

 

You will have to explain this statement: frequency entries moved from e.g. 14.015000 into 14015000

 

When you import an ADIF file, the file is opened read only. No information is modified in the file. So, I'm obviously not understanding what you're saying. 73.

On 01/22/2021 3:44 AM PETER DOUGHTY via groups.io < g3tkk@...> wrote:

 

 

I am in the middle of moving my station software from one PC to another

and have run into ADI/BAD.adi problems.

 

I have a good .ADI backup of my logbook but when I load it into the new

Logger software ( ver 3,50,424 ) I get a massive Bad.adi file with many

( scores and scores) frequency entries moved from e.g. 14.015000 into

14015000 or even 14.015.000000.

 

I have done this many times and have not had this go wrong.

 

Please can I have some advice as what I can do to stop this happening.

 

 

Thanks

 

 

Peter  G3TKK

 

 

 

 


Garanti sans virus. www.avast.com


Re: Import ADI problems

F5bqu
 

DEAR BOB,

 

thank you for the excellent work however and unless I am mistaken, when I importing an adif log of another instance  on my  logbook, the new qso does not increment the existing qso number but it restarts by n ° 1.

Otherwise no major worries thank you again.

 

73 QRO de F5BQU

 

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Bob
Envoyé : vendredi 22 janvier 2021 09:57
À : hamlogger@groups.io
Objet : Re: [hamlogger] ADI problems

 

You will have to explain this statement: frequency entries moved from e.g. 14.015000 into 14015000

 

When you import an ADIF file, the file is opened read only. No information is modified in the file. So, I'm obviously not understanding what you're saying. 73.

On 01/22/2021 3:44 AM PETER DOUGHTY via groups.io < g3tkk@...> wrote:

 

 

I am in the middle of moving my station software from one PC to another

and have run into ADI/BAD.adi problems.

 

I have a good .ADI backup of my logbook but when I load it into the new

Logger software ( ver 3,50,424 ) I get a massive Bad.adi file with many

( scores and scores) frequency entries moved from e.g. 14.015000 into

14015000 or even 14.015.000000.

 

I have done this many times and have not had this go wrong.

 

Please can I have some advice as what I can do to stop this happening.

 

 

Thanks

 

 

Peter  G3TKK

 

 

 


Garanti sans virus. www.avast.com

2481 - 2500 of 84599