With each Softrol AutoPulse Automation System you will receive a wiring map of how each machine is connected to the network. With the provided ArcNet wiring map, go to the Hub and start disconnecting each ArcNet connection one at a time watching the “Recon” light while each line is being removed.

If the “Recon” light turns off after disconnecting a certain connection, look to see if the rest of the automation is operating properly. If the automation is operating properly, reconnect the troubled ArcNet connection to the Hub and verify that the problem still exists. If the “Recon” light starts flashing, disconnect the troubled ArcNet connection and proceed with the following:

On the provided map, look to see what machines are connected together in the ArcNet loop. For example: We have a ArcNet line to machines 10, 11, and 12. The line with the troubled connection will be labeled “To AutoPulse ID 10”.

First check all of the machine setups to make sure that they have not been altered. Make sure each machine ID is correct and please notice the machine that has the termination point of the ArcNet link.

The ArcNet is terminated with a 93-ohm terminator. If this terminator has been removed, intermediate communication will occur.

Starting with machine 10, disconnect the ArcNet connection. Go to the Hub and reconnect the ArcNet loop labeled “To Machine 10”.

Check the Recon light. If it starts flashing, disconnect the ArcNet connection from the Hub and proceed to machine 11 and disconnect the ArcNet connection then recheck the hub.

If the Recon light is still flashing, remove the 93-ohm terminator from machine 12 and place it in line at machine 11. Reconnect the ArcNet connection to the Mod Hub and check the Recon light.

If the flashing stops, reconnect the ArcNet to machine 10 and check the Recon light on the Mod Hub. If the Recon light remains silent, you have narrowed the problem down to either the ArcNet cable has been damaged between machines 11 or 12 or machine 12 is having communication problems.

It would also be advisable to check the all of the machine setups to insure that there are no duplicated ArcNet Ids. This is just an example of how to trouble shoot your communications.