Differences

This shows you the differences between two versions of the page.

--- packet:ninotnc [2026/02/08 14:31] – [Experimental new modes] m0lte
+++ packet:ninotnc [2026/09/09 07:29] (current) – [Pinout] ei5iyb
@@ Line 55: / Line 55: @@
 Baud is symbols per second, bps is bits per second. Where baud=bps, that means each symbol carries 1 bit (i.e. a symbol can have two states, 0 or 1). Where baud is 2x bps, that means each symbol carries 2 bits (i.e. a symbol can have four states: 00, 01, 10, 11).
-** Decoding Operating Modes from BrdSwchMod **
+**Decoding Operating Modes from BrdSwchMod**
 When the test button is pressed on the TNC, along with the frame it emits to the radio, it will emit a different frame to the KISS client that is connected.  The BrdSwchMod value in the test frame can be decoded to share information about the TNC:
@@ Line 137: / Line 137: @@
   * AX.25 - Basic over-the-air protocol utilised for packet radio
   * IL2P - Improved Layer 2 Protocol - effectively implements AX.25 but with some over-the-air improvements, transparent to the host software at both ends.
-  * IL2P+CRC - IL2P with added checksum. Co-developed by Nino KK4HEJ and Jonathan G4KLX to resolve corruption found with IL2P in practice.
+  * IL2P+CRC / IL2Pc - IL2P with added checksum. Co-developed by Nino KK4HEJ and Jonathan G4KLX to resolve corruption found with IL2P in practice.
   * BW - in this context, for FM: channel spacing, and for SSB: audio bandwidth.
   * Baud - symbols per second
@@ Line 219: / Line 219: @@
 It's also useful to measure the peak-to-peak voltage of the transmit audio signal fed to the radio after proper deviation is set, using an oscilloscope. In this case it was 690mV. This will serve as a "good enough" deviation setting in the future for this particular radio, and likely for similar radios of the same model.
+==== Deviation / test-tone reference ====
-The FM modes tones are as follows:
+Press the TEST button to emit the tone shown, then tune TX deviation to the target.
+Deviation tuning applies to the FM modes only; SSB rows list the audio/centre tone for reference.
+Values current for firmware v3/4.44.
-, 0001: 999 Hz tone for 2.4kHz deviation \\
+^ Switch ^ Band ^ Modulator ^ Test Tone / Centre Freq (Hz) ^ Target Deviation (kHz) ^
-, 0011: 500 Hz tone for 1.2kHz deviation \\
+| 0000 | FM | GFSK 9600 | 999 | 2.4 |
-, 0111: 1248 Hz tone for 3.0kHz deviation \\
+| 0001 | FM | C4FSK 19200 | 2079 | 5.0 |
-:       2079 Hz tone for 5.0kHz deviation \\
+| 0010 | FM | GFSK 9600 | 999 | 2.4 |
-C4FSK 9600 - 1039Hz for 2.5kHz outer deviation \\
+| 0011 | FM | C4FSK 9600 | 1039 | 2.5 |
-C4FSK 19200 - 2079Hz for 5.0kHz outer deviation \\
+| 0100 | FM | GFSK 4800 | 500 | 1.2 |
+| 0101 | FM | QPSK 3600 | 2079 | 5.0 |
+| 0110 | FM | AFSK 1200 | 1248 | 3.0 |
+| 0111 | FM | AFSK 1200 | 1248 | 3.0 |
+| 1000 | SSB | PSK 300 | 1500 | n/a (SSB) |
+| 1001 | SSB | PSK 300 | 1500 | n/a (SSB) |
+| 1010 | SSB | PSK 1200 | 1500 | n/a (SSB) |
+| 1011 | SSB | PSK 1200 | 1500 | n/a (SSB) |
+| 1100 | SSB | AFSK 300 | 1700 | n/a (SSB) |
+| 1101 | SSB | AFSK 300 | 1700 | n/a (SSB) |
+| 1110 | SSB | AFSK 300 | 1700 | n/a (SSB) |
+| 1111 | — | SET FROM KISS | n/a | n/a |
 ==== Frequency misalignment ====
@@ Line 324: / Line 338: @@
 * Note - for a startup script you should always use the temporary value rather than writing to memory each time
-=== GPIO ===
-With Raspberry Pi GPIO, put /usr/bin in the crontab path, and add the following to /etc/crontab:
-<code>
-# 1000 - BPSK300
-*     * * *   root    raspi-gpio set 5 op dh && raspi-gpio set 6 op dl && raspi-gpio set 13 op dl && raspi-gpio set 19 op dl
-# 1001 - QPSK600
-*    * * *   root    raspi-gpio set 5 op dh && raspi-gpio set 6 op dl && raspi-gpio set 13 op dl && raspi-gpio set 19 op dh
-</code>
-dl = drive low, dh = drive high.
-Wire the numbered GPIO pins to the bottom of the MODE DIP switch, turn all the switches off, and it'll mode-switch automatically. I've gone for BPSK300 for the first half of each hour, and QPSK600 for the second half.
-I picked GPIOs 5, 6, 13 and 19 (consecutive physical pins) to map to the DIP switch pins from left to right as you look at the PCB.
-=== MCP2221A ===
-The MCP2221A USB chip has four GPIOs which can be used to control the mode, instead of the DIP switches. This can be useful particularly on a remote site, and removes the need for a second cable (and works with a machine without its own GPIO interface).
-This is experimental and is likely to change. See https://github.com/g5dsg/2221aTool for up to date info. Thanks to Dan for working on this.
-General steps:
-''git clone https://github.com/g5dsg/2221aTool.git''
-Install python3.
-then, once (persistent):
-''sudo python3 ./2221aTool.py setup-gpio''
-this will configure the GPIO pins as outputs, and make them all low at power on.
-then, when required (non-persistent):
-''sudo python3 ./2221aTool.py set-gpio 1111''
-where 1111 is the state of the four switches, left to right.
-Wiring as follows. **NOTE - you MUST either remove the DIP switch or leave all four switches set permanently off with the jumpers in place.**
-Note: bit of an edge case, but it is required to run ''sudo python3 ./2221aTool.py setup-gpio'' at least once on a TNC before it can be flashed with new firmware, or indeed just used normally at all, at least while some of the MODE DIP switches are set to zero.
-{{:packet:ninotnc-mcp2221a-mode.jpg?400|}}
 ===== Pinout =====
-Note: this is the BACK / SOLDER side of the PLUG.
+Note: this is the BACK / SOLDER side of the PLUG. You are looking at the solder cups, NOT the pins.
 {{:kantronicstncwiring.png|}}
+We have section on making cables for NinoTNC -> [[cables|Transceiver Connections]]
 ===== Firmware =====
@@ Line 406: / Line 377: @@
 </code>
-Use v3 firmware unless you know you have a 512kb chip, which is none of the OARC UK kits (i.e. ignore the v4 firmware - it's the same, but for the bigger chip).
+Use v3 firmware if you have a 256kb chip, or the v4 firmware if you have a 512kb chip. They are functionally identical, just tailored for the memory map of the device.
 If you get dire warnings about bricked TNCs, know is this highly unlikely. Unplug TNC, reboot system, plug TNC, try again.