org.lsst.ccs.subsystems.fcs.drivers

Class LoaderCanOpenProxy

java.lang.Object

java.util.Observable

org.lsst.ccs.framework.Module

org.lsst.ccs.subsystems.fcs.drivers.CanOpenProxy

org.lsst.ccs.subsystems.fcs.drivers.LoaderCanOpenProxy

All Implemented Interfaces:

Observer, org.lsst.ccs.framework.Configurable, org.lsst.ccs.framework.HardwareController, org.lsst.ccs.framework.SignalHandler

public class LoaderCanOpenProxy
extends CanOpenProxy

The tcp server for the loader when we want to connect or disconnect loader hardware. So this tcp proxy won't start during initialisation phase.

Author:

virieux

Nested Class Summary

Nested Classes

Modifier and Type	Class and Description
protected static class	FcsTcpProxy.ClientContext

Nested classes/interfaces inherited from class org.lsst.ccs.subsystems.fcs.drivers.CanOpenProxy

CanOpenProxy.PDOStorage

Nested classes/interfaces inherited from class org.lsst.ccs.framework.Module

org.lsst.ccs.framework.Module.ValueUpdate

Nested classes/interfaces inherited from interface org.lsst.ccs.framework.Configurable

org.lsst.ccs.framework.Configurable.Environment

Field Summary

Fields

Modifier and Type	Field and Description
protected FcsTcpProxy.ClientContext	clientContext
protected static org.lsst.ccs.utilities.logging.Logger	fcslog
protected Condition	hardwareBooted
protected Lock	lock
protected boolean	stopped
protected boolean	stopping
protected boolean	tcpServerStarted

Fields inherited from class org.lsst.ccs.subsystems.fcs.drivers.CanOpenProxy

bootedNodesMap, hardwareList

Fields inherited from class org.lsst.ccs.framework.Module

environment, log, name, nObserverThreads, registry, tickMillis

Constructor Summary

Constructors

Constructor and Description
LoaderCanOpenProxy(String aName, int aTickMillis, int portNumber, String aClientName, long hardwareBootTimeout)

Method Summary

Modifier and Type	Method and Description
Object	call(String clientName, String command) This methods send a command to the tcp client.
org.lsst.ccs.framework.TreeWalkerDiag	checkHardware() We want that the checkHardware method does nothing during INITIALISATION phase for the loader tcpProxy because the loader might be not connected.
void	connectHardware() This methods connect the CWrapper client, and the TCP server and check the hardware.
boolean	isReady(String clientName)
boolean	isTcpServerStarted()
void	shutdownNow()
void	start() We don't want the tcp server to be started during INITIALISATION phase.
void	startServer() Starts the server tcp on the port portNumber.
void	startThreadReader() Starts a thread which read on the tcp socket, waiting for messages coming from tcp proxy.
void	stopServer() Stops the tcp server.

Methods inherited from class org.lsst.ccs.subsystems.fcs.drivers.CanOpenProxy

checkCanOpenNodeConfiguration, checkCanOpenNodes, checkStarted, checkStopped, configAsHeartbeatConsumer, configAsHeartbeatProducer, configAsHeartbeatProducer, disconnectHardware, displayReadPDOs, getBootedNodesMap, getBootedNodesNB, getDetectedNodeForSerialNumber, getExpectedNodesNB, getHardwareBootTimeout, getMyClientName, getNodes, getPdoStorage, identifieHardware, initializeHardware, initModule, isBooted, isBooted, isHardwareIdentified, isHardwareReady, isNodeIdBootedAndOK, listHardware, listNodes, readPDOs, readSDO, readSDO, sendCanOpen, setExpectedNodesNB, setHardwareBootTimeout, setHardwareBootTimeout, tick, toString, writeSDO, writeSDO

Methods inherited from class org.lsst.ccs.framework.Module

