HW Functionality

Functionality
applicom®
a product of Woodhead Software & Electronics
Functionality 1 08/02/2008
Copyright © 2006 Woodhead Software & Electronics. All rights reserved.


Table of contents
1. Description of the hardware solution...........................................4
2. Use constraints..............................................................................7
Compatibility of configurations ................................................................................7
Compatibility of applicom software versions / applicom interfaces.........................8
User rights agreement for the applicom® program.................................................9
3. Client mode - Server mode .........................................................11
4. Use of the software solution in client mode..............................12

Wait mode .............................................................................................................13
Deferred mode ......................................................................................................14
Cyclic mode...........................................................................................................16
5. Use of the software solution in server mode ............................20
6. Database: Internal data area .......................................................21

Organization of the bit area ...................................................................................22
Organization of the word area...............................................................................23
General organization of the word area..................................................................24
Example of using the database.............................................................................25
Events FIFO in Database ......................................................................................26
Management of cyclic functions by the “command flag-status word” pair ............27
DATABASE access locks......................................................................................28
Modem link management ......................................................................................30

1. Description of the hardware solution
The applicom® product is designed for applications on PC computers, such as MMI, supervisor,
process control system, MES, RDBMS, specific development, requiring communication with PLCs
and I/O peripherals connected to local area networks.
The applicom® product is available under the Microsoft environments Windows XP, Windows
2003 server and Windows Vista.
The function of the applicom® concept is to allow the users to develop their applications without
worrying about the difficulties related to field network protocols and the performance that depends
on the frequency and the amount of data exchanged.
Performance is guaranteed by the quality of exchange management on the applicom® coprocessor
interfaces each of which is equipped with the applicom® real time multi-task kernel.
List of interfaces offered as standard on the applicom® product:
Reference Type
For Serial Networks
PCI1000 PCI bus, 1 Serial channel
PCI2000 PCI bus, 2 Serial channels
PCI4000 PCI bus, 4 Serial channels
For Ethernet Networks
PCI2000ETH PCI bus, 1 Ethernet channel 10/100 Mb + 1 Serial channel
For Profibus Networks
PCI1500PFB PCI bus, 1 Profibus channel 1.5 Mb
PCI1500S7 PCI bus, 1 Profibus S7 channel 1.5 Mb
PCI2000PFB PCI bus, 1 Profibus channel 12 Mb + 1 Serial channel
CPCI1000PFB CompactPCI bus, 1 Profibus channel 12 Mb
For Modbus Plus Networks
PCI2000MBP PCI bus, 1 Modbus Plus channel + 1 Serial channel
For WorldFIP Networks
PCI2000FIP PCI bus, 1 WorldFIP channel + 1 Serial channel

List of protocols offered as standard on the applicom® product:
Protocols Manufacturer
Jbus ,Modbus (serial and TCP/IP), Modbus Plus Schneider Electric
Uni-Telway, Fipway, Ethway, Uni-Te TCP/IP Schneider Electric
3964-3964R, AS511 (prog port), PPI+, MPI Siemens
Industrial Ethernet ISO layer 4 and TCP/IP Siemens
Sucoma Moeller
Sysmac-Way, FINS TCP/IP Omron
Data Link Otic Fischer
Profibus Siemens + EN 50170
DF1 to DH/DH+/DH485, DF1 (prog. port), EtherNet/IP Allen-Bradley
S-Bus Saia-Burgess
SNP-X GE Fanuc
TI-Dir Siemens/TI
SRTP TCP/IP GE Fanuc
SRTP TCP/IP Alstom / Cegelec
Melsec A & Q TCP/IP Mitsubishi
Alnet II TCP/IP Altus
These solutions provide end users, integrators and manufacturers/OEMs a communication solution
which is easy to implement. The applicom® software tools, in fact, include all components required
to produce your industrial projects:
the applicom configuration console to describe the PLCs connected to the network.
the initialization utility PCINIT, available in executable version and in Windows service
version (usable in automatic mode on booting the computer or manual mode).
the management tasks and protocol tasks downloaded on system start-up in the applicom®
interfaces.
the tools used to test and diagnose the network and the equipment.
For the link with your applications, you have standardized application interfaces, irrespective of the
protocol used:
an OPC server, the worldwide industrial standard for data exchange with your supervision
applications.
a DDE/SuiteLink server based on the DDE protocol (standard DDE or FastDDE) or on the
SuiteLink protocol.
A function library, providing access, in your programming language, to the applicom®
concept functionality.
an ActiveX communication check to develop with tools like Visual Basic, Delphi, etc.
The applicom® concept also makes available pre-processing functions:

