brainwagon

You’ve had a C compiler sitting in front of you and some communications textbooks, and so you’ve done some hard work and created a new digital mode that you’d like to see widely deployed. What should you do? Well, let’s begin with what you should not do:

1. First, you shouldn’t presume to dictate what frequencies it should be used on without paying some close attention to the bandplans, both voluntary and involuntary, that we as hams have established. A particularly bad choice would be to recommend frequencies such as 14.101, which are uncomfortably close to the 20m beacon that many hams rely on.
2. You should not recommend frequencies that are likely illegal. Modes wider than 1khz, or which use unspecified coding aren’t legal on 30m in the U.S.
3. You should not call your mode something which is either incorrect, or at best misleading. If you say your mode is spread spectrum, it’s going to make a lot of people upset, and you could have avoided that by knowing what words mean.
4. You should not keep the details of your scheme private. As amateurs, we are tasked with improving the radio art through experimentation, and trade secret modulation does nothing to encourage or aid that kind of cooperation. I’d suggest that you make your scheme open source to achieve maximum impact. Private protocols and encodings are basically just encryption.
5. You should not make vague assertions about the mode’s performance. Comparisons of a mode which runs at (say) 16 baud and take 2.25khz of bandwidth have to be carefully made when compared with modes that run at (say) 31.25 baud and only 80hz or so of bandwidth.
6. Lastly, you shouldn’t fabricate communications between yourself and the FCC in support of your new mode. It doesn’t lend much credibility when you later retract all evidence that you did so by deleting posts from your blog.