一块适合于DIY的廉价51串行编程器[套件供应]

通常学习单片机最有用的是编程器和仿真机,一台商品化的编程器至少要几百元,仿真机价格更高,往往让初学者难以选择。这里介绍的一款由德国的Peter Dannegger设计的51编程器,一推出就反响强烈,既能锻炼自己的动手能力,又能廉价地装备一台多用编程器,无论是学习单片机或业余时间搞开发,都是一个非常好的选     

单总线芯片编程器的设计与实现

本文简要介绍了编程器设计原理和DS2502芯片编程算法,重点讨论了DS2502量产型专用编程器的软硬件设计与实现方法。该编程器采用脱机编程工作方式,可单次编程最大10片DS2502,满足批量编程的设计需求。     

单总线芯片编程器的设计与实现

本文简要介绍了编程器设计原理和DS2502芯片编程算法,重点讨论了DS2502量产型专用编程器的软硬件设计与实现方法.该编程器采用脱机编程工作方式,可单次编程最大10片DS2502,满足批量编程的设计需求.     

手持编程器核心模块的研发

阐述了一种基于CAN总线技术的多任务手持编程器。重点描述了手持编程器核心模块的硬件结构和软件设计方法,建立手持编程器研发装置,实现远距离对PLC主机进行调试和监控,符合工业领域实际应用。     

简便易学的单片机开发系统PROG—100（三）

在讨论了PROG-100编程器的硬件结构和软件开发语言的特色之后,请读者跟随我们试一试如何使用PROG-100编程器开发一个单片机应用程序。您可以体会一下轻轻松松地进行单片机应用程序开发工作的乐趣。首先接通编程器电源。屏幕显示如下:     

“可编程序控制器及其应用”讲座 第九讲 编程器

本讲介绍的 P190编程器是 GOULD 公司的通用产品。P190编程器与584可编程序控制器相连接,主要用于为584组态、编程和监控。其它型号的可编程序控制器的编程器原理和方法都与此类似。     

DIY一台实用的51单片机编程器

学习单片机最常用是编程器和仿真机,一台商品化的编程器至少要几百元,仿真机价格更高,往往让初学者难以选择。这里介绍的一款国外电子网站推出的廉价51单片机编程器,能够可靠读写常用的14种51单片机,自己动手装配一台,无论是学习单片机或业余时间搞开发,都是一个非常好的选择。     

基于ARM7的PLC手持编程器通信接口设计

文章介绍了构成PLC手持编程器的主控处理器ARM7芯片S3C44BOX、CAN控制器MCP2510、CAN收发器TJAl050的基本结构及工作原理,设计了PLC手持编程器的具体通信电路.说明了S3C44BOX处理器的SIO功能;针对CAN控制器MCP2510,论述了其SPI接口指令以及时序的控制方法.重点阐述了手持编程器数据通信的软件设计方法.并实现了手持编程器与PLC之间数据的正确传输.     

“精通PIC单片机”实用技术讲座(九) PIC16F62X的性能和实验板电路——中断程序实例之一[套件供应]

本刊读者服务部产品供应信息中,刊出的V1.30实验PIC编程器(见页上的“精通PIC单片机”讲座学习套件及辅导材料)套件,除编程器外均附有相关的实验板。该套件售出后,已有多个读者打来电话,要求介绍配套的实验板电路,以便使用。 V1.30实验PIC编程器所配套的实验板电路比V1.01实验PIC编程器配套的实验板电路     

有保护功能的简易编程器

一、简介 本文介绍一种51单片机编程器，成本很低，适合初学者自己动手制作。目前国内诸多刊物上介绍各种简易编程器的文章不少，但都有一个致命的缺点：那就是都不具备电源保护功能，如果一旦不小心把单片机插反，就会对单片机或编程器及电脑串行接口带来损失，本文介绍的一种简易编程器具有自动断电保护功能，当单片机插反，保护电路会立刻切断电源（电源指示灯进入闪烁状态），既保护了单片机、编程器，也保护了计算机USB口，避免造成不必要的损失。它所支持的芯片型号如表1所示。     

