Schedule Commands - Revision history

Gelu: /* Service Mode */

2026-01-20T20:03:58Z

Service Mode

← Older revision		Revision as of 20:03, 20 January 2026
Line 199:		Line 199:
	=== Service Mode ===		=== Service Mode ===

	; SERVICE-IN [antennalist]		; SERVICE-IN antennalist
	: Updates the list of antennas placed into service mode by adding the [antennalist] to the existing list.		: Updates the list of antennas placed into service mode by adding the antennalist to the existing list.
	: The service list is stored in <code>acc.ini</code>.		: The service list is stored in <code>acc.ini</code>.

	After updating the service list, the new antennas added to the list are removed from subarrays and driven to the service position.		After updating the service list, the new antennas added to the list are removed from subarrays and driven to the service position.

	'''Warning''': Once in service position, antennas should be placed in '''local mode'''.		'''Warning''': Once in the service position, antennas should be placed in '''local mode'''.


	; SERVICE-OUT [antennalist]		; SERVICE-OUT antennalist
	: Updates the list of antennas placed into service mode by deleting the [antennalist] from the existing list.		: Updates the list of antennas placed into service mode by deleting the antennalist from the existing list.
	: The service list is stored in <code>acc.ini</code>		: The service list is stored in <code>acc.ini</code>

Gelu: /* Subarrays */

2026-01-19T22:00:45Z

Subarrays

← Older revision		Revision as of 22:00, 19 January 2026
Line 223:		Line 223:
	; SUBARRAY2 antennalist		; SUBARRAY2 antennalist
	: Assigns antennas to subarray2.		: Assigns antennas to subarray2.
	: Antennas must not already be in subarray1.		: Antennas must not already be in subarray1 or in the SERVICE list.

	'''Note''': Since Dec 03, 2015, LO switching is no longer automatic.		'''Note''': Since Dec 03, 2015, LO switching is no longer automatic.

Gelu: /* Service and Subarrays */

2026-01-19T21:39:43Z

Service and Subarrays

← Older revision		Revision as of 21:39, 19 January 2026
Line 210:		Line 210:
	; SERVICE-OUT [antennalist]		; SERVICE-OUT [antennalist]
	: Updates the list of antennas placed into service mode by deleting the [antennalist] from the existing list.		: Updates the list of antennas placed into service mode by deleting the [antennalist] from the existing list.
	: The service list is stored in <code>acc.ini<		: The service list is stored in <code>acc.ini</code>

	'''Warning''': Once out of service, antennas should be explicitely placed in one of the operational subarrays using the SUBARRAY1 and SUBARRAY2 commands.		'''Warning''': Once out of service, antennas should be explicitely placed in one of the operational subarrays using the SUBARRAY1 and SUBARRAY2 commands.

Gelu: /* Service Mode */

2026-01-19T21:39:02Z

Service Mode

← Older revision		Revision as of 21:39, 19 January 2026
Line 199:		Line 199:
	=== Service Mode ===		=== Service Mode ===

	; SERVICE ~~[add\|del\|in\|out]~~ [antennalist]		; SERVICE-IN [antennalist]
	: Updates the list of antennas placed into service mode.		: Updates the list of antennas placed into service mode by adding the [antennalist] to the existing list.
	~~: Default~~ list ~~is <code>ant1-15</code>~~.
	: The service list is stored in <code>acc.ini</code>.		: The service list is stored in <code>acc.ini</code>.

	~~Aliases:~~		After updating the service list, the new antennas added to the list are removed from subarrays and driven to the service position.
	* add ≡ in
	* del ≡ out

	~~After updating~~ the ~~service~~ list, antennas ~~are removed~~ from ~~subarrays and driven to~~ the service ~~position~~.		'''Warning''': Once in service position, antennas should be placed in '''local mode'''.


			; SERVICE-OUT [antennalist]
			: Updates the list of antennas placed into service mode by deleting the [antennalist] from the existing list.
			: The service list is stored in <code>acc.ini<

	'''Warning''': Once in service ~~position~~, antennas should be placed in ~~'''local mode'''~~.		'''Warning''': Once out of service, antennas should be explicitely placed in one of the operational subarrays using the SUBARRAY1 and SUBARRAY2 commands.

	----		----

