Use Cases

The following examples show you how you can use the xPico 200 Series.

Connect to a Bluetooth SPP-enabled PC to use CLI

Connect to a Bluetooth SPP-enabled PC to use CLI

This example uses CLI over serial to configure an xPico 250 or xPico 270 to connect to a Bluetooth Classic Master SPP PC in order to use CLI over a Bluetooth connection. Because it uses CLI commands to configure the Bluetooth connection, it assumes Line 1 is already enabled and using the Command Line protocol, as is default.

Step 1 - Pair and connect to a Bluetooth Classic Master SPP PC

  1. Connect the xPico 200 Series to a PC using a serial cable. This does not need to be the same PC to which you're configuring a Bluetooth connection, but it can be.
  2. On the PC, open a terminal such as Tera Term and connect to the device using serial. This example uses Tera Term.
  3. In Tera Term, type status to enter the status level.
  4. Send Bluetooth to enter the status Bluetooth level.
  5. Send Classic to enter the status Bluetooth Classic level.
  6. Send Master to enter the status Bluetooth Classic Master level.
  7. Send Broadcast scan to scan for compatible Bluetooth devices.
  8. After the results are shown, send Connect <Device Address> SPP [passphrase] using the device address of the desired Bluetooth device from the results. The passphrase can be left blank if there is no passphrase. In this example, no passphrase is specified.
  9. Depending on your PC, you may need to confirm the connection from your PC.

Step 2 - Assign a Bluetooth_SPP Line

  1. Send the exit command four times to return to the root.
  2. Send config to enter the config level.
  3. Send Bluetooth_SPP to enter the config Bluetooth_SPP level.
  4. Send Master to enter the config Bluetooth_SPP Master level.
  5. Send show to see a list of Bluetooth Classic Master SPP devices connected.
  6. Send Device <Device Address> to enter the config Bluetooth_SPP Master Device level for the specified Bluetooth device.
  7. Send SPP Line SPP_1 to assign this device to Line SPP_1.
  8. Send write to write the changes.

Step 3 - Configure Line SPP_1 for CLI

  1. Send the exit command three times to return to the config level.
  2. Send Line SPP_1 to change to the config Line SPP_1 level.
  3. Send show to see the Line SPP_1 configuration.
  4. Confirm that Line SPP_1 is enabled and using the Command Line protocol, which is default.

Step 4 - Connect to Line SPP_1 from the PC

  1. On the Bluetooth-enabled PC, open Tera Term and connect to the device using serial and the COM port assigned to your PC's Bluetooth connection. In this example, COM5 is being used.
  2. You can now enter CLI commands over the Bluetooth SPP connection.

Access CLI and Trouble Log over mux, configuring via XML

This example uses CLI to import XML configuration. The import configures Line 1 for mux, Virtual Line 1 for CLI, and Virtual Line 2 for the trouble log. It then shows how to use both those virtual lines over mux. Because it uses CLI to import the XML configuration, it assumes Line 1 is already enabled and using the Command Line protocol, as is default.

Step 1 - Import XML configuration

  1. Connect the xPico 200 Series to a PC using a serial cable.
  2. On the PC, open a terminal such as Tera Term and connect to the device using serial. This example uses Tera Term.
  3. Send config to enter the config level.
  4. Send Line 1 to enter the config Line 1 level.
  5. Send Flow Control Hardware to set Flow Control to Hardware. Flow Control is required to import XML configuration.
  6. Paste the following XML in Tera Term.
