Appendix A - System Parameters - Revision history

AShanks at 20:19, 22 December 2025

2025-12-22T20:19:38Z

← Older revision		Revision as of 20:19, 22 December 2025
Line 1:		Line 1:
	~~[[APU-102 Manual]]~~<div><p>The following system parameter groups are listed as they appear on the Edit Parameters (EP) menu. See [[APU-102 User Interface]], for information on using the EP command on the Supervisory Menu.</p>		<div><p>The following system parameter groups are listed as they appear on the Edit Parameters (EP) menu. See [[APU-102 User Interface]], for information on using the EP command on the Supervisory Menu.</p>
	<p>'''These parameters are for reference only and are not intended to be a comprehensive listing as the APU software is constantly evolving. Through periodic reviews and updates, we endeavor to keep it as current as possible. For parameters not found in this text, refer to the on-board help within the EP application (<CRTL>-U) or to the revision text file “VERSION.TXT” on the APU. Parameters from this text but not on your APU are not available to the current version of software in the APU. '''</p>		<p>'''These parameters are for reference only and are not intended to be a comprehensive listing as the APU software is constantly evolving. Through periodic reviews and updates, we endeavor to keep it as current as possible. For parameters not found in this text, refer to the on-board help within the EP application (<CRTL>-U) or to the revision text file “VERSION.TXT” on the APU. Parameters from this text but not on your APU are not available to the current version of software in the APU. '''</p>

GMalcom: /* FTP Host INI file example */

2024-10-22T14:35:48Z

FTP Host INI file example

← Older revision		Revision as of 14:35, 22 October 2024
Line 4,336:		Line 4,336:
	== FTP Host INI file example ==		== FTP Host INI file example ==
	<p>FTP reporting requires a matching <basefile_name.INI> file for the AccessFilename, <basefile_name.ACC> specified for AEI or maintenance reporting. For example, SAMPLE.ACC for FTP requires SAMPLE.INI. Contact Comet Electronics for assistance in creating ACC and INI files.</p>		<p>FTP reporting requires a matching <basefile_name.INI> file for the AccessFilename, <basefile_name.ACC> specified for AEI or maintenance reporting. For example, SAMPLE.ACC for FTP requires SAMPLE.INI. Contact Comet Electronics for assistance in creating ACC and INI files.</p>
	~~<p><br></p>~~
	~~<div>~~<p> [FTP]</p>		{\| class="wikitable" style="border-collapse: collapse; width: 60%; background-color: rgb(236, 240, 241); margin-left: auto; margin-right: auto;" border="2px" cellpadding="4px"
			\|-
			\| style="width: 100%;" \| <p> [FTP]</p>
	<p>Host                                         = 192.168.1.215 ;(or url, e.g., ftp.myftp.com)</p>		<p>Host                                         = 192.168.1.215 ;(or url, e.g., ftp.myftp.com)</p>
	<p>UserName                                = railnet</p>		<p>UserName                                = railnet</p>
Line 4,352:		Line 4,354:
	<p>SendCommand3=</p>		<p>SendCommand3=</p>
	<p>SendCommand4=</p>		<p>SendCommand4=</p>
	~~<p><br></p></div>~~		\|}
	<p>Example file: SAMPLE.INI to use with SAMPLE.ACC</p>
			<p style="text-align: center;" >Example file: SAMPLE.INI to use with SAMPLE.ACC</p>

	<br>		<br>

GMalcom: /* VIO.CFG (Virtual I/O Configuration file) example */

2024-10-22T14:32:24Z

VIO.CFG (Virtual I/O Configuration file) example

