Mvi94 BSCH User Manual

MVI94-BSCH
FLEX I/O Platform Bosch Communication I/O Module
User Manual
May 09, 2007
Please Read This Notice

Successful application of this module requires a reasonable working knowledge of the Rockwell Automation FLEX I/O hardware, the MVI94-BSCH Module and the application in which the combination is to be used. For this reason, it is important that those responsible for implementation satisfy themselves that the combination will meet the needs of the application without exposing personnel or equipment to unsafe or inappropriate working conditions. This manual is provided to assist the user. Every attempt has been made to assure that the information provided is accurate and a true reflection of the product's installation requirements. In order to assure a complete understanding of the operation of the product, the user should read all applicable Rockwell Automation documentation on the operation of the Rockwell Automation hardware. Under no conditions will ProSoft Technology be responsible or liable for indirect or consequential damages resulting from the use or application of the product. Reproduction of the contents of this manual, in whole or in part, without written permission from ProSoft Technology is prohibited. Information in this manual is subject to change without notice and does not represent a commitment on the part of ProSoft Technology Improvements and/or changes in this manual or the product may be made at any time. These changes will be made periodically to correct technical inaccuracies or typographical errors.
Your Feedback Please

We always want you to feel that you made the right decision to use our products. If you have suggestions, comments, compliments or complaints about the product, documentation or support, please write or call us. ProSoft Technology 1675 Chester Avenue, Fourth Floor Bakersfield, CA 93301 +1 (661) 716-5100 +1 (661) 716-5101 (Fax) http://www.prosoft-technology.com Copyright ProSoft Technology, Inc. 2000 - 2007. All Rights Reserved. MVI94-BSCH User Manual May 09, 2007 PSFT.BSCH.MVI94.UM.07.05.09 ProSoft Technology , ProLinx , inRAx , ProTalk and RadioLinx are Registered Trademarks of ProSoft Technology, Inc.
Contents
MVI94-BSCH FLEX I/O Platform Bosch Communication I/O Module
Contents
PLEASE READ THIS NOTICE...........................................................................................................2 Your Feedback Please ..................................................................................................................2 1 2 QUICK START ............................................................................................................................5 HARDWARE INSTALLATION ....................................................................................................7 2.1 Verify Package Contents ..............................................................................................7 Mounting the MVI 94 Flex I/O Base..............................................................................................8 Setting Jumpers ............................................................................................................................9 Installing the Module onto the Base..........................................................................................11 Installing the Serial Adapter Cables ..........................................................................................12 2.2 Wiring the Power Connections ..................................................................................12 CONFIGURATION.....................................................................................................................13 3.1 Bosch Master ...............................................................................................................14 3.2 Commands ...................................................................................................................16 3.2.1 Enable Code ................................................................................................................17 3.2.2 Internal Address...........................................................................................................17 3.2.3 Poll Interval Time .........................................................................................................17 3.2.4 Count............................................................................................................................18 3.2.5 Swap Code ..................................................................................................................18 3.2.6 Slave Node ..................................................................................................................18 3.2.7 Function Code..............................................................................................................18 3.2.8 Device Address............................................................................................................18 3.3 Uploading and Downloading the Configuration File................................................18 3.3.1 Required Hardware......................................................................................................19 3.3.2 Required Software .......................................................................................................19 3.3.3 Transferring the Configuration File to Your PC............................................................20 3.3.4 Transferring the Configuration File to the Module .......................................................22 DIAGNOSTICS AND TROUBLESHOOTING ...........................................................................27 4.1 The Configuration/Debug Menu .................................................................................27 4.1.1 Navigation ....................................................................................................................28 4.1.2 Keystrokes ...................................................................................................................28 4.2 Required Hardware......................................................................................................28 4.3 Required Software.......................................................................................................29 4.4 Using the Configuration/Debug Port .........................................................................29 4.5 Main Menu ....................................................................................................................30 4.5.1 Opening the Data Analyzer Menu................................................................................30 4.5.2 Viewing Block Transfer Statistics.................................................................................31 4.5.3 Restoring the Default Configuration.............................................................................31 4.5.4 Opening the Database Menu .......................................................................................31 4.5.5 Opening the Command Error List Menu ......................................................................31 4.5.6 Opening the Command List Menu ...............................................................................31 4.5.7 Transferring the Configuration File from module to PC ..............................................31 4.5.8 Transferring the Configuration File from PC to module ..............................................32 4.5.9 Viewing Version Information ........................................................................................32 4.5.10 Warm Booting the Module ...........................................................................................32 4.5.11 Cold Booting the Module..............................................................................................32 4.5.12 Viewing Port Communication Status ...........................................................................33 4.5.13 Viewing Port Configuration ..........................................................................................33
ProSoft Technology, Inc. May 9, 2007
Page 3 of 66

4.6 4.6.1 4.6.2 4.6.3 4.6.4 4.6.5 4.7 4.7.1 4.7.2 4.7.3 4.7.4 4.7.5 4.7.6 4.7.7 4.7.8 4.7.9 4.8 4.9 4.9.1 4.9.2 4.9.3 4.9.4 4.9.5 5 Command List Menu................................................................................................... 33 Redisplaying the Menu................................................................................................ 33 Redisplaying the Current Page ................................................................................... 33 Viewing the Previous Page of Commands.................................................................. 33 Viewing the Next Page of Commands ........................................................................ 34 Returning to the Main Menu ........................................................................................ 34 Data Analyzer .............................................................................................................. 34 Analyzing Data for Port 1 ............................................................................................ 35 Analyzing Data for Port 2 ............................................................................................ 35 Displaying Timing Marks in the Data Analyzer............................................................ 35 Removing Timing Marks in the Data Analyzer ............................................................ 35 Viewing Data in Hexadecimal Format ......................................................................... 35 Viewing Data in ASCII (Text) Format .......................................................................... 35 Starting the Data Analyzer .......................................................................................... 36 Stopping the Data Analyzer......................................................................................... 36 Returning to the Main Menu ........................................................................................ 36 Data Analyzer Tips ...................................................................................................... 37 LED Status Indicators................................................................................................. 39 PRT1 ........................................................................................................................... 39 U1 ................................................................................................................................ 39 U2 ................................................................................................................................ 39 STS.............................................................................................................................. 39 PRT2 ........................................................................................................................... 40
Contents
REFERENCE ............................................................................................................................ 41 5.1 Product Specifications ............................................................................................... 41 5.1.1 Features and Benefits ................................................................................................. 41 5.1.2 General Specifications ................................................................................................ 42 5.1.3 Hardware Specifications.............................................................................................. 42 5.1.4 Functional Specifications............................................................................................. 42 5.2 Functional Overview ................................................................................................... 43 5.2.1 Database ..................................................................................................................... 44 5.2.2 Data Transfer............................................................................................................... 45 5.2.3 Command List ............................................................................................................. 49 5.3 Cable Connections...................................................................................................... 50 5.3.1 RS-232 ........................................................................................................................ 50 5.3.2 RS-232 Configuration/Debug Port............................................................................... 52 5.3.3 RS-485 ........................................................................................................................ 53 5.3.4 RS-422 ........................................................................................................................ 53 5.3.5 DB9 to Mini-DIN Adaptor (Cable 09) ........................................................................... 54 5.4 Error/Status Data......................................................................................................... 54 5.4.1 Error/Status Data......................................................................................................... 54 5.4.2 Command Error List .................................................................................................... 56 5.4.3 Error Codes ................................................................................................................. 56 5.5 Configuration Form..................................................................................................... 57
SUPPORT, SERVICE & WARRANTY............................................................................................. 61 Module Service and Repair ........................................................................................................ 61 General Warranty Policy Terms and Conditions .................................................................. 62 Limitation of Liability.................................................................................................................. 63 RMA Procedures ......................................................................................................................... 63 INDEX............................................................................................................................................... 65
Page 4 of 66
Quick Start
Quick Start
This section describes the procedure to be followed for installing and configuring the module for communications. These steps should be followed for successful implementation of a module in a user application. 1 2 3 4 Define the communication characteristics of the Bosch master port. Define the command lists to be used on the Bosch master port. Fill in the blank configuration form for application using the data sets defined in steps one and two. Edit the configuration text file MVI_BSCH.TXT to reflect the desired data from the configuration form and save the file under a different name. This text file is provided on the program disk supplied with the module. Connect the MVI94-BSCH module's Configuration/Debug Port with a nullmodem cable. Connect the module to a 24 VDC power source. Select the directory containing the correct configuration file on the computer. Start Hyperterminal on the computer. Press the '?' key on the terminal to be certain the module is communicating with the computer and that the main menu mode is current. Press [R] in Hyperterminal to select the receive option. Press [Y] to confirm that you wish to download a new configuration. Press [ALT] [F3] and enter the name of the configuration file to load into the module. The configuration will be downloaded, and the module will restart using the new configuration. Connect the module's Bosch master port to the Bosch slave. If everything is configured correctly and the cable connections are correct, communications should be present on the master port. Monitor the communication statistics for the port to be certain everything is working correctly. View the database in the module using the terminal emulator. Edit the ladder logic provided with the module for your system. The ladder logic is responsible for transferring the data between the module and processor. Connect the module to the Flex I/O processor or Control Net processor. If all is configured correctly, the data in the module should be visible in the processor. Use the Configuration/Debug port to view the backplane transfer statistics.
5 6 7 8 9 10 11
12
13 14 15
16
17
Page 5 of 66
Quick Start
Page 6 of 66
Hardware Installation
In This Chapter
Verify Package Contents.......................................................... 7 Mounting the MVI 94 Flex I/O Base ......................................... 8 Setting Jumpers ....................................................................... 9 Installing the Module onto the Base ....................................... 11 Installing the Serial Adapter Cables ....................................... 12 Wiring the Power Connections ............................................... 12
2.1
Verify Package Contents

