Differences

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

--- packet:ft-450d [2024/02/15 17:37] – m0lte
+++ packet:ft-450d [2024/04/07 17:23] – m0lte
@@ Line 2: / Line 2: @@
 m to 6m with ATU capable of matching 3:1, 100W. RS232 CAT control. 6 pin mini DIN data port. Easily modified for RF or IF output to an SDR using a HupRF board.
+{{ :radios:yaesu-ft-450d-manual.pdf | User manual }}
+{{ :radios:yaesu-ft-450d-service-manual.pdf | Service manual}}
+{{ :packet:yaesu-ft-450d-hidden-menu.pdf | Service menu}}
 ===== TNC cable =====
@@ Line 7: / Line 13: @@
 {{:packet:ft-450d_data_jack.png|}}
-| **Pin** | **Use** | **NinoTNC pin** |
+| **Pin** | **Use**  | **NinoTNC / Kantronics pin** |
-|    | Transmit Audio (Input) | 1  |
+| 1       | TX audio | 1               |
-|   | PTT | 3  |
+| 2       | Ground   | 6               |
-|   | Receive Audio (Output) | 5  |
+| 3       | PTT      | 3               |
-|   | GND | 6  |
+| 5       | RX audio | 5               |
+A suitable cable can be made from a PS/2 extension lead, scrap PS/2 mouse or keyboard. Sometimes with the mouse/keyboard option, not all of the required pins are populated, so may not be suitable. Identify the pins with a multimeter (a croc clip lead is useful here.) Solder a DB9 plug on to the other end as above.
 ===== Usage with NinoTNC =====
@@ Line 27: / Line 35: @@
 Previously there was an article here involving a full isolation circuit with relay powered by DC brought out from the TNC, but this has proven to not be necessary.
+{{tag>radio packet hf}}
+===== Errata =====
+M0GZP has found, empirically, that both the input and output pins should perhaps be documented at 60mV instead of 500mV. This is why the NinoTNC SIGNALS settings of 0000 works for this radio, which is unexpected.