9.607 SatService-IO-FEP

This page describes the device driver and the device window for the SatService-IO-FEP device. This device monitors and controls the SatService IO-FEP controller.

The SatService-IO-FEP device driver is part of the sat-nms framework for M&C of plain digital I/O functions. Monitoring alarm circuits or controlling waveguide switches are indicatives for applications of this framework.

The application configuration normally does not access the SatService-IO-FEP device driver directly (except to access the temperature readings). There are a couple of application level logical devices (e.g. Input , Output or WG-Switch ) which may use the SatService-IO-FEP device driver as a low level driver to access the physical I/O ports.

Input ports

The variables 'inputs.0', 'inputs.1' and 'inputs.2' refer to the input ports 1..16, 17..32 and 33..48 respectively. The least significant bit in a variable reports the state of the lowest numbered port in it's group.

The variables report the logical state if the input. A bit set to '1' denotes an 'ON' or 'FLT' state, '0' stands for 'OFF' or 'OK'. The reported input states respect the 'delay' and 'invert' settings configured in the IO-FEP for each individual port.

Unused ports always report a '0', the same applies to the input ports 33..48 if the IO-FEP has no extension board installed.

Output ports

The variable 'outputs' reports the actual state of the digital outputs and also sets the output states. The least significant bit in the variable corresponds to output 1, the most significant bit to output 16. The port states respect the 'invert' setting configured for each individual port in the IO-FEP.

Unused ports and ports which are configured in the IO-FEP as HPA muting outputs always report the state '0'. Writing to these ports will be ignored.

Waveguide switches

The variable 'wgstat' reports the actual state of the waveguide switches. For each waveguide switch there are 2 bits, indicating the position of the switch. '01' denotes position 'A', '10' denotes position 'B'. The bit combinations '00' and '11' both indicate a fault. This similar to the way, the physical position indicators of a waveguide switch are working. However, the bits reflect a logical state in the IO-FEP rather than the physical state of the position indicators. This is because the IO-FEP hides it's internal queuing mechanism for switch actuation's from the controlling M&C.

• bit 0 --- 0x00000001switch 1, position A
• bit 1 --- 0x00000002switch 1, position B
• bit 2 --- 0x00000004switch 2, position A
• bit 3 --- 0x00000008switch 2, position B
• bit 4 --- 0x00000010switch 3, position A
• bit 5 --- 0x00000020switch 3, position B
• bit 6 --- 0x00000040switch 4, position A
• bit 7 --- 0x00000080switch 4, position B
• bit 8 --- 0x00000100switch 5, position A
• bit 9 --- 0x00000200switch 5, position B
• bit 10 --- 0x00000400switch 6, position A
• bit 11 --- 0x00000800switch 6, position B
• bit 12 --- 0x00001000switch 7, position A
• bit 13 --- 0x00002000switch 7, position B
• bit 14 --- 0x00004000switch 8, position A
• bit 15 --- 0x00008000switch 8, position B
• bit 16 --- 0x00010000switch 9, position A
• bit 17 --- 0x00020000switch 9, position B
• bit 18 --- 0x00040000switch 10, position A
• bit 19 --- 0x00080000switch 10, position B
• bit 20 --- 0x00100000switch 11, position A
• bit 21 --- 0x00200000switch 11, position B
• bit 22 --- 0x00400000switch 12, position A
• bit 23 --- 0x00800000switch 12, position B
• bit 24 --- 0x01000000switch 13, position A
• bit 25 --- 0x02000000switch 13, position B
• bit 26 --- 0x04000000switch 14, position A
• bit 27 --- 0x08000000switch 14, position B
• bit 28 --- 0x10000000switch 15, position A
• bit 29 --- 0x20000000switch 15, position B
• bit 30 --- 0x40000000switch 16, position A
• bit 31 --- 0x80000000switch 16, position B