← Older revision		Revision as of 14:32, 22 October 2024
Line 4,260:		Line 4,260:
	== VIO.CFG (Virtual I/O Configuration file) example ==		== VIO.CFG (Virtual I/O Configuration file) example ==
	<p>There are numerous opto-isolated inputs and outputs available on the APU-102. Currently, the outputs are hard coded in the application. To make use of the inputs, the APU-102 Application software needs to know the connection and usage. This is done with the VIO.CFG (Virtual I/O Configuration file). There are 2 types of inputs available. ALARMS which act on specific TTL input level transitions (logic zero or one) and COUNTS which require multiple transitions to cause action. The VIO.CFG can contain both types. Either requires numeration and identification. The lines leading with semi-colons are comments and are ignored by the APU.</p>		<p>There are numerous opto-isolated inputs and outputs available on the APU-102. Currently, the outputs are hard coded in the application. To make use of the inputs, the APU-102 Application software needs to know the connection and usage. This is done with the VIO.CFG (Virtual I/O Configuration file). There are 2 types of inputs available. ALARMS which act on specific TTL input level transitions (logic zero or one) and COUNTS which require multiple transitions to cause action. The VIO.CFG can contain both types. Either requires numeration and identification. The lines leading with semi-colons are comments and are ignored by the APU.</p>
	<div><p>ALARMS#1</p>		<div>
			{\| class="wikitable" style="border-collapse: collapse; width: 60%; background-color: rgb(236, 240, 241); margin-left: auto; margin-right: auto;" border="2px" cellpadding="4px"
			\|-
			\| style="width: 100%;" \| <p>ALARMS#1</p>
	<p>;^     ^</p>		<p>;^     ^</p>
	<p>;\|     \|</p>		<p>;\|     \|</p>
Line 4,326:		Line 4,329:
	<p>; AUX BLK 2     3     0      40    Temp probe</p>		<p>; AUX BLK 2     3     0      40    Temp probe</p>
	<p>; AUX BLK 2     5     0      20    Tag valid reader 2 ant 1</p>		<p>; AUX BLK 2     5     0      20    Tag valid reader 2 ant 1</p>
	<p>; AUX BLK 2     7     0      10    Tag valid reader 2 ant 0</p></div>		<p>; AUX BLK 2     7     0      10    Tag valid reader 2 ant 0</p>
	<p>Example file: VIO.CFG</p>		\|}
			</div>
			<p style="text-align: center;" >Example file: VIO.CFG</p>

	== FTP Host INI file example ==		== FTP Host INI file example ==

GMalcom: /* Ports.Ethernet.DNSTableFilename Parameters */

2024-10-22T13:42:09Z

Ports.Ethernet.DNSTableFilename Parameters

← Older revision		Revision as of 13:42, 22 October 2024
Line 4,247:		Line 4,247:
	<p>If url’s are used for outbound connections, the APU needs to know how to resolve the url to numeric IP’s so it can connect. If the APU is using DHCP, the DHCP server provides the DNS routing information. If a fixed IP is used, the DNS table gives the APU a list of DNS servers to use. The following is an example DNS Table File for Ports.Ethernet.DNSTableFilename parameter:</p>		<p>If url’s are used for outbound connections, the APU needs to know how to resolve the url to numeric IP’s so it can connect. If the APU is using DHCP, the DHCP server provides the DNS routing information. If a fixed IP is used, the DNS table gives the APU a list of DNS servers to use. The following is an example DNS Table File for Ports.Ethernet.DNSTableFilename parameter:</p>
	<div><p><br></p>		<div><p><br></p>
	~~<p>~~8.8.8.8<~~/p>~~
	<p>8.8.4.4<~~/p>~~		{\| class="wikitable" style="border-collapse: collapse; width: 60%; background-color: rgb(236, 240, 241); margin-left: auto; margin-right: auto; height: 92px;" border="2px" cellpadding="4px"
	<p>192.168.10.25<~~/p>~~		\|- style="height: 92px;"
	<p>192.168.2.2</p>		\| style="width: 100%; height: 92px;" \| 8.8.8.8<br>8.8.4.4<br>192.168.10.25<br>192.168.2.2<br>
	<p><br></p><~~/div~~>		\|}
	<p>~~Example file: DNS.DAT~~</p>
			<p style="text-align: center;" ><span style="font-size: 14.4px;">Example file: DNS.DAT</span><br></p></div>
	<p><br></p>		<p><br></p>

	<br>		<br>

	== VIO.CFG (Virtual I/O Configuration file) example ==		== VIO.CFG (Virtual I/O Configuration file) example ==
	<p>There are numerous opto-isolated inputs and outputs available on the APU-102. Currently, the outputs are hard coded in the application. To make use of the inputs, the APU-102 Application software needs to know the connection and usage. This is done with the VIO.CFG (Virtual I/O Configuration file). There are 2 types of inputs available. ALARMS which act on specific TTL input level transitions (logic zero or one) and COUNTS which require multiple transitions to cause action. The VIO.CFG can contain both types. Either requires numeration and identification. The lines leading with semi-colons are comments and are ignored by the APU.</p>		<p>There are numerous opto-isolated inputs and outputs available on the APU-102. Currently, the outputs are hard coded in the application. To make use of the inputs, the APU-102 Application software needs to know the connection and usage. This is done with the VIO.CFG (Virtual I/O Configuration file). There are 2 types of inputs available. ALARMS which act on specific TTL input level transitions (logic zero or one) and COUNTS which require multiple transitions to cause action. The VIO.CFG can contain both types. Either requires numeration and identification. The lines leading with semi-colons are comments and are ignored by the APU.</p>

