Date   

Re: Odd one with rotator

Steve G1XOW
 

No worries Gary. The version is 4.0.248 btw.

 

Get yourself on 80M SSB and we can both work without a rotator !!

 

73 Steve G1XOW

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Gary Hinson
Sent: 24 March 2021 19:51
To: hamlogger@groups.io
Subject: Re: [hamlogger] Odd one with rotator

 

Hi Steve.

 

Tnx info.

 

I’m pretty sure someone else reported something very similar with the rotator heading to 0 degrees recently, so it smells like a bug.  Unfortunately, my rotators are old and manual, like me, so I can’t do much fault-finding, but others on the beta crew can.

 

Bob is stacked-up dealing with a flurry of error-trapped-bugs at the moment, with a new update due out soon plus, hopefully, the final production version of the v4 full installer before long.

 

I’ll pass your message (and the other one, if I can find it) to Bob and the beta crew anyway. 

 

Please be patient chaps.  Meanwhile, listen out for DX stations due North … such as me, long path on the Far Side 😊

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Steve G1XOW
Sent: 25 March 2021 07:02
To: hamlogger@groups.io
Subject: [hamlogger] Odd one with rotator

 

Hi All,

 

Have been using L32 for a few years now and just spotted something odd. I don’t think this used to happen but cannot be 100% certain.

 

For example, when I click on a DX spot (e.g. ZF2PG) the popup rip tells me 274 degrees and instructs the rotator to move. However, it’s sending “AP1000” to the rotator instead of the correct bearing. This result in the controller receiving the desired heading of zero and thus it turns CW to 360 degrees.

 

I have noticed this a few times where it was supposed to be 55 degrees but it also went to 360 CW.

 

To complicate matters, if I click on the correct place on the DX spot map it always goes to the right bearing.

 

The controller is a uHam station master which is emulating a Hygain DCU-1 protocol). See debug image attached.

 

To double check I have confirmed the behaviour is normal and correct when used with PSTrotator instead of L32.

 

Any ideas?

 

73 de Steve G1XOW

 


"db BUSY" error?

Ken Lemke
 

(If this a dupe, I apologize..) Anyway, I got a warning when I tried to flag a couple of QSOs for upload to eQSL and LoTW...."I am about to reset complex keys in database...db Busy flag is set to false..." I get the same when I attempt to add county info to the logbook entry. I looked at the ADIF file, and it seems that the problematic QSO entries have a highly truncated data set...barely half the data. Also, logger32 wont let me automatically upload to eQSL and LoTW now. Running 3.5xxx, havent uploaded 4 yet. I Cant figure how to clear this...HELP!


Re: Odd one with rotator

Gary Hinson
 

Hi Steve.

 

Tnx info.

 

I’m pretty sure someone else reported something very similar with the rotator heading to 0 degrees recently, so it smells like a bug.  Unfortunately, my rotators are old and manual, like me, so I can’t do much fault-finding, but others on the beta crew can.

 

Bob is stacked-up dealing with a flurry of error-trapped-bugs at the moment, with a new update due out soon plus, hopefully, the final production version of the v4 full installer before long.

 

I’ll pass your message (and the other one, if I can find it) to Bob and the beta crew anyway. 

 

Please be patient chaps.  Meanwhile, listen out for DX stations due North … such as me, long path on the Far Side 😊

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Steve G1XOW
Sent: 25 March 2021 07:02
To: hamlogger@groups.io
Subject: [hamlogger] Odd one with rotator

 

Hi All,

 

Have been using L32 for a few years now and just spotted something odd. I don’t think this used to happen but cannot be 100% certain.

 

For example, when I click on a DX spot (e.g. ZF2PG) the popup rip tells me 274 degrees and instructs the rotator to move. However, it’s sending “AP1000” to the rotator instead of the correct bearing. This result in the controller receiving the desired heading of zero and thus it turns CW to 360 degrees.

 

I have noticed this a few times where it was supposed to be 55 degrees but it also went to 360 CW.

 

To complicate matters, if I click on the correct place on the DX spot map it always goes to the right bearing.

 

The controller is a uHam station master which is emulating a Hygain DCU-1 protocol). See debug image attached.

 

To double check I have confirmed the behaviour is normal and correct when used with PSTrotator instead of L32.

 

Any ideas?

 

73 de Steve G1XOW

 


Odd one with rotator

Steve G1XOW
 

Hi All,

 