<?xml version="1.0" standalone="yes"?>
<!-- Automatically generated XML -->
<!DOCTYPE configrecord [
   <!ELEMENT configrecord (configgroup+)>
   <!ELEMENT configgroup (configitem+)>
   <!ELEMENT configitem (value+)>
   <!ELEMENT value (#PCDATA)>
   <!ATTLIST configrecord version CDATA #IMPLIED>
   <!ATTLIST configgroup name CDATA #IMPLIED>
   <!ATTLIST configgroup instance CDATA #IMPLIED>
   <!ATTLIST configitem name CDATA #IMPLIED>
   <!ATTLIST configitem instance CDATA #IMPLIED>
   <!ATTLIST value name CDATA #IMPLIED>
]>
<configrecord version = "0.1.0.1">
   <configgroup name = "Line" instance = "1">
      <configitem name = "Name">
         <value></value>
      </configitem>
      <configitem name = "Interface">
         <value>RS232</value>
      </configitem>
      <configitem name = "State">
         <value>Enabled</value>
      </configitem>
      <configitem name = "Protocol">
         <value>Mux</value>
      </configitem>
      <configitem name = "Baud Rate">
         <value>9600 bits per second</value>
      </configitem>
      <configitem name = "Parity">
         <value>None</value>
      </configitem>
      <configitem name = "Data Bits">
         <value>8</value>
      </configitem>
      <configitem name = "Stop Bits">
         <value>1</value>
      </configitem>
      <configitem name = "Flow Control">
         <value>Hardware</value>
      </configitem>
      <configitem name = "Gap Timer">
         <value>&lt;Four Character Periods&gt;</value>
      </configitem>
      <configitem name = "Threshold">
         <value>56 bytes</value>
      </configitem>
      <configitem name = "Push">
         <value></value>
      </configitem>
   </configgroup>
   <configgroup name = "Line" instance = "Virtual_1">
      <configitem name = "Name">
         <value></value>
      </configitem>
      <configitem name = "State">
         <value>Enabled</value>
      </configitem>
      <configitem name = "Protocol">
         <value>Command Line</value>
      </configitem>
      <configitem name = "Gap Timer">
         <value>&lt;Four Character Periods&gt;</value>
      </configitem>
      <configitem name = "Threshold">
         <value>56 bytes</value>
      </configitem>
      <configitem name = "Push">
         <value></value>
      </configitem>
   </configgroup>
   <configgroup name = "Line" instance = "Virtual_2">
      <configitem name = "Name">
         <value></value>
      </configitem>
      <configitem name = "State">
         <value>Enabled</value>
      </configitem>
      <configitem name = "Protocol">
         <value>Trouble Log</value>
      </configitem>
      <configitem name = "Gap Timer">
         <value>&lt;Four Character Periods&gt;</value>
      </configitem>
      <configitem name = "Threshold">
         <value>56 bytes</value>
      </configitem>
      <configitem name = "Push">
         <value></value>
      </configitem>
   </configgroup>
</configrecord>

Step 2 - Use mux to access CLI on Virtual Line 1

  1. Disconnect Tera Term and reconnect to the xPico 200 Series to access mux on Line 1.
  2. Type 1v1 and press ENTER to connect to Virtual Line 1 as instance 1. Note that mux does not echo input characters.
  3. Type 1sb~ and press ENTER to prepare to send data. The ~ is specified as the escape character.
  4. Type ?~ and press ENTER to prepare the ? CLI command. The ~ followed by a newline terminates the data. Note that a newline is not being sent to the Virtual Line 1 because one isn't needed after the ? command.
  5. Type 1p and press ENTER to send the prepared data.
  6. Type 1rb~2000 and press ENTER to receive data. You will see the results of the ? command.
  7. Type 1sb~ and press ENTER to prepare to send data again.
  8. Type config and press ENTER to prepare the config command with a newline. Unlike the ? command, the config command requires a newline.
  9. Type ~ and press ENTER to send the escape character and indicate the end of the data being prepared.
  10. Type 1p and press ENTER to send the prepared data.
  11. Type 1rb~2000 and press ENTER to receive data. You can repeat steps 7 through 10 to send CLI commands over mux to the Command Line on Virtual Line 1.

Step 3 - Use mux to access the trouble log on Virtual Line 2

  1. Type 2v2 and press ENTER to connect to Virtual Line 2 as instance 2.
  2. Type 2rb~2000 to receive data from the trouble log.
  3. If there is more data, repeat step 2 as necessary to receive additional data from the trouble log.