GMalcom at 20:31, 21 October 2024

2024-10-21T20:31:16Z

← Older revision		Revision as of 20:31, 21 October 2024
Line 1:		Line 1:
	[[APU-102 Manual]]<div><p>The following system parameter groups are listed as they appear on the Edit Parameters (EP) menu. See [[User Interface]], for information on using the EP command on the Supervisory Menu.</p>		[[APU-102 Manual]]<div><p>The following system parameter groups are listed as they appear on the Edit Parameters (EP) menu. See [[APU-102 User Interface]], for information on using the EP command on the Supervisory Menu.</p>
	<p>'''These parameters are for reference only and are not intended to be a comprehensive listing as the APU software is constantly evolving. Through periodic reviews and updates, we endeavor to keep it as current as possible. For parameters not found in this text, refer to the on-board help within the EP application (<CRTL>-U) or to the revision text file “VERSION.TXT” on the APU. Parameters from this text but not on your APU are not available to the current version of software in the APU. '''</p>		<p>'''These parameters are for reference only and are not intended to be a comprehensive listing as the APU software is constantly evolving. Through periodic reviews and updates, we endeavor to keep it as current as possible. For parameters not found in this text, refer to the on-board help within the EP application (<CRTL>-U) or to the revision text file “VERSION.TXT” on the APU. Parameters from this text but not on your APU are not available to the current version of software in the APU. '''</p>

GMalcom at 20:30, 21 October 2024

2024-10-21T20:30:57Z

← Older revision		Revision as of 20:30, 21 October 2024
Line 1:		Line 1:
	[[APU-102 Manual]]<div><p>The following system parameter groups are listed as they appear on the Edit Parameters (EP) menu. See ~~Section 4.0,~~ User Interface, for information on using the EP command on the Supervisory Menu.</p>		[[APU-102 Manual]]<div><p>The following system parameter groups are listed as they appear on the Edit Parameters (EP) menu. See [[User Interface]], for information on using the EP command on the Supervisory Menu.</p>
	<p>'''These parameters are for reference only and are not intended to be a comprehensive listing as the APU software is constantly evolving. Through periodic reviews and updates, we endeavor to keep it as current as possible. For parameters not found in this text, refer to the on-board help within the EP application (<CRTL>-U) or to the revision text file “VERSION.TXT” on the APU. Parameters from this text but not on your APU are not available to the current version of software in the APU. '''</p>		<p>'''These parameters are for reference only and are not intended to be a comprehensive listing as the APU software is constantly evolving. Through periodic reviews and updates, we endeavor to keep it as current as possible. For parameters not found in this text, refer to the on-board help within the EP application (<CRTL>-U) or to the revision text file “VERSION.TXT” on the APU. Parameters from this text but not on your APU are not available to the current version of software in the APU. '''</p>