Have been using L32 for a few years now and just spotted something odd. I don’t think this used to happen but cannot be 100% certain.

 

For example, when I click on a DX spot (e.g. ZF2PG) the popup rip tells me 274 degrees and instructs the rotator to move. However, it’s sending “AP1000” to the rotator instead of the correct bearing. This result in the controller receiving the desired heading of zero and thus it turns CW to 360 degrees.

 

I have noticed this a few times where it was supposed to be 55 degrees but it also went to 360 CW.

 

To complicate matters, if I click on the correct place on the DX spot map it always goes to the right bearing.

 

The controller is a uHam station master which is emulating a Hygain DCU-1 protocol). See debug image attached.

 

To double check I have confirmed the behaviour is normal and correct when used with PSTrotator instead of L32.

 

Any ideas?

 

73 de Steve G1XOW

 


Re: Bandmap callsigns on WSJT-X not transferring to L32 Input Window

Gary Hinson
 

Hi Jerry.

 

OK, please [double] check your setups in both WSJT-X and Logger32 using chapter 15 of the Logger32 v4 User Manual

 

Here’s how the ‘manual calling’ sequence works, as I understand it:

  • WSJT-X receives and decodes messages, broadcasting the decoded messages to other programs via UDP using a specific UDP port
  • Logger32 receives the decodes via UDP on the specific UDP port, analyses them (e.g. for new ones and LoTW users) and displays them accordingly on the UDP BandMap
  • If you click an interesting callsign on the band map, a box soon appears around it …
  • … When Logger32 sees a decoded message indicating the interesting station is nearly finished or has finished a QSO, it sends the decoded message back to WSJT-X via UDP
  • WSJT-X receives the decode via UDP, populates the callsign field, composes the usual set of TX messages, and starts calling him
  • If the QSO completes, WSJT-X pops up the “Log QSO” form
  • Logger32 effectively clicks the “Log” button for you
  • WSJT-X broadcasts the logged QSO via UDP
  • Logger32 receives the logged QSO via UDP
  • Logger32 logs the QSO, optionally adding additional info from previous QSOs or online lookups

 

With the manual calling debug screen open (from the UDP BandMap menu), you should be able to see the sequence unfold – key steps at least.

 

You might also try using JTDX instead of WSJT-X.  JTDX works much the same, except it does not pop up the “Log QSO” form for Logger32 to click – provided it is set up to auto-log. 

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Jerry Spring
Sent: 25 March 2021 04:10
To: hamlogger@groups.io
Subject: Re: [hamlogger] Bandmap callsigns on WSJT-X not transferring to L32 Input Window

 

I turned off “Clear call sign on QSY > 1 KHz” and that did not solve the problem. I also noted that L32 no longer automatically logs the QSO, as it did before (the option is still selected).  I take it the two are connected. 


Jerry


Re: Bandmap callsigns on WSJT-X not transferring to L32 Input Window

Jerry Spring
 

I turned off “Clear call sign on QSY > 1 KHz” and that did not solve the problem. I also noted that L32 no longer automatically logs the QSO, as it did before (the option is still selected).  I take it the two are connected. 


Jerry


Re: CW mode control for Flex 6600

K8pk@...
 

Paul, had the same problem with my 6600.  Fixed it by changing radio to Kenwood, 38400 baudrate, 8 databits, 1 stop stopbit, no parity.  Com port connected to Slice A in SmartSDR CAT. Good luck!

Peter K8PK 


Expert Electronics TCI protocol?

Steve G1XOW
 

 

At some point will Logger32 support the new TCI (transceiver control interface) that Expert/SunSDR developed?

 

TCI is a large step forward in CAT interfacing that has otherwise been stagnant for some 25 years. I see JTDX already supports it and a few other loggers: LogHX, SWISSLOG, RUMlog etc. I gather that Log4om is also on the way.

 

73 de Steve G1XOW

 

 


Re: Bandmap callsigns on WSJT-X not transferring to L32 Input Window

Gary Hinson
 

Hi Jerry.

 

We are currently beta testing a change that stops Logger32 erasing callsigns from the log entry pane when the UDP BandMap is open … since we normally operate split in FT8, and splits above 1 kHz were tripping the “Clear callsign on QSY > 1kHz setting” for those using it.

 

There are other changes & bug-fixes in the works, so it may take a wee while to complete the testing and release the next version.

 

I just hope it will cure your issue.

 

73

