Subversion Repositories Brabant Water.oosterhout

Rev

Blame | Last modification | View Log | Download 

README.

                    MODSOFT TCP/IP SETUP INSTRUCTIONS


THESE INSTRUCTIONS ARE APPLICABLE UNDER THE DOS/WINDOWS 3.X, 
WINDOWS 95 AND WINDOWS NT OPERATING SYSTEMS FOR ACCESS TO A PLC 
VIA TCP/IP(TRANSPORT CONTROL PROTOCOL/INTERNET PROTOCOL) OR VIA DECnet.

NOTE: 
Please read and completely understand these instructions before
installation.  If a networking system administrator exists at your
site, it is suggested that you have him/her review these
instructions before proceding.

IMPORTANT: 
Please see Sections B.1 and B.2 for install changes specific
to DECnet.


I. Quick Setup for WIN 95 and WIN NT:

NOTE: 
-For setup under WIN 3.1 or inconsistencies in the quick setup with your system, 
 refer to the detailed instructions in section III.
-The quick setup assumes you installed Modsoft in the default C:\modsoft
 directory

 A.) FOR WIN '95 SYSTEMS

     1) Edit the VSLDOS.INI file located in c:\modsoft\vsl.  
       a) Go to the uncommented line   TRANSPORT=   ;  
          Type in the <netkey>.   Example: TRANSPORT=WINSOCK
       b) Go to the line that reads: NETMODULE=;
          Type in  NETMODULE=JSBW95WS
       c) Save file.

     2) Copy the HOSTS.SAM file to HOSTS in the directory c:\windows
       a) Go to the uncommented line in the HOSTS file that reads 
          127.0.0.1 localhost
       b) Replace that line with:
          <IP_address of the machine>  <your_IP_alias> localhost

            Example:  205.111.123.5 jdoe@inst.com localhost   
       c) Save file

     3) Go to the directory C:\WINDOWS, and edit SYSTEM.INI
       a) Add a line under section [386Enh] that reads:
          DEVICE=C:\MODSOFT\VSL\JSBDOSWS.VXD
       b) Save file

     4) Go to the root directory and edit AUTOEXEC.BAT
       a) Add line:
          SET VSL=C:\MODSOFT\VSL
       b) Save file
   
     5) Reboot the system.  


 B.) FOR WIN NT SYSTEMS

     1) Edit the VSLDOS.INI file located in c:\modsoft\vsl.  
       a) Go to the uncommented line   TRANSPORT=   ;  
          Type in the <netkey>.   Example: TRANSPORT=WINSOCK
       b) Go to the line that reads: NETMODULE=;
          Type in  NETMODULE=JSBWNTWS
       c) Save file.

     2) Copy the HOSTS.SAM file to HOSTS in the directory C:\WINNT
       a) Go to the uncommented line in the HOSTS file that reads 
          127.0.0.1 localhost
       b) Replace that line with:
          <IP_address of the machine>  <your_IP_alias> localhost

            Example:  205.111.123.5 jdoe@inst.com localhost   

       c) Save file

     3) Copy the HOSTS.SAM file to HOSTS in the directory \I386
       a) Go to the uncommented line in the HOSTS file that reads 
          127.0.0.1 localhost
       b) Replace that line with:
          <IP_address of the machine>  <your_IP_alias> localhost

            Example:  205.111.123.5 jdoe@inst.com localhost   

       c) Save file

     4) Go to the file C:\WINNT\SYSTEM32\AUTOEXEC.NT
       a) Add 2 lines to this file:  CD C:\MODSOFT\VSL and JSBDOSWS.EXE
       b) Save file

     5) Go to START button
       a) Select SETTINGS->CONTROL PANEL, from the control panel select 
          the SYSTEM icon.
       b) Select the TAB environment
       c) There are two fields labelled  VARIABLE and VALUE
       d) In the VARIABLE field, type VSL
       e) In the VALUE field, type C:\MODSOFT\VSL 
       f) Click on SET and then OK 

     6) Reboot the system   

II.  DETAILED OVERVIEW

     A.)  Modsoft install for TCP/IP access to a programmable
          logic controller.
 
    1) Under the DOS or Windows 3.x Operating Systems:
    install the DOS TSR (Terminate-and-Stay-Resident)
    based TCP/IP stack. (Note: Win95 already has a TCP/IP
    stack installed.)

    2) Install Modsoft from installation diskettes.

    3) Edit the vsldos.ini configuration file; for
    Win95 and Windows NT edit the hosts file and for Win95
    edit the \windows\system.ini file.
    
    4) Set the VSL environment variable.

    5) Load Network and Network Module (netmod) drivers.

    6) Using Modsoft with TCP/IP.


     B.)  Modsoft installation changes for DECnet access to a
          programmable logic controller.

    1) Set the VSL environment variable.

    2) Load the DECnet Network Module (netmod).


