W4/VP9KF

W4/VP9KF Logo

W4/VP9KF




W4/VP9KF  (North Carolina)
 RSS news feed help F:69 A:7 K:1 SSN: 0  WWV Log VP9KF & G4BKI
Last reload: 2018-11-12 20:03:32Z

Latest WWV data: 2018-11-12 20:00:08Z

Data policy  Disclaimer

menu
Home  | CW/CEPT  | Propagation  | W4/VP9KF  | VP9KF  | G4BKI  | G4BKI/J3 & J37KF  | Logs  | Software  | IP Ham  | Blog  | CW Links  | Hintlink
  Call History Files  | Telnet Files  | N1MM+ Logger tips  | Logger32 tips  | Applications - Latest Versions  | Units"Forecastfox" replacement

W4/VP9KF Logger32 tips page

Latest information, support and questions can be found on the Logger32 groups.io Group [with nearly 4,800 members]
Latest updates are NOT directly announced on the group, ever (you may find out by a comment from another list member referring to a version later than yours).
The author seems to have started doing so. However, if the author doesn't stop spouting his political opinions on the reflector, support will be removed from here.

Give your platform, Windows version and all other important information.
XP will not update some files automatically, as SSL (https://) is more fully rolled out during mid-2018. Windows releases before Windows 7 are not recommended.
By the way, I refuse to use Windows 10.
  Logger32 latest version number. Logger32 home site. Starting at v3.47 updates are automatic.
You can find further extensive help and advice on Logger32 at Gary (a beta tester) ZL2IFB's web site.

The first thing is to go into Windows audio configuration and TURN OFF Windows sound generation. There is a good technical reason for this if you are using the PC's serial port for keying the transmitter.

The second thing is to slightly reconfigure the COM ports. Go into Windows Device Manager [if using Win 10, select Control Panel/All Control Panel Items/Systems/Device Manager], select Ports(COM & LPT), then at each Com port, select Properties/Port Settings/Advanced.

Then find Rcvr (bytes) and set it to 64; then select Tx (bytes) and also set it to 64. Change 'Latency Timer' to 1ms [NOTE! This depends on the specific RS-232 COM type device, some have it and some don’t]. This will improve the speed of your USB/Serial devices and help eliminate CW stutter.
W4/VP9KF - CW keying hints

CW keying hints
  How to make your logging program work with CW.

The K1EL WinKeyer needs to have the correct FTDI USB driver loaded on the PC. Use Device Manager to confirm it is there and to see what COM port it is on. It may have changed.
If the keyer 'disappears', go into Device Manager, right click on the USB port and deselect "allow USB to sleep when inactive".
Download the WKxMGR software from K1EL and confirm you can talk to the
WinKeyer. It is useful to configure the WinKeyer, update the firmware and for trouble shooting. Note there are different versions depending on the WinKeyer you have.

Early WK2USBs had a problem of getting locked up if they had internal batteries installed and  the PC's USB port went to sleep. To unlock the WK2USB you need to disconnect the
WinKeyer's internal batteries. There is a firmware update that fixes this problem. If you are operating while connected to a PC, leave the batteries out anyway. Memories will be retained.
W4/VP9KF - some fixes for Logger32

Logger32 Fixes
  All software has some niggles, these are some easily fixable things in the source code.


Bandmap header shows 'M' when it should be 'm'. In fact, lots of the windows do.

m for metres, not M!

Request denied message error showed 'Mhz' when it should be 'MHz' (this has been fixed)

MHz, not Mhz


Everybody I've talked to recently (and the manufacturers) always use the term ROTATORS, not rotors (this has been fixed in some places)

Rotators


It would be very nice if the telnet window had buttons and not just a pull-down menu for sending commands




It would be good to have the program version number shown in the status bar:



There's no way to change the order in which Logger32 'boots' certain functions. It always does:
  • Download (for ~1m 10s) Club Log updates
  • Connect to telnet cluster node
  • Check for Logger32 updates
This seems a bit 'daft'. Surely it should be: Check Logger32 update, download Club Log updates, connect to cluster.
If just booting to check for an update, it takes 1m 44s and if one is available the cluster node has been bothered without cause.
Being able (in the .INI?) to define the boot order would be a real bonus.
Oh, and being able to set a threshold of hours passed before a Club Log update is forced would be good too. It seems to be 24 hours.

Why is the telnet client window wiped when you disconnect? Keeping data in place is good for debugging (like N1MM+ Logger).

It would be nice to restart on the same band as you were last on or one which you choose as a default. Without a rig attached it goes to .00000, yet the bandmap shows '10M'.

It would be nice to have band buttons (like N1MM+ Logger, but better... have them disappear when disabled).

Why, oh why, aren't new version releases announced on the groups.io Group and  the web page????

Please remember that the Logger32 code is written and supported (website) by a group of volunteers. It's tough because of the vast number of transceivers, support devices, modes and versions of PCs and Windows that are supported. Some troubleshooting is recurring and is not easy to find in the ex-Yahoo Group 'archives' [lets out a groan]. Hence these notes. Some problems are difficult to reproduce without many hours of exploratory  time.

menu
Home  | CW/CEPT  | Propagation  | W4/VP9KF  | VP9KF  | G4BKI  | G4BKI/J3 & J37KF  | Logs  | Software  | IP Ham  | Blog  | CW Links  | Hintlink
  Call History Files  | Telnet Files  | N1MM+ Logger tips  | Logger32 tips  | Applications - Latest Versions  | Units"Forecastfox" replacement

footer
  © 2003-2018 W4/VP9KF, Paul H. Evans. All rights reserved. IP footer
User Agent: CCBot/2.0 (https://commoncrawl.org/faq/) IP Address: 54.162.166.76