TCB FAQs

From TCBWiki

Jump to: navigation, search

Contents

[edit] Startup/Booting

If the TCB receives data on the serial port while it is trying to boot up, it may not finish the boot process. The TCB startup process happens in two stages. First a bootloader called MicroMonitor is started. It does some basic hardware setup, then prints a prompt "9-run?". If no serial input is received for a few seconds, it starts the application normally. If serial input is received while it is at that prompt, it aborts the automatic startup. That provides a way to regain control of the unit if something were to go wrong with the application that would cause it to crash.

The only time serial input should be able to stop the booting process is during the few seconds it waits at the "9-run?" prompt. If that occurs, cycling power or just typing "reset" should cause it to start up again.

[edit] What's the difference between the TCB2 and TCB4?

The TCB-2 and TCB-4 are nearly identical in all respects except for the physical packaging and LCD screen size.

[edit] Can I swap radio cables between units?

In most cases, swapping cables between a TCB-2 or TCB-4 and a TCB-3 as you did should work fine. For the few radios that require something other than the default switch settings, it is necessary to make sure that the switch settings were equivalent.

The difference between the 8 pin connectors used on the TCB-2 and TCB-4 and the 10 pin connectors used on the TCB-3 is relevant only for Tait radio cables which include serial data lines. In all other cases, only the center 8 conductors are used, so the two connector types are completely interchangeable.

[edit] How do I install firmware updates?

TCB2 Firmware Updates

TCB316 Firmware Updates

TCB4 Firmware Updates

[edit] What kind of cable to I need to connect a TCB radio port to an E&M port?

See:

[edit] Why don't the buttons line up right in RCI?

If your computer's screen resolution is not set to 96 DPI, some items might not line up right, some text might not fit in the available space, and you might get scrollbars even for small windows. The solution is to change your screen resolution. To do that, minimize all of your windows, right-click on the desktop (where there are no icons), and select "Properties". Then select the "Settings" tab (probably on the far right) and click on the "Advanced" button (probably in the bottom-right corner). The specific location of the DPI setting in that dialog varies depending on your video driver. If you can find it, make sure it is set to 96 DPI. If it is, you may want to try changing it to something else (maybe 120 DPI), rebooting, changing it back to 96 DPI, and rebooting again. That will force Windows to rebuild some of your fonts for the correct size.

[edit] Why can I enter only two digits for each field of an IP address?

If you are unable to enter IP addresses like 192.168.25.21, instead getting 19.16.25.21, the problem can be solved as follows: Either change your screen resolution (as described in the section above), or upgrade RCI to at least version 2.6.1.22, which allows three digits to be entered even if the screen resolution is not 96 DPI.

[edit] What are my options for connecting my computer to the TCB so I can use RCI?

The RCI (Remote Control Interface) software supports two methods of connecting to a TCB: a RS-232 serial port or Ethernet. Both methods allow the TCB to be controlled, but the VoIP features work only with Ethernet, not with a serial connection.

Serial: Most desktops and older laptops have serial ports, typically using a DB-9 connector, but occasionally using a DB-25 (the parallel printer port also uses a DB-25, but is not compatible). Newer laptops often do not have a serial port, but it is possible to buy a USB-to-serial adapter that will also work. Serial cables can be up to maybe 100 feet long (without using special extenders); if you need more distance, consider using Ethernet instead.

Ethernet:

If you decide to use Ethernet to connect the computer to the TCB, you have several options for cabling:

  1. Crossover cable. If you have only the computer and TCB to connect (no other network devices), you can use a special crossover cable to directly connect the Ethernet jack on the TCB to the Ethernet jack on the computer. A typical network cable will not work for this.
  2. Ethernet hub or switch. Use a standard Ethernet cable to connect the TCB to the hub or switch and another cable to connect the computer to the hub or switch. If you have Ethernet jacks wired into the walls, they are probably connected to a hub or switch somewhere. You can also buy small switches (hubs are getting rare), often integrated into a router/firewall of some kind (wireless, cable, DSL, etc).