GMalcom: /* Filename Parameter Options */

2024-10-21T19:56:18Z

Filename Parameter Options

Show changes

GMalcom: /* SupportThreads */

2024-10-21T19:55:48Z

SupportThreads

← Older revision		Revision as of 19:55, 21 October 2024
Line 3,972:		Line 3,972:
	<p><br></p>		<p><br></p>
	<div>		<div>
			{\| style="border-collapse: collapse;" border="1px" cellpadding="2px"
	{\| style="border-collapse: collapse;" border="1px" cellpadding="2px"
	\|-		\|-
	\| <p>SupportThreads.DetectorSupportThread</p>		\| <p>SupportThreads.DetectorSupportThread</p>
	\|-		\|-
	\| <p>Parameter</p>		\| <p>Parameter</p>
	\| <p>Description</p>		\| <p>Description</p>
	\| <p>Valid Value(s)</p>		\| <p>Valid Value(s)</p>
	\|-		\|-
	\| <p>.PortFile</p>		\| <p>.PortFile</p>
	\| <p>Optional.</p>		\| <p>Optional.</p>
	<p>Port filename. Indicates the port on which external defect detectors communicate with the APU-102 to harvest Consist data.</p>		<p>Port filename. Indicates the port on which external defect detectors communicate with the APU-102 to harvest Consist data.</p>
	\| <p>Up to 29 alphanumeric.</p>		\| <p>Up to 29 alphanumeric.</p>
	<p>Remote (modem) communications port</p>		<p>Remote (modem) communications port</p>
	<p>$LOCPORT.DAT</p>		<p>$LOCPORT.DAT</p>
Line 4,008:		Line 4,007:
	<p><br></p>		<p><br></p>
	<div>		<div>
			{\| style="border-collapse: collapse;" border="1px" cellpadding="2px"
	{\| style="border-collapse: collapse;" border="1px" cellpadding="2px"
	\|-		\|-
	\| <p>SupportThreads.GEMicroHBDSupportThread</p>		\| <p>SupportThreads.GEMicroHBDSupportThread</p>
	\|-		\|-
	\| <p>Parameter</p>		\| <p>Parameter</p>
	\| <p>Description</p>		\| <p>Description</p>
	\| <p>Valid Value(s)</p>		\| <p>Valid Value(s)</p>
	\|-		\|-
	\| <p>.PortFile</p>		\| <p>.PortFile</p>
	\| <p>Optional.</p>		\| <p>Optional.</p>
	<p>Port filename. Indicates the port on which the APU-102 communicates with the GE Micro Hot Box Detector</p>		<p>Port filename. Indicates the port on which the APU-102 communicates with the GE Micro Hot Box Detector</p>
	\| <p>Up to 29 alphanumeric.</p>		\| <p>Up to 29 alphanumeric.</p>
	<p>Remote (modem) communications port</p>		<p>Remote (modem) communications port</p>
	<p>$LOCPORT.DAT</p>		<p>$LOCPORT.DAT</p>
Line 4,036:		Line 4,034:
	<p>Default: NONE</p>		<p>Default: NONE</p>
	\|-		\|-
	\| <p>.LoggerSwitch</p>		\| <p>.LoggerSwitch</p>
	\| <p>Optional.</p>		\| <p>Optional.</p>
	<p><br></p>		<p><br></p>
	\| <p>0 -  Off. No data is logged. (Default)</p>		\| <p>0 -  Off. No data is logged. (Default)</p>
	<p>1 -  Status & Local activity messages are logged.</p>		<p>1 -  Status & Local activity messages are logged.</p>
	<p>2 -  Status & Local activity messages are logged.</p>		<p>2 -  Status & Local activity messages are logged.</p>
Line 4,051:		Line 4,049:
	<p><br></p>		<p><br></p>
	<div>		<div>
	{\|
			{\| style="border-collapse: collapse;" border="1px" cellpadding="2px"
	\|-		\|-
	\|<p>SupportThreads.NTPService</p>		\| <p>SupportThreads.NTPService</p>
	\|-		\|-
	\|<p>Parameter</p>		\| <p>Parameter</p>
	\|<p>Description</p>		\| <p>Description</p>
	\|<p>Valid Value(s)</p>		\| <p>Valid Value(s)</p>
	\|-		\|-
	\|<p>.Enable</p>		\| <p>.Enable</p>
	\|<p>Optional.</p>		\| <p>Optional.</p>
	<p>Enables NTP Service (Network Time Protocol). This feature allows the APU-102 to synchronize its clock with a network Time Server. It can use private time server or an Internet time server if it is reachable. </p>		<p>Enables NTP Service (Network Time Protocol). This feature allows the APU-102 to synchronize its clock with a network Time Server. It can use private time server or an Internet time server if it is reachable. </p>
	\|<p>1 numeric.</p>		\| <p>1 numeric.</p>
	<p>1 = Enabled</p>		<p>1 = Enabled</p>
	<p>0 = Disabled</p>		<p>0 = Disabled</p>
	\|-		\|-
	\|<p>.IPAddressOrHostName</p>		\| <p>.IPAddressOrHostName</p>
	<p><br></p>		<p><br></p>
	<p>or</p>		<p>or</p>
	<p><br></p>		<p><br></p>
	<p>.PrimaryIPAddressOrURL</p>		<p>.PrimaryIPAddressOrURL</p>
	\|<p>Optional.</p>		\| <p>Optional.</p>
	<p>Required if NTP service is enabled. (Parameter name version dependent)</p>		<p>Required if NTP service is enabled. (Parameter name version dependent)</p>
	<p>IP address or URL</p>		<p>IP address or URL</p>
	\|<p>Up to 39 alphanumeric.</p>		\| <p>Up to 39 alphanumeric.</p>
	<p>IP address or URL of NTP Server</p>		<p>IP address or URL of NTP Server</p>
	<p><br></p>		<p><br></p>
	<p>Default: BLANK</p>		<p>Default: BLANK</p>
	\|-		\|-
	\|<p>.SecondaryIPAddressOrURL</p>		\| <p>.SecondaryIPAddressOrURL</p>
	\|<p>Optional.</p>		\| <p>Optional.</p>
	<p>Secondary NTP service (version dependent).</p>		<p>Secondary NTP service (version dependent).</p>
	<p>IP address or URL</p>		<p>IP address or URL</p>
	\|<p>Up to 39 alphanumeric.</p>		\| <p>Up to 39 alphanumeric.</p>
	<p>IP address or URL of NTP Server</p>		<p>IP address or URL of NTP Server</p>
	<p><br></p>		<p><br></p>
	<p>Default: BLANK</p>		<p>Default: BLANK</p>
	\|-		\|-
	\|<p>.IntervalInMinutes</p>		\| <p>.IntervalInMinutes</p>
	\|<p>Optional.</p>		\| <p>Optional.</p>
	<p>This is the interval in minutes to run the NTP time synchronization. APU-102’s time drift is minimal and many consists hosts provide time synchronization so frequent NTP updates are not necessary. Some NTP services will block access if excessive requests are made.</p>		<p>This is the interval in minutes to run the NTP time synchronization. APU-102’s time drift is minimal and many consists hosts provide time synchronization so frequent NTP updates are not necessary. Some NTP services will block access if excessive requests are made.</p>
	\|<p>Up to 5 Numeric</p>		\| <p>Up to 5 Numeric</p>
	<p>Interval in minutes</p>		<p>Interval in minutes</p>
	<p>Recommended: 1440 = 24hrs</p>		<p>Recommended: 1440 = 24hrs</p>
Line 4,099:		Line 4,098:
	</div>		</div>
	<p><br></p>		<p><br></p>

	= MoreSessions (5.2+) =		= MoreSessions (5.2+) =
	<p><br></p>		<p><br></p>

GMalcom: /* SupportThreads.GEMicroHBDSupportThread */

2024-10-21T19:55:33Z

SupportThreads.GEMicroHBDSupportThread

← Older revision		Revision as of 19:55, 21 October 2024
Line 4,008:		Line 4,008:
	<p><br></p>		<p><br></p>
	<div>		<div>
	{\|
			{\| style="border-collapse: collapse;" border="1px" cellpadding="2px"
	\|-		\|-
	\|<p>SupportThreads.GEMicroHBDSupportThread</p>		\| <p>SupportThreads.GEMicroHBDSupportThread</p>
	\|-		\|-
	\|<p>Parameter</p>		\| <p>Parameter</p>
	\|<p>Description</p>		\| <p>Description</p>
	\|<p>Valid Value(s)</p>		\| <p>Valid Value(s)</p>
	\|-		\|-
	\|<p>.PortFile</p>		\| <p>.PortFile</p>
	\|<p>Optional.</p>		\| <p>Optional.</p>
	<p>Port filename. Indicates the port on which the APU-102 communicates with the GE Micro Hot Box Detector</p>		<p>Port filename. Indicates the port on which the APU-102 communicates with the GE Micro Hot Box Detector</p>
	\|<p>Up to 29 alphanumeric.</p>		\| <p>Up to 29 alphanumeric.</p>
	<p>Remote (modem) communications port</p>		<p>Remote (modem) communications port</p>
	<p>$LOCPORT.DAT</p>		<p>$LOCPORT.DAT</p>
Line 4,035:		Line 4,036:
	<p>Default: NONE</p>		<p>Default: NONE</p>
	\|-		\|-
	\|<p>.LoggerSwitch</p>		\| <p>.LoggerSwitch</p>
	\|<p>Optional.</p>		\| <p>Optional.</p>
	<p><br></p>		<p><br></p>
	\|<p>0 -  Off. No data is logged. (Default)</p>		\| <p>0 -  Off. No data is logged. (Default)</p>
	<p>1 -  Status & Local activity messages are logged.</p>		<p>1 -  Status & Local activity messages are logged.</p>
	<p>2 -  Status & Local activity messages are logged.</p>		<p>2 -  Status & Local activity messages are logged.</p>
Line 4,046:		Line 4,047:
	</div>		</div>
	<p><br></p>		<p><br></p>

	== SupportThreads.NTPService ==		== SupportThreads.NTPService ==
	<p><br></p>		<p><br></p>

GMalcom: /* SupportThreads.DetectorSupportThread */

2024-10-21T19:55:21Z

SupportThreads.DetectorSupportThread

← Older revision		Revision as of 19:55, 21 October 2024
Line 3,972:		Line 3,972:
	<p><br></p>		<p><br></p>
	<div>		<div>
	{\|
			{\| style="border-collapse: collapse;" border="1px" cellpadding="2px"
	\|-		\|-
	\|<p>SupportThreads.DetectorSupportThread</p>		\| <p>SupportThreads.DetectorSupportThread</p>
	\|-		\|-
	\|<p>Parameter</p>		\| <p>Parameter</p>
	\|<p>Description</p>		\| <p>Description</p>
	\|<p>Valid Value(s)</p>		\| <p>Valid Value(s)</p>
	\|-		\|-
	\|<p>.PortFile</p>		\| <p>.PortFile</p>
	\|<p>Optional.</p>		\| <p>Optional.</p>
	<p>Port filename. Indicates the port on which external defect detectors communicate with the APU-102 to harvest Consist data.</p>		<p>Port filename. Indicates the port on which external defect detectors communicate with the APU-102 to harvest Consist data.</p>
	\|<p>Up to 29 alphanumeric.</p>		\| <p>Up to 29 alphanumeric.</p>
	<p>Remote (modem) communications port</p>		<p>Remote (modem) communications port</p>
	<p>$LOCPORT.DAT</p>		<p>$LOCPORT.DAT</p>
Line 4,003:		Line 4,004:
	</div>		</div>
	<p><br></p>		<p><br></p>

	== SupportThreads.GEMicroHBDSupportThread ==		== SupportThreads.GEMicroHBDSupportThread ==
	<p><br></p>		<p><br></p>