DOCSLIB.ORG

Magensa Qwickpin, Generation/Verification of PIN Offset

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Magensa Qwickpin, Generation/Verification of PIN Offset Magensa QwickPIN Generation/Verification of PIN Offset Programmer’s Reference Manual March 18, 2021 Document Number: D998200466-11 REGISTERED TO ISO 9001:2015 Magensa, LLC I 1710 Apollo Court I Seal Beach, CA 90740 I Phone: (562) 546-6400 I Technical Support: (888) 624-8350 www.magtek.com Copyright © 2006 - 2021 MagTek, Inc. Printed in the United States of America INFORMATION IN THIS PUBLICATION IS SUBJECT TO CHANGE WITHOUT NOTICE AND MAY CONTAIN TECHNICAL INACCURACIES OR GRAPHICAL DISCREPANCIES. CHANGES OR IMPROVEMENTS MADE TO THIS PRODUCT WILL BE UPDATED IN THE NEXT PUBLICATION RELEASE. NO PART OF THIS DOCUMENT MAY BE REPRODUCED OR TRANSMITTED IN ANY FORM OR BY ANY MEANS, ELECTRONIC OR MECHANICAL, FOR ANY PURPOSE, WITHOUT THE EXPRESS WRITTEN PERMISSION OF MAGTEK, INC. MagTek®, MagnePrint®, and MagneSafe® are registered trademarks of MagTek, Inc. Magensa™ is a trademark of MagTek, Inc. DynaPro™ and DynaPro Mini™, are trademarks of MagTek, Inc. ExpressCard 2000 is a trademark of MagTek, Inc. IPAD® is a trademark of MagTek, Inc. IntelliStripe® is a registered trademark of MagTek, Inc. AAMVA™ is a trademark of AAMVA. American Express® and EXPRESSPAY FROM AMERICAN EXPRESS® are registered trademarks of American Express Marketing & Development Corp. D-PAYMENT APPLICATION SPECIFICATION® is a registered trademark to Discover Financial Services CORPORATION MasterCard® is a registered trademark and PayPass™ and Tap & Go™ are trademarks of MasterCard International Incorporated. Visa® and Visa payWave® are registered trademarks of Visa International Service Association. MAS-CON® is a registered trademark of Pancon Corporation. Molex® is a registered trademark and PicoBlade™ is a trademark of Molex, its affiliates, related companies, licensors, and/or joint venture partners. ANSI®, the ANSI logo, and numerous other identifiers containing "ANSI" are registered trademarks, service marks, and accreditation marks of the American National Standards Institute (ANSI). ISO® is a registered trademark of the International Organization for Standardization. UL™ and the UL logo are trademarks of UL LLC. PCI Security Standards Council® is a registered trademark of the PCI Security Standards Council, LLC. EMV® is a registered trademark in the U.S. and other countries and an unregistered trademark elsewhere. The EMV trademark is owned by EMVCo, LLC. The Contactless Indicator mark, consisting of four graduating arcs, is a trademark owned by and used with permission of EMVCo, LLC. The Bluetooth® word mark and logos are registered trademarks owned by Bluetooth SIG, Inc. and any use of such marks by MagTek is under license. Google Play™ store, Google Wallet™ payment service, and Android™ platform are trademarks of Google Inc. Apple Pay®, iPhone®, iPod®, Mac®, and OS X® are registered trademarks of Apple Inc., registered in the U.S. and other countries. iPad™ is a trademark of Apple. Inc. App StoreSM is a service mark of Apple Inc., registered in the U.S. and other countries. IOS is a trademark or registered trademark of Cisco in the U.S. and other countries and is used by Apple Inc. under license. Microsoft®, Windows®, and .NET® are registered trademarks of Microsoft Corporation. All other system names and product names are the property of their respective owners. Magensa QwickPIN| Generation/Verification of PIN Offset | Programmer’s Reference Manual Page 2 of 23 (D998200466-11) Table 0-1 - Revisions Rev Number Date Notes Initial Release. This version of document is compatible with 10 March 2021 QwickPIN API version 1.2.0.1 11 March 2021 Data Magensa QwickPIN| Generation/Verification of PIN Offset | Programmer’s Reference Manual Page 3 of 23 (D998200466-11) 0 - Table of Contents Table of Contents Table of Contents .............................................................................................................................................. 4 1 Introduction ............................................................................................................................................... 5 2 QwickPIN Operations ............................................................................................................................... 7 2.1 /api/PINOffset/Generate ................................................................................................................ 7 2.1.1 INPUT PROPERTIES ................................................................................................................. 7 2.1.2 OUTPUT PROPERTIES .............................................................................................................. 7 2.2 /api/PINOffset/Verify ...................................................................................................................... 9 2.2.1 INPUT PROPERTIES ................................................................................................................. 9 2.2.2 OUTPUT PROPERTIES .............................................................................................................. 9 3 Error Codes and Reasons ...................................................................................................................... 11 3.1 Sample Error Response ................................................................................................................. 11 3.2 Error Codes and Reasons .............................................................................................................. 12 4 IP Whitelist............................................................................................................................................... 13 Appendix A PAN Data ................................................................................................................................. 14 Appendix B PIN Data .................................................................................................................................. 18 Appendix C Postman .................................................................................................................................. 20 Appendix D Glossary of Terms .................................................................................................................. 22 Appendix E References .............................................................................................................................. 23 Magensa QwickPIN| Generation/Verification of PIN Offset | Programmer’s Reference Manual Page 4 of 23 (D998200466-11) 1 - Introduction 1 Introduction The purpose of this document is to describe the main operations available in Magensa QwickPIN Web service and their required & optional input/output parameters. It also provides sample REST requests & responses as reference for client developers. It also includes error codes, reasons, and a sample error response. QwickPIN Web service enables clients to easily generate & verify the PIN Offset via Basic Authentication if required fields are inputted correctly. QwickPIN Web Service has IP Whitelist feature so it will check for specific IP addresses and rejects any incoming data that does not originate from one of the authorized IP addresses. Please refer to chapter 4 for more detail information. QwickPIN Web service end point provides swagger documentation and swagger.json which can be imported to Postman program. Please refer to Appendix C for how to import swagger.json to Postman. This service comprises of two APIs, one is for generation of PIN Offset and the other one is for verification of PIN Offset. The input format for Verification API is the same as Generation API with an extra input for “RefPINOffset” which will be used for verification process. RefPINOffset is a required field with QwickPIN API ver 1.2.0.1. Depending on PAN Data Type, the format of PAN Data will be different. PAN Data Type can be one of the following: • MagtekARQC • MagTekTrack2Encrypted • DukptPAN MagTekARQC is the ARQC data in TLV format generated from MagTek Reader (EMV dip or Fallback MSR Swipe). MagTekTrack2Encrypted is the regular MSR Swipe where Encrypted Track2 and MSR KSN are available. TokenV2 can be used to encrypt track2 for this option. Please refer to Appendix A for how to encrypt track2 with TokenV2 service. DUKPT PAN is a value where a client will encrypt the data (concatenated values of PAN, Exp Date and Service Code) under DUKPT. Exp Date and Service Code, however, are not required for generating/verifying PINOffset. To know more about building PAN Data, please refer to Appendix A in this document. Each decrypted PAN can be validated by Luhn Algorithm or Modulus 10 algorithm in BIN level. It’s up to clients for enabling/disabling it. If clients have multiple BINs, each BIN has Luhn Check option separately. Input parameter RefID allows a customer to provide a reference ID to link its financial system to Magensa service. It can be a GUID or any other information a customer wants to use. Input parameter PIN DataType is used for PIN block format. Although the most common PIN Block encoding format is ISO_0 type, QwickPIN supports ISO 0, ISO 1, ISO 2, and ISO 3. For PIN Data, Magensa currently supports 4-digit PIN that is enclosed in the Encrypted PIN Block. PIN Block needs to be encrypted under DUKPT key with pin variant. Conditionally, PIN Data requires a json string which contains both EPB and KSN. PIN Data can also be obtained from TokenV2 when plain PIN block is sent to TokenV2 for encryption. Please refer to Appendix B for how to build plain PIN block and to obtain Encrypted PINBlock. Magensa QwickPIN|
Load more