Make sure that you verify the contents of the product before you discard the packing material. The following components should be included with the product: 1 2 3 A MVI94 Flex I/O Base A MVI94 Module with 3 jumpers installed One Serial Adapter Cable
Page 7 of 66
Mounting the MVI 94 Flex I/O Base
1 2
3 4 5
6 7
Remove the cover plug (if used) in the male connector of the unit to which you are connecting this Base. Check to make sure that the 16 pins in the male connector on the adjacent device are straight and in line so that the mating female connector on this Base will mate correctly. Make certain that the female flexbus connector C is fully retracted into the Base. Position the Base on a 35 x 7.5mm DIN rail A at a slight angle with the hook B on the left side of the Base hooked into the right side of the unit on the left. Rotate the Base onto the DIN rail with the top of the rail hooked under the lip on the rear of the Base. Use caution to make sure that the female flexbus connector does not strike any of the pins in the mating male connector. Press the terminal base down onto the DIN rail until flush. The locking tab D snaps into position and locks the terminal base to the DIN rail. If the Base does not lock in place, use a screwdriver or similar device to move the locking tab down, press the Base flush with the DIN rail and release the locking tab to lock the base in place. Gently push the female flexbus C connector into the adjacent base or adapter male connector to complete the flexbus connections.
Page 8 of 66
Setting Jumpers
Before installing the MVI94 module onto its base, the module's configuration can be set using the jumpers on the bottom of the module as shown in this figure. MVI94-DOS Shipping Configuration
Port 2 RS-232/422/485: Select with jumper (shipped in 232). BP Reset: If the MVI94 module is to be reset when the Flex Bus is reset, install the BP RESET jumper in the Enabled position. ATTENTION: Do not remove or replace a base unit when power is applied. Interruption of the flexbus can result in unintended operation or machine motion. SETUP: To place the module in SETUP mode, install the jumper in the Selected position (DOS default). To prevent the module from being in Setup mode, move the jumper to the disabled position (GSC, MBM, etc. default), as shown in the following illustration.
Page 9 of 66
MVI94-BSCH FLEX I/O Platform Bosch Communication I/O Module MVI94-GSC/MBM/DNPM, etc Shipping Configuration
Page 10 of 66
Installing the Module onto the Base

1 2 Rotate the keyswitch 1 on the Base clockwise to position #1. Make certain the flexbus connector 3 on the Base is pushed all the way to the left to connect with the neighboring base or adapter. The Module cannot be installed unless the flexbus connector is fully extended. 3 Make sure that the pins on the bottom of the Module are straight so they will align properly with the connector socket on the Base. 4 Position the Module with its alignment bar 5 aligned with the groove 6 on the Base.
Press firmly and evenly to seat the Module in the Base. The Module is seated when the latch 7 on the Base is locked into the Module.
Page 11 of 66
Installing the Serial Adapter Cables

Two identical serial adapter cables are supplied. Each cable has a locking-type 8 pin Mini-DIN plug on one end and a DB-9 male connector on the other end. The Mini-DIN connector on each cable is inserted into the Mini-DIN receptacles marked PRT1 and PRT2 on the Base. To install the locking-type Mini-DIN connector, slide the spring-loaded sleeve back while inserting the plug into the receptacle on the Base, and then release the sleeve when fully seated. The locking mechanism prevents the cable from being removed during normal operation. To remove the cable, slide the sleeve back and remove the plug.
2.2
Wiring the Power Connections

External power is supplied to the Base on the 2 pin screw terminal block. The power supply can be either 24Vdc or 12Vdc, and should be located in close proximity of the base. Connect dc common to the COM terminal Connect +24V dc or +12V dc to the 24VDC terminal
Page 12 of 66
Configuration
Configuration
In This Chapter
Bosch Master ......................................................................... 14 Commands............................................................................. 16 Uploading and Downloading the Configuration File ............... 18
This section of the documentation describes the configuration data required by the communication module. It is important that the module be configured accurately for reliable and correct operation. The Reference chapter of the documentation contains a configuration form that can be used to aid in configuring the module. All configuration information for the module is stored in the module's Flash ROM. This provides permanent storage of the information. The user configures the module using a text file and then using the terminal server software provided with the module to download it to the module's Flash ROM. The file contains the configuration for the database, Flex backplane data transfer, master port and the command list. This file is downloaded to the module for each application. An example file (MVI_BSCH.TXT) is shipped with the module and should be used as a starting point for configuration. Use any text editor you are familiar with to edit the data in the file. When you have completed editing the file, download it to the module using the terminal server software provided by ProSoft Technology. A different file can be used for each application. The configuration file is separated into sections with topic header names enclosed in the [ ] characters. The configuration file consists of the following topics:
[Section] [BOSCH MASTER] [COMMANDS] Description Configuration of the module database, backplane data transfer and master port. Command list data for the Bosch master port.
After each section header, the file contains a set of parameters. Unique labels are used under each section to specify a parameter. Each label in the file must be entered exactly as shown in the file for the parameter to be identified by the program. If the module is not considering a parameter, look at the label for the data item. Each parameter's value is separated from the label with the ':' character. This character is used by the program to delimit the position in the data record where to start reading data. All data for a parameter must be placed after the ':' character. For numeric parameter values, any text located after the value will not be used. There must be at least on space character between the end of the parameter value and the following text. An example of a parameter entry is given below: Baud Rate: 38400 #Baud rate for port 110 to 115K ProSoft Technology, Inc. May 9, 2007 Page 13 of 66
MVI94-BSCH FLEX I/O Platform Bosch Communication I/O Module The parameter label is "Baud Rate" and the parameter value is 38400. The characters after the parameter value are ignored and are used for internal documentation of the configuration file.
Configuration
The following table describes the baud rate values expected by the program. Because the baud rate parameter can potentially exceed the value for a word value, high baud rates must be shortened.
Baud Rate 110 150 300 600 1200 2400 4800 9600 19,200 28,800 57,600 115,200 Parameter Value 110 150 300 600 12 or 1200 24 or 2400 48 or 4800 96 or 9600 19, 192 or 19200 28, 288 or 28800 57 or 576 115 or 1152
Any record that begins with the '#' character is considered to be a comment record. These records can be placed anywhere in the file as long as the '#' character is found in the first column of the line. These lines are ignored in the file and can be used to provide documentation within the configuration file. Liberal use of comments within the file can ease the use and interpretation of the data in the file. A description of each section and its contained data items (parameters) is given below.
3.1
Bosch Master
The [BOSCH MASTER] section of the configuration file sets the Bosch master port communication parameters, to define the database, to define the command list specifications for the master port and to specify the Flex backplane data transfer parameters. The following table lists the parameters defined in this section:
[Section]/Item [BOSCH MASTER] Module Name: Up to 80 chars 1 to 3996 Value Range Description Configuration header for Master Bosch Port. Name of the module for use on reports. Use this parameter to identify your module in your system. This parameter defines the maximum register in the database. You should size the database for your application leaving room for expansion in the future. Requests for registers outside of the range selected will be returned with an error message.
Maximum Register:
Page 14 of 66
Configuration

Value Range 1 to 3995 Description This value represents the relative starting position in the module's internal database where the Error/Status data will be stored. The table can be placed anywhere in the module's data space. The content of the Error/Status table is updated at the frequency defined in the parameter below. If a value of 1 is set for the parameter, the data will not be placed in the database. This parameter specifies the number of program cycles between each update of the Error/Status Block data in the module. If the parameter is set to a value of 0, the data is never updated. This parameter specifies the starting register in the internal database to write over the backplane. This parameter specifies the number registers in the internal database to write over the backplane. This parameter computes the number of blocks to transfer from the module to the backplane. The number of blocks must be >= 2 for proper backplane data transfer. This parameter specifies the starting register in the internal database to fill with data read over the backplane. This parameter specifies the number registers in the internal database to consider from the read operations over the backplane. This parameter computes the number of blocks to transfer from the backplane to the module. The number of blocks must be >= 2 for proper backplane data transfer. This parameter specifies the protocol to be used on the port. Valid Protocols are 0=Full Duplex and 1=Half Duplex. This parameter specifies the termination type to be used on the port. Valid termination types are 0=BCC and 1=CRC. This is the baud rate to be used on the port. Enter the baud rate as a value. For example, to select 19K baud, enter 19200. Valid entry for this field include: 110, 150, 300, 600, 1200, 2400, 4800, 9600, 19200, 28800, 38400, 57600 and 115. This is the Parity code to be used for the port. The coded values are as follows: 0=None, 1=Odd, 2=Even, 3=Mark and 4=Space. This parameter sets the number of data bits for each word used by the protocol. This parameter sets the number of stop bits to be used with each data value sent. This parameter sets the number of milliseconds to delay after RTS is asserted before the data will be transmitted.
[Section]/Item Error/Status Block Pointer:
Error/Status Frequency:
0 to 65535
Write Start Register: Write Register Count:
0 to 3995 12 to 3996
Read Start Register:
0 to 3995 12 to 3996
Read Register Count:
Protocol:
0 or 1
Termination Type:
0 or 1
Baud Rate:
110 to 115K
Parity:
0 to 4
Data Bits:
5 to 8
Stop Bits: RTS On:
1 or 2 0 to 65535
Page 15 of 66

