...
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 | ||
|---|---|---|
| ||
%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 Include | ||||
|---|---|---|---|---|
|
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
...