"Update on import" ADIF to fix WSJT-X 1.9.1 TX_PWR bug?
Posted: 26 Aug 2018, 13:51
Hi there,
I just wrote a bug report at https://groups.yahoo.com/neo/groups/wsjtgroup because WSJT-X exports the field TX_PWR in it's ADIF in a slightly incorrect way (there's the letter 'W' appended where there should be only a number, that's against ADIF standard.).
I saved my ADIFs and have a SQLite Log4OM database file, so I wrote a little python script to update the TX_PWR field in the Log4OM database directly from the already imported ADIF (see here: https://gist.github.com/RipperFox/0f2fd ... d90d5953dd).
So I was able to fix my QSOs logged in WSJT-X this way - but other's might not have the knowledge/time to fix their stuff - so it might however be possible to add a "update" feature to the ADIF import?
73, Sascha DK9SAS
I just wrote a bug report at https://groups.yahoo.com/neo/groups/wsjtgroup because WSJT-X exports the field TX_PWR in it's ADIF in a slightly incorrect way (there's the letter 'W' appended where there should be only a number, that's against ADIF standard.).
I saved my ADIFs and have a SQLite Log4OM database file, so I wrote a little python script to update the TX_PWR field in the Log4OM database directly from the already imported ADIF (see here: https://gist.github.com/RipperFox/0f2fd ... d90d5953dd).
So I was able to fix my QSOs logged in WSJT-X this way - but other's might not have the knowledge/time to fix their stuff - so it might however be possible to add a "update" feature to the ADIF import?
73, Sascha DK9SAS