Date   

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

gerdslogger
 

Am 08.11.2019 um 18:49 schrieb Bob:
Gerd. Open the HAMqth window. Click the TRANSFER menu. FIELDS TO TRANSFER ON CLICK. Check the fields you want to copy from HAMqth to your logbook. Again, click the TRANSFER menu. Check the menu option TRANSFER FIELDS ON AUTOLOOKUP. Now does the UPDATE QSO option work?

About the DX Spot, I can not answer your question. I do not use DX Clusters so I don't know if it works or not. Several Beta testers have used the feature with no complaints.

73.

Hello Bob,
I have two questions for this news ... first to update for logged qso ...
I go to the call where I have no data .. click on it, it changes to yellow color, in lookup hamqth the little windows of "update QSO" changed from red to green ... I click on update, it goes to red, but nothing is happen in the logbook page .. its still emty, no name, qth etc ... have I missed something to apply???
next to spot ... make a qso, if its ready, in the event viewer comes up the "spot", if I click on it,
DL1BBO de VE7CC-1 08-Nov-2019 1213Z CCC >
DX 14074 VA3CTX FT8 -10dB from EN93 2254Hz ... see this in the telnet window .. but nothing comes up
in the DX Spot window ( the normal dx spot, right click in the Log Entry Window works ok)
Thanks for ur help, 73 de gerd, dl1bbo

Thank you Bob, now the updates works .. 73 de gerd, dl1bbo


Re: where Logger32 keeps the logs?

Bob
 

Alex, I am not sure what you mean by LoTW-paper QSL progress. The three files contain all QSL status flags - QSOs marked to send a QSL, QSOs with QSLs sent, QSOs with QSL received (by QSL I mean paper, LoTW and eQSL). Also, these three files contain all award statistics - submitted and granted. 73.

On November 8, 2019 at 1:18 PM Alex Malyava - K2BB <alex.k2bb@...> wrote:

Thanks Bob,
sounds like a plan. 
another question - are you sure that lotw-paper qsl progress is in those 3 files as well?
I have no problem importing my log from the lotw, but I will have to go through all of those paper cards and entering them again :)

thanks,
Alex K2BB

On Fri, Nov 8, 2019 at 12:13 PM Bob < k4cy@...> wrote:
Alex the logbook database name and location is not fixed. The same with any backups you have made in the past. Here's the plan ... Open the file called Logger32.INI in the \Logger32 directory. It is a textfile, so open it with NotePad. Search for a line that starts with  Logbook Path= In my INI the complete line is  Logbook Path=Logbook Path=Logbook to use=TEST  I now know my logbook is in the C:\Logger32\LOGS\ directory. Now to find the name of the logbook. Search the INI for a line that starts with Logbook to use=  In my INI the full line is Logbook to use=TEST I now know the Logbook name and path is C:\Logger32\LOGS\TEST ... Now were having fun ... I you look in the path name (in my case C:\Logger32\LOGS\) you will find 20+ files with names that start with your logbook name (in my example TEST). You are only interested in three if them <your logbook name>.ISD, <your logbook name>.ISF, and <your logbook name>.ISM. That is your logbook. Everything else can be recreated from those three files. SeventyThree(s).
On November 8, 2019 at 11:27 AM Alex Malyava - K2BB < alex.k2bb@...> wrote:

Hi all,
my SSD drive have failed... it is not recognized as properly functional disk drive, but still can be recovered on the file level utilizing special software.

I copied whole X:\Logger32 folder to my main C drive, but the Q's I see there are 3 years old, as of the moment I copied them from another machine.

What am I missing?
Is there any other location with log database? Maybe some \\AppData whatever?

Thanks,
Alex K2BB

PS - and yes, I will do backups from now on :)

 

 

 


 


Re: where Logger32 keeps the logs?

Alex Malyava - K2BB
 

never mind, all the stats were recovered.
I found what was the root cause of the problem.
I have disk C with 3-years old copy of Logger 32.
I have recovered Logger32 folder for X drive into some E:\Logger32 folder and ran the logger from there, but the config values are still pointing to the C:\Logger32 version which is outdated.
Repointed it to the right folder and everything is there !!!
Wow, I feel good :)

On Fri, Nov 8, 2019 at 1:18 PM Alex Malyava <alex.k2bb@...> wrote:
Thanks Bob,
sounds like a plan. 
another question - are you sure that lotw-paper qsl progress is in those 3 files as well?
I have no problem importing my log from the lotw, but I will have to go through all of those paper cards and entering them again :)