[Section]/Item RTS Off: Value Range 0 to 65535 Y or N Description
Configuration
This parameter sets the number of milliseconds to delay after the last byte of data is sent before the RTS modem signal will be set low. This parameter specifies if the CTS modem control line is to be used. If the parameter is set to N, the CTS line will not be monitored. If the parameter is set to Y, the CTS line will be monitored and must be high before the module will send data. This parameter is normally only required when halfduplex modems are used for communication (2wire). This parameter specifies the number of milliseconds to delay after a response timeout before sending an ENQ. This parameter specifies the number of commands to be processed by the Bosch Master port. This parameter specifies the number of milliseconds to wait between issuing each command. This delay value is not applied to retries. This parameter sets the address in the internal database where the command error data will be placed. If the value is set to 1, the data will not be transferred to the database. This parameter represents the message response timeout period in 1-ms increments. This is the time that a port configured as a master will wait before re-transmitting a command if no response is received from the addressed slave. The value is set depending upon the communication network used and the expected response time of the slowest device on the network. This parameter specifies the number of times a command will be retried if it fails.
Use CTS Line:
ENQ Delay:
0 to 65535 0 to 100 0 to 65535
Command Count: Command Delay:
Error Block Pointer:
1 to 3995
Response Timeout:
0 to 65535
Retry Count:
0 to 10
3.2
Commands
The [COMMANDS] section of the configuration file sets the Bosch master port command list. This list polls Bosch slave devices attached to the Bosch master port. The module supports read and write commands. The various Bosch commands are implemented by accessing internal addresses that correspond to different functions. The command list is formatted differently than the other sections of the configuration file. Commands are present in a block between the labels START and END. These labels inform the program where the list resides. The module's program will parse all commands after the START label until it reaches the END label or until the command count entered for the port is reached. The function codes used for each command are either a write (0) or a read (1). Each command list record has the same format. The first part of the record contains the information relating to the MVI94-BSCH, communication module
Page 16 of 66
Configuration
and the second part contains information required to interface to the Bosch slave device. The command structure is displayed in the following table for all functions supported:
Each parameter is discussed below:
3.2.1
0 = Disabled
Enable Code
1 = Enabled with Poll Interval (seconds) utilized 2 = Conditional (executed when point in database changes) This field defines whether or not the command is to be executed and under what conditions. If the parameter is set to 0, the command is disabled and will not be executed in the normal polling sequence. The command can be executed under the control of the PLC processor through the use of a Command Control block. Setting the parameter to a value of 1 for the command causes the command to be executed each scan of the command list if the Poll Interval Time is set to zero. If the Poll Interval time is set, the command will be executed, when the interval timer expires. If the parameter is set to 2, the command will execute only if the internal data associated with the command changes. This value is valid only for write commands.
3.2.2
Internal Address
This field specifies the database register to be associated with the command. If the command is a read function, the data read from the slave device will be placed starting at the register value entered in this field. If the command is a write function, the data written to the slave device will be sourced from the address specified. Register addresses specified for commands must reside in the range specified by the Maximum Register parameter under the [BOSCH MASTER] section.
3.2.3
Poll Interval Time
This parameter specifies the minimum interval to execute continuous commands (Enable code of 1). The parameter is entered in units of seconds. Therefore, if a value of 10 is entered for a command, the command will execute no more frequently than every 10 seconds. ProSoft Technology, Inc. May 9, 2007 Page 17 of 66
Configuration
3.2.4
Count
This parameter specifies the number of registers to be associated with the command. For a write command this will determine the number of registers (words) written to the slave device. For read commands this value must be set to 1.
3.2.5
Swap Code
This parameter defines if the data received from the Bosch slave is to be ordered differently than received from the slave device. This parameter is helpful when dealing with floating-point or other multi-register values, as there is no standard method of storage of these data types in slave devices. This parameter can be set to order the register data received in an order useful by other applications. The following table defines the values and their associated operations:
Code 0 1 2 3 Operation None -- No change is made in the byte ordering. Words -- The words are swapped. Words & Bytes -- The words are swapped and then, the bytes in each word are swapped. Bytes --The bytes in each word are swapped.
3.2.6
Slave Node
This parameter specifies the Bosch slave node address on the network to be considered. Values of 0 to 255 are permitted.
3.2.7
Function Code
This parameter specifies the Bosch function to be executed by the command. The following table defines the purpose of each function supported by the module.
Func 0 1 Description Write Parameters Read Status
3.2.8
Device Address
This parameter specifies the starting register address to be considered by the command in the Bosch slave device. Refer to the documentation of each Bosch slave device on the network for their register address assignments.
3.3
Uploading and Downloading the Configuration File

ProSoft modules are shipped with a pre-loaded configuration file. In order to edit this file, you must transfer the file from the module to your PC. After editing, you must transfer the file back to the module.
Page 18 of 66
Configuration
This section describes these procedures. Important: The illustrations of configuration/debug menus in this section are intended as a general guide, and may not exactly match the configuration/debug menus in your own module. For specific information about the configuration/debug menus in your module, refer to The Configuration/Debug Menu.
3.3.1
Required Hardware
You can connect directly from your computer's serial port to the serial port on the module to view configuration information, perform maintenance, and send (upload) or receive (download) configuration files. ProSoft Technology recommends the following minimum hardware to connect your computer to the module: 80486 based processor (Pentium preferred) 1 megabyte of memory At least one serial communications port available A null modem serial cable.
3.3.2
Required Software
In order to send and receive data over the serial port (COM port) on your computer to the module, you must use a communication program (terminal emulator). A simple communication program called HyperTerminal is pre-installed with recent versions of Microsoft Windows operating systems. If you are connecting from a machine running DOS, you must obtain and install a compatible communication program. The following table lists communication programs that have been tested by ProSoft Technology.
DOS Windows 3.1 Windows 95/98 Windows NT/2000/XP ProComm, as well as several other terminal emulation programs Terminal HyperTerminal HyperTerminal
The module uses the Ymodem file transfer protocol to send (upload) and receive (download) configuration files from your module. If you use a communication program that is not on the list above, please be sure that it supports Ymodem file transfers.
Page 19 of 66
Configuration
3.3.3
1
Transferring the Configuration File to Your PC
Connect your PC to the Configuration/Debug port of the module using a terminal program such as HyperTerminal. Press [?] to display the main menu.
Press [S] (Send Module Configuration). The message "Press Y key to confirm configuration send!" is displayed at the bottom of the screen.
Page 20 of 66
Configuration
Press [Y]. The screen now indicates that the module is ready to send.
From the Transfer menu in HyperTerminal, select Receive File. This action opens the Receive File dialog box.
Use the Browse button to choose a folder on your computer to save the file, and then click Receive.
Note: ProSoft Technology suggests that you upload the configuration file preloaded on your module. However, configuration files are also available on the ProSoft CD as well as the ProSoft Technology web site at http://www.prosofttechnology.com. Select Ymodem as the receiving protocol.
Page 21 of 66
MVI94-BSCH FLEX I/O Platform Bosch Communication I/O Module 7
Configuration
Click the Receive button. This action opens the Ymodem File Receive dialog box, showing the progress of your file transfer.
When the configuration file has been transferred to your PC, the dialog box will indicate that the transfer is complete.
The configuration file is now on your PC at the location you specified. You can now open and edit the file in a text editor such as Notepad. When you have finished editing the file, save it and close Notepad.
3.3.4
Transferring the Configuration File to the Module
Perform the following steps to transfer a configuration file from your PC to the module.
Page 22 of 66
Configuration
Connect your PC to the Configuration/Debug port of the module using a terminal program such as HyperTerminal. Press [?] to display the main menu.
Press [R] (Receive Module Configuration). The message "Press Y key to confirm configuration receive!" is displayed at the bottom of the screen.
Press [Y]. The screen now indicates that the PC is ready to send.
Page 23 of 66
MVI94-BSCH FLEX I/O Platform Bosch Communication I/O Module 4 From the Transfer menu in HyperTerminal, select Send File.
Configuration
The Send File dialog appears.
Use the Browse button to locate the configuration file your computer.
Note: This procedure assumes that you are uploading a newly edited configuration file from your PC to the module. However, configuration files are also available on the ProSoft CD as well as the ProSoft Technology web site at http://www.prosoft-technology.com. 6 Select Ymodem as the protocol.
Page 24 of 66
Configuration
Click the Send button. This action opens the Ymodem File Send dialog box.
When the file transfer is complete, the module's configuration/debug screen indicates that the module has reloaded program values, and displays information about the module.
Your module now contains the new configuration.
Page 25 of 66
Configuration
Page 26 of 66
Diagnostics and Troubleshooting

In This Chapter
The Configuration/Debug Menu ............................................. 27 Required Hardware ................................................................ 28 Required Software ................................................................. 29 Using the Configuration/Debug Port....................................... 29 Main Menu ............................................................................. 30 Command List Menu .............................................................. 33 Data Analyzer......................................................................... 34 Data Analyzer Tips................................................................. 37 LED Status Indicators ............................................................ 39
The module provides information on diagnostics and troubleshooting in the following forms: Status data values are transferred from the module to the processor. Data contained in the module can be viewed through the Configuration/Debug port attached to a terminal emulator. LED status indicators on the front of the module provide information on the module's status.
4.1
The Configuration/Debug Menu

The Configuration and Debug menu for this module is arranged as a tree structure, with the Main Menu at the top of the tree, and one or more sub-menus for each menu command. The first menu you see when you connect to the module is the Main menu. Because this is a text-based menu system, you enter commands by typing the command letter from your computer keyboard in the terminal application (for example, HyperTerminal). The module does not respond to mouse movements or clicks. The command executes as soon as you press the command letter you do not need to press [Enter]. When you type a command letter, a new screen will be displayed in your terminal application.
Page 27 of 66
4.1.1
Navigation
All of the sub-menus for this module contain commands to redisplay the menu or return to the previous menu. You can always return from a sub-menu to the next higher menu by pressing [M] on your keyboard. The organization of the menu structure is represented in simplified form in the following illustration:
The remainder of this section shows you the menus available for this module, and briefly discusses the commands available to you.
4.1.2
Keystrokes
The keyboard commands on these menus are almost always non-case sensitive. You can enter most commands in lower case or capital letters. The menus use a few special characters ([?], [-], [+], [@]) that must be entered exactly as shown. Some of these characters will require you to use the [Shift], [Ctrl] or [Alt] keys to enter them correctly. For example, on US English keyboards, enter the [?] command as [Shift][/]. Also, take care to distinguish capital letter [I] from lower case letter [l] (L) and number [1]; likewise for capital letter [O] and number [0]. Although these characters look nearly the same on the screen, they perform different actions on the module.
4.2
Required Hardware
You can connect directly from your computer's serial port to the serial port on the module to view configuration information, perform maintenance, and send (upload) or receive (download) configuration files. ProSoft Technology recommends the following minimum hardware to connect your computer to the module: 80486 based processor (Pentium preferred) 1 megabyte of memory At least one serial communications port available A null modem serial cable.
Page 28 of 66
4.3
Required Software
In order to send and receive data over the serial port (COM port) on your computer to the module, you must use a communication program (terminal emulator). A simple communication program called HyperTerminal is pre-installed with recent versions of Microsoft Windows operating systems. If you are connecting from a machine running DOS, you must obtain and install a compatible communication program. The following table lists communication programs that have been tested by ProSoft Technology.
DOS Windows 3.1 Windows 95/98 Windows NT/2000/XP ProComm, as well as several other terminal emulation programs Terminal HyperTerminal HyperTerminal
The module uses the Ymodem file transfer protocol to send (upload) and receive (download) configuration files from your module. If you use a communication program that is not on the list above, please be sure that it supports Ymodem file transfers.
4.4
Using the Configuration/Debug Port

