Marker: Difference between revisions
WIP |
wip |
||
| Line 36: | Line 36: | ||
|- | |- | ||
|Test circuits | |Test circuits | ||
|Test parts of the | |Test parts of the switching network for availability, false crosses and grounds, and double connections | ||
|- | |- | ||
|Preference and selection chain circuits | |Preference and selection chain circuits | ||
|Analyze available options and chooses the best one according to a pre-set algorithm, and data regarding the previous selection that was made | |Analyze available options and chooses the best one according to a pre-set algorithm, and data regarding the previous selection that was made | ||
|- | |||
|State control circuits | |||
|Monitors and advances the overall state of the marker | |||
|- | |- | ||
|Error checking circuits | |Error checking circuits | ||
| Line 51: | Line 54: | ||
|} | |} | ||
Trouble Reporting | == Trouble Reporting == | ||
Concentrating control functions into just a few fast-acting but complex units meant that means had to be devised for reporting [[trouble]], and reproducing test calls to aid in localizing problems. Since it was nearly impossible to identify a problem with a marker just by looking at it, marker-based common control switches employed trouble indicators or [[Trouble Recorder|trouble recorders]] that displayed faults as they occurred. This aided maintenance staff in resolving issues. | |||
Second Trial | == Second Trial and Alternate Routing == | ||
Markers are intrinsically capable of retrying in the event of failures. | |||