7524 Interface Support User's Guide
Native Server Functional Overview
Comparison of 7524, 7526, 7527 Command Capabilities
This publication describes the configuration and use of the 7524 Interface Support for OS/2 and Windows NT program product. This product allows use of radio-frequency-linked IBM 7524 data collection terminals with Data Collection Connection (DCConnect).
This publication provides information and reference for system personnel responsible for the installation and operation of the 7524 Interface Support for OS/2 and Windows NT software product.
Products discussed in this publication may not be available in your country. The 902-928 MHz Spread Spectrum Technology (SST) products (7524-302 Radio Frequency (RF) Controller, 7524-402/422 Radio Frequency Bases, 7524-310 LAN Repeater) are not available in any European countries. Consult IBM about product availability in your country.
Operation of 7524 UHF radio frequency products is subject to individual licensing from your country's government. IBM will be able to assist you in obtaining the approvals and operating frequency required.
One or more of the following IBM publications may be needed for reference when using this publication.
References in this publication to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM licensed program or other IBM product in this publication is not intended to state or imply that only IBM's program or other product can be used. Any functionally equivalent product, program, or service that does not infringe on any of IBM's intellectual property rights or other legally protectible rights can be used instead of the IBM product, program, or service. Evaluation and verification of operation in conjunction with other products, programs, or services, except those expressly designated by IBM, are the user's responsibility.
IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquires, in writing, to:
IBM Director of Commercial Relations
IBM Corporation
500 Columbus Avenue
Thornwood, NY 10594
U.S.A.
For online versions of this documentation, we authorize you to:
You are responsible for payment of any taxes, including personal property taxes, resulting from this authorization.
THERE ARE NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
Some jurisdictions do not allow the exclusion of implied warranties, so the above exclusion might not apply to you.
Your failure to comply with the terms above terminates this authorization. Upon termination, you must destroy your machine-readable documentation.
The following terms are trademarks of the IBM Corporation in the United States or other countries, or both:
| IBM | Operating System/2 |
| OS/2 |
Other company, product, and service names may be trademarks or service marks of others.
The following information describes how to use this book.
How to Use the Contents
To view a topic, click on the topic.
How to Obtain Additional Information
After you select a topic, the information for that topic appears in the window. Underlined words or phrases indicate that additional information is available. Using a mouse, click on the underlined word. Additional information will appear in the window.
This chapter explains how to:
Use the setup menus or switch settings on the 7524 RF controller, bases, and terminals to configure the hardware for use with 7524 Interface Support.
Configure the 7524-301/302/304 RF Controller through its menu system per instructions in its accompanying User's Guide, with specific settings as follows.
7524-301 UHF Controller
Note: Setting the Call Sign here is not required if you have set it in the 7524 Terminal Notebook.
Note: This refers to the HOST communications port on the 7524-301/302 RF Controller.
7524-302 SST Controller
Note: The LAN ID of the 7524-302 Controller must match that set on each 7524-402/422 RF Base and each 7524-102/202 terminal to which the controller should communicate. Generally, use LAN ID = 0 (this is the factory default). You must use a different LAN ID if your RF terminals are attaching to a near-by, unrelated SST system. Changing the LAN ID prevents unrelated systems from communicating.
Note: This refers to the HOST communications port on the 7524-301/302 Radio Frequency Controller.
7524-304 SST Controller
Refer to the documentation that comes with 7524-304 SST Controller. Where the options in the configuration match those available in a 7524-302 controller, you can use the same settings.
7524-401 Base
7524-402/422 Base
7520-001 Base (for 2.4 GHz)
On 7524-101/102/051/052/054 hand-held terminals, press the gold shift key followed by the MENU key to access the setup menus.
On 7524-201/202/204 mobile-mount terminals, use the Right shift (gold-colored) followed by the MENU key (the Left shift key) to access the menus.
The menus used to set critical parameters are protected by a password. All terminals use the password CR52401, and this cannot be changed. Optionally, you can set a password that protects against all access to the setup menus. Having this optional password active prevents any unauthorized tampering with the display contrast and beeper volume settings. The optional password can be set or erased only after using the critical parameters access password to access the Setup Parms menu; it can consist of 1 to 7 characters of your choice. If the optional password is set, the CR52401 password can be used as a synonym; that is, it is a master password at all times.
The Setup menu structure on the 7524 terminals allows you to set various operating features for the terminal:
Note: For the backlight to come on, the operator must press the gold shift and "light" key. After that, the backlight automatically comes back on for the timer duration after each key stroke.
For UHF units
Set Baud rate, protocol, radio number, transaction resend timer, and RF power timer.
The radio button specifies a terminal address from 0-126.
The transaction resend timer determines how long the terminal waits before resending a transaction if it has not received an acknowledgement from the PC that the transaction arrived.
The RF power timer determines how long the terminal maintains power for the RF receiver after a message is transmitted to the PC. When the timer expires, the terminal goes into a mode where the RF receiver is powered off for 8 seconds, on for 2 seconds, off for 8 seconds, and so forth. The default value is 60 seconds, that should be adequate for most installations. However, if you have more than 20 terminals and communications slow down, increase the RF power timer to 120 seconds.
For SST units
Set LAN ID, Host name, radio number, and transaction resend timer.
On all terminals, adjust the screen size to show as much information as possible while maintaining a font size acceptable to your application.
The DCConnect terminal configuration supports up to 20 lines by 40 characters (20x40). If the terminal supports at least a 20x40 screen size, then set the physical terminal size to be close to 20x40. Otherwise, you should configure the terminal screen to its maximum dimensions. When writing transaction programs and defining messages to be displayed, take into account the number of rows and columns that the terminal can display. For example, on the 7524-10x models, the maximum screen size is 21 rows by 26 columns. If you choose this size, write your transaction programs such that no messages or prompts go beyond column 26.
Select the Setup parms menu item and use the password CR52401 to set the following parameters.
Select the Setup parms menu item, and use the password CR52401 to set the following parameters.
Note: Each 7524-302 Controller on a LAN must have a unique Host Name. Your 7524 units running 7524 Extended Terminal Services communicates to the controller attached to the DCConnect personal computer, while other 7524s running host terminal emulations (for example, 3270, 5250, VT-220) communicates to the controller connected to their respective hosts. The physical LAN (for example, RS-485 RF LAN or Ethernet LAN) and the 7524-402/422 RF bases can be shared by all of the 7524 terminals and controllers, no matter what terminal program or host emulation they are running. (All the 7524 equipment is utilizing the same LAN ID in this scenario).
The setup parameters for the 7524-xx4 terminals are the same as for 7524-xx2 (See7524-052, 7524-102 Hand-Held and 7524-202 Mobile-Mount 9xx MHz SST Terminals) terminals except that the range of the LAN IDs is 0-15.
7524 CFRs developed for the 7527 can generally be used on the 7524, but require re-compiling and re-linking. Refer to Custom Function Routines (SeeCustom Function Routines) for additional details of supported CFR APIs.
The programming tools (library, header, and example files) required to create CFRs for 7524 ETS are included in the \DCCONN\SAMPLES\7524CFR directory on your drive where the 7524 Interface Support for OS/2 and Windows NT has been installed. Refer to the 7524 Extended Terminal Services Programming Technical Reference for detailed information about creating CFRs for the 7524.
Some CFRs originally developed for the 7526 or the 7527 will be usable on the 7524 after a re-linking to the CFRAPI24.LIB library. This is true if:
Note: An exception to this is IdleManager; 7524 ETS format is the same as that for the 7526, but 7527 ETS does not have a delay parameter, and 7527 programs that call IdleManager must be modified with a time delay value and re-compiled.
If an API that was used is not supported by 7524 ETS, or if WaitEvent calls should be added to maintain battery operation time, the CFR source code must be modified and re-compiled and linked.
In general, you should modify the source code to include CFRAPI24.H instead of the header files used for 7526 and 7527 ETS (CFRAPI.H, DCTxxx.H, and so forth) and then re-compile the code. This provides a thorough check of which functions were used in the source. The compiler provides warning reports of any 7526/7527 functions that were used but are not supported in the CFRAPI24.H.
7524 Interface Support for OS/2 and Windows NT supplies a Native Server API through which DCConnect or other terminal controller/server programming can communicate with 7524 ETS running in the IBM 7524 Radio Frequency Terminals. When using DCConnect, you do not need to know anything about this Native Server function or interface; DCConnect takes care of all of this for you. However, if you want to use 7524 terminals running 7524 Extended Terminal Services without using DCConnect, the Native Server provides a valuable set of tools for use with your own programming.
The Native Server is an executable file (NUI_SERV.EXE) that issues status information to the console. The Native Server writes status information to standard output only and does not require nor solicit console input. The Native Server can be started with its output redirected to the 'nul' device, a file, or a named pipe, as appropriate.
The Native Server always start at least one additional process once it has been called: its communications process. For servicing RF DCTs, it starts additional processes as defined by its configuration file NUIF_APP.
The default mode causes the Native Server to start an instance of the program associated with its terminal number as defined in NUIF_APP. The terminal controller/server programming can start multiple instances of the same program or a different program for each terminal if desired.
The program associated with a terminal (terminal program) is started whenever a 7524 RF DCT is turned on. If an instance of the terminal program for that DCT exists, it is terminated and then restarted. The terminal program itself handles all DCT initialization and other procedures when it is called, which always occurs when the DCT is powered on. For this reason, messages from the terminal indicating a power-up event are not explicitly passed on to the terminal program.
Multi-connect mode must be specified for each DCT that is to employ it, thereby allowing a group of DCTs to operate in multi-connect mode while others are operated with instances of individual terminal programs. Only one multi-connect group can be used. Multi-connect mode is specified in the Native Server configuration file NUIF_APP by prefixing the name of the terminal program with a tilde ( ~ ) character.
The first DCT in the multi-connect group that is powered on after Native Server startup causes a single instance of the terminal program to be started. Once started, the terminal program will not be terminated by DCT power-up events. A DCT operated in Native Server multi-connect mode will be notified when the DCT is powered on. It is the responsibility of the terminal program to watch for these events if they are needed for DCT initialization (reload the 7524 application, for example).
In multi-connect mode, all data from all DCTs in the group is sent to the single instance of the terminal program. It is the responsibility of the terminal program to route incoming and outgoing data properly using the DCT address (terminal number).
The following screens show the configuration of the Native Server using the program NUI_CFG.EXE. This program replaces all manual file editing with menus. NUI_CFG.EXE's first menu allows you to set communications, application, terminal power-up and Native Server runtime options as shown.
Communications parameters for the Native Server session are set in the Communications Setup screen.
The Communications Setup screen is used to select and configure the communications port to be used with the Native Server. Item 5, "Enh Poll", is a performance improvement for use with the 7524-301/302 controller only and is not functional in version 3.00 of the Native Server.
The following screen is used to configure application programs to be started by the Native Server. This screen lists up to 15 separate applications, but only one should be used because 7524 Extended Terminal Services will not allow selection of an application by the operator; the application to be run must be set in the Native Server Run Time Options screen.
The entire path name for the application must be specified. If the first character of the application path name is a tilde ( ~ ), that application is a multi-connect application, and all terminals associated with the application will communicate with a single instance of the application.
The application program.exe is started when the first terminal is powered on, and all terminal traffic is routed to this application. You should not have this application started outside the Native Server's control.
The terminal sign-on, or power up message, is defined on the following screen. For the 7524 Extended Terminal Services system, the opening screen capability is not necessary and should not be used.
The last screen shows the Runtime Options. Item 4 "Auto start app" is the most important for the 7524 implementation and should be set to a nonzero value (should be set to match the single application number in the Applications Setup screen).
Item 2 "Server ID" lets you run up to 10 instances of the Native Server, from 10 different directories. Each would use a different device name (for example, COM1, COM2, and so forth) and would communicate with separate 7524-301/302 RF controllers.
The Native Server implements an API called by the nui_api() family, contained in the source code module NUI_FUNC.C. When the Native Server is first started, it will establish communications with the RF network. When the first terminal powers on (or responds with its power-on message if it is already on), the terminal program that the Native Server starts must first open the Native Server using nui_api_open(). This establishes the appropriate queues between the Server and the API. The terminal program must close the Server using nui_api_close() when it has completed.
The nui_api() family also provides read and write functions for communicating with the RF DCTs.
When using the binary mode of the Native Server API, all data passed between a DCT and the Native Server API is unmodified. Any addressing, commands, or other data that might be required by the RF system itself will be added and stripped off transparently to the process interfacing to the API. In Server Native mode, the Native Server API will be compatible with the present API.
Because the nui_api() family provides fully binary data transfer, event data normally sent as a message using the Native Data Stream is provided by the following return values.
Return Code | Meaning |
NUI_OK | Normal completion. |
NUI_STOP | This value indicates to the application that the Native Server wishes it to terminate. If it does not terminate within 15 seconds, the Native Server will terminate it. The application will receive this event if the Native Server is shut down or reset, or if an error is detected. |
NUI_DEAD | This value informs the application that the associated RF terminal has not been passed a message for a predetermined length of time. The application can act on this event or ignore it. This code could be returned if an operator went to lunch and left the terminal powered on, for example. |
NUI_TIMEOUT | This value is returned if there is no data available for the application to read from the Native Server. It is returned at the expiration of the timeout if no data is available. Your application can do idle processing or simply reissue the read. |
NUI_BAD | This code indicates that a fatal error occurred that prevents continued execution. |
NUI_BOOT | This value is returned if the associated RF terminal powered on. It can be used to reload data into the terminal, or it can be ignored. |
This function establishes a dialog with the Native Server. It must be called before any other API function. It is ignored if a dialog is already open.
Note: Use only the NUI_BINARY stream type defined as follows when communicating to a 7524 running 7524 Extended Terminal Services.
#define NUI_BINARY 1 /* binary data stream */ #define NUI_NATIVE 2 /* Native data stream */ #include "nui_func.h" rc = nui_api_open (int stream); int rc; Return value as specified in Return Codes (SeeReturn Codes) int stream; Defines data stream. If NUI_NATIVE is specified, all data written to nui_api_write() must be syntactically correct Native commands with the initial W and the terminal address omitted. This is identical to nui_func(). The specified data stream remains in effect until the Server is closed. |
This function writes data to the Native Server. The maximum number of bytes that can be written per call is 1024.
#include "nui_func.h" rc = nui_api_write (tnum, data, count); int rc; Return value as specified in Return Codes (SeeReturn Codes) int tnum; Must contain terminal number to send data to. If the terminal number is (-1), the Server will use the terminal number associated with this process (in multi-connect mode, the terminal number must be explicitly specified). unsigned char *data; Pointer to buffer containing the data to write. int *count; On entry, number of bytes to write from buffer; on return, contains the number of bytes actually written. |
This function is used to read data from the Native Server.
#include "nui_func.h" rc = nui_api_read (timeout, tnum, buffer, count); int rc; Return value as specified in Return Codes (SeeReturn Codes) . int timeout; Specifies the number of seconds to wait on read. If the timeout expires before data becomes available, NUI_TIMEOUT will be returned. The timeout value can range from 0 (no wait) to 1800 seconds. int *tnum; On return, will contain terminal number from which data was received or with which the return value is associated. unsigned char *buffer; Pointer to the buffer to contain the data read. int *count; On entry, specifies size of buffer; on return, contains the number of bytes actually read |
This function is used to write a message to the Native Server console. It is necessary because standard I/O is redirected to the DCTs.
#include "nui_func.h" rc = nui_api_con (string); int rc; Return value as specified in Return Codes (SeeReturn Codes) . char *string; Null-terminated message to write to Server console. |
This function closes the dialog with the Native Server. It is ignored if no dialog exists.
#include "nui_func.h" rc = nui_api_close (); int rc; Return value as specified in Return Codes (SeeReturn Codes) . |
Table A-1. Key Definitions
| Commands | 7524 ETS | 7526 | 7527 ETS |
|---|---|---|---|
| Original 7494-ELF Commands | |||
| :0 Display message (MSG) | X | X | X |
| :1 Read badge (FB) | X | X | X |
| :2 Keyboard input, numeric (NK) | X | X | X |
| :3 Keyboard input, alpha-numeric (AK) | X | X | X |
| :4 Keyboard or badge input (KB) | X | X | X |
| :8 Link (SF) | X | X | X |
| :9 Key not used (N/A) | X | X | X |
| ;0 Hot key (HF) | X | X | X |
| ;1 Variable badge/stripe read (DB, VB) | X | X | X |
| ;2 Latching function (LF) | X | X | X |
| String commands | |||
| :F Append (APND) | X | X | X |
| :H Clear (CLRD) | X | X | X |
| :J Format (FRMT) | X | X | X |
| Display commands | |||
| :E Show (SHOW) | X | X | X |
| :T Clear (CLRS) | X | X | X |
| :U Set cursor (CURS) | X | X | X |
| DIDO commands | |||
| :M DI read (RDDI) |
| X | X |
| :N DI wait (WTDI) |
| X | X |
| :P DO write (WRDO) |
| X | X |
| Input/Output | |||
| :R Read - excluding RS-232 port for 7524 (READ) | X | X | X |
| :W Write - excluding printer for 7524 (SEND) | X | X | X |
| Miscellaneous commands | |||
| :6 Write to display in CMD D (N/A) | X | X | X |
| :A Auto transaction state (AUTO) | X | X | X |
| :D Delay (DLAY) | X | X | X |
| :G Go to line/label (GOTO) | X | X | X |
| :GS Go to subroutine (GOSUB) |
| X |
|
| :I Transaction buffer mode (MODE) | X |
| X |
| :K Verify (VRFY) | X | X | X |
| :L Label (LABEL) |
| X |
|
| :Q Quit transaction send current data (TERM) | X |
| X |
| :S Set UV character shift offset (N/A) | X |
| X |
| :X Screen editing markers (BNAV, ENAV) |
|
| X |
| :Y Screen editing input/jump points (NAV, INAV) |
|
| X |
| :Z On key Goto (ONKEY) | X | X | X |
| :ZS On key Gosub (ONSUB) |
| X |
|
| ;7 Append to user variable in CMD D (APNDSTR) | X | X | X |
| ;C Set LED (LED) |
| X | X |
| ;A Alias transaction ID (AKA) | X | X | X |
| ;M Execute CFR (CCFR) | X | X | X |
| ;N Test user variable (TEST) | X | X | X |
| ;O Save/restore cursor to/from UV (N/A) | X |
| X |
| ;R Return from subroutine (RETURN) |
| X |
|
| Commands | 7524 ETS | 7526 | 7527 ETS |
|---|---|---|---|
| 0 Reset terminal | X | X | X |
| 1 Transmit terminal status | X | X | X |
| 2 Write to terminal display | X | X | X |
| 3 Transmit BIOS version | X | X | X |
| 4 Set terminal TOD | X | X | X |
| 5 Audible tone | X | X | X |
| 6 Transmit terminal features | X | X | X |
| 7 Transmit TOD to host | X | X | X |
| 8 Specify polled buffer | X | X | X |
| 9A Send file status | X | X | X |
| 9B Initialize text file | X | X | X |
| 9C Load text file | X | X | X |
| 9F Transmit file contents | X | X | X |
| 9G Erase files | X |
| X |
| A On/Off line | X | X | X |
| B Positive host acknowledge | X | X | X |
| C Negative host acknowledge | X | X | X |
| D Download transaction | X | X | X |
| F Storage query | X | X | X |
| G Test event handler | X | X | X |
| I Set user variable | X | X | X |
| IM Set multiple user variables | X |
|
|
| K Transaction release | X |
| X |
| L Loopback test | X |
| X |
| MA Send CFR status | X | X | X |
| MB Allocate CFR file | X | X | X |
| MC Load CFR file | X | X | X |
| MD Start CFR | X | X | X |
| NA Send validation file status | X |
| X |
| NB Initialize validation file | X |
| X |
| NC Load validation file | X |
| X |
| ND Signal validation file load complete | X |
| X |
| O Write to terminal display with attributes | X | X | X |
| V Remote validation response | X | X | X |
Table A-3. CFR Functions/APIs
| Function/API | 7524 ETS | 7526 | 7527 ETS |
|---|---|---|---|
| CFR Functions | |||
| ComGetAppVector |
|
| X |
| ComGetIntVector |
|
| X |
| ComGetMdmCtl |
|
| X |
| ComGetNetPort |
|
| X |
| ComGetParms |
|
| X |
| ComGetProtocol |
|
| X |
| ComQuery |
|
| X |
| ComQueryData |
|
| X |
| ComRead |
|
| X |
| ComReqDownload |
|
| X |
| ComSetAppVector |
|
| X |
| ComSetBuffer |
|
| X |
| ComSetIntVector |
|
| X |
| ComSetMdmCtl |
|
| X |
| ComSetNetPort |
|
| X |
| ComSetParms |
|
| X |
| ComSetProtocol |
|
| X |
| ComTapRdy |
|
| X |
| ComTapRead |
|
| X |
| ComTapWrite |
|
| X |
| ComWrite |
|
| X |
| DidoQuery |
|
| X |
| DidoRead |
| X | X |
| DidoSet |
|
| X |
| DidoWrite |
| X | X |
| KbdGetShift | X |
| X |
| KbdQueryData |
|
| X |
| KbdQueryPost |
|
| X |
| KbdReadAscii | X | X | X |
| KbdReadAsciiRec |
|
| X |
| KbdReadMakeBreak |
|
| X |
| KbdReadMakeBreakRec |
|
| X |
| KbdReadScan |
|
| X |
| KbdReadScanRec |
|
| X |
| KbdSetBuffer |
|
| X |
| KbdSetEcho |
|
| X |
| KbdSetKeyTables |
|
| X |
| KbdSetShift |
|
| X |
| KbdWaitAsciiRec |
|
| X |
| KbdWaitMakeBreakRec |
|
| X |
| KbdWaitScanRec |
|
| X |
| KbdSetMode |
| X |
|
| MemAlloc |
|
| X |
| MemFree |
|
| X |
| MemQuery |
|
| X |
| PrtChar |
| X | X |
| PrtInit |
| X | X |
| PrtQuery |
| X | X |
| PrtQueryData |
| X | X |
| PrtSetBuffer |
| X | X |
| PrtSetStatus |
| X | X |
| PrtStr |
| X | X |
| RtcGetAsciiDate | X | X | X |
| RtcGetAsciiTime | X | X | X |
| RtcGetDate | X |
| X |
| RtcGetFormat |
|
| X |
| RtcGetTime | X |
| X |
| RtcSetDate |
|
| X |
| RtcSetFormat |
|
| X |
| RtcSetTime |
|
| X |
| SenActLed | X | X | X |
| SenQuery |
|
| X |
| SenQueryData | X |
| X |
| SenRead | X | X | X |
| SenSet |
|
| X |
| SenSetBuffer |
|
| X |
| SenSetDiscrimGroup |
|
| X |
| SenSetGlobalParams |
|
| X |
| SenSetVector |
|
| X |
| SpkBeep | X | X | X |
| SpkQuery | X |
| X |
| TchQuery |
|
| X |
| TchQueryData |
|
| X |
| TchRead |
|
| X |
| TchSet |
|
| X |
| TmrCountRead |
|
| X |
| TmrCountWrite |
|
| X |
| TmrGetInt |
|
| X |
| TmrRead |
|
| X |
| TmrSetInt |
|
| X |
| VioClear | X | X | X |
| VioGetCurPos | X | X | X |
| VioQuery | X | X | X |
| VioReadCell | X |
| X |
| VioReadCellStr | X |
| X |
| VioReadChar | X |
| X |
| VioReadCharStr | X | X | X |
| VioRestoreCurPos |
|
| X |
| VioRestoreCurType |
|
| X |
| VioSaveCurPos |
|
| X |
| VioSaveCurType |
|
| X |
| VioSelCharSet |
|
| X |
| VioSelMode |
|
| X |
| VioSetFont |
|
| X |
| VioSetCurPos | X | X | X |
| VioSetCurType | X | X | X |
| VioWrtCellString | X |
| X |
| VioWrtCharStr | X | X | X |
| VioWrtCharStrAtt | X |
| X |
| VioWrtNatt |
|
| X |
| VioWrtNCell |
|
| X |
| VioWrtNChar | X |
| X |
| VioWrtPixel |
|
| X |
| LockQuery |
|
| X |
| LockSet |
|
| X |
| NmiCritSectEnter |
|
| X |
| NmiCritSectExit |
|
| X |
| NmiGetAppVect |
|
| X |
| NmiSetAppVect |
|
| X |
| PftReset |
|
| X |
| PftQueryReset |
|
| X |
| PftQueryPost |
|
| X |
| PftSetAppRestartEntry |
|
| X |
| PftSetExcHandler |
|
| X |
| PftStatus |
|
| X |
| HitWatchdog | X | X | X |
| CFR APIs | |||
| AliasTransID | X | X | X |
| CallKeyDef | X |
| X |
| ClearUserVariable | X | X | X |
| DataFile | X | X | X |
| GetTermAddress |
| X |
|
| IdleManager (see Note below) | X | X | X |
| MaxMemory | X | X | X |
| PntrFile0 | X | X | X |
| ProcBufferedHostCmds |
|
| X |
| QueryTransactionCnt | X |
|
|
| ReadUserVariable | X | X | X |
| ResizeFile |
|
| X |
| SendTransaction | X | X |
|
| ShowClock |
|
| X |
| TransactionMsg | X | X | X |
| Validation | X | X | X |
| WaitEvent | X |
|
|
| WriteToTrans | X | X | X |
| WriteUserVariable | X | X | X |
| ProcBufferedHostCmds |
|
| X |
Note: 7524 ETS and 7526 require time delay parameter.
(1) Set Host speed, data bits, stop bits, and parity. Host speed needs to match the controller (9600, 19200, 38400,...), Data bits should be 8, stop bits should be 1, and parity should be none.
(2) You can tune your system for maximum performance by observing the Heart Beat monitor on the 7524-301 controller's display panel (listed underneath HB on the display). Observe the maximum value shown during typical operation, and set the MAX RTC SLOTS to this value.
Setting the value too high results in lower response time to active terminals as inactive terminals are being given a time slot on which to communicate.
Setting the value too low results in excessive collisions of terminal communications back to the bases.