hardware  Quick Start

How to setup and communicate with a AMOS based module

» Posted on 7. Jun 2013

Related links:  PDS-ModulesCommands | Programmer | Interfacing


Hardware Quick-Start Guide


In this post the user will be taken through the steps how to connect a hardware containing AMOS as its operating system like a PDS module to a PC and how to start communicating with the hardware using a terminal program.

It is assumed that the desired hardware is connected to a COM port or USB port of the PC. PDS modules can be connected directly to a COM port using a PDS-to-Serial cable, or it may be connected to an USB port using a USB-to-Serial or a BSLcomLink adapter.

Before continuing, the user should know on which COM port the hardware is connected to the PC. The PC’s device manager window can help to find this data out:


If the PC has DB9 COM-port interface(s), then Communications Port (COMx) will appear the list. As shown in the figure above, if the hardware is connected directly to the COM port of the PC, then the only available option is the COM1. If  the PC has more than one communication port, then the user must know to which one the hardware is connected.

If a USB-to-Serial or the BSLcomLink adapter is used, then USB Serial Port (COMx) will appear in the list. As shown in the figure above, if the hardware is connected over USB to the PC, then the only available option is the COM11. Again if more than one USB Serial Ports are listed, the user has to find out to which one the hardware is connected.


Preparing the PC

A terminal program is needed to communicate with the hardware. In this example we use PuTTY as terminal application. If PuTTY is not installed already on the PC please download PuTTY to your PC and run the application. Following window should appear on your screen:


As shown in figure below, select first in the category windows on the left side the option “Session” if not already selected. Then fill the red information on your PC considering to use your COM port number not the one shown in the figure below! Check if “Serial” and “Always” options are selected as marked red, before saving this configuration.


This was the minimum setting required to establish a communication link to the hardware. But you may optionally follow the configuration settings bellow if you experience difficulties or you prefer to have same look-and-feeling of the terminal program as shown later in examples in this post.

Optional Configurations

In the Category Appearance you should change the Font to Fixedsys, 10-point as shown below. If your system doesn’t have the Fixedsys font, then use “Courier New, Regular, 10-point” as an alternative. Please check all other options to match the settings as shown below:


In the Category Keyboard please match all the settings same as shown below:


In the Category Colours follow the two screen-shots below configuring PuTTY on your PC:

Foreground color:


Background color:


In the Category Window follow the settings below:


In the Category Behaviour follow the settings below. Please consider to use the COM port number your hardware is connected to and not the Com number shown below: 


In the Category Terminal follow the settings below:


Then go back to the Category Session and save all changes. You should then see following screen-shot but with the COM port number, where your hardware is connected to:



Finally you are ready to open the terminal session. Click on the button “OPEN” to start the session.

You should now face into an empty terminal window. This can be changed easily! Just type reset into the terminal window. If everything was configured correctly you should see the welcome screen of AMOS with build version information and other actual system data:


 If you type list, then you will get a list of all actual available AMOS commands:


In the most cases when you type one of the listed commands without any parameters, you will get a brief help for the command you typed in and the syntax how to use the command. But this is not given for all listed commands; for example this is not true for the command reset.


Submit a Comment