Rockwell Automation Allen-Bradley ControlLogix 1756-MVI User manual

ControlLogix
Multi-Vendor
Interface Module
1756-MVI
Programming Reference
Manual

Important User Information
Because of the variety of uses for the products described in this
publication, those responsible for the application and use of this
control equipment must satisfy themselves that all necessary steps
have been taken to assure that each application and use meets all
performance and safety requirements, including any applicable laws,
regulations, codes and standards.
The illustrations, charts, sample programs and layout examples shown
in this guide are intended solely for purposes of example. Since there
are many variables and requirements associated with any particular
installation, Allen-Bradley does not assume responsibility or liability
(to include intellectual property liability) for actual use based upon
the examples shown in this publication.
Allen-Bradley publication SGI-1.1, Safety Guidelines for the
Application, Installation and Maintenance of Solid-State Control
(available from your local Allen-Bradley office), describes some
important differences between solid-state equipment and
electromechanical devices that should be taken into consideration
when applying products such as those described in this publication.
Reproduction of the contents of this copyrighted publication, in whole
or part, without written permission of Rockwell Automation, is
prohibited.
Throughout this manual we use notes to make you aware of safety
considerations:
Attention statements help you to:
•identify a hazard
•avoid a hazard
•recognize the consequences
Allen-Bradley and ControlLogix are trademarks of Rockwell Automation.
Borland C++ is a trademark of Borland Corporation.
Microsoft C++, Windows 95/98, and Windows NT are trademarks of Microsoft Corporation.
ATTENTION
!
Identifies information about practices or
circumstances that can lead to personal injury or
death, property damage or economic loss
IMPORTANT Identifies information that is critical for successful
application and understanding of the product.

European Communities (EC)
Directive Compliance
If this product has the CE mark it is approved for installation within
the European Union and EEA regions. It has been designed and
tested to meet the following directives.
EMC Directive
This product is tested to meet the Council Directive 89/336/EC
Electromagnetic Compatibility (EMC) by applying the following
standards, in whole or in part, documented in a technical
construction file:
•EN 50081-2 EMC — Generic Emission Standard, Part 2 —
Industrial Environment
•EN 50082-2 EMC — Generic Immunity Standard, Part 2 —
Industrial Environment
This product is intended for use in an industrial environment.
Low Voltage Directive
This product is tested to meet Council Directive 73/23/EEC Low
Voltage, by applying the safety requirements of EN 61131-2
Programmable Controllers, Part 2 - Equipment Requirements and
Tests. For specific information required by EN 61131-2, see the
appropriate sections in this publication, as well as the Allen-Bradley
publication Industrial Automation Wiring and Grounding Guidelines
For Noise Immunity, publication 1770-4.1.
This equipment is classified as open equipment and must be
mounted in an enclosure during operation to provide safety
protection.

1Publication 1756-RM004B-EN-P - October 2000
Preface
About This Reference Manual
Introduction
This reference manual provides information needed to develop
application programs for the 1756-MVI ControlLogix Multi-Vendor
Interface Module. The 1756-MVI module allows access through the
ControlLogix platform to devices with a serial port. The MVI module is
user programmable to accommodate devices with unique serial
protocols.
This manual contains the available software API (Application
Programming Interface) libraries and tools, module configuration and
programming information, and example code.
Audience
This manual is intended for control engineers and technicians who are
installing, programming, and maintaining a control system that
includes a 1756-MVI module.
We assume that you:
•are familiar with software development in the 16-bit DOS
environment using the C programming language.
•are familiar with Allen-Bradley programmable controllers and
the ControlLogix platform.
Common Techniques Used
in this Manual
The following conventions are used throughout this manual:
•Bulleted lists provide information, not procedural steps.
•Numbered lists provide sequential steps.
•Information in bold contained within text identifies menu
windows, or screen options, screen names, and areas of the
screen.
•Change bars in the left margin of the page indicate material that
is new to this revision.

Publication 1756-RM004B-EN-P - October 2000
P-2 About This Reference Manual
Contents
This programming reference manual contains the following chapters:
References
For additional information refer to the following publications:
•ControlLogix 1756-MVI Multi-Vendor Interface Module
Installation Instructions, publication number1756-1N001A-US-P
•General Software Embedded DOS 6-XL Developer’s Guide 1.2
•Introduction to ControlLogix Module Development, CID#X1557
Screen captures are pictures of the software’s actual
screens and windows. The names of screen buttons and
fields are often in bold in the text of a procedure.
The “MORE” icon is placed beside any paragraph that
references sources of additional information outside of this
document.
More
2
1
3
Application
Development
Overview
4CIP Messaging
Serial Port API
5
1756-MVI Module
Overview
MVI Backplane API Programming the MVI
Module
6
More