Automatic exchanges (cyclic mode).
Monitoring and detection of changes in the status or time-stamped values.
Variable sorting and processing.

The application layer of the applicom® concept (user library, DDE/SuiteLink server and OPC
server) disregards the main characteristics of the field network protocols used.

2. Use constraints
Caution: the present version of the applicom product does not allow:
simultaneous use of the software solution and an applicom hardware interface, irrespective
of the type of this hardware interface.
simultaneous use of the OPC server and the DDE/SuiteLink server.
However, the present version of the applicom product allows:

cohabitation of the applicom solution and the applicomIO product.
simultaneous use of the OPC server or of the DDE/SuiteLink server with the library.
applicom® product requires a protection key. This is resident on the applicom® physical interface.
Key reference:
CA0105 (general case)
CA0106 in case of use of EtherNet/IP (Allen-Bradley)
CA0107 to be able to run applicom® product on Vista system
CA0108 to be able to run applicom® product on Vista system with the use of EtherNet/IP
(Allen-Bradley)
The applicom® product requires a minimum PROM version on the applicom® interfaces greater
than or equal to V3.2.
Compatibility of configurations
The applicom® product allows to retrieve and convert configurations made from an older applicom
version, with the following exceptions:
Configurations had to be created with an applicom version >=3.6
ISA cards and PCI2000IBS are now not supported. As a consequence, if the older
configuration includes few of these cards, they will be automatically deleted from the
configuration when opening the console (as well as all others card having a upper card
number)
To convert the configurations, following up the previous applicom version uninstallation, it is

required to:
Install the new version
Convert each configuration by opening and re-saving it inside the configuration console

Compatibility of applicom software versions / applicom interfaces
If you use this applicom® software version with an applicom® interface delivered with an anterior
software version, you have to verify:
The compatibility of the applicom® interface EPROM version as compared to the version of
the applicom® software.
The compatibility of the applicom® interface EPROM version as compared to protocols
used (see the protocol manuals, chapter ‘Evolution / Compatibility’).
The compatibility of the applicom® interface protection key with your operating system.
Software version applicom® interfaces EPROM version

applicom® 2.5 2.6 2.7 2.8 2.9 3.0 3.1 to 3.2 3.6 to 3.9 >=4.0
V 2.1 X X X X X X X X X
V 2.2 X X X X X X X
V 2.3 X X X X X X
V 2.4 X X X X X
V 2.5 – V 2.9 X X X
V 3.0 – V 3.5 X X
>= V 3.6 X
applicom® interfaces EPROM version

Miscellaneous 2.5 2.6 2.7 2.8 2.9 >= 3.0
Module 5RS485 X
TimeOut max 4095 X X X X
(ms) 65535 X X

User rights agreement for the applicom® program
LEGAL TITLE TO THE PROGRAM:
The use of an APPLICOM product requires the purchase of an exploitation license which is
obligatory.
The acquisition of this license can be obtained either through:
a single station license (to be used on a single computer)
or a station license ( to be used on a non-limited number of computers)
The HOLDER of the license is the owner of the magnetic or other media on which the software
is recorded initially or subsequently. However, the license is granted under the express
condition that applicom international retains title to the program recorded on the original media
and to all copies which may be made of that program subsequently, whatever the form and
whatever the nature of the medium of said original and copies. A license is not a contract for
sale of the original program or of any copy of it.
Where an applicom® product is used without a protocol supplied by applicom international,
that product may be used without benefit of a license.
Single station license

