Frequently Asked Questions: PSC / Percon Products

Falcon RF Portable Data Terminal FAQ's

1. Falcon RF Connectivity Troubleshooting Guideline
2. What equipment do I need to use a Falcon RF terminal?
3. How do I configure my Falcon RF?
4. How can I connect my RF Falcon to my host system using Falcon Configuration Utility version 2.6?
5. Which PSC portable data collector would be best for my application?
6. How do I change the configuration settings for the Breezelan RF card?
7. How do I use the Symbol RF Card upgrade utility?
8. What are the latest RF drivers, and how can I tell which drivers are loaded on my Falcon RF unit?
9. How can I tell if the latest version of PowerNet is installed on a Falcon RF?
10. Is Intermec compatible with any of our Falcon RF units?
11. What IP address should I use on the Falcon if I have a DHCP server?
12. How do I get to the DOS prompt using PowerNet?
13. When I enter the IP address, the Host IP address and the Authorization Code, where is that information stored?
14. During the installation of PowerNetTN, I am prompted for an installation key.  What is that?
15. Falcon & RF Card Type Compatibility Chart

 1.  Falcon RF Connectivity Troubleshooting Guideline

While designing and installing RF applications can be very complicated, basic connectivity can be established by following some simple steps.  The intent of this guide is to help with the troubleshooting of generic network connectivity issues in which the RF Falcon cannot see or be seen by the network.  These steps work for all radios that the Falcon supports.  These steps also assume that the Falcon has been configured for the radio it is using and that the access point has also been configured and is hooked to the network.

To use this guide, answer question #1 and then proceed through the questions as directed based on your answers. Once you get to a troubleshooting procedure to try, if you still have problems, start at the beginning and answer based on the new situation.  If you need additional assistance, contact PSC Technical Support.
 

1. Ping the host system from a PC on the network.

   The Ping was successful; proceed to #2

   The Ping was not successful.  The host is not visible to the network segment that the PC is on.  Verify that the host is indeed operational and that you have the correct IP address for it. Once you can successfully ping the host from a PC on the same network segment as the Access Point, proceed to #2.

    

2. Ping the Access Point from a PC on the network

   The Ping was successful, the Access Point is communicating with the network.  Proceed to #3.

   The Ping was not successful.  Verify the correct installation and setup of the Access Point including the network connection, power supply and unique IP Address setting.  the Access Point needs to be operational before any portable activity can occur.   You will need to successfully communicate with the Access Point before attempting any communication with Falcon units that use that Access Point.  Once you can successfully Ping the Access Point, proceed to #3.

    

3. Ping the portable from a PC on the network.

   The Ping was successful, you have established connectivity with the Falcon.  Any functionality beyond this simple connectivity check will be based on the RF application you are attempting to run.

   The Ping was not successful.  The radio in the Falcon is not communicating with the radio in the Access Point.   See the section below on Access Point and Radio Configuration and then proceed to #4.

    

4. After verifying all Access Point and Falcon configuration settings are correct, try to Ping the portable again from a PC on the network.

   The Ping was successful, connectivity has been established.

   The Ping was not successful.  Ensure the radio card is seated correctly and that the antenna cable is connected in the Falcon.  Also, do a cold boot of the Falcon to ensure the current settings are in effect.

    

5. Once connectivity has been established, if you still have trouble getting the Falcon to work on the network, see the section below on RF Connectivity VS Productivity.

Access Point and Radio Configuration
If you can ping the access point but not the Falcon itself, check the antenna on the access point and ensure that the configurable options for both the portable and the access point are compatible.

All RF access points and radios supported by the Falcon (Proxim, Symbol, etc.) have configuration settings that control how the network talks to the access point and how the access point controls what radios can talk to the network.  Some of these settings share common names (like IP Address) but many of these settings have different names for each type of radio.  These names include, but are not limited to, Net#, Domain, SubChannel, and ESSID.  (This guide does not attempt to define all of the settings for the different radios so you will need to reference the documentation on your specific radio for specific help with these settings.)

The important thing to remember about these various settings is that they control if and how the Falcons communicate with the network through the access point.  This means that getting these settings mixed up will prevent the Falcon from communicating with the network.  The good news about these settings is that the default settings, as set by the Falcon Configuration Utility, work.

