# # Set a DIM_SERVERNAME # #SERVERNAME "hvcrate00" # # BITRATE # only supported: 125 or 250 BITRATE 250 # # Devicetype specify # 0 for HW_PCI # 1 for HW_USB # #DEVICETYPE 0 # # CANPORTNUMBER: # 0 means first detected # 1..n specify #CANPORTNUMBER 0 # # LOG FACILITY # specify the local facility. To use syslog to create own logfile # eg logfacility local0 .. local7 : # # add in /etc/syslog.conf: local0.* /var/log/iseg2dim # append ";local0.none" to /var/log/messages line to prevent double logging # LOGFACILITY "local0" # # Loglevel, set from # 0 (silent) ... 7 (debug) # don't set below 3 # To log every received command set to >=6 # #define LOG_EMERG 0 /* system is unusable */ #define LOG_ALERT 1 /* action must be taken immediately */ #define LOG_CRIT 2 /* critical conditions */ #define LOG_ERR 3 /* error conditions */ #define LOG_WARNING 4 /* warning conditions */ #define LOG_NOTICE 5 /* normal but significant condition */ #define LOG_INFO 6 /* informational */ #define LOG_DEBUG 7 /* debug-level messages */ # LOGLEVEL 6 # # The backlog contains the last messages that were sent and received on a CAN # bus. It is useful to debug error conditions on the bus, because one can go # back and inspect the traffic history after a problem. # # The maximum number of messages and the directory where the dump files are # written can be configured. A size of 0 disables the backlog facility. # BACKLOG_SIZE 1000 BACKLOG_DIR /var/log/iseg2dim-backlog # floats get min/max # ints only Interval # Case Sensitive # Currents in uA # deadbands in % 0..100 # min max f. Integer: # DimService is update every min s if it is changing # DimService is update every max s if it is constant # # Settings per Crate # crate_alive_Interval_min 2 crate_alive_Interval_max 60 crate_On_Interval_min 2 crate_On_Interval_max 60 crate_Supply24V_Interval_max 60 crate_Supply24V_Interval_min 3 crate_Supply24V_deadband 5 crate_Supply5V_Interval_max 60 crate_Supply5V_Interval_min 3 crate_Supply5V_deadband 5 crate_Battery_Interval_max 60 crate_Battery_Interval_min 3 crate_Battery_deadband 5 crate_TempBackPlane_Interval_max 60 crate_TempBackPlane_Interval_min 3 crate_TempBackPlane_deadband 5 crate_TempPowerSupply_Interval_max 60 crate_TempPowerSupply_Interval_min 3 crate_TempPowerSupply_deadband 5 crate_StatusACLinePower_Interval_min 2 crate_StatusACLinePower_Interval_max 60 crate_Status_Interval_min 2 crate_Status_Interval_max 60 crate_SoftwareID_Interval_min 30 crate_SoftwareID_Interval_max 120 crate_DeviceID_Interval_min 30 crate_DeviceID_Interval_max 120 # # Settings per Module # mod_DeviceClass_Interval_min 60 mod_DeviceClass_Interval_max 120 mod_GeneralStat_Interval_min 2 mod_GeneralStat_Interval_max 60 mod_Status_Interval_min 2 mod_Status_Interval_max 60 mod_RampSpeed_Interval_max 60 mod_RampSpeed_Interval_min 5 mod_RampSpeed_deadband 5 # Alarm and AlarmInformation is event driven, never updated periodicaly mod_Alarm_Interval_min 60 mod_Alarm_Interval_max 60 mod_AlarmInformation_Interval_min 60 mod_AlarmInformation_Interval_max 60 mod_Control_Interval_min 5 mod_Control_Interval_max 60 mod_EventStatus_Interval_min 5 mod_EventStatus_Interval_max 60 mod_EventMask_Interval_min 5 mod_EventMask_Interval_max 60 mod_EventChannelStatus_Interval_min 5 mod_EventChannelStatus_Interval_max 60 mod_EventChannelMask_Interval_min 5 mod_EventChannelMask_Interval_max 60 mod_On_Interval_min 5 mod_On_Interval_max 60 mod_Emcy_Interval_min 5 mod_Emcy_Interval_max 60 mod_Supply24V_Interval_max 120 mod_Supply24V_Interval_min 60 mod_Supply24V_deadband 5 mod_Supply5V_Interval_max 120 mod_Supply5V_Interval_min 60 mod_Supply5V_deadband 5 mod_BoardTemp_Interval_max 120 mod_BoardTemp_Interval_min 60 mod_BoardTemp_deadband 5 mod_ErrThreshold_Interval_max 120 mod_ErrThreshold_Interval_min 60 mod_ErrThreshold_deadband 5 mod_QueueSize_Interval_min 5 mod_QueueSize_Interval_max 60 # # Settings per Channel # ch_VMeas_Interval_max 10 ch_VMeas_Interval_min 1 ch_VMeas_deadband 5 ch_IMeas_Interval_max 10 ch_IMeas_Interval_min 1 ch_IMeas_deadband 5 ch_VSet_Interval_max 60 ch_VSet_Interval_min 3 ch_VSet_deadband 5 ch_ISet_Interval_max 60 ch_ISet_Interval_min 3 ch_ISet_deadband 5 ch_NominalV_Interval_max 120 ch_NominalV_Interval_min 60 ch_NominalV_deadband 5 ch_NominalI_Interval_max 120 ch_NominalI_Interval_min 60 ch_NominalI_deadband 5 ch_Status_Interval_min 2 ch_Status_Interval_max 60 ch_Stat_Interval_min 2 ch_Stat_Interval_max 60 ch_On_Interval_min 2 ch_On_Interval_max 60 ch_EventStatus_Interval_min 30 ch_EventStatus_Interval_max 60 ch_EventMask_Interval_min 30 ch_EventMask_Interval_max 60 ch_doClear_Interval_min 60 ch_doClear_Interval_max 120 # ALIAS keyword and parameters are case sensitive # usage ALIAS # eg ALIAS hvcrate00.mod00.ch00 sm3.l4.drift # include Servername! # Example ALIAS for full equipped devclass21 crate: #ALIAS hvcrate00.crate sm00-sm06 ##------------------------------------------ #ALIAS iseg2dim.bus0.mod08 hcvrate.SM01-1 #ALIAS iseg2dim.bus0 hvcrate00 # prevent channel 15 from being renamed to avoid collisions when renaming channels #ALIAS (iseg2dim\.bus\d+\.mod\d+.ch15\..*) \1 #----------------------------------------------------------------------------- # Stack-wise renaming of channels (UNTESTED!!!) # # Note: this is the default mapping, used e.g. at CERN # # These aliases rename the channels of two modules that control the anode # or drift voltages of one supermodule, respectively. The first module # controls stacks 0 and 1 and layers 0-2 of stack 2. The second module # controls layers 3-5 of stack 2 and stacks 3 and 4. #----------------------------------------------------------------------------- #ALIAS iseg2dim\.bus0\.mod(1[23]).ch(\d+)\.(.*) HV.17_$[((\1%2)*15+\2)%6]_$[((\1%2)*15+\2)/5].ANODE.\3 #ALIAS iseg2dim\.bus0\.mod(1[23]).ch(\d+)\.(.*) HV.17_$[((\1%2)*15+\2)%6]_$[((\1%2)*15+\2)/5].DRIFT.\3 #----------------------------------------------------------------------------- # Layer-wise renaming of channels # # Note: this mapping is only used for super-module integration in Muenster # # These aliases rename the channels of two modules that control the anode # or drift voltages of one supermodule, respectively. The first module # controls layers 0-2 and the second module layers 3-5. #----------------------------------------------------------------------------- #ALIAS iseg2dim\.bus0\.mod(1[45]).ch(\d+)\.(.*) HV.00_$[\2%5]_$[(\1%2)*3+\2/5].ANODE.\3 #ALIAS iseg2dim\.bus0\.mod(1[23]).ch(\d+)\.(.*) HV.00_$[\2%5]_$[(\1%2)*3+\2/5].DRIFT.\3 #----------------------------------------------------------------------------- # Alias to mimick the old naming scheme used at CERN that supported only # a single CAN bus and a single crate per server process. # # The first alias ensures that the crate services are presented without # a number, the second alias renames all other services. # ----------------------------------------------------------------------------- # ALIAS iseg2dim\.bus0\.crate(\d+)\.(.*) ra99cr99.crate.\2 # ALIAS iseg2dim\.bus0\.(.*) ra99cr99.\1 ALIAS iseg2dim\.bus0\.crate(\d+)\.(.*) ra14cr3.crate.\2 ALIAS iseg2dim\.bus0\.(.*) ra14cr3.\1 ALIAS iseg2dim\.bus1\.crate(\d+)\.(.*) ra14cr2.crate.\2 ALIAS iseg2dim\.bus1\.(.*) ra14cr2.\1 #ALIAS iseg2dim.bus0.crate0 HV.SM00.CRATE #ALIAS iseg2dim.bus0.mod08 HV.SM00.MOD_ANODE_LO #ALIAS iseg2dim.bus0.mod09 HV.SM00.MOD_ANODE_HI #ALIAS iseg2dim.bus0.mod10 HV.SM00.MOD_DRIFT_LO #ALIAS iseg2dim.bus0.mod11 HV.SM00.MOD_DRIFT_HI