[ Pobierz całość w formacie PDF ]

1 32 18
1746-FIO4V Fast Analog Comb 2 In & 2 Voltage Out
1 54 1
1746-NO4I 4 Channel Analog Current Output
1 54 2
1746-NO4V 4 Channel Analog Voltage Output
1 35 10
1746-NT4 4 Channel Thermocouple Input Module
1 35 33
1746sc-NT8 Spectrum Controls, 4 Analog inputs isolated
1 35 13
1746-NR4 4 Channel RTD/Resistance Input Module
3 127 5
1746-HSCE High Speed Counter/Encoder
1 33 3
1746-HS Single Axis Motion Controller
3 101 14
1746-HSRV SLC Servo Single AX MC
1 35 12
1746-HSTP1 Stepper Controller Module
1 35 6
1746-BAS1c BASIC Module - 5/01 Configuration
4 131 6
1746-BAS2c BASIC Module - 5/02 Configuration
4 136 27
1746-QS Synchronized Axes
4 131 15
1746-QV Open Loop Velocity
1 32 25
1747-DCM1c Direct Commun. Module (1/4 RACK)
1 33 25
1747-DCM2c Direct Commun. Module (1/2 RACK)
1 34 25
1747-DCM3c Direct Commun. Module (3/4 RACK)
1 35 25
1747-DCM4c Direct Commun. Module (FULL RACK)
4 158 11
1747-MNET Module Interface
4 136 6
1747-SDN DeviceNet Scanner
4 136 8
1747-SN Remote I/O Scanner
1 35 7
1747-DSN1c Distributed I/O Scanner - 7 Blks
4 136 7
1747-DSN2c Distributed I/O Scanner - 30 Blks
1 42 9
1747-KE1c Interface Module, Series A
1 35 9
1747-KE2c Interface Module, Series B
a.The module names shown in this table correspond to those used by the OC_GetIOConfiguration and
OC_CreateIOConfiguration functions.
b.The mix code for a module is composed of one byte field. The upper 3 bits represent the class of the
module, and the lower 5 bits represent the I/O mix of the module.
c.Some modules can have multiple configurations. To distinguish between different configurations of the
same module, a single digit is appended to the module name.
Publication 1747-6.5.3 June 1998
5 6 Configuring I/O Modules
Notes:
Publication 1747-6.5.3 June 1998
Chapter 6
Library of Routines
Introduction The MS-DOS API is a run-time library that can be linked with most industry
standard programming language compilers using the Pascal calling convention.
The Windows NT API is a 32-bit DLL that can be linked with most industry-standard
programming language compilers.
This chapter provides the programming information for each routine and identifies
which operating system supports the routine. The calling convention for each API
function is shown in C format.
Publication 1747-6.5.3 June 1998
6 2 Library of Routines OC_CalculateCRC
OC_CalculateCRC OC_CalculateCRC calculates a 16-bit CRC.
Syntax:
void OC_CalculateCRC(BYTE *bufPtr, WORD bLen, WORD *Crc);
Parameters:
Parameter: Description:
bufPtr Points to the buffer that contains the bytes for the CRC calculation
bLen Number of bytes for which to calculate the CRC
Crc A word that returns the calculated CRC
Description:
This function is useful for verifying data integrity. For example, a CRC might be appended to data stored
in the host retentive data partition. When the data is later retrieved, a new CRC can be calculated and
compared to the old CRC to ensure the data is valid.
Return Value:
none
Considerations:
Supported in the DOS API library and the Windows NT API library
Example:
BYTE buffer[100];
WORD buffer_crc;
int retcode;
retcode = OC_CalculateCRC( buffer, 100, &buffer_crc );
Publication 1747-6.5.3 June 1998
OC_ClearFault Library of Routines 6 3
OC_ClearFault OC_ClearFault clears any fault condition of the scanner.
Syntax:
int OC_ClearFault(HANDLE handle);
Parameters:
Parameter: Description:
handle Must be a valid handle returned from OC_OpenScanner
Description:
All extended error information must be retrieved before the fault can be cleared.
If the scanner encounters an error condition, it generates an extended error and faults. The fault forces the
scanner into Idle mode. The scanner cannot be placed into Scan mode until the fault is cleared.
Return Value:
Name: Value: Description:
SUCCESS fault was cleared successfully
2
ERR_OCACCESS handle does not have access to the scanner
11
ERR_OCEXTERR scanner extended error message, see OC_GetExtendedError
5
ERR_OCINIT scanner has not been initialized, see OC_InitScanner
10
ERR_OCRESPONSE scanner did not respond to request
Considerations:
Supported in the DOS API library and the Windows NT API library
Example:
HANDLE Handle;
int retcode;
retcode = OC_ClearFault( Handle );
Publication 1747-6.5.3 June 1998
6 4 Library of Routines OC_CloseScanner
OC_CloseScanner This function must always be called before exiting the application.
Syntax:
int OC_CloseScanner(HANDLE handle);
Parameters:
Parameter: Description:
handle Must be a valid handle returned from OC_OpenScanner
Description:
This function releases control of the scanner device, releases the interrupt assigned by OC_OpenScanner,
and disables the segment address assignment.
ATTENTION: The system might become unstable if you don t call OC_CloseScanner before exiting
the application.
!
Return Value:
Name: Value: Description:
SUCCESS scanner was closed successfully
2
ERR_OCACCESS handle does not have access to the scanner
Considerations:
Supported in the DOS API library and the Windows NT API library
Example:
HANDLE Handle;
int retcode;
retcode = OC_CloseScanner( Handle );
Publication 1747-6.5.3 June 1998
OC_ConfigureDII Library of Routines 6 5
OC_ConfigureDII OC_ConfigureDII allows an application to receive a message from the scanner when
an input bit pattern of a discrete I/O module matches a compare value.
Syntax:
int OC_ConfigureDII(HANDLE handle, DII_CFG *diicfg);
Parameters:
Parameter: Description:
handle Must be a valid handle returned from OC_OpenScanner
diicfg Points to the DII configuration
Description:
The application configures the compare value using this function and when the comparison completes, the
scanner generates a message to the application. The application must then call OC_PollScanner to retrieve
the message.
The DII_CFG structure is defined as:
typedef struct {
BYTE SlotNum; /* slot number 1-30*/
BYTE IOIncludeMask;/* bits allowed mask */
BYTE IOEdgeType;/* bit pattern to compare */
WORD PresetCount;/* number of matches */
} DII_CFG;
This value: Means: [ Pobierz całość w formacie PDF ]