(A) Kein Zoll, sondern nur Einfuhrumsatzsteuer? Amateurfunk-Bausätze fallen unter den TARIC Warencode 8517 (“[..] andere Sende- oder Empfangsgeräte für Töne, Bilder oder andere Daten, einschließlich Apparate für die Kommunikation in einem drahtgebundenen oder drahtlosen Netzwerk [..]“) (siehe auch Zollinformation von DK3RED).
(B) CE Kennzeichnung nicht notwendig? In der Richtlinie 2014/53/EU, Anhang I, Paragraph 1, (a) sind “[..] Bausätze für Funkanalgen, die von Funkamateuren zusammengebaut werden [..]” explizit von der Kennzeichnungspflicht ausgenommen.
A QRP Appliance comes to live. It contains:
- KD1JV Tribander
- with speaker mod
- power supply mod
- Elecraft T1 Tuner
- American Morse Paddle
- Power Poles
The information available on the web may be misleading: the jumper enumeration is ambiguous and little information on the extended range exists.
I have summarized the information on how to enable all-band TRX on the FT 817 ND in the picture below.
As described in http://www.ngunn.net/cyberworld/hamradio/t1/ I have successfully integrated a T1 tuner into my FT 817. My tuner was sensitive to noise on the 9V rail – using the 12V rail from the data port and some blocking capacitors I finally got the tuner working.
How to connect morse key to an iPhone? Using the buttons on the standard headphones does not work, as the apple interface does not provide low-level access to low-level events like button-down. The idea (R1, R2) will be (1) put a signal to one stereo channel (2) receive the same signal on the input channel (small resistor will simulate mic) (3) detect tone level changes for input channel -> real time-morse (4) put side-tone & co to remaining stereo channel.
- 1(Tip) – Key (Ground)
- 2 – Ear (Contact)
- 3 – Ear (Ground)
- 4(Ground) – R2(46,6k) – Key 1
- 4(Ground) – R3(22k) – Key 2
- 4(Ground) – R1(1k) – 3
As of today bandplan information for amateur radio is accessible in form of various spreadsheets, PDFs or even in Wikipedia. Of course this differs from country to country. Depending on the source, the bandplan may be outdated and it can be challenging to find a valid source for up-to-date information. While it is possible to find bandplan authoritative information on bandplan usage for the three different IARU regions, the best-practices for the member countries are even more difficult to find. In short: the information is difficult to find, exists in various formats and is not at hand when you really need it.
For my FT 817 remote control project I was in need of a digital bandplan for my C source code. Instead of hacking the information into the corresponding C structures I chose a different approach: I created a structured XML file with the bandplan information and used XSLT scripts to generate the corresponding C structures from the XML file:
Using (XSLT) scripts this information can be converted to C source code:
Well I did not stop there: I implemented capabilities for handling different regions within the frequency bands, countries and licenses. In the XML files this looks like this:
In addition to the obvious bandplan informations it was also helpful to create channels on particular frequencies. These channels can contain a name or a mode information, i.e. for switching the TRX automatically.
During the implementation I realized, that all entries should have some generic information, i.e. the author of the entry, a version number, a timestamp and a reference. The references (i.e. HTML, PDF or spreadsheets) can be downloaded within the framework I have created, stored to the git repository and checked for updates using MD5 sums. Checking the bandplans for possible changes is easily done now using the toplevel makefile:
$ make check_references
It is possible to check the syntax of all bandplans using the top level makefile:
$ make xmltest
What can we do with this structured XML documents? Obviously I have used it for my Arduino project. Using this information source it is easy to create HTML bandplans, PDFs or structures in the programming language of your flavour for further work.
$ make html
|Frequency (MHz)||Bandwidth (kHz)||Mode||License||Reference||Comment|
|3.500 – 3.580||2.700||
|3.500 – 3.510||0.200||CW||
|3.510 – 3.560||0.200||CW||
|3.560 – 3.580||0.200||CW||
|3.580 – 3.590||0.500||Digital||
|DE01||small bandwidth digital modes|
|3.590 – 3.600||0.500||Digital||
|DE01||small bandwidth digital modes, automatic digital stations|
|3.600 – 3.620||2.700||All||
|3.620 – 3.650||2.700||All||
|3.650 – 3.700||2.700||All||
|3.700 – 3.800||2.700||All||
|3.760||DE01||Emergency Region 1|
|3.775 – 3.800||2.700||All||
Now there is a structured document framework, which can handle all bandplan information. So far I have implemented US and german bandplans. We now have one source for all the information we need. The XML bandplan project is a building block for your future ideas and projects. Feel free to contact me and contribute ideas, converters, updates and bandplan content.
There are three morse decoders in the App Store. Same test case for all of them: “CQ CQ CQ DE DG
D6FL DG6FL K” from memory of my palm paddle with 20wpm.
- MorseDecoder (HotPaw Productions)
Seems to work
- MorseDec (Luca Facchinetti)
Room for improvement
- Morsepad (Black Cat Systems)
Does not work at all