To connect to the module's Configuration/Debug port: 1 2 Connect your computer to the module's port using a null modem cable. Start the communication program on your computer and configure the communication parameters with the following settings:
57,600 None 8 1 XON/XOFF
Baud Rate Parity Data Bits Stop Bits Software Handshaking
Open the connection. When you are connected, press the [?] key on your keyboard. If the system is set up properly, you will see a menu with the module name followed by a list of letters and the commands associated with them. If there is no response from the module, follow these steps: 3 Verify that the null modem cable is connected properly between your computer's serial port and the module. A regular serial cable will not work. 2 Verify that RSLinx is not controlling the COM port. Refer to Disabling the RSLinx Driver for the Com Port on the PC. 3 Verify that your communication software is using the correct settings for baud rate, parity and handshaking. 4 On computers with more than one serial port, verify that your communication program is connected to the same port that is connected to the module. If you are still not able to establish a connection, you can contact ProSoft Technology Technical Support for further assistance. 1 ProSoft Technology, Inc. May 9, 2007 Page 29 of 66
4.5
Main Menu
When you first connect to the module from your computer, your terminal screen will be blank. To activate the main menu, press the [?] key on your computer's keyboard. If the module is connected properly, the following menu will appear on your terminal screen:
Some of the commands available to you from this menu are designed for advanced debugging and system testing only, and can cause the module to stop communicating with the processor or other devices, resulting in potential data loss or other failures. Only use these commands if you are specifically directed to do so by ProSoft Technology Technical Support staff. Some of these command keys are not listed on the menu, but are active nevertheless. Please be careful when pressing keys so that you do not accidentally execute an unwanted command. Caution: Some of the commands available to you from this menu are designed for advanced debugging and system testing only, and can cause the module to stop communicating with the processor or with other devices, resulting in potential data loss or other failures. Only use these commands if you are specifically directed to do so by ProSoft Technology Technical Support staff. Some of these command keys are not listed on the menu, but are active nevertheless. Please be careful when pressing keys so that you do not accidentally execute an unwanted command.
4.5.1
Opening the Data Analyzer Menu
Press [A] to open the Data Analyzer Menu. Use this command to view all bytes of data transferred on each port. Both the transmitted and received data bytes are displayed. Refer to Data Analyzer for more information about this menu. Important: When in analyzer mode, program execution will slow down. Only use this tool during a troubleshooting session. Before disconnecting from the Config/Debug port, please be sure to press [M] to return to the main menu and disable the data analyzer. This action will allow the module to resume its normal operating mode. Page 30 of 66 ProSoft Technology, Inc. May 9, 2007
4.5.2
Viewing Block Transfer Statistics
Press [B] from the Main Menu to view the Block Transfer Statistics screen. Use this command to display the configuration and statistics of the backplane data transfer operations between the module and the processor. The information on this screen can help determine if there are communication problems between the processor and the module. Tip: To determine the number of blocks transferred each second, mark the numbers displayed at a specific time. Then some seconds later activate the command again. Subtract the previous numbers from the current numbers and divide by the quantity of seconds passed between the two readings.
4.5.3
Restoring the Default Configuration
Press [C] to the restore the configuration parameters to the factory default settings.
4.5.4
Opening the Database Menu
Press [D] to open the Database View menu. Use this menu command to view the current contents of the module's database.
4.5.5
Opening the Command Error List Menu
Press [E] to open the Command Error List. This list consists of multiple pages of command list error/status data. Press [?] to view a list of commands available on this menu.
4.5.6
Opening the Command List Menu
Press [L] to open the Command List menu. Use this command to view the configured command list for the module.
4.5.7
Transferring the Configuration File from module to PC
Press [S] to receive (download) the configuration file from the module to your PC. Press [Y] to confirm the file transfer, and then follow the instructions on the terminal screen to complete the file transfer process. After the file has been successfully downloaded, you can open and edit the file to change the module's configuration.
Page 31 of 66
4.5.8
Transferring the Configuration File from PC to module
Press [R] to send (upload) the configuration file from your PC to the module and store the file on the module's Compact Flash Disk. Press [Y] to confirm the file transfer, and then follow the instructions on the terminal screen to complete the file transfer process. After the file has been successfully downloaded, the module will restart the program and load the new configuration information. Review the new configuration using menu commands [6] and [0] to be certain the module is configured correctly.
4.5.9
Viewing Version Information
Press [V] to view Version information for the module. Use this command to view the current version of the software for the module, as well as other important values. You may be asked to provide this information when calling for technical support on the product. Values at the bottom of the display are important in determining module operation. The Program Scan Counter value is incremented each time a module's program cycle is complete. Tip: Repeat this command at one-second intervals to determine the frequency of program execution.
4.5.10
Warm Booting the Module
Caution: Some of the commands available to you from this menu are designed for advanced debugging and system testing only, and can cause the module to stop communicating with the processor or with other devices, resulting in potential data loss or other failures. Only use these commands if you are specifically directed to do so by ProSoft Technology Technical Support staff. Some of these command keys are not listed on the menu, but are active nevertheless. Please be careful when pressing keys so that you do not accidentally execute an unwanted command. Press [W] from the Main Menu to warm boot (restart) the module. This command will cause the program to exit and reload, refreshing configuration parameters that must be set on program initialization. Only use this command if you must force the module to re-boot.
4.5.11
Cold Booting the Module
Press [Esc] to restart the module and force all drivers to be loaded. The module will use the configuration stored in the module's Flash ROM to configure the module. Page 32 of 66 ProSoft Technology, Inc. May 9, 2007
4.5.12
Viewing Port Communication Status
Press [1] from the Main Menu to view the port communication status for the application port. Use this command to view communication status and statistics for the selected port. This information can be informative when trouble-shooting communication problems.
4.5.13
Viewing Port Configuration
Press [6] from the Main Menu to view configuration information for the application port. Use this command to display detailed configuration information for the port.
4.6
Command List Menu

Use this menu to view the configured command list for the module. Press [?] to view a list of commands available on this menu.
4.6.1
Redisplaying the Menu
Press [?] to display the current menu. Use this command when you are looking at a screen of data, and want to view the menu choices available to you.
4.6.2
Redisplaying the Current Page
Press [S] to redisplay the current page of data. Use this command to display the current page of commands. Ten commands are displayed on each page. If an enabled command has an error, the EN field will contain a value of -1. This indicates that the command will be re-issued every 30 seconds.
4.6.3
Viewing the Previous Page of Commands
Press [P] to display the previous page of commands. ProSoft Technology, Inc. May 9, 2007 Page 33 of 66
4.6.4
Viewing the Next Page of Commands
Press [N] to display the next page of commands.
4.6.5
Returning to the Main Menu
Press [M] to return to the Main Menu.
4.7
Data Analyzer
The data analyzer mode allows you to view all bytes of data transferred on each port. Both the transmitted and received data bytes are displayed. Use of this feature is limited without a thorough understanding of the protocol.
Page 34 of 66
Important: When in analyzer mode, program execution will slow down. Only use this tool during a trouble-shooting session. Before disconnecting from the Config/Debug port, please be sure to press [M] to return to the main menu and disable the data analyzer. This action will allow the module to resume its normal operating mode.
4.7.1
Analyzing Data for Port 1
Press [1] to display I/O data for Port 1 in the Data Analyzer. The following illustration shows an example of the Data Analyzer output.
4.7.2
Analyzing Data for Port 2
Press [2] to display I/O data for Port 2 in the Data Analyzer.
4.7.3
Displaying Timing Marks in the Data Analyzer
You can display timing marks for a variety of intervals in the data analyzer screen. These timing marks can help you determine communication-timing characteristics.
Key [5] [6] [7] [8] [9] Interval 1 mSec ticks 5 mSec ticks 10 mSec ticks 50 mSec ticks 100 mSec ticks
4.7.4
Removing Timing Marks in the Data Analyzer
Press [0] to turn off timing marks in the Data Analyzer screen.
4.7.5
Viewing Data in Hexadecimal Format
Press [H] to display the data on the current page in hexadecimal format.
4.7.6
Viewing Data in ASCII (Text) Format
Press [A] to display the data on the current page in ASCII format. This is useful for regions of the database that contain ASCII data. ProSoft Technology, Inc. May 9, 2007 Page 35 of 66
4.7.7
Starting the Data Analyzer
Press [B] to start the data analyzer. After the key is pressed, all data transmitted and received on the currently selected port will be displayed. An example display is shown below:
The Data Analyzer displays the following special characters:

