EDITING .INI File (e.g. adding COM ports for DirectSOFT)? . . . See FAQ0008 & FAQ0204
COMMUNICATION Problems? . . . See FAQ0013
INSTALLATION Problems? . . . See FAQ0016
PRINTING Problems? . . . See FAQ0018
DOCUMENTATION Problems? . . . See FAQ0040

FAQ0001 (see also DS Data FAQ0002)
06-May-2002
Q: Using both DirectSOFT Programming and DS Data simultaneously, why does my PC lock-up?
A: You are probably using a common link. Instead, create two different links.

FAQ0002
21-May-2002
Q: Can I import rung comments in DirectSOFT?
A: Yes, but only in v4.0. Earlier versions do not support this.

FAQ0003 
21-May-2002
Q: How can I prevent my rung comments from getting corrupted?
A: Upgrade to at least DirectSOFT v3.0c Build 80 (many comment issues were fixed). DirectSOFT v4.0 supports export comments. Therefore exporting comments often would provide you with a safety guard in a text format. Also, DirectSOFT v4.0 provides ability to do backups of project. Also, it is better to work with the project directly on the hard drive and not a server.

FAQ0004
21-May-2002
Q: What causes "Error, invalid path values .DTA"?
A: The .DTA files are for Data View in DirectSOFT. If you copied your project to a different folder, but you didn't copy the .DTA files as well, you will get this error.

FAQ0005 (see also ECOM FAQ0002)
28-May-2002
Q: What causes "Task code error response" with extended E353 error?
A: Error is from PLC and means "timeout in the background communications." Error is due to backplane comm problem (ECOM, DCM, etc.)

FAQ0006
28-May-2002
Q: What causes "Error filter error reading internal op codes importing TISoft to DS" error?
A: This is a bug that was fixed with DirectSOFT v3.0c Build71 + patch.

FAQ0007
29-May-2002
Q: What files are effected by a save?
A: For details, see file DSP save and load chart2.PDF. The following is a summary of the file extensions:

File --> Save Project --> to Disk (Ctrl+S):

• PRJ - Ladder program
• VD - V-memory data
• VF - V-memory editor format
• TLS - PLC parameters, I/O configuration, pause bits
• ESD - Element documentation (nickname, wiring info, description)
• ESX - Index for element documentation
• LDA - Maps rung comments to rung numbers
• LCD - Ladder comment data
• LCX - Ladder comment index
• LDO - Online only, maps rung comments to rung numbers (temporary until saved offline to LDA)
• SCD - Stage comment data
• SCX - Stage comment index
• WSP - DirectSOFT window layout
• RD - 305 R-memory data
• RF - 305 R-memory data editor format
• PRT - Print layout config
• DV - DV1000 setup
• PID - PID documentation
• INF - Project information

In DirectSOFT v5.0 there is an additional file effected:

• XML - Docking-pane screen coordinates

Write-to-Disk (Ctrl+F12) button:

• PRJ - Ladder program

In DirectSOFT v5.0 there is an additional file effected:

• XML - Docking-pane screen coordinates

FAQ0008
09-Jul-2008
Q: What things can be setup using the DS500.INI (DS300.INI / DS400.INI) file?
A: The following parameters can be added (or adjusted) in the DS500.INI (DS300.INI / DS400.INI) file.
To see how to pull up the .INI file for editing, refer to DirectSOFT FAQ0204.

• COMxEnable: Enable, disable, add or delete serial COM port resources for links.
• ModemEnable: Enable or disable serial modem resource.
• EthernetEnable: Enable or disable Ethernet resources for links.
• Autosense: Enable or disable the autosensing of links on startup. (Once links have been created, they are validated each time you start DSLaunch).
• Dump: Causes link to output serial connection debug information to a file for troubleshooting links. This feature is used in conjunction with DBWin32 logger (details given in DirectSOFT FAQ0013 under DUMP section.
• PROGRAM COLORS: Modify default program colors. The parameter numbers and colors are not defined in a user-friendly manner. Therefore this should only be used to fix a problem (e.g. see DirectSOFT FAQ0020, FAQ0043).
• UDPPortNumEnable: Enable or disable UDP port numbering parameter for links.
• PROJECT PATH: Modify default project path.
• LadderPalette: Enable or disable ladder logic palette.
• UseLargeBtns: Modify toolbar button size.
• BACKUP PATH: Modify default backup project path.
• RTSxDelay: Modify serial RTS timing control.
• OnTheWeb: Enable, disable the DSLaunch's "DirectSOFT on the Web" feature
• INFLOOPTIMEOUT: Set DirectSOFT's internal loop timeout value as a protection against infinite loops that can cause crashes. This number is the maximum number of loops allowed to do an internal operation in DirectSOFT. Under normal conditions, this number will never be reached. But in cases where there could be very large databases, this number may need to be increased to allow DirectSOFT more loops to complete a certain operation.

NOTES:
(1) - Only use this to fix a problem (e.g. DirectSOFT FAQ0020, FAQ0043). The parameter and color numbers are not defined in a user-friendly manner.
(2) - Became available with DirectSOFT v3.0c Build 54 (01-Sep-2000)
(3) - Became available with DirectSOFT v4.0 Build 18 (09-Dec-2002)
(4) - Only available in DirectSOFT v4.0. Not available in DirectSOFT v5.0.
(5) - Only modify this if you have received the "Infinite Loop Timeout" message. This parameter became available with DirectSOFT v4.0 Build 20 (27-Jun-2003).

FAQ0009
07-Jun-2002
Q: Getting CSMain.exe error when doing a Find for an element in Ladder view.
A: Upgrade to at least v3.0c Build71 +patch or v4.0.

FAQ0010
10-Jun-2002
Q: In DirectSOFT under Add Link get double listings (two COM1's, two COM2's, two Ethernets etc.).
A: One of three things has probably happened:

• Installed DirectSOFT two times under itself or . . . 
• Installed DirectSOFT v3.0c B71 patch (Devasync.DLL file) in the wrong folder (and thus has two copies of it). Should only be in the BIN folder underneath DirectSOFT folder.
• Upgrade of DirectSOFT failed or was interrupted or aborted.

The bottom line is that you have multiple copies of the Devasync.DLL and Devether.DLL files and you only need one. To fix search your hard drive and delete all copies of these two files except the ones in the DirectSOFT4\Bin or DirectSOFT32\Bin folders.

FAQ0011 (see also DS Data FAQ0053)
17-Jun-2002
Q: Trying to get USB adapter to work, getting "Comm Error - Cannot access comm port. The port may not be present or another application might be using it."
A: Make sure that there are not any other devices (like internal modems) using the COM port that the USB adapter driver is trying to use. Also, it is recommended that you upgrade DirectSOFT to at least v4.0 Build 18, or v3.0 Build 80. Or make sure you use a USB that has been approved and tested by Host Engineering for use with DirectSOFT. Also, it is recommended that you:

1. Install USB device driver first.
2. Connect the USB device secondly.

 This list is updated as we go:

• Automation Direct USB-RS232 (Win98, WinME, Win2K, WinXP).
• Belkin F5U103 USB-to-Serial adapter (Win98, WinME, WinNT, Win2K, WinXP).
• Belkin F5U105 USB-to-Serial adapter (customer using and it worked).
• Belkin F5U109 PDA adapter (Win98, WinME, WinNT, Win2K, WinXP).
• Belkin F5U409-CU (works but incompatible with Toshiba 5005 laptop).
• Keyspan USA-19QW (at least DirectSOFT v4.0 Build 16 or DirectSOFT v3.0 Build 80 required; WinXP).
• Digi AccelePort USB 2 two-port adapter (Win98, WinME).
• Xircom PGSDB9 USB-to-Serial adapter (Win98, WinME).
• Prolific (customer using on WinXP and it worked).
• Targus (DOES NOT WORK!)
• Quatech (DOES NOT WORK!)

3. Finally, your USB adapter may be wanting to use a COM port that you do not have enabled for DirectSOFT. For example, some want to use COM port #5. By default, DirectSOFT does not have this COM port enabled in the .INI file.
   
   - To pull up the .INI file for editing, see DirectSOFT FAQ0204.
   - To edit the COM resources in the .INI file, see DirectSOFT FAQ0008.

FAQ0012
17-Jun-2002
Q: Using Targus USB converter, WinXP, Toshiba Satellite 2405 S201, getting, "Error connecting to PLC"
A: Host has not tested the Targus USB converter and it is therefore we cannot recommend it. However, upgrading your DirectSOFT to the latest Build is always recommended because Host continuously attempts to improve communications with the wide variety of USB drivers now being sold. (see DirectSOFT FAQ0011 for list of compatible USBs).

FAQ0013 (see also DS Data FAQ0045; similar to ECOM FAQ0024; similar to EZ Ethernet FAQ0005)
18-Jun-2008
Q: Need general help on communications from PC to PLC and establishing a link.
A: First of all, always make sure you are using the latest version of DirectSOFT possible.

Secondly, if you are using an ECOM and have WinXP on your PC with a firewall (particularly with SP2), then you must do one of the following:

     (1)  Turn the firewall off, or
     (2) Create an exception for CSMAIN.EXE application (located in the BIN folder under your DirectSOFT folder), or
     (3) Create an exception for port #0x7070 (28784) for both TCP and UDP protocols, which is the port number that all of our Ethernet devices use for communication.

Thirdly, you can control which communications resources on your PC you want to let DirectSOFT use by entries in the DirectSOFT initialization file (DS500.INI):

COMMUNICATIONS RESOURCES

You must edit DirectSOFT's DS500.INI file to change communication resources.
(To pull up the .INI file for editing, see DirectSOFT FAQ0204)

There are 3 parameters that can be modified regarding communication resources:
     (1) COMxEnable - To edit this resource in the .INI file, see DirectSOFT FAQ0008.
     (2) ModemEnable - To edit this resource in the .INI file, see DirectSOFT FAQ0008.
     (3) EthernetEnable - To edit this resource in the .INI file, see DirectSOFT FAQ0008.

NOTE: In some extremely rare cases with DirectSOFT versions older than v4.0, to totally disable Ethernet resources you not only have to do the above, but also you may need to rename the files Devether.DLL and Protoecm.DLL to Devether.OLD and Protoecm.OLD. Don't forget to rename them back after troubleshooting!

STARTUP

1. Using the resources enabled in the .INI file, DirectSOFT's CommServer tries to find PLCs.
2. If it finds some, it creates DirectSOFT links to them.
3. If it finds none, then it comes up without creating links.
4. As it attempts to use communication resources on your PC then one of the following happens:

1. DirectSOFT comes up normally. Yay!
    
2. "Error connecting to PLC!" or "No response from PLC!"

• This means DirectSOFT found the resource on your PC OK, but it had trouble connecting to the PLC.
• Check cabling or other physical things outside the PC.
• If you are using a DL105, they tend to be a bit more sensitive to flakey cables and electrical noise. Try a new cable, especially if you can use the same setup and talk to other DL PLCs (e.g. DL205).
• On a DL305 system make sure the power supply is capable of supplying enough power for the DCU. Try external power.
• Could be Microsoft ActiveSync is using COM port.

3. "Error: cannot access comm port. The port may not be present or another app may be using it"

• This means DirectSOFT can't gain access to the COM port because something else is using it.
• Check to see if anything else is using COM port:
  
  i)    RSLogix
  ii)   PDA Software (Palm Pilot, Pocket PC, etc.)
  iii)  GPS Software
  iv)  Digital Camera Software
  v)   IR (infrared) Drivers
  vi)  Microsoft ActiveSync
  vii) Palm OS HotSync
   
• Sometimes if upgrading operating systems (e.g. Win2K to WinXP) the COM ports somehow get dysfunctional. May have to disable all COM ports in the BIOS and then reinstall the upgrade, then re-enable them in the BIOS.
• If using a USB-to-Serial converter or a USB Port Replicator, its driver may not act like a regular COM port. (DirectSOFT "thinks" it is talking to a regular COM port). If this is the case there is no immediate fix. Host Engineering periodically updates DirectSOFT attempting to compensate for these kinds of driver problems.
• If using a USB-to-Serial converter, sometimes it is very important that you load the driver first, before connecting the device itself. In fact, in some cases, if this is done in the wrong order it takes special steps to fix the problem. See the website of the manufacturer of your converter for details. See DirectSOFT FAQ0011.
• Try disabling all resources in the .INI file.

4. "Transport protocol error"

This means you are using Ethernet as a link and it timed out and is commonly due to one or more of the following issues:

• Bad cabling; check all cables to make sure they are OK. (e.g. Are they susceptible to noise due to bad shielding, etc?)
• Using wrong cable (crossover instead of straight-through, or vise versa). Make sure that the Link light is ON; this means that the cable electrical connection is good.
• The cable is running through a very electrically noisy environment.
• ECOM not seated properly. Make sure it is.
• If your PC has 2 (or more) NICs (Network Interface Cards), then make sure that you try one of these:
       - Reprioritize your NICs:
            If you have WinXP:
                 (1)  Start -->  Control Panel.
                 (2)  Double-click on the "Network Connections" icon.
                 (3)  On the menu at the top, select Advanced --> Advanced Settings...
                 (4)  On the "Adapters and Bindings" tab, in the top window, select the connection you are using.
                 (5)  Use the green arrows at the right to move this connection to the top of the list.
                 (6)  Press <OK> and close Network Connections window.
                 (7)  You may have to reboot your PC.
            If you have WinVista:
                 (1)  Start -->  Control Panel.
                 (2)  Double-click on the "Network & Sharing Center" icon.
                 (3)  At the left of this window, click on "Manage network connections"
                 (4)  Press the <ALT> key to make a menu appear at the top of this window.
                 (5)  On the menu at the top, select Advanced --> Advanced Settings...
                 (6)  On the "Adapters and Bindings" tab, in the top window, select the connection you are using.
                 (7)  Use the green arrows at the right to move this connection to the top of the list.
                 (8)  Press <OK> and close Network Connections window.
                 (9)  You may have to reboot your PC.
       - Uninstall or disable one NIC
       - Make sure that the NICs don't have common protocols enabled (i.e. IPX and TCP/IP). In other words, you might enable IPX on one NIC and TCP/IP on the other NIC, but not on both simultaneously (see DirectSOFT FAQ0183 for installing protocols).
• There are multiple LAN connections in your Network Connections. Disable all but the one you are planning on using.
• There are "Bridged" LAN connections in your Network Connections. Unbridge them by setting them simply to "Disabled."
• There are WAN connections enabled. Disable them.
• Using an H0-ECOM/ECOM100 and the PLC firmware is not up to date. Make sure it is.
• Using an H0-ECOM/ECOM100 and a D0-06LCD display but it is not up to date. Make sure the LCD has a date code of 032A or later.
• Using an H2-ECOM/ECOM100 and you have it installed in Slot 0 (the slot adjacent to the CPU). Install it in a different slot.
• Using an H4-ECOM/ECOM100 and it has bent pins on the ECOM and/or the CPU. Check for bent pins.
• The ECOM, CPU or the backplane is bad.
• Extremely busy network traffic. Isolate the network.
• Busy network or PLC sluggishness. Under the Link's Advanced Settings (Link Editor, Port Tab), try increasing the Timeout and Retry values. (e.g. Try going to a DOS command prompt window and using the "ping" command to ping the ECOM's IP address. If Ping works, note the response times. In the link's Advanced Settings (Link Editor, Port Tab), increase the Timeout value to at least 2 or 3 times that response value.)

5. "PLC is not in terminal mode!..."

• The mode switch on the PLC is in the RUN or STOP position. Switch it to the TERM position.

6. "Unable to open Online Program"

• The mode switch on the PLC is in the RUN or STOP position. Switch it to the TERM position.

7. "CSMAIN.EXE error" or DirectSOFT locks up or mouse hangs up.

• This means that DirectSOFT's CommServer has accessed a resource on your PC that has a conflict or doesn't exist.
• First try upgrading to at least DirectSOFT v4.0 Build 22. We believe we have fixed the last of these types of failures in this build! (If you have v3.0 there are some improvements in Build 80, however, it could still have some problems since we have stopped development on v3.0).
• If you have DS Data simultaneously using the same link as DirectSOFT then instead make separate links (i.e. one link for DS Data and one link for DirectSOFT).
• Try disabling all resources in the .INI file.
• Make sure TCP/IP protocol is loaded.
• If using v4.0 Build 16 or earlier, or v3.0 Build 71 or earlier, you may need to:
       (1) Upgrade to later version;
       (2) Make sure IPX protocol is loaded (see DirectSOFT FAQ0183 for installing protocols) for the NIC you are using.
• Could be Microsoft ActiveSync is using COM port.

8. "Error opening connection to Ethernet device"

• This is usually caused by having 2 (or more) NIC (Network Interface Cards). Thus try one of these:
       - Reprioritize your NICs:
            If you have WinXP:
                 (1)  Start -->  Control Panel.
                 (2)  Double-click on the "Network Connections" icon.
                 (3)  On the menu at the top, select Advanced --> Advanced Settings...
                 (4)  On the "Adapters and Bindings" tab, in the top window, select the connection you are using.
                 (5)  Use the green arrows at the right to move this connection to the top of the list.
                 (6)  Press <OK> and close Network Connections window.
                 (7)  You may have to reboot your PC.
            If you have WinVista:
                 (1)  Start -->  Control Panel.
                 (2)  Double-click on the "Network & Sharing Center" icon.
                 (3)  At the left of this window, click on "Manage network connections"
                 (4)  Press the <ALT> key to make a menu appear at the top of this window.
                 (5)  On the menu at the top, select Advanced --> Advanced Settings...
                 (6)  On the "Adapters and Bindings" tab, in the top window, select the connection you are using.
                 (7)  Use the green arrows at the right to move this connection to the top of the list.
                 (8)  Press <OK> and close Network Connections window.
                 (9)  You may have to reboot your PC.
       - Uninstall or disable one NIC
       - Make sure that the NICs don't have common protocols enabled (i.e. IPX and TCP/IP). In other words, you might enable IPX on one NIC and TCP/IP on the other NIC, but not on both simultaneously (see DirectSOFT FAQ0183 for installing protocols).

9. "Comm error reading program from PLC"

• The mode switch on the PLC is in the RUN or STOP position. Switch it to the TERM position.
• This error means that DirectSOFT received an incorrect response from the PLC, so the physical connection is probably OK; however, it is possible that the port of the PLC itself is defective.
• If you are using a USB-to-Serial converter it could be there is an incompatibility between your PC and the converter. (e.g. we know of an incompatibility between the Belkin F5U409-CU converter and the Toshiba 5005 laptop).
• Make sure you are not running two copies of DirectSOFT simultaneously (like v3.0 and v4.0). Also, along these lines, if you do install two versions, this is OK as long as they are in different folders and are not run at the same time.
• We have found that RSLogix (Allen-Bradley) software interferes with the PC's communcations over serial ports (e.g. COM1). So if doing a serial link and you get this error, it could be due to this software. Make sure that this software is not running in the background, or that it does not run in the Terminate Stay Ready (TSR) fashion.
• Increase the link's Retries and Timeout values; especially if using a modem link.
• If using a modem link, make sure that both the Compression and Error Correction are turned off.

10. "Knowledge base mismatch"

• Message means the CPU picked for the link is not supported in the installed version of DirectSOFT.

11. "Error attempting to access unlocked device"

• This is caused when trying to reconnect to a PLC in which DirectSOFT did not disconnect from previously in a clean manner. Solution is normally to either try again, or power cycle the PLC.
• To prevent this from happening in the future, either:
  - Use the PLC --> Disconnect from DirectSOFT before unplugging the cable to the PLC.
  - Close DirectSOFT before unplugging the cable to the PLC.

12. Goes offline by itself after using the link.

• The only thing that we have seen that cures this strange behavior is to uninstall DirectSOFT and then reinstall.

13. Sometimes gets a PLC password prompt; but the PLC doesn't have a password!

• This is caused by data errors in the communication. The problem is electrical noise either due to an excessively noisy environment, or a bad cable (e.g. shielding going bad).

14. "Comm error unlocking PLC"

• The first thing DirectSOFT tries to do when connecting is to unlock the PLC. This is to see if the PLC sends back a warning that there is a password. If you get this message instead of a password prompt, it means that something went amiss when DirectSOFT attempted to unlock. The PLC sent back an invalid response or didn't send a reply at all. For solutions try the things listed under "Transport protocol error" above.

15. "Support for the PLC type specified in the link is not installed"

• This simply means what it says, and is usually caused by one of the following:
  - Unknown PLC specified in the link, therefore check if the CPU specified in the link matches your hardware.
  - PLC is not supported with the version of DirectSOFT you are using.
  - DirectSOFT cannot find the knowledge base DLL. This is usually an installation problem. You may need to uninstall and reinstall making sure you are the Administrator of your PC.
  - PLC responding to link is sending an invalid identifier. This may be a PLC problem. You might try power cycling the PLC.

MODEM LINKS

Modem links must be configured manually. Here is a checklist for getting a modem connection working:

• Are you using the correct cabling?
• Are the port settings the same for the modem as they are for the PC comm port (baud, parity, data bits, etc.)?
• Make sure PC modem data compression is turned off.
• Make sure PC modem error correction is turned off.
• May need to set the modem link Retries to maximum.
• May need to set the modem link Timeout value to maximum.

USB-TO-SERIAL

These devices have drivers with them that should make them act like regular COM ports. (See DirectSOFT FAQ0011 for approved USB-to-Serial devices tested by Host Engineering). However there have been a few vendors that don't do this with their drivers. DirectSOFT "thinks" it is talking to a COM port, Ethernet NIC, or modem. It doesn't know a USB-to-serial device.

The order of installation, however, seems to be important:

1. Install USB device driver first.
2. Connect the USB device secondly.

AUTOSENSE

Once links have been created for DirectSOFT, it validates these each time you start it. You can stop this from happening by editing the .INI file and changing AutoSense:
- To pull up the .INI file for editing, see DirectSOFT FAQ0204.
- To edit Autosense parameter in the .INI file, see DirectSOFT FAQ0008.

DUMP (for troubleshooting SERIAL and MODEM links)

When you can't figure why things won't work exactly right, you can use this debug function with a little help from Automation Direct, or Host Engineering. This parameter is in the .INI file.
- To pull up the .INI file for editing, see DirectSOFT FAQ0204.
- To edit Dump parameter in the .INI file, see DirectSOFT FAQ0008.

After making this change you should start the debug window logger:

1. Start --> Programs --> DirectSOFT --> DirectSOFT Program Tools --> DBWin32 Logger
2. Start DirectSOFT.
3. DirectSOFT will ask you if you want to enable the debug mode. Answer <YES>.
4. Now DirectSOFT will dump information into the open debug window.
5. Save this data into a text file and send to Automation Direct or Host Engineering.

FAQ0014
24-Jun-2002
Q: Mouse scroll wheel doesn't work in DirectSOFT, but works in other applications.
A: The first thing to try is to update to at least DirectSOFT v4.0 Build 24. If that doesn't work then you may need to download the mouse control software for your mouse. For example, download and install Microsoft Intellipoint for Microsoft mice, and Logitech MouseMan software for Logitech mice, etc.

FAQ0015
25-Jun-2002
Q: Using DirectSOFT v3.0c Build 71 + patch; why is there no option to export program to CSV file.
A: This is not supported in v3.0c, must have v4.0.

FAQ0016
12-Jun-2008
Q: Having DirectSOFT installation problems.
A: Primary things to check before consulting the errors listed below:

1. Consult DirectSOFT FAQ0140 to make sure that Windows operating system you are using supports the version of DirectSOFT you are attempting to install.
2. If you have to log on to your PC (i.e. WinNT, Win2K, WinXP), make sure you are logged in with Administrator privileges.
3. A wide variety of problems can be solved on Win95, Win98 and WinME PCs by installing DirectSOFT in Safe Mode.

Below are various installation errors that have been encountered and their solutions.

• (1) Entered the keycode and it appears to install but it stops on the last screen. If you try to close it, it says, "Setup is not complete."
  This could be due to you trying to install DirectSOFT on a Windows system that is not supported. For example installing DirectSOFT v4.0 on Win95. On Win95 it will probably install but by default it will try to go ahead and install the CTRIO Workbench and ERM Workbench. These will sometimes not install properly because they will definitely not run on Win95. You may try the "custom" installation and then choose not to install the Workbenches. However, getting DirectSOFT to run on Win95 may be a problem as it is not guaranteed to work on this OS.
   
• (2) Entered the keycode and it unpacks, but nothing else happens; or it returns to the Showcase screen.
  This is a Windows system problem regarding InstallShield that we believe is related to your PC's Temp folder. This sometimes happens after your PC has recently crashed instead of being shutdown. Or if a previous install of a software package crashes. You might try:
  
  Making sure there are no other applications running.
  -  Close all applications, reboot your PC and try again.
  
  If this doesn't work, try deleting the files and folders under the TEMP folder (particularly any folders beginning with "pft" and ending in "~tmp":
  1.  Close all applications that are currently running.
  2.  Right-click on "My Computer" icon and pick "Properties."
  3.  Pick the "Advanced" tab.
  4.  Click the <Environment Variables...> button.
  5.  In the top window you can see the pathname of the TEMP variable. (You may have to press the <Edit> button to see the whole path).
  6.  <Cancel> out of all these windows.
  7.  Use Windows Explorer and browse to this TEMP folder.
  8.  Delete folders and files in this TEMP folder.
  9.  Reboot your PC and try install again.
  
  If this doesn't work, then:
  1.  Make sure you have the latest system updates for your version of Windows.
  2.  Reboot PC and try install again.
  
  If this doesn't work, then:
  1.  Create a temporary folder on your hard drive.
  2.  Copy the entire installation CD to this folder.
  3.  Run the install from there by browsing out to the folder and double-clicking on the SETUP.EXE.
  
  If this doesn't work, then:
  -  You may have a defective CD; contact AutomationDirect or the vendor you purchased it from and talk to a tech.
   
• (3) "There is not enough space on drive c: to extract this package. Please free up X MB and click Retry"
  This error can occur when you have plenty of hard drive space left, but just not enough space in your Temp folder left (according to its size allocation) to install. 2 suggested fixes:
  
       - Delete all or most of the files in c:\Documents and Settings\UserName\Local Settings\Temp folder.
       - Create a folder on the hard drive and copy then entire installation CD to that folder and run the installation from there.
   
• (4) "Error 112 - Contact software vendor"
  This error is an InstallShield error. It occurs when you do not have Administrator privileges (WinNT, Win2K, WinXP). Generally speaking it is a system problem. InstallShield website (http://www.installshield.com) lists Error 112 as a decompression problem. With regards to DirectSOFT it means for some reason the system can't open the DATA1.CAB or DATA2.CAB, etc. file(s). InstallShield website gives some suggestions on what to do to fix this conflict: (see Error112InstallErrors.MHT).
   
• (5) "Win16 modem config not compatible with Win32 modem config"
  This has occurred because you are upgrading from v2.0 to v3.0. The installation cannot automatically reconfigure the Modem Links created in v2.0. Thus, the upgrade installation outputs the old Modem Link information (phone numbers, etc.) into the MODEM.TXT file so you can use the information there to recreate your Modem Links for v3.0 manually.
   
• (6) "Ctl3d32.dll which is not the correct version. This version of ctl3d32.dll is designed only for Win32 or Win95 systems."
  If you are trying to install v4.0 Build 18 or earlier onto Win95 or WinNT, DirectSOFT's install engine puts this version of the CTL3D32.DLL file on your system. This is great if you actually have Win95 PC. However, if you have a WinNT PC this could cause a problem. This has been corrected in v4.0 Build 20 and greater. To fix this you can either download the latest Build of DirectSOFT v4.0 or replace the incorrect CTL3D32.DLL with the correct one. There are three versions of the file:
  
  CTL3D32.DLL     26 KB     5/18/1997 8:54am   (Win95 version)
  CTL3D32.DLL     44 KB     5/19-Nov98 8:01pm   (Win98 version)
  CTL3D32.DLL     27 KB     5/30/1997 10:02pm (WinNT version)
  
  If you have Win95 or Win98 this file is located in your Windows\System folder. If you have WinNT it is in WinNT\System32 folder. Whichever one you have there is the wrong one. You can download all three here, then extract them and rename and use only one of them. Only one version of this file should exist on your system, so hunt down the others using your Search and either rename them or eliminate them altogether.
  
  The above zipped file (CTL3D32.ZIP) contains 3 files:
  
  CTL3D32_95.DLL (for Win95)
  CTL3D32_98.DLL (for Win98)
  CTL3D32_NT.DLL (for WinNT)
  
  You must rename the one you use to CTL3D32.DLL.
   
• (7) "Can't run 16-bit program." with "Can't find file <pathname> or one of its components. Check to insure the path and filename and that all required libraries are available."
  With this error dialog notice there is an <Ignore> button. Try that first. If that doesn't work, notice in the "Can't find file..." message, the "Documents and Settings" path was shortened to "docume~1" but the "local settings" folder name is NOT shortened to "local~1." This is why it doesn't work. This is evidently a bug in WinNT, Win2K and WinXP, where a login is required on the PC. To fix:
  1.  Create some temporary folders (e.g. c:\temp).
  2.  Right-mouse on the "My Computer" icon.
  3.  Select "Properties."
  4.  Select "Advanced" tab.
  5.  Press the <Environment Variables> button.
  6.  Write down the TEMP and TMP variables' pathnames (if you intend on restoring them later after this procedure).
  7.  Select TEMP variable from the top list.
  8.  Press <Edit> button.
  9.  Change pathname to something very simple (e.g. c:\temp).
  10. Select TMP variable from the top list.
  11. Press <Edit> button.
  12. Change pathname to something very simple (e.g. c:\temp).
  13. Attempt to install DirectSOFT.
  14. Restore the TEMP and TMP variable settings to those you wrote down if you want to.
   
• (8) "Can't run 16-bit Windows program." with "This program or one of its components is compressed. Use the MS-DOS Expand command to copy the file from the Windows Setup disks."
  
  Here are a few of things to try:
  
  SUGGESTION #1 - This suggestion goes on the idea that your system has a problem with handling long filenames:
  1.  Copy the entire contents of the installation CD to a temporary folder (c:\temp).
  2.  Browse to the temporary folder (c:\temp).
  3.  Right-click on Setup.EXE and select "Properties."
  4.  Click on the "Compatibility" tab.
  5.  Check the "Run this program in compatibility mode for:"
  6.  From the pull-down menu select some other Windows OS than the one you are using.
  7.  Click the <OK> button.
  
  NOTE: After copying files from a CD to a hard drive sometimes the Windows OS will write-protect all the files. So, if you have trouble performing the above steps because it says the file is write-protected, then you will have to turn the "Read-only" attribute off. You do this in the same manner as above except that the setting is on the "General" tab.
  
  8.  Try to install by double-clicking on the Setup.EXE.
  
  Repeat the above steps for other Windows OS selections in the pull-down menu.
  
  SUGGESTION#2 - This suggestion, like the one above, goes on the idea that your system has a problem with handling long filenames:
  NOTE: This involves editing your registry. You may want to get your PC specialist to do this for you! You can cause unrecoverable damage by editing the wrong things in the registry!
  
  1.  Go to the registry:  Start --> Run...; then type regedit and press the <OK> button.
  2.  Go to Edit --> Find... and type in NtfsDisable8dot3NameCreation to search for.
  3.  This value is usually found at:  HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\FileSystem or something close to that.
  4.  The value of the above parameter (NtfsDisable8dot3NameCreation) should be zero.
  5.  If it is not, double-click on the parameter and type a zero there.
  6.  Exit the registry.
  7.  Reboot your PC.
  8.  Try to install DirectSOFT.
  
  SUGGESTION #3 - This suggestion goes on the idea that the error reported is indeed accurately describing your system problem. Believe it or not this is rare in this case!:
  1.  Create a temporary folder (e.g. c:\test)
  2.  Go to DOS Command window (Start --> Programs --> Accessories --> Command Prompt).
  3.  Type in:    expand c:\windows\*.* c:\test
  4.  Press <ENTER>.
  
  This command will attempt to expand any unexpanded files from the Windows folder and copy them to the folder c:\test. After it does all the files you will get a message that will say something like:
  
        "Total increase:  261 files, 37185096 bytes expanded to 37185096 bytes, 0% increase"
  
  Regardless of what the other numbers are, if the increase is "0%" then this means that no unexpanded files exited in the folder tested. If this is the case then delete all the files in your c:\test folder and repeat the above steps for c:\windows\system and c:\windows\system32 folders. You would use the command:
  
            expand c:\windows\system\*.* c:\test
            expand c:\windows\system32\*.* c:\test
  
  If you get some other increase besides "0%" then this means that some of the files in the windows folder tested needed to be expanded. Therefore, the ones that it expanded you will need to copy from the c:\test folder back into the windows folder that you tested.
   
• (9) Error with GPID-VDD.DLL file.
  This seems to be a Win2K system error/problem. Make sure your Win2K has the latest updates. A simple work-around is to just press the <Ignore> button and DirectSOFT should install properly.
   
• (10) "Congrats you have found a new keycode!" - but can't find the DSP.LOG file.
  You probably got this message after upgrading to v4.0 Build 16. This is a known bug. It was fixed in v3.0 Build 80 and v4.0 Build 18. To get your new Product Key, you will have to contact Automation Direct or the distributor that you purchased it from and have proof of the purchase of your upgrade package. Sorry for the inconvenience!
   
• (11) "Unable to load instctr.dll" error.
     Suggested solutions:
  - You are trying to install CTRIO Workbench v2.x onto a Win95 PC. It is not compatible with Win95.
  - You are trying to install CTRIO Workbench v1.x onto a PC that has DirectSOFT v4.x. It is not compatible with that version.
  - You are trying to install CTRIO Workbench onto a Win98 PC that has a system problem. First try installing in the Safe Mode. If this doesn't work you may have to reinstall Win98.
   
• (12) ERM Workbench won't run.
  You will encounter problems if you installed ERM Workbench on Win95. It will probably install without error, but it will not run properly.
   
• (13) "Hlvdd - Hardlock virtual device cannot find /// Fast Hardlock driver error."
  "Hardlock is a software protection hardware dongle device driver. You will probably have to uninstall Hardlock; or resolve the issue with the software that utilizes it.
   
• (14) "Error occurred during move data process:-115."
  Regarding this error, the Microsoft Knowledgebase says, "The directories into which files are copied do not have Change or Modify NTFS permissions for the account under which the setup is run. Or the directories have a Read-Only attribute set." Therefore it could be:
  - Your Login permissions do not allow you access to this folder.
  - The folder and/or the files there are Write Protected.
  - Other applications are using the folders/files.
   
• (15) Trying to upgrade, but install says it doesn't see the previously installed version.
  The upgrade program first looks for the DSP3x.EXE or DSP4x.EXE file. Then it looks inside the actual .EXE file it finds for support information. If it fails either of these, it will report that it can't find the previously installed version. The only time we've seen this is when the actual downloaded upgrade program was corrupt. So, if you downloaded it, try it again.
   
• (16) "Uninstaller setup failed to initialize" and then a crash with message "InstallShield engine has encountered a problem and needs to close." (similar to DS Data FAQ0085)
  This means that InstallShield was unable to create the UnDSP.ISU uninstall log file for some reason. This error is just a warning and shouldn't interfere with completing the installation. Possible fixes:
       - Just press the <OK> button and ignore the message.
       - Make sure you have Administrator rights on your PC.
       - Uninstall and then delete all the .ISU files associated with DirectSOFT and then try again:
            Files to delete:
            1)  UnDSP.ISU
            2)  UnDSD.ISU
            3)  UnCTRIO.ISU
            4)  UnERM.ISU
   
• (17) "The Win16 SubSystem was unable to Enter Protected Mode..."
  This is an NTVDM (WinNT Virtual DOS Machine) subsystem error. Try the following link for a fix:
  http://support.microsoft.com/default.aspx?scid=kb;EN-US;314106
   
• (18) "16-bit MS-DOS SubSystem error."
  This is a bug that is most of the time caused by one of the five things listed below. CAUTION: You may want to get your in-house System Administrator to do this for you! If one of these five things do not fix the problem, then please refer to Microsoft Knowledge Base Articles #324767, 314452, 305521 & 314106 for further ideas.
  
  - Your PC has a virus.
      a) Do a thorough virus scan of your PC.
  
  - Autoexec.NT file needed.
       a) Copy the AUTOEXEC.NT file from the c:\Windows\Repair folder (or Windows installation CD) into the folder listed in the error message itself (e.g. c:\Windows\System32).
  
  - Config.NT file needed:
       a) Copy the CONFIG.NT file from the c:\Windows\Repair folder (or Windows installation CD)  into the folder listed in the error message itself (e.g. c:\Windows\System32).
  
  - Corrupted registry entry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers\VDD.
       a) Find the above using Regedit.
       b) On Edit menu, click Delete.
       c) On Edit menu, point to New, and then click Multistring Value.
       d) Type VDD in the Value Name box, then press <ENTER>.
       e) Exit Regedit.
  
  - Command.COM file is damaged or wrong version.
       a) Verify that the proper version of Command.COM file is installed in the Systemroot\System32 folder. Should have:
            Size: 50620
            Date: 08-23-2001
            Time: 4:00 A.M.
   