Publication 1756-RM004B-EN-P - October 2000
About This Reference Manual P-3
Definitions of Terms
Used in this Manual
Rockwell Automation
Support
Rockwell Automation offers support services worldwide, with over 75
sales/support offices, 512 authorized distributors, and 260 authorized
systems integrators located throughout the United States alone, plus
Rockwell Automation representatives in every major country in the
world.
Local Product Support
Contact your local Rockwell Automation representative for:
•sales and order support
•product technical training
•warranty support
•support service agreements
Technical Product Assistance
If you need to contact Rockwell Automation for technical assistance,
call your local Rockwell Automation representative, or call Rockwell
directly at: 1 440 646-6800.
For presales support, call 1 440 646-3NET.
This term Means
API Application Programming Interface.
Backplane The electrical interface, or bus, to which modules connect when inserted
into the rack. The 1756-MVI module communicates with the control
processor(s) through the ControlLogix backplane (a.k.a. ControlBus).
BIOS Basic Input Output System. The BIOS firmware initializes the module at
power-on, performs self-diagnostics, and provides a DOS compatible
interface to the console and Flash ROM disk.
CIP Control and Information Protocol. This is the messaging protocol used for
communications over the ControlLogix backplane. See the ControlNet
Specification for details.
Connection A logical binding between two objects. A connection allows more efficient
use of bandwidth, since the message path is not included once the
connection is established.
Consumer A destination for data.
Library The library file containing the API functions. The library must be linked with
the developer’s application code to create the final executable program.
Originator A client that establishes a connection path to a target.
Producer A source of data.
Target The end-node to which a connection is established by an originator.

Publication 1756-RM004B-EN-P - October 2000
P-4 About This Reference Manual
You can obtain technical assistance online from the following
Rockwell Automation WEB sites:
•www.ab.com/mem/technotes/kbhome.html (knowledge base)
•www.ab.com/networks/eds (electronic data sheets)
Your Questions or Comments about This Manual
If you find a problem with this manual, please notify us of it on the
enclosed Publication Problem Report (at the back of this manual).
If you have any suggestions about how we can make this manual
more useful to you, please contact us at the following address:
Rockwell Automation, Allen-Bradley Company, Inc.
Control and Information Group
Technical Communication
1 Allen-Bradley Drive
Mayfield Heights, OH 44124-6118

iPublication 1756-RM004B-EN-P - October 2000
Table of Contents
Chapter 1
1756-MVI Module Overview
What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . 1-1
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
LED Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Configuration Jumpers . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
System Firmware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
BIOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
BIOS Console Services . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
BIOS Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Operating System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Chapter 2
Application Development
Overview
What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . 2-2
API Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Calling Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Header Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Sample Application Code . . . . . . . . . . . . . . . . . . . . . . . 2-3
Multithreading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Development Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Chapter 3
MVI Backplane API
What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . 3-1
MVI API Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
MVI Backplane API Architecture . . . . . . . . . . . . . . . . . . . . 3-2
MVI Backplane API Functions . . . . . . . . . . . . . . . . . . . . . . 3-5
Initialization Functions . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Direct I/O Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Miscellaneous Functions. . . . . . . . . . . . . . . . . . . . . . . . 3-20
Chapter 4
CIP Messaging API
What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . 4-1
CIP Messaging API Files . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
CIP API Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Backplane Device Driver. . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
CIP API Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Initialization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Object Registration. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Connected Data Transfer . . . . . . . . . . . . . . . . . . . . . . . 4-10
Callback Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Special Callback Registration . . . . . . . . . . . . . . . . . . . . 4-25
Miscellaneous Functions. . . . . . . . . . . . . . . . . . . . . . . . 4-28

Publication 1756-RM004B-EN-P - October 2000
Table of Contents ii
Chapter 5
Serial Port API
What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . 5-1
Serial API Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Serial Data Transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Serial Port API Functions . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Initialization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Port Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Miscellaneous Functions. . . . . . . . . . . . . . . . . . . . . . . . 5-35
Chapter 6
Programming the MVI Module
What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . 6-1
ROM Disk Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
CONFIG.SYS File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Command Interpreter. . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Sample ROM Disk Image . . . . . . . . . . . . . . . . . . . . . . . 6-3
Creating a ROM Disk Image . . . . . . . . . . . . . . . . . . . . . . . 6-4
Using DISKIMAG: DOS Disk Image Builder . . . . . . . . . 6-4
Using WINIMAGE: Windows Disk Image Builder . . . . . 6-6
Downloading a ROM Disk Image. . . . . . . . . . . . . . . . . . . . 6-8
MVI Flash Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
Using the MVI Flash Update Utility . . . . . . . . . . . . . . 6-8
MVIUPDAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Booting from the C: (Compact Flash) Drive . . . . . . . . . . . . 6-11
Index

