Multitech MT1932ZDXK User Manual download pdf (Page 13)

03/03 13 - 16 DS 2.501A

Example:- Set address 5.

When using a user defined preset (or customized preset) first make

sure that preset 0 is selected via the bit switch. The unit should then be

left with the address selected on the bit switches (bit switch 7 ON). This

ensure that should data corruption occur the controller will not attempt

to load any default values. As the application is user defined the

controller cannot know what would be suitable defaults. The preset

setting can be checked using Satchnet via the system module.

COLD STARTING CONTROLLERS

In order to cold start an IAC controller (i.e. clear out the configuration

data) the following procedure should be followed.

1. Disconnect all outputs from the plant.

2. Set bit switch 1 ON, all others OFF.

Toggle bit switch 8. This causes the controller to load preset

application 1.

3. Set all bit switches to OFF. Toggle bit switch 8. This causes the

controller to load preset 0 (no application).

4. If you are using preset 0 you should now set the controller address.

If you are using a hardware preset application set the application

number on bit switches 1 to 6 and ensure that bit switch 7 is set to

OFF.

5. Once the application number is set it must be entered into the IAC

by toggling bit switch 8.

6. If the IAC is not to be connected to a computer then it is not

necessary to set an address for it.

7. Set the controller address (if required) on bit switches 1 to 6 and

set bit switch 7 to ON.

8. Once the address has been set it must be entered in to the IAC by

toggling bit switch 8. The controller address is now loaded and the

IAC will communicate at 1200 bps.

9. Re-connect outputs to plant.

Note:

Whenever a firmware upgrade is performed the unit must be cold started.

CONTROLLER LED

Normal Operation

On both the IAC400 and IAC200 controllers the on board LED is under

software control and should, under normal operation, flash at a regular

interval. The rate of flash is directly proportional to the loading imposed

by the application the controller is running, i.e. the more modules you

use the slower the LED flashes.

Unit Initialization

Whenever the controller is powered up or reset the LED will initially

flash very quickly before adopting the standard flash rate. (Only applies

to VAV207, VAS207 and DDC 206 and later versions).

Data Corruption

If a controller appears to be continually performing unit initialization, it

is likely that data corruption has occurred. Toggle bit switch 8 to reload

defaults. Download the configuration from Satchnet if it is a software

preset.

SECTION 6 –SATCHNET COMMUNICATION

TROUBLE SHOOTING

This section gives guidelines for interpreting the communications

failure percentage displayed on Satchnet. It is not intended that this will

provide an answer to every problem but providing that the Satchnet

wiring recommendations are followed (Section 1) it should be possible

to diagnose most communication problems.

Before any analysis of possible problems can be performed, it is

necessary to get all controllers on an "even playing field" from the

Satchnet point of view. Ideally a duplicate copy of Satchnet should be

installed in a separate directory. Controllers should then be created but

no parameters extracted from them. Ideally all controllers should be

placed on the same Satchnet screen but if this is not possible group

them according to location. If possible all controllers should be running

the same application or no application. By following this procedure you

ensure that the polling of the controllers is evenly spread and thereby

make the communication failures statistic comparable between

controllers.

To view the failure percentage of a controller you must click on the

controller with the RIGHT button. The following window is displayed.

The operation of the failure statistic is influenced by many things such

as:

Protocol used,

Satchnet polling used,

Relative controller transceiver transmitter strengths,

Location of failing controller.

The precise nature of the failure percentage and how one failing

controller affects another is therefore site specific. However, some

general trends have been noted.

A failure percentage of 0-10% does not generally have a detrimental

effect on system performance. Some messages may fail but are

automatically re-tried by Satchnet. Where MIUs and IAC

touch-screens are used, there may be a slight increase in failure

percentage of 2-3% due to the message buffering these products

introduce.

Where two controllers have been given the same address the failure

percentage of that address will typically range from 40-90%. Other

working controllers will be affected and their failure percentages will

typically range from 10-30%.

Where a controller or group of controllers have a 100% failure rate,

suspect either addressing, wiring or hardware faults.

In general when tracing communications problems always start with

the unit with the highest failure rate. Isolation of this unit may well

improve the failure rates of the other controllers. The LAN may be split

up to help locate the fault.

GROUP ADDRESSING

The IAC200/400/600 may belong to 10 groups. The IAC200/400/ 600

will accept a group message if the message group address matches

any one of programmed group addresses.

Do not mix different controller types on the same group address. This

will result in corruption of the slave controller.

Set switch 7 to ON

Set address 5, set

switches 1 and 3 ON.

Set switch 8 to ON

Set switch 8 to OFF

This procedure will enter

the address into the

controller memory.

1 2 ... 8 9 10 11 12 13 14 15 16

Comments to this Manuals

No comments

Multitech MT1932ZDXK User Manual Page 13

Comments to this Manuals

Related products and manuals for Networking Multitech MT1932ZDXK