QRP Appliance?

A QRP Appliance comes to live. It contains:

  1. KD1JV Tribander
    1. with speaker mod
    2. power supply mod
  2. Elecraft T1 Tuner
  3. American Morse Paddle
  4. Power Poles

07.03.15 - 1.jpg


Verified All-Band TRX for the Yaesu FT 817 ND

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.

Bild.png


Elecraft T1 ATU in FT 817: Done.

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.evernote-camera-roll-20150207-145037


Connect Morse Key to Iphone

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.

Pasted Graphic

  • 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

I got a prototype running with irmc-ios (R4) and the same physical interface also works with iMorsix (R3).
IMG_0188

(R1) Hijacking Power from […] Audio Interface
(R2) Sources: hijack-main
(R3) App: iMorsix
(R4) App: irmc-ios


XML Bandplan – Structured Amateur Radio Bandplan

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:
<bandname=“40m”author=“DG6FL”created=“20121109”valid=“20130101”ref=“DE02”>
<countryname=“DE”/>
</band>
Using (XSLT) scripts this information can be converted to C source code:
constt_bandbands[]={
{“2200m”,13570,13780, NULL },
{“2200m: CW, QRSS, narrow digital modes”,13570,13780, NULL },
{“160m”,181000,185000, NULL },
};
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:
<regionmin=“7175000”max=“7300000”bandwidth=“2700”ref=“US01”>
<licensename=“Amateur_Extra”ref=“US01”/>
</region>
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.
<channelname=“PSK31”freq=“7035000”ref=“US02”><modename=“Digital”/></channel>
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

For such a structured document it is very important, that its syntax is correct. Therefore I have described the document structure in a DTD file. This DTD file is referenced in all the XML bandplan files:
<!DOCTYPE note SYSTEM “bandplan.dtd”>
It is possible to check the syntax of all bandplans using the top level makefile:
$ make xmltest

HTML Output

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
Klasse_A: 750W (PEP)
Klasse_E: 100W (PEP)
DE02
3.500 – 3.510 0.200 CW
Klasse_A: 750W (PEP)
Klasse_E: 100W (PEP)
DE01 Intercontinental QSO
3.510 – 3.560 0.200 CW
Klasse_A: 750W (PEP)
Klasse_E: 100W (PEP)
DE01 Contest
3.555 CW DE01 QRS
3.560 CW DE01 QRP
3.560 – 3.580 0.200 CW
Klasse_A: 750W (PEP)
Klasse_E: 100W (PEP)
DE01
3.560 CW DE01 QRP
3.580 – 3.590 0.500 Digital
Klasse_A: 750W (PEP)
Klasse_E: 100W (PEP)
DE01 small bandwidth digital modes
3.590 – 3.600 0.500 Digital
Klasse_A: 750W (PEP)
Klasse_E: 100W (PEP)
DE01 small bandwidth digital modes, automatic digital stations
3.593 WSPR WSPR01 WSPR
3.600 – 3.620 2.700 All
Klasse_A: 750W (PEP)
Klasse_E: 100W (PEP)
DE01
3.620 – 3.650 2.700 All
Klasse_A: 750W (PEP)
Klasse_E: 100W (PEP)
DE01 SSB contest
3.630 Digital DE01 Digital Speech
3.650 – 3.700 2.700 All
Klasse_A: 750W (PEP)
Klasse_E: 100W (PEP)
DE01
3.690 SSB DE01 QRP
3.700 – 3.800 2.700 All
Klasse_A: 750W (PEP)
Klasse_E: 100W (PEP)
DE01
3.735 Digital DE01 ATV
3.760 DE01 Emergency Region 1
3.775 – 3.800 2.700 All
Klasse_A: 750W (PEP)
Klasse_E: 100W (PEP)
DE01 Intercontinental QSO
 
 

Summary

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.

Open Issues
Current Version (June 2013) v0.7.16


Morse Decoder Test – iPhone / iPad

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.

Results:

  1. MorseDecoder (HotPaw Productions)
    Seems to work
  2. MorseDec (Luca Facchinetti)
    Room for improvement
  3. Morsepad (Black Cat Systems)
    Does not work at all

Raspi As WSPR Transmitter

Recently the Raspberry Pi (Raspi) has gained much interest in the Ham Radio community. One interesting things is: the I/O pins provide access to a clock signal (GPCLK0) and it is possible to modulate this clock signal via software. This has motivated Guido Ten Dolle (PE1NZZ) to implement a WSPR transmitter and to publish the sources under GPL. Within the last days I have made some minor modifications to the WsprryPi sources, built a 30m QRP filter using the ugly method and connected everything to my doublet antenna.

Raspi as WSPR Transmitter

Immediately my 10mW have been received in 743km distance by G6HUI (WSPR Spots):

Timestamp Call MHz SNR Drift Grid Pwr Reporter RGrid km az
 2013-04-13 15:30  DG6FL  10.140199  -16  -1  JO40cb  0.01  G6HUI  IO81wl  743  286
7869km with 10mW
Timestamp Call MHz SNR Drift Grid Pwr Reporter RGrid km az
 2013-04-22 05:02  DG6FL  10.140238  -21  1  JO40cb  0.01  W4AC  EL86  7869  289

Information on how to do this yourself can be found in the WsprryPi repository.