III.  DETAILED INSTRUCTIONS
 A.1  INSTALLING THE DOS TSR BASED TCP/IP STACK.

      NOTE: 
      For Win95 this step is NOT necessary.

      For Windows NT:
      Although a TCP/IP stack is deliverable with Windows NT, you must still
      install a TSR for TCP/IP communications. The TSR is called jsbdosws.exe
      and is under the <modsoft_installation_directory>\vsl directory. 
      It is recommended that you add the following lines to your autoexec.nt
      file:   cd <modsoft_installation_directory>\vsl
         jsbdosws.exe
      The autoexec.nt file is found under the 
         <windows_nt_installation_directory>\system32 directory.
      You may also load the TSR at the DOS command line BUT YOU MUST BE
      in the <modsoft_installation_directory>\vsl directory when you load it.

      For DOS and Windows 3.1:
      Follow the stack-provider's install-instructions.  
      Verify that the stack is installed correctly.
      Once the TCP/IP stack is installed, verify connectivity.  To verify
      IP-to-IP connectivity use the ping program.  i.e.- ping  <some_host>
      To verify TCP-to-TCP connectivity use a TCP application program like
      telnet.  i.e.- telnet <some_host>

      Modsoft 2.51 supports the following TCP/IP stacks:

      DOS TCP/IP STACK                                        VSL NETWORK KEY
                                                                 (netkey)
 
      3Com 3+Open TCP v1.0, 1.1, 1.2, 2.0, 2.1                     3open
      Beame and Whiteside TCP/IP v2.2, 2.3, 3.0                    bw
      Digital Pathworks for DOS (TCP/IP) v4.1                      decnet
      D-Link TCP/IP for DOS v2.0                                   locus2
      FTP PC/TCP v2.04, 2.05, 2.1                                  ftp
      FTP PC/TCP v2.2, 2.3                                         ftp22
      HP ARPA Services for DOS v2.1                                3open
      IBM TCP/IP                                                   ibmtcp
      Locus TCP/IP for DOS v2.0                                    locus2
      Microsoft LAN Manager for MS-DOS (TCP/IP) v2.1 2.1a, 2.2     lanman
      Novell LAN Workplace for DOS v4.0, 4.01, 4.1, 4.12           novlwp
      Sun PC/NFS v3.0                                              pcnfs
      Sun PC/NFS v3.5, 4.0a, 5.0, 5.1.5                            pcnfs2
      Ungermann-Bass Net/One TCP/IP v16.4, 16.5, 16.6              netone
      Walker Richer and Quinn Reflection Network Series v2.1       3open
      Wollongong Pathway Access v1.1, 1.1.1, 1.1.2, 1.2, 2.0, 3.0  pathway
      Wollongong WIN/TCP for DOS v4.1.1                            wintcp
      Windows 95                                                   winsock
      Windows NT TCP/IP                                            winsock 


 A.2  INSTALL MODSOFT FROM INSTALLATION DISKETTES.

      Follow the install procedures outlined in the Modsoft Programmer
      User Manual.


 A.3  EDIT THE VSLDOS.INI CONFIGURATION FILE, AND FOR WIN95/Windows NT, 
      EDIT THE HOSTS FILE AND FOR WIN95 EDIT THE \WINDOWS\SYSTEM.INI FILES.

      The vsldos.ini file is located in the <modsoft_installation_directory>\VSL 
      directory.

      Each  supported TCP/IP stack has a VSL network module (netmod) and 
      corresponding netkey.  Record that netkey in the vsldos.ini file,
      with your editor-of-choice.

      In the vsldos.ini file there is a heading entitled [vsl-default].  The
      first uncommented line following this heading (commented lines begin
      with a semi-colon) should read:  transport=.

      After the edit of  the former, the line should read:  transport=<netkey>
      where <netkey> is the VSL network key that corresponds to the installed
      TCP/IP stack.  For example, if Novell's Lan Workplace for DOS is the TCP/IP
      stack installed, then the first uncommented line following the [vsl-default]
      heading should read: transport=novlwp. Another example: if you are using
      Win95 or Windows NT, then the first uncommented line following 
      the [vsl-default] heading should read: transport=winsock.  
 
      A list of  netkeys is above in Section A.1, for your convenience, and also
      in the vsldos.ini file.

      For Windows NT: find the section of the vsldos.ini file that has the heading
      [winsock-transport].  Go to the line that reads: netmodule=.  For Win95
      that line should read netmodule=JSBW95WS; for Windows NT it should read 
      netmodule=JSBWNTWS.  Save the vsldos.ini file after you make the modification.
      For Win95 and Windows NT, copy the hosts.sam file (for Win95 the file is 
      under the \windows directory; for Windows NT it is under both the \i386 
      and the <windows_nt_installation_directory>) to hosts.  Replace the first 
      uncommented line in the file that reads: 127.0.0.1 localhost with 
      <your_IP_address_in_dot_notation_form>  <your_IP_alias> localhost.

      For example:

            84.31.1.1 jdoe@inst.com localhost

      For Win95, add a line to the \windows\system.ini file under the
      [386Enh] section that reads:
            device=<modsoft_installation_directory>\vsl\jsbdosws.vxd
     
      Note: The computer will have to be rebooted to have that change take
      effect.


 A.4  SET THE VSL ENVIRONMENT VARIABLE

      Modsoft 2.5 TCP/IP communications requires the setting of the VSL
      environment variable.  

      It is suggested that this environment variable be set in your autoexec.bat
      file.

      Type:  set VSL=<modsoft_installation_directory>\vsl

      For NT: go to Start button, select Settings->Control Panel->System.
      Select the TAB   Environment.  There are two fields labelled Variable 
      and Value near the end of the tab screen. 

      In the Variable field, type VSL.
 
      In the Value field, type drive:<modsoft_installation_directory\vsl


      Helpful hint:  If you have installed Novell's Lan Workplace for DOS (LWP),
      there is a barely-documented environment variable, EXCELAN, that is required.
      It must be set to the installation directory of the LWP software.


 A.5  LOAD NETWORK AND NETMOD DRIVERS
      NOTE:  For Win95, this step is NOT necessary.

      For Windows NT, the netmod, jsbdosws.exe, is the only driver you must load.
      Although a TCP/IP stack is deliverable with Windows NT, you
      must still install that TSR for TCP/IP communications. It is under the
      <modsoft_installation_directory>\vsl directory. 
      It is recommended that you add the following lines to your autoexec.nt file:
         cd <modsoft_installation_directory>\vsl
         jsbdosws.exe
      The autoexec.nt file is found under the 
         <windows_nt_installation_directory>\system32 directory.
      You may also load the TSR at the DOS command line BUT YOU MUST BE
      in the <modsoft_installation_directory>\vsl directory when you load it.
      (Note: the rest of this is not necessary for Windows NT.)
      Load all network drivers, in ISO-layered order.
      i.e.- physical, link, network, transport.

      Then load the network module (netmod).

      The netmod is located in the <modsoft_installation_directory>\vsl.
      Load it after the load of  TCP/IP.  Note: you do not have to load TCP/IP
      for Windows NT.   The netmod is an executable,
      with extension, .exe, with the same name as the network key BUT
      preceded by the letter, m.
   
      For example: if you have installed Novell's Lan Workplace for DOS (LWP)
      the VSL network key  (from above) is listed as, novlwp, thus the VSL
      network module is mnovlwp.exe.  

      To load the netmod change to the <modsoft_installation_directory>\vsl.
      Type: mnovlwp.
 
      Note: It is suggested that the load of all drivers take place in a batch file,
      that is invoked on power-up of your computer. 

      An example follows, and assumes the LWP stack is installed:

            lh LSL
            lh 3C509
            lh IPXODI
            lh VLM
            lh TCPIP
            MNOVLWP


 A.6  USING MODSOFT WITH TCPIP

      To access a controller via TCP/IP in Modsoft, select TCP/IP under Protocol 
      from either the Offline|Change Plc Address sub-menu or the 
      Online|Direct to Plc sub-menu. (TCP/IP access is also available from
      the Utility|Quantum Backplane|Direct to Plc sub-menu and the 
      Utility|PLC & IO Status|Direct to PLC sub-menu.)

      The Dest_Port should remain at 502, the default.  The port, 502,
      is Schneider Automation's well-known TCP/IP port and would
      only change if testing to a firewall.

      The Dest_Index should remain at 0, the default, unless you are
      using Schneider's Modbus Plus to Ethernet bridge to talk between
      a NOE and a MB+ node.  A destination index of 0 accesses the PLC
      at Head 0.

      Input the IP address, symbolically or in dot notation, of the Network Options
      Ethernet (NOE) module in the TCP/IP Address field.  No broadcast/multicast
      IP address will be accepted.

      Note: the IP address (or the translated symbolic address) must agree 
      with the IP address in the configuration extension of the controller you want
      to access.  It is essential that the configuration extension be correctly
      set-up in order to access the NOE module via TCP/IP.  See the  Modicon
      Quantum Ethernet TCP/IP Module User Guide for details. (part # 840 USE 107 00)




 B.1  SET THE VSL ENVIRONMENT VARIABLE

      The virtual socket library (VSL) is used in Modsoft 2.5 (and beyond) to
      provide access to a PLC via DECnet.  

      The VSL requires the setting of the VSL environment variable.
 
      It is suggested that this environment variable be set in your autoexec.bat
      file.

      Type: set VSL=<modsoft_installation_directory>\vsl




 B.2  LOAD THE DECnet NETWORK MODULE (netmod)

      Load all DECnet drivers.
 
      Then load the network module (netmod), mdecnet.exe.

      The netmod is located in the <modsoft_installation_directory>\vsl.
 
      To load the netmod change to the <modsoft_installation_directory>\vsl.
 
      Type: mdecnet.
 
      An examples follows, and assumes the load of the DECnet drivers
      delivered with BGAT:

            lh dllndis
            lh netbind
            lh sch /h
            lh dnnethat
            mdecnet
 
 
TRADEMARKS:
DECnet is a Registered Trademark of Digital Equipment Corporation.
Modsoft and BGAT (Base Gateway) are Registered Trademarks of
Schneider Automation, Inc.
Win95, Windows NT and Windows 3.x are Registered Trademarks of the Microsoft
Corporation.
DOS is a Registered Trademark.