The variable 'wgcmd' is the complement to 'wgstat' for actuating the switches. In the software the bits of this variable are treated like output ports which perform the switch motor actuation. In fact, the IO-FEP monitors 0 to 1 transitions of each bit and performs the switch actuation accordingly. The actuation pulse duration is controlled by the IO-FEP, not by the sat-nms software. Nevertheless, the IO-FEP waveguide switch interface is fully compatible to the WG-Switch logical device.

Switches configured in the IO-FEP as 'unused' always report the position '00'. The same applies to the switches 9..16 if no extension board is installed in the IO-FEP.

PSU fault monitoring

The IO-FEP "E" version, together with firmware versions beginning from January 2013, monitors the presence of power supply voltages. The sat-nms device driver reports these PSU fault flags as 'faults.11' to 'faults.14'. With IO-FEP versions that do not support PSU monitoring, these fault flags remain unset / uninitialized.

The PSU monitoring for the redundant supply voltages may be masked in the IO-FEPs setup. The IO-FEP reports always them as OK in this case.

Configuration settings

If used with the sat-nms framework for M&C of plain digital I/O functions, the SatService IO-FEP acts like an unprogrammed PLC device. It is intended, that the device driver processes switch settings and changes of input circuits as fast as possible. The following settings are necessary to achieve this:

• When defining the IO-FEP device in the device setup window , there must not be defined any other devices beside the IO-FEP for this interface.
• The IDLE time for the interface must be set to 200 msecs
• In the IO-FEP's device setup dialog, the 'retries' parameters must be set to '0', the snmpTimeout to '200 msec' and the snmpRetries parameter to '2'
• Any WG-Switch configured to work via the IO-FEP must use a pulseWidth of 1500 msecs or longer.

Device window pages

The following table shows which device window pages are available with this individual device type. Tool-bar functions not mentioned here are described at the general description of device windows .

• --- Shows / commands I/O port states.
• --- Shows the temperature readings
• --- The faults page.
• --- The device info page.
• --- The maintenance page. The configuration parameters described below are set at this page.

Configuration parameters

At the maintenance page of the device window there are a couple of configuration parameters which must be set to make the software talk to the device.

• parameter --- description

• address --- The SNMP address specification for the device. The full address specification consists of the following fields:aaa.bbb.ccc.ddd:pppp read-community write-community

  • aaa.bbb.ccc.ddd --- The IP address of the device in 'dotted quad' notation. This field is mandatory.
  • pppp --- The IP port number where the device accepts SNMP requests. The port number may be omitted, the driver uses the standard port 161 in this case.
  • read-community --- The SNMP read community name. This must match the read community expected by the device.
  • write-community --- The SNMP write community name. This must match the write community expected by the device. The write community name may be omitted, the driver uses the read community name for both, read and write in this case. If both community names are missing, the driver uses 'public' as a default for read and write community.

• retries --- The number of communication retries which are made at application level. For use with the sat-nms framework for M&C of plain digital I/O functions this parameter must be set to 0.

• snmpTimeout --- The timeout value used by the SNMP protocol implementation. The default value is 5 seconds. For use with the sat-nms framework for M&C of plain digital I/O functions this parameter must be set to 200 msec.

• snmpRetries --- The the number of retries used by the SNMP protocol implementation. The default value is 2 retries.

• swCtrlFaultSrc --- Defines in which way the driver evaluates the switch control fault flag (faults.17). This fault flag tells that the IO-FEP actually is not capable to control switches or to report input signals correctly.

  • COMM --- The switch control fault is determined only from the communication fault flag, the PSU fault flags are ignored. This settings should be used if IO-FEP (not the extended version) is controlled
  • COMM+PSU1 --- The switch control fault is set if the IO-FEP either shows a communication fault or the primary EXT24 voltage fails. This setting should be used if controlling an IO-FEP-E with a single EXT24 power supply.
  • COMM+PSU1+PSU2 --- The switch control fault is set if the IO-FEP either shows a communication fault or both EXT24 voltages fails. This setting should be used if controlling an IO-FEP-E with redundant EXT24 power supplies.

Variables defined by this device driver