If you think that the settings may have become corrupted, simply use the Falcon Configuration Utility to send the required files again.  The only thing you need to do is set the basic address information for each Falcon.  (If using TCP/IP network protocol you need to set the correct IP and Router addresses, and Subnet Mask.  If using Novell network protocol, you need to set the Preferred Server and appropriate Frame.)

RF Connectivity vs. Productivity
The ability for the network to "see" a Falcon and vice-versa is only the first step in using a RF Falcon to collect data.  Just like a DOS PC being used on the network, the Falcon needs to run an application designed to utilize the network link and allow real-time data collection. 

There are two fundamental ways of doing this with Falcon.  You can run an application specifically designed for the Falcon, such as IntelliTrack RF, or you can run a terminal emulation utility on the Falcon that will allow the Falcon to link up to an existing host application that runs on terminals like PowerNet TN.

If you are able to connect to the network and do a successful ping of the portable but your application is not working, the first thing to try is reloading the application to the Falcon.  If this does not correct the problem you will need to look at specific troubleshooting information for the application itself.

 2.  What equipment do I need to use a Falcon RF terminal?

Warnings
PSC Falcon portables support several different types of RF radios. When using standard transmission protocols, like 802.11, some radios from one manufacturer may work with an RF backbone (access points, network links, etc.) from another manufacturer. It is up to the equipment reseller and/or end user to know which radios they have and/or want to use.

Solution

• RF communication with a PSC Falcon data collector is nothing more than DOS PC networking using radio waves instead of a cable to connect to the network. This means that you will need:
  • RF-capable Falcons
  • A radio for each Falcon
  • Enough radio Access Points to cover the area in which you will be working.

A software application that will run on the Falcon and can use the DOS network link provided via the radios. PSC sells one RF software application, IntelliTrack RF. PSC also sells PowerNet TN which is a terminal emulation package. PowerNet runs on the Falcon and allows the Falcon to emulate a variety of terminals normally connected via mainframe computers.

Following is a listing of the pieces needed for the different RF configurations PSC sells:

RF Component List

Symbol

• RF Falcon (See the Percon/PSC Price Book for specific Falcon variations and part numbers)
• Spectrum 24 500mW Access Point (00-500-00)
• Access Point Antenna (required)
• Single Antenna s/4´ cable (00-502-00)

Proxim

