| Both sides previous revision
Previous revision
Next revision
|
Previous revision
Next revision
Both sides next revision
|
wiki:tcb:operation:troubleshooting [2018/02/12 01:02]
opadmin [Troubleshooting] |
wiki:tcb:operation:troubleshooting [2018/02/12 18:37]
opadmin [Troubleshooting] |
| <li><p><b>My monitor resolution is too small, I can't see all of OP Config on the screen!</b></p></li> | <li><p><b>My monitor resolution is too small, I can't see all of OP Config on the screen!</b></p></li> |
| <ol> | <ol> |
| <li><p>You can minimize the large header by clicking the small icon next the words "OP Config." This will reduce the window enough that it will fit on a screen of 768 pixels tall. <a href="http://openpanzer.org/forum/index.php?topic=46" target="_blank">See this thread in the forum</a> for a discussion.</p></li> | <li><p>You can minimize the large header by clicking the small icon next the words "OP Config" (or select the Hide Header option under the Tools menu). This will reduce the window height enough to fit on a screen 768 pixels tall.</p></li> |
| </ol> | </ol> |
| <br /> | <br /> |
| <li><p><b>I can't get OP Config to connect to the TCB!</b></p></li> | <li><p><b>I can't get OP Config to connect to the TCB!</b></p></li> |
| <ol> | <ol> |
| <li><p>Make sure you <a href="doku.php?id=wiki:opconfig:gs:drivers">installed the correct USB drivers</a>.</p></li> | <li><p><b>Drivers:</b> Make sure you <a href="doku.php?id=wiki:opconfig:gs:drivers">installed the correct USB drivers</a>.</p></li> |
| <li><p>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>Baud Rate:</b> Make sure the Baud Rate is set correctly. For USB connections it should always be 115,200. That is usually also the best rate for Bluetooth as well, unless you specifically changed it on the </html>[[wiki:opconfig:tabs:misc#baud_rates|Misc tab]]<html> for some reason.</p></li> |
| <li><p>Make sure the Baud Rate in OP Config is set correctly. For USB connections it should always be 115,200. That is usually also the best rate for Bluetooth as well, unless you specifically changed it on the </html>[[wiki:opconfig:tabs:misc#baud_rates|Misc tab]]<html> for some reason.</p></li> | <li><p><b>Wrong COM Port:</b> There can be multiple COM ports on your computer, each one assigned to various USB devices you may have. Make sure you know which COM port number belongs to your TCB. It is possible this number may change over time if you plug the TCB into a different USB slot. See the discussion in the <a href="doku.php?id=wiki:opconfig:gs:drivers">Drivers</a> section for ways to identify which COM port your TCB has been assigned. Note also there are two orange LEDs on the TCB board near the USB connector. These LEDs blink anytime communication occurs from either direction. The LED closest to the USB connector will light up anytime the computer sends data to the TCB. When you click the Connect button, this LED should blink several times (though it may take a few seconds to start). If this LED never illuminates and the OP Config program says that connection failed, you probably do not have the correct COM port selected.</p></li> |
| <li><p>Make sure you don't have any other programs connected to the TCB, for example the Arduino IDE. Sometimes if you did have another program connected (such as the Arduino IDE), even if you close that Windows will still think the COM port is taken. Close OP Config, unplug the TCB, then plug the TCB back in. Then re-open OP Config and try connecting again.</p></li> | <li><p><b>COM Port Busy:</b> Only one program can access a COM port at a time. Did you connect to the TCB with the Arduino IDE or with some other serial monitoring program? If so, OP Config may be unable to open the COM port. Close the other programs and try again, you may also need to restart OP Config.</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>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. |
| </ol> | </ol> |
| <br /> | <br /> |