APSU PVs - Revision history

Jkirchman: /* PSS PVs */ Use png for PSS list since pdf is not supported by wiki-ext

2026-04-20T22:12:18Z

PSS PVs: Use png for PSS list since pdf is not supported by wiki-ext

← Older revision		Revision as of 22:12, 20 April 2026
Line 148:		Line 148:
	The SI group has assured us that '''for Gen3 PSS system the shutter control PVs did not change. Only the Gen4 systems PVs were changed.''' For the second run in 2024, the Gen4 systems are at 8ID, 9ID, 15ID, 16BM, 19ID, 20ID, 22ID, 25ID and 31ID, 33ID and 34ID.		The SI group has assured us that '''for Gen3 PSS system the shutter control PVs did not change. Only the Gen4 systems PVs were changed.''' For the second run in 2024, the Gen4 systems are at 8ID, 9ID, 15ID, 16BM, 19ID, 20ID, 22ID, 25ID and 31ID, 33ID and 34ID.

	[[:Media:PSS Version List.~~pdf~~\|Latest beamline PSS version list (~~PDF~~)]]		[[:Media:PSS Version List.png\|Latest beamline PSS version list (PNG)]]

	This list was last updated in March 2026 and details the PSS Gen version at each beamline.		This list was last updated in March 2026 and details the PSS Gen version at each beamline.

Jkirchman: Sync with the latest changes to the internal wiki

2026-04-20T21:56:03Z

Sync with the latest changes to the internal wiki

← Older revision		Revision as of 21:56, 20 April 2026
Line 102:		Line 102:

	===New===		===New===
	These PVs are new and were not ~~present~~ before:		These PVs are new and were not there before:
	Sxxyy-FEEPS:TripsExistM		Sxxyy-FEEPS:TripsExistM
	0 OFF (No Trip)		0 OFF (No Trip)
Line 144:		Line 144:
	There have been a significant amount of PV changes with the PSS PVs. Unfortunately there is no easy translation tool from older PVs to the new APSU PSS PVs.		There have been a significant amount of PV changes with the PSS PVs. Unfortunately there is no easy translation tool from older PVs to the new APSU PSS PVs.

	~~Each~~ beamline could look at the PSS Input/Output EPICS screens to determine what their new PVs are. This can be done by starting up /APSshare/adlsys/xfd-display then selecting the light blue "PSS" button, then selecting "Main" from the menu and then ~~find~~ the drop-down blue button for the beamline (e.g. 27-ID). From there select either "Inputs" or "Outputs~~". If the beamline is a Gen4 system, then select either "Systems" or "Stations~~". These 2 EPICS screens will display all of the PSS PVs and you can find the appropriate ones needed.		It has been suggested that each beamline could look at the PSS Input/Output EPICS screens to determine what their new PVs are. This can be done by starting up /APSshare/adlsys/xfd-display then selecting the light blue "PSS" button, then selecting "Main" from the menu and then finding the drop-down blue button for the beamline (e.g. 27-ID). From there select either "Inputs" or "Outputs". These 2 EPICS screens will display all of the PSS PVs and you can find the appropriate ones needed.

			The SI group has assured us that '''for Gen3 PSS system the shutter control PVs did not change. Only the Gen4 systems PVs were changed.''' For the second run in 2024, the Gen4 systems are at 8ID, 9ID, 15ID, 16BM, 19ID, 20ID, 22ID, 25ID and 31ID, 33ID and 34ID.

			[[:Media:PSS Version List.pdf\|Latest beamline PSS version list (PDF)]]

			This list was last updated in March 2026 and details the PSS Gen version at each beamline.

	According to the SI group, '''for Gen3 PSS system the shutter control PVs did not change. Only the Gen4 systems PVs were changed.''' For this second run in 2024, the Gen4 systems will be 8ID, 9ID, 15ID, 16BM, 19ID, 20ID, 22ID, 25ID (to be completed after the Aug 2024 shutdown), 31ID, 33ID and 34ID. [[:File:PSS_Version_List.png\|This list details the PSS Gen version at each beamline]]
	See the following example PSS Gen4 PVs where:		See the following example PSS Gen4 PVs where:
	xx = 2 digit sector number		xx = 2 digit sector number

