Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No FT4 mode included #296

Closed
ea5wa opened this issue Dec 21, 2023 · 5 comments
Closed

No FT4 mode included #296

ea5wa opened this issue Dec 21, 2023 · 5 comments

Comments

@ea5wa
Copy link

ea5wa commented Dec 21, 2023

Trying to import some FT4 QSOs from another software, QSO are saved as MFSK mode. I take a look to the Settings-Modes and realized that there are no FT4 mode.

Is it possible to include it in the next release?

Thanks 73

@foldynl
Copy link
Owner

foldynl commented Dec 22, 2023

FT4 mode does not have a separate mode, but it is a submode of MFSK. That's why it can't be seen in Settings-Modes. But if you activate MFSK, you can see it as a its submode.

Getting back to import, I tested FT4 QSO mode import, but I didn't find any problems when FT4 is exported correctly - that means as Mode MFSK and submode FT4. Can you please give me the ADI record of the given QSO so I can check it?

@ea5wa
Copy link
Author

ea5wa commented Dec 22, 2023

Here you have two adi files. In 0-sats.adi you can see some FT4 QSOs. As you said, FT4 is a submode, but why is FT8 a mode? In ultims.adi you can see some FT8 QSOs.

I've renamed the extension because adi is not supported by GitHub

ultims.txt
0-sats.txt

@ea5wa
Copy link
Author

ea5wa commented Dec 22, 2023

I've just realized that reports are not correct
image

@foldynl
Copy link
Owner

foldynl commented Dec 23, 2023

I verified provided files and I don't see any issue during import the file to QLog.

As you said, FT4 is a submode, but why is FT8 a mode?

Good question, unfortunately, it is not a question to me. Please, see ADIF specification where FT8 is defined as Mode and FT4 is defined as a submode of MFSK.

I've just realized that reports are not correct

It is difficult to implement this correctly. QLog currently defines a default RST per Mode. MFSK is a digital mode where the so-called RSQ (quality) report format can be used but in case of FT4 it is dB report format.

There is a good news that it can be easily changed.

  1. FT4 QSOs are mostly received from external sources. So you don't have to worry about the default RST value because the external source provide a correct RST value.
  2. If you want to enter FT4 QSO manually and the default RST value is unacceptable for you, it is possible to edit the default RST for MFSK in QLog's Settings -> Modes -> Report.

@foldynl
Copy link
Owner

foldynl commented Jan 5, 2024

I am closing the issue. If you need more info, please, open a new issue report.

@foldynl foldynl closed this as completed Jan 5, 2024
@foldynl foldynl pinned this issue Jan 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants