Click Logo for Home Page
Axisware EDI Driver Tips


Home | Products | Downloads | Manuals | Prices | Order Info | Register a Product | Support |

One of the most important factors in diagnosing and fixing a problem is obtaining and correctly interpreting accurate information about the problem. This page outlines methods that can be used to assist in this process of troubleshooting driver problems.  These notes refer to FactoryLink EDI driver products sold by Axisware.

Performing FactoryLink Startup Commands Manually
Verify Driver Installation
Configuration Problems
EDI Task Startup Errors
Run Time Errors
        EDI Task Reporting of Driver Detected Errors
        Driver Reporting of Errors
        Driver Diagnostic Logging (AWS-.. part numbers)

<Back to Support Index

Performing FactoryLink Startup Commands Manually

On this page there are references to entering certain commands that will manually perform specific FactoryLink startup functions. This is done to verify the configuration up to a specific point.

To do these commands, you need an MS-DOS prompt window.

In all cases it is important that the command window you are using has the appropriate values for the environment variables "FLINK" and "FLAPP". This can be verified by entering the "set" command without arguments and verifying these variables from the output.

It is often easier to verify a command's output by redirecting the output to a text file. The file name does not matter, except you must remembered it to view the output!  Reusing the command name with a .txt extension will help when collecting multiple output files. Having these files available will often reduce the time required to discuss your problem with technical support personnel. Sending these files with email to technical support (support@axisware.com) will help us provide best possible initial response.

In order to verify the environment variables required, perform the following steps:

1) Open a command window

2) Enter the "set" command with redirected output, for example: "set >set.txt"

3) Edit the output file (in this example set.txt) and search for the strings "FLINK=" and "FLAPP=". You can use Notepad as a text editor on Windows platforms.

4) If they are not properly set, set the variables with set commands, for example:
"set FLINK=C:\FLNT".  Note: the only space in this command is after set.
You can also build a command file to set both variables. (On Windows platforms this file should have a ".bat" file extension)

Top

Verify Driver Installation

The required order of installation is:

1) Install FactoryLink Base Product

2) Install the FactoryLink Device Interface (DI) Option. This is a separate step that can be done as part of the initial install process, after the base code has been installed, or it can be done later.

3) Install the EDI Driver according to the instructions in the manual for the driver you have purchased.

If you are upgrading FactoryLink, please note that as part of driver installation some FactoryLink files are modified. When you reinstall or upgrade FactoryLink these modifications are overwritten back to the base FactoryLink files. Please refer to the Axiware Driver Install Tips page for more information.

To verify that a driver is properly installed open the FactoryLink Configuration Manager and verify that the driver is listed on the Configuration Manager and that you can select it and view the driver configuration tables. If a message stating a missing key file name of "ediunsol" appears then the FactoryLink Device Interface (DI) option has not been installed.

In FactoryLink, each EDI protocol module or driver is assigned a four (4) letter identifier or ID (XXXX). This ID is the value used in the Device Name column in the External Device Definition Table. For example the four letter ID for the GE Fanuc PCIM driver is PCIM. If a message appears stating a missing key file name of XXXX� then the driver was not properly installed.

Create simple entries in the configuration tables for the driver, exit from Configuration Manager and then enter the following command at a command prompt: "ctgen -v XXXX". For example "ctgen -v PCIM". The error messages from this section may seem cryptic, but you should see output similar to the following:

XXXXSHDR (proc_hdr):
XXXXSOVR: (table '0') 2 records.
XXXX_HDR (proc_hdr):
XXXX_OVR: (table 'TableName') 261 records.

If the configuration manager does not start, or the output of the "ctgen" command does not contain the expected output, please refer to the Axisware Driver Install Tips page for more information.

Top

Configuration Problems

The FactoryLink "DCT" (device configuration table) generation program, edistart, runs in a text window during startup, so error messages relating to information entered in the driver's configuration tables may not be noticed. In order to verify that there are no untranslatable entries in these tables enter the following command at a command prompt: "edistart -r". This command runs the DCT generation program, and any errors determined by the driver software at this point will be output to the screen.

Also, the edistart command with a "-v" parameter specified will output a formatted description of the tables, which will be used for more information in the Runtime Errors section below. However at this point in troubleshooting, you are looking for driver-reported errors in the edistart output and it is easier to see these errors if the "-v" parameter is not used.

Note: be sure you have run the "ctgen" step before entering edistart commands. The entries in the Configuration Tables are stored in a configuration database. Edistart, the DCT generation program, does not use this database, but uses the "CT" (.ct) files generated from the database by the ctgen program.   You can run ctgen from the command prompt.

The errors generated by edistart are driver dependent, so please refer to the appropriate error section in the driver's manual for details of specific error messages.

Top

EDI Task Startup Errors

