没有合适的资源?快使用搜索试试~ 我知道了~
首页1747系列控制器比较与用户指南:1747-OCE vs 1747-OCF
1747系列控制器比较与用户指南:1747-OCE vs 1747-OCF
需积分: 9 1 下载量 127 浏览量
更新于2024-07-21
收藏 1.96MB PDF 举报
本资源是关于Allen-Bradley 1747系列开放控制器的手册,主要关注1747-OCE和1747-OCF两种型号。该手册旨在帮助用户了解和比较这两种控制器的功能、特性和使用方法,特别是利用1747-OCF的BIOS功能。手册强调了重要用户信息,由于产品的多样性和广泛的应用场景,使用者必须确保在实际应用过程中满足所有性能和安全要求,包括相关法律、法规、代码以及标准。 手册中包含了丰富的示例和图表,这些都是为了展示可能的解决方案和操作方法,但需注意的是,由于每项安装都有其特定的变量和要求,Allen-Bradley并不对基于手册示例的实际应用承担任何责任或法律责任,包括知识产权责任。这表明用户在参考手册时,应结合自身的具体环境和需求进行判断,必要时寻求专业指导。 对于固态控制器(如1747系列)与传统电磁设备之间的区别,SGI-1.1版的安全指南提供了更深入的阐述,该指南可在本地Allen-Bradley办事处获取,它将帮助用户理解固态控制技术的特性和安装维护中的注意事项,以确保安全有效的工作流程。 这份1747用户手册不仅提供了技术性的指导,还强调了用户责任和潜在风险,鼓励用户在使用前充分评估并采取适当的预防措施。对于那些从事工业自动化和控制系统设计、安装和维护的工程师和技术人员来说,这是一个不可或缺的参考资料。
资源详情
资源推荐
![](https://csdnimg.cn/release/download_crawler_static/9350035/bg10.jpg)
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)
![](https://csdnimg.cn/release/download_crawler_static/9350035/bg11.jpg)
1747-UM001A-US-P - March 2000
Introducing the Open Controller 1-5
Communicating with the Open
Controller
Your CONTROLLER application software communicates with the
SCANNER to control I/O by reading and writing to the dual-port registers.
Your application can access the dual-port registers using:
• the function calls in the open controller API (application program
interface) to access dual-port registers
Choose 1747-OCAPID for DOS or 1747-OCAPINT for Windows NT
• a software package, such as SoftLogix 5 or Controlware, that have
built-in drivers that access the open controller dual-port registers
• the drivers you develop
The dual-port documentation is available through the A-B technology
licensing program. For more information, contact Rockwell Automation
Technical Services.
Using the API software
The APIs (1747-OCAPID for DOS and 1747-OCAPINT for Windows NT)
provide libraries of C function calls for interfacing with the open controller
dual-port memory. Each library provides calls for typical control functions,
such as:
• configure I/O files
• initialize the SCANNER
• define user LEDs, 3-position switch, 2-position jumper, and external
watchdog
• read CONTROLLER status
• read/write input/output data
• enable/disable forces
The APIs support Microsoft and Borland C compilers in the DOS and
Windows NT environments. The DOS API is compiled as a 16-bit
MS-DOS library using the 80386 instruction set. The Windows NT API is a
standard 32-bit DLL.
![](https://csdnimg.cn/release/download_crawler_static/9350035/bg12.jpg)
1747-UM001A-US-P - March 2000
1-6 Introducing the Open Controller
Compatibility Issues
The 1747-OCE and 1747-OCF are compatible with Allen-Bradley 1746
chassis, I/O and power supplies, as well as existing open controller optional
modules and application code, except as noted in this section.
This section describes the major functional differences between the
1747-OCE and the 1747-OCF. The main focus is on differences that may
affect software developers, primarily as it relates to accessing the local I/O
scanner.
Open controller PCI-based option modules
All open controller option modules are compatible with the 1747-OCE and
the 1747-OCF, expect as noted in the following table:
Resource allocation
The open controller CPU interfaces with the local I/O scanner through an
8K byte dual port RAM and an interrupt request line. The most significant
difference between the two open controllers is how these resources are
mapped into the system.
On the 1747-OCE, the local I/O scanner interface is ISA-bus based which
requires you to configure the memory window and interrupt through
software.
The 1747-OCF scanner uses the PCI bus. The memory window and
interrupt are allocated by the system BIOS at system startup.
This revision level Of this option module
Is compatible with
this open controller
ALL rev. levels A-B Communications Module
cat. no. 1747-OCKTX/D
1747-OCE
Rev. D01 and above only A-B Communications Module
cat. no. 1747-OCKTX/D
1747-OCF
![](https://csdnimg.cn/release/download_crawler_static/9350035/bg13.jpg)
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.
![](https://csdnimg.cn/release/download_crawler_static/9350035/bg14.jpg)
1747-UM001A-US-P - March 2000
1-8 Introducing the Open Controller
Software not using the APIs
Software that does not use the open controller APIs must be modified to
find the 1747-OCF scanner and retrieve the assigned resources. Sample
code that performs this function is available upon request from Rockwell
Automation Technical Services.
Hardware differences
The following features of the 1747-OCE are either not present on the
1747-OCF, or are implemented differently.
Battery backup of dual-port memory
The dual-port memory is battery backed on the 1747-OCE. It is not battery
backed on the 1747-OCF.
Scanner reset
The controller CPU has the ability to reset the local I/O scanner. This
function is implemented differently in hardware on the 1747-OCF than on
the 1747-OCE. The difference is transparent to users of the DOS or NT
APIs. Software not using the APIs (or NT device driver) must be modified.
Sample code which performs this function is available upon request from
Rockwell Automation Technical Services.
Real-time clock SRAM
The 1747-OCE includes 4K bytes of static RAM within the real-time clock.
This SRAM is not available on the 1747-OCF.
The following API functions will return an error if used with the 1747-OCF:
OC_ReadRtcSRAM
OC_WriteRtcSRAM
Static RAM
The 1747-OCF includes 512K bytes of battery-backed static RAM. This
SRAM is not available on the 1747-OCE.
The following NT API functions are available for the 1747-OCF only, and
will return an error if used with the 1747-OCE:
Important: You must write the output image data into the dual-port register
before changing your open controller to scan mode. We
recommend that you do this for both the 1747-OCE and the
1747-OCF
剩余125页未读,继续阅读
![-](https://csdnimg.cn/download_wenku/file_type_column_c1.png)
![-](https://csdnimg.cn/download_wenku/file_type_column_c1.png)
![-](https://csdnimg.cn/download_wenku/file_type_column_c1.png)
![-](https://csdnimg.cn/download_wenku/file_type_column_c1.png)
![-](https://csdnimg.cn/download_wenku/file_type_column_c1.png)
![](https://csdnimg.cn/download_wenku/file_type_ask_c1.png)
![](https://csdnimg.cn/download_wenku/file_type_ask_c1.png)
![](https://csdnimg.cn/download_wenku/file_type_ask_c1.png)
![](https://csdnimg.cn/download_wenku/file_type_ask_c1.png)
![](https://csdnimg.cn/download_wenku/file_type_ask_c1.png)
![](https://csdnimg.cn/download_wenku/file_type_ask_c1.png)
![](https://csdnimg.cn/download_wenku/file_type_ask_c1.png)
![](https://csdnimg.cn/download_wenku/file_type_ask_c1.png)
![](https://csdnimg.cn/download_wenku/file_type_ask_c1.png)
![](https://csdnimg.cn/download_wenku/file_type_ask_c1.png)
![](https://csdnimg.cn/download_wenku/file_type_ask_c1.png)
![](https://profile-avatar.csdnimg.cn/default.jpg!1)
cnooctom
- 粉丝: 0
- 资源: 2
上传资源 快速赚钱
我的内容管理 展开
我的资源 快来上传第一个资源
我的收益
登录查看自己的收益我的积分 登录查看自己的积分
我的C币 登录后查看C币余额
我的收藏
我的下载
下载帮助
![](https://csdnimg.cn/release/wenkucmsfe/public/img/voice.245cc511.png)
最新资源
- 解决Eclipse配置与导入Java工程常见问题
- 真空发生器:工作原理与抽吸性能分析
- 爱立信RBS6201开站流程详解
- 电脑开机声音解析:故障诊断指南
- JAVA实现贪吃蛇游戏
- 模糊神经网络实现与自学习能力探索
- PID型模糊神经网络控制器设计与学习算法
- 模糊神经网络在自适应PID控制器中的应用
- C++实现的学生成绩管理系统设计
- 802.1D STP 实现与优化:二层交换机中的生成树协议
- 解决Windows无法完成SD卡格式化的九种方法
- 软件测试方法:Beta与Alpha测试详解
- 软件测试周期详解:从需求分析到维护测试
- CMMI模型详解:软件企业能力提升的关键
- 移动Web开发框架选择:jQueryMobile、jQTouch、SenchaTouch对比
- Java程序设计试题与复习指南
资源上传下载、课程学习等过程中有任何疑问或建议,欢迎提出宝贵意见哦~我们会及时处理!
点击此处反馈
![](https://img-home.csdnimg.cn/images/20220527035711.png)
![](https://img-home.csdnimg.cn/images/20220527035711.png)
![](https://img-home.csdnimg.cn/images/20220527035111.png)
安全验证
文档复制为VIP权益,开通VIP直接复制
![](https://csdnimg.cn/release/wenkucmsfe/public/img/green-success.6a4acb44.png)