Updated March 5, 2001
The purpose of this document is to provide "How to" information on DCConnect, shortcuts, "gotcha's", workarounds, and productivity enhancements.
Two rules apply to all the information presented herein:
In order for a CFR running in mode 2 be able to append to the transaction buffer or to send a transaction, you have to use CallKeyDef() to call a transaction program to do this on behalf of the CFR. When a CFR is called in mode 2 (function 0 or function 2), no transaction program is running and so certain resources such as the transaction record are not set up. In this situation, the CFR code must put the data that should be appended to the transaction into a user variable (10 or greater) using the API WriteUserVariable() and then use CallKeyDef() to call a transaction program to take the data from that user variable, APND it to the transaction buffer and then SEND it.
A CFR is called in mode 1 when a transaction program is running and the CCFR command is used. In this case the transaction buffer is initialized so the CFR can use WriteToTrans to append to that transaction buffer. However, there is no CFR API in the 7527 that allows the CFR to send the transaction. In addition, CallKeyDef() cannot be used to call a transaction program to do the SEND because a transaction program is already in progress (the one that called CCFR). Therefore a CFR called in mode 1 must return to the transaction program which can then do the SEND command.
Note: When a mode 2 CFR uses CallKeyDef to call a transaction program, that transaction program cannot use CCFR to call back into the CFR since the CFR is already running. This is the converse situation to a mode 1 CFR being unable to use CallKeyDef to start another transaction program - since the transaction program that called the CFR is already running.
Mode 1 vs mode 2 is somewhat tricky to understand. A single CFR can be used in mode 1 and mode 2 at different times. Mode 2 is often referred to as a CFR that never returns from case 0 or case 2 - basically taking over the terminal. However, whether or not the CFR returns from function 0 or function 2, the same rules apply because the issue is whether or not a transaction program is already in running when the CFR is called. When the terminal is put in service (function 0) or powered on (function 2), the CFR is called and no transaction is in progress. Whether or not the CFR ultimately returns, if a transaction needs to be sent, CallKeyDef has to be used and WriteToTrans cannot be used.
Conversely when the CFR is called from a transaction program using the CCFR command, regardless of what function number is passed in, if a transaction needs to be sent, the CFR must return to the transaction program in order to call the SEND command; the CallKeyDef API cannot be used. The WriteToTrans API can be used from within the CFR in this situation.
As you develop transaction programs and CFRs for use with the DCConnect Client on one of the supported data collection terminals, you may at some point find that there is not enough room in the terminal to store all the files that must be downloaded. This is most likely to happen with Antares terminals - which have the least amount of RAM memory available.
To get around this problem, the DCConnect Client can be run with 'file paging' active. In this mode, transaction program files and validation files are loaded to the 'hard disk' of the terminal rather than directly into RAM memory. Then as transaction programs are run, only those programs and validation files that are used are loaded into memory. The least recently used programs/files are unloaded from memory if space runs out.
This feature was added to the DCConnect Client in version 1.40T and is activated by adding the following keyword to EMULATOR.INI:
FILE_PAGING = YIn conjunction with this keyword you may also need to use the LOCK_IN_MEMORY keyword to list any validation files that are referenced by a CFR in a DataFile() API call. This will force these files to always be in memory - because an address is returned to the caller of the DataFile API and this address must remain valid at all times.
Refer to the sections Keyword: FILE_PAGING and Keyword: LOCK_IN_MEMORY in the DCConnect User's Guide for more information.
As you are developing your transaction programs and testing them out in the terminal, you may find that the transaction program does something that you did not expect. To help figure out what the transaction program is doing, you can turn on the 'Stepping' mode of the DCConnect Client. When in this mode, the Client will show on the status line the next step to be performed (e.g. APND, SHOW, GOSUB, ...). If you press Enter, that command will be performed and the next step will be shown. If you press Esc, 'Stepping' mode is cancelled and the program runs normally.
In conjuction with the 'stepping mode', or at any other time, you can view the contents of user variables via the DCConnect Client menus. These menus are also where you go to turn on 'stepping' mode.
The ability to step through transaction programs and to view user variables was added to the DCConnect Client in version 1.40T. The options to perform these functions, START STEPPING and VIEW USER VAR, are found on the DIAGNOSITCS menu (which is option 3 from the main DCConnect Client menu).
Refer to the section Diagnostics Menu in the DCConnect User's Guide for more information.
The Windows/NT version of Netscape that ships on the -03 CD will cause a trap on certain PCs. The percentage of PCs is fairly low; but of course if it's happening to you then that doesn't matter. If you are experiencing problems with the Netscape such that you cannot install the DCConnect products, you must obtains Netscape for Windows/NT from another source. You can visit the Netscape site where, as of March 1998, free downloads of the Netscape browser were available.
After the new version of Netscape is installed, run the installation from the DCConnect CD again, this time specifying that Netscape should not be installed.
In some instances, you may have already installed and configured DAE for other applications. The CS2 version shipped with the DCConnect product has a fix for a problem of timing out. The current DAE plan is to incorporate this fix in the next DAE release. If the DAE version you have install on the system is at 1.31 with PTF1 and PTF2 installed, you can do the following as a work around:
The following procedure can be used to generate a text input file from a 16-bit DCC/2 .VAL file. This procedure makes use of the TEDIT editor on OS/2 which comes with OS/2 3.x and 4.x. We'll use SAMPLE.VAL as the 16-bit .VAL file in this example:
tedit sample.txt
c/x/y/To get the record separator and line feed characters, the num lock key will need to be active and you'll need to use the Alt-nnn key combination to get the character. So in place of the 'x' above, press and hold the Alt key and type 30 on the numeric keypad; then release the Alt key. In place of the 'y' above, press and hold the Alt key and type 10 on the numeric keypad; then release the Alt key.
Once you get the proper command line, press Enter.
Between notepad and edit I'd recommend using notepad. However, neither one lets you specify the line feed character for the target of the change operation so you have to manually change every record. If you have a different editor which allows the line feed character to be typed as the target, then use that editor instead. If using notepad, do the following after you bring the file into the notepad editor:
New with fix pack D for the 1.4.0 version of the DCConnect Transaction Building Tool is a utility that can combine a top-level DCTPB program file with all imbedded files to form a single listing file which can be useful for analyzing the programs or for searching through them.
Refer to the DCConnect Transaction Building Tool User's Guide for more information (search for IMBEDSCR.EXE).
This same utility can be used with Transaction Connection scripts!
Prior to fix pack D for the 1.4.0 version of the DCConnect Transaction Building Tool, you could not mix the use of the MESSAGE command and the use of inline messages in the same set of transaction programs. (Inline messages are those that are specified directly in the SHOW, APND or SEND commands using double quotes surrounding the message text). In the past, if both kinds of messages were intermixed, you would see that in some cases the wrong message was displayed when running the transaction programs.
With fix pack D, the Building Tool was changed to do a two-pass compile so that it could handle both kinds of messages simultaneously.
When the 1.4.0 DCConnect CDs were created, the products were built using the latest fix packs for the IBM Visual Age C++ compiler. The way the Visual Age compiler is set up, there are certain compiler DLLs that must be shipped with the product. One of these is CPPWOT3.DLL. Other products built using this compiler also use this DLL and also must therefore ship them. Once example, is IBM's DB2 Universal Database.
A problem arises when different products are using different levels of these DLLs. Whichever product is first is in the path is the one whose DLLs will be used. Other products which were built expecting different versions could have problems.
This is the case with CPPWOT3.DLL, which is used by DCConnect, DB2 Universal Database and in the License Use Management software of several products. Prior to the 1.4.0 CDs, DCConnect's version was in synch with these other products. With the 1.4.0 CDs, DCConnect's version of this DLL is now later. And if DCConnect is in the path after the other products, then you see the problem with the large transaction program icons.
The problem can be solved by renaming the other copies of the .DLL on the system to something like CPPWOT3.HID so that DCConnect's version is the one that is found. As of yet we have not heard of any negative side-effects of doing this. You may find CPPWOT3.DLL in the following directories as well as other places:
c:\sqllib\bin c:\ifor\win\bin
To find all copies of CPPWOT3.DLL on your Windows/NT system, use the Start -> Find -> Files or Folders option. Fill in CPPWOT3.DLL for the 'Named' field and select 'Local hard drives (C: ...)' for the 'Look in' field. Also make sure the 'Include subfolders' check box is checked. Then press the Find Now button to start the search. All matching files will be listed in the box below. You can rename the file directly from this window using the right-mouse button on the name and selecting the Rename option.
Another possible workaround is to change the path so that the DCConnect \DCCONN\DLL directory comes before the others. Changing the path is usually best done with great caution - therefore this is not the recommended solution.
On systems with Windows/NT version 4.0 that do not have service pack 3 of NT installed, we see a lot of traps in the DCConnect GUI - particularly when shutting down the GUI. The installation of service pack 3 for Windows/NT makes this problem go away.
There are two known reasons why the help in the DCConnect GUI may not work properly on Windows/NT systems:
When different versions exist, the symptom is usually that the DCConnect GUI traps or just disappears when you select any help function.
You can verify this by looking for the indicated .DLL files on your harddrive. If found elsewhere, you'll need to either rename those other occurrences or change the PATH statement in your environment (Control Panel -> System -> Environment tab) such that DCCONN\DLL comes before the directories of the other products that are in conflict.
The PATH statement can be shortened through the Windows/NT Control Panel, System icon on the Environment tab. You may be able to eliminate duplicate references or references to samples directories that are not important. You may also have to convert long path names to their short (8.3) equivalent.
The system message viewer can take quite some time to come up if you use the GUI to bring it up. It's much quicker to simply go to the /DCCONN/DATA subdirectory and either edit or type the MESSAGES.DAT file. The structure of this file is to wrap and overwrite the oldest record after it's filled, so to find the latest messages in the file, perform a search and look for "-------------". Two lines of dashes indicate the wrap position.
The system message viewer shows multiple types of messages - some start with DCRxxx, and others don't. The messages starting with DCR are messages that come from the DCConnect Server (runtime). These messages pertain to terminal control, communications, etc. The messages without numbers come from the GUI as a result of configuration, job building and other actions. Some are startup errors which are logged only when the Server is started. Specifically the message "Terminal is not configured in DCC/2" indicates a terminal which is defined somewhere in DCConnect, say in Mailbox Configuration, but not in all the other places which are required (like Node Configuration, Function Group Configuration). These terminals need to be FULLY configured before this message goes away at startup time. Note: The "DCC/2" displayed in this message is our mistake and will be fixed in the next release.
Since DCCONN/BIN is party of the path, you can start the DCConnect User Interface from a command line by entering:
DCCONN
Older models of the 7526 terminal did not support the parallel port being used for a printer. If you have one of these models and in the DCConnect terminal notebook for the terminal, the Devices->Parallel Devices->Parallel Port Setting parameter is set to 'Printer', the download will fail as described.
To fix this problem, change the setting to anything except for 'Printer', save the configuration and retry the download.
If your 7526 terminal is assigned to a serial port on the PC or on an ARTIC card be sure the line is set for 8 data bits, no parity and 1 stop bit. The initialization of the CFR involves binary data that can't be represented properly with just 7 bits of data.
The CFR is always initialized, even if none is assigned to the terminal. We have to be sure to remove a CFR from the terminal if one was previously assigned but no longer is. The initialization of the CFR to remove it from the terminal is a recent addition to the server code. Therefore this is a problem that may show up after installing the latest DCConnect software.
While the DCConnect GUI can be used to start and stop the Server, it may by started from the command line by first changing to the DCCONN\BIN directory (this is very important) and the entering the following:
DCXCPOS2The only parameter which is accepted by this program is the .INI file name. It defaults to DCX2.INI which is where the GUI stores its configuration information (in the DCCONN/DATA subdirectory), but if you wish to start the Server with an alternate INI file, it may be passed as follows:
DCXCPOS2 C=xxxxxxx.INIwhere ".xxxxxxxx". is the name of your alternate file. A full path may be specified for the file name, following the "C=" portion of the parameter.
If you want the DCConnect server to be started whenever your PC reboots, it is usually not sufficient to simply drag the server icon to the startup folder. Since the server must be started in the DCCONN\BIN directory, it is better to create a command file which changes to that directory and then starts the server. An icon could than be created for this command file and that icon could be added to the startup folder.
A utility is provided in the DCCONN/BIN subdirectory called TESTTERM.EXE which permits a command line interface into the DCConnect runtime without having to start the GUI. To start this interface, in a window or fullscreen, enter:
TESTTERM termnamewhere 'termname' is the name of one of the DCConnect configured terminals. This field is case sensitive and must match exactly the name of the terminal you wish to debug. Once started, TESTTERM may be used to display the status of the terminal, download it, and a number of other terminal control functions. After it is started, the terminal name may be changed with option #16. DO NOT leave a space between the '16' and the 'terminal name' when selecting this option. This will cause the terminal name to not be found. For instance, if the terminal is called RECEIVING_A and you want to switch to that terminal name for testing, at the TESTTERM command prompt, enter the following:
16RECEIVING_Aand press the enter key. Other functions in TESTTERM are self-explanatory.
Another nice utility for debugging communications to terminals is the LINETRAC program, also in DCCONN/BIN. This utility only works with serial ports (COM1 - COM4), the RF line or the TCP/IP 75XX line. It does not support attachment via ARTIC or the TCP/IP DOS line; use the monitor in the GUI to monitor terminal activity on these lines.
To start line tracing for all terminals on COM1, for example, start a command line window or full screen and enter:
LINETRAC COM1Other parameters to use in place of COM1 include COM2, COM3, COM4, RF, TCP, TCPIP or TCP/IP.
When the line trace utility starts, it will display all communications data for the specified communications line. Commands from DCConnect and all terminals on the line will be shown. Each message indicates:
LINETRAC RF > RF.OUTWhen monitoring one of the COMx lines, the majority of commands on the line are polls issued by DCConnect, asking terminals for transactions. By default, these polls are not included in the data that the line trace utility captures. If you want to see the polls in the line trace, you can use the SHOW_POLLS parameter. For example:
LINETRAC COM2 SHOW_POLLS > COM2.OUTSince RF and TCPIP lines are not polled, the SHOW_POLLS parameter is not valid for those line types.
Sometimes a transaction that is an error is rejected by the receiving host or other application. This transaction therefore can't be sent anywhere and it blocks all transactions that are behind it in the mailbox. The application can not process any more transactions until the offending one is removed.
RELTX32.EXE can be used to view and optionally release the first transaction currently in a particular mailbox. This utility is found in the DCCONN/BIN directory.
To run this utility, open a command line session and run the following from the DCCONN/BIN directory:
RELTX32 mailboxnamewhere "mailboxname" is the name of the mailbox as defined in the DCConnect user interface. This procedure will display the all the fields of the first transaction in the mailbox and it will prompt you for an action. Press one of the following keys:
It is not necessary to bring up the GUI and manually submit a validation file when validation data changes. There is a program called SUBMIT.EXE in the DCCONN/SAMPLES subdirectory (also provided with source code) which will handle updating validation data without manual intervention if you're pretty good at building command files. Since the SAMPLES subdirectory is not placed in the path when you install DCConnect, you'll may need to move SUBMIT.EXE to some directory which is in the path; for example, DCCONN/BIN.
To submit a new or updated validation file, enter:
SUBMIT source.txt target.VALwhere "source.txt" is the raw text input for your validation file and "target.VAL" is the name of the target validation file which is referred to in the terminal's settings notebook. Note that the extension must be ".VAL".
The source name may be fully qualified with the disk/subdirectory information to allow SUBMIT to find them. If no path is specified, DCConnect assumes the source is in the DCCONN\VAL directory.
The target name cannot include any path information.
If DCConnect is running, the SUBMIT program will automatically cause the updated validation file to be downloaded to all terminals that have indicated the require it to be downloaded in the terminal settings notebook.
Since DCConnect Server limits you to one RF connection, it's possible that some customers will find it necessary to connect two 7524-302 controllers to a single system. You can use COM ports configured for NET 232 to create the bridge (38Kbps). Connect the async controller (root node) to the host via the Host port. COM2 is used as a Net 232 port, and is connected to COM2 on a second controller (Not a root) via a null modem cable. Net1 on the second controller is configured as Net485 and is attached to an RF Base. Communications will be slower than natively attached controllers, but should work.
The following documents sample configurations for various Intermec/Norand controllers and access points (bases) that we got working in the lab - which does not necessarily mean it will be right for a customer situation. Our testing involved one controller attached to one access point. When multiple access points are involved certain parameters in the access points, such as RoutePriority, will probably be different.
1) RC4030E used as a controller
Attached with null modem cable: ANSI, full duplex, 19200, N, 8, 1
[HOST] HostAlias = "HOST"
HostType =
[PORTS] Ethernet address
[Async Host] Baudrate = 19200 (must match DCConnect)
StopBits = 1 (must match DCConnect)
Parity = None (must match DCConnect)
Databits = 8 (must match DCConnect)
HostInactiveTimeout = 0
AddressType = Normal
EnhancedPolling = Disabled
MultipleBuffering = Enabled (Important)
Full Duplex = Disabled
[GATEWAY] GroupChaining
Compression
[TCPIP] IP_ROUTER = <0.0.0.0>
[ETH0] IPAddress = 99.99.99.44
SubnetMask = 255.255.240.0
[CONFIG] Password = ""
The LAN ID is set via the switches on the controller. Switches 2, 3 and
4 can be set to values from 0-7 (switch 2 = 1, switch 3 = 2, and switch
4 = 4). Switch 5 should always be on. All others should be off during
normal operation. In our testing we were using LAN ID 4, so switch 4 was
also on. Switch 11 must be turned on in order to update the flash in the
controller. See the Intermec/Norand documentation for more details.
2) Intermec 2100 Access Point with one 2.4ghz Radio
Attached with null modem cable: ANSI, full duplex, 19200, N, 8, 1
The configuration below was used with the controller configured as in #1
above.
The menus in the 2100 have some redundancy; options accessed through
one path can sometimes be accessed via other paths. Listed below are
are most of the options through all the paths. Any options not shown were
left at their default values.
[QuickStart] IPAddress = 99.99.99.200
IPSubnetMask = 255.255.240.0
LAN ID (Domain) = 4 (must match cntrllr, terminals)
2.4Ghz OpenAir Security ID = "NORANDOWL" (Important)
[Ethernet] MacAddress ...
PortControl
HelloPeriod <2 seconds>
INCAFrameType
[2.4Ghz OpenAir-A] MacAddress ...
PortControl
HelloPeriod <2 seconds>
[Master Config] Channel 1
Subchannel 1
WirelessHops
MacConfiguration
[INCA/IP] MacAddress ...
Port
HelloPeriod <2 seconds>
Mode
[Network Config] IPAddress = 99.99.99.200
IPSubnetMask = 255.255.240.0
IPRouter = 0.0.0.0
IPFrameType
DHCP
DHCPServerName "Intermec DHCP Server"
AutoARPMinutes 5
[BridgeConfig] LanID (Domain) 4
RootPriority 1
EthernetBridging
SecondaryLANBridgePriority 1
SecondaryLANFlooding
[GlobalFlooding] MulticastFloodMode
MulticastOutboundToTerminals
MulticastOutboundToSecLANS
UnicastFloodMode
ARPServerMode
[Filters] (used defaults)
[GlobalRFParameters] (used defaults)
[Summary]
Port Ethernet OpenAir-A INCA/IP
---- -------- --------- -------
MasterName ... ...
MacAddress ... ... ...
PortControl Enabled Enabled Enabled
HelloPeriod 2 2 2
Network Bridge
------- ------
IPAddress 99.99.99.200 LAN ID 4
IPMask 255.255.240.0 Root Priority 1
RouterIP 0.0.0.0 Bridge Priority 1
AutoARPPeriod 5
DHCPState Enabled
DHCPServerName Intermec DHCP Server
3) 6710 Access Point with 900 mhz OWL (Falcon) radio
Attached with null modem cable: ANSI, full duplex, 9600, N, 8, 1
The configuration below was also used with the controller configured as
in #1 above.
[TCPIP] IPRouter = 0.0.0.0
[Eth0] IPAddress = 99.99.99.200
SubnetMask = 255.255.240.0
Type =
[Bridge] SerialNum = ...
LAN ID = 4
RootPriority = 1
BridgePriority = 1
[PortTable]
[1] Name = "Omde"
MacAddr = ...
Port
HelloPeriod = 2
[Ethernet] Type
BridgeFlags
[StaticAddrTable] (used defaults)
[2] Name = "omdflca"
MacAddr = ...
Port
HelloPeriod = 1
[Falcon] BridgeFlags
[Falcon] FileName = "falcon_d.29k"
Mode/channel = DS225K/Channel25
[3] Name = ""
...
[FilterValueTable] (used defaults)
[FilterExprTable] (used defaults)
UniFloodLevel
MultiFloodLevel
AwakeTime 0
NetName ""
[DixTypeFilters] (used defaults)
[Config] Password = ""
The most common cause of this is having the terminals assigned to the wrong DCConnect Mailbox. Open the Mailbox Configuration folder in DCConnect and check the transaction count for the configured mailboxes by selecting VIEW - DETAILS VIEW. If the transactions are being routed to the correct mailbox, check the MAPICS Settings Notebook page and ensure the Mailbox name listed is exactly like the one in DCConnect Mailbox Configuration. Remember that this field is case sensitive.
This can also be caused by renaming any of the MAPICS function groups in DCConnect. AHISS/TC formats and routes the transactions based on the Function Group to which the terminal is assigned, and the function key that was pressed. If the DCConnect function group names have been changed, the HCMxx.SCR file must be changed to match the new names.
For instance, in the HCMxx.SCR file, the command
StartFunctionGroup ( XA262A )starts the Discrete Manufacturing function group commands for the 7526 Model 200 terminal. If, in DCConnect, the function group sending these transactions is called "DM7526" or something else, AHISS/TC will not have a set of commands designed to process those transactions. If AHISS/TC receives transactions for which it has no defined actions, it will release the transaction from the logfile and after 3 releases will stop. If the AHISS/TC session continually stops after having successfully started and signed-on, this is the most likely cause.
Key assignments, such as the
StartKey ( F1 )within the scripts are not affected by reassignment of keys since every MAPICS transaction program starts with an AKA (Also Known As) command which sends the correct Key ID, regardless of the key to which the transaction program is bound.
The TC or AHISS application most likely had a problem connecting to the correct emulation session. Ensure the emulator is up and running, and that the Short Session ID assigned in the ERPBridge for MAPICS Settings Notebook is not in use by some other process.
If it successfully connects, signs on and after a few seconds goes to a "Completed" status, it is probably because the AHISS/TC session has received transactions for which it has no script defined. This is caused by renaming the Function Group. AHISS/TC will release only 3 transactions for which it has no script before it shuts down.
This can be caused by a number of conditions. Check the following:
This will occur if the row/column position of the User ID, Password, Procedure and Library fields are not in the default locations or if the userid/password are unrecognized. The HCMxx.SCR file places these fields at 6x53, 7x53, 8x53 and 10x53 respectively. If these input fields have been moved in a custom sign on screen, change the row/column positions indicated in the logon subroutine of the HCMxx.SCR file.
New with fix pack D for the 1.4.0 version of Transaction Connection is a utility that can combine a top-level TC script with all imbedded scripts to form a single listing file which can be useful for analyzing the scripts or for searching through them.
Refer to the Transaction Connection Series User's Guide & Reference for more information (search for IMBEDSCR.EXE).
This same utility can be used with DCTPB programs!
If you ever have to manually make changes to the configuration of an Antares terminal via its menus, it is best to do so after making sure the DCConnect Client is not running on the terminal. If the Client is running when changes are made via the Antares menus, you might get in the situation where the terminal freezes up as the changes are being saved or it might the problem might not show up until the next time the terminal is rebooted. In some cases, the terminal may even have to be reflashed with both Intermec flash and the DCConnect Client files before it can be used again.
If you find that it often takes several attempts to scan bar codes from an Antares terminal, try enabling the Scan Ahead option in the Antares configuration. This can be done at the terminal using the Antares menus (after shutting down the Client). From the main menu, select 'Configuration Menu' then 'Terminal Menu' then 'Scanner' and change the Scan Ahead option to Enabled.
For a more permanent change that can be applied to all terminals, you can add the following to the SETUPANT.INI file:
// Enable Scan Ahead $+SD1For more information about using the Antares menus and the SETUPANT.EXE utility, refer to that section in the DCConnect Client User's Guide.
In order to be able to communicate with a 6400 terminal, or any terminal for that matter, the security ID configured in the terminal must match the security ID configured in the access point. By default the 6400 is configured to use NORANDOWL as the security ID. The only way to change this is using a special utility that would have to be loaded to each terminal. It is much easier to make sure the access points are configured to use NORANDOWL as the security ID. If other terminal models besides 6400 terminals (e.g. Janus, Antares) are on the same network, then those terminals' security IDs must also be set to NORANDOWL.
To cold-reset a 6400 terminal first make sure the terminal is powered off; you may need to remove the battery and put it back in. Then press and hold both the blue and orange shift keys (might be able to do them both with one thumb). While still holding down those shift keys, press and hold both green ENT keys at the top. Keep holding until the screen turns on. Then you can release all keys and the terminal should reset and boot up.
Unlike most other terminals, the Symbol Spectrum 24 terminals supported by the DCConnect Client (LRT3840, PDT6840, VRC3940, ...), do not automatically power off after a period of inactivity. There is a way to configure this be recompiling options into a Symbol utility but that is not very easy.
Instead, the DCConnect Client was enhanced to provide this capability. As of version 1.40X, the following keyword:
POWER_OFF_TIMER = 3can be added to EMULATOR.INI to configure the number of minutes that the terminal will power off after if there is no scanner or keyboard activity. Refer to the section Keyword: POWER_OFF_TIMER in the DCConnect User's Guide for more information.
By default, the Symbol Spectrum 24 terminals supported by the DCConnect Client (LRT3840, PDT6840, VTC3940, ...) do not automatically give a key click sound when keys are pressed. Something in the Client's use of the terminal prevents this from happening.
However, as of version 1.40T, the DCConnect Client can be configured to sound a key click by adding the following keyword:
KEY_CLICK = Yto EMULATOR.INI. Refer to the section Keyword: KEY_CLICK in the DCConnect User's Guide for more information.
To cold-start a locked up Telxon 960SL, first take out the battery and put it back in to ensure the unit is off. Then hold down the Cntrl and Enter keys and while keeping them down, press and release the on/off button. Keep holding the Cntrl and Enter keys until something happens. If nothing happens, the battery is probably dead.
If you are experiencing periodic slow downs in the Telxon network - where responses takes several seconds instead of the normal fraction of a second, make sure the following is true: