APU-102 AEI Site Operation - Revision history

AShanks at 20:23, 22 December 2025

2025-12-22T20:23:06Z

← Older revision		Revision as of 20:23, 22 December 2025
Line 1:		Line 1:
	<div~~><p>[[APU-102_Manual\|APU-102 Manual]]</p~~></div>		<div></div>

	= Train Processing Overview =		= Train Processing Overview =

GMalcom: Adding links

2024-09-27T19:42:50Z

Adding links

GMalcom: /* Axle Acquisition Subsystem */

2024-09-27T19:17:50Z

Axle Acquisition Subsystem

← Older revision		Revision as of 19:17, 27 September 2024
Line 42:		Line 42:
	= AEI Subsystems =		= AEI Subsystems =
	== Axle Acquisition Subsystem ==		== Axle Acquisition Subsystem ==
	<p>In the axle acquisition subsystem the APU-102 receives inputs from two wheel detector segments that provide signals for identifying cars, locomotives, and determining train direction and speed. The axle acquisition side of the AEI system establishes initial train presence and begins the acquisition cycle.</p><p>A wheel detector has two elements, or segments, at a fixed distance, required for calculating axle direction and speed: an “A” side wheel detector segment and a “B” side wheel detector segment.</p><p>Refer to the axle acquisition block diagram in ''~~2.10~~ Train Processing Block Diagrams'' for a system overview. For detailed information on how the axle acquisition subsystem interfaces with the APU-102 system, refer to ''[[#APU-102_Data Processing\|APU-102 Data Processing]]''.</p>		<p>In the axle acquisition subsystem the APU-102 receives inputs from two wheel detector segments that provide signals for identifying cars, locomotives, and determining train direction and speed. The axle acquisition side of the AEI system establishes initial train presence and begins the acquisition cycle.</p><p>A wheel detector has two elements, or segments, at a fixed distance, required for calculating axle direction and speed: an “A” side wheel detector segment and a “B” side wheel detector segment.</p><p>Refer to the axle acquisition block diagram in ''[[#Train_Processing_Block_Diagrams\|Train Processing Block Diagrams]]'' for a system overview. For detailed information on how the axle acquisition subsystem interfaces with the APU-102 system, refer to ''[[#APU-102_Data Processing\|APU-102 Data Processing]]''.</p>

	== RFID Subsystem ==		== RFID Subsystem ==

GMalcom: /* RFID Subsystem */

2024-09-27T19:06:03Z

RFID Subsystem

← Older revision		Revision as of 19:06, 27 September 2024
Line 45:		Line 45:

	== RFID Subsystem ==		== RFID Subsystem ==
	<p>The RFID subsystem is responsible for getting the information from the electronic tags mounted on the train to the APU-102. It consists of the AI1200 Reader Module, the AR2200 RF Unit and the antennas and tags. The antennas mounted on the sides of the tracks are turned on as each train passes. Each car tag then sends its data to the antenna, and the antenna passes the data to the APU-102.</p><p>Refer to the tag acquisition block diagram in ''~~2.10~~ Train Processing Block Diagrams'' for an overview of this system. For detailed information on how the RFID subsystem interfaces with the APU-102 system, refer to ''~~2.7~~ APU-102 Data Processing.''</p>		<p>The RFID subsystem is responsible for getting the information from the electronic tags mounted on the train to the APU-102. It consists of the AI1200 Reader Module, the AR2200 RF Unit and the antennas and tags. The antennas mounted on the sides of the tracks are turned on as each train passes. Each car tag then sends its data to the antenna, and the antenna passes the data to the APU-102.</p>
			<p>Refer to the tag acquisition block diagram in ''[[#Train Processing_Block_Diagrams\|Train Processing Block Diagrams]]'' for an overview of this system. For detailed information on how the RFID subsystem interfaces with the APU-102 system, refer to ''[[#APU-102 Data_Processing\|APU-102 Data Processing]].''</p>

	= Communications =		= Communications =

GMalcom at 18:49, 27 September 2024

2024-09-27T18:49:04Z

Show changes

GMalcom at 18:44, 27 September 2024

2024-09-27T18:44:58Z

Show changes

GMalcom: /* Operation Example */

2024-09-27T17:54:12Z

Operation Example

← Older revision		Revision as of 17:54, 27 September 2024
Line 332:		Line 332:

	= Operation Example =		= Operation Example =
	<p>As the system is started, the APU-102 software initializes the hardware and begins monitoring for a new train arrival. When a train enters into the presence detector field or the first axle event of the first piece of equipment passes the site, the APU-102 begins a record session. As the train passes, each axle event and tag are logged along with a timestamp for each. After the train has left the site, the APU-102 ends the record session. The closing of the record session begins a tag time-out period to allow the system to receive any tags from the reader that have not yet been transferred. An axle identification routine is activated to process (correlate) the raw axle event information (As and Bs) into axles. A car identification routine is activated to process (correlate) the raw axle information into cars. This output is saved as part of the basic raw data necessary to provide the processing functions for the host system information and the user interface. The correlated car information will be matched with the tag data by comparing the timestamps between the axle information and the tag information. “Fix-up” processing is run to refine the accuracy of the consist. The consist is now ready to be transmitted to the host system by the APU.</p><p>The APU-102 connects to the host system. After connection, the APU-102 and host negotiate the logon/password sequence if necessary. After a valid logon is processed, the APU-102 transfers the consist to the host. The APU-102 marks as sent, sends additional unsent consists or logs off and disconnects.</p><p>For detailed information on APU-102 system software menus, refer to'' ~~4.0~~ APU-102 User Interface.''</p>		<p>As the system is started, the APU-102 software initializes the hardware and begins monitoring for a new train arrival. When a train enters into the presence detector field or the first axle event of the first piece of equipment passes the site, the APU-102 begins a record session. As the train passes, each axle event and tag are logged along with a timestamp for each. After the train has left the site, the APU-102 ends the record session. The closing of the record session begins a tag time-out period to allow the system to receive any tags from the reader that have not yet been transferred. An axle identification routine is activated to process (correlate) the raw axle event information (As and Bs) into axles. A car identification routine is activated to process (correlate) the raw axle information into cars. This output is saved as part of the basic raw data necessary to provide the processing functions for the host system information and the user interface. The correlated car information will be matched with the tag data by comparing the timestamps between the axle information and the tag information. “Fix-up” processing is run to refine the accuracy of the consist. The consist is now ready to be transmitted to the host system by the APU.</p>
			<p>The APU-102 connects to the host system. After connection, the APU-102 and host negotiate the logon/password sequence if necessary. After a valid logon is processed, the APU-102 transfers the consist to the host. The APU-102 marks as sent, sends additional unsent consists or logs off and disconnects.</p>
			<p>For detailed information on APU-102 system software menus, refer to'' [[APU-102 User_Interface\|APU-102 User Interface]].''</p>

	= Train Processing Block Diagrams =		= Train Processing Block Diagrams =

GMalcom: /* Axle Acquisition Subsystem */

2024-09-27T17:30:50Z

Axle Acquisition Subsystem

← Older revision		Revision as of 17:30, 27 September 2024
Line 123:		Line 123:
	== Hardware Subsystems ==		== Hardware Subsystems ==
	=== Axle Acquisition Subsystem ===		=== Axle Acquisition Subsystem ===
	<p>Detecting Presence, Speed, and Direction</p><p>Wheel detectors provide the system with three key pieces of information: presence, direction, and speed. Each wheel detector configuration the APU-102 uses consists of a minimum of two segments. Each segment of the wheel detector produces a signal as the wheel passes. Train presence, or one axle count, is determined when a wheel passes over both segments.</p><p>Because there are at least two segments placed a fixed distance apart, the APU-102 is able to determine speed. As previously mentioned, each segment's signal is independently timestamped by the master system clock as it occurs. (See ''2.7.1.2 Timebase Synchronization and Time Correlation''.) By measuring the time it takes the wheel to travel the fixed distance from one segment to the other, the software is able to calculate speed. Speed detection is paramount to the APU-102. If the speed calculated by the system is incorrect, the cross-checking mechanisms in the software are thrown off. The software processing would also be affected because it locates car and locomotive patterns in the wheel data. The processing would lose the ability to accurately measure dimensions, which would cause the results to falter.</p><p>The two-wheel detector segments also determine direction. The left segment is identified as the A segment, and the right segment is identified as the B segment. If the wheel passes from A to B, the wheel detector reports a left to right movement. If the wheel passes from B to A, it must be moving right to left. System parameters for orientation (E/W, W/E, N/S, S/N) and direction (L/R, R/L) may be set to determine the direction of left to right and right to left. See ''Appendix A: System Parameters'' for information on setting parameters.</p><p>Some wheel detectors have three and four segments (A, B, C and A, B, C, D respectively). This feature contributes to accurate direction detection. (Refer to the sections ''Types of Wheel Detectors'' and ''Slow Speed and the “C” Pulse.'')</p><p>Parameters that affect this processing include:</p><p style="margin-left: 25px;"><span id="HTMLENTITY:1727479488846" style="font-family: <span class=" title=""" contenteditable="false" draggable="true" mwt-noneditable="" mwt-wikimagic="" mwt-placeholder="" mwt-htmlentity="" span="">courier new", courier;" class="mwt-preserveHtml" >Session#.SiteInformation.TrackOrientation~~</span>~~</p><p style="margin-left: 25px;"><span id="HTMLENTITY:1727448230617" style="font-family: <span class=" title=""" contenteditable="false" draggable="true" mwt-noneditable="" mwt-wikimagic="" mwt-placeholder="" mwt-htmlentity="" span="">courier new", courier;" class="mwt-preserveHtml" >Session#.SiteInformation.TrackDirection (change not recommended)~~</span></p>~~<p><br></p><p>These parameters need to be setup on all active sessions and could be different. The owner railroad (Session1), may call the site N-S, Session2 may call it E-W.</p><p><br></p>		<p>Detecting Presence, Speed, and Direction</p><p>Wheel detectors provide the system with three key pieces of information: presence, direction, and speed. Each wheel detector configuration the APU-102 uses consists of a minimum of two segments. Each segment of the wheel detector produces a signal as the wheel passes. Train presence, or one axle count, is determined when a wheel passes over both segments.</p><p>Because there are at least two segments placed a fixed distance apart, the APU-102 is able to determine speed. As previously mentioned, each segment's signal is independently timestamped by the master system clock as it occurs. (See ''2.7.1.2 Timebase Synchronization and Time Correlation''.) By measuring the time it takes the wheel to travel the fixed distance from one segment to the other, the software is able to calculate speed. Speed detection is paramount to the APU-102. If the speed calculated by the system is incorrect, the cross-checking mechanisms in the software are thrown off. The software processing would also be affected because it locates car and locomotive patterns in the wheel data. The processing would lose the ability to accurately measure dimensions, which would cause the results to falter.</p><p>The two-wheel detector segments also determine direction. The left segment is identified as the A segment, and the right segment is identified as the B segment. If the wheel passes from A to B, the wheel detector reports a left to right movement. If the wheel passes from B to A, it must be moving right to left. System parameters for orientation (E/W, W/E, N/S, S/N) and direction (L/R, R/L) may be set to determine the direction of left to right and right to left. See ''Appendix A: System Parameters'' for information on setting parameters.</p><p>Some wheel detectors have three and four segments (A, B, C and A, B, C, D respectively). This feature contributes to accurate direction detection. (Refer to the sections ''Types of Wheel Detectors'' and ''Slow Speed and the “C” Pulse.'')</p><p>Parameters that affect this processing include:</p>
			<p style="margin-left: 25px;">Session#.SiteInformation.TrackOrientation</p>
			<p style="margin-left: 25px;">Session#.SiteInformation.TrackDirection (change not recommended)<p><br></p>
			<p>These parameters need to be setup on all active sessions and could be different. The owner railroad (Session1), may call the site N-S, Session2 may call it E-W.</p><p><br></p>

	==== Types of Wheel Detectors ====		==== Types of Wheel Detectors ====

GMalcom: /* Detecting That the Train Has Gone */

2024-09-27T17:25:20Z

Detecting That the Train Has Gone

← Older revision		Revision as of 17:25, 27 September 2024
Line 100:		Line 100:
	<p style="margin-left: 25px;">SysDiags.PresenceLoop.PresTimeOutAboveSpeed</span></p>		<p style="margin-left: 25px;">SysDiags.PresenceLoop.PresTimeOutAboveSpeed</span></p>
	<p style="margin-left: 25px;">SysDiags.PresenceLoop.PresenceTimeoutSeconds</span></p><p><br></p>		<p style="margin-left: 25px;">SysDiags.PresenceLoop.PresenceTimeoutSeconds</span></p><p><br></p>

	~~<br>~~

	=== Aborting Trains ===		=== Aborting Trains ===

GMalcom: /* Post Processed Files */

2024-09-27T17:25:10Z

Post Processed Files

← Older revision		Revision as of 17:25, 27 September 2024
Line 116:		Line 116:
	<p>These files are the result of each step of processing that occurs during post cycle processing. Each step of the processing is stored as another individual file to allow analysis of each stage.</p>		<p>These files are the result of each step of processing that occurs during post cycle processing. Each step of the processing is stored as another individual file to allow analysis of each stage.</p>

	~~<br>~~
	=== Disk Manager ===		=== Disk Manager ===
	<p>Because of the storage requirements for the data and limited capacity, the AEI application contains a Disk Manager to maintain free space by removing train data files that are no longer needed. They are removed on a first-in, first out basis. To reduce the amount of disk space used, the disk manager in the AEI application software can be instructed to remove either raw or post processed data files from the disk as well.</p>		<p>Because of the storage requirements for the data and limited capacity, the AEI application contains a Disk Manager to maintain free space by removing train data files that are no longer needed. They are removed on a first-in, first out basis. To reduce the amount of disk space used, the disk manager in the AEI application software can be instructed to remove either raw or post processed data files from the disk as well.</p>

← Older revision		Revision as of 19:42, 27 September 2024
Line 73:		Line 73:
	== Collecting Data ==		== Collecting Data ==
	=== System Parameters That Affect Data Processing ===		=== System Parameters That Affect Data Processing ===
	<p>References to APU application software parameters occur frequently in this chapter. They are listed as “parameters that affect this processing.” For a complete list of APU-102 parameter options and defaults, refer to ''Appendix A: System Parameters''. To view current system parameters from the Display Parameters screen (DP command on either system menu) or edit system parameters from the Edit Parameters screen (EP command on the Supervisory Menu)</p>		<p>References to APU application software parameters occur frequently in this chapter. They are listed as “parameters that affect this processing.” For a complete list of APU-102 parameter options and defaults, refer to ''[[Appendix_A_System_Parameters\|Appendix A: System Parameters]]''. To view current system parameters from the Display Parameters screen (DP command on either system menu) or edit system parameters from the Edit Parameters screen (EP command on the Supervisory Menu)</p>

	=== Timebase Synchronization and Time Correlation ===		=== Timebase Synchronization and Time Correlation ===
Line 117:		Line 117:
	== Hardware Subsystems ==		== Hardware Subsystems ==
	=== Axle Acquisition Subsystem ===		=== Axle Acquisition Subsystem ===
	<p>Detecting Presence, Speed, and Direction</p><p>Wheel detectors provide the system with three key pieces of information: presence, direction, and speed. Each wheel detector configuration the APU-102 uses consists of a minimum of two segments. Each segment of the wheel detector produces a signal as the wheel passes. Train presence, or one axle count, is determined when a wheel passes over both segments.</p><p>Because there are at least two segments placed a fixed distance apart, the APU-102 is able to determine speed. As previously mentioned, each segment's signal is independently timestamped by the master system clock as it occurs. (See ''2.7.1.2 Timebase Synchronization and Time Correlation''.) By measuring the time it takes the wheel to travel the fixed distance from one segment to the other, the software is able to calculate speed. Speed detection is paramount to the APU-102. If the speed calculated by the system is incorrect, the cross-checking mechanisms in the software are thrown off. The software processing would also be affected because it locates car and locomotive patterns in the wheel data. The processing would lose the ability to accurately measure dimensions, which would cause the results to falter.</p><p>The two-wheel detector segments also determine direction. The left segment is identified as the A segment, and the right segment is identified as the B segment. If the wheel passes from A to B, the wheel detector reports a left to right movement. If the wheel passes from B to A, it must be moving right to left. System parameters for orientation (E/W, W/E, N/S, S/N) and direction (L/R, R/L) may be set to determine the direction of left to right and right to left. See ''Appendix A: System Parameters'' for information on setting parameters.</p><p>Some wheel detectors have three and four segments (A, B, C and A, B, C, D respectively). This feature contributes to accurate direction detection. (Refer to the sections ''Types of Wheel Detectors'' and ''Slow Speed and the “C” Pulse.'')</p><p>Parameters that affect this processing include:</p><p style="margin-left: 25px;">Session#.SiteInformation.TrackOrientation</p><p style="margin-left: 25px;">Session#.SiteInformation.TrackDirection (change not recommended)</p><p><br></p><p>These parameters need to be setup on all active sessions and could be different. The owner railroad (Session1), may call the site N-S, Session2 may call it E-W.</p><p><br></p>		<p>Detecting Presence, Speed, and Direction</p><p>Wheel detectors provide the system with three key pieces of information: presence, direction, and speed. Each wheel detector configuration the APU-102 uses consists of a minimum of two segments. Each segment of the wheel detector produces a signal as the wheel passes. Train presence, or one axle count, is determined when a wheel passes over both segments.</p><p>Because there are at least two segments placed a fixed distance apart, the APU-102 is able to determine speed. As previously mentioned, each segment's signal is independently timestamped by the master system clock as it occurs. (See ''2.7.1.2 Timebase Synchronization and Time Correlation''.) By measuring the time it takes the wheel to travel the fixed distance from one segment to the other, the software is able to calculate speed. Speed detection is paramount to the APU-102. If the speed calculated by the system is incorrect, the cross-checking mechanisms in the software are thrown off. The software processing would also be affected because it locates car and locomotive patterns in the wheel data. The processing would lose the ability to accurately measure dimensions, which would cause the results to falter.</p><p>The two-wheel detector segments also determine direction. The left segment is identified as the A segment, and the right segment is identified as the B segment. If the wheel passes from A to B, the wheel detector reports a left to right movement. If the wheel passes from B to A, it must be moving right to left. System parameters for orientation (E/W, W/E, N/S, S/N) and direction (L/R, R/L) may be set to determine the direction of left to right and right to left. See ''Appendix A: System Parameters'' for information on setting parameters.</p><p>Some wheel detectors have three and four segments (A, B, C and A, B, C, D respectively). This feature contributes to accurate direction detection. (Refer to the sections ''[[#Types_of_Wheel_Detectors\|Types of Wheel Detectors]]'' and ''[[#Slow_Speed_and_the_"C"_Pulse\|Slow Speed and the “C” Pulse]].'')</p><p>Parameters that affect this processing include:</p><p style="margin-left: 25px;">Session#.SiteInformation.TrackOrientation</p><p style="margin-left: 25px;">Session#.SiteInformation.TrackDirection (change not recommended)</p><p><br></p><p>These parameters need to be setup on all active sessions and could be different. The owner railroad (Session1), may call the site N-S, Session2 may call it E-W.</p><p><br></p>

	==== Types of Wheel Detectors ====		==== Types of Wheel Detectors ====
Line 185:		Line 185:

	=== Presence Detector Timeouts ===		=== Presence Detector Timeouts ===
	<p>Site-specific presence detector timeouts may be set in the APU-102 application software.</p><p>Parameters that affect this processing include:</p><p style="margin-left: 25px;">SysDiags.PresenceLoop.MinAxles</p><p style="margin-left: 25px;">SysDiags.PresenceLoop.LowSpeedThresh</p><p style="margin-left: 25px;">SysDiags.PresenceLoop.HighSpeedThresh</p><p style="margin-left: 25px;">SysDiags.PresenceLoop.PresTimeOutAboveSpeed</p><p style="margin-left: 25px;">SysDiags.PresenceLoop.PresenceTimeoutSeconds</p><p style="margin-left: 25px;">SysDiags.PresenceLoop.SecondsBetweenTrains</p><p style="margin-left: 25px;">SysDiags.PresenceLoop.ExcessPresencePeriodWarningTimeout</p><p>For instructions on using the override and timeout functions, refer to the '''Edit Parameters''' (EP) function in ''~~4.0~~ APU-102 User Interface'' and Acquisition Parameters in ''Appendix A: System Parameters''.</p>		<p>Site-specific presence detector timeouts may be set in the APU-102 application software.</p><p>Parameters that affect this processing include:</p><p style="margin-left: 25px;">SysDiags.PresenceLoop.MinAxles</p><p style="margin-left: 25px;">SysDiags.PresenceLoop.LowSpeedThresh</p><p style="margin-left: 25px;">SysDiags.PresenceLoop.HighSpeedThresh</p><p style="margin-left: 25px;">SysDiags.PresenceLoop.PresTimeOutAboveSpeed</p><p style="margin-left: 25px;">SysDiags.PresenceLoop.PresenceTimeoutSeconds</p><p style="margin-left: 25px;">SysDiags.PresenceLoop.SecondsBetweenTrains</p><p style="margin-left: 25px;">SysDiags.PresenceLoop.ExcessPresencePeriodWarningTimeout</p><p>For instructions on using the override and timeout functions, refer to the '''Edit Parameters''' (EP) function in ''[[APU-102_User_Interface\|APU-102 User Interface]]'' and Acquisition Parameters in ''[[Appendix_A_System_Parameters\|Appendix A: System Parameters]]''.</p>

	== Multi-Track Processing ==		== Multi-Track Processing ==
Line 194:		Line 194:

	=== Inter-Track Communication (ITC) ===		=== Inter-Track Communication (ITC) ===
	<p>ITC was designed for double-track installations. 2 APU-102s share acquisition data via a serial connection. They also provide presence awareness to the adjacent APU-102 when their own track is occupied via hard-wired control signals between the APU-102s. Activity on any connected APU-102 starts the acquisition clock on all. ITC logic determines which tags belong to our train (and which ones don’t). If the APU-102 can’t determine if the tag belongs its train, it does not use it in makeup of the consist. (If in doubt, throw it out). Refer to the ''AEI System Site Installation Guide'' for additional information on equipment installation.</p><p>Parameters that affect this processing include:</p><p style="margin-left: 25px;">Acquisition.ITC1.ChannelFileName</p><p style="margin-left: 25px;">Acquisition.ITC1.InterferenceUnitLocation</p><p style="margin-left: 25px;">Acquisition.ITC1.ITCSpeedThresh</p>		<p>ITC was designed for double-track installations. 2 APU-102s share acquisition data via a serial connection. They also provide presence awareness to the adjacent APU-102 when their own track is occupied via hard-wired control signals between the APU-102s. Activity on any connected APU-102 starts the acquisition clock on all. ITC logic determines which tags belong to our train (and which ones don’t). If the APU-102 can’t determine if the tag belongs its train, it does not use it in makeup of the consist. (If in doubt, throw it out). Refer to the ''[[AEI_System_Site_Installation_Guide\|AEI System Site Installation Guide]]'' for additional information on equipment installation.</p><p>Parameters that affect this processing include:</p><p style="margin-left: 25px;">Acquisition.ITC1.ChannelFileName</p><p style="margin-left: 25px;">Acquisition.ITC1.InterferenceUnitLocation</p><p style="margin-left: 25px;">Acquisition.ITC1.ITCSpeedThresh</p>

	=== Dynamic Adjustment of Confidence Logic ===		=== Dynamic Adjustment of Confidence Logic ===
Line 254:		Line 254:

	=== Header and Tag Formats ===		=== Header and Tag Formats ===
	<p>The List Clean Consist ('''L''') function in the APU-102 application software allows you to display tag information in various formats. Entering the '''L''' command with an optional extension determines the format that displays. The optional List Clean Consist extensions are the Compass Format ('''LC'''), TCS Format ('''TL'''), T94 Format ('''LT94'''), and Full Consist Format ('''LF''').</p><p>Refer to ~~4.0~~ APU-102 User Interface for command operating instructions and Appendix B: Host Reporting Formats.</p>		<p>The List Clean Consist ('''L''') function in the APU-102 application software allows you to display tag information in various formats. Entering the '''L''' command with an optional extension determines the format that displays. The optional List Clean Consist extensions are the Compass Format ('''LC'''), TCS Format ('''TL'''), T94 Format ('''LT94'''), and Full Consist Format ('''LF''').</p><p>Refer to [[APU-102_User_Interface\|APU-102 User Interface]] for command operating instructions and [[Appendix_B_Host_Reporting_Formats\|Appendix B: Host Reporting Formats]].</p>

	== Connecting to Other Wayside Equipment ==		== Connecting to Other Wayside Equipment ==
Line 305:		Line 305:
	\|<p>Detects objects that are being dragged by the train.</p>		\|<p>Detects objects that are being dragged by the train.</p>

	\|}<p><br></p><p>Connecting to additional equipment allows information from each unit to add value to the information contained on other units at the site. Wayside equipment typically connects to the APU-102 via an RS-232 port. Verify the communications protocol (baud rate, data bits, stop bits, parity, flow control, etc.) for the wayside equipment and set the port to match in the APU-102 application software. Newer defect detectors connect via a '''''LAN''''' (Local Area Network) Refer to the ''AEI System Site Installation Guide'' for additional information on equipment installation.</p><p>Parameters that may affect this processing include:</p><p style="margin-left: 25px;">Ports.AUX#PORT.Name</p><p style="margin-left: 25px;">Ports.AUX#PORT.Driver</p><p style="margin-left: 25px;">Ports.AUX#PORT.Port</p><p style="margin-left: 25px;">Ports.AUX#PORT.BaudRate</p><p style="margin-left: 25px;">Ports.AUX#PORT.WordLen</p><p style="margin-left: 25px;">Ports.AUX#PORT.StopBits</p><p style="margin-left: 25px;">Ports.AUX#PORT.Parity</p><p style="margin-left: 25px;">Ports.AUX#PORT.FlowControl</p><p style="margin-left: 25px;">Ports.ETHERNET.IPAddress</p><p style="margin-left: 25px;">Ports.ETHERNET.SubnetMask</p><p style="margin-left: 25px;">Ports.ETHERNET.Gateway</p>		\|}<p><br></p><p>Connecting to additional equipment allows information from each unit to add value to the information contained on other units at the site. Wayside equipment typically connects to the APU-102 via an RS-232 port. Verify the communications protocol (baud rate, data bits, stop bits, parity, flow control, etc.) for the wayside equipment and set the port to match in the APU-102 application software. Newer defect detectors connect via a '''''LAN''''' (Local Area Network) Refer to the ''[[AEI_System_Site_Installation_Guide\|AEI System Site Installation Guide]]'' for additional information on equipment installation.</p><p>Parameters that may affect this processing include:</p><p style="margin-left: 25px;">Ports.AUX#PORT.Name</p><p style="margin-left: 25px;">Ports.AUX#PORT.Driver</p><p style="margin-left: 25px;">Ports.AUX#PORT.Port</p><p style="margin-left: 25px;">Ports.AUX#PORT.BaudRate</p><p style="margin-left: 25px;">Ports.AUX#PORT.WordLen</p><p style="margin-left: 25px;">Ports.AUX#PORT.StopBits</p><p style="margin-left: 25px;">Ports.AUX#PORT.Parity</p><p style="margin-left: 25px;">Ports.AUX#PORT.FlowControl</p><p style="margin-left: 25px;">Ports.ETHERNET.IPAddress</p><p style="margin-left: 25px;">Ports.ETHERNET.SubnetMask</p><p style="margin-left: 25px;">Ports.ETHERNET.Gateway</p>

	<br>		<br>