search

mbridak / FieldDayLogger

ARRL Field Day Logger written in Python using Qt5
https://mbridak.github.io/FieldDayLogger/
GNU General Public License v3.0
24 stars 6 forks source link

[2024 FD] FT8 contacts log as type DIW and are not handled correctly #45

Closed mathuin closed 4 months ago

mathuin commented 4 months ago

Describe the bug The FT8 contacts logged via WSJT-X were recorded as type DIW. They were not included as digital QSOs for the purpose of calculating score.

To Reproduce Steps to reproduce the behavior:

  1. Configure fdlogger and wsjtx as normal for Field Day.
  2. Make an FT8 contact.
  3. Note that fdlogger shows Digital: 0 in the title bar, and that the log records something like the following: 
105 N3BEN          1B  SC 2024-06-23 17:30:32 2024-06-23 17:30:00 14074823M 20  DIW

Expected behavior I expected Digital: 1 and the QSO points calculated correctly as a result.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

Additional context I'm hoping that I can figure out how to edit the database and correct this so it will generate the appropriate logs.

mbridak commented 4 months ago

Thanks for the report. I'll take a look at it when i get back from vacation.

On Sun, Jun 23, 2024, 11:13 AM Jack Twilley @.***> wrote:

Describe the bug The FT8 contacts logged via WSJT-X were recorded as type DIW. They were not included as digital QSOs for the purpose of calculating score.

To Reproduce Steps to reproduce the behavior:

  1. Configure fdlogger and wsjtx as normal for Field Day.
  2. Make an FT8 contact.
  3. Note that fdlogger shows Digital: 0 in the title bar, and that the log records something like the following:

105 N3BEN 1B SC 2024-06-23 17:30:32 2024-06-23 17:30:00 14074823M 20 DIW

Expected behavior I expected Digital: 1 and the QSO points calculated correctly as a result.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: Raspbian 11

Additional context I'm hoping that I can figure out how to edit the database and correct this so it will generate the appropriate logs.

— Reply to this email directly, view it on GitHub https://github.com/mbridak/FieldDayLogger/issues/45, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALWVLRLXYZJF2EOK67TYMWDZI4F4HAVCNFSM6AAAAABJYSMJGSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM3DQOBRGUYTKNY . You are receiving this because you are subscribed to this thread.Message ID: @.***>

mathuin commented 4 months ago

Turns out the real issue is an additional date_time field which moves everything to the right. The following sqlite command appears to have repaired the database:

update contacts set frequency=band,band=mode,mode=power,power=grid,grid=opname,opname='' where frequency like '%:%';
wvolz commented 3 months ago

I had the same issue, and believe this query also deals with the unique_id column and moving the "opname" column. Of course I suspect this is not that big of a deal for reporting so this is just in case it's helpful.

update contacts set frequency=band,band=mode,mode=power,power=grid,grid=opname,opname=unique_id,unique_id=lower(hex(randomblob(16))) where frequency like '%:%';