Gary  ZL2iFB

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Jerry Spring
Sent: 24 March 2021 17:04
To: hamlogger@groups.io
Subject: [hamlogger] Bandmap callsigns on WSJT-X not transferring to L32 Input Window

 

[Edited Message Follows]

I just upgraded from V3.5 to V4.0 and everything seemed to go perfectly.  Except that I can no longer double click on a callsign in the WSJT-X bandmap window and have it transferred to the Input "Call" field in L32.  The only field that does transfer is the Grid square.  So the UDP link is working.  I have the UDP server set to 127.0.0.1 in WSJT-X  with port 2238.  These are the same settings I see at the bottom of L32, when I hover over UDP.  What am I missing?  I also tried setting the port on both to 2237, with identical results. 

Thanks,

Jerry VE6TL


Bandmap callsigns on WSJT-X not transferring to L32 Input Window

Jerry Spring
 
Edited

I just upgraded from V3.5 to V4.0 and everything seemed to go perfectly.  Except that I can no longer double click on a callsign in the WSJT-X bandmap window and have it transferred to the Input "Call" field in L32.  The only field that does transfer is the Grid square.  So the UDP link is working.  I have the UDP server set to 127.0.0.1 in WSJT-X  with port 2238.  These are the same settings I see at the bottom of L32, when I hover over UDP.  What am I missing?  I also tried setting the port on both to 2237, with identical results. 

Thanks,

Jerry VE6TL


Re: Data transfer to Logger32

Gary Hinson
 

Section 15.4 of the Logger32 v4 User Manual explains the setup, with pictures.

https://www.logger32.net/files/Logger32_v4_User_Manual.pdf

73
Gary ZL2iFB

-----Original Message-----
From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Andy M0NKR via groups.io
Sent: 24 March 2021 04:14
To: hamlogger@groups.io
Subject: Re: [hamlogger] Data transfer to Logger32

What are they in Jtdx?

They need to match logger32 or vice-versa

Andy
M0NKR
On 23 Mar 2021, at 15:08, KE1F Lou <lmecseri@cfl.rr.com> wrote:

I have the following numbers

TCP server 127.0.0.1

ICP Port 52001

and

2nd UDP 127.0.0.1

UDP port 2333

what are the "correct" numbers?

Lou, KE1F

On 3/23/2021 10:51 AM, Andy M0NKR via groups.io wrote:
Make sure the UDP or TCP port addresses are correct.

73
Andy
M0NKR
On 23 Mar 2021, at 14:44, KE1F Lou <lmecseri@cfl.rr.com> wrote:
My old computer stopped working so I got a new one with new problems. All the problems are resolved, with the exception of one.

On my old computer, running old Logger 32 when I made a FT8 QSO, miraculously the QSO data was transferred from JTDX to my main logging program Logger32.

Now, I am running the new, Logger32 v. 4. The miraculous transfer is not taking place.

I sure could use some guidance to make this miracle to happen :)

73, Lou KE1F











CW mode control for Flex 6600

Paul Sturpe
 

Selecting a cw frequency as defined under Tools, setup Bands & Modes does not put my Flex 6600 into CW mode.
The Operator window changes to CW mode but the radio doesn't.

I'm running Logger32 version 4.0.248.  Radio is selected as PowerSDR.  All other modes seem to work OK.

Paul, W3GQ


Re: Data transfer to Logger32

KE1F Lou
 

Both programs had to have the same UDP & Port numbers and open port.

Make sense now.

73, Lou KE1F

On 3/23/2021 6:06 PM, Andy M0NKR via groups.io wrote:
What was the fix action?

73
Andy
M0NKR
On 23 Mar 2021, at 22:05, KE1F Lou <lmecseri@cfl.rr.com> wrote:

Thank you to all of you who helped me to get back into ham radio and contesting.

This computer sh.t is real hard on an old timer with poor hearing, eye site etc.

Thanks again and see you guys and girls in the CW, RTTY, FT8 and FT4 bands.

73, Lou KE1F

On 3/23/2021 11:13 AM, Andy M0NKR via groups.io wrote:
What are they in Jtdx?

They need to match logger32 or vice-versa

Andy
M0NKR
On 23 Mar 2021, at 15:08, KE1F Lou <lmecseri@cfl.rr.com> wrote:
I have the following numbers

TCP server 127.0.0.1

ICP Port 52001

and

2nd UDP 127.0.0.1

UDP port 2333

what are the "correct" numbers?

