SoftPLC
 
Font size:      

Configuration

Configuration Editor Usage

RIOSLAVE.LST file editor


Load button will load the configuration file from the development system's disk.

Save button will write the configuration file to the development system's disk.

Fetch button will load the configuration file from the runtime system's disk.

Send button will write the configuration file to the runtime system's disk. The next step is to restart or cycle power on the SoftPLC for the changes to take place. As an alternative to cycling power, you may enter "Remote Program" mode using NexGen, then select "Remote Program" a second time. This psuedo transition from Remote Program to Remote Program is a signal to the TLM that it should reload its configuration file. This way you can reconfigure without cycling power, although it does require you enter "Remote Program" mode (twice!).

RIO.LST Configuration File Details

The configuration file for the RIO TLM is /SoftPLC/tlm/RIO.LST. This file is used to set the debug level, baudrate, termination resistor on/off state, and the I/O Bus Addresses and associated SoftPLC Datatable assignments for each RIO network.

;Configuration file for SoftPLC RIO.TLM. 

;Any part of any line in this text file to the right of a semicolon is a 
;comment and will be ignored by the TLM. 

;There are 4 sections in this file: [DRIVER], [CARDS], [INPUTS], 
;and [OUTPUTS]. 


;[DRIVER] is a place for global parameters. 


;[INTERFACES] lists each RIO interface (i.e. bus or cable) in the system on 
; a separate line. 
; There are columns for PortNum, and Baudrate. 
; PortNums start at zero and go up from there. 
; Baudrate must be one of 57600, 115200, or 230400. 


;[INPUTS] lists blocks of words that are to be copied from each 
;interface into the SoftPLC input image table as part of the I/O scan. 
;Only I:xxx type addresses may be used here.  DtAddr is the 
;memory address within SoftPLC and must be in the I: datatable section. 
;IOBusAddr is the address that is determined by the physical rack and slot 
;used on an RIO bus. 
;Each row in this section describes a block whose length is 
;given by NumWords.  A block may be as long as you like, and 
;sometimes you will have only one block, other times you might 
;have several.  This scheme lets you map any IOBusAddr 
;to any real input DtAddr. 


;[OUTPUTS] lists blocks of words that are to be copied from 
;SoftPLC's output image table onto a bus as part of the I/O scan. 
;Only O:xxx type addresses may be used here.  DtAddr is the 
;memory address within SoftPLC and must be in the O: datatable section. 
;IOBusAddr is the address that is determined by the physical rack and slot 
;used on an RIO bus. 
;Each row in this section describes a block whose length is 
;given by NumWords.  A block may be as long as you like, and 
;sometimes you will have only one block, other times you might 
;have several.  This scheme lets you map any DtAddr 
;to any one or more real output IOBusAddrs.  The same DtAddr may 
;be mapped to more than one output IOBusAddr. 


;A "word" corresponds to an I/O group, and this is the granularity 
;given by this configuration strategy. 
;Unlike AB PLC's, with this SoftPLC RIO driver, both the I:ABC and O:ABC 
;at a given ABC DTAddr element may both be used simultaneously. 

 
[DRIVER] 
DEBUG=0       ; set to 0 or 1 


[INTERFACES] 
;PortNum        Baudrate    TermResistor 
0               230400       no   ;COM5
;1              115200       no   ;COM6


[INPUTS] 
;DtAddr         NumWords    PortNum     IOBusAddr 
I:000           64         0           I:000 


[OUTPUTS] 
;DtAddr,        NumWords,   PortNum,    IOBusAddr 
O:000           64         0           O:000 


;EOF