Gelu at 23:34, 7 January 2026

2026-01-07T23:34:03Z

← Older revision		Revision as of 23:34, 7 January 2026
Line 1:		Line 1:
	= EOVSA Schedule Commands =		= EOVSA Schedule Commands =

	This page documents the Schedule Commands used by the ~~{{Expanded Owens Valley Solar Array}} (~~EOVSA) Monitor & Control system to operate antennas, front-end electronics, digital control modules, frequency synthesizers, and safety monitors.		This page documents the Schedule Commands used by the EOVSA Monitor & Control system to operate antennas, front-end electronics, digital control modules, frequency synthesizers, and safety monitors.

	----		----

Gelu at 23:27, 7 January 2026

2026-01-07T23:27:54Z

Show changes

Nkuroda at 13:21, 3 November 2016

2016-11-03T13:21:29Z

Show changes

Nkuroda at 19:47, 21 September 2016

2016-09-21T19:47:02Z

← Older revision		Revision as of 19:47, 21 September 2016
Line 92:		Line 92:
	\|1		\|1
	\|0		\|0
	\|3		\|2
	\|3		\|2
	\|-		\|-
	\|2		\|2
	\|0		\|0
	\|6		\|4
	\|6		\|4
	\|-		\|-
	\|3		\|3
	\|0		\|0
	\|9		\|6
	\|9		\|6
	\|-		\|-
	\|4		\|4
	\|0		\|0
	\|12		\|8
	\|12		\|8
	\|-		\|-
	\|5		\|5
	\|0		\|0
	\|15		\|10
	\|15		\|10
	\|-		\|-
	\|6		\|6
	\|0		\|0
	\|18		\|12
	\|18		\|12
	\|-		\|-
	\|7		\|7
	\|9		\|2
	\|12		\|12
	\|21		\|14
	\|-		\|-
	\|8		\|8
	\|9		\|2
	\|15		\|14
	\|24		\|16
	\|-		\|-
	\|9		\|9
	\|9		\|4
			\|14
	\|18		\|18
	~~\|27~~
	\|-		\|-
	\|10		\|10
	\|9		\|4
	\|21		\|16
	\|30		\|20
	\|-		\|-
	\|11		\|11
	\|9		\|4
	\|24		\|18
	\|33		\|22
	\|-		\|-
	\|12		\|12
	\|9		\|4
	\|27		\|20
	\|36		\|24
	\|-		\|-
	\|13		\|13
	\|18		\|6
	\|21		\|20
	\|39		\|26
	\|-		\|-
	\|14		\|14
	\|18		\|8
	\|24		\|20
	\|42		\|28
	\|-		\|-
	\|15		\|15

Nkuroda at 19:41, 21 September 2016

2016-09-21T19:41:19Z

← Older revision		Revision as of 19:41, 21 September 2016
Line 1:		Line 1:
	NOTE: All Schedule commands accept as optional arguments a list of antennas to which the command should selectively sent. Accepted syntaxes are:		NOTE: All Schedule commands accept as optional arguments a list of antennas to which the command should selectively sent. Accepted syntaxes are:

	Command ant1 ant2 ant3		Command ant1 ant2 ant3

	Command ant1-3		Command ant1-3

	Command subarray1		Command subarray1

	Command subarray2		Command subarray2
	If no antenna list is indicated, the command is sent to all antennas currently in subarray1
			If no antenna list is indicated, the command is sent to all antennas currently in subarray1.

	== Commands handled directly by ACC ==		== Commands handled directly by ACC ==
Line 36:		Line 41:
	<span style="color: red">Warning:</span> The command is executed only if the DCM modules are in auto mode (see the DCMAUTO-ON and DCMAUTO-OFF command below).		<span style="color: red">Warning:</span> The command is executed only if the DCM modules are in auto mode (see the DCMAUTO-ON and DCMAUTO-OFF command below).

	NOTE		NOTE: The DCMREGIME settings are changed on the edge of the next second after a TCP/IP message is received by ACC at the TCP.dpp.port (default port: 6344-set in ACC.ini file ). The message is expected to be a fixed length binary string having the following format

	The DCMREGIME settings are changed on the edge of the next second after a TCP/IP message is received by ACC at the TCP.dpp.port (default port: 6344-set in ACC.ini file ). The message is expected to be a fixed length binary string having the following format

	<pre>REGIME + blank space + 50 32bit integers (I32)</pre>		<pre>REGIME + blank space + 50 32bit integers (I32)</pre>
