New Search

If you are not happy with the results below please do another search

21 search results for:

1

Firmware

/in

Firmware refers to the source code that the device is programmed in. For the Syrus it’s the JAR and JAD – Java Files.  

2

Protocols

/in ,

A protocol is the special set of rules that end points in a telecommunication connection use when they communicate. Protocols specify interactions between the communicating entities. For Syrus it refers to TAIP Protocol.

3

Extended Tags

/in ,

This message allows the creation and con guration of up to three sets of information tags to be used by an event having the Message ID quali er set to A, B or C. This will make such an event generate an EV reporting message with extra information tags as described on the EV message section. For […]

4

Actions

/in ,

A valid TAIP message without the opening (>)and closing (SED00NV0;F00+;ACT=SSSXP21< The action above is ACT=SSSXP21, this means that when F00+ (Ignition is ON) we are going to automatically execute SSSXP21. There are two types of actions ACT & XCT, when the Event Handling|Message Routing is Silent – we do not worry about which one to […]

5

Event Trigger

/in ,

A trigger is determinated with the logical combination of several situations (also called signals). A logical combination is basically an equation (speci fically: a boolean equation) that combines signals (situations) with the logical operators AND, OR and NOT. In Syrus, these boolean equations use the postfi xed notation, meaning that the operator is at the end of […]

6

Boolean Logic

/in ,

Logical operation used to combine signals: &: AND |: OR !: NOT

7

Signals

/in ,

As described in the previous section, the event machine takes actions like reporting or switching outputs whenever a user de fined trigger goes off . This trigger is confi gured by the user with the logical combination of situations. A situations makes reference to a vehicle state which is in fact represented by signals and their state. Syrus’ […]

8

Destination Address (DAs)

/in ,

A Destination Address is a user-de fined group of Destination Points. This enables some reporting commands to route their report to several destinations at the same time with a single de finition. Up to 10 (0 to 9) DAs maybe de ned. Refer to the DA message for more information. This command enables the user to group a […]

9

Message Identifier

/in ,

Alphabetical characters used to identify messages. The letter V is the standard’s one. This message allows the creation and configuration of up to three sets of information tags to be used by an event having the Message ID qualifier set to A, B or C. The message has the following format: A[BBB…] A: Identifier of […]

10

Event Handling|Message Routing

/in ,

Message routing: N: Normal. Route the Event Message to the speci fied Destination Address. X: Serial Port. Route the Event Message to the unit’s serial port only. S: Signal only. Do not generate an Event Message. The event’s signal still follows the event’s state. U: Undefi ned. Delete the event’s de finition.