Lou, KE1F

On 3/23/2021 10:51 AM, Andy M0NKR via groups.io wrote:
Make sure the UDP or TCP port addresses are correct.

73
Andy
M0NKR
On 23 Mar 2021, at 14:44, KE1F Lou <lmecseri@cfl.rr.com> wrote:
My old computer stopped working so I got a new one with new problems. All the problems are resolved, with the exception of one.

On my old computer, running old Logger 32 when I made a FT8 QSO, miraculously the QSO data was transferred from JTDX to my main logging program Logger32.

Now, I am running the new, Logger32 v. 4. The miraculous transfer is not taking place.

I sure could use some guidance to make this miracle to happen :)

73, Lou KE1F












A note to Bob

John Scott, VE1JS
 

Hi Bob
Several weeks ago you suggested that I try JTDX again.  I have done so.  Thanks for the suggestion.  It is growing on me; I'm beginning to really like it.

Now, in the Department of Wouldn't it be nice:  It would be  nice if, in the CONFIG drop down of  the UDP band map, the line for the JTDX Control Panel were a check box.  If checked and JTDX is started from within Logger32, the the JTDX Control  Panel would start  automatically and shutdown the same way when JTDX is closed from within Logger32.  If not checked JTDX would just start without the control panel.  I can't see why anyone would want to have the JTDX control panel running without JTDX!

Seventy-three(s).

John, VE1JS


Re: Data transfer to Logger32

Andy M0NKR
 

What was the fix action?

73
Andy
M0NKR

On 23 Mar 2021, at 22:05, KE1F Lou <lmecseri@cfl.rr.com> wrote:

Thank you to all of you who helped me to get back into ham radio and contesting.

This computer sh.t is real hard on an old timer with poor hearing, eye site etc.

Thanks again and see you guys and girls in the CW, RTTY, FT8 and FT4 bands.

73, Lou KE1F

On 3/23/2021 11:13 AM, Andy M0NKR via groups.io wrote:
What are they in Jtdx?

They need to match logger32 or vice-versa

Andy
M0NKR
On 23 Mar 2021, at 15:08, KE1F Lou <lmecseri@cfl.rr.com> wrote:
I have the following numbers

TCP server 127.0.0.1

ICP Port 52001

and

2nd UDP 127.0.0.1

UDP port 2333

what are the "correct" numbers?

Lou, KE1F

On 3/23/2021 10:51 AM, Andy M0NKR via groups.io wrote:
Make sure the UDP or TCP port addresses are correct.

73
Andy
M0NKR
On 23 Mar 2021, at 14:44, KE1F Lou <lmecseri@cfl.rr.com> wrote:
My old computer stopped working so I got a new one with new problems. All the problems are resolved, with the exception of one.

On my old computer, running old Logger 32 when I made a FT8 QSO, miraculously the QSO data was transferred from JTDX to my main logging program Logger32.

Now, I am running the new, Logger32 v. 4. The miraculous transfer is not taking place.

I sure could use some guidance to make this miracle to happen :)

73, Lou KE1F














Re: Data transfer to Logger32

KE1F Lou
 

Thank you to all of you who helped me to get back into ham radio and contesting.

This computer sh.t is real hard on an old timer with poor hearing, eye site etc.

Thanks again and see you guys and girls in the CW, RTTY, FT8 and FT4 bands.

73, Lou KE1F

On 3/23/2021 11:13 AM, Andy M0NKR via groups.io wrote:
What are they in Jtdx?

They need to match logger32 or vice-versa

Andy
M0NKR
On 23 Mar 2021, at 15:08, KE1F Lou <lmecseri@cfl.rr.com> wrote:

I have the following numbers

TCP server 127.0.0.1

ICP Port 52001

and

2nd UDP 127.0.0.1

UDP port 2333

what are the "correct" numbers?

Lou, KE1F

On 3/23/2021 10:51 AM, Andy M0NKR via groups.io wrote:
Make sure the UDP or TCP port addresses are correct.

73
Andy
M0NKR
On 23 Mar 2021, at 14:44, KE1F Lou <lmecseri@cfl.rr.com> wrote:
My old computer stopped working so I got a new one with new problems. All the problems are resolved, with the exception of one.

On my old computer, running old Logger 32 when I made a FT8 QSO, miraculously the QSO data was transferred from JTDX to my main logging program Logger32.

Now, I am running the new, Logger32 v. 4. The miraculous transfer is not taking place.