• RF Falcon (See the Percon/PSC Price Book for specific Falcon variations and part numbers)
• Proxim 500mW Access Point (00-511-50)
• Access Point Antenna (Optional - for greater coverage)
• 9dBi Omnidirectional (00-514-00)
• 5.15dBi Omnidirectional (00-513-00)
• Access Point Antenna Extension Cable (Required w/Optional antenna)
• 5´ low-loss (00-523-00
• 10´ low-loss (00-518-00)
• 20´ low-loss (00-519-00)

BreezeCOM

• RF Falcon (See the Percon/PSC Price Book for specific Falcon variations and part numbers)
• BreezeNET PRO.11 Access Point (00-529-00)
• BreezeNET Dual 5 dBi Antennas (required) (00-530-00)

Once you have decided on a radio you may also require a software package such as PowerNet TN for terminal emulation or IntelliTrack RF.  The part numbers are listed below.  If you require a network version, contact your reseller.

PowerNet TN

• Basic w/User´s Manual (00-744-00)
• Advanced w/User´s Manual (00-744-30)

IntelliTrack RF (62-012-00)

 3.  How do I configure my Falcon RF?

Warnings
There are specific system files for each of the different types of Falcons. When using the Falcon Configuration Utility, sending the wrong files can cause the Falcon to lock. Always ensure you have the correct type of Falcon selected before you send the files to the portable.

Solution

1. Install the Falcon Configuration Utility (2.3 or higher). Make sure your portable is also at the same BIOS level as the Falcon Configuration Utility you are using (you can verify this by typing REV at a DOS prompt of the Falcon). If not, run the core update utility located in the folder called COREUPD under the folder 8LINE or 16LINE respectively. These folders are under the main folder where you installed the Configuration Utility. (This is normally PERCON\FALCON). See the README.TXT file in the COREUPD folder for specific instructions for updating the Bios.
2. Run the Falcon Configuration Utility and select the corresponding radio button at the bottom of the main screen to choose which Falcon you are installing to. It is very important that you choose the correct Falcon type here, or you will send an RF configuration to your unit that could cause it to lock up.
3. Select the CUSTOM button.
4. You will now be prompted to choose a Configuration File. This file contains the basic drivers for the radio card you own. Files starting with PX are for Proxim radios and files starting with SM are for Symbol radios. Each file name corresponds to a network protocol. Choose the one which fits your network connectivity profile (e.g. PX_TCPIP for Proxim Radio Cards using the TCP/IP protocol).
5. Next you will be prompted to load a Program Set. If you have your own application, choose UPGBASE.PRS as it will only install the basic files needed on the portable.
6. Now you will be at a screen with four button bar options. Choose the first, FILE CONFIGURATION.
7. At the bottom of the menu window, click on the NEXT button twice until you arrive at a three-button window, prompting for TEXT FILE, AUTOEXEC.BAT and CONFIG.SYS.
8. Click on the TEXT FILE button so you may modify your NET.CFG settings. Your NET.CFG file is separated by which Falcon you have and the network card type in the directory structure (e.g. the NET.CFG for a Falcon 315 with a Proxim Radio is located in the C:\PERCON\FALCON\8LINE\RF\PROXIM directory).
9. Modify and save your NET.CFG parameters.  (Note:  The NET.CFG file referenced here is used for Falcons running Bios version 2.5 and earlier.  Falcons running Bios 2.6 and later will need to make these changes to the SOCKET.CFG file which is found in this default path:  C:\PERCON\FALCON26\RF\NETWORK.)

   If you are making modifications for an IPX network (Bios version 2.5 and earlier), you only need to change the PREFERRED SERVER settings and possibly FIRST NETWORK DRIVE. Your binding to 802.2 and 802.3 are already assigned.

   If you are making modifications so your portable will interact with a network over TCP/IP, then you only need to add the following:

   • The Falcon's IP address
   • The subnet address the Falcon will be connecting to
   • A router IP address (if necessary)

After these features are updated, choose DONE and select DOWNLOAD to transmit to your portable.

 4.  How can I connect my RF Falcon to my host system using Falcon Configuration Utility version 2.6?

In order to connect to the network using the Falcon Configuration Utility v. 2.6, you must add the socket.cfg file to the list of application files to download to the Falcon. If you are using TCP/IP as the protocol, the IP address, subnet mask and router must be put in the socket.cfg file.

Step 1:

• Open the Falcon Configuration Utility, click the CUSTOM button.  A screen will appear where you are to choose the configuration files to be loaded to your Falcon. 
• Depending on which RF card is in your unit, and the protocol you are using, select the appropriate card.  For example, if you are loading the Symbol Spectrum 24 card that uses the 802.11 protocol, select the S802tcp.cfg file. (A complete listing of the files offered and the corresponding RF card is listed below.)
• Click OK.  (You can view the contents of the configuration file by opening it in Notepad.  To do this from within the Falcon Configuration Utility, right click the file then select Open With.. (or Open) from the dropdown box.  If you selected Open With, choose Notepad to view the file.  If you chose Open, your file should open.)

Step 2:

• Another screen will appear where you are to choose a program setting file for your Falcon.  This file determines the lengths and types of barcodes you are scanning with the Falcon. The default.prs file will be selected by default and may be used to connect to the network.  You can change the settings at a later time in the installation if you wish. For example, if you do not want users to scan I 2 of 5 barcodes longer then 10 characters, you can set the maximum length to 10.  Select the file you wish to download to the portable and click Open.

Step 3: 

• The next screen that appears has four buttons you can choose from.  Select the button labeled 'File Configuration'.  The list of files located under the title 'Application Files' lists the files that will be downloaded to your Falcon.  You must add the SOCKET.CFG file to this list.
• Select the ADD button, then the BROWSE button
• Click on the RF folder located in the OPEN pop-up box. 
• Select the NETWORK folder.  Inside the NETWORK folder change the  "Files of Type:" prompt at the bottom of the pop-up screen to read 'ALL [*.*]' . 
• The SOCKET.CFG file should appear.
• Highlight the SOCKET.CFG file. 
• RIGHT click on the file.  A drop down box should appear.
• Select Open.  The SOCKET.CFG file should open and you can enter your IP address, Subnet Mask and Router. 
• Make sure you save the file after editing it by clicking FILE and SAVE.
• Click Open.  The File Selection screen should appear showing the paths of a) where the file is located on the PC and b) where the file is to be placed on the terminal. 
• Edit the location of the file on the portable to read C:\NET\SOCKET.CFG. Click OK. 
• The application list should now appear and the SOCKET.CFG file should be in the list of files under the title 'Application Files'.
• Also notice the NET.CFG files.  There are two listed and which one you will use depends on the type of Falcon you are using.  If you are using the 310 or 315, then select the Net31X.  If you are using the 320, 325, 330 or 335, then select the Net32X.  Depending on the RF Card manufacturer you have chosen, you may need to edit this file to reflect the appropriate NET_ID or Domain.   Please refer to the documentation provided by the manufacturer of your RF card for more detailed information on this topic.