thanks,
Alex K2BB

On Fri, Nov 8, 2019 at 12:13 PM Bob <k4cy@...> wrote:
Alex the logbook database name and location is not fixed. The same with any backups you have made in the past. Here's the plan ... Open the file called Logger32.INI in the \Logger32 directory. It is a textfile, so open it with NotePad. Search for a line that starts with  Logbook Path= In my INI the complete line is  Logbook Path=Logbook Path=Logbook to use=TEST  I now know my logbook is in the C:\Logger32\LOGS\ directory. Now to find the name of the logbook. Search the INI for a line that starts with Logbook to use=  In my INI the full line is Logbook to use=TEST I now know the Logbook name and path is C:\Logger32\LOGS\TEST ... Now were having fun ... I you look in the path name (in my case C:\Logger32\LOGS\) you will find 20+ files with names that start with your logbook name (in my example TEST). You are only interested in three if them <your logbook name>.ISD, <your logbook name>.ISF, and <your logbook name>.ISM. That is your logbook. Everything else can be recreated from those three files. SeventyThree(s).
On November 8, 2019 at 11:27 AM Alex Malyava - K2BB <alex.k2bb@...> wrote:

Hi all,
my SSD drive have failed... it is not recognized as properly functional disk drive, but still can be recovered on the file level utilizing special software.

I copied whole X:\Logger32 folder to my main C drive, but the Q's I see there are 3 years old, as of the moment I copied them from another machine.

What am I missing?
Is there any other location with log database? Maybe some \\AppData whatever?

Thanks,
Alex K2BB

PS - and yes, I will do backups from now on :)

 


Re: where Logger32 keeps the logs?

Alex Malyava - K2BB
 

Thanks Bob,
sounds like a plan. 
another question - are you sure that lotw-paper qsl progress is in those 3 files as well?
I have no problem importing my log from the lotw, but I will have to go through all of those paper cards and entering them again :)

thanks,
Alex K2BB

On Fri, Nov 8, 2019 at 12:13 PM Bob <k4cy@...> wrote:
Alex the logbook database name and location is not fixed. The same with any backups you have made in the past. Here's the plan ... Open the file called Logger32.INI in the \Logger32 directory. It is a textfile, so open it with NotePad. Search for a line that starts with  Logbook Path= In my INI the complete line is  Logbook Path=Logbook Path=Logbook to use=TEST  I now know my logbook is in the C:\Logger32\LOGS\ directory. Now to find the name of the logbook. Search the INI for a line that starts with Logbook to use=  In my INI the full line is Logbook to use=TEST I now know the Logbook name and path is C:\Logger32\LOGS\TEST ... Now were having fun ... I you look in the path name (in my case C:\Logger32\LOGS\) you will find 20+ files with names that start with your logbook name (in my example TEST). You are only interested in three if them <your logbook name>.ISD, <your logbook name>.ISF, and <your logbook name>.ISM. That is your logbook. Everything else can be recreated from those three files. SeventyThree(s).
On November 8, 2019 at 11:27 AM Alex Malyava - K2BB <alex.k2bb@...> wrote:

Hi all,
my SSD drive have failed... it is not recognized as properly functional disk drive, but still can be recovered on the file level utilizing special software.

I copied whole X:\Logger32 folder to my main C drive, but the Q's I see there are 3 years old, as of the moment I copied them from another machine.

What am I missing?
Is there any other location with log database? Maybe some \\AppData whatever?

Thanks,
Alex K2BB

PS - and yes, I will do backups from now on :)

 


Re: Run Time Error 7 Out of Memory

Bob
 

Jim, what URL did you use? Let me take a peek. 73.

On November 8, 2019 at 12:33 PM Jim Ciurczak <nfjimc@...> wrote:

Hi Bob. I was trying the non Club Log download. I did try the Clun Log one and it loaded just fine.

73 and thanks!

Jim K2QB

 


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

Bob
 

Gerd. Open the HAMqth window. Click the TRANSFER menu. FIELDS TO TRANSFER ON CLICK. Check the fields you want to copy from HAMqth to your logbook. Again, click the TRANSFER menu. Check the menu option TRANSFER FIELDS ON AUTOLOOKUP. Now does the UPDATE QSO option work?

About the DX Spot, I can not answer your question. I do not use DX Clusters so I don't know if it works or not. Several Beta testers have used the feature with no complaints.

73.