Jkirchman: Update date for the PV gateway list

2025-01-31T16:12:50Z

Update date for the PV gateway list

← Older revision		Revision as of 16:12, 31 January 2025
Line 8:		Line 8:

	==PV Gateways==		==PV Gateways==
	In order to access the APS-U PVs, each beamline host needs to know where to find these PVs. This is the function of a PV gateway which IT has configured for each beamline. The PV gateway's network interface is updated to include the new private VLAN for the IOCs which host the APS-U PVs. This PV gateway configuration maintenance is performed by Marty Smith in CTL and Brian Robinson in IT. See the list of [[:File:pvgateway_list.png\|PVgateways]] at the beamlines (as of ~~2024~~-06-27).		In order to access the APS-U PVs, each beamline host needs to know where to find these PVs. This is the function of a PV gateway which IT has configured for each beamline. The PV gateway's network interface is updated to include the new private VLAN for the IOCs which host the APS-U PVs. This PV gateway configuration maintenance is performed by Marty Smith in CTL and Brian Robinson in IT. See the list of [[:File:pvgateway_list.png\|PVgateways]] at the beamlines (as of 2025-01-31).

	'''Important things to note:'''		'''Important things to note:'''

Jkirchman: Modifications made by Marty Smith: Updated page so that beamlines will know not to specifically set EPICS_CA_ADDR_LIST but are supplied with an alternative

2025-01-31T15:46:39Z

Modifications made by Marty Smith: Updated page so that beamlines will know not to specifically set EPICS_CA_ADDR_LIST but are supplied with an alternative

← Older revision		Revision as of 15:46, 31 January 2025
Line 3:		Line 3:
	This wiki will help to describe what is new, what has been removed, and how to convert to using some of the new PVs available.		This wiki will help to describe what is new, what has been removed, and how to convert to using some of the new PVs available.

	~~As mentioned elsewhere here,~~ Mark Rivers has documented the process he used to find the relevant medm screens and the useful PVs for his beamline:		Mark Rivers has documented the process he used to find the relevant medm screens and the useful PVs for his beamline:
	https://github.com/CARS-UChicago/GSECARS-EPICS/blob/master/docs/EPICS_Beamline_PVs.docx		https://github.com/CARS-UChicago/GSECARS-EPICS/blob/master/docs/EPICS_Beamline_PVs.docx
	https://github.com/CARS-UChicago/GSECARS-EPICS/blob/master/docs/EPICS_Beamline_PVs.pdf		https://github.com/CARS-UChicago/GSECARS-EPICS/blob/master/docs/EPICS_Beamline_PVs.pdf
