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

Using QSSTV with CW ID and FSKID for legal reasons (proposal) #35

Open
barrydegraaff opened this issue Jul 15, 2023 · 2 comments
Open
Labels
enhancement New feature or request

Comments

@barrydegraaff
Copy link
Contributor

I do not know what the requirements are in various countries for sending your HAM call sign, in The Netherlands one is required to send it at the beginning and the end of a transmission. (keeping it short here for the case of SSTV)

https://wetten.overheid.nl/BWBR0036375/2021-06-18

image

I want to use the FSKID, which makes the repeater understand my callsign (and relay the image). But I also want to adhere to regulations.

The only way to do this in QSSTV is to uncheck the CW-ID option, then QSSTV will send the FSKID at the end of the transmission, this means I have to click the CW ID button manually for TX-ing my call sign every time I transmit an image.

So the problem is QSSTV can only send the CW ID OR the FSKID at the end of the transmission... what I would like is the CW-ID at the beginning and the FSKID at the end.

A fix would be as follows:

Change txfunctions.cpp:

        case TXSSTVIMAGE:
          waitTxOn();
          addToLog("Entered SSTVTXIMAGE",LOGTXFUNC);
          startProgress(sstvTxPtr->calcTxTime(0));
          addToLog("Entered before SSTVTXIMAGE",LOGTXFUNC);
          if(sstvTxPtr->sendImage(txWidgetPtr->getImageViewerPtr()))
            {
              switchTxState(TXSSTVPOST);
            }
          else
            {
              switchTxState(TXIDLE);
            }
          break;
        case TXSSTVPOST:
          addToLog("Entered TXSSTVPOST ",LOGTXFUNC);
          if (useCW)
            {
              sendCW();
            }
          else
            {
              sendFSKID();
            }
          waitEnd();
          switchTxState(TXRESTART);
          break;

to:

        case TXSSTVIMAGE:
          waitTxOn();
          if(useVOX) synthesPtr->sendTone(1.,1700.,0,false);
          if (useCW)
          {
             sendCW();
          }
          addToLog("Entered SSTVTXIMAGE",LOGTXFUNC);
          startProgress(sstvTxPtr->calcTxTime(0));
          addToLog("Entered before SSTVTXIMAGE",LOGTXFUNC);
          if(sstvTxPtr->sendImage(txWidgetPtr->getImageViewerPtr()))
            {
              switchTxState(TXSSTVPOST);
            }
          else
            {
              switchTxState(TXIDLE);
            }
          break;
        case TXSSTVPOST:
          addToLog("Entered TXSSTVPOST ",LOGTXFUNC);
          sendFSKID();
          waitEnd();
          switchTxState(TXRESTART);
          break;

In sstvtx.cpp in method bool sstvTx::sendImage(imageViewer *ivPtr) remove the line:

if(useVOX) synthesPtr->sendTone(1.,1700.,0,false);

Please let me know if there are any drawbacks of sending the FSKID always, thanks!

@dl8dtl dl8dtl added the enhancement New feature or request label Jul 21, 2023
@dl8dtl
Copy link
Collaborator

dl8dtl commented Jul 21, 2023

In general, I think having that option is a good idea.
Regarding legal requirements, it seems the Netherlands (as far as I can read that) are a little stricter than other countries. Germany requires "at the beginning and end of transmission, at least every 10 minutes", but there is no specific form required, thus a callsign clearly embedded in the SSTV image would also satisfy that.

@barrydegraaff
Copy link
Contributor Author

@dl8dtl the requirement to send the call in a specific class of emission has been dropped in The Netherlands a few years ago.

So it does not matter how you send the call, as long as it is at the beginning AND at the end. And every 5 minutes but for SSTV not many transmissions are longer than 5 minutes. And short transmissions count as one transmission where short is undefined in law.

Technically FSKID is only at the end.

Is it likely one is fined for this? I think not, and even if so, fighting it in court there is a chance you still would not have to pay as there is the letter and the spirit of the law. Meaning if you are using FSKID and also put your call in the image... it's probably fine, but still it seems like an easy fix in the software and then it is 100% legal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants