• No se han encontrado resultados

CAPITULO IV: MARCO METODOLÓGICO

4.5. Técnicas de Procesamiento, Análisis de Datos y Presentación de

2.7 : Network capacity

The amount of dynamic system control is limited by the available network capacity.

The maximum number of messages per second is:

-1 Number instructions/Sec (BWCharaekr Mesgge,Legg% Arbitration tim e|

Equation 1 : Instruction capacity of a network

2.8 ! Network packet protocol

The network packet should contain the following information:

Target address field, host address field, transmission start time, message creation time, command type and associated data and terminator fields. Since the processor clocks are not synchronised and since one of the design parameters specified time independence across the network (See Page 38), the two time fields are ignored. The resultant packet adhered to the following protocol (Table 4).

< TARGET> <HOST> < COMMAND > <DATA> <TERMINATOR>

8 Bit ASCn 'A'-'Y* 8 Bit A scn 'A'-'Y' 8 Bit ASCn •A’-'Y’ n * 8 Bit ASCII n<27 ASCn(0x5A) ’Z’ Table 4 : Network packet protocol used on the twin photometric telescope The target address is a 8 bit ASCII coded field which defines the recipient address. This address is compared to both the node and wild card addresses stored in the

erasable, programmable read only memoiy (EPROM) and if equal to either of the EPROM stored values the message is for that processor.

The host address, similar to the target address, is an 8 bit ASCII coded field but defines the sender address. It is used to specify the call-back address when replying to a message.

Valid addresses can be any character between ASCII(0x41) ('A') and ASCII(0x59) ('Y'). The addresses are specified as follows:

Address Process description Address Type Macro Set

A R.A. main Physical

B DEC main Physical

C R.A. offset Physical

D DEC offset Physical

E Counters Physical

F Dome Physical

G Operator control Physical

H Log Virtual

I Error Virtual

W All Virtual devices Macro {H ,I}

X All devices Macro

Y All Physical devices Macro { A,B,C,D,E,F,G } Table 5 : Network addresses

As well as the physical addresses (A-G) there are also virtual, wild card and macro addresses. These enable compact network wide instructions to be sent quickly to physical and emulated nodes using one command. For example sending a RESET

instruction inserting ’Y’ in the target field resets all physical devices, including the operators console.

Chapter 3 ; Design of the distributed control system for the St

Andrews twin photometric telescope

This chapter describes in detail the design and construction of the system hardware

3.1 : Overview

The control system design is subjected to constraints governed by the concept of a

generic distributed control system as outlined in chapter 2.

Parameters relating to the distributed architecture

1. Each physical process must be modelled by a software algorithm.

The physical process must be suitable for embedding into software for use in the given microcontroller. For example, controlling the angular position of an axis using actuators and encoders lends itself easily to embedding into small microcontrollers, but CCD image reduction clearly would not be applicable due to the memory and floating point calculations required.

2. Each algorithm must be time independent of other physical processes.

If mutually dependant algorithms were embedded into separate microcontrollers Hnked only by a common network, the efficiency of both algorithms would be dependant on the network packet transmission rate. Since the network protocol used cannot guarantee immediate transmission, both algorithms must be time independent. Since there is a 95% chance that a message can be successfully transmitted in 1 second, this is not strictly true, but for physical processes required to control the telescope, where the process loop time is in the order of milliseconds, the network propagation rate is insufficient.

3. The controlling algorithm for each physical process must interface to a time independent network.

As above, commands sourced from the operator to the microcontroller pass through the network. Therefore this algorithm is time independent.

4. All microcontrollers are linked to the operator's console by one common multinode, duplex, non-hierarchical network.

This enables the operator to update the console with ease, without disconnecting vendor specific boards or modifying complex configurations.

2. All network data characters shall be printable and readable on a VT52 standard terminal.

While the network was being installed, ambiguity existed over hot key functions from various consoles. For example, some dumb terminals send ASCII(O) and ASCII(IO) with the carriage return character ASCII(13). This would cause a packet error in each controller, invalidating the previous message. Also, to analyse network messages, a dumb terminal was used as a probe, but the display was limited to printable characters. By changing the packet terminator to ASCII(90), 'Z* both ambiguity and network display conditions were satisfied. All other characters lay within the ranges 'A'-'Z*, T ','0 '.

Each controller has the ability to communicate to any other node, so only one network is used. If multiple networks were to be used, a suitable gateway must be installed, transparent to each microcontroller. Each node must be able to transmit and receive data packets without being overridden by a higher priority node. The only exception to this is the system failure scenario, where the console node should have a higher priority to enable system restart. This can be implemented by the console software as shown later.

These four parameters enable the distributed architecture to perform without a

severe error occurring. Further constructional constraints were applied during | system design in response to the problems encountered while developing the

I

]

prototype. j

1

1 1. The telescope system is required to plug into COM 1-4 of any 32 bit PC I

1

After analysis of the telescope operation, it was found that there were six independent physical processes acting on the telescope that could be integrated into a distributed control system architecture. These were:

1. Reference right ascension

This consists of coarse encoder, fine encoder, sidereal drive, clutch solenoid, clamp motor, slew motor and limit switches.

2. Reference declination

This consists of coarse encoder, fine encoder, tangent arm, clamp motor, slew motor and limit switches.

3. Offset right ascension

This consists of encoder, tangent arm motor, centre detent and limit switches.

4. Offset declination

This consists of encoder, tangent arm motor, centre detent and limit switches.

5. Dome azimuth

This consists of encoder, hydraulic valves. 6. Photomultiplier counter

This consists of two photomultiplier pulse inputs and IMhz time signal. The photomultiplier counter process required the recorded data to be transferred to the host console at regular intervals to stop data stacking in the microcontroller RAM. This would be negligible for long period integrations, but would invalidate the time independent criteria when undertaking high speed photometry and was discontinued.

3.2 ; Electrical considerations

When the design was conceived, a firm step was taken to use the nearest state of the

art technology available to the department. This included new ICs such as generic array logic devices (GAL’s), HCT series logic and integrated process controllers (IPC's). This drive for modem technology enabled multiple functions to be integrated onto one generalised device. This reduced board space, power requirements and noise levels, whilst returning constant propagation delays across logic gates and faster processing speeds. With reference to an earlier design based on the Z80 processor it was shown that a physical reduction in board space by a factor of 3 coupled with a power reduction by a factor of 10 could be achieved. Surface mount packaging was used during the development of the prototype but it was found that the board manufacturing process was too unreliable for direct soldering of packages at the required pin resolution. Surface mount formats would have reduced the board size further, but no other advantages would be gained.

The main disadvantage of using high speed processor cards was a lower input noise immunity and higher crosstalk on the printed circuit board due to the lower gate hysteresis levels and higher clock rates used. Careful track placement, input filtering and device decoupling lowered the noise level of the card. It was also found that the initial expense of using new devices was returned on the reduced board size and board production cost.

3.3 : Printed circuit board manufacture considerations

All microcontroller boards were identical in design and lead to 'mass production' runs, reducing the tooling and labour time. Boards were developed in house using

the facilities of the physics department electronics workshop. It took 8 weeks to produce 30 drilled, plated double sided boards ready for population.

During the construction of the prototype it was found that the board quality was poor and inconsistent; a fault tracked down to the opacity of the acetate and the developer / echant fluid quality. A minimum track width of 0.2mm was realised with an average error rate of 10 cut tracks per board.

3.4 : Design of microcontroller boards

The microcontroller design was split into three distinct areas; the microcontroller board and support devices, input / output boards to interface it to the outside environment and a power conditioning unit.

Each board was designed using the most applicable devices, but changes were introduced due to financial constraint. These modifications related to the functionality and reliability of each unit.

3.5 ; The CPU board

The CPU board comprised of a microcontroller unit, ROM, RAM, I/O buffer and memory logic to map the ROM, RAM and I/O buffer into the correct location in memory.

Ideal Processor : IMS T414

The ideal processor available was the Inmos T414 transputer, a 32 bit transputer unit with 2Kbytes of on chip RAM (Diagram 10).

System Services Link Services Timers Link Interface 2K bytes of on RAM Link Interface Link Interface External Memory Interface Event

Documento similar