Re: Program loses frequency and a lag on entering callsigns
Jan
Hi Ron
My 7300 shows in the CI-V USB Baud Rate a maximum setting of 115200 which I use with Logger32. You said yours is not going above 19200 but you use 9600. Why not use 19200?? 73 Jan PA4JJ Op 12-9-2020 om 15:30 schreef Ron Stone
via groups.io:
Hi Bob -- ____________________________________________________ my dxspider clusters running on a raspberry pi: pa4jj-2 83.162.186.242 port 7300 pa4jj-3 83.162.186.242 port 7388
|
||
|
||
Re: Program loses frequency and a lag on entering callsigns
Bob
As I don't have an IC-7300, I leave it to those that do to walk you through the settings. 73
|
||
|
||
Re: Program loses frequency and a lag on entering callsigns
Ron Stone
Hi Bob
Not to imply that your program isnt the best there is..... ! I have been using it since 1995 - that's an excellent 25 years - and only recently have I run into problems with it. So do please accept my thanks for it. Freeware and great support ? Not many others like that so you can be very proud of it. Regarding the entry of calls into the logbook entry window, previously instantaneous, so I rolled back to 3.50.394 and hey now the calls go in there fast again. No more lag at all !. Then I uploaded 422 again and now the calls go in just as fast. Surely one for "Go figure...." I have checked the radio settings as you suggest. Not possible in the IC7300 menus to go above 19200 baud so I have left it at 9600 where it was. Putting CI-V transceive to OFF (I had it ON) resulted in no frequency change on VFO movement so I changed it back to ON and it is responding to QSY's again. I have tried playing with all settings of polling times and nothing makes any difference. Used the radio debug window and indeed the frequency went to 0.00 when the prog lost the frequency. I have attached a screen dump of when it happened. So the loss of frequency still happens very often unfortunately. Now hear this.. Tried my W10 laptop and no prob with call entries or frequency. Everything stable. So I suppose the next step - taken reluctantly as I really dont like W10- is to upgrade my W7 machine to W10. I've ordered a large thumb drive to back everything up and then will try again. Others commenting. Thanks but are you using W7 or W10 please ? 73 and thanks again for your help. Stay safe Ron
|
||
|
||
Re: Program loses frequency and a lag on entering callsigns
NICK K. PLUMIDAKIS
Dear Ron Hi. I am using the 7300 as my primary radio with L32 and microKEYER II and is working fantastic. Best 73’s DE Nick SV1VS
From: hamlogger@groups.io
[mailto:hamlogger@groups.io] On Behalf Of ja1nlx
Sent: Saturday, 12 September, 2020 1:03 To: hamlogger@groups.io Subject: Re: [hamlogger] Program loses frequency and a lag on entering callsigns
Sample picture is in the IC-7300 section in Logger32 Help. 73 On 2020/09/12 6:53, Bob wrote:
--
|
||
|
||
Re: Program loses frequency and a lag on entering callsigns
ja1nlx
Sample picture is in the IC-7300 section in Logger32 Help. 73
On 2020/09/12 6:53, Bob wrote:
--
73 de aki JA1NLX
|
||
|
||
Re: Program loses frequency and a lag on entering callsigns
Bob
...but wait. I checked the help file. I see this for IC-7300 menu settings:
Select Set/Connectors and set following items.
ACC/USB Output Select: AF
ACC/USB AF Output Level: 20%
ACC/USB AF SQL: OFF
ACC/USB AF Beep/Speech Output: OFF
USB MOD level: 50%
DATA OFF MOD: MIC
DATA MOD: USB
Select Set/Connectors/CI-V and set following items.
CI-V address: 94h
CI-V Transceive: OFF
CI-V USB->Remote Transceive address: 94h
CI-V Output (for ANT)
: OFF
CI-V USB Port: Unlink from [Remote]
CI-V USB Baud Rate: 115200
CI-V USB Echo Back: ON
I see this for Logger32 settings:
73.
|
||
|
||
Re: Program loses frequency and a lag on entering callsigns
Bob
... and, to make sure your settings are all correct, hopefully someone with an IC7300 will post a picture of their configuration window. 73.
|
||
|
||
Re: Program loses frequency and a lag on entering callsigns
Bob
Ron, my first suggestion is to recommend you use a program that works for you. But, seeing as many thousands of Logger32 users have no problem with CAT control (and hundreds using IC7300s), maybe you'd like to do some experimentation to resolve your problems ...
My SWAG at why the CAT fails periodically is that you have the polling interval too short. Click SETUP | RADIO | RADIO 1 CONFIGURATION. A rhetorical question - What is the polling interval? Add 100ms and try that for a while. If that resolves the problem, reduce it by 25ms. Experiment until you get a reliable configuration. Other than that, you could open the Radio debug window (Right click on the RADIO pane on the bottom status bar, then click SHOW RADIO DEBUG WINDOW. There is a goldmine of information now waiting to be interpreted.
In regard to your high speed keyboard. You said: typing any call into the entry window incurs a significant lag. For instance typing GW3YDX takes four seconds to appear after the G is entered ... Aren't you the lucky one. I tried it here. I typed G and waited for 10 seconds, but nothing happened. Then I thought maybe because my call is K4CY I should type K and wait 10 seconds? Nope, still nothing happens. Maybe you could try to explain your observations in a way I could attempt to duplicate.
SeventyThree(s).
|
||
|
||
Program loses frequency and a lag on entering callsigns
Ron Stone
Greetings. I'm using L32 version 3.50.422. CAT control is via a IC7300. Correct frequency is shown in the entry window but often it is sporadically lost and replaced with 0.00, then switches back to the correct frequency. If there is a call in the entry window it is lost. Additionally, typing any call into the entry window incurs a significant lag. For instance typing GW3YDX takes four seconds to appear after the G is entered. There is nothing gobbling memory from the PC. Neither of these issues are RF-related as they both occur during both RX and TX periods. Neither of these issues occur when I use N1MM+ for contesting. PC is a Windows 7 machine but it is stable and responsive with all other programs. This issue is only evident in Logger32 and I would dearly love it if someone can suggest a fix, thanks. 73 and stay safe Ron GW3YDX
|
||
|
||
Re: Problem with Logger32 autoinstall
Bob
1. You must change the Logger32.exe settings so it is run as an administrator. Do this: Find the Logger32.exe icon in the \Logger32 directory. Right click on it, the click the PROPERTIES menu. The Logger32.exe properties window opens. Click the COMPATIBILITY tab. Click CHANGE SETTINGS FOR ALL USERS. Check the option RUN THIS PROGRAM AS AN ADMINISTRATOR. Click APPLY. Click OK.
2) To update your QTH, do this: On the Logbook Entry Window, right click where you type in the callsign. On the menu, click SETUP. On the new menu, click My QTH Lat/Long.
Please read the Logger32 help file. You will find it much easier and enjoyable to know how to make it work. After you have successfully upgraded, you can download the latest help file from https://github.com/VA7HU/Logger32-Helpfiles/releases
SeventyThree(s).
|
||
|
||
Re: Problem with Logger32 autoinstall
ja1nlx
Hi You must set Logger32.exe and Logger32autoinstaller.exe to run as administrator. I do not know what you want to update, however right click on
Logbook entry window and click Setup. 73
On 2020/09/11 20:30, SM0YHN@...
wrote:
Hello, --
73 de aki JA1NLX
|
||
|
||
Re: Problem with Logger32 autoinstall
GM4OSS
You need to run Logger in admin mode for auto installer to work. Close Logger down, right click icon, right click Logger, select 'run as administrator'. Steve GM4OSS
On Fri, 11 Sep 2020, 12:30 pm , <SM0YHN@...> wrote:
|
||
|
||
Problem with Logger32 autoinstall
SM0YHN@...
Hello,
I have decided to change from paperlogging to electronic logging and I am trying to install Logger32 on my laptop running Google Crome with windows10 and I have for the moment disabled my Norton antivirusprogram. After my initial installing, I have run Logger32 automatic update installer. See the screeencopy below. After answering Yes, I got thr Errormessage below: My second problem is when customizing the logbook window (e.g. updat my location) and clicking on the icons, they will not be highlighted so I cannot update. So if you can help me with my two problems, 1. what to do with the errormessage when autoinstalling Logger32? 2. why will the icons not be highlighted when I click on them? Thank you in advance for your help 73 de SM0YHN/Thorbjörn Odsjö
|
||
|
||
Re: Problem with 4.0.134 auto install
Radio Ktwonf
Thanks Aki Got Jim's SETUP file off of L32BETA and 4.0.135 is now working correctly 73
On Thursday, September 10, 2020, 08:16:27 PM EDT, ja1nlx <ayoshida0205@...> wrote:
Neil It is L32BETA to test Logger32 ver4. 73 On 2020/09/11 2:29, Radio Ktwonf via
groups.io wrote:
Not sure what the current .io group is for L32 v4 problems so I
will post here. Got the message that 4.0.134 was available this
a.m. and clicked to install. Installer ran but only opened the
Telnet , Logbook Entry and Tracking windows along with L32 Lookup and and L32Sync. Windows such as Logbook Page, Prior QSO's, DXspots etc did not open. When I went into View and attempted to open any of these windows I got the following error message : Logger 32 : Runtime error 339 : Component MSHFLXGD.OCX or one of its dependencies not correctly registered : a file is missing or invalid. Clicking on the error acknowledgement box immediately terminated L32 Note that I have been using ver 4 since 4.0.15 with no autoinstaller issues of this type. O/S is Win 8.1 and searching does not find this file in any of the systems areas on my L32 Drive. TIA - Neil K2NF K2NF --
73 de aki JA1NLX -- K2NF
|
||
|
||
Re: Problem with 4.0.134 auto install
ja1nlx
Neil It is L32BETA to test Logger32 ver4. 73
On 2020/09/11 2:29, Radio Ktwonf via
groups.io wrote:
Not sure what the current .io group is for L32 v4 problems so I will post here. Got the message that 4.0.134 was available this a.m. and clicked to install. Installer ran but only opened the Telnet , Logbook Entry and Tracking windows along with --
73 de aki JA1NLX
|
||
|
||
On Top
John Owens
I have found that if L32 has been up for a while, that when I go to UDP to bring up JTDX, the waterfall and main data window do not come up on top. They are on my desktop. If I close L32 and the JTDX windows, open it it up again, and then go to UDP, the windows do come up on top. What am I doing the wrong way????
John Owens - N7TK
|
||
|
||
Re: Problem with 4.0.134 auto install
n5kd
I’m also having the same issue with dependencies not registered.
Had to <ALT> <CTRL> <DEL> to stop program is it would not fully start.
73’ Pete, N5KD.
Sent from Mail for Windows 10
From: Radio Ktwonf via groups.io
Sent: Thursday, September 10, 2020 5:29 PM To: hamlogger@groups.io Subject: [hamlogger] Problem with 4.0.134 auto install
Not sure what the current .io group is for L32 v4 problems so I will post here. Got the message that 4.0.134 was available this a.m. and clicked to install. Installer ran but only opened the Telnet , Logbook Entry and Tracking windows along with
|
||
|
||
Problem with 4.0.134 auto install
Radio Ktwonf
Not sure what the current .io group is for L32 v4 problems so I will post here. Got the message that 4.0.134 was available this a.m. and clicked to install. Installer ran but only opened the Telnet , Logbook Entry and Tracking windows along with
L32 Lookup and and L32Sync. Windows such as Logbook Page, Prior QSO's, DXspots etc did not open. When I went into View and attempted to open any of these windows I got the following error message : Logger 32 : Runtime error 339 : Component MSHFLXGD.OCX or one of its dependencies not correctly registered : a file is missing or invalid. Clicking on the error acknowledgement box immediately terminated L32 Note that I have been using ver 4 since 4.0.15 with no autoinstaller issues of this type. O/S is Win 8.1 and searching does not find this file in any of the systems areas on my L32 Drive. TIA - Neil K2NF K2NF
|
||
|
||
Re: Logger 32 quits shortly after launch
Hi Bob Villi & Jim
Thanks for you posts and advice. Yes I did delete the Logger 32 directory prior to reinstalling the program (in hindsight not a good move). When the program quits it just closes (no flash or sulphur thankfully) - the cursor spins for about a second (like the system is very busy) and it's closed. I tried renaming the .ini file. The program then acts like I would expect, letting me put in my call to start as a new user. Can even adjust & move the various windows as I like. If I try to log, the program says I am trying to log with no frequency; but when I try to change the frequency (on the log entry box) the cursor spins and the program quits as before. Bob - you are right there is no urgency & Jim is almost certainly right in saying that I am missing something simple. Someone once said (maybe it was me!) that the simplist things are hardest to find. Whoever it was, they were 100% correct. Thanks again for your suggestions.
|
||
|
||
Re: QRZ MODULE
larry fields
thanks and will let you know what happens Thanks and 73 Larry Fields: du1/n6hpx MANILA PH (PH:9163405944(GLOBE)) =============================== CLUBS ARRL DX1PAR, 7095 Khz DX1PRS 145.340 Mhz DX1AFP 432.440 Mhz
On Wed, Sep 9, 2020 at 1:36 AM Rick Ellison <rellison@...> wrote:
|
||
|