Specifications

i50 Manual (5.10)

Page 22

www.datalinksystemsinc.com

7.2 Programming

When the i50 Programmer starts for the first time, it will ask which PC COM port should be used to

connect to the i50. This can be changed at any time using the Connection/Select Port menu. Once

the port is selected, the programmer will attempt to open the connection and send programming

commands to the i50. If the port is open at the time the programmer application is closed, it will

automatically be opened the next time the programmer starts. The Open Port and Close Port buttons

can also be used to open and close the port manually.

Connect the i50 to the PC COM port, and reboot the i50 to enter programming mode. A reboot can

be forced by removing power briefly, or by using the Reboot button on the programmer toolbar. Note:

the reboot button only works when the PC is connected to the device’s RJ-45 Program connector. If

successful, the programmer will show a “Got settings OK” message, along with the detected firmware

version and any optional features.

Optional features can be included in custom firmware, depending on customer requirements and

available firmware space. The current options include:

Accel: 3D accelerometer support

AES-256: Encryption available on the i50C only

PDT: Support for PDT-100 satellite terminal

GS: Globalstar 1620 support

Dial-up: Allows a third-party to connect to an i50 serial port using PPP

RF: RF modem support

OBD-II: External OBD-II engine monitoring

Driver: Driver ID features (when using Garmin terminals)

Wi-Fi: Internal Wi-Fi module

No Waypts: Waypoints turned off

Grace: Support for Grace pagers

Kenwood: Enables interface to NXDN/Fleetsync radio systems

Garmin: External Garmin terminal for messaging and route planning

Signs: Transparent data port modified to talk to portable road signs

NTCIP: Transparent data port modified for NTCIP signs

Amsig/NTCIP: Transparent data port can send to portable or NTCIP signs.

The programmer automatically reads the asset’s settings, which are shown under the “Current Asset

Value” column. If no local data exists, the programmer automatically creates a local copy that can be

modified by a user, shown under the “New Value” column. Figure 4 shows the settings window where

two values have been modified by a user. Any settings that do not match the asset values are shown

in red, and a red bar is displayed to warn of the mismatch. This provides a quick method of tracking

changes before they have been sent to the asset. At any time the current asset values can be copied

into the local values using the Copy Asset Values button, erasing any changes the user has made.