It gives the right to use an applicom® product on a single computer which only use the
communication protocol and the operating system mentioned on the (documents delivery slip,
invoice) provided with the product. These documents must be conform to the licensee's order.
The single station contract (or agreement) is subject to the standard terms and conditions
offered by applicom international.
Multistation license
It gives you the right to use an applicom® product on several computers which only use the
protocol(s) and the operating system(s) mentioned on the multilicense contract.
The licensee will have the right to purchase additional cards he will be able to use with copies
of the software only for and on one site specified on the multistation license.
One copy of the software is provided with each card.
The multistation contract(agreement) is subject to the standard terms and conditions offered by
applicom international.
NUMBERING OF LICENSES:
Single workstation license:
The number of the applicom® card used with the program is the reference number. This
number will be requested in all cases by our After Sales Service department before any
assistance is given.
Multiple workstation license:

When a multiple workstation license is ordered, a user rights agreement assigning an
identification number for the user site is issued in two copies by applicom international. One of
these two copies must be returned to us after addition of the name and signature of the
manager responsible at the user site and the official company stamp. The multiple workstation

license number will be requested in all cases by our After Sales Service department before any
assistance is given.
RESTRICTIONS ON REPRODUCTION:
This program is protected by copyright. Any unauthorized reproduction of the program,
including modification, integration or inclusion of that same program in other software may be
carried out only for backup or filing purposes. The HOLDER is permitted to copy the program
only if it is included or integrated into other software developed by the user organization
holding the appropriate license for the application concerned. Distribution of copies of the
program to third parties is strictly prohibited. The HOLDER may be open to legal proceedings
for any breach of copyright caused or incited by its failure to observe the terms and conditions
of the present license. The copyright warning must be reproduced and included in all copies.

3. Client mode - Server mode
There are two principal modes for using the applicom product depending on the type of protocol
used and the type of application for which applicom interfaces are used.
Client mode
In this type of operation, the applicom software initiates exchanges to or from the connected
equipment. Regardless of the type of application (specific development, OPC,…), it is responsible
for acquiring process data from the equipment at the desired rate.
Server (or slave) mode

In this type of operation, the master or external client initiates exchanges toward the applicom
database. Slave or server mode provides the master or external client with a database composed
of 32 kbits and 32 kwords. The master or external client can access this database freely just as it
accesses any other equipment.
Depending on the protocol selected, the applicom product offers client mode, server mode or both
at the same time. Refer to the documentation of your protocol.

4. Use of the software solution in client mode
Client mode provides your application with easy access to data located in the PLCs.
In this type of operation, the applicom software initiates exchanges to or from the connected
equipment. The application is responsible for acquiring process data from the equipment at the
desired rate
In client mode, the applicom interfaces offer several possibilities for accessing data (synchronous,
asynchronous, cyclic,…). Depending on the type of client application, there are certain levels of
knowledge of these different mechanisms:
If your application uses one of the data servers integrated in the applicom offer (OPC
server, DDE/SuiteLink server), these modules are entirely responsible for the
communication and optimization of transactions with applicom interfaces. Your application
simply references the different variables to access via “image variables” type topics, each
topic symbolizing one piece of remote equipment.
If your application is built around a specific development using the applicom library, it can
be used to process all data access possibilities. In this case, detailed knowledge of usable
mechanisms is necessary, in particular:
Wait mode (synchronous)
Deferred mode (asynchronous)
Cyclic mode (cyclic asynchronous)
Comments:
In the past, many suppliers of supervision application packages developed drivers for
access to applicom interfaces. If one of these packages is used, the communications driver
supplied by the software publisher optimizes communication with applicom interfaces. Even
so, the use of these drivers is increasingly restricted to the benefit of OPC and
DDE/SuiteLink servers integrated in the applicom product
Applicom offers applicom ActiveX Control communication for clients who want to carry out
a specific development rapidly but want to benefit from the optimization mechanisms
integrated in the OPC server. This leads to very rapid deployment of OPC client
applications (graphic configuration of variables, generation of Visual Basic code,…) in
Visual Basic, Delphi and Visual C++ environments.

