1.0  Introduction

This module provides a two-way communications interface between a host laptop (or desktop) computer and any of the RoboBricks2 modules connected to the CAN Bus.  The WireHost module is a tremendously useful debugging tool since the user can exercise direct control of any connected module from his laptop computer.  Simple keyboard commands typed on the host computer can be sent to any connected RoboBrick2 module. Replies, if any, from the module are displayed on the host computer. Since the WireHost uses a J11 cable for communication and the Laptop uses a serial cable,  a DB9RJ11 module or an equivalent device is necessary to provide a physical interface between the  cable types.  The DBRJ11 serves no other purpose but to accommodate this physical interface.

2.0  Connecting the WireHost Module

Connect the WireHost module to the CAN Bus and use the DB9RJ11 to interface the RJ11 cable from the WireHost with the DB9 cable coming from the serial port of the laptop computer.  The microcontroller chip should be removed from the Controller28 module (same is true for other Controller modules) otherwise the microcontroller chip will be sending commands at that will interfere with the WireHost commands being sent from the laptop.

[picture 1  module alone;       picture 2, module connected to laptop and CAN bus.]

3.0  WireHost Communications

Some of the more useful commands used by the host computer are:

 Z  - Interrogates the CAN bus and lists all connected modules.

For instance, assume that an IO8, MiniMotor2 and an LCD32 module are connected to the CAN bus and host computer has established a communication with the CAN bus using a communication program such as Windows Hyperlink.  At the prompt, typing the command "Z" will result in the following information being printed to the host computer screen:

03:10 00 03 01 03 0C:"MidiMotor2-B" 07:"Gramson"
08:10 00 08 01 03 05:"IO8-B" 07:"Gramson"
20:10 00 20 01 03 07:"LCD32-A" 07:"Gramson"

The first two numbers shown for each module are that module's address given in hex notation.  For example 0x03 is the address for the MiniMotor2 module and 0x20 is the address for the LCD32 module.  The letter following the modules name identifies the module's revision number and the number (07) is the length of the next string (in this case "Gramson").

 Sxx - Selects Module xx for two way communication where xx is the module's Hex Address as shown in the chart below.  

A module must first be addressed before any communication between it and the host computer can take place.  The chart below lists each module's address number.  The hex addresses are show in red and are to be used with the Select Address  command S.   For instance, to establish communication with the LCD32 module, the command "S20" would be sent from the host computer.  and establish communication with the Shaft2 module, the command "S5" would be sent.  Communication can only take place with one module at a time so every time you switch from one module to another, you must send the appropriate address information first.

RoboBricks2 Module Types & Addresses