Differences
This shows you the differences between two versions of the page.
| Both sides previous revision
Previous revision
|
|
wiki:tcb:operation:troubleshooting [2019/05/23 19:53]
opadmin [Troubleshooting] |
wiki:tcb:operation:troubleshooting [2019/05/23 19:55]
opadmin [Troubleshooting] |
| <li><p><b>Wrong Dipswitch Setting:</b> Make sure Dipswitch #5 is in the correct position for the method you are using to connect. Set Dipswtich #5 to On if you are connecting with a USB cable. Set it to Off if you are trying to connect over the Serial 1 port (for example, with a Bluetooth adapter).</p></li> | <li><p><b>Wrong Dipswitch Setting:</b> Make sure Dipswitch #5 is in the correct position for the method you are using to connect. Set Dipswtich #5 to On if you are connecting with a USB cable. Set it to Off if you are trying to connect over the Serial 1 port (for example, with a Bluetooth adapter).</p></li> |
| <li><p><b>Alternate Connection Method:</b> If all else fails, try creating a connection using the longer two-step process. As usual select the correct COM Port, but instead of trying to connect go to the Firmware tab of OP Config and click the Snoop button. If a Snoop connection is successful you will see a notification to that effect at the bottom of the window, and the TCB will spit out some information in the console window. It may be a lot of information if the radio receiver is connected/detected. The Snoop connection only listens to the TCB, it doesn't talk. But if that part works, you are already halfway to a full connection. After the TCB has completed printing debug information, now click the Connect button and the full communication connection should be made.</p></li> | <li><p><b>Alternate Connection Method:</b> If all else fails, try creating a connection using the longer two-step process. As usual select the correct COM Port, but instead of trying to connect go to the Firmware tab of OP Config and click the Snoop button. If a Snoop connection is successful you will see a notification to that effect at the bottom of the window, and the TCB will spit out some information in the console window. It may be a lot of information if the radio receiver is connected/detected. The Snoop connection only listens to the TCB, it doesn't talk. But if that part works, you are already halfway to a full connection. After the TCB has completed printing debug information, now click the Connect button and the full communication connection should be made.</p></li> |
| <li><p></html>{{ wiki:usbpowermanage.jpg?direct&200|USB Power Management}}**Windows Turning the COM Port Off:** If even the alternate connection method isn't working, check to make sure Windows isn't turning off your COM port in order to save power. You can check this setting by opening **Device Manager**, then expand the **USB Serial Bus controllers** heading. Here you will find one or more items called **USB Root Hub**. Right-click on each one and select Properties, then on the Power Management tab un-check the option that says "Allow the computer to turn off this device to save power." Expand the image at right to see an example.</p></li><html> | <li><p></html>{{ wiki:usbpowermanage.jpg?direct&200|USB Power Management}}**Windows Turning the COM Port Off:** If even the alternate connection method isn't working, check to make sure Windows isn't turning off your COM port in order to save power. You can check this setting by opening **Device Manager**, then expand the **USB Serial Bus controllers** heading. Here you will find one or more items called **USB Root Hub**. Right-click on each one and select Properties, then on the Power Management tab un-check the option that says "Allow the computer to turn off this device to save power." Expand the image at right to see an example.<html></p></li> |
| </ol> | </ol> |
| <br /> | <br /> |