Hello Bob,
I have two questions for this news ... first to update for logged qso ...
I go to the call where I have no data .. click on it, it changes to yellow color, in lookup hamqth the little windows of "update QSO" changed from red to green ... I click on update, it goes to red, but nothing is happen in the logbook page .. its still emty, no name, qth etc ... have I missed something to apply???
next to spot ... make a qso, if its ready, in the event viewer comes up the "spot", if I click on it,
DL1BBO de VE7CC-1 08-Nov-2019 1213Z CCC >
DX 14074 VA3CTX FT8 -10dB from EN93 2254Hz ... see this in the telnet window .. but nothing comes up
in the DX Spot window ( the normal dx spot, right click in the Log Entry Window works ok)
Thanks for ur help, 73 de gerd, dl1bbo


Re: Run Time Error 7 Out of Memory

Jim K2QB
 

Hi Bob. I was trying the non Club Log download. I did try the Clun Log one and it loaded just fine.

73 and thanks!

Jim K2QB


Re: where Logger32 keeps the logs?

Bob
 

Alex the logbook database name and location is not fixed. The same with any backups you have made in the past. Here's the plan ... Open the file called Logger32.INI in the \Logger32 directory. It is a textfile, so open it with NotePad. Search for a line that starts with  Logbook Path= In my INI the complete line is  Logbook Path=Logbook Path=Logbook to use=TEST  I now know my logbook is in the C:\Logger32\LOGS\ directory. Now to find the name of the logbook. Search the INI for a line that starts with Logbook to use=  In my INI the full line is Logbook to use=TEST I now know the Logbook name and path is C:\Logger32\LOGS\TEST ... Now were having fun ... I you look in the path name (in my case C:\Logger32\LOGS\) you will find 20+ files with names that start with your logbook name (in my example TEST). You are only interested in three if them <your logbook name>.ISD, <your logbook name>.ISF, and <your logbook name>.ISM. That is your logbook. Everything else can be recreated from those three files. SeventyThree(s).

On November 8, 2019 at 11:27 AM Alex Malyava - K2BB <alex.k2bb@...> wrote:

Hi all,
my SSD drive have failed... it is not recognized as properly functional disk drive, but still can be recovered on the file level utilizing special software.

I copied whole X:\Logger32 folder to my main C drive, but the Q's I see there are 3 years old, as of the moment I copied them from another machine.

What am I missing?
Is there any other location with log database? Maybe some \\AppData whatever?

Thanks,
Alex K2BB

PS - and yes, I will do backups from now on :)

 


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

gerdslogger
 

Am 04.11.2019 um 22:07 schrieb 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

 

Hello Bob,

I have two  questions for this news ... first to update for logged qso ...

I go to the call where I have no data .. click on it, it changes to yellow color, in lookup hamqth the little windows of "update QSO" changed from red to green ... I click on update, it goes to red, but nothing is happen in the logbook page .. its still emty, no name, qth etc ... have I missed something to apply???

next to spot ... make a qso, if its ready, in the event viewer comes up the "spot", if I click on it,

DL1BBO de VE7CC-1 08-Nov-2019 1213Z   CCC >
DX 14074 VA3CTX FT8 -10dB from EN93 2254Hz ... see this in the telnet window .. but nothing comes up

in the DX Spot window ( the normal dx spot, right click in the Log Entry Window works ok)

Thanks for ur help, 73 de gerd, dl1bbo


where Logger32 keeps the logs?

Alex Malyava - K2BB
 

Hi all,
my SSD drive have failed... it is not recognized as properly functional disk drive, but still can be recovered on the file level utilizing special software.

I copied whole X:\Logger32 folder to my main C drive, but the Q's I see there are 3 years old, as of the moment I copied them from another machine.

What am I missing?
Is there any other location with log database? Maybe some \\AppData whatever?

Thanks,
Alex K2BB

PS - and yes, I will do backups from now on :)


Re: Run Time Error 7 Out of Memory

Bob
 

Which of the two options are you trying to download the file. I just tested the Club Log file, and it works as expected. Typically the problem is not actually lack of memory but recursive code (a procedure that calls itself again and again in a loop) that eventually consumes all the memory. SeventyThree(s).

SeventyThree(s).

On November 8, 2019 at 10:45 AM Jim Ciurczak <nfjimc@...> wrote:

Trying to download the LoTW User file and receiving the above error. Memory should not be an issue. Running the latest version of Logger32, Windows 10 64 bit with 8G of RAM. I show only 38% being used at the time.

Jim K2QB

 


Run Time Error 7 Out of Memory