Both the TCB and the computer also need to have valid IP addresses so they can send information back and forth. The way those addresses are assigned depends on what else is in the network.

  1. If there is a DHCP server on the network to assign IP addresses (more on that later), everything should be really easy.
    1. Connect the computer to the network then reboot it so it can get a new address from the DHCP server. If that doesn't work, see the troubleshooting section below.
    2. Connect the TCB to the network. Then using the TCB's touchscreen, go to the "Setup" tab and press the "Network" button. Make sure that both "Enable Network" and "Use DHCP to obtain an IP address automatically" are selected, then exit the network setup and reset the unit (you may be prompted to; if not, use the reset button on the touchscreen - do not just turn the power off or the changes you made to the settings will not be saved).
    3. When the TCB finishes resetting, go back to the setup tab and get to the network settings. Note the IP address displayed there. It will typically be something like 192.168.0.3 (the last digit will likely change, the others could too).
    4. Start RCI on the computer. Enter the IP address noted above into the connection dialog and it should connect. Otherwise, see the troubleshooting section below.

How to know if you have a DHCP server

  • DHCP is a protocol used to automatically assign unique IP addresses to each device on a network. Most networks that have a connection to the Internet have a router that acts as a DHCP server.
  • On a PC connected to the network, open a Windows command prompt (one way to to this is to click Start, then select Run and type in "cmd"). Type "ipconfig /release" then "ipconfig /renew". If it prints some addresses, it probably worked which indicates that it was able to obtain an address from the DHCP server. If it instead prints an error message, the network may not have a DHCP server. See below for an alternative.
  • If the TCB is set to obtain an IP address automatically using DHCP and has been reset while connected to the network, but the network setup on the LCD shows an IP address of 0.0.0.0, the TCB was unable to obtain a valid IP address using DHCP. Note that with firmware versions prior to V4.x, the last valid IP address may be shown instead of 0.0.0.0, so this is not a good test of whether a DHCP server is present on the network.
  1. If there is not a DHCP server on the network, you will need to assign IP addresses manually (a "static IP" address).
    1. If the network used to connect your PC and the TCB does not have a DHCP server, you will need to assign a unique "static IP address" to the TCB and to the computer before they will be able to communicate.
    2. How to manually assign an IP address on TCB...
      1. Using the TCB's touchscreen, go to the "Setup" tab and press the "Network" button. Make sure that both "Enable Network" is checked and that "Use DHCP to obtain an IP address automatically" is NOT checked.
      2. Touch the IP address field; this should open a keypad where you can enter an IP address. In most cases, an IP address of 192.168.0.2 will work (the last number needs to be unique among devices on the network, and should not be set to 0, 1 or 255). Set the netmask to 255.255.255.0 and the gateway to 192.168.0.1. Exit the network setup and reset the unit (you may be prompted to; if not, use the reset button on the touchscreen - do not just turn the power off or the changes you made to the settings will not be saved).
      3. Some general guidelines about addresses:
        1. 192.168.0.xxx address are often used on local networks.
        2. The first three numbers (192.168.0) need to be the same (assuming the netmask is set to 255.255.255.0).
        3. The gateway address should use the same first three numbers as the IP address. The last number is typically a 1. Setting the gateway address is essential even if no gateway device exists on the network.
    3. How to manually assign an IP address on Windows XP...
      1. Start > settings > network connection > or Control panel > network connections
      2. Local Area Conection > right-click > properties.
      3. General tab > Internet Protocol (TCP/IP). Properties Button or double-click it.
      4. If can't open it, may need to log on as administrator.
        1. IP Address: 192.168.0.3 (must be different than the address given to the TCB above)
        2. Subnet mask: 255.255.255.0
        3. Default gateway: 192.168.0.1

Testing a network connection:

  • If the RCI software running on the PC is able to establish a connection to the TCB using the process described above, no further testing is necessary; the network is configured correctly.
  • The simplest network test is "ping". It sends a "ping" request to another device on the network and waits for a "pong" response, just to test that the other device is listening. To use ping, on a PC connected to the network open a Windows command prompt (one way to to this is to click Start, then select Run and type in "cmd"). Type "ipconfig xxx.xxx.xxx.xxx" where the xxx.xxx.xxx.xxx part is the IP address of the TCB and press ENTER. The computer will attempt to send four ping request to the TCB, then report on the results (on non-Windows systems, ping may keep sending requests until you stop it by pressing CTRL-C). If the network is configured correctly, 100% of the ping requests should succeed.
  • Another test that can also be run from a Windows command prompt is to try to establish a telnet connection. Type "telnet xxx.xxx.xxx.xxx" and press ENTER. If you see a "TCBx>" prompt each type you press ENTER, it is working. The RCI software uses a telnet connection to communicate with the TCB. For more information about using telnet, see http://link-comm.com/tcbwiki/index.php?title=TCB_FAQs#How_can_I_control_a_TCB_through_a_command_line_interface.3F

