Alliance Laundry Systems NK120 用户手册
505942
23
Troubleshooting
© Copyright, Alliance Laundry Systems LLC – DO NOT COPY or TRANSMIT
Network Board Blocks Card Reader
Communications to FEC -
Communications to FEC -
Some failure modes may
prevent the card reader (if connected) to communicate
with the FEC. If this is the case, the NWB itself may
or may not be able to communicate with the FEC.
with the FEC. If this is the case, the NWB itself may
or may not be able to communicate with the FEC.
To eliminate the possibility of a bad reader, it is helpful
to temporarily eliminate the NWB from the circuit.
Unplug the harness from the NWB to the card reader,
and also unplug the harness from the NWB to the FEC.
Next, connect the harness which is used to connect a
card reader directly to the FEC.
to temporarily eliminate the NWB from the circuit.
Unplug the harness from the NWB to the card reader,
and also unplug the harness from the NWB to the FEC.
Next, connect the harness which is used to connect a
card reader directly to the FEC.
NOTE: This harness is not included in machines
containing a NWB, the individual performing the
service to the machine will have to have this
harness.
containing a NWB, the individual performing the
service to the machine will have to have this
harness.
Once the card reader is linked directly to the FEC, wait
15 seconds, and insert any card into the reader. The
FEC display should change to reflect the card insertion.
If the FEC does not indicate that a card was inserted,
the NWB may not be the problem. In this case, see the
section on Card Readers.
15 seconds, and insert any card into the reader. The
FEC display should change to reflect the card insertion.
If the FEC does not indicate that a card was inserted,
the NWB may not be the problem. In this case, see the
section on Card Readers.
If the card reader does communicate the card insertion
to the FEC, remove the temporary harness and put the
original harnesses back in place, so that the NWB is
once again in the circuit.
to the FEC, remove the temporary harness and put the
original harnesses back in place, so that the NWB is
once again in the circuit.
Next, swap the harness from the NWB to the card
reader with a known good harness. If the reader is now
able to communicate a card insertion, the harness is at
fault, and must be changed. If not, put the original
harness back, and continue.
reader with a known good harness. If the reader is now
able to communicate a card insertion, the harness is at
fault, and must be changed. If not, put the original
harness back, and continue.
Check that there is 5 VDC across pins 1 & 2 of H1 on
the NWB. If this voltage is not there, communication
between the FEC and the card reader or NWB will not
occur.
the NWB. If this voltage is not there, communication
between the FEC and the card reader or NWB will not
occur.
If there is 5VDC across pins 1 & 2 of H1 and the card
reader cannot communicate with the FEC, swap the
harness between the FEC and NWB with an known
good harness. If this fixes the problem, the harness is
at fault.
reader cannot communicate with the FEC, swap the
harness between the FEC and NWB with an known
good harness. If this fixes the problem, the harness is
at fault.
If the harness is not at fault, the NWB should be
swapped with a known good board. If this fixes the
problem, the NWB needs to be replaced. If after
changing out the NWB and the harness with known-
good samples the card reader cannot communicate with
the FEC, the FEC must be at fault.
swapped with a known good board. If this fixes the
problem, the NWB needs to be replaced. If after
changing out the NWB and the harness with known-
good samples the card reader cannot communicate with
the FEC, the FEC must be at fault.
Network Board to PC
Communication Problems
Communication Problems
Communication between the NWB and the PC may be
interrupted via several cases:
interrupted via several cases:
• NWB not operating correctly (not executing
program)
• NWB cannot communicate with FEC (NWB cannot
get its correct node number)
• Problems on network external to the NWB under test
- Wires flipped at one or more points on the Network
- Short on the Network
- Noise on the Network (another node jabbering,
- Short on the Network
- Noise on the Network (another node jabbering,
reflections, etc.)
NWB Not Operating Correctly -
If the NWB is not
executing the code in the processor correctly, there is
no way it can communicate with the FEC. Use the
network board operating LED test and the network
board communicating LED test to verify operation.
no way it can communicate with the FEC. Use the
network board operating LED test and the network
board communicating LED test to verify operation.
NWB Cannot Get Node Number From PC -
If this is
the case, the PC should be able to communicate with
the NWB by attempting to communicate with node
250. Note that since 250 is the default node in the
NWB, if it cannot retrieve another node number from
the FEC, it will default to 250. When running this test,
remember that there may be other nodes on the
network, due to other failures, that may result in more
than one node 250 on the network. If this is the case,
the PC may not be able to get through to any node
numbered 250. Because of this, it is desirable, if
possible, to perform this test on a “1-node” network,
which contains only the NWB under test.
the NWB by attempting to communicate with node
250. Note that since 250 is the default node in the
NWB, if it cannot retrieve another node number from
the FEC, it will default to 250. When running this test,
remember that there may be other nodes on the
network, due to other failures, that may result in more
than one node 250 on the network. If this is the case,
the PC may not be able to get through to any node
numbered 250. Because of this, it is desirable, if
possible, to perform this test on a “1-node” network,
which contains only the NWB under test.
If the PC can communicate with the NWB as node 250,
then either the FEC has node number 250 programmed
into it (test via the Microwand), or the NWB is not
communicating with the FEC. Use the network board
communicating LED test to verify operation.
then either the FEC has node number 250 programmed
into it (test via the Microwand), or the NWB is not
communicating with the FEC. Use the network board
communicating LED test to verify operation.
Problems Related to Network -
If possible, it may be
beneficial to isolate the NWB in question from the rest
of the network, creating a “1-node” network. This
eliminates other network boards, mis-wiring on the
network, etc., as causes for a NWB not communicating
with the PC.
of the network, creating a “1-node” network. This
eliminates other network boards, mis-wiring on the
network, etc., as causes for a NWB not communicating
with the PC.
With the NWB alone connected to the PC, attempt to
communicate with the board. If no communication
occurs at any node number, the NWB or the harness
from the NWB to the connector at the rear of the
machine is bad. Try swapping the NW cable from the
rear connector to the NWB and test again. If
communication is successful, the harness needs to be
replaced.
communicate with the board. If no communication
occurs at any node number, the NWB or the harness
from the NWB to the connector at the rear of the
machine is bad. Try swapping the NW cable from the
rear connector to the NWB and test again. If
communication is successful, the harness needs to be
replaced.