# Devices

In Kalipso, each Project has to be associated with a Terminal. Kalipso already has a list of predefined Terminals that can be used on your Projects. It’s possible that you may have to add a Terminal of your own.

![](/files/-MBJ23HT3y-09iIVIhqE)

* **Group** - A Terminal can be associated with a customized group. For instance, you can define manufactures as groups. Kalipso offers a set of start terminals, such as "Casio", "Honeywell", among other recognized brands. These are system groups. Choosing a specific group the information in the table below in the window changes showing the specific data for that group.

A Group can be used to organize Terminals. A Group is an abstract identity. You can use it to group Terminals by manufacturer or anything else.

{% hint style="info" %}
System groups are non-editable .
{% endhint %}

In addition to the suggested groups, it is possible to create a new group. For this purpose, a new group can be added by clicking on the icon on the right.

In the same window you can find four buttons: add, edit, duplicate and delete. These buttons allow the management of the terminals in the logic of the objective of each button.

Only after creating a new group is it possible to edit or delete it.

### New group

When you click to add or edit a group, the following window appears.

![](/files/-MBKFFS2c2pWFIVUpW2K)

On the right side are three buttons that allow you to edit an existing group, add a new group or delete a group (except if the group is one of the pre-installed ones available in Kalipso).

In the same window is a table with the following basic data:

* **Name** - Name of the group.
* **Type** - It is usually just terminals.
* **Description** - Brief description of the terminal group.

To add or edit a group a new window appears:

![](/files/-MBKFwJ0Hz1t_LsB8MQn)

The options are:

* **Name** - Name of the group. The group name cannot contain spaces.
* **Description** - Brief description of the terminal group.
* **Image** - If you want, you can add an Image to your group, to better identify it.

### Add or Edit a device

![](/files/-MBKK4yD83pq7NgWh3zN)

#### Tab - General

*Identification*

* **Name** - Name of the device.
* **Group** - Area where you can associate with a pre-existing group or create a new one.
* **Description** - Terminal description.

*Details*

* **Ratio** - You can define the ratio in pixels or auto
* **Operating System** - Write the Terminal’s Operating System. It’s informative, no interference with your Project.

*Screen*

* **Width** - Width of the screen (to check Terminal definitions or use “Get Screen Dimensions” Action).
* **Height** - Total height of the screen (to check Terminal definitions or use “Get Screen Dimensions” Action).

*Bar's Height*

* **Title Bar** - Windows title bar height
* **System Bar** - System bar height

*Scroll Bar*

* **Thickness** - Although this value is filled by default, you can use “[Get Screen Dimensions](/kalipso5/developing/form/actions/actions-description/group-others/get-screen-dimensions.md)” Action to know this value.

#### Tab - Keys

Each Terminal has a different set of Keys. These Keys can be used as [Events](/kalipso5/developing/form/controls/events.md). This way, you can define a Key to trigger [Actions](/kalipso5/developing/form/option-window/actions.md). Using the “Keys.exe” application on your PDA, you can know what code is associated with each Key. To define a Key, insert its Name and Code. Also, you can load the Operative System’s default Keys.

![](/files/-MBKaCdxb-W8J7w1h4d4)

#### Tab - Image

If you want, you can add an Image to your Terminal, to better identify it.

![](/files/-MBKauSmhPgv97wmYK0C)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://doc.sysdevmobile.com/kalipso5/using/environment/file/devices.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.