[wt4hq] Logsync issues; plan for this year?

Laurent HAAS - F6FVY f6fvy at free.fr
Wed May 11 15:11:39 CEST 2016


Hi Mario

Le 11/05/2016 à 08:43, Mario Lorenz a écrit :

> Olaf, DJ7TO, has done tests here. His report is that he took several
> PCs, several differing logs (as if there had been connection issues),
> then turned on sync and let them run overnight. He reports a delta of
> up to 500 QSOs, both with 4.16 and 4.20. He reported this with only 3
> PCs active.

Interesting. I'd very interested by these logs. Could you make them 
available somewhere please ?

Also, do you know where these logs come from ?

And were they originally incomplete, or did you remove Q from them and how ?

FYI, I just uploaded to our repository a tool called wtMonkey. It's a 
small app you have to put in the same directory as Win-Test (no 
installer). It requires wtCom.dll, but you normally have it in your 
Win-Test directory. It also requires a master.scp file in the databases 
directory.

http://download.win-test.com/utils/wtMonkey.zip

The purpose of wtMonkey is to enter Q in a log the same way as a human 
would do. It just mimics keypresses on the target log(s).

Quick how-to :

1/ Start Win-Test and create a new IARU HF empty log. Make sure you note 
the name of the station (STN1 for example). Set the band / mode as you 
want for this log.

2/ Start wtMonkey. Set the number of monkeys to 1 (you can use several 
monkeys only if you have several instances of Win-Test running on the 
*same* machine), and enter the name of the station (like STN1) in the 
"target logs" field. Hit Start. QSO should be entered in the Win-Test 
log. You can also send "direct commands" to Win-Test when the monkey is 
stopped (only useful when you have numerous running Win-Test on the same 
PC).

> Next idea: What would happen (ie. would logsync be able to cope with it)
> if we, say, every hour or so, manually copied the logs from all
> bridgeheads to a central location, merged them, and merged the result
> back to each station ?

You must pay attention to *modify* the Station Name when the merged log 
will be reloaded by the stations. If not, by default, the name of the 
"master" log will used for all of them, and it will lead to a network 
error message.

73

Larry - F6FVY

-- 
Remember Jan. 7 2015 - #JeSuisCharlie
Remember Nov. 13 2015 - #JeSuisParis


More information about the Wt4hq mailing list