Step 4: 

• Click the next button at the bottom of the screen. 
• Select the appropriate items you wish to add and select NEXT. 
• If you wish to add anything to the Autoexec.bat, Config.sys or the text file, you may do so at this screen by selecting the appropriate button.  Also, be sure that the appropriate Falcon type is selected under 'Select Product'.  Then select Done.

Step 5:

• Click on the COMM SETTINGS button and ensure that the appropriate COMM Port and baud rate are selected.
• Click OK to return to the File Configuration screen.

Step 6:

• Select Download.
• After the files you wish to download are ready to be transferred to the portable, a screen will appear that asks you to type LD at the DOS prompt on the portable. 
• Type LD and click enter on the PC.  The files should transfer from the PC to the Falcon. 

Step 7: 

• At the end of the transfer, you will see an error message that says 'Insufficient Disk Space'.  This is a cosmetic error only and will not prevent your unit from connecting to the network in any way. 
• After the file transfer is complete, reboot the unit. 
• Once the unit is back at the DOS prompt, try to PING the portable from a PC connected to your network. 
• To do this, go to the DOS prompt and type 'PING XXX.XXX.XXX.XXX' , where the X's are the address you gave to the portable. If it is successful, you will see a reply from the portable.  If you do not, FORMAT the Falcon and try the above steps again making sure all of your configurations are set correctly, such as your IP address, your Domain or NET-ID and other configurations which can prevent you from connecting to the network.

Step 8: 

• You will be asked to save the configuration file after clicking EXIT.
• Choose YES and save the configuration with an appropriate name.  The next time you need to configure a Falcon with this configuration, all you need to do is select it under the Configuration menu.  The Socket.cfg will automatically be placed in the list of files to download so you will not need to add it again, although if you are using it to configure multiple Falcons, you will need to change the IP address information for each unit you are configuring.

 5.  Which PSC portable data collector would be best for my application?

The Product Selection Guide is available in Adobe Reader PDF format.

 6.  How do I change the configuration settings for the Breezelan RF card?

BreezeCom uses the program "BRZSETUP" to create an .ini file which is then transferred to the Falcon RF.  The settings created using the the BRZSETUP program must match the settings on the AP or you will not be able to connect to the network using your Falcon.  The steps below outline the the procedure that should be taken when configuring a BreezeCom card with TCP/IP using the Falcon Configuration Utility.  This FAQ assumes the operating system is Windows-based (NT, 95, 98).

1. Using either My Computer or Windows Explorer to to the C:\PERCON\FALCON\RF\BRZCOM directory.
2. Copy the BRZWLAN.INI file to the C:\TEMP directory.
3. After copying the file double click on the BRZSETUP.EXE file located in the C:\PERCON\FALCON\RF\BRZCOM directory.
4. A program should run that will prompt you to "Enter path of INI file:."  Type in C:\TEMP\BRZWLAN.INI and then press Enter.
5. A screen should appear titled "BreezeCOM SA-PCR SETUP Ver 04.03.00.06."   Note:  If this screen does not appear and you get an Error, Ill path! (press any key to continue) message then go back to the first step.  This error message indicates that BRZWLAN.INI is not in the location specified.
6. Configure the settings to be changed using the various function keys offered on the screen.  If you are unsure of what a particular setting is used for choose F1 for Help.
7. After changing the desired settings select F2 to Save.
8. Press Esc to leave the program.  Your BRZWLAN.INI file should be changed to reflect the changes made in the BRZSETUP program.
9. Copy the C:\TEMP\BRZWLAN.INI file to the C:\PERCON\FALCON\RF\BRZCOM directory.  You will be prompted to overwrite the existing BRZWLAN.INI file; select Yes.
10. Ensure that the AP is configured with the same settings by connecting to the AP via a serial connection to your PC.
11. Configure the Falcon using the Falcon Configuration Utility.  If you are unsure how to do this see Falcon RF FAQs.

 7.  How do I use the Symbol RF Card upgrade utility?