Line 50:		Line 53:
	The actual DCM attenuations for a given tuning slot are calculated based on the following formula		The actual DCM attenuations for a given tuning slot are calculated based on the following formula

	~~<pre>~~atten[pol,tuning_index]=base_atten[pol,tuning_index]+regime*2db~~</pre>~~		'''''atten[pol,tuning_index]=base_atten[pol,tuning_index]+regime*2db'''''

	'''DPPOFFSET-OFF'''		'''DPPOFFSET-OFF'''
Line 239:		Line 242:

	NOTE: Unlike the general coinvention, not providing a list of antennas commands all cRIOs to restarts their execution.		NOTE: Unlike the general coinvention, not providing a list of antennas commands all cRIOs to restarts their execution.
	'''
	TRACKTABLE filename [antennalist]'''		'''TRACKTABLE filename [antennalist]'''

	Uploads to all antennas in the list the tracking table located at “c:\parm\filename”		Uploads to all antennas in the list the tracking table located at “c:\parm\filename”
Line 247:		Line 250:

	Uploads to all cRIOs corresponding to antennas in the list the trajectory file table located at “c:\parm\filename”		Uploads to all cRIOs corresponding to antennas in the list the trajectory file table located at “c:\parm\filename”
	'''
	UNLISTEDCOMMAND [antennalist]'''		'''UNLISTEDCOMMAND [antennalist]'''

	Any command not listed above is sent for local execution to all cRIOs corresponding to antennas in the list.		Any command not listed above is sent for local execution to all cRIOs corresponding to antennas in the list.
Line 314:		Line 317:
	Starts/Ends the execution of the trajectory script		Starts/Ends the execution of the trajectory script

	NOTE: At startup, the WINDSCRAM loop is activated or not according with the latest active written in the initialization file.		NOTE: At startup, the WINDSCRAM loop is activated or not according with the latest '''''active''''' written in the initialization file.

	'''BSCRAM-ON'''		'''BSCRAM-ON'''
Line 339:		Line 342:

	Sets the BRIGHTSCRAM Monitor waiting time before clearing the BRIGHSCRAM ACTIVE state.		Sets the BRIGHTSCRAM Monitor waiting time before clearing the BRIGHSCRAM ACTIVE state.

	~~Note: This setting is saved in the crio.ini file and remains persistent until changed~~

	~~'''BSCRAM-OFFSET'''~~

	~~Sets the BRIGHTSCRAM operation mode to stow the antenna when in active state.~~

	Note: This setting is saved in the crio.ini file and remains persistent until changed		Note: This setting is saved in the crio.ini file and remains persistent until changed
Line 352:		Line 349:
	Sets the BRIGHTSCRAM operation mode to apply offsets		Sets the BRIGHTSCRAM operation mode to apply offsets

	Note: This setting is saved in the crio.ini file and remains persistent until changed		Note: This setting is saved in the crio.ini file and remains persistent until changed.

	'''BSCRAM-AZELOFF azoff eloff'''		'''BSCRAM-AZELOFF azoff eloff'''

Nkuroda at 19:12, 21 September 2016

2016-09-21T19:12:07Z

