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

Payload ID request #25

Closed
TSalwach opened this issue Mar 14, 2021 · 4 comments
Closed

Payload ID request #25

TSalwach opened this issue Mar 14, 2021 · 4 comments

Comments

@TSalwach
Copy link

Hi
Please add those ID's, those are for me and my friends, I'm sending them in single request.
SP6ZWR-13
SQ6QV-13
SQ6NLN-13

73
Tom SQ6QV

@darksidelemm
Copy link
Member

Are you sure you want the -13 callsigns? This may get confused with an APRS-sourced call, or if you use APRS trackers as well as this. Are you expecting all of these callsigns to be used? For testing you should be using the 4FSKTEST callsign.

@TSalwach
Copy link
Author

We will be using RS41 software sending also same position with same callsign by APRS.
If this is a problem for habhub software You can do -4FSK. This is to avoid confusion.
Yes all those callsigns will be used, sometimes we fly 3 baloons at the same time.

@darksidelemm
Copy link
Member

Yes, using the same callsign won't end well.

I've allocated the following:
45, SP6ZWR-4FSK
46, SQ6QV-4FSK
47, SQ6NLN-4FSK

73
Mark

@TSalwach
Copy link
Author

Thanks!

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