Wait mode
Wait mode is used to manage exchanges synchronously. The library includes a set of functions to:
Access to protocol communication ports by functions of type READWORD, WRITEWORD,
...allowing to exchange data between the application and the aimed equipment.
Access to non protocoled communication ports by functions of type READMES,
WRITEMES, WRITEREADMES...allowing to transmit and receive buffers on the aimed
channel.
When this type of function is run, the program will wait until:
The function is transferred to the protocol task of the aimed channel.
The formatting related to the protocol is done and transmission is performed on the cable.
The target equipment response is received and processed.
Formatting is done and variables are returned, accompanied by the exchange status.
This mode has the advantage of making the application evolve synchronously with respect to the
change in variable status in the destination equipment as well as the exchange status. This mode
also provides the widest range of functions.
It has the disadvantage, however, that if a large quantity of data must be retrieved or if the
application requires significant processing time, execution is slowed down.

Deferred mode
Deferred mode is used to manage exchanges asynchronously. The library includes a set of
functions to:
Access to protocoled communication ports by functions of type READDIFWORD,
WRITEDIFWORD, ...allowing to exchange data between the application and the aimed
equipment.
Access to non protocoled communication ports by functions of type READDIFMES,
WRITEDIFMES, WRITEREADDIFMES...allowing to transmit and receive buffers on the
aimed channel.
When functions are run in deferred mode, your applicative program will only wait:
Until the request is transferred to the deferred function manager.
It will then be able to continue; at the same time the deferred function manager will run the function
and store its result. The program can search for the result later at its own rhythm in this manager.
The advantage of this operating mode is that the applicative program is not blocked while data are
retrieved. On the other hand, it allows asynchronous operation between the evolution of the
variables and its processing by the program.
Important notes:

The applicom® interface can store up to 64 deferred functions during execution. If it
receives a request when this number is reached, status 41 (Deferred read or write attempt
when the FIFO is full) is sent back to the requesting equipment to indicate that its function
has not been taken into account. To release the FIFO, function TRANSDIF (or
TRANSDIFPACK) must be run in order to retrieve the previous request result.
If you run the function TRANSDIF with the FIFO empty, status 42 (Attempt to transfer data
from the deferred request FIFO when it is empty) will be returned. In the same way, if you
try a TRANSDIF while the deferred request is being run, status -5 will be returned.
Function TESTTRANSDIF allows you to take stock of the performed deferred requests.
The number of deferred requests is restricted to 64 for all the tasks (8 maximum) and each
of them retrieves with the function TRANSDIF only those responses to its own requests.
The status which guarantees the exchange quality can be processed on function
TRANSDIF. It equals 0 for a read (READDIF..) or -1 for a write (WRITEDIF..). Status 0 at
request (READDIF....) only means that the function was accepted by the deferred function
manager.

Cyclic mode
This operating mode fully uses the capacities of the applicom® concept. It can be used to automate
predefined exchanges:
By configuration, when the server is put into service, using the cyclic function configuration
utility PCCYC.
By program, using the function CREATECYC.
These cyclic functions can be permanent, or activated/ activated once time/deactivated selectively
either
Via the cyclic mode functions included in the library (STARTCYC, ACTCYC, STOPCYC, ..)
Via cyclic function topics (DDE/SuiteLink and OPC).
Via command flags located in the interface data base (usable by programs and by DDE
and OPC servers)
There are two principal types of cyclic functions:

For cyclic read functions, the contents of the variables will be picked in the equipment
and stored in the interface database (database/ see cross reference).
For cyclic write functions, the contents of the variables will be picked in the interface
database and transmitted to the target equipment.
The frequency of these functions can be configured, either in chained mode, or at a defined period
(modulo 100 milliseconds). The function period will only be respected if the exchange execution
time is less than the period. The maximum number of cyclic functions is 255 per channel.

