DirectSOFT Comm Link Problems
DirectSOFT Comm Link Problems
COMMON ISSUES
PICK THE GROUP OF INSTRUCTIONS BELOW THAT BEST APPLIES TO YOUR PC.
If you have WinVista, skip to the heading WinVista below. If not, read the information under the
heading WinXP & Win7.
If you have DirectSOFT v3, then the .INI file must be searched for and manually edited. The
easiest way to do this is:
(1) Close DirectSOFT and DSLaunch.
(2) Use the Windows Start button: Start Run
(3) Type in ds300.ini and press <OK>. This will open the file in NotePad text editor.
(4) Make the edits; save the file and exit.
(5) Restart DSLaunch (or DirectSOFT).
If you have DirectSOFT v4, v5 or v6, then the easiest way to edit this file is:
(1) Close DirectSOFT.
(2) Start DSLaunch.
(3) In the left column under Utilities, double-click DS400.ini (or DS500.ini, or DS600.ini).
This will open the file in NotePad text editor.
(4) Make the edits; save the file and exit.
(5) Restart DSLaunch (or DirectSOFT).
Another thing to try if the above doesnt work:
(1) Close DirectSOFT.
(2) Click Start button.
(3) In the Search programs and files box, type in DS400.ini (or DS500.ini, or DS600.ini).
(4) Click on the search result and edit that file; save the file and exit.
(5) Restart DSLaunch (or DirectSOFT).
1|Page
WINVISTA
WinVista has some extra protection features, so the above procedures may not work depending on
its settings. WinVista has a feature called UAC (User Access Control) that is, by default, turned on.
However, it is possible to turn this feature off, and this dramatically affects the editing of the .INI
file. To modify the UAC setting:
(1) Use the Windows Start button: Start Control Panel.
(2) Click on User Accounts.
(3) Click on Turn UAC ON/OFF.
This will tell you if this feature is on or off. Depending on this setting go to the proper heading below
(UAC=ON or UAC=OFF).
UAC=ON
With UAC=ON, the security measures of WinVista create a virtual store copy of your .INI file and
redirect DirectSOFT to use this copy instead of the one that is normally stored in the C:\Windows
folder.
If you have DirectSOFT v3, v4, v5.0 or v5.1 then you will have to find this file manually and
edit it:
(1) Close DirectSOFT and DSLaunch.
(2) Use Windows Explorer to browse to:
c:\Users\<username>\AppData\Local\VirtualStore\Windows\
(3) Find the DS300 (or DS400, or DS500, or DS600.INI) file and open it with NotePad.
(4) Make your edits; save the file and exit.
(5) Restart DSLaunch (or DirectSOFT).
2|Page
3|Page
If you have a DL05, DL06 or DL405 PLC, there are LEDs on the right side of the DL05/DL06
PLCs and on the front of the DL405 PLCs that show comm port activity. On the DL05/DL06
they are marked RX1 or RX2 and they will blink if the port is seeing activity. The DL405 has
a general RX LED and it will report any activity on any comm port, so it is less useful unless
you are sure nothing else is connected to the CPU.
Blinking at least means there is a valid electrical signal being received and it could merely
be a baud or parity setting issue. Not that on the DL05/DL06 Port 1 (the RJ12 style), these
settings are fixed at 9600, odd parity, 1 stop bit, so make sure the software link matches
these settings. On the DL405 only the 15-pin port has fixed settings.
DL205 PLCs do not have any LEDs for serial communication so they can be more
problematic. Port 1 (RJ12) is fixed like the DL05/DL06 PLCs, so this is always the best
choice when trying to connect initially.
The other additional ports of the PLCs can be configured so it is possible if the CPU is not
brand new, that they have been previously configured with settings that DirectSOFT cannot
connect with.
USER-MADE CABLES
The PC side of the cable must have pins 7 and 8 jumpered. Also if you have one of the PLCs
mentioned above with communication LEDs, look for RX activity. If you dont see it, try swapping
the RX and TX wires. We always recommend our premade cables. They are inexpensive and proven.
4|Page