1747系列控制器比较与用户指南：1747-OCE vs 1747-OCF

1747

需积分: 9 127 浏览量更新于2024-07-21 收藏 1.96MB PDF 举报

身份认证购VIP最低享 7 折!

30元优惠券

资源详情

资源推荐

1747-UM001A-US-P - March 2000

1-4 Introducing the Open Controller

Your application (the code you develop) uses the dual-port memory to

communicate with the SCANNER and to handle control functions on the

1746 backplane, such as:

• SCANNER commands and responses

• battery and SCANNER status

• scan rate frequency and timing

• I/O image counters

• priority messages and interrupts

• semaphores to ensure data integrity

• software-generated watchdogs

• control of the four user-definable LEDs, the 3-position switch, and the

2-position jumper

The SCANNER functionality of the dual port supports I/O control

functions, such as:

• synchronizing scans to the application

• forcing I/O

• discrete-input interrupts

• I/O module-driven interrupts (such as for the 1746-BAS module)

• I/O slot enables and disables

• I/O resets

In addition to providing access to the control SCANNER, the dual-port

memory also provides non-volatile storage for:

• I/O values

• application parameters (timers, counters, presets)

1747-UM001A-US-P - March 2000

Introducing the Open Controller 1-7

DOS API considerations

An application using the open controller DOS API on the 1747-OCE must

select an unused 8K byte memory window address and interrupt line for the

local I/O scanner. These values are passed to the API in the

OC_OpenScanner function call. For example, the following statement

would configure the memory window at C800:0000H, and select interrupt

request 11:

OC_OpenScanner(&Handle, 0xC800, 11)

When running on the 1747-OCF, the memory window and interrupt

parameters are ignored. The OC_OpenScanner function will first search the

PCI bus for the local I/O scanner, and the values that were allocated by the

BIOS are used. This allows you to use the same code for both open

controllers since any parameters entered for the 1747-OCE will simply be

ignored if you are using a 1747-OCF.

The open controller DOS API version 1.04 has been modified to support the

1747-OCF. The DOS API is a static library; therefore, any applications

developed with earlier versions (1.03 and earlier) of the DOS API will have

to be re-linked with the updated API in order to be used with the 1747-OCF.

Contact Rockwell Automation Technical Services for information about

updating your API software.

Windows NT API considerations

The open controller Windows NT API consists of two components:

• a device driver

• a DLL

The device driver is responsible for allocating the dual port register (DPR)

memory window and interrupt. The device driver searches the PCI bus for

the 1747-OCF scanner and uses the resources allocated by the BIOS.

The NT API functions are contained within a DLL. It is not necessary to

make any changes to or re-link existing 1747-OCE applications that will be

used on the 1747-OCF, unless unsupported API functions are used (see

Summary of API Differences later in this chapter). All that is required is

that the new device driver and DLL be installed (version 1.03 or later of the

NT API). Contact Rockwell Automation Technical Services for information

about updating your API software.

剩余125页未读，继续阅读

cnooctom

粉丝: 0
资源: 2

1747系列控制器比较与用户指南：1747-OCE vs 1747-OCF

1747-SN-ASB说明书

1747-SDN 模块ADR手册.pdf

AB用户手册.rar

Sphinx文档与用户手册编写经验分享

网络协议分析与抓包工具使用手册

优化数据决策流程：决策树可视化工具使用手册

Python图形化网络数据可视化：拓扑工具使用手册

Java Map高效使用手册：掌握最佳实践与性能优化技巧

怎样进行用户说明手册和使用手册的编写。

digsilent用户使用手册

启智 ros用户使用手册

uos 使用使用手册

怎样进行用户说明手册和使用手册的编写

nccloud使用手册

sum02b用户手册

ht7036用户手册

hive用户手册pdf

spyglass 2018 用户手册

rslogix5000用户手册

jaamsim用户手册翻译

最新资源