Cellocator compact инструкция

У нас вы можете скачать книгу cellocator compact инструкция в fb2, txt, PDF, EPUB, doc, rtf, jar, djvu, lrf!

The communication port is closed. This software provides the ability to: Incoming messages log, Decoded messages information, and a Control interface menu bar.

Communication Center Main Window 5. Each incoming message entry includes the type of message received and the source: This window also displays various action results. In the case of a transmission from the Communication Center to an end unit, an entry indicates the transmission results: For a complete list of transmission result code refer to the Cellocator Wireless Protocol document. The information is shown as a list of messages that can be expanded to show the data they hold.

Right click on a line to shrink or expand it. The basic text of the message which includes the kind of message it was designed to decode and the type of data shown in the message. The definition information has its source in the Telemetry. Do not change the definitions of this file. Changes can cause file corruption. A set of buttons and tabs in the Control interface menu bar provides the user with tools to send commands to the units. Dedicated buttons used to send status and reset commands.

The commands structures are defined in the Commands. Activates a drop down menu with commands defined in the Commands. Please refer to the Cellocator Wireless Protocol for additional information. Activates the Custom Commands window which allows the user to send commands, without the need to re-set the Commands.

A user can add a custom command in the form of a hexadecimal string in the following format: Determines if a default header, defined in the Commands.

Allows the user to add an 8-bit additive checksum or a 16bit cyclical redundancy check CRC16 at the end of the custom message nothing appears after this value. Allows the user to add a bit authentication code at any specified position, relative to the user custom hex string.

Allows the user to add the unite number, as a 32 bit unsigned integer, at the position specified. The position is relative to the user custom hex string. The Communication Center creates a log file messagelogfile.

Messages can be decoded from the log file or a specific message Hex string can be decoded. A hex string can be copied from the messagelogfile.

The MCGP header, at the beginning of the message, is not included. Every message that the Communication Center receives is written to the messagelogfile. The file can be loaded by clicking on File and selecting the relevant file.

Decode String Window 5. The user can add the unite number, as a bit unsigned integer, at the position specified. When this checkbox is clicked every packet command that is send from the Communication Center is sent without a command numerator field.

Clicking on Programming opens the OTA Programmer window Figure 28 which display the parameters data blocks for modification. Cellocator Compact Fleet Evaluation Manual commands are necessary to program several parameters from several blocks. When values change is completed, a programming message is sent to the unit specified in the Unit Number and the Address fields. After updating the unit a Reset Command must be sent to unit.

The Parameter Library Explorer opens Figure The Parameter Library Explorer Window 2. Set the relevant parameters to program or click Program all parameters. Close the Parameter Library Explorer. Select the communication protocol in the protocol field. Click Reset unit after programming. Press Send to program the unit. When checked, it activates the CAN Parameters window. The window is also activated when the Communication Center receives a type 9 message.

The CAN parameters can be loaded from an ini file. The CAN trigger that activated the transmission is listed with the sensor to which it is linked. It is displayed with the sensor to which it is linked. To create an ini file with CAN parameters use the Cellocator programmer.

CAN Parameters Window 5. When checked the Forward Data window is displayed. Various parameters can be set to control the type of message and format that is sent and received to and from the MDT.

When checked, the Garmin window is displayed. In the Command drop-down list parameters can be set to control the type of message and format that is sent and received to and from the Garmin. Clicking on the Units List check box activates the Unit List window. In this window the units that have made contact with the software, by sending at least one message, are listed.

This function is not implemented. When checked, it activates the Messages Screen window. The history of all received messages is displayed. Double clicking on any message shows it in the main window if the Unit Number field matches the one in the message. Used to lock the main window to the current message. Messages still continue to accumulate in the Communication Center buffer but they are not presented in the main window. Update unit number if necessary: If checked, double clicking on a message in the Messages Screen window will update the Unit Number field in the main window to match the one in the selected message.

When checked, a user can filter only one Unit to be displayed in the Communication Center. Page 48 of Cellocator Compact Fleet Evaluation Manual 6 Additional Software Components This section describes software components which are included in the evaluation kit, in addition to the Programmer and the Communication Server which have been described above.

The simulator is pre-configured for use in the event that actual GPS data is not available, due to a lack of access to open skies. The following elements are configurable: GPS Simulator Window 1. Location details are displayed in degrees, minutes and seconds, or as a floating point decimal value. Sets the quality of the received GPS signal. This information simulates the quality of the signal received and the user can verify if a unit will confirm the acceptance of a signal in accordance to the configuration.

The location can be defined for testing purposes. The elevation of the vehicle, in meters. The direction of the vehicle in degrees. The speed of the vehicle in kilometers per hour. If Ground Speed is more than 0, the location will change accordingly. A log is generated and saved on disk. Data is transmitted in actual UTC time. A log is generated. When checked, a GPS package is sent every 1 second. This is configurable but it is recommended to work at 1 second intervals.