Troubleshooting (this section not finished):

  • serial or ethernet
  • crossover cable
  • OS on the computer - Windows XP.
  • start > run > cmd, then "ipconfig"
  • Local area network - not wireless - not telephone
    • If no LAN, try turning wireless off. ipconfig again.
  • If all addresses 0...
  • Just a cable, or hub/switch - ethernet switch
  • Crossover cable.
  • Windows XP - has RCI up.
  • Start > Control Panel > Network > Local Area Connection
  • Try ping. If that works, try a telnet client (from the Windows command prompt, try "telnet 192.168.???.???" using the IP address of the TCB.

VoIP

  • If RCI can connect, but VoIP doesn't seem to work:
    • Try disabling any software firewalls (Windows XP comes with one built in). Remember to re-enable the firewall afterward. If you can set up an exception ("hole" in the firewall) for UDP packets on port 23000, you should be able to get VoIP to work with the firewall enabled.
    • In RCI, clear the "VoIP Enabled" checkbox, exit RCI, restart RCI, then re-check that box. If that fixes the problem, please let us know and mention "Ticket #410".
    • If TCB2 or TCB4, try using the LCD touchscreen to set up VoIP to send to the computer's IP address. This is normally not necessary, but may help with troubleshooting.
    • Download WireShark and use it to view the packets passed between the computer and TCB on port 23000.

[edit] How can I control a TCB through a command line interface?

Most of the features of the TCB-2, TCB-3 and TCB-4 can be accessed through the built-in touchscreen (except for the TCB-3, which doesn't have one) or through a computer running RCI (the Remote Control Interface) software. Both of those interfaces work by sending text commands to the TCB's command processor. When running RCI, it is possible to view these commands by selecting the "Communications" menu, then "View Communications".

It is also possible to access that command line interface using a terminal emulator program like HyperTerminal, which is included with Windows(tm). This might be useful for several reasons:

  1. You want to send a list of commands from your computer to the TCB without using RCI.
  2. You want to access an advanced command that is not available from the LCD touchscreen or RCI.
  3. You are using a computer that can't run RCI (possibly because it doesn't use Windows(tm)).
  4. You want to control a TCB from another software package (besides RCI). Please contact Link Communications if you plan to do this; we can provide additional documentation and information about getting status information back from the TCB to your software.

HyperTerminal (or many other terminal-emulation programs) can connect to the TCB by one of two methods: a serial port or Telnet (using a Ethernet network connection).

  • Serial: Only one program at a time can communicate with a TCB using its serial port. If you are running RCI and it is using the serial port, you will have to exit RCI before HyperTerminal will be able to connect. When you are finished with HyperTerminal, you will have to disconnect (use the hang-up-phone button) or exit it before trying to connect again with RCI.
  • Telnet: The TCB can support up to four simultaneous Telnet connections (in addition to the serial port). Because of this, it is possible to have more than one computer running RCI connect to a single TCB simultaneously, or to have both RCI and HyperTerminal connect simultaneously (from the same or different computers).
    • Note: If more than one computer running RCI is controlling a TCB, any changes made on one computer will immediately show up on the other computer(s).
    • Note: It is possible to run more than one instance (copy) of RCI on one computer, connected to the same or different TCBs. This generally works fine, but if the VoIP feature is used, only the copy of RCI that was started first will be able to send and receive audio.
[edit] To connect using serial
    • By serial:
      • Connect a serial cable between the TCB and your computer.
      • Run a communications program (like HyperTerminal, which is included with Windows) and set it for 115K baud.
      • Pressing ENTER on your computer keyboard should then cause the TCB to print a "TCBx>" prompt (where "x" depends on which type of TCB it is).
[edit] To connect using Telnet
  • Using HyperTerminal:
    • Make a new connection. In the "Connect To" dialog, set "Connect Using" to "TCP/IP (Winsock)" rather than "COMx". Leave the port number at 23, as that is the default for Telnet. The "Host Address" will be the IP address of the TCB (you can find that on the "Setup" tab by pressing the "Network" button.
  • Using TeraTerm:
    • TeraTerm is an improved alternative to HyperTerminal. It can be downloaded free from <http://www.ayera.com/teraterm/>.
    • Follow the directions for HyperTerminal above.
  • Using the telnet client included with Windows:
    • Get to a Windows command prompt (press the Start button, click on Run, and enter "cmd" (without the quotes)).
    • Type "telnet <ip address>" where "<ip address>" is the address of the TCB. For example: "telnet 192.168.25.13"
    • Note that this telnet client seems to cause all typed characters to show up twice. To avoid this, use one of the options listed above.
[edit] Using either serial or Telnet

After connecting via either serial or Telnet as described above:

  • Pressing ENTER on your computer keyboard should then cause the TCB to print a "TCBx>" prompt (where "x" depends on which type of TCB it is).
  • Type TCB's password (default is "*1234"). You should see "User 100 is logged in" as the serial response.
  • At this point, you can type the commands listed in the TCB manual (they all start with '*'). For example, "*03 1 04" (without the quotes) will query the TCB to find out if group 1 contains port 04.
  • If you change any settings using the command line interface, you may want to save them to the TCB's permanent memory so they won't be lost if the power cycles. To do that, enter "*#".
[edit] Advanced Commands

There are more commands available than those listed in the manual. They are primarily intended for use by the LCD touchscreen controller or RCI, but they can also be entered manually. Note that they may change without notice (especially the ones that start with "194").

To enter any of the advanced commands, you must:

  • Connect as described above (using serial or Telnet)
  • Log in with the TCB's password (default of "*1234")
  • Enter the advanced programming mode by entering "187101". The response should be "User 101 is logged in".
  • You can then enter advanced commands. For example:
    • "009" will cause a large grid to be printed that shows the state of the internal audio crosspoint (audio switches). By looking at that grid, it is possible to determine which receivers can be heard on each transmitter.
    • "194 017 00 001" will list the members of group 1. Change the last digit to view the members of a different group.

[edit] How do I disable transmit for a radio?

The command to disable transmit has not been added to RCI or the LCD touchscreen interface yet, but it can be done as follows:

  • Get into advanced command mode as described above.
  • Enter the command to control the PTT. Its format is "155 pp x" where "pp" is a two digit port number (with leading zero if necessary) and "x" is 0 to disable the PTT or 1 to enable it. For example, "155 07 0" should disable PTT 7 (and cause "PTT for port 7 is disabled" to be printed), while "155 07 1" should enable it again.
  • An update to RCI is planned that will make this much easier. Contact Link Communications for details.

[edit] How to I add a port to more than one group?

It is typically not a good idea to add a port to more than one group, as it often leads to some people hearing only one side of some conversations. For example, if port 3 was a member of both group 1 and group 2 and was carrying on a conversation with a member of group 1, the other ports in group 2 would be able to hear any transmissions from port 3, but would not be able to hear the replies from members of group 1. To avoid this confusion, the TCB typically prevents adding a port to more than one group simultaneously. It enforces this when adding a port to a group by removing that port from any other groups.

It is possible to add a port to more than one group simultaneously using an advanced command. To do this:

  • Get into advanced command mode as described above.
  • You may want to display the current members of the groups you plan to change. "194 017 00 001" will list the members of group 1. Change the last digit to view the members of a different group.
  • To add a port to a group, enter "017 0 R 00 G PP" where:
    • R is:
      • 0 to remove the port from other groups before adding it (the way RCI and the LCD touchscreen usually work)
      • 1 to leave port PP alone if it is already in another group
      • 2 to leave port PP in any groups it is already in, but also add it to the specified group G.
    • G is the group number (1..5)
    • PP is the port number (use a leading zero if necessary to make it two digits, "03" for example)

For example, entering the following: 

 017 0 2 00 1 03
 017 0 2 00 2 03

will add port 3 to both group 1 and group 2. You can confirm that it worked by entering: 

 194 017 00 001
 194 017 00 002

[edit] How do I use VoIP to link two TCBs?

Two TCBs (any combination of TCB-2 and TCB-4) can be linked together over a network connection using the built-in VoIP feature. When linked that way, port 2 of each unit sends audio to and receives audio from port 2 on the other TCB. By adding port 2 to a talk group on each TCB, those talk groups (one on each TCB) are effectively combined into one, allowing users of each system to communicate, even if the TCBs are many miles apart. To set up such a VoIP link between TCBs:

  • Both units must be able to "see" each other on the network. In most cases, this means that they need to have public IP addresses (not be hidden behind a firewall).
  • The touch screen on the TCB (rather than RCI) must be used to set up the destination VoIP IP address (the address of the other unit that is to communicate with). That setting can be found by selecting the Setup tab and pressing the Network button.
  • Port 2 on each unit should be set for VOX access (Setup tab, Port 2, Manually Adjust Settings, VOX).

Note that if RCI is used after setting up such a VoIP link, that clicking on ports will change which ports are connected to port 2, which will change which port's audio is linked to the other TCB.

[edit] I am using a satellite-based network connection for RCI. Do I need to change anything?

It depends on now the satellite network connection is configured. There are several potential issues:

  • Bandwidth.
    • RCI requires very little bandwidth to establish the basic control connection to a TCB via telnet. A burst of about 200KB of data is sent when RCI synchronizes. A slow connection can make this transfer take a few seconds longer, but isn't a problem otherwise. After synchronizing, RCI uses very little bandwidth for the control connection.
    • VoIP. If you enable VoIP from RCI, it currently uses about 150kbps continuously from the TCB to RCI, and when the PTT bar is active, from RCI back to the TCB. Changes to reduce the bandwidth used are in the works; contact Link Communications for details.
  • NAT (network address translation). The routers used for some satellite network connections use NAT to provide isolated network IP addresses for the devices connected to them. A side effect of NAT is that the devices on the isolated network behind the router are not directly visible (and cannot be directly connected to) from the other side of the router. For example, the satellite router might provide a connection to the Internet using IP address 67.42.171.29, which can be reached from anywhere on the Internet. The devices connected to the router, however, might have "local" addresses like 192.168.0.2 (they typically start with 192.168). Such "local" addresses are not visible from other places on the Internet. If a TCB is connected to the Internet through such a router, the following methods may provide a way to access it through the Internet connection:
    • VPN. If the satellite router provides a VPN server, a computer with an Internet connection could use VPN client software to connect to the router. The VPN software would then make the computer appear to be part of the "local" network with the TCB (it would probably generate a 192.168... address for the computer). The computer should then be able to connect to the TCB exactly as if it was directly connected to the same network. Both control commands and VoIP should work normally as long as enough bandwidth is available.
    • Port forwarding. The satellite router might support a feature known as "port forwarding". Port forwarding allows a computer on the Internet to connect to the router (using the router's IP address) and request a certain type of connection (like telnet). When the router detects such a request, it may be configured to "forward" the request to one of the local addresses, such as the TCB's address. The control connection used by RCI would require the Telnet connections to be forwarded. Telnet uses the TCP/IP protocol. Telnet uses port 23 for the initial contact, then switches to a different port number for further communications. The router will probably need support specifically designed to work with Telnet to handle the forwarding when it switches to another port number. To support VoIP, port 23000 would need to be forwarded. Once the telnet connection is forwarded, configuring this should be relatively straightforward, as the port number is always the same.
  • Latency. Latency is the time it takes for a message sent by RCI to reach the TCB, or vice-versa. Satellite network connections typically have much more latency than other network connections (at least partially because the RF signals have to travel so far to and from the satellite). While latency isn't a big problem in itself, it may confuse RCI, which expects responses within a certain amount of time. If there is too much latency (delay), you may have to tell RCI to wait longer after sending a message before expecting a reply.

RCI sends messages to the TCB-4 every couple of seconds and watches for responses to make sure they are still connected. If it doesn't get the responses it expects quickly enough, it triggers a reconnect. RCI stores a file with a bunch of settings, including the ones that affect the reconnecting process, in a file. On my computer, that file is stored at the path: 

 C:\Documents and Settings\steve.strobel\Local Settings\Application Data\Link Communications\RCI

It will be some different on your computer; you will have to at least change the steve.strobel part to the user name you log onto that computer with. If you can't find the right path, try doing a search in all of Documents and Settings for "TCB4RCISettings.ini". After exiting RCI, you can edit TCB4RCISettings.ini by right-clicking on it, and selecting "Open" or "Open With" in the menu (if it asks you what to open it with, try Notepad).

Inside that file you should find a section like this: 

GeneralSection]
UseMultiple=0
CPTTTimeout=2
ConsoleMode=1
ClientMode=0
NormalPingTime=3
MaxPingsWithoutPrompt=2
MaxPingsWithoutCRC=20
MaxConnectionResponseTime=2

You can edit the settings in that file, save the file, and restart RCI to see if the changes make any difference. I would start by increasing MaxPingsWithoutPrompt to at least 4, maybe to 6. If that doesn't help, try increasing MaxPingsWithoutCRC. You could also increase NormalPingTime (so it won't check to see if it is connected as often), but I don't think that is as good of a solution as the previous two. Increasing MaxConnectionResponseTime could help if it was having trouble connecting, but since that works, I don't think it will do any good in this case. If things seem to get worse rather than better, you can just erase that file and run RCI again. It will make a new copy of the file with the default settings (you will have to enter the IP address of the TCB-4 again).

See also VoIP

[edit] Can I back up the settings in my TCB, or copy them to another unit?

See Backing Up Or Cloning TCBs.

[edit] Is there an easy way to enter a bunch of destinations (radio channels) on more than one TCB?

There are three ways:

[edit] How can I change the password from the default of *1234?

TCB-2 and TCB-4: The password can be changed from the Setup tab by pressing the Programming button (in the System group). A new password can be entered under the label Enter Programming Mode.

TCB-2, TCB-3 or TCB-4 running older versions of RCI: In the TCB Settings menu, select TCB Network Settings. Enlarge the dialog by clicking on the bottom edge or lower-right corner of it and dragging it downward. A group of settings titled DTMF Programming should become visible. You can enter a new password below the label Enter Programming Mode.

TCB-2, TCB-3 or TCB-4 running newer versions of RCI: Connect to the TCB using the serial port or network (telnet); HyperTerminal will work in either case.

  • Log on with your existing password (default is *1234), then enter "187101" to get into advanced programming mode.
  • To find out the number of the macro used to implement the password, recall the macro number that is currently named *1234:
    • 012 *1234
    • It should respond with "Commands named *1234: xxx" <- note what xxx is so you can use it in the next command
  • Change the name of that macro:
    • 010 xxx <new password>
    • The new password can use any digit except ! (exclamation point).
  • Save settings:
    • *#

Note that whichever method is used to change the password, you will have to use the new password in the future when accessing the setup features of the TCB. Specifically:

  • RCI will need to know the new password the next time it tries to connect to the TCB. To enter the new password, select the Communications menu, then Communications Settings. The new password can be entered below the label Enter Password (note that it will appear as something like ***** to prevent revealing your actual password). Press the Reconnect button to make sure that RCI is able to connect with the new password.
  • On the TCB-2 and TCB-4, the Setup tab may be password protected (that option can be set in the same place that the password is changed using the touchscreen, as described above). If it is, the new password will need to be used to access that tab.

Q: What if I forgot the password?

A: The TCB doesn't save changed settings immediately, so you may be able to go back to the previous password. The following things cause the TCB to save its settings:

  • In RCI: File menu, Save Settings (on TCB)
  • DTMF Command: *# (you must be logged on with your password to do this)
  • TCB-2 and TCB-4 Touchscreen: Setup tab, Save button
  • TCB-2: Turning off the power switch on the front panel

If the settings have not been saved since you changed the password, you can revert to the previous password by unplugging power to the TCB. Warning: this will cause any settings you have changed since last saving to be lost.

If the settings have been saved since the password was changed, contact technical support for assistance.

[edit] How can I use the TCB to send EIA tone keying sequences?

See EIA Tone Signaling.

[edit] What is the process for replacing the processor card?

See Removing and Replacing the TCB4 processor card.

[edit] Why does my TCB2, TCB3 or TCB4 reset over and over?

There are several possibilities:

  • If the TCB is running software V3.xx or earlier and RCI (the Remote Control Interface software) is running while the TCB tries to start up or save settings, it may occasionally cause another reset. This problem can be worked around by exiting RCI for a minute or so to let the TCB finish booting up. Once it has completed the boot process, RCI can be started again without causing a reset. Updating the firmware to V4.xx will prevent this problem.
  • If a TCB2 or TCB4 displays "Loading data..." on the touchscreen for a while, then the screen goes blank and it resets, the problem is very likely to be a bad connection between the plug-in boards and the backplane. It can often be resolved by unplugging all of the cards as described for the processor card in the FAQ above and plugging them back in. If that doesn't help, try the following:
    • Power down and unplug all of the radio cards (just pulling them out an inch will work). Leave the processor card installed (it is required for operation and must always be installed in the original slot). Power up and see if it gets past the "Loading data..." message. If it gets to the touchscreen calibration it is working; you can power down and go to the next step.
    • Power down and plug in the radio card in slot 1 (the slot furthest from the processor board). Power up and see if it gets past the "Loading data..." step as described above.
      • If this step fails, try a different radio card in slot 1. The radio cards are identical, but a radio card has to be installed in slot 1 for any of the other radio card slots to be functional.
    • Power down, plug in another radio card, and repeat the test for each other radio card. If a radio card prevents the system from booting, leave it uninstalled or try it in a different slot.
    • Note that there are three LEDs on each radio card that should begin blinking while the "Loading data..." message is displayed. If they do not blink, there is a problem that will cause the TCB to reset in a few seconds.
    • If the radio card in slot 1 works but all other cards fail regardless of where they are plugged in, the problem may be with the card installed in slot 1; try a different card in that slot. The card installed in that slot automatically becomes a master clock source for the other cards, so if it is defective, the other cards will all fail to work (their LEDs won't blink) even if they are not defective .
    • If a card doesn't work regardless of which slot it is plugged into, check that none of the pins are bent on its connector to the backplane.
  • When the TCB detects a problem, it may automatically reset to try to correct the problem. Before such a reset, it will always print a message out the serial port describing why it is resetting.
    • To troubleshoot the problem, connect a computer's serial port to the serial port on the microprocessor card, run a terminal program (like HyperTerminal, Procomm, Putty or TeraTerm) and set it for 115200 baud with no handshaking. If you can capture and email a copy of the diagnostic messages to Linkcomm, we can help determine the problem.
    • When the problem is that a radio card is failing to communicate as described above, the diagnostic messages will mention "ping warnings" for the radio card. Removing the card will allow the other cards to work normally. Note that card #1 must be installed for the other cards to work; if card #1 fails, move a different card to that slot.

[edit] Why does RCI display an "is not a valid IP address" message every time it connects?

There is a bug in RCI version 2.6.2.17 (and probably some other versions) that causes this message when the computer running RCI is connected to the TCB using a serial cable. It is fixed in V4.45 and later versions (it was fixed sometime before then, but we haven't tracked down the specific version). There are several ways to deal with the problem:

  • Update RCI to a later version (we recommend updating the firmware at the same time).
  • Connect the computer running RCI to the TCB using an Ethernet network rather than a serial cable.
  • Enable the network interface on the TCB (even if it isn't connected to a network). This gets rid of the error message you otherwise get when connecting serially.
    • This can be done in RCI from the TCB Settings menu > TCB Network Settings. You may get several "is not a valid IP address" warning windows at this time; just close them. The "TCB Network Settings" window should appear. Check the box labeled "Enable Network". If you don't want to actually connect to a network, uncheck the "Use DHCP" box. The other three entries can be left with their default values (0.0.0.0). Click "Done", then from the File menu > Reset TCB. After it resets, RCI should automatically reconnect without the previous problems.

[edit] Why does RCI display an "Update Needed" message every time it connects?

It is normal for RCI to display a "SynchronizerForm" with the message "Update Needed. RCI and TCB are out of synch." when you have updated one and not the other. It can also happen when RCI has trouble receiving all of the data sent by the TCB. One clue that this has occurred is that the firmware version will be displayed on the SynchronizerForm as "V2.4.x or earlier". If this occurs, click the button "Continue without updating".

This problem has the same root cause as the previous one. The same methods can be used to fix it.

[edit] Why does RCI show blank port and group labels?

This problem has the same root cause as the previous one. The same methods can be used to fix it.

[edit] When using the MSAT-xxx, can two handsets be used simultaneously?

  • MSAT Handi-Remote: No. When the Handi-Remote is connected to the MSAT radio, only the remote handset (at the other end of the CAT-5 connection) can be connected or used.
  • MSAT-PSTN: Kind of. The MSAT radio can be used from either the MSAT handset or the PSTN when the other is not active. When the PSTN is off-hook, the handset will display correct status messages, but will not be able to send commands (pressing keys won't work). This is also true if the handset is located some distance away using a Handi-Remote.
  • MSAT-IP or MSAT-IP LMR: Yes. The locally-connected handset can operate simultaneously with any remote physical or virtual handsets connected via the IP network.
Retrieved from "http://linkcomm.com/tcbwiki/index.php?title=TCB_FAQs"