¿ªÔÆÌåÓý

FT8 Pull Request submitted - Signal Level "+" sign


 

Just submitted a PR to add a "+" sign to FT8 signal reports that are not negative (including the "+" for positive signal levels does appear to be the FT8 convention)

The change is very simple to implement if anyone would like to try it:

In sbitx_ft8.c, line 488, change:

? ????????? sprintf(buff, "%s %3d %3d %-4.0f ~? %s\n", time_str,

to:

????????? sprintf(buff, "%s %3d %+3d %-4.0f ~? %s\n", time_str,

(it's just the addition of a single "+" character.

This will result in signals with a positive strength to show the "+" sign in the output window. It also causes the "+" sign to now be sent (when signal reports are positive) during a QSO.

73; Steve, N3SB


 

Preface: I know almost nothing about coding.?

My question is, how will the logging program respond to a 0(zero) report value since it is unsigned?

David

On Wed, Jan 3, 2024 at 18:39 Steve Beckman <n3sb@...> wrote:
Just submitted a PR to add a "+" sign to FT8 signal reports that are not negative (including the "+" for positive signal levels does appear to be the FT8 convention)

The change is very simple to implement if anyone would like to try it:

In sbitx_ft8.c, line 488, change:

? ????????? sprintf(buff, "%s %3d %3d %-4.0f ~? %s\n", time_str,

to:

????????? sprintf(buff, "%s %3d %+3d %-4.0f ~? %s\n", time_str,

(it's just the addition of a single "+" character.

This will result in signals with a positive strength to show the "+" sign in the output window. It also causes the "+" sign to now be sent (when signal reports are positive) during a QSO.

73; Steve, N3SB


 

Hi David - a 0 will get a plus sign in front of it, which appears to be convention.

BTW - I'm seeing another convention that signal reports are two digits. If that's the case, it's easy to accommodate: just add a "0" digit after the "+" digit that was just added, like this:

????????? sprintf(buff, "%s %3d %+03d %-4.0f ~? %s\n", time_str,

FYI I made this change, and completed an FT8 contact with this new code where the report I sent was formatted as "+03" and the other station decoded it fine.

73; Steve, N3SB


 

On Thu, Jan 4, 2024 at 01:03 AM, Steve Beckman wrote:
sprintf(buff, "%s %3d %+03d %-4.0f ~? %s\n", time_str,
Steve,
I tried the modification and it works as follows.

The file name is correct: modem_ft8.c


until then, the second post says:

sprintf(buff, "%s %3d %+03d %-4.0f ~ %s\n", time_str,


What you see on the screen is -04 instead of -4.
Those who have used the FT8 operating mode before will expect this during operation.

Keep up the good work, I hope you find the solution to the hidden call sign of the station <...>.
?
--
Gyula HA3HZ


 

Steve,
I'm just writing to help you put the / sign in parentheses that are different from the usual structure (meaning occasional call signs).
For example, I called station EA8AAH/5 and I thought from its transmission frequency that it answered me, because I saw HA3H <...> -03.
? I deleted 73 from the GRID (CQed without Grid) and answered.
This was literally made blind. Here is a picture of it.
--
Gyula HA3HZ