An activities log of received messages is displayed. Prerecorded NMEA data can be used for testing purposes. In Automatic management mode, the simulator waits for a unit command in order to start sending GPS updates every second, exactly as the real unit does. The tool is useful for software testing and simulation of movement of multiple units.

All selected protocol messages can be displayed by clicking on the arrow in the bottom right corner. A user can define a target IP and target port of the actual server. The user can change input states and define the Dallas number and view the output status. A user can set the battery levels. The user can also use live MDT. To test GPRS communication, perform the following steps: Enter the unit number.

The unit number is an imbedded serial number programmed into the unit. This number can be found on the label on the unit casing. Verify that GPRS dial up setting are correct: Verify that the first message arrives from the unit.

It is displayed in the left hand text box: A response should be received from the end unit. Verify that the appropriate led on the tester lights. In the same way deactivate the siren. The following window opens: Define the COM port. In the drop down list of modems, select the appropriate modem.

In the GSM Signal Quality window, verify that the system reports successful initialization of the terminal modem. If so, the SMS module is properly configured. In order to send an SMS message to the unit, go to control interface and check the box: It requires a special listening cable the Interconnection Recording Cable.

To setup the listening cable, perform the following steps. Connect the listening cable to the Compact unit as showed in Figure Setting Up the Listening Cable 2. Connect the listening cable to a commercial 12VDC power source. Connect the two serial connectors on the listening cable to the PC being used for testing purposes. Start the Communication Logger software Figure Make sure that Record Binary Data is not checked. Connect the Compact Unit to power and turn it on.

After the application has run for a few minutes, a file, communicationlog. Zip the file and send it to Cellocator. Communication Logger Window 6.

Each parameter is also accompanied with a short description, making it easier to understand, as well as a link to an online help file. It also helps diagnose problem due to faulty PL settings.

To display the results of comparison between two PL files, perform the following steps: Open Pl file 1 Open PL file 2. In the Compare Results window, the differences between parameters on the PL files are show according to the following criteria: Displayed parameter s with identical address but different name.

Displayed parameter s with identical name but different address. Displayed parameter s that exist in one PL file but do not exist in the other one. Change the name of PL file and save it. Remove or replace word s of Comment or Help link from all parameters in a PL file. For example, in order to remove the links from a PL file, go to drop down menu select Help, leave the remaining fields empty and click Replace.

Software and hardware details are provided in accordance with the hardware uploaded. The selected PL is automatically configured and is displayed in the Configuration Settings window. For detailed technical specifications, please refer to the Programming Manual and the Cellocator Wireless Protocol document which can be downloaded from the Pointer website.

It is based on the Compact Fleet sequence with the relevant additions for the Compact Can. Beside the communication parameters, the specific parameters defining what CAN information should be captured and sent to the control center, is also defined. Refer to Section 4 of this document. Acceptance test to validate that the evaluation environment is properly functioning refer to Compact Fleet Evaluation Manual Section 3. This information, together with the information provided in this document, is required to acquire a comprehensive understanding of the Compact CAN evaluation environment.

CelloTrack products support tracking, communication, and GPS location-based features. The FMS standard provides fleet managers with access to important vehicle information.

Using the provided interface users can: The Compact CAN unit can be delivered in several configurations according to the following table: It describes how to install and verify the proper functioning of the Compact Fleet installation kit elements with additional information relevant to the Compact CAN installation kit elements. To download the manual, access the Pointer Website www.

It describes every byte of the incoming and outgoing packets, which can be sent or received by the unit over-the-air. These, of course, are in addition to those provided in the Compact Fleet Evaluation kit. It also includes a GSM receiver. Unzip the files to the FMS Transmitter folder.

To setup the FMS Transmitter, perform the following steps: Open the port by clicking Open. To load a file and send messages, perform the following steps. In the Proprieties box, the log indicators light green replacing red when the correct format is detected.

The total number of CAN messages being sent is displayed. Click Show Messages in order to view, in the Sending window, the messages being transmitted. To create an identifier and send such messages, perform the following steps: In the following example, Brake has been selected.

To load and send messages, perform the following steps: The PGN field is filled in automatically in accordance with the selected parameter. Click Send to send the FMS information. To send user-selected data, perform the following steps: Set the desired parameters in the Automatic Message window. All of the selected information is transmitted continuously at the repetition rate defined in the FMS standard. There are two versions of Compact Can units: In the You want to use the custom sensors file?

A user can build a new filter. Filters that have been pre-programmed can be loaded. Design of triggers will permit the unit to react to certain conditions of the information extracted to sensors. Complex triggers involve the occurrence of one or two conditions for more than a predefined time period. A template defines the contents of a message dealing with a particular event. This function deactivates all defined parameters. This command issues a unit interrogation.

