You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 27 Next »

Target releasealpha 1.0
Epic
Document status
DRAFT
Document owner
Designer
Developers
QA

Goals

  • improve the stability of the DAFNE orbit acquisition system.

Overall strategy

  • develop and debug the new DEVIL204 along with the regular run of the legacy system;
  • get rid of the phisical DEVIL204 by moving its code to a virtual machine;
  • get rid of the 4 LEXTEL couples by employing the SIS3153 VME Ethernet controllers.

Repository

TypeDetails

Type

git

Link / Path

https://baltig.infn.it/lnf-da-control/lv-dcs-new204
NOTE: the only file included in the git repo is GOD.lvproj . No VIs are included in the git repo at this moment.

Branch

main

Hardware description

TypeDescription
ProcessorStandard DANTE virtual machine vldantedevxxx
VME controllers

Nr. 4 VME controller SIS3153 USB-0 USB3.0-VME Interface with 1 Gbps SFP Tranceiver

VME hardwareStandard Apple DEVILs (364-5-6-7), HP DVM+MUX
HardwareBergotz modules for BPM signal acquisition

Programming languages

LanguageRequired Add ons/Plugins/Extensions/Libraries
LabVIEW 12.0.1f5 (32-bit)

liblv2vmechaos.lvlib (for SIS3153 usage)
git repo: https://baltig.infn.it/chaos-lnf-control/lv-vme-chaos-driver.git

Description

Due to safety reasons, the development of the new DEVIL204 takes place on the virtual machine vldantedev038 that temporarily mounts a copy of the dcs_lv12/source_linux actual directory.
Any VIs and data files created/modified/removed concern the directories:

/u2/dcs/source_linux//0_classes/GOD/
/u2/dcs/source_linux/devils/DISARMED/DEVIL204-NEW/
/u2/dcs/source_linux/lib/lv-vme-chaos-driver/

Any derogation from this assumption will be highlighted.

Repo git della librearia di accesso alla SIS3153, clonato in: /u2/dcs/source_linux/lib/lv-vme-chaos-driver
(dovrebbe stare nella /usr/local/natinst/LabVIEW-2012/user.lib/ ma questo andrebbe poi fatto su tutte le macchine. Messo invece nella .../source_linux/lib/ , di modo che valga per tutti).

Repo git del progetto LabVIEW GOD.lvprog del nuovo DEVIL204, clonato in .../u2/dcs/source_linux//0_classes/GOD/

Warnings and Fixes to be done

Warnings

GGODSta.vi and GGODDyn.vi have the "append" and "write" cases DISABLED to avoid memcached real write operations

To be done

I DBFiles dei DEVILs 364, 365, 366, 367 sono sbagliati (il DEVIL365 ha 24 componenti e NON 23 come scritto nel DBFile Solaris). 

The VIs .../0_classes/GOD/library/fetchORB[Sta|Dyn].vi and their SubVIs .../0_classes/GOD/library/bundleORB[Sta|Dyn].vi must be optimized by moving the code that parses the descriptors in the "init" frame so that it is executed only once.

Al momento la difficoltà maggiore è quella di riottenere una tabella di ordinamento tramite i VIs:
precompileORB.vi
precompileORB_IR.vi
I suddetti VIs sono stati modificati per quanto riguarda il recupero degli indirizzi ma ci sono degli errori.

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

BoolddInLegacy data-dependency input

Indicators

Data type

Name

Description

BoolddOut

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

The connector pane pattern for all initHWXXX VIs is fixed and mandatory and – for (wrong) historical reasons – does not return any errors.

Examples

---

closeGOD.vi

Close the IP connections with the four VME SIS3153 controllers and dispose the connection handles.

Controls

Data type

Name

Description

BoolddInLegacy data-dependency input
errorClustererrorIn


Indicators

Data type

Name

Description

BoolddOutLegacy data-dependency output
errorClustererrorOut

Details

---

Examples

---

GGODConnection.vi

Array of cluster. Some variables are constants saved as default values

Variables

Data type

Name

Type

Description

abcDEVILconstant[ 364, 365 ,366, 367 ] (see fig. 1-a, 1-b)
abcelementconstant

[ 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)

abccontrollerIPconstant[ 192.168.192.91, 192.168.192, 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)
U32vme handle
Written at startup by the initHWGOD.vi
U32DEVILBaseAddressconstant0xE0000000 for all 4 DEVILs
U32DEVILBufferOffsetconstant0x200000 (2 MB) for all 4 DEVILs
abcHCIDynDescriptorconstant

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".

U32HCIDynOffsetconstantPosition of the dynamic fork in the DEVIL memory. It varies depending on the lenght of other data written before in memory
U32HCIDynNumOfLongwordsconstantThe 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.
abcHCIStaDescriptorconstant

 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".

U32HCIStaOffsetconstantPosition of the static fork in the DEVIL memory. It varies depending on the lenght of other data written before in memory.
U32HCIStaNumOfLongwordsconstantThe 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.


Turn for electronsTurn for positrons



Figure 1-a: The sequence [0,1,2,3] is sorted according to the direction of the electrons beam: starting from rack 071 (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 063 (DEVIL365 > 364 > 367 > 366)

Details

---

Examples

---


GRawBuffer.vi

LNFDCS-122 - Getting issue details... STATUS

  • No labels