← Older revision		Revision as of 19:12, 21 September 2016
Line 251:		Line 251:

	Any command not listed above is sent for local execution to all cRIOs corresponding to antennas in the list.		Any command not listed above is sent for local execution to all cRIOs corresponding to antennas in the list.

			== <span style="color: red">Commands handled directly by cRIOs</span> ==

			<span style="color: red">NOTE: These commands are selectively sent by ACC to all antennas in the optional argument antenalist, or, if not present, to all antennas in subarray1</span>

			'''AGC active [low [high [samples]]]'''

			Activates (1) or deactivates (0) the front end automatic gain control loop, which adjust the FEMATTN level when both of the HPOL and VPOL voltages, averaged over the given number of consecutive '''''samples''''' , cross the '''''low''''' and '''''high''''' voltage limits. Missing parameter values are uploaded from the [FEM AGC] section of the local “c:\ni-rt\startup\crio.ini” file. All parameters provided when an AGC command is issued are saved in the same file for further use.

			NOTE: At startup, the AGC loop is activated or not according with the latest '''''active''''' value written in the initialization file.

			'''AZELOFF azoff eloff'''

			Sets the Azimuth and Elevation offsets indicated in the argument list

			'''RADECOFF raoff decoff'''

			Sets the RA and DEC offsets indicated in the argument list

			'''FLUSH'''

			Flush the existing tracktable from the associated antenna controller

			'''ND-ON and ND-OFF'''

			Set on/off the local noise diode.

			'''POSITION azimuth elevation'''

			Requests a given azel position

			'''RESTART'''

			Reboots the cRIO

			'''DRIVE-RESET'''

			Resets Antenna controller

			'''STOP'''

			Stops the antenna

			'''STOW'''

			Stows the antenna

			'''TRACK'''

			Sets antenna in track mode

			'''TEC-LOG'''

			Dumps all TEC register values to the local log file “c:\tec.txt” for debugging purposes

			'''TEC-INIT'''

			Initializes the TEC controller with hard-wired register values read from a working controller.

			'''TRAJ-ON and TRAJ-OFF'''

			Starts/Ends the execution of the trajectory script

			NOTE: At startup, the WINDSCRAM loop is activated or not according with the latest active written in the initialization file.

			'''BSCRAM-ON'''

			Activate the BRIGHTSCRAM Monitor

			'''BSCRAM-OFF'''

			Deactivate the BRIGHTSCRAM Monitor

			'''BSCRAM-CLEAR'''

			Takes the antenna out of the BRIGHTSCRAM Active State independently of the brightness sensor state.

			If the BRIGHTSCRAM Monitor’s operation mode is set to STOW, clearing the BRIGHSCRAM ACTIVE state does not have any effect on the mechanical state of the antenna. If the BRIGHTSCRAM Monitor’s operation mode is set to OFFSET, clearing the BRIGHSCRAM ACTIVE state results in removing the AZEL offsets.

			Note: If the BRIGHTSCRAM Monitor is active, the antenna may get back in the Active State depending on the state of the brightness sensor.

			'''BSCRAM-SET'''

			Force the antenna into the BRIGHTSCRAM Active State independently of the brightness sensor state.

			'''BSCRAM-WAIT seconds'''

			Sets the BRIGHTSCRAM Monitor waiting time before clearing the BRIGHSCRAM ACTIVE state.

			Note: This setting is saved in the crio.ini file and remains persistent until changed

			'''BSCRAM-OFFSET'''

			Sets the BRIGHTSCRAM operation mode to stow the antenna when in active state.

			Note: This setting is saved in the crio.ini file and remains persistent until changed

			'''BSCRAM-OFFSET'''

			Sets the BRIGHTSCRAM operation mode to apply offsets

			Note: This setting is saved in the crio.ini file and remains persistent until changed

			'''BSCRAM-AZELOFF azoff eloff'''

			Sets the Azimuth and Elevation Offsets (degrees) for the BRIGHTSCRAM offset operation mode.

			Note: This setting is saved in the crio.ini file and remains persistent until changed. Default values re AZOFF=0 and ELOFF=10

			<span style="color: red">Warning:</span> No action is taken if less than 2 arguments are provided

			'''WSCRAM-ON'''

			Activate the WINDSCRAM Monitor

			'''WSCRAM-OFF'''

			Deactivate the WINDSCRAM Monitor

			'''WSCRAM-LIMIT value'''

			Sets the wind speed threshold.

			Note: This setting is saved in the crio.ini file and remains persistent until changed.

			'''WSCRAM-WAIT seconds'''

			Sets the WINDSCRAM Monitor waiting time between checking the wind speed.

			Note: This setting is saved in the crio.ini file and remains persistent until changed.

			'''UpdateElevationDiagnostics 1'''

			Requests an update of the elevation trip register.

			'''UpdateAzimuthDiagnostics 1'''

			Requests an update of the azimuth trip register.