The unit replies with its ID. After the upload, the filters and triggers can be monitored on the main window of the Can Filter Editor. Filters or triggers that are inactive are not displayed. After reprogramming, the unit must be reset by disconnecting the power or by command. Select a sensor from the Filters List. A Selected sensor is automatically assigned with an index. To define a report for a sensor, perform the following steps: The templates window opens.

The Sensor page opens. The example below shows a template with Speed and Odometer sensors, as well as the GPS information selected. Click OK to save the template. The values of all sensors in that template, in addition to the optional GPS information, will be transmitted to the server when an event is triggered.

An appropriate template with up to 3 sensors must be prepared for these cases. Simple triggers are selected in the Trigger window.

The Trigger window opens. Select the Input Sensor from the dropdown list of those sensors that were previously defined. Select one of the Input Processing modes: More than one condition trigger can be assigned to a single sensor. The trigger will be activated according to the Threshold value selected.

The Threshold Value is the defined level which, when exceeded, activates a trigger. Trigger on each exceeding update policy reports on each measured value update which exceeds the specified Threshold Value.

It is recommended to deploy the Single trigger per exceeding update configuration so that the network will not be flooded with information and communication costs will be excessive. To detect over speeding, assign a threshold trigger and maximum value threshold type. Select the maximum allowed speed in the Threshold Value parameter and a "single update per exceeding period" for report policy.

Note that because the speed is reported on the CAN bus, 10 times a second, generating an event on each update in excess of the maximum permitted speed— rather than per session — is not recommend as done as it can result in excessive communication costs.

In fact, it is not actually the time that is counted. The trigger occurs after a preprogrammed number of specific sensor updates measurements. Since the frequency of updates is normally defined in the CAN protocol, it is designated as a period. The trigger has been disabled. Real-time values of all defined filters are sent each time a trigger is activated for each of the sensors selected a maximum of 8 or This type of message is not recommended because: The message is of type 9, sub data type 2.

The message is of type 9, sub data type 3. If GPRS is not available, the information is lost. A message is limited to three sensors plus GPS information. To set a trigger output, select a trigger from the Trigger Outputs dropdown box.

Click OK to activate the defined trigger. A maximum of four templates can be defined. The Templates Click on the window is displayed. Select from the existing templates Template 0, Template 1, Template 2 by clicking on the relevant radio button. If the existing templates are not suitable, close the Trigger window and define the required template in accordance with the instructions in Section 4.

Reopen the Trigger window and select the new template. A complex trigger can be defined based upon a subset of the mentioned parameters e. Complex triggers are selected in the Trigger window. The maximum number of complex triggers is 8 in both 8 and 25 sensors version.

The time counter of each trigger is up to seconds. The same single trigger can be used for more than one complex trigger although it is not supported yet by Cellocator tools. The complex trigger input can only be constructed from triggers of the "Threshold" type, with a single trigger per exceeding period. Each simple trigger can be set as either part of complex trigger or simple trigger.

The same trigger cannot be defined simultaneously as part of both a complex trigger and a simple trigger. To set a complex threshold trigger, perform the following steps: Select sensors for Trigger 1 and Trigger 2 in the dropdown lists and, optionally, an Additional Sensor. Select the Trigger output type: The complex trigger interface allows setting two simple sensors and the time of simultaneous activation to generate a trigger. Since the template of logged complex triggers is invariable, the form lets the operator assign one additional sensor.

The example demonstrates a complex trigger, setting the Speed and Engine RPM simultaneous violation for 15 seconds. The following example presents a screenshot of the configured complex trigger screen. To create a new SAE-J filter, perform the following steps: The filter will appear on the main window of the Can Filter Editor. The following is the most important displayed information. Active or inactive filter. Start bit information to be extracted.

Bit length to be extracted. A maximum of 8 complex triggers can be defined for each unit. Please refer to the following table for details.

INI file relates the indices of the sensors and triggers reported by the CAN messages to the actual names. Само по себе устройство старое.

Да не, какая разборка. Это не родная деталь, а сигнализация. Работает или работала , насколько мне известно по принципу спутниковых сигналок тех времён не как сейчас, когда всем доступны мобилы интернет, и как со старлайном — ты сам себе диспетчер то есть с диспетчером в конторе. А надпись могла быть от установщика или хз. Да вообще на фига на разборке писать на детали название города в котором собственно я и купил авто.

Судя по состоянию, она уже не одного владельца порадовала, последний обрел ее в славном городе Петра, куда ее и адресовали, о чем свидетельствует автограф. Cars Experience Communities Read most popular. Yaroslav76 last online 1 day ago. Comments 8 Only registered users can participate in discussions. Sign Up Login with.