alias, change, dropConfigurationContext, getCheckedValueFromConfiguration, getChildren, getComponentByName, getComponentDictionariesTree, getComponentTree, getContext, getDictionary, getEnvironment, getMainDictionary, getModule, getName, getNObserverThreads, getObservables, getParent, getSubsystem, getTickMillis, init, injectResources, listens, newConfigurationContext, notifyChange, notifyChangeWithoutPreliminaryChecks, percolateSignal, processUpdate, publish, publish, publish, publish, publish, publish, publishData, publishData, publishData, publishData, publishData, publishData, publishData, register, sendSignal, sendSignal, sendToReply, sendToStatus, setBeanName, setContext, setEnvironment, setName, setNObserverThreads, setObservables, setStateModularSubsystem, setStateModularSubsystem, setTickMillis, shutdownCommand, signal, startTicking, update

Methods inherited from class java.util.Observable

addObserver, clearChanged, countObservers, deleteObserver, deleteObservers, hasChanged, notifyObservers, notifyObservers, setChanged

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait

Field Detail

stopped

protected volatile boolean stopped

stopping

protected volatile boolean stopping

tcpServerStarted

protected volatile boolean tcpServerStarted

clientContext

protected FcsTcpProxy.ClientContext clientContext

fcslog

protected static final org.lsst.ccs.utilities.logging.Logger fcslog

lock

protected final Lock lock

hardwareBooted

protected final Condition hardwareBooted

Constructor Detail

LoaderCanOpenProxy

public LoaderCanOpenProxy(String aName,
                          int aTickMillis,
                          int portNumber,
                          String aClientName,
                          long hardwareBootTimeout)

Method Detail

start

public void start()

We don't want the tcp server to be started during INITIALISATION phase.

checkHardware

public org.lsst.ccs.framework.TreeWalkerDiag checkHardware()
                                                    throws org.lsst.ccs.HardwareException

We want that the checkHardware method does nothing during INITIALISATION phase for the loader tcpProxy because the loader might be not connected.

Specified by:

checkHardware in interface org.lsst.ccs.framework.HardwareController

Overrides:

checkHardware in class CanOpenProxy

Returns:

Throws:

org.lsst.ccs.HardwareException

connectHardware

public void connectHardware()
                     throws org.lsst.ccs.HardwareException

This methods connect the CWrapper client, and the TCP server and check the hardware.

Overrides:

connectHardware in class CanOpenProxy

Throws:

org.lsst.ccs.HardwareException

isTcpServerStarted

public boolean isTcpServerStarted()

startServer

@Command(type=ACTION,
         level=1,
         description="Starts the tcp server.")
public void startServer()

Starts the server tcp on the port portNumber. And waits for a client connection.

startThreadReader

@Command(type=ACTION,
         level=1,
         description="Starts to listen to the tcp client.")
public void startThreadReader()

Starts a thread which read on the tcp socket, waiting for messages coming from tcp proxy. If the message has a known token (already registred in commandDispenser) it is a response to a can open command that we had sent to the proxy. If the token of the message is null, that means that is's an unsynchronous message coming from the can open stack and transmitted directly from the tcp proxy. That can be : - a boot message : "boot,nodeID" - an emergency message : "emcy,80+NodeID"

shutdownNow

public void shutdownNow()

Overrides:

shutdownNow in class org.lsst.ccs.framework.Module

stopServer

public void stopServer()

Stops the tcp server.

isReady

public boolean isReady(String clientName)

call

public Object call(String clientName,
                   String command)
            throws CWrapperNotConnected,
                   CanOpenCallTimeoutException

This methods send a command to the tcp client. The command is a String and can be understood by the client. Example for a Can Open command : rsdo,1,1018,0 The command is stored in the command dispenser with a token and command corelation. When the response comes back from the proxy we can retrieve it from the dispenser with the call token.

Parameters:

clientName -

command -

Returns:

result of the call or null if the call failed

Throws:

CWrapperNotConnected

CanOpenCallTimeoutException