The Symbol RF card upgrade utility allows you convert your Symbol card from Spring protocol to 802.11 firmware.  You must have an 802.11 compliant Access Point in order to connect an 802.11 RF card to your network.

1. Safe boot the Falcon terminal.  If you are unsure of how to do this, refer to the Falcon Technical Reference Guide.
2. Unzip the Symbol_RF_Card_Upgrade.zip file into its own directory.
3. Open the directory using Windows Explorer or My Computer.
4. Double-click the Install.bat file.
5. A message box will appear asking which firmware you would like to install on the RF card:
   • Enter 1 to install the 802.11 firmware, or
   • Enter 2 if you wish to install the Spring protocol
6. Select a COM port by entering the COM port to which the Falcon is connected.
7. Enter the type of Falcon you are trying to program.
8. Type LD on the portable and press any key on your PC´s keyboard.
   When the files have finished transferring to the Falcon, the unit will reboot.  A message will appear indicating the upgrade was successful.

It is recommended the unit be formatted and reconfigured.  See the Falcon Technical Reference Guide for more information on formatting and configuration.

 8.  What are the latest RF drivers, and how can I tell which drivers are loaded on my Falcon RF unit?

 The following table lists RF Card name, Driver name, Date of Driver, and Size of Driver.  For Powernet and the Falcon Configuration Utility, driver files are located in the NET directory.  If you are using Intellitrack RF, the driver files are located in the RFS directory.

 9.  How can I tell if the latest version of PowerNet is installed on a Falcon RF?

The following steps will determine which version of PowerNet is currently loaded in the Falcon RF unit.

• Safe boot the unit.  If you are unfamiliar with this process, please refer to the Falcon Advanced User´s Guide, Chapter Seven: Resetting the Falcon.
• Type in SOCKETEP and press Enter.
• The TCPIP stack will try to load, however, an error message will appear because the RF card drivers and PCMCIA card drivers are not loaded.
• On the first line after typing SOCKETEP the message "DATLIGHT SOCKETS version XX" will display.  If the version displayed is anything other than 2.06, then download the latest version of PowerNet.

 10.  Is Intermec compatible with any of our Falcon RF units?

Yes, the Proxim RangeLan RF system uses the Open Air protocol, which the Intermec Access Points utilize.  PSC cannot support the Intermec Access Point however, as we do not sell that product.

 11.  What IP address should I use on the Falcon if I have a DHCP server?

Use 0.0.0.1.

 12.  How do I get to the DOS prompt using PowerNet?

You can either safe boot the Falcon and that will immediately put you at the DOS prompt, or you can press capital C at the ‘Press Any Key To Continue' screen, then select exit.

 13.  When I enter the IP address, the Host IP address and the Authorization Code, where is that information stored?

This information is stored in the Power.net file at the root directory on the portable. 

 14.  During the installation of PowerNetTN, I am prompted for an installation key.  What is that?

PE3892.  It is case sensitive, so it must be typed in using capital letters. 

 15. Falcon & RF Card Type Compatibility Chart
(Note: We no longer sell Breezecom so newly released items will not have part numbers but it physically could work)

Tech Support : 973-579-0103  or  973-579-1309
Fax : 973-579-7564
8:30 to 5:00 Eastern Time. Mon.- Fri.

Return to the Instruments & Equipment Home Page

TO SPEAK TO AN I&E ACCOUNT REPRESENTATIVE PLEASE CALL
1-800-432-1255 or 1-973-579-0009