Character [] <> <R+> <R-> <CS> _TT_ Definition Data enclosed in these characters represent data received on the port. Data enclosed in these characters represent data transmitted on the port. These characters are inserted when the RTS line is driven high on the port. These characters are inserted when the RTS line is dropped low on the port. These characters are displayed when the CTS line is recognized high. These characters are displayed when the timing mark interval has been reached. This parameter is user defined.
4.7.8
Stopping the Data Analyzer
Press [S] to stop the data analyzer. Use this option to freeze the display so the data can be analyzed. To restart the analyzer, press [B]. Important: When in analyzer mode, program execution will slow down. Only use this tool during a trouble-shooting session. Before disconnecting from the Config/Debug port, please be sure to press [S] to stop the Data Analyzer before returning to the main menu or disconnecting from the port. This action will allow the module to resume its normal operating mode.
4.7.9
Returning to the Main Menu
Press [M] to return to the Main Menu.
Page 36 of 66
4.8
Data Analyzer Tips

From the main menu, press [A] for the "Data Analyzer". You should see the following text appear on the screen:
After the "Data Analyzer" mode has been selected, press [?] to view the Data Analyzer menu. You will see the following menu:
From this menu, you can select the "Port", the "format", and the "ticks" that you can display the data in. For most applications, HEX is the best format to view the data, and this does include ASCII based messages (because some characters will not display on HyperTerminal and by capturing the data in HEX, we can figure out what the corresponding ASCII characters are supposed to be). The Tick value is a timing mark. The module will print a _TT for every xx mSec of no data on the line. Usually 10msec is the best value to start with. After you have selected the Port, Format, and Tick, we are now ready to start a capture of this data. The easiest way to do so is to go up to the top of you HyperTerminal window, and do a Transfer -> Capture Text as shown below:
Page 37 of 66
After selecting the above option, the following window will appear:
Next name the file, and select a directory to store the file in. In this example, we are creating a file ProSoft.txt and storing this file on our root C: drive. After you button. have done this, press the Now you have everything that shows up on the HyperTerminal screen being logged to a file called ProSoft.txt. This is the file that you will then be able to email to ProSoft Technical Support to assist with issues on the communications network. To begin the display of the communications data, you will then want to press 'B' to tell the module to start printing the communications traffic out on the debug port of the module. After you have pressed 'B', you should see something like the following:
The <R+> means that the module is transitioning the communications line to a transmit state. All characters shown in <> brackets are characters being sent out by the module. The <R-> shows when the module is done transmitting data, and is now ready to receive information back. And finally, all characters shown in the [ ] brackets is information being received from another device by the module. Page 38 of 66 ProSoft Technology, Inc. May 9, 2007
After taking a minute or two of traffic capture, you will now want to stop the "Data Analyzer". To do so, press the 'S' key, and you will then see the scrolling of the data stop. When you have captured the data you want to save, open the Transfer menu and choose Capture Text. On the secondary menu, choose Stop.
You have now captured, and saved the file to your PC. This file can now be used in analyzing the communications traffic on the line, and assist in determining communication errors.
4.9
LED Status Indicators