Important notes:
This can be performed simultaneously on all the channels.
When creating or configuring the cyclic function, the applicom® product can be used to
modify the data format automatically. Words can therefore be read and stored as bits in the
database. Any combination can be made using the following formats: bit, byte, word,
double word, floating word.
The applicative program has direct access to the variable and the exchange statuses locally.
Access to these variables can be managed in different ways:

By using the function TRANSCYC (or TRANSCYCPACK):
When this type of function is called, data is retrieved in Database via the cyclic function
management task (DISPCYC). This mode has the advantage of not requesting the type, address,
and number of variables to be fed back. Simply enter the channel and cyclic function numbers.
Even if the parameter used to store the exchange status in a database word was not used for
creating the cyclic function, the exchange status will be returned.
If TRANSCYC (or TRANSCYCPACK) is used for a function that has never been
activated, status 35 will be returned and no data transferred. Equally, this status can be
returned if you carry out a TRANSCYC although the first execution of this function is not
completed (attempt to transfer data before it has been read in the equipment).
If TRANSCYC is used for a function that is no longer active, status -6 will be returned with
the data.

By using Database functions GETWORD, GETPACKBIT, ....:
When this type of function is called, the data is directly picked in the interface database. This is
certainly one of the fastest methods, but on the other hand, the type, address and number of
variables to be fed back must be known.
The status fed back by the function does not indicate whether or not the cyclic function was
executed correctly. The parameter used to store the cyclic function status in the database when it
was created must be used. The status of this word provides the guarantee that the exchange took
place correctly (this word is only updated by the cyclic function if the exchange status is changed).
By using the event FIFO in Database (CONFDB, GETEVENT):

Evolution of variables in the database can be logged in a 4096-position event FIFO with function
CONFDB. Any status or value change will thus be listed and time-stamped. The applicative
program can query this FIFO with function GETEVENT.

5. Use of the software solution in server mode
The slave or server mode makes available to the master or external client a database, made of 32
kbits and 32 kwords. The master or external client can access this database freely exactly as it
accesses any other equipment.
In this type of operation, the master or external client initiates exchanges toward the applicom
database.
Phases 1, 2, 3 and 4 are fully managed by the interface and require no call to server library
functions.
Note: This type of configuration can also be used to access variables retrieved by cyclic functions
configured on other interface channels (exchange marked A, B and C on the diagram).
In server mode, data is retrieved by the application in the applicom interface database

6. Database: Internal data area
The database is an internal data area of the applicom interface that can be used in different
contexts:
Access variables deposited by master or external client equipment. If a protocol with server
functions is used, this data area is accessible directly by the remote equipment.
Provide variables in the form of bits, words,.. to master or external client equipment
Access variables captured by cyclic read functions configured on master or client channels.
If necessary, this mode can be combined with conventional use of the OPC server. It is
thus possible to configure your own cyclic exchanges via the cyclic function configuration
utility and retrieve the data in the database using a local variable type topic.
Position variables in equipment by cyclic write functions configured in the master or client
channels. This is a very interesting possibility for sending voluminous record files. Writing is
performed in the database (very rapid) and then a pre-configured cyclic write function is
triggered. In this case, only one transaction is carried out on the network.
As a storage area, it is also a possible means of sharing data among several applications
(library, OPC clients,…).
On multichannel applicom boards, enable the creation of simple gateways from one
protocol to another by using the database, e.g. configuration of a cyclic read function to
retrieve data on the first channel and configuration of a cyclic write function returning the
data to equipment on the second communication channel.
The database consists of two independent areas:

a bit area of 32 kbits
a word area of 32 kwords.
Depending on the type of client application, data is retrieved in the database of the applicom
interface by the application as follows:
If your application uses one of the data servers integrated in the applicom product (OPC
server, DDE/SuiteLink server), all communication and optimization of transactions with
applicom interfaces is handled by these modules. Your application simply references the
different variables to access using “local variables” type topics, each topic symbolizing one
database of one applicom interface.
If your application is built around a specific development using the applicom library, it is
possible to
Use direct access functions to database data (getword,…)
Or use the events FIFO associated with the database.
Note: The library functions that access the interface database are available only in wait mode (the
response is immediate since accesses remain local).