I sure could use some guidance to make this miracle to happen :)

73, Lou KE1F











A GREAT BIG THANK YOU!!

Peter Whiffing
 

Hi,
I would just like to take this opportunity to thank this group in general for the great support offered during the implementation of Logger32 and Aki’s interface module to QRZ.com.
Also like to thank Rick and a HUGE thank you to Aki’s JA1NLX. Nothing at all was too much trouble, but i am a great believer that issues aid learning; suffice to say that i have learnt lots. 
Today i did an uninstall/reinstall of Logger32, plus Aki’s interface module and all is working so well.
I am now deciding which windows (size, details, colours) serves me best.
I can honestly say that to me this logging program is the best on the market (my opinion anyway), and would like to thank the developers for a very good “all singing, all dancing” piece of software.
Take care and stay safe everyone 👍🏻😊


Re: Data transfer to Logger32

Andy M0NKR
 

Also need to make sure the ports are open in logger32

Right click on the bottom of your screen to open ports on tcp or udp, they will be coloured blue if open and red if closed

Andy
M0NKR

On 23 Mar 2021, at 15:13, Andrew Goldsmith <andrewgoldsmith22@yahoo.co.uk> wrote:

What are they in Jtdx?

They need to match logger32 or vice-versa

Andy
M0NKR

Sent from my iPhone

On 23 Mar 2021, at 15:08, KE1F Lou <lmecseri@cfl.rr.com> wrote:

I have the following numbers

TCP server 127.0.0.1

ICP Port 52001

and

2nd UDP 127.0.0.1

UDP port 2333

what are the "correct" numbers?

Lou, KE1F

On 3/23/2021 10:51 AM, Andy M0NKR via groups.io wrote:
Make sure the UDP or TCP port addresses are correct.

73
Andy
M0NKR
On 23 Mar 2021, at 14:44, KE1F Lou <lmecseri@cfl.rr.com> wrote:
My old computer stopped working so I got a new one with new problems. All the problems are resolved, with the exception of one.

On my old computer, running old Logger 32 when I made a FT8 QSO, miraculously the QSO data was transferred from JTDX to my main logging program Logger32.

Now, I am running the new, Logger32 v. 4. The miraculous transfer is not taking place.

I sure could use some guidance to make this miracle to happen :)

73, Lou KE1F











Re: Data transfer to Logger32

Andy M0NKR
 

What are they in Jtdx?

They need to match logger32 or vice-versa

Andy
M0NKR

On 23 Mar 2021, at 15:08, KE1F Lou <lmecseri@cfl.rr.com> wrote:

I have the following numbers

TCP server 127.0.0.1

ICP Port 52001

and

2nd UDP 127.0.0.1

UDP port 2333

what are the "correct" numbers?

Lou, KE1F

On 3/23/2021 10:51 AM, Andy M0NKR via groups.io wrote:
Make sure the UDP or TCP port addresses are correct.

73
Andy
M0NKR
On 23 Mar 2021, at 14:44, KE1F Lou <lmecseri@cfl.rr.com> wrote:
My old computer stopped working so I got a new one with new problems. All the problems are resolved, with the exception of one.

On my old computer, running old Logger 32 when I made a FT8 QSO, miraculously the QSO data was transferred from JTDX to my main logging program Logger32.

Now, I am running the new, Logger32 v. 4. The miraculous transfer is not taking place.

I sure could use some guidance to make this miracle to happen :)

73, Lou KE1F











Re: Data transfer to Logger32

KE1F Lou
 

I have the following numbers

TCP server 127.0.0.1

ICP Port 52001

and

2nd UDP 127.0.0.1

UDP port 2333

what are the "correct" numbers?

Lou, KE1F

On 3/23/2021 10:51 AM, Andy M0NKR via groups.io wrote:
Make sure the UDP or TCP port addresses are correct.

73
Andy
M0NKR
On 23 Mar 2021, at 14:44, KE1F Lou <lmecseri@cfl.rr.com> wrote:

My old computer stopped working so I got a new one with new problems. All the problems are resolved, with the exception of one.

On my old computer, running old Logger 32 when I made a FT8 QSO, miraculously the QSO data was transferred from JTDX to my main logging program Logger32.

Now, I am running the new, Logger32 v. 4. The miraculous transfer is not taking place.

I sure could use some guidance to make this miracle to happen :)

73, Lou KE1F







2001 - 2020 of 85242