Line 10:		Line 10:
	In order to access the APS-U PVs, each beamline host needs to know where to find these PVs. This is the function of a PV gateway which IT has configured for each beamline. The PV gateway's network interface is updated to include the new private VLAN for the IOCs which host the APS-U PVs. This PV gateway configuration maintenance is performed by Marty Smith in CTL and Brian Robinson in IT. See the list of [[:File:pvgateway_list.png\|PVgateways]] at the beamlines (as of 2024-06-27).		In order to access the APS-U PVs, each beamline host needs to know where to find these PVs. This is the function of a PV gateway which IT has configured for each beamline. The PV gateway's network interface is updated to include the new private VLAN for the IOCs which host the APS-U PVs. This PV gateway configuration maintenance is performed by Marty Smith in CTL and Brian Robinson in IT. See the list of [[:File:pvgateway_list.png\|PVgateways]] at the beamlines (as of 2024-06-27).

	If the PV gateway ~~has not been configured, it~~'~~s still possible~~ to ~~direct~~ PV ~~queries~~ to the ~~appropriate host. The~~ environment variable ~~EPICS_HOST_ADDR_LIST can be set~~ to ~~point to a gateway configured for~~ the ~~new APSU PVs~~. ~~One such gateway~~ is ~~c2gate1-188 (164.54.188.8)~~.		'''Important things to note:'''
	setenv ~~EPICS_HOST_ADDR_LIST 164.54.188.8~~ (for cshell)		* There are 44 PV gateways at APS and you will get write access to certain PVs through only 1
	export ~~EPICS_HOST_ADDR_LIST~~=~~164.54.188.8~~ (for bash)		* LOM office and perhaps lab networks are usually not the same as the beamline network
	~~This list can include multiple IPs each separated by~~ a ~~space~~. ~~It may~~ be ~~the case that a computer used in an LOM requires setting this list~~ to access ~~APS-U~~ PVs. ~~However, be aware that if two working gateways are included with~~ the ~~addition~~ of the ~~EPICS_HOST_ADDR_LIST multiple responses~~ to ~~a PV access could be received~~. If this ~~occurs, redefine~~ the ~~EPICS_HOST_ADDR_LIST~~ to ~~remove~~ the ~~unnecessary gateway~~.		* LOM offices and perhaps labs will have read only access (if not part of the beamline network)
			* PV write access is granted ONLY from the beamline network PV gateway
	~~Some PVs~~, e.g. ~~undulator~~ PVs~~, can only be written by select users and hosts. Marty maintains~~ a ~~list of those users and hosts~~ in a ~~permissions file. One configuration line contains the list of hosts permitted~~ to ~~perform writes and another line~~ the ~~users permitted to write. Below~~ is the ~~configuration for 27ID where 2 users are allowed~~ (~~rixs and vw5~~) ~~and several~~ computer hosts:
	~~HAG(sector27) {oriana,oriana~~.~~xray.aps~~.anl.gov~~,grimlok,grimlok~~.~~xray~~.~~aps~~.~~anl.gov~~,~~oswin,oswin~~.~~xray~~.~~aps~~.~~anl~~.~~gov,ioc27idmot1,ioc27idmot2,oribi,oribi~~.~~xray~~.~~aps~~.~~anl.gov}~~		===LOM Access to PVs===
	~~UAG(sector27) {rixs,vw5}~~		To get '''read only access''' to accelerator PVs you can run the command /APSshare/adlsys/xfd-display which uses a round robin technique to select 1 of 3 PV gateways; as such you don't know which one you are using, nor should you care. Also using this script you do not need to set any EPICS environment variables unless you need to see PVs from an IOC on your local network. If this is the case then use the environment variable EPICS_CA_AUTO_ADDR_LIST as shown below. This will tell your EPICS Channel Access (CA) client to also do PV searches on all network interfaces that the host machine has. There is no need to set the EPICS_CA_ADDR_LIST environment variable for this case.
	''It's advisable to verify with Marty Smith that the hosts in his list are still the appropriate ones for a beamline.'' Beamline computers are replaced often and the PV gateway permissions file may have stale data.		setenv EPICS_CA_AUTO_ADDR_LIST YES (for cshell)
			export EPICS_CA_AUTO_ADDR_LIST=YES (for bash)

			In order to get write access to accelerator PVs you need to be running your CA client on a beamline host. Then you will be able to access both the beamline hosted PVs as well as the accelerator PVs of interest. Setting the environment variable EPICS_CA_ADDR_LIST is not enough because the other end of the connection does not necessarily know how to send the information back to your CA client. To clarify this statement if you were to set the EPICS_CA_ADDR_LIST environment variable to include the beamline network then the CA search request might get through to the beamline network. However, the CA server (i.e. EPICS IOC) may not know how to get the response back across to the LOM network. Doubtful that this would work without more effort.

			===Beamline Access to PVs===
			There is a PV gateway that is located in the APS computer room that has a connection to the beamline network; most often this gateway has a name that looks like sxxpvgate where xx is the beamline sector number and in some instances will also include the beamline (id or bm). All computer hosts on this network have at a minimum '''read access''' to all accelerator PVs. Write access may be allowed to some PVs such as insertion device controls and beamline shutters. If not, then this is simply an email request to [mailto:mls@anl.gov Marty Smith].

			===PV Gateway Access Security for Beamlines===
			Often times a new beamline computer is added to the beamline network and this does not mean you get the same write permission to PVs that you had on another computer. There are many ways to set up the access security in the PV gateway and currently this decision is left up to the resident beamline personnel. However, in order to make an informed decision about this you will need to know your options; this can be as secure as you would like.
			Here are the options you have to select from:
			1. You must be logged in as a certain user name and logged into a certain computer (This is the most secure method)
			You might have multiple computer names and user names. This would mean that you '''MUST''' be in the user list AND logged into one of the hosts in the
			computer list.
			2. You must be logged into a certain computer but any user logged in has access (This is a list of computer host names)
			3. You must be a certain user logged in
			This means that as long as you are a user in the user name list you can get control from any computer with in the same subnet as the
			beamline PV gateway.

			''It's advisable to verify with [mailto:mls@anl.gov Marty Smith] that the hosts in his list are still the appropriate ones for a beamline.'' Beamline computers are replaced often and the PV gateway permissions file may have stale data.

	==All APS-U PVs==		==All APS-U PVs==
Line 45:		Line 64:

	===Changed===		===Changed===
	Old PV Name: New PV Name~~: 0: 1: 2: 3: 4~~:		Old PV Name: New PV Name:
	EPS:xx:yy:PS1:POSITION Sxxyy-FEEPS:PS1:PositionM Moving Closed Open Position Error		EPS:xx:yy:PS1:POSITION Sxxyy-FEEPS:PS1:PositionM
	EPS:xx:yy:PS2:POSITION Sxxyy-FEEPS:PS2:PositionM Moving Closed Open Position Error		0 Moving
	EPS:xx:yy:SS1:POSITION Sxxyy-FEEPS:SS1:PositionM Moving Closed Open Position Error		1 Closed
	EPS:xx:yy:SS2:POSITION Sxxyy-FEEPS:SS2:PositionM Moving Closed Open Position Error		3 Open
	EPS:xx:yy:FEV:POSITION Sxxyy-FEEPS:FEV:PositionM Moving Closed Open Position Error		4 Position Error
	EPS:xx:yy:BIV:POSITION Sxxyy-FEEPS:BIV:PositionM Moving Closed Open Position Error
			EPS:xx:yy:PS2:POSITION Sxxyy-FEEPS:PS2:PositionM
			0 Moving
			1 Closed
			3 Open
			4 Position Error

			EPS:xx:yy:SS1:POSITION Sxxyy-FEEPS:SS1:PositionM
			0 Moving
			1 Closed
			3 Open
			4 Position Error

			EPS:xx:yy:SS2:POSITION Sxxyy-FEEPS:SS2:PositionM
			0 Moving
			1 Closed
			3 Open
			4 Position Error

			EPS:xx:yy:FEV:POSITION Sxxyy-FEEPS:FEV:PositionM
			0 Moving
			1 Closed
			3 Open
			4 Position Error

			EPS:xx:yy:BIV:POSITION Sxxyy-FEEPS:BIV:PositionM
			0 Moving
			1 Closed
			3 Open
			4 Position Error

	===New===		===New===

Jkirchman: /* Changed */ Made EPS into more like a table and easier to read

2024-09-11T16:06:31Z

Changed: Made EPS into more like a table and easier to read

← Older revision		Revision as of 16:06, 11 September 2024
Line 45:		Line 45:

	===Changed===		===Changed===
	Old PV Name: New PV Name:		Old PV Name: New PV Name: 0: 1: 2: 3: 4:
	EPS:xx:yy:PS1:POSITION Sxxyy-FEEPS:PS1:PositionM		EPS:xx:yy:PS1:POSITION Sxxyy-FEEPS:PS1:PositionM Moving Closed Open Position Error
	0 Moving		EPS:xx:yy:PS2:POSITION Sxxyy-FEEPS:PS2:PositionM Moving Closed Open Position Error
	1 Closed		EPS:xx:yy:SS1:POSITION Sxxyy-FEEPS:SS1:PositionM Moving Closed Open Position Error
	3 Open		EPS:xx:yy:SS2:POSITION Sxxyy-FEEPS:SS2:PositionM Moving Closed Open Position Error
	4 Position Error		EPS:xx:yy:FEV:POSITION Sxxyy-FEEPS:FEV:PositionM Moving Closed Open Position Error
			EPS:xx:yy:BIV:POSITION Sxxyy-FEEPS:BIV:PositionM Moving Closed Open Position Error
	EPS:xx:yy:PS2:POSITION Sxxyy-FEEPS:PS2:PositionM
	0 Moving
	1 Closed
	3 Open
	4 Position Error

	EPS:xx:yy:SS1:POSITION Sxxyy-FEEPS:SS1:PositionM
	0 Moving
	1 Closed
	3 Open
	4 Position Error

	EPS:xx:yy:SS2:POSITION Sxxyy-FEEPS:SS2:PositionM
	0 Moving
	1 Closed
	3 Open
	4 Position Error

	EPS:xx:yy:FEV:POSITION Sxxyy-FEEPS:FEV:PositionM
	0 Moving
	1 Closed
	3 Open
	4 Position Error

	EPS:xx:yy:BIV:POSITION Sxxyy-FEEPS:BIV:PositionM
	0 Moving
	1 Closed
	3 Open
	4 Position Error

	===New===		===New===

Jkirchman: /* PSS PVs */

2024-09-11T15:00:38Z

PSS PVs

← Older revision		Revision as of 15:00, 11 September 2024
Line 125:		Line 125:
	There have been a significant amount of PV changes with the PSS PVs. Unfortunately there is no easy translation tool from older PVs to the new APSU PSS PVs.		There have been a significant amount of PV changes with the PSS PVs. Unfortunately there is no easy translation tool from older PVs to the new APSU PSS PVs.

	Each beamline could look at the PSS Input/Output EPICS screens to determine what their new PVs are. This can be done by starting up /APSshare/adlsys/xfd-display then selecting the light blue PSS button, then selecting the drop-down blue button for the beamline (e.g. 27-ID). From there select either "Inputs" or "Outputs". If the beamline is a Gen4 system, then select either "Systems" or "Stations". These 2 EPICS screens will display all of the PSS PVs and you can find the appropriate ones needed.		Each beamline could look at the PSS Input/Output EPICS screens to determine what their new PVs are. This can be done by starting up /APSshare/adlsys/xfd-display then selecting the light blue "PSS" button, then selecting "Main" from the menu and then find the drop-down blue button for the beamline (e.g. 27-ID). From there select either "Inputs" or "Outputs". If the beamline is a Gen4 system, then select either "Systems" or "Stations". These 2 EPICS screens will display all of the PSS PVs and you can find the appropriate ones needed.

	According to the SI group, '''for Gen3 PSS system the shutter control PVs did not change. Only the Gen4 systems PVs were changed.''' For this second run in 2024, the Gen4 systems will be 8ID, 9ID, 15ID, 16BM, 19ID, 20ID, 22ID, 25ID (to be completed after the Aug 2024 shutdown), 31ID, 33ID and 34ID. [[:File:PSS_Version_List.png\|This list details the PSS Gen version at each beamline]]		According to the SI group, '''for Gen3 PSS system the shutter control PVs did not change. Only the Gen4 systems PVs were changed.''' For this second run in 2024, the Gen4 systems will be 8ID, 9ID, 15ID, 16BM, 19ID, 20ID, 22ID, 25ID (to be completed after the Aug 2024 shutdown), 31ID, 33ID and 34ID. [[:File:PSS_Version_List.png\|This list details the PSS Gen version at each beamline]]

Jkirchman: /* Insertion Device (Undulator) PVs */ Update to some of the ID PVs.

2024-07-31T18:53:15Z

Insertion Device (Undulator) PVs: Update to some of the ID PVs.

← Older revision		Revision as of 18:53, 31 July 2024
Line 205:		Line 205:

	$(xx) = 2 digit sector number		$(xx) = 2 digit sector number
	$(yy) = US or DS (Position of ID in storage ring straight)		$(yy) = us or ds
			$(YY) = US or DS (Position of ID in storage ring straight)
	(Note: there are not any xx or yy display subs, display substitution is P=SxxID:yyID)		(Note: there are not any xx or yy display subs, display substitution is P=SxxID:yyID)
	===Changed===		===Changed===
	====Control Process Variables====		====Control Process Variables====
	--------------------------------------------------------------		--------------------------------------------------------------
	Old PV Name: New PV Name:		Old PV Name: New PV Name:
	ID$(xx):GapSet S$(xx)ID:$(yy)ID:GapSetC		ID$(xx)$(yy):GapSet S$(xx)ID:$(YY)ID:GapSetC
	ID$(xx):TaperGapSet S$(xx)ID:$(yy)ID:TaperGapSetC		ID$(xx)$(yy):TaperGapSet S$(xx)ID:$(YY)ID:TaperGapSetC
	ID$(xx):ScanGap S$(xx)ID:$(yy)ID:ScanGapC		ID$(xx)$(yy):ScanGap S$(xx)ID:$(YY)ID:ScanGapC
	ID$(xx):ScanEnergy S$(xx)ID:$(yy)ID:ScanEnergyC		ID$(xx)$(yy):ScanEnergy S$(xx)ID:$(YY)ID:ScanEnergyC
	ID$(xx):EnergySet S$(xx)ID:$(yy)ID:EnergySetC		ID$(xx)$(yy):EnergySet S$(xx)ID:$(YY)ID:EnergySetC
	ID$(xx):TaperEnergySet S$(xx)ID:$(yy)ID:TaperEnergySetC		ID$(xx)$(yy):TaperEnergySet S$(xx)ID:$(YY)ID:TaperEnergySetC
	ID$(xx):DeadbandGap S$(xx)ID:$(yy)ID:DeadbandGapC		ID$(xx)$(yy):DeadbandGap S$(xx)ID:$(YY)ID:DeadbandGapC
	ID$(xx):HarmonicValue S$(xx)ID:$(yy)ID:HarmonicValueC		ID$(xx)$(yy):HarmonicValue S$(xx)ID:$(YY)ID:HarmonicValueC
	ID$(xx):Start S$(xx)ID:$(yy)ID:StartC		ID$(xx)$(yy):Start S$(xx)ID:$(YY)ID:StartC
	ID$(xx):Stop S$(xx)ID:$(yy)ID:~~StopC~~		ID$(xx)$(yy):Stop S$(xx)ID:$(YY)ID:StopC
			ID$(xx)$(yy):AccessSecurity S$(xx)ID:$(YY)ID:AccessSecurityC
			ID$(xx)$(yy):MotorSpeed S$(xx)ID:$(YY)ID:MotorSpeedC
	====Monitor Process Variables====		====Monitor Process Variables====
	-------------------------------------------------------------		-------------------------------------------------------------
	Old PV Name: New PV Name:		Old PV Name: New PV Name:
	ID$(xx):Gap S$(xx)ID:$(yy)ID:GapM		ID$(xx)$(yy):Gap S$(xx)ID:$(YY)ID:GapM
	ID$(xx):TaperGap S$(xx)ID:$(yy)ID:TaperGapM		ID$(xx)$(yy):TaperGap S$(xx)ID:$(YY)ID:TaperGapM
	ID$(xx):Energy S$(xx)ID:$(yy)ID:EnergyM		ID$(xx)$(yy):Energy S$(xx)ID:$(YY)ID:EnergyM
	ID$(xx):TaperEnergy S$(xx)ID:$(yy)ID:TaperEnergyM		ID$(xx)$(yy):TaperEnergy S$(xx)ID:$(YY)ID:TaperEnergyM
	ID$(xx):Busy S$(xx)ID:$(yy)ID:BusyM		ID$(xx)$(yy):Busy S$(xx)ID:$(YY)ID:BusyM
	ID$(xx):Message1 S$(xx)ID:$(yy)ID:Message1M		ID$(xx)$(yy):Message1 S$(xx)ID:$(YY)ID:Message1M
	ID$(xx):Message2 S$(xx)ID:$(yy)ID:Message2M		ID$(xx)$(yy):Message2 S$(xx)ID:$(YY)ID:Message2M
	ID$(xx):Message3 S$(xx)ID:$(yy)ID:Message3M		ID$(xx)$(yy):Message3 S$(xx)ID:$(YY)ID:Message3M
	ID$(xx):OldGapSet S$(xx)ID:$(yy)ID:OldGapSetM		ID$(xx)$(yy):OldGapSet S$(xx)ID:$(YY)ID:OldGapSetM
	ID$(xx):Taper S$(xx)ID:$(yy)ID:TaperM		ID$(xx)$(yy):Taper S$(xx)ID:$(YY)ID:TaperM
	ID$(xx):EncoderSelect S$(xx)ID:$(yy)ID:LinearEncoderUsedM		ID$(xx)$(yy):EncoderSelect S$(xx)ID:$(YY)ID:LinearEncoderUsedM
	ID$(xx):PositionAccuracy S$(xx)ID:$(yy)ID:PositionAccuracyM		ID$(xx)$(yy):PositionAccuracy S$(xx)ID:$(YY)ID:PositionAccuracyM
	ID$(xx):Location S$(xx)ID:$(yy)ID:LocationM		ID$(xx)$(yy):Location S$(xx)ID:$(YY)ID:LocationM
	ID$(xx):Device S$(xx)ID:$(yy)ID:~~DeviceM~~		ID$(xx)$(yy):Device S$(xx)ID:$(YY)ID:DeviceM
	ID$(xx):Version S$(xx)ID:$(yy)ID:$(dd)VersionM		ID$(xx)$(yy):DeviceLimit S$(xx)ID:$(YY)ID:DeviceLimitM
			ID$(xx)$(yy):Version S$(xx)ID:$(YY)ID:$(dd)VersionM
	Where dd = HPMU, Rev (Revolver), STI (2-Motor ID)		Where dd = HPMU, Rev (Revolver), STI (2-Motor ID)
	ID$(xx):~~ShClosedTime ID$(xx)(zz):ShClosedTime~~		ID$(xx):TaperGapReturn S$(xx)ID:$(YY)ID:TaperGapReturnM
	~~Where zz = us or ds~~		ID$(xx):TotalPower S$(xx)ID:$(YY)ID:TotalPowerM
	~~ID$(xx):MotorSpeed~~ S$(xx)ID:$(yy)ID:~~MotorSpeedC~~		ID$(xx):ExpectedPower S$(xx)ID:$(YY)ID:ExpectedPowerM
	ID$(xx):~~GapReturn~~ S$(xx)ID:$(yy)ID:~~GapReturnM~~		ID$(xx):DeviceLimit S$(xx)ID:$(YY)ID:DeviceLimitM
	ID$(xx):~~TaperGapReturn~~ S$(xx)ID:$(yy)ID:~~TaperGapReturnM~~		ID$(xx):Position1 S$(xx)ID:$(YY)ID:Position1M
	ID$(xx):~~TotalPower~~ S$(xx)ID:$(yy)ID:~~TotalPowerM~~		ID$(xx):Position2 S$(xx)ID:$(YY)ID:Position2M
	ID$(xx):~~ExpectedPower~~ S$(xx)ID:$(yy)ID:~~ExpectedPowerM~~
	ID$(xx):~~AccessSecurity S$(xx)ID:$(yy)ID:AccessSecurityC~~
	~~ID$(xx):DeviceLimit~~ S$(xx)ID:$(yy)ID:~~DeviceLimitM~~
	===Removed===		===Removed===
	The synchronous scanning PVs (those beginning with SS) have been removed. It is unlikely that any beamline was using these PVs.		The synchronous scanning PVs (those beginning with SS) have been removed. It is unlikely that any beamline was using these PVs.

Jkirchman: /* Insertion Device PVs */

2024-07-31T18:23:15Z

Insertion Device PVs

← Older revision		Revision as of 18:23, 31 July 2024
Line 197:		Line 197:
	ALL TopUp related information PVs		ALL TopUp related information PVs

	== Insertion Device PVs ==		== Insertion Device (Undulator) PVs ==
	Here is a list of old and new PV names for insertion devices. The names have changed but there is no change to their meanings.		Here is a list of old and new PV names for insertion devices. The names have changed but there is no change to their meanings.

Line 223:		Line 223:
	====Monitor Process Variables====		====Monitor Process Variables====
	-------------------------------------------------------------		-------------------------------------------------------------
			Old PV Name: New PV Name:
	ID$(xx):Gap S$(xx)ID:$(yy)ID:GapM		ID$(xx):Gap S$(xx)ID:$(yy)ID:GapM
	ID$(xx):TaperGap S$(xx)ID:$(yy)ID:TaperGapM		ID$(xx):TaperGap S$(xx)ID:$(yy)ID:TaperGapM

Jkirchman: /* PV Gateways */

2024-06-27T15:03:36Z

PV Gateways

← Older revision		Revision as of 15:03, 27 June 2024
Line 13:		Line 13:
	setenv EPICS_HOST_ADDR_LIST 164.54.188.8 (for cshell)		setenv EPICS_HOST_ADDR_LIST 164.54.188.8 (for cshell)
	export EPICS_HOST_ADDR_LIST=164.54.188.8 (for bash)		export EPICS_HOST_ADDR_LIST=164.54.188.8 (for bash)
	It may be the case that a computer used in an LOM requires this ~~for~~ APS-U PVs. However, be aware that if two working gateways are included with the addition of the EPICS_HOST_ADDR_LIST multiple responses to a PV access could be received. If this occurs, redefine the EPICS_HOST_ADDR_LIST to remove the unnecessary gateway.		This list can include multiple IPs each separated by a space. It may be the case that a computer used in an LOM requires setting this list to access APS-U PVs. However, be aware that if two working gateways are included with the addition of the EPICS_HOST_ADDR_LIST multiple responses to a PV access could be received. If this occurs, redefine the EPICS_HOST_ADDR_LIST to remove the unnecessary gateway.

	Some PVs, e.g. undulator PVs, can only be written by select users and hosts. Marty maintains a list of those users and hosts in a permissions file. One configuration line contains the list of hosts permitted to perform writes and another line the users permitted to write. Below is the configuration for 27ID where 2 users are allowed (rixs and vw5) and several computer hosts:		Some PVs, e.g. undulator PVs, can only be written by select users and hosts. Marty maintains a list of those users and hosts in a permissions file. One configuration line contains the list of hosts permitted to perform writes and another line the users permitted to write. Below is the configuration for 27ID where 2 users are allowed (rixs and vw5) and several computer hosts:

Jkirchman: /* PV Gateways */

2024-06-27T15:01:38Z

PV Gateways

← Older revision		Revision as of 15:01, 27 June 2024
Line 18:		Line 18:
	HAG(sector27) {oriana,oriana.xray.aps.anl.gov,grimlok,grimlok.xray.aps.anl.gov,oswin,oswin.xray.aps.anl.gov,ioc27idmot1,ioc27idmot2,oribi,oribi.xray.aps.anl.gov}		HAG(sector27) {oriana,oriana.xray.aps.anl.gov,grimlok,grimlok.xray.aps.anl.gov,oswin,oswin.xray.aps.anl.gov,ioc27idmot1,ioc27idmot2,oribi,oribi.xray.aps.anl.gov}
	UAG(sector27) {rixs,vw5}		UAG(sector27) {rixs,vw5}
	It's advisable to verify with Marty Smith that the hosts in his list are still the appropriate ones for a beamline. Beamline computers are replaced often and the PV gateway permissions file may have stale data.		''It's advisable to verify with Marty Smith that the hosts in his list are still the appropriate ones for a beamline.'' Beamline computers are replaced often and the PV gateway permissions file may have stale data.

	==All APS-U PVs==		==All APS-U PVs==