Organization of the bit area
The bit area of the database is a 32 kbit area storing the bit type variables
DATABASE
32 kbits
Address Function
Decimal Hexadecimal
0 0000
1 0001
2 .
. . Available
. . bit area
. .
. .
31 998 7CFE
31 999 7CFF
32 000 7D00
. . Reserved by
. . applicom®
32765 7FFD
32766 7FFE Logging FIFO reset
This bit in monostable.
32767 7FFF Indicates that the logging FIFO is full. In
this case, the oldest loggings are lost.
This bit must be zeroed.

Organization of the word area
The word area of the database is a 32 kword area storing the variables of type:
Bytes
The bytes are stored in the word area (two bytes per word), from offset 25 000 (with respect to the
word addressing).
Word address Byte address

MSB LSB
25000 1 0
25001 3 2
. . .
. . .
31999 13999 13998
Words
There is direct mapping between the address to be entered to access a word and the true address
in the database.
Double words and floating words

A double word or a floating word (32 bits) consists of two 16-bit words:
Word Address Double word address

0 0
1
2 .
3 3
4
. .
. .
32 766 32 766
32 767

General organization of the word area
DATA-BASE
32 K Words
Word Address Function
Decimal Hexadecimale
0 0000
1 0001
. .
. .
24 999 61A7 Available word,
double word,
25 000 61A8 Byte address
floating word
. . 1-0
area
. Available byte
. area
.
31 999 7CFF 13 999 – 13 998
32 000 7D00
. .
Reserved
. .
32 679 7FA7
32 680 7FA8 Tenths of second
32 681 7FA9 Seconds
32 682 7FAA Minutes
32 683 7FAB Hours
32 684 7FAC Days
32 685 7FAD Months
Clock and
32 686 7FAE Years
Calendar
32 687 7FAF Time coded on 16 bits
Hours Minutes Seconds/2
F to B A to 5 4 to 0
32 688 7FB0 Date coded on 16 bits
Years Month Days
F to 9 8 to 5 4 to 0
32 700 7FBC
. .
Reserved
. .
32 767 7FFF
The clock and the calendar are automatically initialized to the computer values when initializing the
applicom interfaces.

Example of using the database
Example 1:
Writing the value 44 in a byte at address 0.
Reading the same value in a word at address 25000.
Example 2:
Writing the value 32000 in a double word at address 25000.
Reading the same value in a 16-bit word at address 25000.

Events FIFO in Database
Evolution of variables in the database can be logged in a 4096-position event FIFO with function
CONFDB. Any status or value change will thus be listed and time-stamped.
The applicative program can query this FIFO with function GETEVENT. This mode has the
advantage of only taking into account the variables whose status has changed.
The status fed back by the function does not indicate if the cyclic function took place correctly. The
parameter used to store the cyclic function status in the database when it was created must be
used. The status of this word provides the guarantee that the exchange took place correctly (this
word is only updated by the cyclic function if the exchange status is changed).

Management of cyclic functions by the “command flag-status word” pair
The first 128 cyclic functions of each channel on the board can be triggered.
To do this, an area of 512 Command flag bits and an area of 512 Status words are reserved in
the applicom® database.
The bit area starts at address 32200. The word area starts at address 32100.
They enable you to start, stop, or activate only once the targeted cyclic function. You must use this
method with triggered write functions (transmission of local variables to a remote device).
The formula to find the command flag address is:
32200 + channel number * 128 + function number
The formula to find the status word address is:
32100 + channel number * 128 + function number
Channel Cyclic Function “Status Word” address area in “Command Flag” address area in
number number word area database bit area database
0 1 to 128 32101 to 32228 32201 to 32328
1 1 to 128 32229 to 32356 32329 to 32456
2 1 to 128 32357 to 32484 32457 to 32584
3 1 to 128 32485 to 32612 32585 to 32712
Example:
The Command flag and Status word addresses of function number 2 of channel 3 are:
bit address = 32200 + 3 * 128 + 2 = 32586
word address = 32100 + 3 * 128 + 2 = 32486
By setting to 1 the command flag bit corresponding to the required cyclic function, the Server will
set the function in the status defined by the value of the status word:
status word = 0:Exceptional activation of the cyclic function (only once).
status word = 1:start the cyclic function.
status word = 2:stop the cyclic function.