Jim K2QB
 

Trying to download the LoTW User file and receiving the above error. Memory should not be an issue. Running the latest version of Logger32, Windows 10 64 bit with 8G of RAM. I show only 38% being used at the time.

Jim K2QB


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

Bob
 

Jerzey, there are two steps. Using the Microsoft Inet control I make a request to HAMQth for the data ... like this

Text11 = callsign to lookup
LookupURL = "http://hamqth.com/adif.php?u=K4CY&p=Password&callsign=CALLSIGN&prg=LOGGER32"

Inet.Execute Replace(LookupURL, "=CALLSIGN", "=" & Text11, 1, -1, 1), "GET"

Then I wait for a reply

Private Sub Inet_StateChanged(ByVal State As Integer)   
    Select Case State
        ' ... Other cases not shown.
        Case icResponseCompleted     ' 12
            strdata = Inet.GetChunk(2048, icString)
            If Len(strdata) > 0 Then
                allDoneInetLookup strdata
            End If
        Case Else
    End Select
End Sub

Strdata is ADIF format text, and the allDoneInetLookup process puts the different fields in the correct place.

Then next of code makes the Update QSO menu visible.... If the Inet execute was initiated by clicking on the Logbook Page, and the lookup was successful, then the menu is visible and clicking on it updates the logbook from data received from HAMQth. If the Inet.executed is initiated from the Logbook Entry Window then the Update QSO menu is not visible.

So, nothing is custom coded for HAMQth. I can make a query from any service and if the reply is ADI format, everything will be populated automatically.

73. 


On November 7, 2019 at 2:39 PM Jerzy Smietanski SP9AUV <sp9auv@...> wrote:

Hello Bob !
Sorry for trouble .
In my lookup named BUREAU_ALL_QRZ_COM_FI.exe I received i.e. field  <APP_QSO_UPDATE :6>SP9CXN>  <EOR>
and download personal data from QRZ or others servers .

But can you answer me to what handler address sendmessage
as in the  sendmessage(Logger32TextBoxhWnd,WM_SetText,0,longint(ADIF_SendString))  for window OPERATOR .
when press UpdateQSO in your HAMQTH ADIF Lookup .
I suppose this is a different handler than the one used for the OPERATOR window . Describe me what method must use to obtain
proper handler .
I ' m try get handler for windows    "Loggbok Page "   by use Logger32LoggbokPageHWnd:= FindWindow('', 'Logbook Page');
but this handler is equal = 0 .
Or you use another method to send to line actually choiced AdifString  by left mouse and display in a a yellow color .
                  
                  Best regards de Jerzy SP9AUV

W dniu 2019-11-05 o 16:44, SP9AUV pisze:
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

 




 


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

Jerzy Smietanski SP9AUV
 

Hello Bob !
Sorry for trouble .
In my lookup named BUREAU_ALL_QRZ_COM_FI.exe I received i.e. field  <APP_QSO_UPDATE :6>SP9CXN>  <EOR>
and download personal data from QRZ or others servers .

But can you answer me to what handler address sendmessage
as in the  sendmessage(Logger32TextBoxhWnd,WM_SetText,0,longint(ADIF_SendString))  for window OPERATOR .
when press UpdateQSO in your HAMQTH ADIF Lookup .
I suppose this is a different handler than the one used for the OPERATOR window . Describe me what method must use to obtain
proper handler .
I ' m try get handler for windows    "Loggbok Page "   by use Logger32LoggbokPageHWnd:= FindWindow('', 'Logbook Page');
but this handler is equal = 0 .
Or you use another method to send to line actually choiced AdifString  by left mouse and display in a a yellow color .
                  
                  Best regards de Jerzy SP9AUV

W dniu 2019-11-05 o 16:44, SP9AUV pisze:

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

 




Re: UDP listening from a different PC.

Bob
 

Probably not. In Logger32 the IP address of the UDP and TCP sockets are fixed at 127.0.0.1 (the localhost of that PC). There may be software available that allows you to fake virtual localhost address on a different PC, but I don't know. SeventyThree(s)

On November 7, 2019 at 11:39 AM ik2rls@... wrote:

Hello, maybe  a new topic/question.

I manage a separate radio (IC7300) for FT8 traffic from my main one (IC7610) used for CW-RTTY-SSB.
I have a main PC laptop connected to 7610, where Logger32 is running.
I have available a second laptop where I would like to install separately WSJT, of course connected to the 7300.
The two laptops are in a same domestic network, they can see each other.

