...
| Code Block | ||
|---|---|---|
| ||
%GOD #GOD**001 @HCI(S) [(DBL),DI32,DU32,DU32,DI32,TF,TF,TF,TF,DI32,DU16:32,TF,TF,TF,TF,DI32,DI32,DI32,DI32,DI32,DI32,DI32,DU16:4,DU16:4,DU16:4,DU16:4] |
...
...
GGODConnection.vi
...
Open the IP connections with the four VME SIS3153 controllers and return the connection handles.
The VME access is A32, D32 and "block transfer" is enabled.
The VME mapped size is 4 MByte (that is the whole Apple DEVIL memory).
The vme_base_address is set to E0000000 (which is the DEVIL extended base address).
Controls
...
Data type
...
Name
...
Description
...
Indicators
...
Data type
...
Name
...
Description
...
Legacy data-dependency output.
The connector pane pattern for all initHWXXX VIs is fixed and mandatory and – for (wrong) historical reasons – it has no indicator returning the error.
The error is returned in ddOut as a boolean obtained from the status element of the output error cluster of the vme_open SubVI.
ddOut = True indicates that an error occourred in the vme_open
Details
| Warning |
|---|
The connector pane pattern for all initHWXXX VIs is fixed and mandatory and – for (wrong) historical reasons – does not return any errors. |
Examples
---
GODStartup.vi
This is the real data loader of the GODSta.vi
Controls
...
Data type
...
Name
...
Description
Indicators
...
Data type
...
Name
...
Description
Details
---
Examples
---
closeGOD.vi
Close the IP connections with the four VME SIS3153 controllers and dispose the connection handles.
Controls
...
Data type
...
Name
...
Description
...
Indicators
...
Data type
...
Name
...
Description
...
Details
---
Examples
---
GGODConnection.vi
Array of cluster. Some variables are constants saved as default values
Variables
...
Data type
...
Name
...
Description
...
[ ORBRAK63, ORBRAK71, ORBRAK70, ORBRAK66 ]
The sequence is sorted according to the direction of the beam for the electronic mode: clockwise, starting from rack 063 (DEVIL364)
...
It varies depending on the DEVIL36X.DBDyn content
In order to fill the ORBHCIDyn cluster with data read from the SIS3153 interface, we read "HCIDynNumOfLongwords" longwords starting from "HCIDynOffset. Data are then passed to the VI
.../0_classes/GOD/library/VMEMemToORBDyn.vi
that reconstructs the ORBHCIDyn cluster by using the "HCIDynDescriptor".
...
It varies depending on the DEVIL36X.DBSta content
In order to fill the ORBHCISta cluster with data read from the SIS3153 interface, we read "HCIStaNumOfLongwords" longwords starting from "HCIStaOffset. Data are then passed to the VI
.../0_classes/GOD/library/VMEMemToORBSta.vi
that reconstructs the ORBHCISta cluster by using the "HCIStaDescriptor".
...
Array of cluster. Some variables are constants saved as default values
Variables
Data type | Name | Type | Description |
|---|---|---|---|
Data type | Name | Type | Description |
| abc | DEVIL | constant | [ 364, 365 ,366, 367 ] (see fig. 1-a, 1-b) |
| abc | element | constant | [ ORBRAK63, ORBRAK71, ORBRAK70, ORBRAK66 ] |
| abc | controllerIP | constant | [ 192.168.192.91, 192.168.192.92, 192.168.192.93, 192.168.192.94 ] The sequence is sorted according to the direction of the beam for the electronic mode: clockwise, starting from rack 063 (DEVIL364) |
| U32 | vme handle | Written at startup by the initHWGOD.vi | |
| U32 | DEVILBaseAddress | constant | 0xE0000000 for all 4 DEVILs |
| U32 | DEVILBufferOffset | constant | 0x200000 (2 MB) for all 4 DEVILs |
| abc | HCIDynDescriptor | constant | It varies depending on the DEVIL36X.DBDyn content In order to fill the ORBHCIDyn cluster with data read from the SIS3153 interface, we read "HCIDynNumOfLongwords" longwords starting from "HCIDynOffset. Data are then passed to the VI |
| U32 | HCIDynOffset | constant | Position of the dynamic fork in the DEVIL memory. It varies depending on the lenght of other data written before in memory |
| U32 | HCIDynNumOfLongwords | constant | The 4 HCIDyn have different length but we use a safe value to fetch any of them without missing any piece of data. The value is set to 64 longwords. |
| abc | HCIStaDescriptor | constant | It varies depending on the DEVIL36X.DBSta content In order to fill the ORBHCISta cluster with data read from the SIS3153 interface, we read "HCIStaNumOfLongwords" longwords starting from "HCIStaOffset. Data are then passed to the VI |
| U32 | HCIStaOffset | constant | Position of the static fork in the DEVIL memory. It varies depending on the lenght of other data written before in memory. |
| U32 | HCIStaNumOfLongwords | constant | The 4 HCISta have different length but we use a safe value to fetch any of them without missing any piece of data. The value is set to 240 longwords. |
...
initHWGOD.vi
Open the IP connections with the four VME SIS3153 controllers and return the connection handles.
The VME access is A32, D32 and "block transfer" is enabled.
The VME mapped size is 4 MByte (that is the whole Apple DEVIL memory).
The vme_base_address is set to E0000000 (which is the DEVIL extended base address).
Controls
Data type | Name | Description |
|---|---|---|
| Bool | ddIn | Legacy data-dependency input |
Indicators
Data type | Name | Description |
|---|---|---|
| Bool | ddOut | Legacy data-dependency output. ddOut = True indicates that an error occourred in the vme_open |
Details
| Warning |
|---|
The connector pane pattern for all initHWXXX VIs is fixed and mandatory and – for (wrong) historical reasons – does not return any errors. |
Examples
---
...
GODStartup.vi
This is the real data loader of the GODSta.vi
Controls
Data type | Name | Description |
|---|---|---|
Indicators
Data type | Name | Description |
|---|---|---|
Details
---
Examples
---
...
closeGOD.vi
Close the IP connections with the four VME SIS3153 controllers and dispose the connection handles.
Controls
Data type | Name | Description |
|---|---|---|
| Bool | ddIn | Legacy data-dependency input |
| errorCluster | errorIn |
Indicators
Data type | Name | Description |
|---|---|---|
| Bool | ddOut | Legacy data-dependency output |
| errorCluster | errorOut |
Details
---
Examples
---
...
| Turn for electrons | Turn for positrons |
|---|---|
 |  |
| Figure 1-a: The sequence [0,1,2,3] is sorted according to the direction of the electrons beam: starting from rack 063 (DEVIL364 > 365 > 366 > 367) | Figure 1-b: The sequence [1,0,3,2] is sorted according to the direction of the positrons beam:, starting from rack 071 (DEVIL365 > 364 > 367 > 366) |
...