COBHAM SAILOR 6194 Installation And User Manual
  1. Manuals
  2. Brands
  3. COBHAM Manuals
  4. Control Unit
  5. SAILOR 6194
  6. Installation and user manual

COBHAM SAILOR 6194 Installation And User Manual

Terminal control unit
Hide thumbs
Table of Contents

Advertisement

Quick Links

SAILOR 6194
Terminal Control Unit
Installation and user manual

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the SAILOR 6194 and is the answer not in the manual?

Questions and answers

Related Manuals for COBHAM SAILOR 6194

Summary of Contents for COBHAM SAILOR 6194

  • Page 1 SAILOR 6194 Terminal Control Unit Installation and user manual...
  • Page 3 SAILOR 6194 Terminal Control Unit Installation and user manual Document number: 98-131593-D Release date: November 18, 2013...
  • Page 4 Thrane & Thrane A/S is trading as Cobham SATCOM. Copyright © 2013 Thrane & Thrane A/S. All rights reserved.
  • Page 5 Safety summary The following general safety precautions must be observed during all phases of operation, service and repair of this equipment. Failure to comply with these precautions or with specific warnings elsewhere in this manual violates safety standards of design, manufacture and intended use of the equipment.
  • Page 6 Personnel installing or servicing the system must be properly trained and authorised by Cobham SATCOM. It is important that you observe all safety requirements listed in the beginning of this manual, and install the system according to the guidelines in this manual.
  • Page 7 Related documents The below list shows the documents related to this manual and to this product. The manuals can be found in the Self Service Center at cobham.com/satcom under Service and Support. Document Ref. Title and description number SAILOR 6006 and SAILOR 6007,...

  • Page 9: Table Of Contents

    Table of Contents Chapter 1 Introduction The Terminal Control Unit ...............1 Chapter 2 Installation Unpacking ....................3 Installing the Terminal Control Unit ..........4 Outline drawing ..................6 Installing Ship Security Alert (SSA) buttons ......7 Installing Non-SOLAS Alarm Panels ..........9 Installing the Glonass option ............10 Chapter 3 Connecting cables Connector overview .................
  • Page 10 Table of Contents Use of Non-SOLAS Alarm Panels ..........46 Chapter 5 Scripting Introduction to scripting ..............47 What can scripts do ................48 Complete example of a Lua script ..........52 Chapter 6 Service Updating software ................59 Status signalling .................. 62 Setting a temporary fixed IP address ........

  • Page 11: Chapter 1 Introduction

    The power for the Terminal Control Unit is supplied through the CAN connector (extended input range 10.5-32 V DC). The Terminal Control Unit is supported by the ThraneLINK Management Application, a Windows program that provides easy monitoring and software update of connected Cobham SATCOM devices with ThraneLINK support.
  • Page 12 Chapter 1: Introduction The Terminal Control Unit...

  • Page 13: Chapter 2 Installation

    Chapter 2 Installation This chapter describes how to unpack, store and install the SAILOR 6194 Terminal Control Unit. It contains the following sections: • Unpacking • What’s in the delivery • Installing the Terminal Control Unit • Outline drawing • Installing Ship Security Alert (SSA) buttons •...

  • Page 14: Installing The Terminal Control Unit

    Chapter 2: Installation What’s in the delivery The following items are included in the delivery of the Terminal Control Unit: • Terminal Control Unit Terminal Control Unit • NMEA2000 Micro Device Cable, 6 m • Mounting tool for spring-loaded terminals •...
  • Page 15 Chapter 2: Installation Unit on a vertical surface, make sure the cable relief is facing down as shown in the picture below. Cable relief for CAN 2. Tighten the screws. 3. Connect all cables as described in Connecting cables on page 13 and fasten the cables to the cable relief with cable strips.

  • Page 16: Outline Drawing

    Chapter 2: Installation Outline drawing Dimensions are in mm Outline drawing...

  • Page 17: Installing Ship Security Alert (Ssa) Buttons

    Chapter 2: Installation Installing Ship Security Alert (SSA) buttons Placing the SSA buttons To fulfil the IMO requirement on covert activation, the alert button installation must be concealed using appropriate covert installation techniques. One of the alert buttons must be placed on the ship’s navigation bridge.
  • Page 18 Chapter 2: Installation 6. Pull the heat-shrink to the back of the board where the button is installed. 7. Shrink the heat-shrink with heat. For information on wiring, see GMDSS or SSA systems (SAILOR 6110 or SAILOR 6120) on page 21. For information on how to configure the SSA buttons, see Configuring SSA buttons on page 39.

  • Page 19: Installing Non-Solas Alarm Panels

    Chapter 2: Installation Installing Non-SOLAS Alarm Panels The Non-SOLAS Alarm Panel is used in Non-SOLAS Distress systems to send Distress alerts. You may use the SAILOR 3042E Alarm Panel. The Non-SOLAS Alarm Panel can be mounted on a wall or desktop. For information on wiring, see Non-SOLAS Distress systems (SAILOR 6150) on page 23.

  • Page 20: Installing The Glonass Option

    Chapter 2: Installation Installing the Glonass option An optional Glonass module is available for the Terminal Control Unit. The Glonass module enables the Terminal Control Unit to receive a Glonass signal and make it available to other parts of the system. Caution! Before removing the cover enclosing the electronic circuits, first make sure you are wearing a wrist strap connected to the work place.
  • Page 21 Chapter 2: Installation 3. Place the Glonass module over the four spacers and mount the four screws through the holes in the Glonass module and into the spacers. Tighten the screws to 1 Nm. 4. Connect the cable harness from the Glonass module to the connector J901 in the Terminal Control Unit.
  • Page 22 Chapter 2: Installation 6. Connect the internal connector on the antenna cable to the antenna connector on the Glonass module as shown in the drawing in step 4. 7. Mount the cover and fasten the screws to 1.5 Nm. For information on how to configure the Glonass module see Configuring the Glonass option on page 42.

  • Page 23: Chapter 3 Connecting Cables

    Chapter 3 Connecting cables This chapter provides a description of the connectors on the Terminal Control Unit and gives guidelines to cabling. It has the following sections: • Connector overview • Power control (X1) • CAN interface (X2) • RS-232 interface (X5) •...

  • Page 24: Connector Overview

    Chapter 3: Connecting cables Connector overview The drawing below shows the connectors on the Terminal Control Unit and the SD card slot for inserting an SD memory card. X5 and X6 are standard connectors for RS-232 (9-pin D-sub) and Ethernet (RJ-45), all other connectors are spring-loaded terminals.

  • Page 25: Power Control (X1)

    Chapter 3: Connecting cables Power control (X1) By default, when the system is powered on, the Terminal Control Unit and the connected mini-C Terminal are always on. If you want to change this behaviour, you must configure the X1 connector using a software command (Constant_On 0).

  • Page 26: Can Interface (X2)

    Chapter 3: Connecting cables CAN interface (X2) The Terminal Control Unit has one CAN interface (spring-loaded terminals) used for communicating with connected equipment, such as a Message Terminal and/or a mini-C GMDSS terminal. The CAN interface is located in the bottom left corner of the Terminal Control Unit as shown below. Do not connect the shield of the CAN cable to the chassis of Important the Terminal Control Unit, or to any other ship ground...
  • Page 27 Chapter 3: Connecting cables • In systems where CAN power is not available, you can connect your power supply or battery to pin3 PWR+ and pin 4 PWR- shown in the drawing on page 16, if the power supply is within the limits stated in General specifications for the TCU on page 65.
  • Page 28 Chapter 3: Connecting cables A double jumper, J1 in the drawing on page 16, connects a 120 Ohm termination for the CAN interface. If you have terminated the CAN connection elsewhere and want to remove the termination in the Terminal Control Unit, you must remove the jumper.

  • Page 29: Interface (X5)

    Chapter 3: Connecting cables RS-232 interface (X5) Overview There is one RS-232 connector, 9-pin D-Sub, on the Terminal Control Unit. The RS-232 (DTE) interface can be used for entering commands or running scripts on the Terminal Control Unit. Note The default setup for the RS-232 interface is 115200 bps 8N1. You must use this setting the first time you connect.

  • Page 30: Lan Interface (X6)

    Chapter 3: Connecting cables LAN interface (X6) Overview There is one Ethernet (10/100 MB) connector on the Terminal Control Unit. We recommend connecting to the slave unit, in order to reserve the free LAN connectors for user interfaces on the master unit. The Ethernet interface can be used to connect a computer and use the easyMail program supplied on CD with the Terminal Control Unit, the ThraneLink Management Application or a terminal program to access the...

  • Page 31: Ssa And Alarm Panel (X7 To X14)

    Chapter 3: Connecting cables SSA and Alarm Panel (X7 to X14) Some of the spring-loaded terminals can have different functions, depending on the system configuration. The function of the I/O pins are automatically configured to match the connected type of satellite terminal. Depending on the connected terminal, some of the I/O pins are preconfigured, and some of the I/O pins are configurable.
  • Page 32 Chapter 3: Connecting cables The Terminal Control Unit can connect up to 6 alarm buttons and 1 test button. The pin-out is shown below. The following spring-loaded terminals are used for the buttons: • SSA Alarm buttons: X7, X8, X9, X10, X11 and X12. •...
  • Page 33 Chapter 3: Connecting cables Note that there may also be a white wire in the cables for the SSA Alarm buttons. Do not connect the white wire from the red SSA alarm buttons - only from the Test button. Non-SOLAS Distress systems (SAILOR 6150) The multi-purpose interface on the Terminal Control Unit can also connect to Non-SOLAS Alarm Panels e.g.
  • Page 34 Chapter 3: Connecting cables With 2 TT-3042E Non-SOLAS Alarm Panels (Inmarsat C Distress Alarm Box): Each Non-SOLAS Alarm Panel uses two connector blocks as shown in the drawings above. Note that X10 pin 1 is shared by the two Non-SOLAS Alarm Panels.
  • Page 35 Chapter 3: Connecting cables Non-SOLAS Alarm Panel Connect the Non-SOLAS Alarm Panel(s) as shown below: Buzzer and Mute button You can also connect a buzzer and a Mute button to X14. The buzzer indicates incoming or outgoing Distress alerts. The buzzer must be self-driven (make a sound when connected to power) and it must be working at 3.3 V DC with a max.

  • Page 36: Grounding The Terminal Control Unit

    Chapter 3: Connecting cables Grounding the Terminal Control Unit The base plate of the Terminal Control Unit must be connected to ship ground in one of two ways: • Mount the Terminal Control Unit on a conducting surface connected to ship ground, or •...

  • Page 37: Cable Requirements

    Chapter 3: Connecting cables Cable requirements The following requirements apply to the cables used with the Terminal Control Unit. Before using the Terminal Control Unit for the first time, check that all cables are correctly wired and fastened. CAN cables The CAN cables must meet the requirements in the NMEA 2000 standard.
  • Page 38 Chapter 3: Connecting cables • The cable length from each device to the CAN T-connector must be maximum 6 m. • The total length of the backbone must be maximum 200 m. • For the distance between the mini-C Terminal and the Power Supply Unit, refer to the installation manual for your mini-C System.

  • Page 39: Chapter 4 Using The Terminal Control Unit

    Chapter 4 Using the Terminal Control Unit This chapter provides a description of how to set up and use the Terminal Control Unit Terminal Control Unit. It has the following sections: • Status indicators • Configuration • Use of SSA buttons •...

  • Page 40: Status Indicators

    Chapter 4: Using the Terminal Control Unit Status indicators Light indicator positions The Terminal Control Unit has a number of light indicators for signalling status and errors/warnings. The indicators show status of power, position and logon as well as status of the Terminal Control Unit and the satellite terminal and program status.
  • Page 41 Chapter 4: Using the Terminal Control Unit The drawing below shows the position of each light indicator. 1. Terminal Control Unit Power/sleep mode, a green indicator 2. Satellite status, a green/red/yellow indicator 3. Position signal, a green/red/yellow indicator 4. Program status in SAILOR 3027, a green/yellow indicator 5.
  • Page 42 Chapter 4: Using the Terminal Control Unit Light indicator functions Terminal Control Unit Power/sleep mode indicator Behaviour Meaning Steady green Terminal Control Unit is on. Flashing green Terminal Control Unit is in power save mode, see Setting up software controlled power management on page 40).
  • Page 43 Chapter 4: Using the Terminal Control Unit Position signal indicator Behaviour Meaning Steady green 3D position fix obtained. Steady yellow No position fix - satellite visible. Steady red No satellite found. Flashing green 2D position fix obtained. Terminal Control Unit is in standby mode. Program status in SAILOR 3027 indicator Behaviour Meaning...
  • Page 44 Chapter 4: Using the Terminal Control Unit Satellite terminal status indicator Behaviour Meaning Green Satellite terminal is on (including sleep mode). Yellow Warning. If a Message Terminal is connected you can access the list of active warnings and errors by selecting the icon in the top right corner of the display.

  • Page 45: Configuration

    Chapter 4: Using the Terminal Control Unit Configuration Using commands Using the com or serial port you can send commands to the Terminal Control Unit or SAILOR 3027. PC with SAILOR 6194 SAILOR 3027 terminal tt6194:/$ can1:/$ Mini-C program To access the Terminal Control Unit or SAILOR 3027 settings using commands, do as follows: 1.
  • Page 46 Chapter 4: Using the Terminal Control Unit Per default the password is empty. To change the password type: password sysadm, then enter and confirm the new password. 5. Type the commands for Terminal Control Unit or SAILOR 3027. To list all commands For a list of all commands for the Terminal Control Unit, type: tt6194:/$ help The commands for the currently selected user mode (normal or sysadm)
  • Page 47 Chapter 4: Using the Terminal Control Unit Note Once auto connect to mini-C is enabled, you can only access the mini-C, but not the TCU if you use the serial connection. To disable auto connect, connect via the LAN interface. Then type: tt6194:/$ auto_minic 0 Automatic Mini-C prompt is disabled...
  • Page 48 Chapter 4: Using the Terminal Control Unit Use DHCP IP address : 0.0.0.0 IP mask : 0.0.0.0 IP gateway : 0.0.0.0 IP DNS : 0.0.0.0 ISO address Unique number : 0x00211628 Dev. inst. Dev. class inst. : 0 Host To use a DHCP server It is recommended to set Use DHCP to on (1).
  • Page 49 Chapter 4: Using the Terminal Control Unit Reset button for IP address The TCU has a button for setting a temporary fixed IP address. When you push the button, the IP address of the TCU is temporarily set to the default value (169.254.100.100).
  • Page 50 Chapter 4: Using the Terminal Control Unit Configuring SSA button type There are two types of SSA buttons. You can distinguish between the two types by the color of the test button: • Standard activation: Covert alert buttons are latched red buttons. Test button is green.
  • Page 51 Chapter 4: Using the Terminal Control Unit behaviour with a command, so that you can use a switch connected to X1 for switching between on and standby. For details on the connector X1, see Power control (X1) on page 15. •...
  • Page 52 Chapter 4: Using the Terminal Control Unit Configuring the Glonass option The Glonass module can be set up in several ways: • Position data are based solely on the Glonass module • Position data come preferably from the Glonass module •...
  • Page 53 Chapter 4: Using the Terminal Control Unit To set navigational input mode Navigational input mode Command can0:/$ cfg -pm 1 To use preferred input only To use 3D fix over preferred input can0:/$ cfg -pm 2 can0:/$ cfg -pm 3 To use preferred input in 2D fix, even if 3D fix is available To use input with best Pdop value...

  • Page 54: Use Of Ssa Buttons

    Chapter 4: Using the Terminal Control Unit Use of SSA buttons You can connect up to 6 SSA covert alert buttons and one SSA test button to the Terminal Control Unit. Do not push the red covert alert buttons, unless you are Important under attack or threat.
  • Page 55 Chapter 4: Using the Terminal Control Unit Sending an SSA test message The SSA test button is green or yellow and should be placed close to the red covert alert button. The test button is normally lit, but switches off when pushed.

  • Page 56: Use Of Non-Solas Alarm Panels

    Chapter 4: Using the Terminal Control Unit Use of Non-SOLAS Alarm Panels You can use the SAILOR 3042E to send a Distress alert to the rescue centre closest to your location. The SAILOR 6108 Non-SOLAS Alarm Panel works similar to the SAILOR 6101/6103 Alarm Panels. Only send a Distress Alert if you are in immediate danger! Important The Distress Alert can be compared to a MAYDAY call.

  • Page 57: Chapter 5 Scripting

    Chapter 5 Scripting This chapter provides an introduction to scripting with the Terminal Control Unit and an example for a script. It has the following sections: • Introduction to scripting • What can scripts do • Complete example of a Lua script Introduction to scripting The Terminal Control Unit supports simple scripting, using Lua language.

  • Page 58: What Can Scripts Do

    Chapter 5: Scripting What can scripts do In this section you find two scenarios to illustrate the use of a script. Scenario 1: Monitoring the engine speed In a mini-C installation the Terminal Control Unit tacho input is connected to an engine tachometer so the Terminal Control Unit can monitor the engine speed.
  • Page 59 Chapter 5: Scripting Scenario 2: Logging the temperature on the SD memory card The script does not necessarily have to involve the mini-C at all. The following example is a Terminal Control Unit installation with a temperature probe connected to an A/D converter input. In this example we want to: •...
  • Page 60 Chapter 5: Scripting 3. Connect to the Terminal Control Unit as described in Using commands on page 35. 4. Type the command lua s, the location of the script on the SD card (/sdcard/) and the script name (test1.lua) to run the script. Example: The following lines show the above procedure executed on a PC connected to a Terminal Control Unit: tt6194:/$ su sysadm...
  • Page 61 Chapter 5: Scripting Control Unit or in response to a change of state of an IO pin. This is controlled with the luaconf command. luaconf a <auto> <auto>=0: No auto execute <auto>=1: Auto execute <auto>=2: Auto execute and auto restart luaconf c <old>...

  • Page 62: Complete Example Of A Lua Script

    Chapter 5: Scripting f = assert(io.open("/dev/minic","r+")) f:write("ver\r") f:flush() s = f:read(256) f:close() Complete example of a Lua script Communicating with a mini-C Communicating with a mini-C requires a number of steps and considerations apart from accessing the /dev/minic device. First and foremost the mini-C connection is a shell interface that accepts commands and sends back a response.
  • Page 63 Chapter 5: Scripting The mini-C response includes an echo of the command itself as well as a trailing prompt for the next command. When reading from the mini-C device there is no built-in mechanism to separate the command and the prompt from the actual response.
  • Page 64 Chapter 5: Scripting local ctrl_pos = 1 new_prompt = tostring(resp) -- Only use the part of the string after the last control char for i = 1, string.len(new_prompt) do if string.sub(new_prompt,i) < " " then ctrl_pos = i end new_prompt = string.sub(new_prompt, ctrl_pos) if new_prompt == last_prompt then eq_count = eq_count + 1 else...
  • Page 65 Chapter 5: Scripting resp = resp .. resp_part if extra_char and not pr then stream:write(extra_char) extra_char = nil until extra_char == nil if resp then local patt -- remove trailing prompt patt = make_pattern(PROMPT) .. "$" resp = string.gsub(resp, patt, "\r\n", 1) -- remove the command itself patt = "^%s*"...
  • Page 66 Chapter 5: Scripting The script uses a number of techniques worth noting: • The platform is checked by inspecting the "TCU" environment variable (see footnote 1. on page 55). That way the script can take different hardware surroundings into account or prevent the script from running on unsupported platforms.
  • Page 67 Chapter 5: Scripting To make it easier to write portable code, the TCU defines a few environment variables. These are available from Lua via the os.getenv function: Variable name Content HOME /sdcard TMPDIR /sdcard The current software version of the TCU (e.g., 1.03) Script security In some applications it is important to ensure that only approved scripts are used and that scripts cannot be altered.
  • Page 68 Chapter 5: Scripting tt6194:/$ lua c /sdcard/test1.lua 1234 1:3560946965 tt6194:/$ where 1:3560946965 is the checksum. Note that any changes in the script file - including subtle changes like extra spaces and different line endings - will change the checksum. Also a different code word will give a different checksum.

  • Page 69: Chapter 6 Service

    Before you can update the software for the Terminal Control Unit you must get a download tool and the new software for the Terminal Control Unit. Do as follows: Cobham eSupport web site (Self- 1. Download the TMA from the Service Center, SSC. You find the SSC in the Service and Support section, 24-7 Service) 2.
  • Page 70 Chapter 6: Service Updating the Terminal Control Unit software To update the Terminal Control Unit software, do as follows: 1. Start the TMA. 2. The TMA searches for units connected to the local network. All units found are shown on the screen. 3.
  • Page 71 Chapter 6: Service 5. Click the icon Software update. The following window is displayed (example): 6. Click the button Update and wait for the update procedure to finish. The software is now updated and the Terminal Control Unit automatically restarts with the new software. You can use the ThraneLINK Management Application at any time to check the software version.

  • Page 72: Status Signalling

    Chapter 6: Service Status signalling Light indicators The Terminal Control Unit has a number of light indicators for signalling status and errors/warnings. See Status indicators on page 30 for a full description of the indicators and their function. Should the system fail, you can use the indicators to see which units are affected.

  • Page 73: Setting A Temporary Fixed Ip Address

    Chapter 6: Service Setting a temporary fixed IP address The TCU has a button for setting a temporary fixed IP address. The function of the button is: When you push the button, the IP address of the Terminal Control Unit is temporarily set to the default value (169.254.100.100).

  • Page 74: Returning Units For Repair

    Your dealer, installer or Cobham SATCOM partner will assist you whether the need is user training, technical support, arranging on-site repair or sending the product for repair. Your dealer, installer or Cobham SATCOM partner will also take care of any warranty issue. Repacking for shipment The shipping carton has been carefully designed to protect the Terminal Control Unit and its accessories during shipment.

  • Page 75: General Specifications For The Tcu

    Appendix A Specifications General specifications for the TCU Item Specifications Power 10.5 to 32 VDC (nom. 12-24 VDC) Power Typical 1 W, Maximum 3 W consumption Standby power < 10 mW Interfaces Ethernet (10/100 Mbit), RJ45 connector (X6) RS-232 (DTE), 9-pin D-sub connector (X5) CAN (including power for the Terminal Control Unit), spring- loaded terminals (X2) I/O spring-loaded terminals, primarily for SSA buttons (up to 6...

  • Page 76: Specifications For I/O Pins

    Appendix A: Specifications Specifications for I/O pins Item Specifications ADC, Pin 1, spring-loaded Analogue to digital converter terminals X7-X12 Input range 0-15 V 2.7 V pull up 10 kOhm Input resistance min. 130 kOhm Accuracy ±15 mV GPI, Pin 1, spring-loaded General purpose input terminals X7-X12 and X14 Input resistance...
  • Page 77 Appendix A: Specifications Item Specifications GPI, Pin 2, spring-loaded General purpose input terminals X7-X12 and X14 Voltage max. 5 V Voltage high min. 2.0 V Voltage low max. 0.8 V Tacho, Pin 1, spring-loaded Tacho input terminal X13 Input resistance min.
  • Page 78 Appendix A: Specifications Specifications for I/O pins...

  • Page 79: Gpio Functions

    Appendix B Lua extensions Lua in the Terminal Control Unit has been expanded with a number of functions to access and control the specific environment. The functions are grouped as follows: • GPIO functions • Miscellaneous functions GPIO functions API functions for general purpose input/output. The following functions are available: •...
  • Page 80 Appendix B: Lua extensions GPIO mapping table The following table shows the mapping of GPIO pins of the TCU: Block Pin type I/O pin X8 PIN 1 Input/output/adc 1 X10 PIN 1 Input/output/adc 2 X12 PIN 1 Input/output/adc 3 X11 PIN 1 Input/output/adc 4 X9 PIN 1 Input/output/adc 5 X7 PIN 1...
  • Page 81 Appendix B: Lua extensions tcu_get_adc_value Purpose: Get the current value of an ADC channel. Format: tcu_get_adc_value (channel) channel: ADC channel. Value: 1-6 Return value: ADC value in [mV]: 0-15000 or Error code: <0=error Example: a = tcu_get_adc_value(2); tcu_get_gpi_pin Purpose: Get the current state of an input pin. Format: tcu_get_gpi_pin (pin) pin:...
  • Page 82 Appendix B: Lua extensions tcu_set_dac_value Purpose: Set DAC output voltage. Format: tcu_set_dac_value (value, channel) value: Value: 0-3000 [mV]. channel: DAC channel. Value: 1 Return value: Error code: 0=OK, <0=error Example: --Set DAC value to 2V tcu_set_dac_value(2000, 1); tcu_set_gpo_pin Purpose: Set state of output pin. Format: tcu_set_gpo_pin (pin, state) pin:...
  • Page 83 Appendix B: Lua extensions tcu_start_gpo_square_wave Purpose: Start gpo square wave with specified interval. Format: tcu_start_gpo_square_wave (pin, high_time, low_time, duration) pin: Pin number. Value: 1-7. high_time: Time of high state in milliseconds. low_time: Time of low state in milliseconds. duration: Duration of square wave in milliseconds. Value: 0=No timeout 2 - 2.147.483.647 milliseconds After timeout, the pin will be left in high state.

  • Page 84: Miscellaneous Functions

    Appendix B: Lua extensions Miscellaneous functions The following miscellaneous functions are available: • tcu_set_time • tcu_power_off_for • tcu_get_sw_start_cause • tcu_get_power_signals • tcu_sleep • tcu_get_product_info • tcu_slog • tcu_serial_baud • tcu_get_powersave_edge_detect • tcu_reset_powersave_edge_detect tcu_set_time Purpose: Set time in TCU. Format: tcu_set_time (year, month, day, hours, minutes, seconds) year: Year: 1970-2037 month:...
  • Page 85 Appendix B: Lua extensions tcu_power_off_for Purpose: Power off TCU for specified time. After the time-out, the Terminal Control Unit will power on again. If the Terminal Control Unit is used with a SAILOR 3027 mini-C, the TCU will attempt to power down the mini-C before powering down itself. This can potentially delay the power off by up to 3 minutes if the mini-C is busy or unable to respond.
  • Page 86 Appendix B: Lua extensions tcu_get_sw_start_cause Purpose: Get reason for latest start-up. Format: tcu_get_sw_start_cause () Return values: Start-up reason flags. 1 = Power on 2 = CAN activity 4 = Timeout 8 = Remote on 16 = Power save AVR start-up reason flags. 1 = Power on 2 = External reset 4 = Brown out...
  • Page 87 Appendix B: Lua extensions automatic: Optional parameter: Set to 1 to re-enable the automatic handling of the power signals. If the parameter is left out (or set to 0), the automatic handling is disabled. Return values: REMOTE_ON signal. 0 = Low / pulled down. 1 = High / disconnected POWER_SAVE signal.
  • Page 88 Appendix B: Lua extensions tcu_get_product_info Purpose: Get TCU product info Format: tcu_get_product_info () Return values: TCU main sw version. TCU AVR sw version. TCU AVR bootloader version. Transceiver type: 0 = Unknown 1 = Land mobile 2 = Maritime 4 = SSAS 5 = Distress 6 = LRIT 7 = SOLAS...
  • Page 89 Appendix B: Lua extensions tcu_slog Purpose: Log to syslog Format: tcu_slog (priority, message) priority: Values: 3 = Error 4 = Warning 6 = Info 7 = Debug message: String to log. Return value: Error code: 0=OK, <0=error Example: local str = string.format('Pin %d is low', tcu_slog(4, str) Result: 00:46:36.479 WARNING:lua_task: Pin 5 is low...
  • Page 90 Appendix B: Lua extensions tcu_get_powersave_edge_detect Purpose: Get powersave input state Format: tcu_get_powersave_edge_detect () Return value: State: 0 (low) or 1 (high) or Error code: <0=error Example: tcu_get_powersave_edge_detect() tcu_reset_powersave_edge_detect Purpose: Reset powersave input state to 0 Format: tcu_reset_powersave_edge_detect () Return value: Error code: 0=OK, <0=error Example: tcu_reset_powersave_edge_detect()

  • Page 91: Glossary

    Glossary Glossary Analogue to Digital Converter Application Programming Interface Controller-Area Network. A message based protocol designed to allow microcontrollers and devices to communicate with each other within a vehicle without a host computer. Digital to Analog Converter DNID Data Network Identifier. An address code to an electronic mailbox at the Land Earth Station.
  • Page 92 Glossary GMDSS Global Maritime Distress Safety System. The system is intended to perform the following functions: alerting (including position determination of the unit in distress), search and rescue coordination, locating (homing), maritime safety information broadcasts, general communications, and bridge-to-bridge communications. Ground General Purpose Input General Purpose Output...
  • Page 93 Glossary Ingress Protection. An international classification system for the sealing effectiveness of enclosures of electrical equipment against the intrusion into the equipment of foreign bodies (i.e. tools, dust, fingers) and moisture. This classification system uses the letters "IP" followed by two or three digits. An "x" is used for one of the digits if there is only one class of protection;...
  • Page 94 Glossary NMEA National Marine Electronics Association (standard). A combined electrical and data specification for communication between marine electronic devices such as echo sounder, sonars, anemometer (wind speed and direction), gyrocompass, autopilot, GPS receivers and many other types of instruments. It has been defined by, and is controlled by, the U.S.-based National Marine Electronics Association.

  • Page 95: Index

    Index Index configuration method, 35 alarm buttons, SSA power management, 40 configuring, 39 SAILOR 6194, 37 connecting, 22 show current, 37 connectors for, 21 SSA buttons, 39 installing, 7 connectors using, 44 CAN, 16 alarm panel, Non-SOLAS for Non-SOLAS Alarm Panels, 23...
  • Page 96 26 mini-C auto connect, 36 modes for power management, 40 mounting screws, 4 torque, 5 Hdop, 43 mounting the SAILOR 6194, 4 indicators, function, 30 Non-SOLAS Alarm Panel initial inspection, 3 connecting, 25 installation, 4 using, 46 IO connectors, 21...
  • Page 97 Index repacking for shipment, 64 updating software, 59 reset IP address, 63 returning units, 64 RS-232 connector, 19 warranty, 64 safety summary, iii script introduction, 47 Lua, 47 security, 57 security script, 57 software update, 59 specifications, 65, 69 SSA buttons configuring, 39 connecting, 22 connectors for, 21...
  • Page 98 Index...
  • Page 100 98-131593-D www.cobham.com/satcom...

Table of Contents

Save PDF