Month: January 2023

GB0WFD – Winter Field Day 2023

Posted on by James M0ZAH

TeamWave will be taking part in the WFD using the call sign GB0WFD.

Below is a message from our Mattermost system.

Thankyou to all of you for your support as at the beginning of the journey with The TeamWave collective. We are happy to announce our first meet up for this year on Sunday the 29th of January. We will be taking part in winter field day as GB0WFD at the NZ and VW site in Wymondham. It is at Standley steel stockholders NR189JD all are welcome but we will be working out of a little shed so please let us know if your interested in coming along.
Within the TeamWave ethos you are encouraged to come along and work the station. Get hands on with us and play some radio. We will be messing around with antennas in the field and there will be tea and coffee provided. If you would like food please bring it along with you. If you would like to come along please let us know in the DXpeditions feed.

If you’d like more information please contact us on our chat system.

Packet Radio SSID and Alias convention

Posted on by Rik M7GMT

SSIDs

SSIDs are used to identify separate services running under the same call sign. For example, you may have a node, a BBS, and a chat server all running on your home packet station. All three can’t operate as exactly the same call, so an SSID is added on the end to differentiate between them.

There isn’t a fixed convention on which services should use which SSID, but as a group, it would be helpful if we had a “standard” we used, just for clarity. It doesn’t really matter what the standard is, as long as we document it, and stick to it.

With that in mind, I would like to propose the following :

  • M7GMT – Your “raw” call sign without an SSID (this implies -0). Your personal terminal. Use when you connect to other systems, are having a chat, etc.
  • M7GMT-1 – BBS (mailbox). This is somewhat of a convention already, with many TNC’s in-built mailbox defaulting to -1.
  • M7GMT-3 – Chat
  • M7GMT-5 – Node

We can use SSIDs 1 to 15, so if there are other services that several stations run (e.g. DX Cluster), we can add a new line here to keep things organised.

Aliases

Aliases are used as a “friendly name” for packet stations, allowing you to connect without having to remember whch SSID you need. For example, my node currently has the alias WYMOND (for Wymondham), so you could connect by typing either connect M7GMT-5 or connect WYMOND.

Aliases can be up to 6 characters, and should be unique on the packet network. The idea is for these to be memorable, so I would be interested in your feedback on the following formats:

  1. WAVExx – WAVE followed by a 2 letter ID. First letter is first letter of city/town/village. Second letter is type: D for digipeater, N for node, B for BBS, and C for chat. Examples:
    • WAVEWD:MB7NAF = Wymondham Digipeater
    • WAVEAN:M7GMT-5 = Attleborough Node
  2. WAVxxx – WAV followed by a 3 letter ID. As option one, but this allows an extra character for station ID, which would help prevent potential clashes as the network grows. Examples:
    • WAVBCC:GB7MSX-3 = Burgh Castle Chat
    • WAVWYD:MB7NAF = WYmondham Digipeater
    • WAVATN:M7GMT-5 = ATtleborough Node
  3. TWxxxx – TW followed by a 4 letter ID. This allows even more flexibility for the station ID, but is perhaps less clear that they are all associated. Examples:
    • TWBUCC:GB7MSX-3 = BUrgh Castle Chat
    • TWWYMD:MB7NAF = WYMondham Digipeater
    • TWATTN:M7GMT-5 = ATTleborough Node

Discuss

Again, what we settle on is less important than sticking to the standard. I would love your feedback on this, other formats to consider, and so on.

Happy packeting!