Question: is it possible to make Logger32 on first laptop UDP/TCP listen to WSJT on the second one?

Thanks in advance!

Saverio IK2RLS, Milan Italy


 


IC-7300 Split.

Dave Colliau
 

Crummy day here in Michigan and I was working on the RCP for the 7300 and I noticed when I go to split the split indicator in the RCP and the call entry window keeps flashing and I cant do anything else within Logger 32 till I turn off the split.  This also does this when split is invoked from the split button on the rig. I changed the polling time and it makes it blink on and off slower or faster I suspect the program and the rig are polling each other in split mode and when the split is off everything else as far as CI-V commands from the RCP are fine .
Any ideas...
Dave N8DC


UDP listening from a different PC.

ik2rls@...
 

Hello, maybe  a new topic/question.

I manage a separate radio (IC7300) for FT8 traffic from my main one (IC7610) used for CW-RTTY-SSB.
I have a main PC laptop connected to 7610, where Logger32 is running.
I have available a second laptop where I would like to install separately WSJT, of course connected to the 7300.
The two laptops are in a same domestic network, they can see each other.

Question: is it possible to make Logger32 on first laptop UDP/TCP listen to WSJT on the second one?

Thanks in advance!

Saverio IK2RLS, Milan Italy


RCP for Yaesu FTDX-101MP or FTDX-101D

John Owens
 

I am hopeful to find someone who has developed a Radio Control Panel for the fairly new Yaesu FTDX-101MP or FTDX-101D. I have one for the FTDX5000, but it doesn't work for the newer rigs. Any help would be greatly appreciated. At nearly 82YO, it is beyond my abilities to learn the code and how to construct one. 

Thanks

John Owens - N7TK
 



Re: Settings for Rotor, Logger32

Jim Hargrave
 

Steph, I think you have finally told us your basic setup.

 

Please verify that I understand your Rotor setup.

 

LOGGER32  <> Remoterig <> Internet <> Remoterig <> ERG <> Rotor (G450c)

¨       Radio <> Antenna

Am I correct so far?        

Jim – w5ifp-

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Bob
Sent: Thursday, November 7, 2019 4:56 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Settings for Rotor, Logger32

 

 

I have no idea what remoterig is (I Googled it; but it still makes no sense to me). All I can suggest is that next time you escape the big city you try a direct Logger32 to ERC connection and see how that works. 73.

 

On November 6, 2019 at 11:01 PM "Steph, F5NZY" <f5nzy@...> wrote:

Hi Bob,

 

You’re right (I’ve read too fast), there’s no Yaesu G-450C, but Yaesu GS232A and Yaesu GS232B, there’s also GS232B A AZ/AZ A and GS232B AZ/AZ B

 

I tried all the Rotor type, including External.

 

You’re right, Yaesu G-450C has not a serial port. I use a ERC Interface who permits me to control the Rotor thru HRD_ROTATOR.

 

But, what I would like now, is when I type a call sign into L32, the antenna moves to the right path.

 

73 de Steph, F5NZY

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Bob
Envoyé : mercredi 6 novembre 2019 20:54
À : hamlogger@groups.io
Objet : Re: [hamlogger] Settings for Rotor, Logger32

 

Steph, I am confused (It is easy to do). You said this:  My rotor is a Yaesu G-450C, in the Help files, I can read, this rotor is not supported, but in this case, why is it in the Rotor type list? I double checked the list of rotors supported by Logger32, I don't see Yaesu G-450C on the list. Then I Googled Yaesu G-450C and the information I found indicates it does not have a serial port interface built in. Steph, then you say you use HRD_ROTATOR and remoterig. Is HRD_ROTATOR from Ham Radio Deluxe? If so, and it works, why are you messing around with Logger32? 

 

Steph, You have configured Logger32 for a GS232B AZ/AZ B rotor. I don't know what RS-232 interface device you are using, but I suspect is uses the GS232B protocol and not the GS232B AZ/AZ protocol. Try changing the rotor type in Logger32. SeventyThree(s).

On November 6, 2019 at 12:48 PM "Steph, F5NZY" <f5nzy@...> wrote:

Hello Jim,

 

  1. Already checked, this Is the good port
  2. 9600 Is the correct baud rate
  3. Already tried, no more success

 

But…

 

My rotor is a Yaesu G-450C, in the Help files, I can read, this rotor is not supported, but in this case, why is it in the Rotor type list?

 

