YRARC Members Forum

JS8CALL 40M NET - MONDAY FEB 8TH @ 7PM EDT For those who may be interested in digital modes, I will be hosting an experimental 40 m net using the js8 protocol on a frequency of 7.078 MHz which is the universal standard js8 frequency. All stations taking part are asked to use the @JSNET call to facilitate group messages. All stations taking part should attempt to space themselves out above 1000 HZ so as to not double up. All stations will be asked to check in after a brief preamble at the start of the net. I will then call the stations individually and allow them to respond. We will be using the standard normal speed which operates in 15 second windows at ~16 words per minute. Due to the slow nature of the protocol, users are encouraged to compress their text messages using unconventional slang (the same way people shorten SMS messages). For example, instead of "you" simply "u" will suffice. At the end of a transmission, all stations are encouraged to put the acronym "BTU" meaning back to you for clarity in addition to using the standard present diamond symbol that automatically indicates the end of a transmission.

See attached for a presentation I gave to the club in 2019. Worth a read if you operate rtty, psk31, FT4, FT8, JT9, JT65, or JS8. Regards, Brian VE3IBW

I picked this up from the SEC-ARES Google group from Barry KB1PA. Before clear text was required, in a Multi agency incident, one responder called dispatch, which was all patched together for interagency coordination, and told dispatch he was code 101 (which for that agency meant he was going on a 10 minute “bio” break). One of the other agencies personnel heard code 101 (for that agency it meant “officer down”), and they all started to respond to the last known location of the original officer post-haste for support. Fortunately no one was injured (maybe some pride was hurt). We should always keep in mind that the object of communications is to communicate. Q-codes (designed for amateur radio Morse code operators), "10" codes, and all but the most universally accepted acronyms are to be avoided in voice communications. So "What's your QTH?" is not only incorrect (in Morse code communications it's simply QTH?) and out-of-place in voice communications, it communicates no more information than "Where are you?". When dealing with municipal emergency services, Maidenhead Grid Locations (e.g. FN03gx) are of course useless, and latitude/longitude and even descriptions like "200 metres north of the intersection of Bathurst and Aurora Heights Drive" will slow things down. That last examples is real. There was a motor vehicle accident near my home with (thankfully minor) personal injuries and I ended up calling 911 describing the location relative to the nearest intersection. The 911 operator wouldn't acknowledge the location until I gave her the address. I didn't know it and had find the sign before emergency services were dispatched. So unless you know them personally, don't assume that the person receiving the message has knowledge of any of the abbreviations or jargon that you've picked up along the way. If you do useit, make sure you use it properly. The exception would be the phonetic alphabet. To my knowledge in Canada the standard phonetic alphabet is used universally in public service and worldwide in aviation. I've noticed that it has been adopted by customer service agents in many companies as well.