Recommended publications
  • Government Open Systems Interconnection Profile Users' Guide, Version 2
    NIST Special Publication 500-192 [ Computer Systems Government Open Systems Technology Interconnection Profile Users' U.S. DEPARTMENT OF COMMERCE National Institute of Guide, Version 2 Standards and Technology Tim Boland Nisr NATL INST. OF STAND & TECH R.I.C, A111D3 71D7S1 NIST PUBLICATIONS --QC- 100 .U57 500-192 1991 C.2 NIST Special Publication 500-192 . 0)0 Government Open Systems Interconnection Profile Users' Guide, Version 2 Tim Boland Computer Systems Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899 Supersedes NIST Special Publication 500-163 October 1991 U.S. DEPARTMENT OF COMMERCE Robert A. Mosbacher, Secretary NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY John W. Lyons, Director Reports on Computer Systems Technology The National Institute of Standards and Technology (NIST) has a unique responsibility for conriputer systems technology within the Federal government. NIST's Computer Systems Laboratory (CSL) devel- ops standards and guidelines, provides technical assistance, and conducts research for computers and related telecommunications systems to achieve more effective utilization of Federal information technol- ogy resources. CSL's responsibilities include development of technical, management, physical, and ad- ministrative standards and guidelines for the cost-effective security and privacy of sensitive unclassified information processed in Federal computers. CSL assists agencies in developing security plans and in improving computer security awareness training. This Special Publication 500 series reports CSL re- search and guidelines to Federal agencies as well as to organizations in industry, government, and academia. National Institute of Standards and Technology Special Publication 500-192 Natl. Inst. Stand. Technol. Spec. Publ. 500-192, 166 pages (Oct. 1991) CODEN: NSPUE2 U.S.
    [Show full text]
  • Package 'Passport'
    Package ‘passport’ November 7, 2020 Type Package Title Travel Smoothly Between Country Name and Code Formats Version 0.3.0 Description Smooths the process of working with country names and codes via powerful parsing, standardization, and conversion utilities arranged in a simple, consistent API. Country name formats include multiple sources including the Unicode Common Locale Data Repository (CLDR, <http://cldr.unicode.org/>) common-sense standardized names in hundreds of languages. Depends R (>= 3.1.0) Imports stats, utils Suggests covr, dplyr, DT, gapminder, ggplot2, jsonlite, knitr, mockr, rmarkdown, testthat, tidyr License GPL-3 | file LICENSE URL https://github.com/alistaire47/passport, https://alistaire47.github.io/passport/ BugReports https://github.com/alistaire47/passport/issues Encoding UTF-8 LazyData true RoxygenNote 7.1.1 VignetteBuilder knitr NeedsCompilation no Author Edward Visel [aut, cre] (<https://orcid.org/0000-0002-2811-6254>) Maintainer Edward Visel <[email protected]> Repository CRAN Date/Publication 2020-11-07 07:30:03 UTC 1 2 as_country_code R topics documented: as_country_code . .2 as_country_name . .3 codes . .5 country_format . .6 nato .............................................7 order_countries . .8 parse_country . 10 Index 12 as_country_code Convert standardized country names to country codes Description as_country_code converts a vector of standardized country names or codes to country codes Usage as_country_code(x, from, to = "iso2c", factor = is.factor(x)) Arguments x A character, factor, or numeric vector of country names or codes from Format from which to convert. See Details for more options. to Code format to which to convert. Defaults to "iso2c"; see codes for more options. factor If TRUE, returns factor instead of character vector. Details as_country_code takes a character, factor, or numeric vector of country names or codes to translate into the specified code format.
    [Show full text]
  • ISO Types 1-6: Construction Code Descriptions
    ISO Types 1-6: Construction Code Descriptions ISO 1 – Frame (combustible walls and/or roof) Typically RMS Class 1 Wood frame walls, floors, and roof deck Brick Veneer, wood/hardiplank siding, stucco cladding Wood frame roof with wood decking and typical roof covers below: *Shingles *Clay/concrete tiles *BUR (built up roof with gravel or modified bitumen) *Single-ply membrane *Less Likely metal sheathing covering *May be gable, hip, flat or combination of geometries Roof anchorage *Toe nailed *Clips *Single Wraps *Double Wraps Examples: Primarily Habitational, max 3-4 stories ISO 2 – Joisted Masonry (JM) (noncombustible masonry walls with wood frame roof) Typically RMS Class 2 Concrete block, masonry, or reinforced masonry load bearing exterior walls *if reported as CB walls only, verify if wood frame (ISO 2) or steel/noncombustible frame roof (ISO 4) *verify if wood frame walls (Frame ISO 1) or wood framing in roof only (JM ISO 2) Stucco, brick veneer, painted CB, or EIFS exterior cladding Floors in multi-story buildings are wood framed/wood deck or can be concrete on wood or steel deck. Wood frame roof with wood decking and typical roof covers below: *Shingles *Clay/concrete tiles *BUR (built up roof with gravel or modified bitumen) *Single-ply membrane *Less Likely metal sheathing covering *May be gable, hip, flat or combination of geometries Roof anchorage *Toe nailed *Clips *Single Wraps *Double Wraps Examples: Primarily Habitational, small office/retail, max 3-4 stories If “tunnel form” construction meaning there is a concrete deck above the top floor ceiling with wood frame roof over the top concrete deck, this will react to wind forces much the same way as typical JM construction.
    [Show full text]
  • ADA Adoption Handbook: a Program Manager's Guide, Version
    Technical Report CMU/SEI-92-TR-029 ESC-TR-92-029 Ada Adoption Handbook: A Program Manager's Guide Version 2.0 William E. Hefley John T. Foreman Charles B. Engle, Jr. John B. Goodenough October 1992 Technical Report CMU/SEI-92-TR-029 ESC-TR-92-029 October 1992 Ada Adoption Handbook: A Program Manager's Guide Version 2.0 AB William E. Hefley SEI Services John T. Foreman Defense Advanced Research Projects Agency Charles B. Engle, Jr. Florida Institute of Technology John B. Goodenough Real-Time Systems Program Unlimited distribution subject to the copyright. Software Engineering Institute Carnegie Mellon University Pittsburgh, Pennsylvania 15213 This report was prepared for the SEI Joint Program Office HQ ESC/AXS 5 Eglin Street Hanscom AFB, MA 01731-2116 The ideas and findings in this report should not be construed as an official DoD position. It ispublished in the interest of scientific and technical information exchange. FOR THE COMMANDER (signature on file) Thomas R. Miller, Lt Col, USAF SEI Joint Program Office This work is sponsored by the U.S. Department of Defense. Copyright© 1992 by Carnegie Mellon University. Permission to reproduce this document and to prepare derivative works from this document for internal use is granted, provided the copyright and “No Warranty” statements are included with all reproductions and derivative works. Requests for permission to reproduce this document or to prepare derivative works of this document for external and commercial use should be addressed to the SEI Licensing Agent. NO WARRANTY THIS CARNEGIE MELLON UNIVERSITY AND SOFTWARE ENGINEERING INSTITUTE MATERIAL IS FURNISHED ON AN “AS-IS” BASIS.
    [Show full text]
  • April/May 2006 U.S
    Language | Technology | Business Industry Focus: Mobile Applications Embedded multilingual mobile applications Mobile applications for the Arabic market Chinese input on mobile devices Multilingual handwriting recognition technology Search engine marketing in multiple languages Open source: a model for innovation April/May 2006 U.S. $7.95 Canada $9.95 Getting Started Guide: Content Management 01 Cover #79 LW331-7.indd 1 4/10/06 8:02:59 AM 02-03 ads.indd 2 4/10/06 7:38:35 AM 0ODFVQPOBUJNFy -BOHVBHFTPGUXBSFXBTTMPXBOEEJTDPOOFDUFE 1FPQMFIBEUPQBZZFBSBGUFSZFBSGPSPMEUFDIOPMPHZ 5IFO-JPOCSJEHFPQFOFE'SFFXBZ /PX5.T HMPTTBSJFT BOESFQPSUTBSFBDDFTTFE UISPVHIUIF8FC"OEDMJFOUT 1.T BOEUSBOTMBUPST DPMMBCPSBUFJOTUBOUMZ 8IFSFXJMM'SFFXBZUBLFZPV 'BTU $POOFDUFE 'SFF XXX(FU0O5IF'SFFXBZDPN LB ad MLC free 31306 indd 1 3/17/06 1:19 PM 02-03 ads.indd 3 4/10/06 7:38:49 AM MultiLingual #79 Volume 17 Issue 3 April/May 2006 Editor-in-Chief, Publisher: Donna Parrish Managing Editor: Laurel Wagers IN THE GLOBAL MARKETPLACE, Translation Dept. Editor: Jim Healey Copy Editor: Cecilia Spence News: Kendra Gray, Becky Bennett Illustrator: Doug Jones Production: Sandy Compton Webmaster: Aric Spence Assistant: Shannon Abromeit Advertising Director: Jennifer Del Carlo Advertising: Kevin Watson, Bonnie Merrell Editorial Board Jeff Allen, Henri Broekmate, Bill Hall, Andres Heuberger, Chris Langewis, Ken Lunde, John O’Conner, Mandy Pet, Reinhard Schäler Advertising [email protected] www.multilingual.com/advertising 208-263-8178 Subscriptions, back issues, customer service [email protected] www.multilingual.com/subscribe With business moving at lightning speed, you need Submissions, letters the expertise of a partner experienced at navigating the [email protected] evolving global landscape. Our three decades of quality- Editorial guidelines are available at focused, advanced solutions have resulted in long-standing www.multilingual.com/editorialWriter client relationships.
    [Show full text]
  • IGOSS-Industry/Government Open Systems Specification
    NIST Special Publication 500-217 Computer Systems IGOSS-Industry/Government Technology Open Systems Specification U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Gerard Mulvenna, Editor Standards and Technology NIST RESEARCH INFORMATION NAT-L INST. OF STAND & TECH R.I.C. MAR 2 6 1996 "'^ NIST PUBLICATIONS CENTER QC 100 .U57 iO. 500-217 994 7he National Institute of Standards and Technology was established in 1988 by Congress to "assist industry in the development of technology . needed to improve product quality, to modernize manufacturing processes, to ensure product reliability . and to facilitate rapid commercialization ... of products based on new scientific discoveries." NIST, originally founded as the National Bureau of Standards in 1901, works to strengthen U.S. industry's competitiveness; advance science and engineering; and improve public health, safety, and the environment. One of the agency's basic functions is to develop, maintain, and retain custody of the national standards of measurement, and provide the means and methods for comparing standards used in science, engineering, manufacturing, commerce, industry, and education with the standards adopted or recognized by the Federal Government. As an agency of the U.S. Commerce Department's Technology Administration, NIST conducts basic and applied research in the physical sciences and engineering and performs related services. The Institute does generic and precompetitive work on new and advanced technologies. NIST's research facilities are located
    [Show full text]
  • Download Guide
    Informatica® Big Data Quality 10.2.2 Content Guide Informatica Big Data Quality Content Guide 10.2.2 February 2019 © Copyright Informatica LLC 1998, 2019 This software and documentation are provided only under a separate license agreement containing restrictions on use and disclosure. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica LLC. U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation is subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License. Informatica and the Informatica logo are trademarks or registered trademarks of Informatica LLC in the United States and many jurisdictions throughout the world. A current list of Informatica trademarks is available on the web at https://www.informatica.com/trademarks.html. Other company and product names may be trade names or trademarks of their respective owners. Portions of this software and/or documentation are subject to copyright held by third parties. Required third party notices are included with the product. The information in this documentation is subject to change without notice. If you find any problems in this documentation, report them to us at [email protected].
    [Show full text]
  • Business Requirements Document DATA SYNCHRONIZATION DATA MODEL for TRADE ITEM (DATA DEFINITION)
    Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM (DATA DEFINITION) 1 2 Business Requirements Group 3 (BRG) 4 5 Business Requirement 6 Document For 7 8 Data Synchronization Data Model 9 for Trade Item 10 (Data Definition) 11 12 13 14 Version 7.7.1 15 16 May 24, 2005 17 18 COPYRIGHT 2005, GS1™ Version 7.7.1 Page 0 of 195 Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM (DATA DEFINITION) 19 20 DOCUMENT HISTORY 21 22 Document Number: 7.7.1 Document Version: 7.7.1 Document Issue Date May 23, 2005 23 24 Document Summary Document Title EAN•UCC – Business Requirements Document For Data Synchronization Data Model for Trade Item – (Data Definition) Owner Align Data BRG Grant Kille - Co-Chair -Julia Holden – Vice Chair Vic Hansen –Co-Chair-Olivier Mouton –Vice Chair UCC - [email protected] UCC – [email protected] Status For ITRGapproval – BRG Approved 25 26 Document Change History Log Date of Change Version Reason for Summary of Change CCR # Change February 17, 2001 X.0 Messaging Documentation to support the XXXXX Architecture Core Item Business Process and to reflect the UCC UML methodology standards February 28, 2001 2.0.1 Common Data Item Edited the Common data item Rpt report. April 27, 2001 2.0.4 Added the Item Item Containment is described Containment and has models but no attribute lists May 8, 2001 3.1 Comments at Vote Approved BRD with the title of “Core Item & Extension of Relationship Dependent Data to Enable Trade” (This document input to approved July 2001 Business Message Standard – Simpl eb) June 5, 2001 4.1 Meeting in Orlando See section 4.4 Change 01-000009 Summary that was documented on change request 01-000009 May 9, 2002 5.0 UCC work group BRD format was upgraded to 01-000011 meeting and GSMP standards.
    [Show full text]
  • MACHINE SAFETY EXPERTISE for PNEUMATICS Machine Safety for PNEUMATICS IT’S THAT EASY
    MACHINE SAFETY EXPERTISE FOR PNEUMATICS Machine Safety for PNEUMATICS IT’S THAT EASY AV03/AV05 with AES Dual valve IS12-PD SV07 LU6 AS3-SV Duško Marković, Technical Support Applications AVENTICS MACHINE SAFETY Introduction | Machine safety 3 Introduction Protecting people, machines, animals, and property is the primary objective of safety-related pneumatics systems and components. For all production machinery, standards and regulations define measures to prevent accidents through safe machine design. This guide covers key topics in the implementation of relevant directives and standards for safety-related pneumatics using examples, circuit diagrams, and products. Every workplace accident that happens on a machine is one too many. With its focus on safe products and solutions, AVENTICS makes an important contribution to improving machine safety. 3 Introduction AVENTICS has extensive, long-term experience in designing pneumatic controls. Pneumatics can be used to implement 4 Basic conditions a number of technical preventive measures, such as ensuring a limited, safe speed, reducing pressure and force, safely 25 AVENTICS expertise releasing energy, and guaranteeing a safe direction of travel or blocking a movement. We advise on all matters of machine 44 Product overview with service life ratings safety for pneumatic controls and offer comprehensive service to help you develop and achieve a sound safety concept. We 52 Glossary supply the right products and the required documentation. 55 Contact Your advantages with AVENTICS W Proven expertise thanks to many years of experience in equipping machines and systems in line with standards W Products including complete documentation with reliability ratings (B10/MTTF values) W Free access to IFA-rated switching examples on our website W Safety-related pneumatic components in certified quality 4 Machine safety | Basic conditions Directives and standards The European Machinery Directive 2006/42/EC on machine engineering aims to ensure a common safety level for new machines distributed and operated in the member states.
    [Show full text]
  • 3-D Graphics / AI Theory Three-Dimensional Graphics, Part 1 Page 8 Earl Hinrichs Uses High Performance Graphics IC to Create and Display Depth
    No. 41 May/June 1988 $3.95 THE MICRO TECHNICAL JOURNAL 3-D Graphics / AI Theory Three-Dimensional Graphics, Part 1 page 8 Earl Hinrichs uses high performance graphics IC to create and display depth. Neural Networks page 16 Modeling human reasoning is the first step in creating a useful robot. The Logic Of Programming Languages page 22 Proving that a language is logically valid beats testing it for 10 years. Applying Information Theory page 42 Calculating the maximum theoretical data compression and then applying it. Plus: Updating The C Reviews page 48 RS-232 Interfacing page 30 Button's Great Share", page 58 MarketiJ , H' ..of AndMuc Mu II 11 •• 1 .. 1.1 11111.111 III II I " VERY HIGH RESOLUTION The PC Tech COLOR and MONOCHROME video processor boards employ the TMS 34010 high performance graphics co·processor to insure the best possible video performance at reasonable prices. Color 34010 Video Processor: • Featured on the cover of Micro Cornucopia. • From 800 x 512 through 1024 x 800 resolution (depending on monitor and configuration). • 8 Bits per pixel for 256 simultaneous colors • Hardware support for CGA/MDA emulation. • PC, XT, and AT compatible The PC Tech Color 34010 video processor is a superior 34010 native code and DGIS development tool. We support up to 4 megabytes of program (non-display) 34010 RAM as well as up to 76aK bytes of display RAM. Compare our architecture and prices to any other intelligent graphics board. Then choose the PC Tech Color 34010 Video Processor for your development engine and your production requirements as well.
    [Show full text]
  • Machine Safety Guide | AVENTICS
    Your Guide for Machine Safety Pneumatic solutions conform ISO 13849 Reduce safety risks for your employees and improve the productivity of your machinery. Optimized machine safety with Emerson To prevent accidents at work, companies have to protect themselves against safety risks. But meeting required safety standards can present a real challenge. Emerson’s ASCO and AVENTICS products and solutions for fluid control & pneumatics make an important contribution to improving machine safety. We have extensive, long-term experience in designing pneumatic controls. Pneumatics can realize technical safety measures and is critical in industries using machines with horizontal or vertical motions especially. Protecting people, machines, animals, the environment, and property is the top priority, best achieved using safety-related solutions for fluid control and pneumatics. 3 Introduction 32 AV valve system 4 Directives and standards with AES fieldbus system 5 Hazards and risks: 34 503 Zone Safety Valve system Estimate – assess – eliminate 36 Series AS air preparation units 6 Towards safe machinery: 38 Series 65X Series Redundant Risk assessment safe exhaust Valve 8 Risk assessment: Risk analysis 40 Safety at maximum level 10 Risk analysis: identifying hazards 42 Series SV01/-03/-05 safety valves 11 Risk analysis: 44 Series ISO valve IS12 Risk estimation –Performance level 46 Series LU6 12 Risk assessment: Risk evaluation 48 Analog distance measuring sensors 14 Implementing a safety function – your go-to guide! 50 SISTEMA, the software assistant
    [Show full text]
  • Getty Vocabularies: LOD AAT Semantic Representation Version: 1.2 Last Updated: March 18, 2014
    Getty Vocabularies: LOD AAT Semantic Representation Version: 1.2 Last updated: March 18, 2014 Table of Contents 1 Introduction ........................................................................................................................................................... 3 1.1 The Getty Vocabularies and LOD ................................................................................................................ 3 1.1.1 About the AAT .................................................................................................................................... 3 1.2 Revisions, Review, Feedback ....................................................................................................................... 4 1.2.1 Revisions ............................................................................................................................................. 4 1.2.2 External Review Process ..................................................................................................................... 4 1.2.3 Providing Feedback ............................................................................................................................. 4 1.2.4 Disclaimer ........................................................................................................................................... 4 1.3 Abbreviations ............................................................................................................................................... 5 1.4 RDF Turtle ..................................................................................................................................................
    [Show full text]