Summary of the content on the page No. 1
Serial and IR Automation Specifications and
Programming Guide
PRO
for iScan VP20, VP30, VP50 and VP50
Revised - December 2007
Summary of the content on the page No. 2
Document Contents 0 Preface......................................................................................................................... 3 0.1 Information Warranty Statement ........................................................................ 3 0.2 Document Scope and Limitations....................................................................... 4 0.3 Document Conventions....................................................................................... 4 0.3.1 Model
Summary of the content on the page No. 3
0 Preface Thank you for purchasing a DVDO iScan VP Series video processor. We believe xx the iScan will become a favorite device in your multimedia presentation system due to picture quality, ease of use, and the level of control the iScan gives you or your customer over the processed signal. This document is intended to cover the supplemental control PRO functionality that is available for the iScan VP20, VP30, VP50, and VP50 . 0.1 Information Warranty Statement The information p
Summary of the content on the page No. 4
0.2 Document Scope and Limitations This document will cover the necessary information required to construct and transmit a serial (RS-232) or Infrared (IR) control signal to a DVDO iScan VP model xx video processor. These two basic mediums of control, are intended to convey the intentions of the user or automation system into the processes that operate the iScan. This document will cover the naming conventions, syntax, electrical specifications, and some troubleshooting that may be req
Summary of the content on the page No. 5
0.3.2 Product Introduction This section is a brief introduction with pictures of each of the models of the iScan VP series – it is only intended as a brief “spotters guide” to iScan units. Please refer to xx your product’s user’s manual or our website for more in-depth product information at www.anchorbaytech.com/products/systems (replacement user’s manuals may be obtained in PDF form at the same website by clicking on the “support” tab and selecting “documentation”). If you are trying t
Summary of the content on the page No. 6
0.3.4 VP30 (MM603) iScan VP30 Front iScan VP30 Back This model is our high-end entry-level product with the full four HDMI complement, the RGBHV/Component 3 input and Analog video output – with available options like an SD-SDI input and the ABT102 Deinterlacing add-on card for exceptional reproduction of interlaced SD content. The VP30 also features more in-depth user controls and greater input flexibility, allowing it to be an excellent addition to a high-end home theater system,
Summary of the content on the page No. 7
PRO 0.3.6 VP50 (MM606) PRO iScan VP50 Front PRO iScan VP50 Back PRO The iScan VP50 is the first Video Processor to achieve the THX certification for Video Processors, setting the benchmark for video processing. This device is also the first HDMI 1.3 compatible video processor with the same outstanding Anchor Bay VRS HD and SD content processing algorithms of the preceding models, while adding even further configuration and calibration controls for ISF calibration and the new HD-SDI
Summary of the content on the page No. 8
0.4 How does automation work? The iScan line of DVDO brand video processors are designed to enable control and flexibility over various input and output signal configurations – as well as our proprietary algorithms to improve several aspects of video quality and enable new capabilities that legacy devices by themselves are not able to achieve. This product has many features (covered in the User’s Manual) which are intended to make day-to-day use of our video processing product easier in s
Summary of the content on the page No. 9
0.4.3 What is Binary? The digital world is all ones and zeros. By placing ones and zeros in a standardized pattern we can encode data that can be exchanged between multiple devices. The lowest level of encoding data is “binary notation”. In this notation, a “bit” represents the “true” or “false” presence of the numeric value at that bit location. Therefore, if the bit representing a “4” was “true”, one would add the “4” to the total of the “byte” (the total size of the number). For ou
Summary of the content on the page No. 10
As an example, using “65” again – the HEX equivalent is “41h”. So what’s the “h” at the end? There are two commonly accepted ways to identify HEX notation in a sentence (or “string”). One is with the use of a “0x00” notation, where the two last zeros represent the two HEX characters, or with “00h” showing that this is a two nybble-byte in HEX notation. This can get confusing the more you learn – so take a moment to highlight this section or put a Post-It flag on this page for future ref
Summary of the content on the page No. 11
0.5 A brief dialog about remote controlling a VPxx series video processor Please be honest with yourself and ensure that you have understood the previous sections. If you’re not confident about how binary = HEX = decimal and relates to ASCII, then you may want to check out the internet for more information on digital information technology – or contact our Technical Support Hotline at (U.S. Domestic) 1- 866-423-3836 extension 333, or (International) 1-408-395-4455 extension 333. Alternat
Summary of the content on the page No. 12
0.6 A dialog about input video memories Due to the number of inputs and different types of input formats and ever further numerous types of source devices, we at Anchor Bay added input memories, which allow the user/system-integrator to configure very specific “effects” for a specific input format on a specific input connection. This means that a single input can have many different settings within the same control – just based on the input format that it is receiving. PRO As an example
Summary of the content on the page No. 13
This page intentionally left blank 13
Summary of the content on the page No. 14
1 RS-232 Control 1.1 The RS-232 Physical Connection RS-232 connections come in several styles which are accepted in the consumer electronics industry. The most common is the 9-pin D-Subminiature connector found on the back of most computers, and is the one that we use on the iScan VP products. xx The female serial port, found on the back panel of an iScan VP video processor. xx In this interface, there are a few different signals which must be supported. These are (all pin numbers
Summary of the content on the page No. 15
1.1.1 The Anchor Bay RS-232 Protocol In this portion of the document, we will discus the three types of control communications that occur between the iScan and the controlling device. 1.1.2 A Dialog on Checksums Checksums are a way for a receiving device to double check the communication that occurred between the transmitting device and the receiver. In most systems, Checksums are not needed – however some installations absolutely require them (for example: industrial control or corporat
Summary of the content on the page No. 16
Also, each of the above “characters” has a related HEX notation number to go with it: “Attention” = Start Text or STX = 0x02 in HEX notation >>pause<< = Null or NUL = 0x00 in HEX notation “I’m Done Talking” = End Text or ETX = 0x03 in HEX notation It is up to the individual programmer to determine which method is easiest to understand – but if you haven’t chosen your programming style yet, this writer recommends sticking with HEX notation. One thing that should be avoided at all costs
Summary of the content on the page No. 17
Before we start listing Command ID bytes, lets look at the “this long” portion of our sentence. For this, count the two command ID bytes (count the bytes, don’t add the values!), add the count of the two NUL bytes (again, don’t add the values), add the count of the value bytes (this really should sink in now - don’t add the values themselves). This equals the “byte-count” for the command sentence (string) – we are always counting bytes. Below is an example of the bytes we want to count:
Summary of the content on the page No. 18
Let’s look at the sentence again, replacing what we know now: “0x02 0x33 0x30 0x30 0x35 0x41 0x31 0x00 0x31 0x00 [checksum – optional] 0x03” If you recall, unless your application calls for it specifically – YOU DO NOT NEED A CHECKSUM!!! If your application doesn’t need it, you are done with the sentence construction (just remove the optional placeholder for the “checksum - optional”): Let’s look at the sentence again, with out the optional checksum placeholder: “0x02 0x33 0x30 0x30 0
Summary of the content on the page No. 19
The checksum. This is the last part other than the Command ID Table and Value Table you might need to create a command string. Again, unless your customer/job requirements demand/specify it – YOU DO NOT NEED A CHECKSUM!! Assuming that you absolutely need to have a checksum due to a customer/job requirement, the checksum is fairly easy - add the value of every byte from the beginning of the string (at STX) to the last “NUL” just before the ETX (0x03). For the “Power On” command, this wo
Summary of the content on the page No. 20
1.2.1 Example RS-232 Command Packets This section contains the most commonly requested automation command-type strings (no checksums are provided): Power On 0x02 0x33 0x30 0x35 0x41 0x31 0x00 0x31 0x00 0x03 Off 0x02 0x33 0x30 0x35 0x41 0x31 0x00 0x30 0x00 0x03 Input Composite 1 0x02 0x33 0x30 0x35 0x41 0x43 0x00 0x31 0x00 0x03 Composite 1 0x02 0x33 0x30 0x35 0x41 0x43 0x00 0x32 0x00 0x03 S-Video 1 0x02 0x33 0x30 0x35 0x41 0x43 0x00 0x33 0x00 0x03 S-Video 2 0x02 0x33 0x30 0x35
