Versions Compared

Old Version 82

changes.mady.by.user Alessandro Stecchi

Saved on

compared with

New Version Current

changes.mady.by.user Alessandro Stecchi

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

versionDEVILs
newOCEM_3.4664, 665, 671, 614
For test from 3.2: , 626, 633
newOCEM_3.3ABANDONED (note: some sub-VIs can still have the "_3.3" version in their names)
newOCEM_3.2652, 655, 647, 650, 659, 672, 683, 682, 696, 697, 695, 692 [!C], 693 [!C], 694 [!C], 691 [!C], 673, 674, 675, 676, 678, 644,627, 635
_ethtutti gli altri DEVILs con classe MG1

...

Note

Le versioni _newOCEM_3.3 – utilizzate sino al 15/12/2021 sui DEVIL 664 e 665 sulla vldantedev028 – sono state rimpiazzate dalle _newOCEM_3.4.
Di conseguenza la "_newOCEM_3.3" è abbandonata e deprecata
WARNING: alcuni sub-VI possono ancora avere il nome che termina con "_3.3".

Impostazione GMG1Dyn all'avvio del DEVIL

...

Macchina: vldantedev024 (LabVIEW 2012, SP1)
DEVIL:       671
VNC:         192.168.198.124:5971
prefs:        TCP_DCS port = 6345, idleTime = 100 msIPTable:    da fare

Type

DESIGN NAME

SYSTEM NAME

MAC ADRESS

IP

IP [HEX]

Cavo
+

Cavo
-

RACK

Pulsed Dipole

DP01

DHPTB102

00:90:E8:67:18:61

192.168.190.157

C0A8BE9D

1

2

SABTF2-001

DC Dipole

DH01

DHSTB201

00:90:E8:66:74:D2

192.168.190.158

C0A8BE9E

3

4

SABTF2-001

DC Dipole

DH02

DHSTB202

00:90:E8:66:74:DC

192.168.190.159

C0A8BE9F

5

6

SABTF2-003

DC Dipole

DC01

DHSTB203

00:90:E8:63:EB:5B

192.168.190.160

C0A8BEA0

7

8

SABTF2-003

DC Quadrupole

QUAD01

QUATB201

00:90:E8:67:16:06

192.168.190.151

C0A8BE97

20

19

SABTF2-002

DC Quadrupole

QUAD02

QUATB202

00:90:E8:66:74:D3

192.168.190.152

C0A8BE98

18

17

SABTF2-002

DC Quadrupole

QUAD03

QUATB203

00:90:E8:63:EB:6A

192.168.190.153

C0A8BE99

16

15

SABTF2-002

DC Quadrupole

QUAD04

QUATB204

00:90:E8:67:16:07

192.168.190.154

C0A8BE9A

14

13

SABTF2-002

DC Quadrupole

QUAD05

QUATB205

00:90:E8:66:74:D5

192.168.190.155

C0A8BE9B

12

11

SABTF2-002

DC Quadrupole

QUAD06

QUATB206

00:90:E8:67:18:58

192.168.190.156

C0A8BE9C

10

9

SABTF2-002

...

Link of another table with the same information:
https://docs.google.com/spreadsheets/d/1n2rS3Ecr308gLilQp7u6ZMFP828-Q82ixltUHv28k68/edit?usp=sharing

New elemType descriptors

...

Table of new elemType descriptors. For a full description of these descriptors click here

NOTE (*): byte 1 and byte 3 are decoded by the elemType2InterfaceType VI only for some PS classes:

  • byte 1 is meaningful only for SYS8X00 and serial Modbus
  • byte 3 is meaningful only for E642 and EEI
  • byte 0 and byte 2 do not depend on "protocol" and are passed through as they are.

Be aware that byte 1 and byte 3 can also be used to discriminate other classes (besides those mentioned above) but, in that case, they have to be interpreted by a dedicated piece of code.

Pattern for EEI

byte 3      01 = Type quadrupole DC, 02 = Type dipole DC, 03 = Type dipole pseudo-pulsed
byte 2      00 = bipolar, 01 = unipolar with remote control of polarity change
byte 1       xx = interface type (unique in this case ?) TO BE DECIDED: maybe the pseudo-pulsed should be different
byte 0      07 = Protocol EEI

Pattern for CAENels NGPS

byte 3      xx = TO BE DECIDED
byte 2      xx = TO BE DECIDED
byte 1       xx = TO BE DECIDED
byte 0      08 = Protocol CAENels NGPS

How to search for a specific elemType in all DBSta files

Code Block
titleExample of DBFile for an element of class "MG1"
%MG1
#DHSA*001
@HCI(S)[(I32),(DBL),HU32,DBL,DBL,DBL,DBL,DI32,DBL:2:4]
MG1,DHSA*001,00020000,0.1,3.0,3.0,3.0,1,11.0:12.0:13.0:14.0:21.0:22.0:23.0:24.0
... etc ...
             XXXXXX00
			       --

The first byte of the elementType field, indicates the PS protocol (e.g. in the above example, "00" indicates the protocol SYS8X00).

Using the egrep command

...

Excerpt from  MG1 class documentation

Excerpt Include
MG1 dataset
MG1 dataset

Ethernet connection

Questi alimentatori si connettono in Ethernet e quindi abbiamo lo stesso problema degli alimentatori Genesys e CAENels Easy Driver.
Anche quì, si usa un canale seriale fake per ogni alimentatore e si mette l'IP nel campo subID2.
P.es.: l'IP 192.168.190.131 si scrive come con 4 HEX come C0A8BE83

...

Sviluppo di Command e Control

Si parte dalle versioni _newOCEM_3.3.vi create per i CAENels Easy Driver

...

dalle versioni _newOCEM_3.3.vi create per i CAENels Easy Driver


Jira
serverINFN Ticketing System
columnIdsissuekey,summary,issuetype,created,updated,assignee,priority,status,resolution
columnskey,summary,type,created,updated,assignee,priority,status,resolution
maximumIssues20
jqlQuerykey = lnfdcs-56
serverId8087fedc-8816-3706-9e66-78f987f39e0c

Modifiche rispetto alle versioni precedenti


Note

Le versioni _newOCEM_3.3 – utilizzate sino al 15/12/2021 sui DEVIL 664 e 665 sulla vldantedev028 – sono state rimpiazzate dalle _newOCEM_3.4.
Di conseguenza la "_newOCEM_3.3" è abbandonata e deprecata
WARNING: alcuni sub-VI possono ancora avere il nome che termina con "_3.3".

MG1Ctrl_newOCEM_3.4.vi     EEI in progress, CAENels NGPS beta
MG1Cmd_newOCEM_3.4.vi      EEI in progress, CAENels NGPS beta
initHWMG1_newOCEM_3.4.vi   EEI in progress, CAENels NGPS beta
closeMG1_3.4.vi            EEI in progress, CAENels NGPS ready
.../0_classes/MG1/cmd/exeCmd(MG1)_3.4.vi                       EEI, CAENels NGPS
.../0_classes/MG1/cmd/startCmd-MG1_3.4.vi                      EEI, CAENels NGPS
.../0_classes/MG1/cmd/bypass-MG1_eth_3.3.vi                    EEI, CAENels NGPS
.../0_classes/MG1/cmd/libraries/elemType2InterfaceType_3.3.vi  EEI, CAENels NGPS
.../0_classes/MG1/cmd/libraries/SWTCFinalDataCheckE642_3.3.vi  EEI, CAENels NGPS
.../0_classes/MG1/cmd/libraries/SWTCSeekLastData_3.3.vi        EEI, CAENels NGPS

...