Performance issues for the ASE driver

Support | Order Placement | ProScada Home Page | Download Demos

Application notes for ASE Driver

General Recomendations
======================

Cable
-----
See the manual \FIX32\NLS\ASEDOC.HLP

DCS Settings
------------
the following must be setup in the DCS, I am reading this in a document called "Advant Excom Manual"

1/ a RS232_n database element
2/ a EXCOM_n datbase element

while the serial settings you chose should work I recomend the following

19200.
7 data bits.
1 stop bit.
no parity.
flow control none

Driver Settings
----------------
To talk to the PLC/DCS with the DSCA114 I recomend adress Network=0 & Node=0. Only use another address if you wish to talk to another AC410 connected to this one via ethernet MOD300.

Application Note regarding AX & DX Blocks
=========================================
I contacted ABB and asked some questions

Q What is an AX block & how does it differ for an AI block
A the AI reads the S100 IO & AX reads S400 IO (Newer IO)

Q So is there a newer version of excom protocol, or should a AI poll read an AX block.
A The protocol has not changed you 'should...' be able to read an AX block using the the excom protocol filetype "AI".

The ASE driver does read AIC blocks in the DCS, so it should be able to read AX blocks as well (poll by file type AI with block ID). If this does not work I consider this to be a "Bug" in the DCS software.

As a work around I recomend the following:

Create DAT blocks of type Real/float and add some programming to the DCS to copy the AX blocks to the DAT blocks then create "DATR" blocks in the ASE driver config.

Create DAT blocks of type 32 bit and add some programming to the DCS to copy the DX blocks to the DAT blocks (32 DX blocks into one DAT) then create "DATD" blocks in the ASE driver config. and address them <device>:DATD:<bit 0-31>. Note that this technique is recomended anyway because one DI block takes 6 bytes and one DATD block takes 9 bytes (contains 32 DI's).

See Tips on Optimizing Most Drivers