Fix a missing build step. Add a configuration step (Save Settings). Add more diagnostics and troubleshooting steps.

m17
Rob Riggs 2019-06-23 21:56:56 -05:00
rodzic 49a7d1f5ee
commit 5fd7b89778
1 zmienionych plików z 123 dodań i 0 usunięć

Wyświetl plik

@ -570,6 +570,7 @@
" * Connect one diode from *j49* to the upper power rail. The cathode bnad should be neares the power rail.\n",
" * Connect a jumper wire across the *e49-f49* gap.\n",
" * Connect the 220nF capacitor from *e50* to *g49*.\n",
" * Connect the 10kΩ resistor from *h46* to *h49*.\n",
" * Connect a wire from *i49* to *i36*.\n",
" * Connect a short jumper from *g37* to *g38*, tying VinA- to VoutA\n",
" * Connect a short jumper from *g32* to *g33*, tying VinB- to VoutB\n",
@ -745,6 +746,25 @@
"\n",
"![TncConfigApp Output](TncConfigApp-Output.png)\n",
"\n",
"#### Save Changes\n",
"\n",
"Once you are done configuring the TNC for your radio, go to the *Save Settings* section and press the \"Save Changes* button. This will write the configuration values to the board's EEPROM.\n",
"\n",
"We will then need to verify that the settings have been saved. It may be helpful to jot down all of the settings right now in case the settings are not retained.\n",
"\n",
"![TncConfigApp Save](TncConfigApp-Save.png)\n",
"Save Settings screen. Ignore the \"There are no unsaved changes\" text.\n",
"\n",
"To verify that the settings have been saved, press the \"Disconnect\" button on the top right.\n",
"\n",
"Unplug the USB cable from the TNC for a few seconds, then plug it back in. Using the Config App, reconnect to the TNC and verify that all of the level settings that you have just made have been retained.\n",
"\n",
"If the settings have not been retained, go to the [Testing and Troubleshooting](#Testing-and-Troubleshooting) section.\n",
"\n",
"### Using the TNC\n",
"\n",
"The TNC is now a fully operational KISS TNC. You can use APRS applications like Xastir on Linux, APRSIS32/CE on Windows, even \n",
"\n",
"\n",
"## Testing & Troubleshooting\n",
"\n",
@ -774,7 +794,110 @@
"\n",
"Verify that your USB port is capable of delivering 500mA.\n",
"Verify that your USB cable is still in good condition. If in doubt, try another one.\n",
"Verify that the USB connector on the Nucleo board has not been damaged. If it has, you will need to repair or replace the Nucleo board.\n",
"\n",
"### Nucleo Connection\n",
"\n",
"**Is the Nucleo board recognized by the OS**\n",
"\n",
"This section assumes that you have verified that power and ground are OK.\n",
"\n",
"The Nucleo board, when connected to a computer via USB, should enumerate a number of ports on the host machine:\n",
"\n",
" * A mass storage device which is mounted by the operating system\n",
" * This will mount as a drive letter on Windows\n",
" * This will appear as a drive on the MacOS desktop\n",
" * This should be mounted at/run/media/{USER}/NODE_L432KC on modern Linux systems, and appear as a mount point in the file explorer.\n",
" * A serial port\n",
" * This will appear as a COM port on Windows.\n",
" * This will appear as /dev/cu.usbmodemXXXXX on MacOS.\n",
" * This will appear as /dev/ttyACMx on Linux.\n",
" * An MBED or ST/Link progamming interface\n",
" * This is not used by this project.\n",
"\n",
"If the Nucleo board fails to enumerate all of these devices, you may be using a \"power only\" USB cable. Use your DMM to check the connectivity on the USB cable data lines. Or try another cable.\n",
"\n",
"I have not run into any problems with drivers on any of the operating systems tested.\n",
"\n",
"### Firmware Programming\n",
"\n",
"This section assumes that you have verified that the Nucleo device is enumerating properly and the Nucleo's mass storage device is mounted.\n",
"\n",
"Programming simply involves copying the firmware binary to the mass storage device. You will see the multi-color LED (LD1) on the Nucleo board flash while it programs.\n",
"\n",
"Linux may report that the device is full if you have programmed it once already. The solution here is to disconnect the USB cable from the Nucleo board and plug it back in. If you have permissions issues on Linux, you may need to add your user to the \"plugdev\" group use `sudo` to copy the file to the Nucleo board.\n",
"\n",
"There are few potential issues with programming. The MBED site is the best place for help on mounting an programming the Nucleo board.\n",
"\n",
"\n",
"### Audio Input\n",
"\n",
"You will need an oscilloscope to fully test the audio input section.\n",
"\n",
"This section assumes that you have verified the power settings, that the Nucleo connections are OK, that the firmware has been programmed, and that you can connect to the TNC from the Mobilinkd Config App.\n",
"\n",
"#### DC Offset\n",
"\n",
"Disconnect the radio from the TNC. We will be using the Mobilinkd Config App to charaterize the DC offset by changing the audio input gain.\n",
"\n",
" * Connect the config app to the TNC and go to the *Audio Input* settings.\n",
" * Set the audio input gain to 0. Use a DMM to verify that the voltage at *g49* is 1.65V.\n",
" * Set the audio input gain to 1. Use a DMM to verify that the voltage at *g49* is 0.825V.\n",
" * Set the audio input gain to 2. Use a DMM to verify that the voltage at *g49* is 0.41V.\n",
" * Set the audio input gain to 3. Use a DMM to verify that the voltage at *g49* is 0.2V.\n",
" * Set the audio input gain to 4. Use a DMM to verify that the voltage at *g49* is 0.1V.\n",
"\n",
"If the voltage is not 1.65V when the gain is set to 0, check the wiring of the cable from *j8* to *j46* and the 10kΩ resistor from *h46* to *h49*. Check the output of pin A4 on the Nucleo board. Each of these points should be at 1.65V. Fix any wiring problems. Verify that the Schottky diodes are oriented properly. Use the diode test function on the DMM to verify that the diodes have not been damaged.\n",
"\n",
"When changing the input gain, the measured voltage should roughly halve at each step. The voltages should change if the TNC is programmed and the config app is communicating with the TNC. If the voltages do not change, the TNC is not programmed or the config app is not communicating with the TNC.\n",
"\n",
"#### Audio Cable\n",
"\n",
"You will need an oscilloscope to check the audio input.\n",
"\n",
"Connect the audio cable to the radio only.\n",
"Disconnect it from the TNC if it is connected.\n",
"Turn on the radio.\n",
"Using the oscilloscope, verify that the radio's audio output signal is present at the the cable tip\n",
"\n",
" * Measure across the tip and sleeve of the connector (the sleeve is ground). If an audio signal is not present:\n",
" * turn up the volume on the radio\n",
" * use a DMM to check continuity on the cable\n",
" * verify that the cable is properly seated in the radio\n",
" * verify that the cable pinout is correct\n",
"\n",
"#### Raw Audio Input\n",
"\n",
"Connect the cable to the TNC.\n",
"\n",
"With the oscilloscope, verify that you see an audio signal at:\n",
"\n",
" * The 3.5mm connector tip *c58*.\n",
" * The capacitor at *e50* and *g49*\n",
" * The wire from *i49* to *i36* -- this is the input to the audio input buffer.\n",
"\n",
"Check the wiring along the way.\n",
"\n",
"If the audio output is being clipped at -0.3V and/or +3.6V, reduce the audio volume on the radio.\n",
"\n",
"#### Buffered Audio Input\n",
"\n",
"This assumed that the raw audio output is good up to the audio input buffer at *i36*.\n",
"\n",
"With the oscilloscope, verify that you see an audio signal at:\n",
"\n",
" * The jumper at *g37* to *g38*.\n",
"\n",
"Verify that the resistor from *g41* to *g32* is not shorted to the jumper at *g37* to *g38*.\n",
"Verify that conenction power and ground connections of the op amp.\n",
"\n",
"#### Filtered Audio Input\n",
"\n",
"This assumed that the buffered audio output is good up to the jumper at *g37* to *g38*.\n",
"\n",
"Filtered audio output should appear at the resistor lead at *i29*.\n",
"\n",
"Verify all of the connections in the [Audio Input](Audio Input) section.\n",
"\n"
]
},