Integrating program analyses with programmer productivity tools

Because software continues to grow in size and complexity, programmers increasingly rely on productivity tools to understand, debug, and modify their programs. These tools typically use program analyses to produce information for the programmer. This is problematic because it is based on the assumption that the programmer and program analyses all use the same vocabulary. If the programmer and analyses did not use the same vocabulary then the results of the analyses will be meaningless to the programmer. For example, ‘v124 may be NULL’ does not mean much to the programmer but ‘myStack may be NULL’ is meaningful. Often, the programmer and analyses prefer different vocabularies. While the programmer prefers his programs' source code, an analysis will prefer a simplified representation. Unfortunately, writing an analysis that works on the source code is difficult because the analysis must deal with the idiosyncracies of the source language (e.g. nested classes). In comparison, writing an analysis on SSA form is easy but the output of the analysis is not meaningful to the programmer; it must somehow be translated into something the programmer understands. We present a system, RTalk, that makes it easy to support both the programmers' and the analysis' needs. RTalk generates a translator between the programmers' and the analysis' vocabulary. Thus both the programmer and the analysis can use the vocabulary most natural to them. We demonstrate the effectiveness of RTalk by describing program understanding and program optimization tools that we have already built using RTalk. Copyright © 2011 John Wiley & Sons, Ltd.     

Program Complexity and Programmer Productivity

This paper proposes a measure of program control complexity from an information theory viewpoint. A set of empirical data showing programmer productivity as a function of program control complexity is also presented. The data reveals a step-function-like contour to programmer productivity with increasing program control complexity.     

A software tool for top-down programming

Top-down design and programming methods have become well established in both commercial and academic environments. However, a programmer using such methods faces a number of organizational difficulties. This paper describes a software tool, written in Pascal, which eliminates these difficulties. It allows a programmer to interactively develop programs in a top-down fashion.     

Guidelines for Determining When to Use GKS and When to Use PHIGS

GKS, GKS-3D, and PHIGS are all approved ISO standards for the application programmer interface. How does a system analyst or programmer decide which standard to use for his application? This paper discusses the range of application requirements likely to be encountered, explores the suitability of GKS and PHIGS for satisfying these requirements, and offers guidelines to aid in the decision process.     

M68HC08系列双排直插式MCU通用编程器设计

在分析比较M68HC08系列芯片进入监控状态不同条件的基础上，讨论了基于MC68HC908JB8芯片的通用编程器的硬件和软件设计思想，同时给出新型号芯片的加入方法。该通用编程器由基板和适配头两部分组成，具价格低廉、使用方便、易扩充等特点，且有一定的使用价值。     

Choosing a programming language

This paper evaluates the use of a functional language for implementing domain-specific functionality. The factors we consider when choosing a programming language are programmer productivity, maintainability, efficiency, portability, tool support, and software and hardware interfaces. The choice of programming language is a fine balancing act. Modern object-oriented languages such as Java and C# are more orthogonal and hide fewer surprises for the programmer, although the inevitable accumulation of features makes this statement less true with every new version of each language.     

A tutorial on Reed–Solomon coding for fault-tolerance in RAID-like systems

It is well-known that Reed-Solomon codes may be used to provide error correction for multiple failures in RAID-like systems. The coding technique itself, however, is not as well-known. To the coding theorist, this technique is a straightforward extension to a basic coding paradigm and needs no special mention. However, to the systems programmer with no training in coding theory, the technique may be a mystery. Currently, there are no references that describe how to perform this coding that do not assume that the reader is already well-versed in algebra and coding theory. This paper is intended for the systems programmer. It presents a complete specification of the coding algorithm plus details on how it may be implemented. This specification assumes no prior knowledge of algebra or coding theory. The goal of this paper is for a systems programmer to be able to implement Reed-Solomon coding for reliability in RAID-like systems without needing to consult any external references. © 1997 John Wiley & Sons, Ltd.