1Publication 1756-RM004B-EN-P - October 2000
Chapter 1
1756-MVI Module Overview
What This Chapter Contains
The following table identifies what this chapter contains and where to
find specific information.
Features
The 1756-MVI module allows the user to develop C language code to
support the transfer of serial data to/from three serial ports, as well as
the transfer of 16-bit, 32-bit, float, and ASCII characters between the
ControlLogix processor and the MVI.
The MVI sits as a target device on the ControlLogix backplane and will
accept CIP connections from an originator based on the “generic
module” profile. The MVI can be configured with an I/O module
connection for scheduled (Class 1) data transfers up to 496 bytes
to/from the 5550 processor. The MVI supports unscheduled (class 3)
data transfers up to 478 bytes generated from MSG (message)
instructions in the 5550.
For information about See page
Features 1-1
LED Indicators 1-3
Configuration Jumpers 1-4
System Firmware 1-5
BIOS 1-5
BIOS Console Services 1-5
BIOS Setup 1-5
Operating System 1-8

Publication 1756-RM004B-EN-P - October 2000
1-2 1756-MVI Module Overview
A block diagram of the module is shown in figure 1.1.
Figure 1.1 1756-MVI Module Block Diagram
The 1756-MVI module has three serial ports. Serial port PRT1 (also
called the “console port”) is used with a programming console via an
RS-232 interface. The other two serial ports, PRT2 and PRT3, can be
configured to communicate with foreign devices via RS-232, RS-422,
or RS-485 interfaces.
The 1756-MVI module includes the following features:
•1M bytes of RAM for temporary storage of user programs and
data
•Persistent program storage in FLASH memory, with 896K bytes
available for user program storage
•Two RS-232 / RS-422 / RS-485 compatible serial ports for
communications to foreign devices (PRT2 and PRT3)
•One RS-232 compatible serial port for communicating with a
programming terminal (PRT1, console)
•LED’s for module status, communications status, and general
purpose use
•ControlLogix bus interface
•Embedded BIOS and DOS-compatible operating system.
Communications
Processor
ControlBus
I/F
Flash
ROM RAM
RS-232
Serial Port
PRT1
(Console)
PRT2
PRT3
Compact
Flash
(Optional)

Publication 1756-RM004B-EN-P - October 2000
1756-MVI Module Overview 1-3
LED Indicators
The 1756-MVI module has seven LED indicators at the top of its front
panel. Five of these indicators display the module’s status and port
activity. The other two, LEDs U1 and U2, are controlled by the user
application and may be used for any purpose.
Figure 1.2 LED Indicators
LED Description Status Meaning
P1, P2, P3 Port Activity Off No serial activity detected on corresponding port.
Green Serial activity detected on corresponding port.
U1, U2 User Defined - Application dependent.
BATT Battery Off Battery voltage normal.
Red Battery voltage low. Service required.
OK (1)
(1) Defaults shown. The OK LED can also signify Status determined by the user-programmable
“SetModuleStatus” command. Note that neither the SetModuleStatus command nor the
BIOS/hardware has priority on the LED, so each can overwrite the other.
Module Status Off Power is OFF or module is not installed.
Green Power is ON. Normal Operation.
Red Power up non-recoverable fault.
Flashing
Green/Red
NVS update in progress.
Not configured.(2)
Not connected.(2)
Recoverable major fault.(2)
(2) These are “typical” for ControlLogix modules. Because the MVI module is user-programmable,
this has to be implemented by the user.

Publication 1756-RM004B-EN-P - October 2000
1-4 1756-MVI Module Overview
Configuration Jumpers
Three configuration jumpers are located on the 1756-MVI module’s
printed circuit board, as shown in figure 1.3.
Figure 1.3 Configuration Jumpers
Jumpers PRT2 and PRT3 are used to configure the serial ports for
RS-232, RS-485, or RS-422 compatibility. The Setup Jumper is used to
force the console port (PRT1) to a known state.
When the Setup Jumper is installed, the module will boot with the
console port enabled at 19200 baud, no parity, 8 data bits, and 1 stop
bit. If the Setup Jumper is not installed, the module will boot with the
console port set up as configured by the BIOS Setup Menu.
See chapter 6 of this manual and publication 1756-IN001A-US-P for
more information.
PRT2SETUP PRT3
IN = SETUP MODE
OUT = APPLICTION
MODE
RS232
RS422
RS485
RS485
RS422
RS232