DATABASE access locks
Access to Database data areas can be locked by setting special words in Database (32 700 to
32 763).
There are:
Eight lock areas on the word area
Eight lock areas on the bit area
These locks can be placed (or removed) by writing certain words in the database from:
Master or external client equipment.
The applicative program, using the function:
Bit area locks
Address Function
32 700 Lower limit of bit area 0 lock
32 701 Upper limit of bit area 0 lock
32 702 Type of lock on bit area 0
32 703 User free bit
32 704 to 32 707 Parameters, bit area 1
Word area locks:
Address Function
32 732 Lower limit of word area 0 lock
32 733 Upper limit of word area 0 lock
32 734 Type of lock on word area 0
32 735 User free word
32 736 to 32 739 Parameters, word area 1
Lock type:
0: No protection
1: Read protected
2: Write protected
3: Read and write protected
When the user program places a lock (SETWORD), none of the communication channels has
further access to the locked data.

When external equipment (master or client) places a lock, only equipment connected on the same
channel has access to the data.
Access to a locked data area produces:

In JBUS / MODBUS a response error 4.
In UNI-TELWAY / ETHWAY a negative report = H'FD'
When the upper and lower limits are already positioned, simply write in the Lock type word to
permit, or not, access to this area.
A lock block can protect another block or itself. A lock can therefore be placed with the certainty
that other equipment cannot remove it.

Modem link management
The interface applicom® allows the use of standard modems on leased lines (LL), or switching
network (STN).
Management of modem signals depends on the choice made when the channel was configured.
The RS232 line can be managed in two ways:
2-signal RS232:
The 2-signal option means that the protocol task installed at the channel level only manages TxD
and RxD for the data transmission and reception.
You can position your RTS and DTR check signals from the applicative program by
using function SETMODEM (nchan, rts, dtr, status), or by OPC/DDE with the
RTS_DTR item.
You can query CTS and DCD check signals from the applicative program by using
function GETMODEM(nchan, cts, dcd, status), or by OPC/DDE with the CTS and
DCD items.
This configuration allows the use of FULL DUPLEX modems on leased lines (LL) or switching
network (STN).
6-signal RS232:
The 6-signal option means that the protocol task installed at the channel level manages the
following signals:
TxD et RxD for data transmission and reception.
RTS, output signal positioned by the applicom® interface before each
transmission.
CTS, input signal positioned by the modem, must be active to allow the
transmission.
DCD, input signal positioned by the modem, must be active to allow the reception.
The DCD can be connected to any incoming signal from the modem, for example
the DSR.
You can position the DTR check signal from the applicative program by using function
SETMODEM( nchan, rts, dtr, status) or by OPC/DDE with the RTS_DTR item. The RTS signal
status is unimportant since it will be positioned automatically.
You can query the CTS and DCD check signals from the applicative program by using function
GETMODEM(nchan, cts, dcd, status) or by OPC/DDE with the CTS or DCD items.
This configuration allows the use of HALF DUPLEX modems on leased lines (LL) or switching
network (STN).

Modem link on switching network (STN)
Numbering modem with number memorization
The communication is set up by the applicative program with the SETMODEM function DTR signal,
or by OPC/DDE with the RTS_DTR item. When DTR is set at 1, the modem must ensure the
numbering then the connection.
Numbering modem without number memorization

The communication is set up by the applicative program by transmitting the character chain that
corresponds to the numbering and modem control (ex: HAYES controls). This sequence can be
transmitted in Jbus, or Modbus Master with function WRITEMES.
The applicative program will find the line status:
By querying the DSR signal of the modem connected to the applicom® interface DCD, by
using the GETMODEM function.
From the modem's response to the control sent (e.g. HAYES controls), retrieved by the
applicom® READMES function.

