28
Problem: Relay does not come on at appropriate time.
Solution:
Check that there are no conflicting events in the configuration. Click
the sort Events button as documented on page 10. It is important to know that
events at the top of the list have lowest priority. The reason for this is the Taralist
controller scans through all events in the list from the top to the bottom before it
refreshes the relays, so events at the bottom of the list can override events at the
top of the list.
An Inductive device can also cause communication malfunctions in the CPU,
review our Documentation on Inductive Devices to correct this problem.
Problem: Clock Speed running slow or fast.
Solution:
The Taralist controller may be affected by temperature. In excessively
cold environments the clock may run slow, in excessively hot conditions the clock
may run fast. This can be corrected using the Time Compensation feature
documented on page 11. The Taralist controllers clock may naturally drift event at
room temperature by as much as 1 second per day. This can be corrected using
the Time Compensation feature.
Problem: Controller is Running HOT.
Solution:
It is normal for some components run very hot on the Taralist series
relay controllers. This is not a concern as we have tested the design carefully and
are operating our components well within the specified limits of the components
we are using. It is NOT normal for the CPU to run hot at any time. The CPU
should remain cool. If the CPU is running hot and/or both Busy/Ready LEDS
are on at the same time, the CPU has been damaged.
Problem: Unable to Communicate with Controller
Solution: Use the ZUSB Communication Module to validate communications; do
NOT use any other communications module if this error occurs. The ZUSB is
the safest communication method of all communication technologies, and must be
used if you experience configuration problems. Make sure you are using the
correct COM port. Our software has been tested under Windows XP, Vista, and
Windows 7. Windows XP Users MUST use .NET Framework 3.5 or Later with
all the latest service packs installed. If the problem persists, makes sure the serial
port is NOT in use by another application. Lastly, we can only recommend trying
a different computer if problems persist.
