<?xml version="1.0" standalone="yes"?>
<?xml-stylesheet type="text/xsl" href="..\..\XSLTemplates\CommandsStyleSheet.xsl"?>
<Command>
<Name>scan bstatus</Name>
<Description>
<DescriptionText><text>
This command is used to display all 'bypassed' I/O bits and groups in a system,
It is intended for use by field service engineers as a convenient means of
displaying bypasses without having to examine the bypass status flags of an
entire bit list or group list.
</text></DescriptionText>
</Description>
<AppliesTo>
<UnnumberedList>
<ListItem><TextApplies>Gravure</TextApplies></ListItem>
<ListItem><TextApplies>Japanese_Newspaper_OEM_Engine</TextApplies></ListItem>
<ListItem><TextApplies>Lotem_400_Fiber_Head_Machine</TextApplies></ListItem>
<ListItem><TextApplies>Lotem_800_Fiber_Head_Machine</TextApplies></ListItem>
<ListItem><TextApplies>Lotem_Quantum</TextApplies></ListItem>
<ListItem><TextApplies>Magnus_400</TextApplies></ListItem>
<ListItem><TextApplies>Magnus_800</TextApplies></ListItem>
<ListItem><TextApplies>Magnus_VLF</TextApplies></ListItem>
<ListItem><TextApplies>Slave_MCE_Firmware</TextApplies></ListItem>
<ListItem><TextApplies>Thermoflex</TextApplies></ListItem>
<ListItem><TextApplies>Think_Motion_Controller</TextApplies></ListItem>
<ListItem><TextApplies>Trendsetter_400/800</TextApplies></ListItem>
<ListItem><TextApplies>Trendsetter_NEWS</TextApplies></ListItem>
<ListItem><TextApplies>Trendsetter_Series_4</TextApplies></ListItem>
</UnnumberedList>
</AppliesTo>
<Notes>
<DescriptionText><text>
The IOS subsystem maintains a bypass flag for every discrete I/O bit and group
in a given system.  User commands are supplied to read, set and clear any
given bypass flag as well clear all bypasses at once.  Each time a bypass flag
is set or cleared the bypass status is automatically saved in nonvolatile
memory.  Bypass statuses are therefore always maintained through power cycles.
</text></DescriptionText>
<DescriptionText><text>
The I/O Scanner has no concept of how these flags are used.  It simply manages
bypass flag states for other subsystems.  If no subsystem is examining the
bypass state of a given bit or group the state is meaningless.
</text></DescriptionText>
<DescriptionText><text>
How can you know if the bypass state is being observed by the firmware?  The
answer is you cant know until a failure occurs because an I/O point (typically
position sensor) is not at its expected value.  The firmware will announce the
name of the bit or group in question.  After diagnosing the problem, field
service engineers or remote customer service personnel have the  option of
bypassing the bit to allow the machine to continue (with diminished throughput
and compromised internal machine safety) until the problem can be fully
addressed.
</text></DescriptionText>
<DescriptionText><text>
Bypassing I/O is not to taken lightly and should be used only to restore
operation to a machine when all the risks and benefits have been carefully
considered.  In order to deal with
the historical problems of "bypassing and forgetting" the firmware is
designed to repeatedly display large windows at the main workstation to remind
user that their machine is compromised and should be serviced soon
possible.
</text></DescriptionText>
<DescriptionText><text>
It is estimated that bypassing will temporarily rectify about 500r more of
potential machine sensor failures.  Bypassing will not necessarily restore
non-functioning machines to a working state for the following reasons:
</text></DescriptionText>
<DescriptionText><UnnumberedList>
<ListItem><Text>
Some I/O points are critical to machine operation and can not be bypassed.
These points have been predefined in the firmware as non-bypassable. Attempts
to bypass these I/O point will result in error messages.
</Text></ListItem>
</UnnumberedList></DescriptionText>
<DescriptionText><UnnumberedList>
<ListItem><Text>
As stated above the firmware may allow bypass status to be set but certain
firmware subsystem don't offer the ability to ignore the input from an I/O point
if the associated bypass flag is set.
</Text></ListItem>
</UnnumberedList></DescriptionText>
</Notes>
<Availability>
<DescriptionText><text>
This command is available.
</text></DescriptionText>
</Availability>
<Access>
Field
</Access>
<LastModified>
18-Jun-2001
</LastModified>
<SeeAlso>
<UnnumberedList>
<li><Link><LinkAddress>../commands/scan_bclear.xml</LinkAddress><LinkTitle>Command: scan bclear</LinkTitle></Link></li>
<li><Link><LinkAddress>../commands/scan_-ioname-.xml</LinkAddress><LinkTitle>Command: scan &lt;ioname&gt;</LinkTitle></Link></li>
</UnnumberedList>
</SeeAlso>
<OtherLinks>
<Link><LinkAddress>..\..\ShowAllErrors.htm</LinkAddress><LinkTitle>Firmware 1 Error Index</LinkTitle></Link>
<Link><LinkAddress>..\..\ShowAllCommands.htm</LinkAddress><LinkTitle>Firmware 1 Command Index</LinkTitle></Link>
<Link><LinkAddress>..\..\ShowAllParameters.htm</LinkAddress><LinkTitle>Firmware 1 Parameter Index</LinkTitle></Link>
</OtherLinks>
<Updated>
Updated: Thu Jul 17 07:25:27 2008 PST
</Updated>
<Links>
</Links>
</Command>
