## Test Connection

Use the New Conection > Test Connection page to compare the version of remote service installed on the device with the latest version available for Carbide. A remote service is any software on the device that can communicate with Carbide. This includes TRK, Trace, Performance Investigator, and other services. In this pane you can:

- Set the device OS used by the device and supported by the remote service
- Verify that Carbide can communicate with the remote service via the chosen connection setting
- Verify that you have the latest version of the remote service installed on the device

Options presented may differ based on the type of connection setting chosen.

Figure 1 - Test Connection pane in the New Connection dialog

##### Table 1 Test Connection pane — items

Item | Explanation
--- | ---
Device OS | A dropdown list of device OSes that are supported by the TRK debug agent software. Select the OS used by the device before running a check.
Select a service to test | Select the remote service type to query on the remote device.
Initiate service testing | Click Initiate service testing to query the remote software on the device for its version number. It then compares the version number found with the latest version available for Carbide. A progress bar will appear when the operation requires more than a few seconds. NOTE The PC must have an internet connection to perform a remote service version check. Once the comparison is complete the Status text is updated with the result and further instructions as required. If a connection fails, the errors normally fall into these two categories: connection failure - this usually indicates the chosen COM port is not open. Try selecting a different COM port, specifically one with a name attached to it (COM4 - BthModem0) for the type of connection you are using (USB or Bluetooth). Repeat as necessary until you get a successful response. Service not responding - this indicates that the COM port is open but the remote service is not responding. First, verify that remote service is up and running on the device. Second, the remote service may be listening on a different COM port, so choose another named COM port and try again.

##### Related references

- On-Device Connections
- Setup Connection
- Install Remote Agents