• (19) "InstallShield error" naming _INS5176._MP as a file it cannot create or find.
  We found this error to be associated with the CISSI.EXE worm virus. Once this worm was cleaned from the PC (as recommended on the Symantec website), then DirectSOFT installed normally.
   
• (20) "Setup has detected that unInstallShield is in use. Please close unInstallShield and restart setup. Error 432."
  This error occurs when InstallShield tries to delete UNINST.EXE from the Windows folder so that it can install the latest version. One or more of the following should fix the problem.
  - Make sure you have Administrator rights.
  - Make sure no other applications (including anti-virus software), installations or processes are running in the background.
  - Verify that there are not more than one instances of InstallShield running by looking on the Processes Tab of the Task Manager. The process is called _INS5576._MP.
  - Verify that there are no instances of IsUninst.EXE running by looking in the Processes Tab of the Task Manager. The process is called IsUninst.EXE.
  - Delete all instances of the file IsUninst.EXE in the Windows folder (c:\Windows or c:\WINNT).
  - Copy the entire contents of the installation CD to a local folder and run the installation from there.
   
• (21) "Error -5009:0x8002801D... Contact software vendor..."
  This error is a Windows system error coming from InstallShield. It means "Library not registered" and may occur when you do not have Administrator privileges (WinNT, Win2K, WinXP). If Admin rights is not the issue, then the offending file named in the error message may need to be manually registered. If so, you may want to contact your IT personnel for help in doing so. Basically you can try going to the Start --> Run... and entering:
  
   regsvr32 <filename>
   
• (22) "Error -5009: 0x8002802B..."
  This is an InstallShield error. To fix, rename the following folder:
  
  c:\Program Files\Common Files\InstallShield\Professional\RunTime
  
  ...to something like:
  
  c:\Program Files\Common Files\InstallShield\Professional\RunTimeOLD
  
  ...and retry the install. If this works, then it is OK to delete the RunTimeOLD folder altogether.

FAQ0017
22-Oct-2007
Q: Why are there instructions listed in the DirectSOFT Help file that do not show any support for the DL CPUs? (e.g. COS, ACOS, ATAN).
A: Because Koyo (the maker of the DL PLCs) sells a larger PLC with a superset of the instructions listed for the AutomationDirect PLCs and DirectSOFT supports those CPUs as well. But these PLCs are sold to a very specific market in Japan and are not available otherwise.

FAQ0018
28-May-2002
Q: Trying to print from DirectSOFT and having various problems.
A: Various printing issues are listed below:

• (1) Sometimes when I come back to the printer options my "Use default" printer is no longer selected and the <OK> button is greyed.
  This was a bug in v3.0c Build 71 (or less) and v4.0 Build 16 (or less) for mainly Win2K PCs. To fix upgrade to a later version. A temporary work-around:
  1.  Deselect "Use default" and select printer.
  2.  Do not reselect "Use default" and it will always use that printer.
   
• (2) Is it possible to get a printout of what is displayed in the Documentation Editor?
  Yes; use Export Documentation and then print the resultant file.
   
• (3) Cannot print to a network printer.
  This is a known bug in earlier versions. Must upgrade to at least v3.0c Build 80 or v4.0 Build 18. Even though it was fixed in v4.0 Build 18, it was not reported in the ReadMe_P.HTM file until v4.0 Build 20.
   