Example of architecture: applicom® Jbus master with numbering
modem

Example of architecture: applicom® Jbus master with auto-response
modem
On an event, the slave drives the modem with a discrete output or with the DTR signal.

Example of architecture: applicom® Jbus slave with auto-response
modem
Alarm feedback on the Masters initiative towards the applicom® interface configured as slave.


HW Functionality

Uploaded by

Copyright:

Available Formats

HW Functionality

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HW Functionality

Uploaded by

Copyright:

Available Formats

Functionality

a product of Woodhead Software & Electronics

Copyright © 2006 Woodhead Software & Electronics. All rights reserved.

Copyright © 2006 Woodhead Software & Electronics. All rights reserved.

1. Description of the hardware solution...........................................4

3. Client mode - Server mode .........................................................11

4. Use of the software solution in client mode..............................12

5. Use of the software solution in server mode ............................20

6. Database: Internal data area .......................................................21

Copyright © 2006 Woodhead Software & Electronics. All rights reserved.

List of interfaces offered as standard on the applicom® product:

Copyright © 2006 Woodhead Software & Electronics. All rights reserved.

The applicom® concept also makes available pre-processing functions:

Copyright © 2006 Woodhead Software & Electronics. All rights reserved.

Copyright © 2006 Woodhead Software & Electronics. All rights reserved.

However, the present version of the applicom product allows:

To convert the configurations, following up the previous applicom version uninstallation, it is

Copyright © 2006 Woodhead Software & Electronics. All rights reserved.

Software version applicom® interfaces EPROM version

applicom® interfaces EPROM version

Copyright © 2006 Woodhead Software & Electronics. All rights reserved.

LEGAL TITLE TO THE PROGRAM:

Single station license

Multiple workstation license:

Copyright © 2006 Woodhead Software & Electronics. All rights reserved.

Copyright © 2006 Woodhead Software & Electronics. All rights reserved.

Server (or slave) mode

Copyright © 2006 Woodhead Software & Electronics. All rights reserved.

Copyright © 2006 Woodhead Software & Electronics. All rights reserved.

Copyright © 2006 Woodhead Software & Electronics. All rights reserved.

Copyright © 2006 Woodhead Software & Electronics. All rights reserved.

Copyright © 2006 Woodhead Software & Electronics. All rights reserved.

There are two principal types of cyclic functions:

Copyright © 2006 Woodhead Software & Electronics. All rights reserved.

Copyright © 2006 Woodhead Software & Electronics. All rights reserved.

Copyright © 2006 Woodhead Software & Electronics. All rights reserved.

By using the event FIFO in Database (CONFDB, GETEVENT):

Copyright © 2006 Woodhead Software & Electronics. All rights reserved.

Copyright © 2006 Woodhead Software & Electronics. All rights reserved.

The database consists of two independent areas:

Copyright © 2006 Woodhead Software & Electronics. All rights reserved.

Copyright © 2006 Woodhead Software & Electronics. All rights reserved.

Word address Byte address

Double words and floating words

Word Address Double word address

Copyright © 2006 Woodhead Software & Electronics. All rights reserved.

Copyright © 2006 Woodhead Software & Electronics. All rights reserved.

Copyright © 2006 Woodhead Software & Electronics. All rights reserved.

Copyright © 2006 Woodhead Software & Electronics. All rights reserved.

Copyright © 2006 Woodhead Software & Electronics. All rights reserved.

Bit area locks

Word area locks:

Copyright © 2006 Woodhead Software & Electronics. All rights reserved.

Access to a locked data area produces:

Copyright © 2006 Woodhead Software & Electronics. All rights reserved.

Copyright © 2006 Woodhead Software & Electronics. All rights reserved.

Numbering modem without number memorization

Copyright © 2006 Woodhead Software & Electronics. All rights reserved.

Copyright © 2006 Woodhead Software & Electronics. All rights reserved.