Publication 1756-RM004B-EN-P - October 2000
1756-MVI Module Overview 1-5
System Firmware
The 1756-MVI module includes an embedded BIOS and a
DOS-compatible operating system stored in Flash ROM. An additional
896K bytes of Flash ROM is configured as a ROM disk for user
program storage.
The ROM disk is mapped as drive A:/. The MVI also supports an
optional Compact Flash. The Compact Flash is mapped as C:/ and
must be enabled in the BIOS setup (see figure 1.5).
BIOS
The BIOS initializes the module and configures its devices. It provides
a DOS-compatible interface for the console and ROM disk services.
The BIOS also provides a means to update the ROM disk image
containing the user programs.
BIOS Console Services
The BIOS supports a DOS-compatible system console by redirecting
the BIOS video and keyboard services (INT10 and INT16) to serial
port PRT1. Special functions, such as cursor positioning, are translated
into ANSI escape sequences.
If the console is disabled in BIOS setup and the Setup Jumper is not
installed, then the video and keyboard redirection is not performed
and PRT1 is available for the user application.
BIOS Setup
The BIOS also allows the user to configure the module using the BIOS
Setup Menu. The Setup Menu provides module type and console port
(PRT1) configuration. The Setup Menu is invoked by typing Ctrl-C on
the console terminal connected to PRT1 when prompted during the
module boot process. The console terminal must be configured for
the ANSI or VT100 character sets in order to properly display the
Setup Menu.

Publication 1756-RM004B-EN-P - October 2000
1-6 1756-MVI Module Overview
Figure 1.4 shows the boot messages displayed on the console after
power-on:
Figure 1.4 Power-On Boot Messages
Type Ctrl-C to if you want to open the BIOS Setup Main Menu
(figure 1.5).
Figure 1.5 BIOS Setup Main Menu
The BIOS Setup Main Menu contains the three items shown above.
To move from one menu item to another, press Tab. To select the
current item, press Enter. To exit the Main Menu and continue
booting, press Esc or choose Exit.
TIP If the 1756-MVI module boot messages do not
appear on the console terminal when the module is
powered on, check the position of the Setup Jumper
(see the Installation Instructions). In Setup Mode
(setup jumper installed), the console port will be
enabled and configured for 19200 baud, no parity, 8
data bits, and 1 stop bit.
General Software 80C386-EX Embedded BIOS (tm) Version 4.1
Copyright (C) 1998 General Software, Inc.
1756-MVI Multi-Vendor Interface Module
MVI BIOS v1.00
Copyright (c) 1999-2000 Online Development, Inc.
Hit ^C if you want to run SETUP.
| System Bios Setup - Utility v4.001 |
| (C) 1998 General Software, Inc. All rights reserved |
+---------------------------------------------------------------+
| |
| |
| MVI Module Configuration |
| Begin Flash ROM Update Mode |
| Reset Configuration to Factory Default |
| Exit |
| |
| |
+---------------------------------------------------------------+
| <Esc> to continue |

Publication 1756-RM004B-EN-P - October 2000
1756-MVI Module Overview 1-7
Selecting the first item in the Main Menu, MVI Module
Configuration, displays the menu shown in figure 1.6:
Figure 1.6 MVI Module Configuration Menu
The MVI Module Configuration Menu is used to configure the
console port and module type. To move between menu items, press
Tab. Press +or -to change an item.
Note: The console settings configured on this menu are only used
when the Setup Jumper is in the Normal position (not installed). If the
Setup Jumper is in the Setup position, the console port is always
enabled and configured for 19200 baud. Console setting changes will
take effect the next time the module boots (after a reboot command
or power cycle).
The Compact Flash is an ideal tool for development because it is a
read/write device. It is much easier to download individual files to the
compact flash than to download a complete disk image to the ROM
disk, which is read-only. Typically, you use the compact flash for
development, and download the final runtime image to the A:\ ROM
disk.
The second choice on the Setup Main Menu, Begin Flash ROM
Update Mode, is used to update the ROM disk image. Once this
mode is entered, the module must be rebooted to continue normal
operation. A special Flash update utility, MVIUPDAT, is used to
transfer the disk image to the module.
| System BIOS Setup - Custom Configuration |
| (C) 1998 General Software, Inc. All rights reserved |
+--------------------------------+------------------------------+
|||
|||
| Console on Port 1 >Disabled | Compact Flash Disabled |
| Console Baud Rate 19200 | |
|||
|||
|||
+--------------------------------+------------------------------+
| ^E/^X/<Tab> to select or +/- to modify |
<Esc> to return to main menu
TIP If you disable the console during the boot process
no characters will be sent to PRT1, and the boot
process will be shortened by several seconds.