The EDI task will output cryptic but sometimes interesting messages concerning the start up of the EDI task and it's protocol modules (drivers). We are not aware of a good way to capture these messages, but the best known method of viewing them is as follows:

1.

Manually start FactoryLink in "debug" mode by entering the command: "flrun -d"

2.

When the Shared Runtime Manager text window appears bring it to the fore ground and watch closely for EDI messages

Top

Run Time Errors

EDI Task Reporting of Driver Detected Errors

The EDI task will output the following message on errors reported by the protocol module (driver) on the Shared User Runtime Manager graphics screen. If the "flrun -d" command was used, these messages will also appear in the Shared Runmgr text window. In the Configuration Manager, you can also put an S in the flags column for the EDI task entry in the shared domain System Configuration table.   Runtime output will then appear in the EDI:shareusr text window instead of the Shared Runmgr window - this can be helpful in viewing EDI output seperate from other FactoryLink task output. The format of the messages is:

LPORT XXX LSTA SSS ERR eeee table ttt pkt:ppp

where:

XXX - Logical Port number
SSS - Logical Station number
eeee - error code in unsigned hexadecimal.
ttt - table number
ppp - packet number in table

To map the table number indicated in the error message to its table name, enter the command: "edistart -r -v >edistart.txt". The edistart program will output formatted information for each configuration table processed. The format is as follows:

Processing XXXX device (note: this line appears once for each driver ID)
Processing <TABLE NAME>
to produce
Definition file: xLLL_TTT.dct ....

where:
LLL is the Logical Port Number
TTT is the Table Number
x is r for Block Read Tables
is w for Block Write Tables
is e for Exception Write Tables
is u for Unsolicited Read Tables

Match the ttt number from the error message with the TTT in the .dct filename. The <TABLE NAME> in the Processing line will be the first up to eight (8) characters in the Read/Write information table name that generated the error.

Top

Driver Reporting of Errors

Most run-time errors will generate messages from the protocol driver. To isolate the messages generated by the protocol driver, start the protocol manually before starting FactoryLink. This process is described below:

1) Position to the protocol module's executable directory, normally "%FLINK%\edi\XXXX".

2) Start the protocol module by entering the command: "XXXXscom edi_LLL -cvarmgr -rvarmgrsu >XXXXscom.txt"
note: all entries are in lower case, and there is no space between "-c" and 'v', or between "-r" and 'v'.

 
Where:
XXXX
is the driver's four (4) letter ID
LLL
three digit logical port number, it must be three digits. Logical port 7 is "007".

If an error message occurs when this command is entered, contact technical support with the contents of the message. If the program starts correctly the cursor will return to the left border, but the prompt will not appear.

After starting the protocol module start FactoryLink, wait for the error to occur, then stop FactoryLink.

If all went well, the prompt will reappear in the command window you ran the protocol module. View the file XXXXscom.txt and refer to the specific driver manual for a description of the error messages.

Top

Driver Diagnostic Logging (AWS- part numbers only)

Axisware drivers with AWS-.. part numbers include diagnostic logging capability so that diagnostic output can be captured to text file and sent to Axisware by email/diskette. Here are the instructions to  turn on diagnostic logs for these drivers. There are two methods, select the one appropriate for your application.

Method 1 is to be used if you are running FactoryLink from a command line, using the flrun command.

At the NT command prompt where you run FL enter the commands

1/ del %FLAPP%\dct\*.dct
2/ set XXXX=-ALL   (This must be exactly as shown, no extra spaces, where XXXX is the 4 character device ID)
3/ flrun

-- end of method 1 --

Method 2 is for running FactoryLink from an icon or from the Start Menu:

In NT/Win9x Control Panel, select System and add an environment variable named XXXX, where XXXX is the 4-character device ID.

Set it's value to -ALL

It does not matter if it is a system or user environment variable. You will need to log out and in again to activate the new variable. Then you can run FactoryLink as normal.

-- end of method 2 --

At runtime the driver will now create log files in %FLAPP%\log, you will see filenames of the form XXXX*.log. A new log file will be created each time the driver is started.   Please run the driver until you reproduce the error conditions then zip and email the logs.  Also please email the XXXX log files from %FLAPP%\dct (do not send the .dct files, just the logs). All logs are text files so if you wish you can add comments in them before sending to give us any extra information.

To turn off diagnostics, set XXXX to -none or remove it from your environment. Logging should never be left on in live running conditions because of the effect on performance and disk space.

Top

If you have done all this and still have problems, please phone or email support@axisware.com

 

Home | Contact Us | Search |
About Us | Links | Privacy |
Copyrights & Disclaimers |
  © 2001-9 Axisware LLC, Plano, TX, USA. Tel +1 (214) 764 1876. Fax +1 (214) 764 1878
About this site. All Trademarks are the property of their respective owners.  E&OE.