• (4) Cross Reference printout shows counters that are not even available for the PLC I am using (e.g. CTA200 is shown when my PLC's range is only CT0-177).
  You program probably contains documentation items that are not in your PLC's range (e.g. a cut/paste from a DL450 program to a DL130 program). Thus, documentation can exist in ranges that are invalid for that PLC. Also, the selection of what documentation to print has nothing to do with the validity of the program. The bottom line is this is actually a feature, not a bug.
   
• (5) Is it possible to print out Cross Reference (Xref) on the Ladders printout?
  No, not yet. But we are considering putting this feature in later versions of DirectSOFT. Perhaps v5.0?
   
• (6) Getting various errors when trying to print (e.g. "Can't read from memory...")
  Sometimes the print layout file gets corrupted for various reasons. So the first thing to try is to delete the PRNTSERV.RST located in the folder c:\DirectSOFT4\Program\Bin.
   
• (7) When I do a Print Preview get "DSP4x.EXE" error and "Unable to save workspace. Disk is write protected or file is read-only!"
  This is caused by the Project files (mainly the .PRN and .WSP files) being write-protected. If you copied the project from another PC, a write-protected disk or a CD-ROM this can occur. To fix:
  1.  Close DirectSOFT.
  2.  Use Windows Explorer and browse to the location of your project.
  3.  Click on the first file of the project.
  4.  Hold the <Shift> key down and click on the last file of the project. (This will select the full range of your project files).
  5.  Right-mouse click on the group and select Properties.
  6.  Under Attributes, uncheck the Read-Only box.
  7.  Click Apply, or OK button.
   
• (8) Using "compressed" print and some of the Ladders lines are missing.
  Normally when you use compressed printing there is a loss of data in the printout. However, make sure that you are using the latest printer driver on your PC and Windows operating system.
   
• (9) When I try to print it appears to lockup.
  This is usually caused by an outdated print driver. Make sure you have the latest driver for your printer. (You can usually browse to your printer's manufacturer's website and download the latest drivers from there). Also, you might want to test it using Print Preview in DirectSOFT because DirectSOFT uses the same printer driver when generating the graphics for the Print Preview. Of course, if it works, then there might be something wrong with your printer, or the port.

FAQ0019
28-May-2002
Q: Importing CSV file causes DirectSOFT to crash.
A: We work very hard to keep all reported crashes from happening. If a crash happens with an import, the first thing to do is to upgrade to the latest Build for your version. So far this has fixed every case to date.

FAQ0020
28-May-2002
Q: Pressing the Default button for color options (View, Color Setup) does not restore the colors to their defaults.
A: This is a bug in v3.0c Build71 (or less), v4.0 Build16 (or less). To fix, upgrade to later versions. Temporary workaround is to:

1. Either set the colors manually back to the defaults in DirectSOFT (View, Color Setup) using the color matrix buttons:
   
   ATTRIBUTE NAME COLOR (right, down)
   Normal Background 1,1
   Uncompiled Background 2,3
   Unsaved to Disk Background 1,4
   Unsaved to PLC Background 3,2
   Disabled Background 3,3
   Selected Background 2,1
   Status Background 3,1
   Status Foreground 4,1
   Comment 6,4
   Description 6,2
   Wiring Info 4,5
   Nickname 5,1
   Element 6,5
   Token 6,5
    
2. Or, you must set the colors back manually in the .INI file as shown below.
   - To pull up the .INI file for editing, see DirectSOFT FAQ0204.
   - To edit the PROGRAM COLORS parameter in the .INI file, see DirectSOFT FAQ0008.
   
   [PROGRAM COLORS]
   0=0
   1=0
   2=0
   3=128
   4=8388736
   5=8421504
   6=8453888
   7=8421376
   8=16512
   9=16711680
   10=16777215
   11=65408
   12=12632256
   13=8454143
   14=16711680
   15=16776960
   16=12582912
   17=16777088
   18=0
   19=0
   20=0
   21=0
   22=0
   23=0
   24=0

FAQ0021
03-Jun-2002
Q: Help file is hard to use.
A: Host is continuing to update and improve the help file, but the manual is always up-to-date.

FAQ0022
15-Nov-2002
Q: Having trouble connecting to Port 1 of DL250. Port 2 works fine.
A: Port 1 is K-seq protocol only. Next, make sure the link properties are 9600 bps, 8 data bits, odd parity. Also don't rule out the possibility that the port on the DL250 could be bad, or that the cable is bad.

FAQ0023
12-Nov-2007
Q: Why are stages shown out of numerical sequence in Stage View?
A: The order is determined by a very complex algorithm and cannot be changed. However, we are considering options for future DirectSOFT releases.

FAQ0024
09-Dec-2002
Q: Need to scroll through the program that advances the screen to the next stage. Currently have to scroll down until it is found.
A: Should use Stage View. This allows one to navigate through Stages easily.

FAQ0025
19-Nov-2007
Q: How can I copy the links from one DirectSOFT installation to another?
A: The links in DirectSOFT are stored in the CommServ.RST file located in the Bin folder located under DirectSOFT. All you have to do is copy this file.

FAQ0026
15-Jan-2003
Q: What is the earliest version of DirectSOFT that supports Exporting Documentation?
A: DirectSOFT Programming v3.0.

FAQ0027
16-Jan-2003
Q: When you enable the Dump function in the DS500.INI file, where does it place the dump file?
A: After editing this parameter in the DS500.INI file you must start the Dbwin32.EXE program. Then in that window you can save the dump to any filename you like.
- To pull up the .INI file for editing, see DirectSOFT FAQ0204.
- To edit the Dump parameter in the .INI file, see DirectSOFT FAQ0008.

FAQ0028
17-Jan-2003
Q: Can DirectSOFT program an SA-21 (0.5K-words version of D3-330P)?
A: Yes.

FAQ0029
17-Jan-2003
Q: Saving or opening a project gets an error. "Couldn't open new database. Reopened failed." But can still get program to come up.
A: Check the Projects Path in the DS500.INI file and make sure it is pointing to a folder that you have access to.
- To pull up the .INI file for editing, see DirectSOFT FAQ0204.
- To edit the PROJECT PATH parameter in the .INI file, see DirectSOFT FAQ0008.

FAQ0030
21-Jan-2003
Q: What is the meaning of all the files in a project?
A: See DSP save and load chart2.pdf document.
Summary:

CSV - Comma seperated variable
CWB - Counter I/O configuration
DTA - Data view
DV - DV1000 setup
ERM - Ethernet remote master config
ESD - Element documentation (nickname, wiring info, description)
ESX - Index for element documentation
INF - Project information
LCD - Ladder comment data
LCX - Ladder comment index
LDA - Maps rung comments to rung #'s
LDO - Online only, maps rung comments to rung #'s (temporarily until saved offline to LDA file)
PID - PID documentation
PRJ - Ladder program
PRT - Print layout config
RD - 305 R-memory data
RF - 305 R-memory data editor format
SCD - Stage comments
SCX - Index for stage comments
TLS - PLC parameters, I/O configuration, pause bits
TXT - Text file
VD - V-memory data
VF - V-memory editor format
WSP - DirectSOFT window layout

In DirectSOFT v5.0 there is an additional file in the project:

XML - Docking-pane screen coordinates

FAQ0031
21-Jan-2003
Q: Is the 330S in DirectSOFT the same as a 330P?
A: Yes.

FAQ0032
21-Jan-2003
Q: Can source code of DirectSOFT be obtained?
A: The source code of DirectSOFT is not for sale.

FAQ0033
21-Jan-2003
Q: Does Host customize DirectSOFT for customers?
A: Customizing DirectSOFT is not something Host has the resources to devote to at this time (January 2003).

FAQ0034
24-Jan-2003
Q: Why do the messages in DirectSOFT come up in German?
A: You have Siemens Step7 software installed on your PC. First try renaming the MFC42LOC.DLL file to *.OLD and reboot. If that doesn't work you may have to uninstall both Step7 and DirectSOFT and then just reinstall DirectSOFT.

FAQ0035
10-Sept-2002
Q: Are there any plans to have Ladders view wrap around instead of scrolling?
A: Host Engineering does not have any plans to change the scrolling Ladders to a wrap-around view.

FAQ0036
10-Dec-2007
Q: What version of firmware in the DL-PLC is required for DirectSOFT v5.x IBoxes to function?
A: IBoxes are supported only in DL05, DL06, DL250-1, DL260 & DL450 CPUs:

FAQ0037 (similar to FAQ0013; see also DS Data FAQ0046)
03-Feb-2003
Q: First time starting DirectSOFT v4.0, crashes and gets CSMain.exe error.
A: The first thing to check is to make sure that IPX protocol is loaded for the NIC that is installed (see DirectSOFT FAQ0183 for installing protocols). Part of this problem was remedied in v4.0 Build 18 so upgrading may very well fix the problem. ReadMe_P.htm file says: "3. CommServer -- Fixed CommServer crash when IPX not installed -- we hope!" However, we know there are still some other issues centered around IPX protocol that we are currently debugging.

FAQ0038
16-Jul-2002
Q: Does DirectSOFT support USB converters that work, not as COM devices, but rather show up as an Ethernet device?
A: No. The type of USBs that DirectSOFT supports are those that show up as COM devices. Ethernet-to-USB will not work because in order to talk to Ethernet, DirectSOFT assumes that you have an ECOM. Thus if you make an Ethernet link, DirectSOFT wants to talk to an ECOM not a serial device. Thus when the Ethernet-to-USB converter converts the Ethernet signals to USB, then the serial device will not understand the ECOM protocol. See DirectSOFT FAQ0011 for compatible USBs.

FAQ0039
04-Feb-2002
Q: Will DirectSOFT export a Ladder file to Tisoft .VPU format?
A: No.

FAQ0040
18-Jun-2008
Q: Having various problems with documentation files (comments, etc.); can this be fixed?
A: There are known problems that can occur when documentation files get corrupted. When corruption has occurred it can cause quite a variety of unpredictable symptoms. Some of the more common:

• Documentation files (ESD, LCD, LDA, SCD) are huge!
• Strange looking characters.
• DirectSOFT locks up.
• Strange behavior when editing documentation (e.g. change one thing and two things change)
• Won't accept comment entries.
• Partial or incorrect printouts.
• Partial or incorrect documentation export file (.CSV or .TXT).
• "DSP4x.EXE - Application Error"
• "Error opening documentation"
• "Can't paste - We are sorry for the inconvenience"
• "Buffer overrun detected! C:\DirectSoft\Bin\esmain.exe"
• "Infinite Loop Timeout. Documentation Database may be corrupted. Or you may want to increase Infinite Loop Timeout setting." - This message is most likely caused by database corruption, but you could get it if you have an unusually large documentation database. To change the "Infinite Loop Timeout" setting you must edit the DSx00.INI file (see FAQ0008 & FAQ0204).

Corruption can happen over time due to system/software crashes, power loss, etc. To facilitate recovery, Host strongly recommends that you utilize the Backup Project feature (which originated in v4.0) to help minimize any rework. In times past some of these documentation corruptions have caused DirectSOFT to crash. Crashing behavior in all known cases to date have been remedied in later Builds of DirectSOFT. Therefore the first thing to do is to upgrade to the latest version. 

If the documentation is corrupt, sometimes it can be salvaged. There are 3 file critical to documentation:

ESX - This file is the database Index for the Element Documentation.
LCX - This file is the database Index for the Ladder Comments.
SCX - This file is the database Index for the Stage Comments.

If these files don't exist, don't worry, DirectSOFT will create them, building backward from the documentation files themselves:

ESD - This file is the database for Element Documentation.
LCD - This file is the database for Ladder Comments.
LDA - Maps Ladder Comments to Rung Numbers.
SCD - This file is the database for Stage Comments.

First, backup the project (if possible). Or print out the documentation. In DirectSOFT v4.0 there is a new Backup feature that allows you to create backups of your projects that are time stamped.

ELEMENT DOCUMENTATION ERRORS

1. Try Deleting the ESX file.
2. Open DirectSOFT and pull up the project.
3. Export the Documentation to TXT or CSV file.
4. Edit the TXT or CSV file and correct any mistakes.
5. Save the TXT or CSV file.
6. Import the documentation from the new TXT or CSV file, choosing the “Delete Existing” option.
7. Save the new project.

NOTE: If this doesn't work, you may have to repeat it, deleting not only the ESX file again, but also deleting the ESD file between Step 3 and Step 4 as well.

LADDERS COMMENT ERRORS

NOTE: If Ladders Comments are corrupted in DirectSOFT v3.0 there is no solution! To prevent the loss of Ladders Documentation in DirectSOFT v3.0 you should print it out often.

1. Delete the LCX file.
2. Open DirectSOFT and pull up the project.
3. Export the Program to TXT or CSV file, choosing the “All” option.
4. Edit the TXT or CSV file and correct any mistakes.
5. Save the TXT or CSV file.
6. Import the Program from the new TXT or CSV file, choosing the “Delete Existing” option.
7. Save the new project. 

NOTE: If this doesn't work, you may have to repeat it, deleting not just the LCX file again, but also deleting the LDA, LCD and LDO files between Step 3 and Step 4 as well.

STAGE COMMENT ERRORS

NOTE: If Stage Comments are corrupted in DirectSOFT v3.0 there is no solution! To prevent the loss of Ladders Documentation in DirectSOFT v3.0 you should print it out often.

1. Delete the SCX file.
2. Open DirectSOFT and pull up the project.
3. Export the Program to TXT or CSV file, choosing the “All” option.
4. Edit the TXT or CSV file and correct any mistakes.
5. Save the TXT or CSV file.
6. Import the Program from the new TXT or CSV file, choosing the “Delete Existing” option.
7. Save the new project. 

NOTE: If this doesn't work, you may have to repeat it, deleting not only the SCX file again, but also the SCD file between Step 3 and Step 4 as well.

FAQ0041 (see also ECOM FAQ0010)
04-Feb-2003
Q: Is it possible to run 2 NICs on 1 PC to 2 separate ECOMs?
A: Yes. But the only way Host has seen this work is if one NIC has IPX-only protocol loaded (and not TCP/IP), and the other NIC has TCP/IP-only protocol loaded (and not IPX). DirectSOFT has no other way to choose between which NIC to use. see DirectSOFT FAQ0183 for installing protocols.

FAQ0042
07-Jul-2002
Q: Used the "Save As..." function and lost documentation!
A: This was a known bug. If you used "Save As..." and then used the same filename for the project documentation would inadvertently get deleted! This was fixed in DirectSOFT v3.0 Build 62. However, the newer Build 71 and Build 71 patch reintroduced the bug because the code (contained in prgrm30.dll) that gets replaced is actually old Build 59 code (3.0.059). Problem completely eradicated in v3.0c Build 80 and any version of v4.0.

FAQ0043
19-Jun-2002
Q: Is there a color setup for monochrome monitors?
A: Monochrome color selection button (View --> Color options...) has been added to v4.0 Build 18. For earlier versions you: 

1. Either set the colors manually in DirectSOFT (View, Color Setup) using the color matrix buttons:
   
   ATTRIBUTE NAME COLOR (right, down)
   Normal Background 1,1
   Uncompiled Background 3,3
   Unsaved to Disk Background 3,3
   Unsaved to PLC Background 3,3
   Disabled Background 3,3
   Selected Background 4,5
   Status Background 6,5
   Status Foreground 1,1
   Comment 6,5
   Description 6,5
   Wiring Info 6,5
   Nickname 6,5
   Element 6,5
   Token 6,5
   
   
2. Or, set the colors manually in the .INI file as shown below.
   - To pull up the .INI file for editing, see DirectSOFT FAQ0204.
   - To edit the PROGRAM COLORS parameter in the .INI file, see DirectSOFT FAQ0008.
   
   [PROGRAM COLORS]
   0=0
   1=0
   2=0
   3=0
   4=0
   5=0
   6=8453888
   7=0
   8=16512
   9=16711680
   10=16777215
   11=12632256
   12=12632256
   13=12632256
   14=8421504
   15=0
   16=16777215
   17=12632256
   18=0
   19=0
   20=0
   21=0
   22=0
   23=0
   24=0

FAQ0044
04-Feb-2003
Q: Using DirectSOFT v2.0 Build 23, trying to communicate to DL250, get "Unknown PLC type" and then "Attempted access of unlocked device."
A: Support was added for the DL250 to DirectSOFT v2.1. Since this is no longer available, you should upgrade all the way to at least v2.4a. It's free and can be downloaded from Host website. See DirectSOFT FAQ0059 for a table showing which versions of DirectSOFT support which DL CPU.

FAQ0045
20-Dec-2007
Q: In the DL06, when Aliases are turned ON, why does the RX/WX instruction show V1200 as CTA200, but the LD instruction doesn't?
A: This has to do with the fundamental function of the addressing parameter of RX/WX instruction versus the LD instruction. The RX/WX parameter is the remote PLC's address, whereas the parameter of the LD instruction is the local PLC's address. Thus, with Aliases turned ON we chose to use the Aliases of the "biggest" DL-PLC that Automation Direct sells (DL450) for the naming of the RX/WX parameter. Examples:

In DL06 with Alias turned OFF:
     LD     V1200          ; No Alias names are displayed for any instruction.
     RX     V1200          ; No Alias names are displayed for any instruction.

In DL06 with Alias turned ON:
     LD     V1200          ; Not displayed as CTA200 because in DL06 counters only go to CTA177.
     RX     CTA200       ; The Alias for DL450's V1200 is used. DL450's counters go up to CTA377.

If, however, you use a smaller V-memory location in the DL06 we get:

In DL06 with Alias turned OFF:
     LD     V1177          ; No Alias names are displayed for any instruction.
     RX     V1177          ; No Alias names are displayed for any instruction.

In DL06 with Alias turned ON:
     LD     CTA177       ; V1177 = CTA177 in DL06.
     RX     CTA177       ; V1177 = CTA177 in DL450 as well.

To turn Aliasing ON or OFF:
     (1)  From DirectSOFT menu:  View --> Options...
     (2)  Select the Global tab.
     (3)  Check or Uncheck "Display Aliases".
     (4)  Press <OK>.

FAQ0046
04-Feb-2003
Q: Can you create an Ethernet link offline?
A: Yes.

For DS Launch:

1. Right-click on Comm Links.
2. Select "Add link..."
3. When the Link Wizard comes up, press the <Link Editor...> button.

If inside DirectSOFT:

1. Choose PLC --> Connect.
2. Press the <Add...> button.
3. When the Link Wizard comes up, press the <Link Editor...> button.

FAQ0047
04-Jan-2008
Q: When configuring a serial link using DirectSOFT, what does the "Radio Link" selection on the Port tab do?
A: This was added in DirectSOFT v4 Build 23 (25-May-2004) so that DirectSOFT could assert the DTR line for the CR-HN series radio modems Automation Direct sells.

FAQ0048 (see also ECOM FAQ0042; DL Plus FAQ0009; DNLoader FAQ0010; DSData FAQ0005; EZ Ethernet FAQ0008; HA-TADP FAQ0002; Lookout Direct FAQ0014; NetEdit FAQ0005; SDK FAQ0020)
31-Jan-2008
Q: Why doesn't the ECOM use subnet mask or gateway address like the ECOM100?
A: Since the ECOM doesn't do "master"-type communications, it doesn't use the subnet mask or gateway address. Whatever talks to the ECOM will be using IPX or UDP/IP, and the ECOM simply swaps the destination and source addresses in the telegram and responds in this way, not "caring" about the subnet or gateway. However, the ECOM100 acts more like a conventional TCP/IP device. The ECOM100 has the capability to be a master and has a full-blown TCP stack inside. Thus, if it is to transmit to an IP address not on its subnet, it will, of course, transmit to its configured gateway address instead.

FAQ0049
09-Feb-2003
Q: How do I upgrade to the latest version of DirectSOFT?
A: If you have DirectSOFT v4.0, or earlier versions, then you will have to order the upgrade from Automation Direct:

Automation Direct
3505 Hutchinson Road
Cumming, GA 30040
800-633-0405
http://www.automationdirect.com

If you already have DirectSOFT v5, then you can download maintenance upgrades by:

1. Go to http://www.hosteng.com . 
2. In the left column, under “Products” click “Software.” 
3. Click on “DirectSOFT” 
4. On the menu at the top, click on “Service Pack.”  

FAQ0050
19-Nov-2002
Q: Can I copy contacts from one rung to another?
A: This feature is not in the current versions of DirectSOFT (v3.0 Build 80; v4.0 Build 18) and there are no plans to add this to these versions. However, this feature will be included in v5.0 of DirectSOFT (no date as to release). Also, to get around this issue now, it is possible to Export the Program to a text file, then use the copy and paste of your favorite text editor to copy contacts from rung to rung. Then use the Import Program to get them back into DirectSOFT project.

FAQ0051
28-Aug-2002
Q: It would be nice to have the optional lines already added to the DS400.INI (or DS300.INI, DS500.INI) file, yet commented out, so one doesn't have to try to remember what to type in, or what heading to put them under, especially since these are not always documented.
A: Added the following to DS400.INI (& DS500.INI) file in DirectSOFT v4.0 Build 18 (to activate them, you simply remove the ";"):

[Comm Server]
;AutoSense=0 (To turn OFF autosensing of Comm Links during Comm Server startup.)

[devasync.dll]
;Dump=1 (To enable a dump of Serial Port debugging information.)

[devether.dll]
;UDPPortNumEnable=1 (To enable display of the UDP Port Number.)

- To pull up the .INI file for editing, see DirectSOFT FAQ0204.
- To edit the above parameters in the .INI file, see DirectSOFT FAQ0008.

FAQ0052
10-Dec-2002
Q: Can I open the same project with two instances of DirectSOFT on two different PCs?
A: No. If you do, then unpredictable results can happen. (e.g. comment files can be corrupted!). DirectSOFT doesn't comprehend other instances of itself wanting to use the same project file. It is only one client per project at a time. However, we are considering putting a mult-client feature in v5.0.

FAQ0053
12-Feb-2003
Q: Does DirectSOFT have problems opening up projects that are read-only?
A: Yes. DirectSOFT needs to open up the files as read/write.

FAQ0054
13-Dec-2002
Q: There is no information in the v4.0 Build 16 help file regarding the setup of the second comm port of the DL06 or the DL260.
A: This was added to Build 18. Read_Me.htm file says, "29. Setup Secondary Comm Port Dialogs now show correct Help files based on PLC type."

FAQ0055
12-Feb-2003
Q: How can I change the default project folder that DirectSOFT uses?
A: You must edit the PATH parameter in DirectSOFT's DS500.INI file. After changing this parameter, then when you use "Save" or "Save As..." or "Open," etc., this will be the default folder.

- To pull up the .INI file for editing, see DirectSOFT FAQ0204.
- To edit the PATH parameter in the .INI file, see DirectSOFT FAQ0008.

FAQ0056
18-Feb-2003
Q: If customer has an OEM-created DirectSOFT v2.0, can he update to v2.4 from website?
A: Yes.

FAQ0057
18-Feb-2003
Q: When trying to download and make diskettes for DirectSOFT v2.4a from website, get "Not enough space on disk."
A: You must first download the file on the website to your hard drive, then execute it (double-click), then choose "Make disks" from menu.

FAQ0058
19-Feb-2003
Q: What is the difference between the Demo version of DirectSOFT and the regular version?
A: Depending on which version of DirectSOFT demo you are talking about:

The DirectSOFT v3.x and v4.x DEMO version:

1. Can view any size Ladder program.
2. Can Save Online / Monitor Status on a 10 Ladder-word program (maximum) in the PLC.
3. Can Monitor Status on a maximum of 4 items in Data View.
4. Can have 4 Data Views maximum.
5. Can have only 1 Comm Link active at a time.
6. Can have only 1 Ladder (Stage, Mnemonic, XRef/Usage) View open at a time.
7. Cannot Save to Disk.
8. Displays a "Nag Dialog" encouraging customers to purchase the full version.
9. Cannot use the DRUM instruction that is available in some CPUs (because of the 10-word maximum of #1 above).

The DirectSOFT5 DEMO version (called DS100):

1. Cannot view any Ladder logic Online or open a Project with Ladder logic larger than 100 Ladder-words.
2. Can Save Online / Monitor Status on a 100 Ladder-word program (maximum) in the PLC.
3. If you create a Ladder logic program larger than 100 words, it will allow you to save it to disk, but you cannot re-open this project (see #1 above).

FAQ0059
20-Feb-2003
Q: Trying to load a project but getting "DirectSOFT recognizes the document <filename> but features or support level is not installed."
A: This error usually means one of the following two things:

• You are using a version of DirectSOFT to try to read a project file that was written for a PLC that is not supported in your version. (e.g. if the project was for a DL260 in v4.0 and you tried to use v2.4 to read it). See table below:

(1)  Partially compatible. The restriction is that the 250-1 local expansion I/O cannot be seen in DirectSOFT.

• Your project is corrupt to the point that DirectSOFT cannot read the PLC Type field in the project header - If this is the case you might try using File --> Export --> Program... and then closing DirectSOFT, reopening, and then using File --> Import --> Program... to see if the corruption gets cleared up.

FAQ0060
04-Mar-2003
Q: Can I use the RTS/CTS Flow Control setting in the Link Wizard to talk from DirectSOFT to DL PLC?
A: No. The reason is that the PLC port does not listen to its CTS line for incoming data. It only uses the Flow Control RTS/CTS lines when it wants to send data. So, if you choose RTS/CTS Flow Control in DirectSOFT, then when DirectSOFT wants to talk to the PLC, it will set the RTS line, which, if wired correctly, would tell the PLC it wants to send data. However, because the PLC is not listening to that line, it would never send DirectSOFT the CTS, so DirectSOFT would time out.

This begs the question, "Why is the Flow Control option selectable in DirectSOFT?" The answer is that if you used a Serial Link to say, COM1, and had an external modem, for example, the modem would be listening to the RTS line and would respond properly. But the PLC port does not function in this manner.

This also begs the question, "Why is Flow Control configurable on the PLC Port?" The answer is that it was specifically designed for sending data to the F2-UNICON and FA-ISONET devices.

FAQ0061
28-Feb-2003
Q: While a Ladders program is pulled up, can I switch to a different CPU?
A: Yes. Use PLC --> Disconnect; move the communication cable (if necessary); then use PLC --> Connect. However, keep in mind that a program has a CPU type associated with it. This is very necessary for programming due to the different ranges of the PLCs as well as their different functions. (You can display what CPU type is associated with the program by using File --> Properties). For example, there are many more functions available for a DL06 than there are for a DL240.

FAQ0062
06-Mar-2003
Q: After making a link to TI335 using an Automation Direct DCU, it is seen as a "stage CPU" and repeatedly gets "Knowledge base mismatch - cannot connect" error.
A: This is a known problem with a TI335. Here are some things to try:

• Power up the TI335 in Program Mode.
• Make sure dipswitch #6 is set to ON.
• Check Hex/ASCII mode setting in the link.
• A DCU is not really necessary. Instead you can connect directly with a cable.

FAQ0063 (see also ECOM FAQ0013)
06-Mar-2003
Q: Connecting to DL PLC with ECOM and getting "????" as the CPU type; or just getting communications errors.
A: Check the following:

• If using H4-ECOM, check for bent pins on ECOM or CPU; or possible bad ECOM, CPU or base.
• If using H2-ECOM make sure ECOM is not in slot 0.
• If using H2-ECOM and DL260, you must have at least DirectSOFT v4.0 Build 18 for the "????" to not be displayed.
• If using H2-ECOM and DL250-1 and DirectSOFT v3.0, must have at least Build 80 for the "????" to not be displayed.
• If using H0-ECOM make sure the PLC firmware is up-to-date.
• If using H0-ECOM and a D0-06LCD, make sure it has a date code of 032A or later.

FAQ0064
04-Feb-2008
Q: How can I disable/enable the "DirectSOFT on the Web" feature in DSLaunch?
A:  By default, the "DirectSOFT on the Web" feature is enabled in DSLaunch.

• To DISABLE:  Right-click on the "DirectSOFT on the Web" icon in DSLaunch and select "Hide".
• To ENABLE:  You must edit the DS500.INI file (for editing this file see DirectSOFT FAQ0204), and set the OnTheWeb parameter back to 1:
  
  [DSLaunch]
  OnTheWeb=1

FAQ0065 (similar to DS Data FAQ0009; see also DS Data FAQ0034; ECOM FAQ0014)
07-Mar-2003
Q: How can I speed up the data throughput of my ECOM?
A: Consider the following:

1. Give the ECOM an isolated network if possible, as network traffic can effect data through-put.
2. ECOMs do at least 1 comm cycle of approximately 128 bytes per PLC scan, but in faster CPUs (e.g. DL260, DL05, DL06) it can do as many as 3. So using a faster PLC CPU will help. 
3. Since the ECOM comm cycle is PLC scan dependent, then anything you can do to make the PLC scan faster will help. 
4. Make sure no other applications or devices are talking to the same PLC via the same ECOM or serial port (e.g. like having DirectSOFT doing status while DS Data is running, or PLC doing/responding to RX/WX from other PLC). There is only so much bandwidth between the serial port/ECOM and the CPU itself.

FAQ0066 (see also ECOM FAQ0016; DS Data FAQ0089)
20-Mar-2008
Q: How can I make a link with DirectSOFT (or DS Data) to a single ECOM/ECOM100 or multiple ECOMs/ECOM100s over the Internet?
A: There are a number of ways to accomplish this due to the versatile ways in which Internet connectivity is established.

Method #1 (Direct Connect): Requires the remote ECOM/ECOM100(s) to have a registered Internet IP address.
Method #2 (Indirect Connect): Requires access to the remote gateway/router which must be configured to translate TCP port #s.
Method #3 (ISP VPN): Requires the ISP (Internet Service Provider) set up a VPN (Virtual Private Network).
Method #4 (VPN Software): Requires the use of some form of VPN software (e.g. PC Anywhere, LogMeIn, etc.).

NOTE: Host Engineering, Inc has a single ECOM on the Internet that you can practice with. Its IP Address is 12.69.41.166.

Method #1 (Direct Connect)

Multiple ECOM/ECOM100 Instructions: In this method if connecting to multiple ECOM/ECOM100s, it is assumed that each ECOM/ECOM100 has its own registered Internet IP address and therefore to connect to each of them only requires that you make separate links to each one.

DirectSOFT Link Configuration to connect to PLC1:
     1.  Build link in DirectSOFT.
          a.  On PLC tab select:
                    PLC Family - Direct LOGIC 205 Series
                    PLC Type - 250

          b.  On the Port tab select:
                    Devices - Ethernet
                    Transport - Winsock
                    Transport Protocol - UDP/IP
                    Node Address - IP Address 12.69.41.166 (Registered Internet IP Address of Host's ECOM)
                    Advanced Settings - Timeout (Increase?)
 
               NOTE: To determine how much the "Timeout" setting should be increased:
                               1.  Go to the DOS Command Prompt (Start --> Programs --> Accessories --> Command Prompt)
                               2.  Type in:    ping 12.69.41.166
                               3.  Make note of the "Maximum" time as listed and increase this number by at least 50%.
                               4.  Enter this number as the "Timeout" setting.

                    UDP Port Number (if it is displayed) - 28,784 (this is the default; must always be this number)

          c.  On the Protocol tab select:
                    Protocols - ECOM

          d.  Click <Auto>. Should beep for success.

          e.  Enter a name for the link and click <Accept>.

Method #2 (Indirect Connect)

Multiple ECOM/ECOM100 Instructions: In this method if connecting to multiple ECOM/ECOM100s, they are assumed to be located behind the gateway/router on an internal network with internal IP addresses assigned to them. Therefore, the DirectSOFT (or DS Data) links to each of them must use the same IP address of the gateway/router (because from the Internet, that is all it can see). Thus, the only way to differentiate between the multiple ECOM/ECOM100s on the other side of the gateway is by DirectSOFT (or DS Data) using different TCP port #s for each. In order to accomplish this 2 things must be done: (1) DirectSOFT (or DS Data) must have this feature turned ON by editing the .INI file, and (2) the remote gateway/router must be configured to translate the TCP port #s to different IP addresses behind its firewall.

DirectSOFT Link Configuration to connect to PLC4:
     1.  Edit .INI file and set UDPPortNumEnable=1
          - To pull up the .INI file for editing, see DirectSOFT FAQ0204.
          - To edit the UDPPortNumEnable parameter in the .INI file, see DirectSOFT FAQ0008.

     2.  Build link in DirectSOFT.
          a.  On PLC tab select:
                    PLC Family - Direct LOGIC 205 Series
                    PLC Type - 250

          b.  On the Port tab select:
                    Devices - Ethernet
                    Transport - Winsock
                    Transport Protocol - UDP/IP
                    Node Address - IP Address 12.69.41.166 (Registered Internet IP Address of Gateway/Router)
                    Advanced Settings - Timeout (Increase?)
 
               NOTE: To determine how much the "Timeout" setting should be increased:
                               1.  Go to the DOS Command Prompt (Start --> Programs --> Accessories --> Command Prompt
                               2.  Type in:    ping 12.69.41.166
                               3.  Make note of the "Maximum" time as listed and increase this number by at least 50%.
                               4.  Enter this number as the "Timeout" setting.

                    UDP Port Number -