Publication 1756-RM004B-EN-P - October 2000
1-8 1756-MVI Module Overview
See chapter 6 for more information.
Operating System
The 1756-MVI module contains a General Software Embedded DOS
6-XL operating system. This provides DOS compatibility along with
real-time multitasking functionality. The operating system is stored in
Flash ROM and is loaded by the BIOS when the module boots.
DOS compatibility allows development of applications using standard
DOS tools, such as Borland™ or Microsoft™ C/C++ compilers. User
programs may be executed automatically on powerup by loading
them from either the CONFIG.SYS file or an AUTOEXEC.BAT file.
See the General Software Embedded DOS 6-XL Developer's Guide for
more information.
IMPORTANT DOS programs that try to access the video or
keyboard hardware directly will not function
correctly on the 1756-MVI module. Only programs
that use the standard DOS and BIOS functions to
perform console I/O are compatible.
More

1Publication 1756-RM004B-EN-P - October 2000
Chapter 2
Application Development Overview
The 1756-MVI API suite allows developers to access the ControlLogix
backplane and serial ports without needing detailed knowledge of the
module’s hardware design. The 1756-MVI API Suite consists of three
distinct components:
•the MVI Backplane API
•the CIP Messaging API
•the Serial Port API
The MVI Backplane API and CIP Messaging API provide access to the
ControlBus. The Serial Port API provides access to the serial ports.
The MVI Backplane API is “generic,” and is portable among all MVI
form factors from Rockwell Automation and third parties. This
“generic” API performs read/write operations with the form factor’s
control processor (PLC) by calling the more specific backplane API
required for that form factor. For example, if running a 1756-MVI, the
generic backplane API calls the CIP API to actually read/write 5550
processor data. If running on third party 1794- form factor, the generic
backplane API calls a SERBUS API to communicate with the Flex
adapter, which in turn sends or receives data to/from a Flex scanner.
The serial port API is portable among all MVI form factors as well.
IMPORTANT Since the MVI API uses the CIP API to access the
backplane, an application that uses the MVI API
cannot directly access the CIP API (CIPAPI.lib,
CIPAPI.h). Similarly, an application using the CIP API
cannot also use the MVI API. In other words, you
use either the MVI Backplane API or the CIP API to
talk to the 5550, but you cannot use both.
•The CIP API is used if you want to control the
CIP connection between a 5550 processor (or
other originator) and the MVI module.
•The MVI Backplane API is used if you simply
want to read/write data for a single 5550
processor, with no concern about the CIP
connection between the processor and MVI.

Publication 1756-RM004B-EN-P - October 2000
2-2 Application Development Overview
What This Chapter Contains
Applications for the 1756-MVI module may be developed using
industry-standard DOS programming tools and the appropriate API
components. This chapter provides general information pertaining to
application development for the 1756-MVI module. The following
table identifies what this chapter contains and where to find specific
information.
API Libraries
Each of the three APIs provide a library of function calls. The libraries
support any programming language that is compatible with the Pascal
calling convention.
Each API library is a static object code library that must be linked with
the application to create the executable program. It is distributed as an
16-bit large model OMF library, compatible with Borland and
Microsoft development tools.
The following compiler versions have been tested and are known to
be compatible with the 1756-MVI module API:
•Borland™ C++ V3.1
•Borland™ C++ V5.02
•Microsoft™ VC++ V1.52
Note: Microsoft Visual C++ versions above 1.52 no longer support
16-bit development. However, Visual C++ 1.52 is available from
Microsoft for those who own later versions of Visual C++.
Calling Convention
The API library functions are specified using the C programming
language syntax. To allow applications to be developed in other
industry-standard programming languages, the standard Pascal calling
convention is used for all application interface functions.
For information about See page
API Libraries 2-2
Calling Convention 2-2
Header Files 2-3
Sample Application Code 2-3
Multithreading 2-3
Development Tools 2-3