for Project:

Welcome to the Bug Tracking System for the Win-Test contest logger. Things to note :

Feel free to report any bugs, however minor. To improve efficiency, please try to be as accurate as possible.

Please don't ask for feature requests here but on the mailing list.

Thanks for your help. Olivier F5MZN and Laurent F6FVY

Task #340 — Log synchroization between different

Attached to Project— Win-Test
Opened by Christoph (DK9TN) - Sunday, 8 Dec 2013, 12:19pm
Bug Report
Current WT-4.x
0% complete

Using WT 4.11

  • running a network with 6 different machines

  • using different callsigns on different machines at the same time for pre-contest operation, e.g. different EA6/homecalls

  • having the "Options | Disable log synchroization on network" checked

still, there were occurences where QSOs from different machines were synchronized over the network. This caused quite some confusion since QSOs from different EA6/homecalls logs got mixed.

The following would be very helpful

  • Disable log synchronization completely when detecting different calls in the network. As it is being done when detecting different contest types in the network.

  • There are two options (1) "Interfaces configuration | protocol advanced settings | Synchronization (in/out)" and (2) "Options | Disable log synchroization on network". It is not clear which setting takes precedence over which.

73 Christoph DK9TN@ED6A

This task depends upon

This task blocks these from closing

Comments (3) | Attachments (0) | Related Tasks (0/0) | Notifications (3) | Reminders (0) | History |

Comment by F6FVY - Sunday, 8 Dec 2013, 4:27pm

I'd be happy (?) to reproduce the bug, while all positions have disabled sync and there are still sync frames ? I just hardened the code to prevent this, but it would require more testing.

The suggestion of blocking sync when callsigns are different is rather hard to implement, as there are cases where people want to sync despite of the different callsigns. For example, the IARU HF HQ in countries where callsigns are different because of geographical regions, etc. I'll check what can be done.

Regarding the two "options", the "disable log sync" takes precedence. The protocols frames options is much more thinner (and is rather reserved for specific usages).


Comment by Christoph - Monday, 9 Dec 2013, 9:16pm

Ok, thanks for the update.

One additional thing: Part of the problem could be that the "Options | Disable log synchroization on network" check is gone every time a log is opened. Hence, in a pre-contest environment the OPs have to remember every time when they open 'their' log to check this (or to type NOSYNC), and they have to be very quick in order to beat the sync process.

Understood that some HQs need to sync between different calls. Would it be an option to make this as an "opt-in" choice, so users have to actively check a "sync log between different callsigns in the network" option?

73 Christoph DK9TN@ED6A

Comment by F6FVY - Monday, 9 Dec 2013, 9:53pm

You hit a bug ;-) Actually, the sync enabled/disabled setting was not correctly saved. That could be a major part of the issues you faced. Sri for that. I just updated the source code.