Documentation for Intellect 4.11.0-4.11.3. Documentation for other versions of Intellect is available too.

Previous page Next page


You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

Messages sent to the core have the following syntax:

CORE||DO_REACT|source_type<OBJECT TYPE>,source_id<OBJECT ID>,action<ACTION> [ ,params<NO. OF PARAMETERS>,param0_name<PARAMETER NAME_0>,param0_val<PARAMETER VALUE_0>]

Below is the syntax of messages that contain two parameters.

CORE||DO_REACT|source_type<OBJECT TYPE>,source_id<OBJECT ID>,action<ACTION>,params<2>,param0_name<PARAMETER NAME_0>,param0_val< PARAMETER VALUE_0>,param1_name<PARAMETER NAME_1>,param1_val<PARAMETER VALUE_1>

The message parameters are described in the table below.

Parameter

Description

source_type<obj>

Object type (see the DDI file ( [OBJTYPE] section) )

source_id<id>

The object ID set when creating the object in Intellect (see Intellect's settings tree)

action<react>

Action (see the DDI file (the [REACT] section) )

params<number>

The number of parameters passed, in decimal format

param0_name<str1>

Parameter name

param0_val<str2>

Parameter value

To check the network, you can use the <trash:N> parameter, where N is the length of the parameter in bytes. As a result, a text string of a given length will be generated in the message, containing numbers and Latin letters. The parameter name can be anything. For example, if you add the following parameter to the message

param1<trash:128>

the following text string will be generated in response

param1<88n9ESCAFyBfHyXzIoPpOF1GirSmlMJ1Ahh9oYZDIQou2RgWY0jXlaL2HhaX9ZY2oKfkQYLuPLg8bGNQK6OumvQjVp1G7BEt1wFsw6FApzIZ3NbBUJNCKnP335OlgEwN>

Note

For working with DDI files, we recommend using the ddi.exe utility (see Section Using the ddi.exe Tool to Work with DDI files).

Example. Sending a message to switch the telemetry to preset mode 4.

CString msg=

“CORE||DO_REACT|source_type<TELEMETRY>,source_id<1.1>,action<GO_PRESET>,params<2>,param0_name<preset>,param0_val<4>,param1_name<tel_prior>,param1_val<2>”;

 SendMsg(id,msg);

  • No labels