Differences

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

--- packet:ninotnc [2024/03/06 17:52] – [Misc Linux Notes] m0lte
+++ packet:ninotnc [2025/04/16 15:23] (current) – [Operating modes] g7taj
@@ Line 21: / Line 21: @@
 ===== UK Stock =====
-By arrangement, Tom M0LTE will be holding stock of PCB + microcontroller only kits in the UK starting mid August. This will be on an ongoing basis. These will be available with circa 2 day shipping from [[https://ko-fi.com/s/981d919ea3|https://ko-fi.com/s/981d919ea3]]. Two sets of components from Mouser takes you over their free shipping threshold.
+By agreement, Tom M0LTE sometimes holds stock of PCB + microcontroller only kits in the UK. These are available from [[https://ko-fi.com/s/981d919ea3|https://ko-fi.com/s/981d919ea3]]. Two sets of components from Mouser takes you over their free shipping threshold.
 ===== Operating modes =====
-Current modes as of firmware release 3.3.1:
+Current modes as of firmware release 3.40 / 4.40 / v40 (all refer to the same version)
+^# ^ Mode ^QtSM Mode ^ Baud  ^ bps   ^ Mod  ^ Proto ^ Usage  ^ BW     ^ Typical use                                                                                ^
+|1 | 0001 | ? |19200 | 19200 | 4FSK | IL2Pc | FM     | 25k    | High SNR links between dedicated data radios. v41 firmware required in practice.           |
+|3 | 0011 | ? | 9600  | 9600  | 4FSK | IL2Pc | FM     | 12.5k  | High SNR links between dedicated data radios. Suitable for UK 2m band.                     |
+|2 | 0010 | ? | 9600  | 9600  | GFSK | IL2Pc | FM     | 25k    | Current recommended mode for new 70cm (25kHz) links where both ends are compatible         |
+|5 | 0101 | ? | 3600  | 3600  | QPSK | IL2Pc | FM     | 12.5k  | For situations where only a speaker/mic connection is available but > 1200 baud is desired |
+|11| 1011 | QPSK v26a | 1200  | 2400  | QPSK | IL2Pc | SSB/FM | 2.4kHz | HF - quadrature version of 1200 BPSK, twice the throughput for +3dB SNR.                   |
+|10| 1010 | ? | 1200  | 1200  | BPSK | IL2Pc | SSB/FM | 2.4kHz | HF - use for circuits where wider transmission is acceptable.                              |
+|9 | 1001 | ? | 300   | 600   | QPSK | IL2Pc | SSB    | 500Hz  | HF - quadrature version of 300 BPSK, twice the throughput for +3dB SNR                     |
+|8 | 1000 | BPSK AX.25 300bd | 300   | 300   | BPSK | IL2Pc | SSB    | 500Hz  | HF - slowest but best performing mode. ~7dB better than classic 300 baud FSK AX.25         |
+|14| 1110 | AFSK AX.25 300bd | 300   | 300   | AFSK | IL2Pc | SSB    | 500Hz  | CRC improvement of IL2P 300 baud AX.25. Recommended if you can't do BPSK / QPSK on HF.     |
+|- | 1111 | ? | n/a   | n/a   | n/a  | n/a   | n/a    | n/a    | Allows the mode to be set by a SETHW KISS command (v41+).                                  |
+IL2Pc is shorthand for IL2P plus CRC.
+**QtSM NOTE: For IL2P and CRC modes, these need to be enabled per modem in the Settings/Modems menu**
-^ Mode ^ Baud ^ bps  ^ Mod  ^ Protocol ^ Intended mode ^ BW     ^ Typical use                                                                                ^
-| 0010 | 9600 | 9600 | GFSK | IL2P+CRC | FM            | 25k    | Current recommended mode for new 70cm (25kHz) links where both ends are compatible         |
-| 0100 | 4800 | 4800 | GFSK | IL2P+CRC | FM            | 12.5k  | Current recommended mode for new 2m (12.5kHz) links where both ends are compatible         |
-| 0101 | 2400 | 2400 | DPSK | IL2P     | FM            | 12.5k  | For situations where only a speaker/mic connection is available but > 1200 baud is desired |
-| 1011 | 1200 | 2400 | QPSK | IL2P+CRC | SSB/FM        | 2.4kHz | HF - quadrature version of 1200 BPSK, twice the throughput for +3dB SNR.                   |
-| 1010 | 1200 | 1200 | BPSK | IL2P+CRC | SSB/FM        | 2.4kHz | HF - use for circuits where wider transmission is acceptable.                              |
-| 1001 | 300  | 600  | QPSK | IL2P+CRC | SSB           | 500Hz  | HF - quadrature version of 300 BPSK, twice the throughput for +3dB SNR                     |
-| 1000 | 300  | 300  | BPSK | IL2P+CRC | SSB           | 500Hz  | HF - slowest but best performing mode. ~7dB better than classic 300 baud FSK AX.25         |
-| 1110 | 300  | 300  | AFSK | IL2P+CRC | SSB           | 500Hz  | CRC improvement of IL2P 300 baud AX.25. Recommended if you can't do BPSK / QPSK on HF.     |
 Superseded (but still supported) modes:
-^ Mode ^ Baud ^ bps  ^ Mod  ^ Protocol ^ Superseded by      ^ Intended mode ^ BW     ^ Typical use                                                                        ^
+^# ^ Mode ^ Baud ^ bps  ^ Mod  ^ Protocol ^ Superseded by   ^ Usage  ^ BW     ^ Typical use                                                                        ^
-| 0000 | 9600 | 9600 | GFSK | AX.25    | 9600 GFSK IL2P     | FM            | 25k    | Backwards compatibility with legacy G3RUH modems                                   |
+|0 | 0000 | 9600 | 9600 | GFSK | AX.25    | 9600 GFSK IL2P  | FM     | 25k    | Backwards compatibility with legacy G3RUH modems                                   |
-| 0001 | 9600 | 9600 | GFSK | IL2P     | 9600 GFSK IL2P+CRC | FM            | 25k    | Backwards compatibility. Obsoleted by 9600 GFSK IL2P+CRC                           |
+|4 | 0100 | 4800 | 4800 | GFSK | IL2Pc    | 9600 4FSK IL2Pc | FM     | 12.5k  | Was the recommended mode for new 2m (12.5kHz) links where both ends are compatible, until 9k6 4FSK came along |
-| 0011 | 4800 | 4800 | GFSK | IL2P     | 4800 GFSK IL2P+CRC | FM            | 12.5k  | Debugging against 4800 GFSK IL2P+CRC in case of issues with the CRC mode           |
+|7 | 0111 | 1200 | 1200 | AFSK | IL2P     | 4800 GFSK IL2Pc | FM     | 12.5k  | Improvement over 1200 AFSK IL2P, where none of the GFSK modes are possible         |
-| 1111 | 1200 | 1200 | BPSK | IL2P     | 1200 BPSK IL2P+CRC | SSB/FM        | 2.4kHz | Backwards compatibility                                                            |
+|6 | 0110 | 1200 | 1200 | AFSK | AX.25    | 1200 AFSK IL2P  | FM     | 12.5k  | VHF APRS, backwards compatibility with classic / legacy TNCs like PK232            |
-| 0111 | 1200 | 1200 | AFSK | IL2P     | 4800 GFSK IL2P+CRC | FM            | 12.5k  | Improvement over 1200 AFSK IL2P, where none of the GFSK modes are possible         |
+|12| 1100 | 300  | 300  | AFSK | AX.25    | 300 AFSK IL2P   | SSB    | 500Hz  | Backwards compatibility with legacy HF packet modems. Modulation invented c. 1962! |
-| 0110 | 1200 | 1200 | AFSK | AX.25    | 1200 AFSK IL2P     | FM            | 12.5k  | VHF APRS, backwards compatibility with classic / legacy TNCs like PK232            |
+|13| 1101 | 300  | 300  | AFSK | IL2P     | 300 AFSK IL2Pc  | SSB    | 500Hz  | IL2P improvement of AFSK 300 baud AX.25.                                           |
-| 1100 | 300  | 300  | AFSK | AX.25    | 300 AFSK IL2P      | SSB           | 500Hz  | Backwards compatibility with legacy HF packet modems. Modulation invented c. 1962! |
-| 1101 | 300  | 300  | AFSK | IL2P     | 300 AFSK IL2P+CRC  | SSB           | 500Hz  | IL2P improvement of AFSK 300 baud AX.25.                                           |
 Prefer:
-  * QPSK > BPSK > DPSK > AFSK
+  * 4FSK > QPSK > BPSK > DPSK > AFSK
-  * IL2P+CRC > IL2P > IL2P > AX.25
+  * IL2Pc > IL2P > AX.25
   * SSB > FM
@@ Line 57: / Line 62: @@
 ===== Signals settings =====
+==== Cheat sheet ====
+  * Switch 1 is TX audio range selection - on/up is high level for louder transmitted audio, off/down is for quieter transmitted audio
+  * Switch 2 is RX audio sensitivity - on/up is low sensitivity for loud radios, off/down is high sensitivity for quiet radios
+  * Switch 3 is AC/DC coupling - normally should be off/down apart from specific radios
+  * Switch 4 is external carrier detect - normally should be off/down unless you need it for a specific purpose
+^ Radio              ^ Signals ^ Notes ^
+| Yaesu FT-450D      | 0000    | Requires low level TX audio - the FT-450D is very sensitive.\\  RX audio setting probably doesn't matter, control with appropriate RF gain / AGC, but off/down works. |
+| Tait TM8100 / 8200 | 1100    | Requires high level TX audio, else the transmitted audio is too quiet in the range of the pot.\\ Requires low level RX audio, else CRC is always lit. \\ Requires AC coupling to block the DC which is present on the TX audio pin. \\ Works with 19k2!! |
+| Tait T2010 I & II | 1100    | Tested up to Modes 0100 4800 GFSK IL2P+CRC |
+| Yaesu FTM-300D | 1100    | Tested up to Modes 0100 4800 GFSK IL2P+CRC |
+| Kenwood TK-90 | 0100 | TX audio is pretty sensitive, works better in mic range. |
+| Quansheng UV-K5 | 1100 | Wiktor - SA0WII has these working with the now well known 9k6 hardware mod |
 ==== Switch 1 - Transmit audio range selection - DATA/MIC ====
@@ Line 201: / Line 222: @@
 [[https://www.printables.com/model/562738-nino-tnc-a4-case|LEDs in a line]] - modified by Jeremy M0JXW
+[[packet:ninotnc-ka2dew-case|KA2DEW case]]
 ===== SLOTTIME and PERSIST =====
@@ Line 254: / Line 276: @@
 , 0111: 1248 Hz tone for 3.0kHz deviation \\
 :       2079 Hz tone for 5.0kHz deviation \\
+C4FSK 9600 - 1039Hz for 2.5kHz outer deviation \\
+C4FSK 19200 - 2079Hz for 5.0kHz outer deviation \\
+==== Frequency misalignment ====
+TL;DR: +/- 4kHz is absolute maximum misalignment for narrow channel, that will still be decoded
+Tested using a 25kHz Tait TM8105, programmed with a 12.5kHz channel, using a 4k8 GFSK signal with 1.2kHz deviation, and tested with a signal generator. The receive performance was fairly consistent with frequency misalignment up to +-4kHz. At that limit, the Tait's RSSI pin was indicating 3dB less signal strength than when the frequency was perfectly aligned. At +- 5kHz misalignment, receive performance disappeared. All packets lost.
+Narrowband Kenwood TK-760, nearly the same as the Tait. Also tried a FTM-3100 set to narrow. Similar, but less accurate and wider. It worked +4kHz to -6kHz, suggesting a couple kHz oscillator misalignment.
 ===== Misc Linux Notes =====
@@ Line 264: / Line 296: @@
 After creating said file, run ''udevadm trigger'' for it to take effect without rebooting.
-==== Auto mode switch ====
+If you have more than 1 TNC connected to the same device, it can be tricky to distinguish between them. The MPC2221a chip in the NinoTNC can be configured to expose a unique serial number, and udev rules can be set to ensure these get allocated consistent /dev nodes between reboots/cable swaps etc.
+Serial number enumeration is disabled on the MPC2221a chip by default, it can be enabled using the tool at https://github.com/g5dsg/2221aTool.
+''git clone https://github.com/g5dsg/2221aTool.git''
+''sudo pip3 install Click''
+''sudo pip3 install pyusb''
+''sudo python3 ./2221aTool.py enum-serial 1''
+The chips have unique serial numbers which If preferred, the same tool can be used to specify a serial number for the device. The serial can be up to 16 characters (including unicode!)
+''sudo python3 ./2221aTool.py set-serial 0123456789''
+You can then update the udev rules to use the serial number you've set (or obtained from the output of dmesg / inspecting ls -l /dev/serial/by-id, if you keep the chip's original serial)
+Example udev rules for 2 TNCs with serials 0123456789 and 987654321:
+<file shell /etc/udev/rules.d/99-ninotnc.rules>
+# Create a handy symlink to make refering to NinoTNC's easier
+SUBSYSTEM=="tty", ATTRS{idVendor}=="04d8", ATTRS{idProduct}=="00dd", ATTRS{serial}=="0123456789", SYMLINK+="tnc-2m"
+SUBSYSTEM=="tty", ATTRS{idVendor}=="04d8", ATTRS{idProduct}=="00dd", ATTRS{serial}=="9876543210", SYMLINK+="tnc-4m"
+</file>
+(Thanks to Nathan, MM3NDH for the udev rule.)
+==== Remote mode switch ====
+=== KISS SETHW command ===
+As of firmware v41, NinoTNC supports setting the mode remotely using a SETHW KISS command in combination with all four MODE DIP switches being set to 1.
+From the release notes:
+Use KISS SETHW command (6) followed by mode number in range 0-14. Mode number is in the modes table above.
+The KISS MODE setting is written to flash memory. To prevent an immediate flash memory write, add 16 to the mode number in the KISS SETHW command - for example, the value 14 would become 30.
+BPQ supports this via the ''KISS'' command. For this command to work, you must set the mode DIP switches to 1-1-1-1 (or //on-on-on-on//), and be in SYSOP mode. To enter SYSOP mode, type ''password'' at the prompt. The prompt will respond with ''OK''. At this point, enter the command below:
+<code>
+kiss <port> 6 <value as determined above*>
+</code>
+* Remembering to add 16 to the value if you don't want the setting written to memory.
+**Examples**
+kiss n is the port number - port 3 in these examples
+the 6 is always constant
+^ Set port n to mode         ^ temporary       ^ persistent      ^
+| FSK300 IL2Pc (40m slot 1)  | ''kiss 3 6 30'' | ''kiss 3 6 14'' |
+| BPSK300 IL2Pc (40m slot 3) | ''kiss 3 6 24'' | ''kiss 3 6 8''  |
+| QPSK600 IL2Pc              | ''kiss 3 6 25'' | ''kiss 3 6 9''  |
+=== GPIO ===
 With Raspberry Pi GPIO, put /usr/bin in the crontab path, and add the following to /etc/crontab:
@@ Line 276: / Line 366: @@
 </code>
-Wire the numbered GPIO pins to the bottom of the MODE DIP switch, turn all the switches off, and it'll mode-switch automatically.
+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 =====
@@ Line 283: / Line 408: @@
 {{:kantronicstncwiring.png|}}
+===== Firmware =====
+To check your firmware version, press the test (red) button on TNC and observe the decoded packet.
+<code>
+=FirmwareVr:3.41=SerialNmbr:=UptimeMilS:0196CC43=BrdSwchMod:040F0002=AX25RxPkts:000008E5=IL2PRxPkts:
+00000000=IL2PRxUnCr:00000000=TxPktCount:000008F6=PreamblCnt:0000000B=LoopCycles:0C0281E9=LostADCSmp:00000000
+</code>
+To upgrade the firmware, see https://github.com/ninocarrillo/flashtnc/blob/master/README.md.
+TL;DR:
+<code>
+# save a headache
+sudo systemctl disable linbpq
+sudo reboot
+# then...
+sudo apt install -y python3 python3-pip python3-serial git
+git clone https://github.com/ninocarrillo/flashtnc
+cd flashtnc
+python3 flashtnc.py N9600A-v3-35.hex /dev/ttyACM0
+# don't forget to...
+sudo systemctl enable linbpq
+sudo systemctl start linbpq
+</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).
+If you get dire warnings about bricked TNCs, know is this highly unlikely. Unplug TNC, reboot system, plug TNC, try again.
+===== Schematic =====
+Available from [[https://tarpn.net/t/nino-tnc/n9600a/n9600a4/n9600a4-assembly.html|tarpn.net]], mirror {{ :packet:2020-11-21-ninotnc-n9600a4r2-sch.pdf | here }}