NRAO Home  >  Green Bank  |  Wiki Topic:    GB > Software > CCBClassDoc (r1.1 vs. r1.2)
   Changes | Index | Contents | Search | Statistics | Go
 <<O>>  Difference Topic CCBClassDoc (r1.2 - 21 Apr 2004 - MelindaMello)
Changed:
<
<

Under construction

>
>

Under construction

Added:
>
>

Overview

The Caltech Continuum Backend is a continuum backend designed for use with th GBT 1cm and 3mm receivers. Unlike most other devices at the gbt, the Ygor manager has no direct access to the hardware. The backend is configured through C libraries provided by CalTech?. Detailed documentation of the libraries is in CCB library the YGOR manager to CCB document. All communication between the manager is done through two sockets, the telemetry socket and the control socket.

 <<O>>  Difference Topic CCBClassDoc (r1.1 - 20 Apr 2004 - MelindaMello)
Added:
>
>

%META:TOPICINFO{author="MelindaMello" date="1082493240" format="1.0" version="1.1"}% -- MelindaMello - 20 Apr 2004

Under construction

Threads

There are 4 threads. Each thread is responsible for a particular set of IO. 3 of them are for IO from the CCB librairy, the other is the PanelSErver? thread.

write_control -- This thread calls the ccb lib function ccb_client_communicate() and blocks. It will not return until there is an error or the clientlink is terminated. Whenever a queued command is queued by the CCBmanager, this thread "tells" the server to send data down to the hardware.

read_control -- This thread calls the ccb lib function ccb_client_communicate() and blocks. It will not return until there is an error or the clientlink is terminated. Whenever there has been a problem with one of the commands sent down to the CCB, it 'tells' the ccb to call the function that was registered with the ccb_cmd_error_callback() lib function.

read_telemetry -- This thread calls the ccb lib function ccb_client_communicate() and blocks. It will not return until there is an error or the clientlink is terminated. It 'tells' the ccb to call the callback functions that were registered with the ccb_monitor_msg_callback(), the ccb_integ_msg_callback() and the ccb_log_msg_callback lib functions.

%META:FILEATTACHMENT{name="CCBclass.pdf" attr="" comment="" date="1082492270" path="CCBclass.pdf" size="5152" user="MelindaMello" version="1.1"}% %META:FILEATTACHMENT{name="CCBthread.pdf" attr="" comment="" date="1082492424" path="CCBthread.pdf" size="3923" user="MelindaMello" version="1.1"}% %META:FILEATTACHMENT{name="ccb_external_hardware_interfaces.pdf" attr="" comment="" date="1082495190" path="ccb_external_hardware_interfaces.pdf" size="976163" user="MelindaMello" version="1.1"}% %META:FILEATTACHMENT{name="ccb_network_interface.pdf" attr="" comment="" date="1082495390" path="ccb_network_interface.pdf" size="978059" user="MelindaMello" version="1.1"}%


Topic CCBClassDoc . { View | Diffs | r1.2 | > | r1.1 | More }
Revision r1.1 - 20 Apr 2004 - 20:34 GMT - MelindaMello
Revision r1.2 - 21 Apr 2004 - 14:19 GMT - MelindaMello
Content copyright © 1999-2007 by the contributing authors.
All material on this collaboration platform is the property of the contributing authors.