This section defines the indications provided on the MVI94-BSCH module through LEDs. A description of each LED is given below:
4.9.1
PRT1
This LED indicates data transmit and receive activity on the configuration port. When the TXD or RXD pin is active on the port, the LED will be illuminated green. When the port is not active, the LED will be in the off state.
4.9.2
U1
This LED indicates backplane data transfer operation. When the module is successfully writing data to the FLEX I/O backplane, the LED will be in the off state. When the module is reading a new block of data from the FLEX I/O backplane, the LED will be in the on state (amber). During normal operation of the module, this LED should turn on and off at a very rapid rate. If the LED never turns on, check your ladder logic to be certain the data transfer is set up correctly.
4.9.3
U2
This LED indicates communication errors on the Bosch master port. The LED is illuminated (amber) when no error exists on the port. If a communication error is recognized on the port, the LED will turn off. If the LED is turned off, check for errors in the command list to determine the error condition recognized by the module.
4.9.4
STS
This LED indicates the "health" of the module. When power is applied to the module, the LED will be illuminated. If the LED is green, the program is working ProSoft Technology, Inc. May 9, 2007 Page 39 of 66
correctly and the user configuration is being used. If the LED is red, the program is halted. Try restarting the module by cycling power. This should cause the module to return to its normal state.
4.9.5
PRT2
This LED indicates data transmit and receive activity on the Bosch master port. When the TXD or RXD pin is active on the port, the LED will be illuminated green. When the port is not active, the LED will be in the off state.
Page 40 of 66
Reference
Reference
In This Chapter
Product Specifications............................................................ 41 Functional Overview............................................................... 43 Cable Connections................................................................. 49 Error/Status Data ................................................................... 54 Configuration Form ................................................................ 57
5.1
Product Specifications
The MVI94 Bosch Communication I/O Module is used to interface Bosch SVB/SVK compatible slave devices (Robert Bosch Corporation's line of packaging machinery) with the Flex I/O system. The module contains a database that is defined by the user. This database is used for the request and command messages sent from the Bosch master port to Bosch slave devices. Data areas in the database can be reserved for status and error information generated by the module under user control.
5.1.1
Features and Benefits
A Bosch master port is present on the communication module to continuously poll Bosch slave devices. Up to 100 user-defined commands can be defined for the port. Data read from Bosch slave devices are placed in the database. Any write requests for the Bosch slave devices are sourced with data from the database. Commands can be activated in the module under processor control. This feature permits the processor to issue a command in the command list under program control. When a command is activated, it will be placed in the command queue for immediate execution. Normal command polling will begin after the command queue is completely processed. The module provides a configuration/debug port for use with an external computer executing a terminal server program. The terminal server program provided with the module permits uploading and downloading of the configuration information required by the module. Additionally, the configuration/debug port provides a view into the database, communication statistics and the configuration.
Page 41 of 66
Reference
5.1.2

General Specifications
Some of the general specifications include: Operation via simple ladder logic Complete setup and monitoring of module through Debug port and user configuration file Flex backplane interface via I/O access
5.1.3
Specification Form Factor
Hardware Specifications
Description Single Slot 1794 Backplane compatible Locate in any slot of Backplane 20 mA @ 5 V 12V to 24VDC 340 mA to 170 mA 0 to 55C (32 to 140F) 40 to 85C (40 to 185F) 30g operational 50g non-operational 5g from 10150 Hz 5 to 95% (non-condensing) Module status Backplane transfer status Application status Serial activity and error LED status Mini-DIN RS-232 Hardware handshaking Mini-DIN RS-232/422/485 jumper selectable 500V optical isolation from backplane 3.7H x 3.7W x 2.7D inches 94H x 94W x 69D mm
Backplane current load External power supply Operating temperature Storage temperature Shock Relative humidity LED indicators
Configuration Serial port (PRT1) Application serial Port (PRT2) Dimensions (with Module installed in Base)
5.1.4
Functional Specifications
Parameter Description General Parameters (Software Configurable) Internal Database 4000 registers (words) available Communication parameters Local Station ID: 0 to 255 Port 0 Baud Rate: 110 to 115.2K baud Port 1,2,3 Baud Rate: 110 to 115K baud Stop Bits: 1 or 2 Data Size: 7 or 8 bits Parity: None, Even, Odd RTS Timing delays: 0 to 65535 ms BOSCH Modes Full-Duplex Error Checking BCC Type BOSCH Master Driver General Configurable Parameters per Master port BOSCH Commands supported Specifications Full-Duplex Point to Point Min Command Delay Number of Commands Response Timeout Retry Count Slave List Error Pointer 0x00 Protected Write 0x01 Unprotected Read
Page 42 of 66
Reference

Specifications Up to 100 command per master port, each fully configurable for function, slave address, register to/from addressing and word/bit count Error codes available on an individual command basis. In addition, a slave status list is maintained per active master port. User configurable polling of commands, including disabled, continuous and on change of data (write only)
Type Command List Status Data Polling of command list
5.2
Functional Overview
The MVI94-BSCH communication module interfaces Bosch SVB/SVK compatible slave devices with the Flex I/O system. The module contains a database that is defined by the user. This database is used for the request and command messages sent from the Bosch master port to Bosch slave devices. Data areas in the database can be reserved for status and error information generated by the module under user control. The database also interfaces with the Flex I/O system using the Flex I/O bus (backplane). Data is made available to the PLC or any processor on a Control Net network using this backplane interface. Input and output image tables in the module present the data in the database to the backplane. A Bosch master port is present on the communication module to continuously poll Bosch slave devices. Up to 100 user-defined commands can be defined for the port. Data read from Bosch slave devices are placed in the database. Any write requests for the Bosch slave devices are sourced with data from the database. Commands can be activated in the module under processor control. This feature permits the processor to issue a command in the command list under program control. When a command is activated, it will be placed in the command queue for immediate execution. Normal command polling will begin after the command queue is completely processed. The module provides a Configuration/Debug port for use with an external computer using a terminal program such as HyperTerminal. Additionally, the Configuration/Debug port provides a view into the database, communication statistics and the configuration.
Page 43 of 66
Reference
5.2.1
Database
Central to the functionality of the module is the database. This database is used as the interface between remote Bosch slave devices and the Flex I/O bus. The size, content and structure of the database are completely user defined. The Flex I/O bus reads data from and write data to the database using the backplane interface. The module interfaces data contained in remote Bosch slave devices to the database using the Bosch master port. User commands are issued out the master port from a command list. These commands gather or control data in the Bosch slave devices. The following illustration shows the relationships discussed above:
Page 44 of 66
Reference
5.2.2
Data Transfer
Data is transferred over the backplane using the module's input and output images. The module is configured with an eight-word input image and a sevenword output image. The module and the Flex processor use these images to page data and commands. The input image is set (written) by the module and is read by the Flex processor. The output image is set (written) by the Flex processor and read by the module. The following illustration shows this relationship:
The module's program is responsible for setting the block identification code used to identify the data block written and the block identification code of the block it wants to read from the processor. User configuration information determines the read (Read Start Register) and write (Write Start Register) locations in the database and the amount of data transferred (Read Register Count and Write Register Count). Each read and write operation transfers a sixword data area. The write operation contains a two-word header that defines the block identification code of the write data and the block identification code of the read block requested. These identification codes are in the range of 0 to 666. A value of zero indicates that the block contains no data and should be ignored. ProSoft Technology, Inc. May 9, 2007 Page 45 of 66
MVI94-BSCH FLEX I/O Platform Bosch Communication I/O Module The first valid block identification code is one and refers to the first block of six words to be read or written.
Reference
The module and the processor constantly monitor input and output images. How does either one know when a new block of data is available? Recognizing a change in the header information of the image (word 0) solves the problem. For example, when the module recognizes a different value in the first word of the output image, new read data is available. When the processor recognizes a new value in the first word of the input image, new write data is available. This technique requires the storage of the previously processed data block identification code. The diagram below shows the normal sequence of events for data transfer:
The steps outlined in the diagram above are discussed below: During program initialization, the write and read block identification codes are set to one. The last block read variable is set to zero. 3 The program copies the first six-word block of the database starting at the user defined Write Start Register to the input image (words 2 to 7). It then sets the current read block code in word 1 of the input image. To "trigger" the write operation, the program places the current write block code into word 0 of the input image. 1 2 Page 46 of 66 ProSoft Technology, Inc. May 9, 2007
Reference
MVI94-BSCH FLEX I/O Platform Bosch Communication I/O Module The Flex processor recognizes a new value in word 0 of the input image (based on the last_write_block_code not equal to write_block_code) in its ladder logic. The ladder logic computes the offset into the file based on the following formula:
write_file_offset = (write_block_code 1) * 6
The new data contained in the input image (words 2 to 7) is copied to the offset in the processor's user data file. The last_write_block_code storage register in the processor is updated with the new write_block_code. NOTE: If the data area transferred from the module exceeds the size of a single user file in the Flex processor, logic will be required to handle multiple files. 5 The ladder logic next examines the value of the read_block_code and computes the offset into the read data file as follows:
read_file_offset = (read_block_code 1) * 6
The required 6-word, read data is copied to the module's output image (words 1 to 6). To "trigger" the transfer operation, the ladder logic moves the read_block_code into word 0 of the output image. 6 The module's program recognizes the new read_block_code. It transfers the data to the correct offset in the database using the following function:
Database_offset = Read_Start_Register + (read_block_code 1 ) * 6
The module sets the last_read_block_code to the value of read_block_code. 7 The module now selects the next read and write blocks. The data for the write operation is placed in the input image and the read_block_code is set. The module "triggers" the transfer operation by setting the new write_block_code in word 0 of the input image. The sequence continues at step 3. The discussion above is for normal data transfer operation. The following table lists the block identification codes used by the module. Block Identification Codes
Type R/W Number 1 to 666 Description Data blocks used to transfer data from the module to the backplane and from the backplane to the module. The module's input/output images are used for the data transfers. These blocks transfer a list of commands to execute from a device on the backplane to the module. The number of commands to be considered is coded in the block number. For example, to add three commands to the command queue, use block 2003. Warm boot the module. When the module receives this block, it will reset all program values using the configuration data. Cold boot the module. When the module receives this block, it will perform a hardware restart.
2001 to 2006
R R
9998 9999
Data is transferred between the processor and the module using the block identification codes of 1 to 666. The other block codes control the module from the processors ladder logic. They are implemented when the ladder logic needs to control the module. In order to use one of the blocks, the ladder logic inserts the data and code in the output image of the module. The data should be set before the code is placed in the block. This operation should be performed after ProSoft Technology, Inc. May 9, 2007 Page 47 of 66
MVI94-BSCH FLEX I/O Platform Bosch Communication I/O Module the receipt of a new write block from the module. A discussion of each set of codes is given below: Commands (Blocks 2001 to 2006)
Reference
These control blocks are sent from the processor to the module to execute one or more commands in the module's command list out the Bosch master port. Commands selected for execution need not have the Enable Code set (1 or 2) but must be valid commands. The format for this block is shown below:
Block 2001 to 2006 Structure
Word 0 1 2 3 4 5 6 Description Command queue block identification code of 2001 to 2006. This word contains the index in the command list for the first command to be entered into the command queue. This word contains the index in the command list for the second command to be entered into the command queue. This word contains the index in the command list for the third command to be entered into the command queue. This word contains the index in the command list for the fourth command to be entered into the command queue. This word contains the index in the command list for the fifth command to be entered into the command queue. This word contains the index in the command list for the sixth command to be entered into the command queue.
When the module receives one of these blocks, it examines word 0 of the output image. This word defines the number of commands contained in the block. The command count is determined by subtracting 2000 from the word value. This permits the controller to set from one to six commands into the command queue. The indexes submitted in the block should be valid for the command list. After the module determines the number of commands to consider, it inserts each command in the command queue. The response message sent from the module to the processor is as follows:
Block 2001 to 2006 Response
Word 0 1 2 3 4 5 6 Description This word contains the block 2001 to 2006 requested by the processor. This word contains the next read request block identification code. This word contains the number of commands in the block placed in the command queue. Not used. Not used. Not used. Not used.
The ladder logic can examine word 2 of the input image to determine the number of commands placed in the command queue. Any errors associated with the command can be viewed in the command list error table.
Page 48 of 66
Reference
Warm-Boot (Block 9998) This block does not contain any data. When the processor places a value of 9998 in word 0 of the output image, the module will perform a warm-start. This involves clearing the configuration and all program status data. Finally, the program will load in the configuration information from the Flash ROM and begin running. There is no positive response to this message other than the status data being set to zero and the block polling starting over. Cold-Boot (Block 9999) This block does not contain any data. When the processor places a value of 9999 in word 0 of the output image, the module will perform a hardware restart. This will cause the module to reboot and reload the program. There is no positive response to this message other than the status data being set to zero and the block polling starting over.
5.2.3
Command List
The MVI94-BSCH communication module's primary services are data concentration and communication gateway. The Bosch master port polls Bosch slave devices based on user-defined commands and places the data in the database. The Flex I/O bus interfaces with this database to a Flex processor. The user is responsible for defining the structure and content of the database. In order to interface the database with Bosch slave devices, you must construct a command list. The commands in the list specify the Bosch slave device to be utilized, the function to be performed (read or write), the data area in the device to interface with and the position in the database to be associated with the device data. Up to 100 commands can be entered for this purpose. The list is processed from top (command #0) to bottom. A poll interval parameter is associated with each command to specify a minimum delay time in seconds between the issuance of a command. If the user specifies a value of 10 for the parameter, the command will be executed no more frequently than every 10 seconds. Additionally, a user specified time delay could be inserted between the issuance of each command. This is useful for slow responding slave devices. Write commands have a special feature, as they can be set to execute only if the data in the write command changes. If the data in the command has not changed since the command was last issued, the command will not be executed. If the data in the command has changed since the command was last issued, the command will be executed. Use of this feature can lighten the load on the Bosch network. In order to implement this feature; set the enable code for the command to a value of 2.
Page 49 of 66
Reference
5.3
Cable Connections
The application ports on the MVI94-BSCH module support RS-232, RS-422, and RS-485 interfaces. Please look at the module to ensure that the jumpers are set correctly to correspond with the type of interface you are using. Note: When using RS-232 with radio modem applications, some radios or modems require hardware handshaking (control and monitoring of modem signal lines). Enable this in the configuration of the module by setting the UseCTS parameter to 1.
5.3.1
RS-232
When the RS-232 interface is selected, the use of hardware handshaking (control and monitoring of modem signal lines) is user definable. If no hardware handshaking will be used, the cable to connect to the port is as shown below:
Page 50 of 66
Reference
RS-232 -- Modem Connection This type of connection is required between the module and a modem or other communication device.
The "Use CTS Line" parameter for the port configuration should be set to 'Y' for most modem applications. RS-232 -- Null Modem Connection (Hardware Handshaking) This type of connection is used when the device connected to the module requires hardware handshaking (control and monitoring of modem signal lines).
Page 51 of 66
MVI94-BSCH FLEX I/O Platform Bosch Communication I/O Module RS-232 -- Null Modem Connection (No Hardware Handshaking)
Reference
This type of connection can be used to connect the module to a computer or field device communication port.
NOTE: If the port is configured with the "Use CTS Line" set to 'Y', then a jumper is required between the RTS and the CTS line on the module connection.
5.3.2
RS-232 Configuration/Debug Port
This port is physically a Mini-DIN connection. A Mini-DIN to DB-9 adapter cable is included with the module. This port permits a PC based terminal emulation program to view configuration and status data in the module and to control the module. The cable for communications on this port is shown in the following diagram:
Page 52 of 66
Reference
5.3.3
RS-485
The RS-485 interface requires a single two or three wire cable. The Common connection is optional and dependent on the RS-485 network. The cable required for this interface is shown below:
5.3.4
RS-422
RS-485 and RS-422 Tip If communication in the RS-422/RS-485 mode does not work at first, despite all attempts, try switching termination polarities. Some manufacturers interpret +/and A/B polarities differently.
Page 53 of 66
Reference
5.3.5
DB9 to Mini-DIN Adaptor (Cable 09)
5.4
Error/Status Data
The module error/status data areas are discussed in this section. The module contains two areas related to this data. The user defines the location of these data sets in the database of the module. The error/status data contains module data and the command error list data set contains the errors associated with the command list.
5.4.1
Error/Status Data
The error/status data table is located at the address assigned by the user. If the address is set to 1 or the frequency parameter is set to 0, the data will not be placed in the database. It will only be available through the Configuration/Debug Port. If valid address and frequency values are assigned, the module will update the data area. The data area will be initialized with zeros whenever the processor is initialized. This occurs during a cold-start (power-on), reset (reset push-button pressed) or a warm-boot operation (commanded or loading of new configuration). The data area is a 32-word register block. The structure of the block is shown below: System Status
Word 0 1 Description Program Cycle Counter Last read block identification code.
Page 54 of 66
Reference

Description Current read block identification code. Current write block identification code. Current command index value. Total number of commands to process by the module. Total number of commands in the command queue. Current state code for the Bosch master port. Current communication state code for the Bosch master port.
Word 2 3 4 5 6 7 8
System Information
Word 9 10 11 13 15 Revision (ASCII) Operating System Rev(ASCII) Production Run Number (ASCII) Description Product Name (ASCII) = BSCH
Block Transfer Statistics

Word 26 27 28 29 30 31 Description Total number of read block operations Total number of write block operations Total number of blocks parsed Total number of event blocks received Total number of command blocks received. Total number block transfer errors.
Master Port Statistics

Word 17 18 19 20 21 22 23 24 25 Description Number of Command Requests Number of Command Responses Number of Command Errors Number of Requests Number of Responses Number of Errors Received Number of Errors Sent Reserved Reserved
Page 55 of 66
Reference
5.4.2
Command Error List
Each command in the command list has a reserved word value for a status/error code. This error data list can be read using the Configuration/Debug Port. Additionally, the data can be placed in the database of the module. The configuration parameter "Command Error Pointer" defines the register address in the database where the data will be placed. The first word in the register location defined contains the status/error code for the first command in the port's command list. Each successive word in the command error list is associated with the next command in the list. Therefore, the size of the data area is dependent upon the number of commands defined. Refer to the following Error Codes section to interpret the status/error codes present in the data area.
5.4.3
Error Codes
The module error codes are listed in this section. Error codes are separated into Bosch error codes and module error codes. Bosch Error Codes These error codes are returned to the module from Bosch slave devices attached to the master port. The error codes are listed in the following table:
Code 16 80 96 112 Description Command Byte Incorrect Illegal Data Address Access Denied Illegal Data Value
Module Error Codes Module error codes are generated by the module's program. These errors can result due to configuration or communication problems. These errors are stored in the Bosch master, command list error table. A word is allocated for each command in the memory area. The following table lists the errors returned by the module for communication errors:
Code 1 2 10 11 20 21 Description CTS modem control line not set before transmit Timeout while transmitting message Timeout waiting for ACK Timeout waiting for response after request NAK received Incorrect BCC in response
The following table lists the errors returned by the module for errors found when parsing the command list: Page 56 of 66 ProSoft Technology, Inc. May 9, 2007
Reference

Description Invalid enable code Internal address > maximum address Invalid node address (<0 or > 255) Count parameter set to 0 Invalid function code All parameters set to 0
Code 41 42 43 44 45 46
Use the error codes returned for each command in the list to determine the success or failure of the command. If the command fails, use the error code to determine the cause of failure.
5.5
Configuration Form
This section contains configuration forms that will aid in the configuration of the module. If you design your system before trying to directly implement it, you will have a greater chance of success. Fill in the configuration form for your application, and then edit the configuration text file.
[Section]/Item [BOSCH MASTER] Module Name: Up to 80 chars 1 to 3996 Value Range Description Configuration header for Master Bosch Port. Name of the module for use on reports. Use this parameter to identify your module in your system. This parameter defines the maximum register in the database. You should size the database for your application leaving room for expansion in the future. Requests for registers outside of the range selected will be returned with an error message. This value represents the relative starting position in the module's internal database where the Error/Status data will be stored. The table can be placed anywhere in the module's data space. The content of the Error/Status table is updated at the frequency defined in the parameter below. If a value of 1 is set for the parameter, the data will not be placed in the database. This parameter specifies the number of program cycles between each update of the Error/Status Block data in the module. If the parameter is set to a value of 0, the data is never updated. This parameter specifies the starting register in the internal database to write over the backplane. This parameter specifies the number registers in the internal database to write over the backplane. This parameter computes the number of blocks to transfer from the module to the backplane. The number of blocks must be >= 2 for proper backplane data transfer.
Maximum Register:
Error/Status Block Pointer:
1 to 3995
Error/Status Frequency:
0 to 65535
Write Start Register:
0 to 3995 12 to 3996
Write Register Count:
Page 57 of 66

[Section]/Item Read Start Register: Value Range 0 to 3995 12 to 3996 Description
Reference
This parameter specifies the starting register in the internal database to fill with data read over the backplane. This parameter specifies the number registers in the internal database to consider from the read operations over the backplane. This parameter computes the number of blocks to transfer from the backplane to the module. The number of blocks must be >= 2 for proper backplane data transfer. This parameter specifies the protocol to be used on the port. Valid Protocols are 0=Full Duplex and 1=Half Duplex. This parameter specifies the termination type to be used on the port. Valid termination types are 0=BCC and 1=CRC. This is the baud rate to be used on the port. Enter the baud rate as a value. For example, to select 19K baud, enter 19200. Valid entry for this field include: 110, 150, 300, 600, 1200, 2400, 4800, 9600, 19200, 28800, 38400, 57600 and 115. This is the Parity code to be used for the port. The coded values are as follows: 0=None, 1=Odd, 2=Even, 3=Mark and 4=Space. This parameter sets the number of data bits for each word used by the protocol. This parameter sets the number of stop bits to be used with each data value sent. This parameter sets the number of milliseconds to delay after RTS is asserted before the data will be transmitted. This parameter sets the number of milliseconds to delay after the last byte of data is sent before the RTS modem signal will be set low. This parameter specifies if the CTS modem control line is to be used. If the parameter is set to N, the CTS line will not be monitored. If the parameter is set to Y, the CTS line will be monitored and must be high before the module will send data. This parameter is normally only required when half-duplex modems are used for communication (2-wire). This parameter specifies the number of milliseconds to delay after a response timeout before sending an ENQ. This parameter specifies the number of commands to be processed by the Bosch Master port. This parameter specifies the number of milliseconds to wait between issuing each command. This delay value is not applied to retries.
Read Register Count:
Protocol:
0 or 1
Termination Type:
0 or 1
Baud Rate:
110 to 115K
Parity:
0 to 4
Data Bits: Stop Bits: RTS On:
5 to 8 1 or 2 0 to 65535 0 to 65535 Y or N
RTS Off:
Use CTS Line:
ENQ Delay:
0 to 65535 0 to 100
Command Count:
Command Delay:
0 to 65535
Page 58 of 66
Reference

Value Range 1 to 3995 Description This parameter sets the address in the internal database where the command error data will be placed. If the value is set to 1, the data will not be transferred to the database. This parameter represents the message response timeout period in 1-ms increments. This is the time that a port configured as a master will wait before re-transmitting a command if no response is received from the addressed slave. The value is set depending upon the communication network used and the expected response time of the slowest device on the network. This parameter specifies the number of times a command will be retried if it fails.
[Section]/Item Error Block Pointer:
Response Timeout:
0 to 65535
Retry Count:
0 to 10
Page 59 of 66
Reference
Page 60 of 66
Reference
Support, Service & Warranty

ProSoft Technology, Inc. survives on its ability to provide meaningful support to its customers. Should any questions or problems arise, please feel free to contact us at:
Internet Phone Postal Mail Web Site: http://www.prosoft-technology.com/support E-mail address: support@prosoft-technology.com +1 (661) 716-5100 +1 (661) 716-5101 (Fax) ProSoft Technology, Inc. 1675 Chester Avenue, Fourth Floor Bakersfield, CA 93301
Before calling for support, please prepare yourself for the call. In order to provide the best and quickest support possible, we will most likely ask for the following information: Product Version Number System architecture Module configuration and contents of configuration file Module Operation o Configuration/Debug status information o LED patterns 5 Information about the processor and user data files as viewed through the processor configuration software and LED patterns on the processor 6 Details about the serial devices interfaced An after-hours answering system allows pager access to one of our qualified technical and/or application support engineers at any time to answer the questions that are important to you. 1 2 3 4
Module Service and Repair

The MVI94-BSCH device is an electronic product, designed and manufactured to function under somewhat adverse conditions. As with any product, through age, misapplication, or any one of many possible problems the device may require repair. When purchased from ProSoft Technology, Inc., the device has a 1 year parts and labor warranty (3 years for RadioLinx) according to the limits specified in the warranty. Replacement and/or returns should be directed to the distributor from whom the product was purchased. If you must return the device for repair, obtain an RMA (Returned Material Authorization) number from ProSoft Technology, Inc. Please call the factory for this number, and print the number prominently on the outside of the shipping carton used to return the device.
Page 61 of 66
Reference
General Warranty Policy Terms and Conditions

ProSoft Technology, Inc. (hereinafter referred to as ProSoft) warrants that the Product shall conform to and perform in accordance with published technical specifications and the accompanying written materials, and shall be free of defects in materials and workmanship, for the period of time herein indicated, such warranty period commencing upon receipt of the Product. Limited warranty service may be obtained by delivering the Product to ProSoft in accordance with our product return procedures and providing proof of purchase and receipt date. Customer agrees to insure the Product or assume the risk of loss or damage in transit, to prepay shipping charges to ProSoft, and to use the original shipping container or equivalent. Contact ProSoft Customer Service for more information. This warranty is limited to the repair and/or replacement, at ProSoft's election, of defective or non-conforming Product, and ProSoft shall not be responsible for the failure of the Product to perform specified functions, or any other nonconformance caused by or attributable to: (a) any misuse, misapplication, accidental damage, abnormal or unusually heavy use, neglect, abuse, alteration (b) failure of Customer to adhere to ProSofts specifications or instructions, (c) any associated or complementary equipment, software, or user-created programming including, but not limited to, programs developed with any IEC1131-3 programming languages, 'C' for example, and not furnished by ProSoft, (d) improper installation, unauthorized repair or modification (e) improper testing, or causes external to the product such as, but not limited to, excessive heat or humidity, power failure, power surges or natural disaster, compatibility with other hardware and software products introduced after the time of purchase, or products or accessories not manufactured by ProSoft; all of which components, software and products are provided as-is. In no event will ProSoft be held liable for any direct or indirect, incidental consequential damage, loss of data, or other malady arising from the purchase or use of ProSoft products. ProSofts software or electronic products are designed and manufactured to function under adverse environmental conditions as described in the hardware specifications for this product. As with any product, however, through age, misapplication, or any one of many possible problems, the device may require repair. ProSoft warrants its products to be free from defects in material and workmanship and shall conform to and perform in accordance with published technical specifications and the accompanying written materials for up to one year (12 months) from the date of original purchase (3 years for RadioLinx products) from ProSoft. If you need to return the device for repair, obtain an RMA (Returned Material Authorization) number from ProSoft Technology, Inc. in accordance with the RMA instructions below. Please call the factory for this number, and print the number prominently on the outside of the shipping carton used to return the device. If the product is received within the warranty period ProSoft will repair or replace the defective product at our option and cost.
Page 62 of 66
Reference
Warranty Procedure: Upon return of the hardware product ProSoft will, at its option, repair or replace the product at no additional charge, freight prepaid, except as set forth below. Repair parts and replacement product will be furnished on an exchange basis and will be either reconditioned or new. All replaced product and parts become the property of ProSoft. If ProSoft determines that the Product is not under warranty, it will, at the Customer's option, repair the Product using then current ProSoft standard rates for parts and labor, and return the product freight collect.
Limitation of Liability
EXCEPT AS EXPRESSLY PROVIDED HEREIN, PROSOFT MAKES NO WARRANT OF ANY KIND, EXPRESSED OR IMPLIED, WITH RESPECT TO ANY EQUIPMENT, PARTS OR SERVICES PROVIDED PURSUANT TO THIS AGREEMENT, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. NEITHER PROSOFT OR ITS DEALER SHALL BE LIABLE FOR ANY OTHER DAMAGES, INCLUDING BUT NOT LIMITED TO DIRECT, INDIRECT, INCIDENTAL, SPECIAL OR CONSEQUENTIAL DAMAGES, WHETHER IN AN ACTION IN CONTRACT OR TORT (INCLUDING NEGLIGENCE AND STRICT LIABILITY), SUCH AS, BUT NOT LIMITED TO, LOSS OF ANTICIPATED PROFITS OR BENEFITS RESULTING FROM, OR ARISING OUT OF, OR IN CONNECTION WITH THE USE OR FURNISHING OF EQUIPMENT, PARTS OR SERVICES HEREUNDER OR THE PERFORMANCE, USE OR INABILITY TO USE THE SAME, EVEN IF ProSoft OR ITS DEALER'S TOTAL LIABILITY EXCEED THE PRICE PAID FOR THE PRODUCT. Where directed by State Law, some of the above exclusions or limitations may not be applicable in some states. This warranty provides specific legal rights; other rights that vary from state to state may also exist. This warranty shall not be applicable to the extent that any provisions of this warranty are prohibited by any Federal, State or Municipal Law that cannot be preempted. Contact ProSoft Customer Service at +1 (661) 716-5100 for more information.
RMA Procedures
In the event that repairs are required for any reason, contact ProSoft Technical Support at +1 661.716.5100. A Technical Support Engineer will ask you to perform several tests in an attempt to diagnose the problem. Simply calling and asking for a RMA without following our diagnostic instructions or suggestions will lead to the return request being denied. If, after these tests are completed, the module is found to be defective, we will provide the necessary RMA number with instructions on returning the module for repair.
Page 63 of 66
Reference
Page 64 of 66
Index
G
General Specifications 42
Index
A
Analyzing Data for Port 1 35 Analyzing Data for Port 2 35
H
Hardware Installation 7 Hardware Specifications 42
I
Installing the Module onto the Base 11 Installing the Serial Adapter Cables 12 Internal Address 17
B
Block 2001 to 2006 Response 48 Block 2001 to 2006 Structure 48 Block Identification Codes 47 Block Transfer Statistics 55 Bosch Error Codes 56 Bosch Master 14
K
Keystrokes 28
L
LED Status Indicators 39
C
Cable Connections 50 Cold Booting the Module 32 Cold-Boot (Block 9999) 49 Command Error List 56 Command List 49 Command List Menu 33 Commands 16 Commands (Blocks 2001 to 2006) 48 Configuration 13 Configuration Form 57 Count 18
M
Main Menu 30 Master Port Statistics 55 Module Error Codes 56 Mounting the MVI 94 Flex I/O Base 8
N
Navigation 28
D
Data Analyzer 34 Data Analyzer Tips 37 Data Transfer 45 Database 44 DB9 to Mini-DIN Adaptor (Cable 09) 54 Device Address 18 Diagnostics and Troubleshooting 27 Displaying Timing Marks in the Data Analyzer 35
O
Opening the Command Error List Menu 31 Opening the Command List Menu 31 Opening the Data Analyzer Menu 30 Opening the Database Menu 31
P
Please Read This Notice 2 Poll Interval Time 17 Product Specifications 41 PRT1 39 PRT2 40
E
Enable Code 17 Error Codes 56 Error/Status Data 54
Q
Quick Start 5
F
Features and Benefits 41 Function Code 18 Functional Overview 43 Functional Specifications 42
R
Redisplaying the Current Page 33 Redisplaying the Menu 33
Page 65 of 66

Reference 41 Removing Timing Marks in the Data Analyzer 35 Required Hardware 19, 28 Required Software 19, 29 Restoring the Default Configuration 31 Returning to the Main Menu 34, 36 RS-232 50 RS-232 -- Modem Connection 51 RS-232 -- Null Modem Connection (Hardware Handshaking) 51 RS-232 -- Null Modem Connection (No Hardware Handshaking) 52 RS-232 Configuration/Debug Port 52 RS-422 53 RS-485 53 RS-485 and RS-422 Tip 53 Viewing the Previous Page of Commands 33 Viewing Version Information 32
Index
W
Warm Booting the Module 32 Warm-Boot (Block 9998) 49 Wiring the Power Connections 12
Y
Your Feedback Please 2
S
Setting Jumpers 9 Slave Node 18 Starting the Data Analyzer 36 Stopping the Data Analyzer 36 STS 39 Support, Service & Warranty 61 Swap Code 18 System Information 55 System Status 54
T
The Configuration/Debug Menu 27 Transferring the Configuration File from module to PC 31 Transferring the Configuration File from PC to module 32 Transferring the Configuration File to the Module 22 Transferring the Configuration File to Your PC 20
U
U1 39 U2 39 Uploading and Downloading the Configuration File 18 Using the Configuration/Debug Port 29
V
Verify Package Contents 7 Viewing Block Transfer Statistics 31 Viewing Data in ASCII (Text) Format 35 Viewing Data in Hexadecimal Format 35 Viewing Port Communication Status 33 Viewing Port Configuration 33 Viewing the Next Page of Commands 34
Page 66 of 66

Mvi94 BSCH User Manual

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Mvi94 BSCH User Manual

Uploaded by

Copyright:

Available Formats

MVI94-BSCH

FLEX I/O Platform Bosch Communication I/O Module

Please Read This Notice

Your Feedback Please

MVI94-BSCH FLEX I/O Platform Bosch Communication I/O Module

ProSoft Technology, Inc. May 9, 2007

MVI94-BSCH FLEX I/O Platform Bosch Communication I/O Module

ProSoft Technology, Inc. May 9, 2007

MVI94-BSCH FLEX I/O Platform Bosch Communication I/O Module

ProSoft Technology, Inc. May 9, 2007

MVI94-BSCH FLEX I/O Platform Bosch Communication I/O Module

ProSoft Technology, Inc. May 9, 2007

MVI94-BSCH FLEX I/O Platform Bosch Communication I/O Module

Verify Package Contents

ProSoft Technology, Inc. May 9, 2007

MVI94-BSCH FLEX I/O Platform Bosch Communication I/O Module

Mounting the MVI 94 Flex I/O Base

ProSoft Technology, Inc. May 9, 2007

MVI94-BSCH FLEX I/O Platform Bosch Communication I/O Module

ProSoft Technology, Inc. May 9, 2007

ProSoft Technology, Inc. May 9, 2007

MVI94-BSCH FLEX I/O Platform Bosch Communication I/O Module

Installing the Module onto the Base

ProSoft Technology, Inc. May 9, 2007

MVI94-BSCH FLEX I/O Platform Bosch Communication I/O Module

Installing the Serial Adapter Cables

Wiring the Power Connections

ProSoft Technology, Inc. May 9, 2007

MVI94-BSCH FLEX I/O Platform Bosch Communication I/O Module

ProSoft Technology, Inc. May 9, 2007

MVI94-BSCH FLEX I/O Platform Bosch Communication I/O Module

[Section]/Item Error/Status Block Pointer:

Write Start Register: Write Register Count:

Read Start Register:

Read Register Count:

Stop Bits: RTS On:

ProSoft Technology, Inc. May 9, 2007

MVI94-BSCH FLEX I/O Platform Bosch Communication I/O Module

Use CTS Line:

0 to 65535 0 to 100 0 to 65535

Command Count: Command Delay:

Error Block Pointer:

ProSoft Technology, Inc. May 9, 2007

MVI94-BSCH FLEX I/O Platform Bosch Communication I/O Module

Each parameter is discussed below:

Poll Interval Time

MVI94-BSCH FLEX I/O Platform Bosch Communication I/O Module

Uploading and Downloading the Configuration File

ProSoft Technology, Inc. May 9, 2007

MVI94-BSCH FLEX I/O Platform Bosch Communication I/O Module

ProSoft Technology, Inc. May 9, 2007

MVI94-BSCH FLEX I/O Platform Bosch Communication I/O Module

Transferring the Configuration File to Your PC

ProSoft Technology, Inc. May 9, 2007

MVI94-BSCH FLEX I/O Platform Bosch Communication I/O Module

ProSoft Technology, Inc. May 9, 2007

MVI94-BSCH FLEX I/O Platform Bosch Communication I/O Module 7

Transferring the Configuration File to the Module

ProSoft Technology, Inc. May 9, 2007

MVI94-BSCH FLEX I/O Platform Bosch Communication I/O Module

ProSoft Technology, Inc. May 9, 2007

The Send File dialog appears.