projects:spill_cnt_io_ctrl:overview
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
projects:spill_cnt_io_ctrl:overview [2012/06/15 16:37] reeg |
projects:spill_cnt_io_ctrl:overview [2012/06/15 16:58] (current) reeg |
||
|---|---|---|---|
| Line 23: | Line 23: | ||
| Besides slow and simple I/O RW settings for device id, polarity and gas flow the requirement for the range setting needs careful consideration. The ranges have to be switched within a cycle pause (Fig. 1). The exact duration of that pause is so far not known, but is assumed to be between 50 and 100ms for a cycle rate of 4 Hz, SIS-18. The new I/O system should be able to do that in real-time to assure the right range setting for every virtual accelerator. The new range values may be changed at any time by the operator/ | Besides slow and simple I/O RW settings for device id, polarity and gas flow the requirement for the range setting needs careful consideration. The ranges have to be switched within a cycle pause (Fig. 1). The exact duration of that pause is so far not known, but is assumed to be between 50 and 100ms for a cycle rate of 4 Hz, SIS-18. The new I/O system should be able to do that in real-time to assure the right range setting for every virtual accelerator. The new range values may be changed at any time by the operator/ | ||
| - | Figure 1: Scheme of a SIS-18 super-cycle with pauses to be used for event triggered range switching. | + | {{:projects: |
| + | **Figure 1:** Scheme of a SIS-18 super-cycle with pauses to be used for event triggered range switching. | ||
| In addition other users of I/O shall have their own I/O module ready to fit in the new crate. This can be the timing for the BPM preamplifiers (DPX). | In addition other users of I/O shall have their own I/O module ready to fit in the new crate. This can be the timing for the BPM preamplifiers (DPX). | ||
| Line 105: | Line 106: | ||
| - | Requirements | + | **Requirements** |
| Parameters | Parameters | ||
| Line 186: | Line 187: | ||
| - | Possible solution | + | **Possible solution** |
| So far a stand-alone solution for the SIS-18 collimator system is available. This non-intelligent modular system is accessed via a Lantronix TCP/IP to RS485 interface. The modules in the crate are all addressed by this RS485 bus. The bus can be enhanced by daisy chain to max. 64 x 8 channels which would be more then required. | So far a stand-alone solution for the SIS-18 collimator system is available. This non-intelligent modular system is accessed via a Lantronix TCP/IP to RS485 interface. The modules in the crate are all addressed by this RS485 bus. The bus can be enhanced by daisy chain to max. 64 x 8 channels which would be more then required. | ||
| Line 195: | Line 196: | ||
| - | Replacement of control system functionality | + | **Replacement of control system functionality** |
| To replace the requirements for online transmission and ‘Zintilla’ of the old ‘Walterkistensystem’ the following solution is proposed. | To replace the requirements for online transmission and ‘Zintilla’ of the old ‘Walterkistensystem’ the following solution is proposed. | ||
| Line 210: | Line 211: | ||
| There is also a possible solution to use existing control system software with FESA by integration of the dedicated gateway, which already exists at GSI (Cosylab development). | There is also a possible solution to use existing control system software with FESA by integration of the dedicated gateway, which already exists at GSI (Cosylab development). | ||
| - | Specification Keywords | + | **Specification Keywords** |
| White Rabbit: | White Rabbit: | ||
projects/spill_cnt_io_ctrl/overview.1339771074.txt.gz · Last modified: 2012/06/15 16:37 by reeg
Page Tools