Also, I use a remoterig and from Home for the rotor, I use HRD_ROTATOR, with GS232B AZ, but I can’t configure it in my L32 from Paris, probably because G-450C is not supported…

 

73 de Steph, F5NZY

 

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Jim Hargrave
Envoyé : mercredi 6 novembre 2019 17:57
À : hamlogger@groups.io
Objet : Re: [hamlogger] Settings for Rotor, Logger32

 

Steph,

Your setup looks normal.

I’m not familiar with the GS232B settings, but can offer some things to look at:

  1. Make sure Windows has assigned the rotor to the right Com port (See Device manager)
  2. Verify that 9600 is the correct baud rate for the rotor.
  3. Try setting DTR/RTS High.

 

Jim – w5ifp-

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Steph, F5NZY
Sent: Wednesday, November 6, 2019 8:39 AM
To: hamlogger@groups.io
Subject: [hamlogger] Settings for Rotor, Logger32

 

Hi all,

I don’t know why it does not work?

Enclosed pictures of my setup.

73 de Steph, F5NZY

<<...>> <<...>> <<...>>

 

 


 

 

 


 


Re: Settings for Rotor, Logger32

Bob
 


I have no idea what remoterig is (I Googled it; but it still makes no sense to me). All I can suggest is that next time you escape the big city you try a direct Logger32 to ERC connection and see how that works. 73.

On November 6, 2019 at 11:01 PM "Steph, F5NZY" <f5nzy@...> wrote:

Hi Bob,

 

You’re right (I’ve read too fast), there’s no Yaesu G-450C, but Yaesu GS232A and Yaesu GS232B, there’s also GS232B A AZ/AZ A and GS232B AZ/AZ B

 

I tried all the Rotor type, including External.

 

You’re right, Yaesu G-450C has not a serial port. I use a ERC Interface who permits me to control the Rotor thru HRD_ROTATOR.

 

But, what I would like now, is when I type a call sign into L32, the antenna moves to the right path.

 

73 de Steph, F5NZY

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Bob
Envoyé : mercredi 6 novembre 2019 20:54
À : hamlogger@groups.io
Objet : Re: [hamlogger] Settings for Rotor, Logger32

 

Steph, I am confused (It is easy to do). You said this:  My rotor is a Yaesu G-450C, in the Help files, I can read, this rotor is not supported, but in this case, why is it in the Rotor type list? I double checked the list of rotors supported by Logger32, I don't see Yaesu G-450C on the list. Then I Googled Yaesu G-450C and the information I found indicates it does not have a serial port interface built in. Steph, then you say you use HRD_ROTATOR and remoterig. Is HRD_ROTATOR from Ham Radio Deluxe? If so, and it works, why are you messing around with Logger32? 



Steph, You have configured Logger32 for a GS232B AZ/AZ B rotor. I don't know what RS-232 interface device you are using, but I suspect is uses the GS232B protocol and not the GS232B AZ/AZ protocol. Try changing the rotor type in Logger32. SeventyThree(s).

On November 6, 2019 at 12:48 PM "Steph, F5NZY" <f5nzy@...> wrote:

Hello Jim,

 

  1. Already checked, this Is the good port
  2. 9600 Is the correct baud rate
  3. Already tried, no more success

 

But…

 

My rotor is a Yaesu G-450C, in the Help files, I can read, this rotor is not supported, but in this case, why is it in the Rotor type list?

 

Also, I use a remoterig and from Home for the rotor, I use HRD_ROTATOR, with GS232B AZ, but I can’t configure it in my L32 from Paris, probably because G-450C is not supported…

 

73 de Steph, F5NZY

 

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Jim Hargrave
Envoyé : mercredi 6 novembre 2019 17:57
À : hamlogger@groups.io
Objet : Re: [hamlogger] Settings for Rotor, Logger32

 

Steph,

Your setup looks normal.

I’m not familiar with the GS232B settings, but can offer some things to look at:

  1. Make sure Windows has assigned the rotor to the right Com port (See Device manager)
  2. Verify that 9600 is the correct baud rate for the rotor.
  3. Try setting DTR/RTS High.

 

Jim – w5ifp-

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Steph, F5NZY
Sent: Wednesday, November 6, 2019 8:39 AM
To: hamlogger@groups.io
Subject: [hamlogger] Settings for Rotor, Logger32

 

Hi all,

I don’t know why it does not work?

Enclosed pictures of my setup.

73 de Steph, F5NZY

<<...>> <<...>> <<...>>

 

 


 

 



 

8241 - 8260 of 86253