User Tools

Site Tools


packet:ninotnc

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
packet:ninotnc [2024/04/01 16:37] – [Cheat sheet] m0ltepacket:ninotnc [2024/05/13 17:48] (current) – [Cheat sheet] m0lte
Line 60: Line 60:
  
 ==== Cheat sheet ==== ==== 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 ^ ^ Radio              ^ Signals ^ Notes ^
-| Yaesu FT-450D      | 0000    +| 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 +| 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. | 
- Requires low level RX audio, else CRC is always lit |+| Tait T2010 | 1100    |  | 
 +| 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. |
 ==== Switch 1 - Transmit audio range selection - DATA/MIC ==== ==== Switch 1 - Transmit audio range selection - DATA/MIC ====
  
Line 271: Line 278:
 </file> </file>
 After creating said file, run ''udevadm trigger'' for it to take effect without rebooting. After creating said file, run ''udevadm trigger'' for it to take effect without rebooting.
 +
 +If this doesn't work immediately, it may be the NinoTNC is not configured to expose its serial number. This can be enabled using the tool at https://github.com/g5dsg/2221aTool.
 +
 +''git clone https://github.com/g5dsg/2221aTool.git''
 +
 +''sudo python3 ./2221aTool.py enum-serial 1''
 +
 +If preferred, the same tool can be used to specify a serial number for the device.
 +
 +''sudo python3 ./2221aTool.py set-serial 0123456789''
 +
 +Then rerun the udevadm trigger command above.
  
 ==== Auto mode switch ==== ==== Auto mode switch ====
Line 325: Line 344:
 {{:kantronicstncwiring.png|}} {{:kantronicstncwiring.png|}}
  
 +===== Firmware =====
 +
 +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.
packet/ninotnc.1711989436.txt.gz · Last modified: 2024/04/01 16:37 by m0lte