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.
Also referred to as the Index, they are unique for every event and can be from 00-99 events.
Event Definition
The Syrus 1 has 70 events and Syrus 2 has 100 events available for the user to confi gure. They may be de fined all at once in a con figuration script or they me be individually de fined at any moment as the user adds/removes functionality. The actual events’ de nitions of the unit may be consulted with the TAIP message >QED<. This will have the unit deliver the con figuration state of all events. An example of the returned confi guration on the TAIP console is: >QED< >RED00NV0;A00TD0&F00&+< >RED01NV1;A00!F03&TD1&F00&+< >RED02XM0;F03!TD2&F00&+< >RED03NV2;G00+< >RED04NV0;A00TD3&F00!&+< >RED05NV1;A00!F03&TD3&F00!&+< >RED06XM0;F03!TD3&F00!&+< >RED07NV0;A00U00&+;ACT=SSSU000< >RED08NV1;A00!F03&U00&+;ACT=SSSU000< >RED09U< >RED10NV0;A00U01&+;ACT=SSSU010< >RED11NV1;A00!F03&U01&+;ACT=SSSU010< >RED12U< >RED13U< >RED14U< >RED15U< >RED16U< >RED17U< >RED18U< >RED19U< >RED20NV0;A00C02&+< >RED21NV1;A00!C02&+< >RED22XM0;F03!C02&+< >RED23U< >RED24U< >RED25U< >RED26U< >RED27U< >RED28U< >RED29U< >RED30U< >RED31U< >RED32U< >RED33U< >RED34U< >RED35U< >RED36sV0;S00-;ACT=SGC02U< >RED37sV0;S00+;ACT=SGC02TC00010< >RED38U< >RED39U< >RED40sV0;F00+;ACT=SSSU001< >RED41sV0;F00-;ACT=SSSU011< >RED42U< >RED43U< >RED44U< >RED45U< >RED46U< >RED47U< >RED48U< >RED49U< You can see some events having a user-de ned TAIP action, diff erent routing options and many undefi ned events (having a \U” (for undefi ned) after the event ID). For more information on how to interpret this reading as well as how to create such con figuration refer to the ED message.
We call the first letter after the start of a command the Qualifier
There are 3 possible Qualifiers: Q, R, S:
Q for Querying/Asking the device something
S for Setting/Configuring the commando on the device configuration
When you finally send something, the Syrus Responds to the command you send, confirming that the device received the command.
Q is used whenever we want to ask the device something, in the example above the command >QVR< can be broken down as:
>QVR< – Q is the Qualifier it stands for Query, VR is the command, there is no structure to this command
We are basically Querying or Asking the device for the Firmware version information. Since VR is the command, we can look this up in the Syrus Manual and confirm the results once we send the command to the device.
Using Syrus Desk we will receive a response similar to:
>RVR;2.0.60;ID=356612021234567<
Notice how the string starts now with R – standing for Response, followed by the command – VR, and finally the content of the response, the Firmware Version in this case (2.0.60) followed by the ID of the Syrus – IMEI. Syrus successfully responded to our Query of Firmware Version.
Webservices refers to the Pegasus Gateay interaction via an API of communication.
API and all relevant information can be found in your Pegasus demo or actual site.
Virtual Private Network – basically it is assigned by the network operator – (cell phone provider for the SIMs) and it is a method of accessing a network (any host IP address ) without having access to the internet.
Trimble ASCII Interface Protocol or TAIP is what we call the Syrus programming/configuration language (>COMMAND<).
Syrus Watch [SW] is a diagnostic server that we have dedicated to all the Syrus. Every customer should have access to their SW account. With the help of SW we can proactively see which devices are about to fail. Syrus GPS devices connect to Syrus Watch every 24 hours. Please see Syrus Watch for more information…
Syrus Desk is the Syrus device programmer that can help you program the device and automatically create quick script configurations. It also features a quick status of the Network and GPS conditions once connected.
A server is a system (software and hardware) that responds to requests across a computer network to provide, or help to provide, a network service. In our industry it usually refers to any endpoint system (software and computer) where AVL devices report to.