Conference varese::basestar_open

    An example of ODS and BASEstar Open configuration working with the 
    DAS for RSLinx.
    
-----------------
ODS configuration
-----------------

reg dir name "/cn=DTL_KA1" attr "/oc=DTL/portid=1KA:2
/netaddress=xxx.xxx.xxx.xxx/stationid=001/rsptimeout=10/niid=1"

reg dir name "/cn=DTL_KT1" attr "/oc=DTL/portid=1KT:0
/netaddress=xxx.xxx.xxx.xxx/stationid=001/rsptimeout=10/niid=0"

reg dir name "/cn=DTL_RM1" attr "/oc=DTL/portid=0RM:3
/netaddress=xxx.xxx.xxx.xxx/stationid=001/rsptimeout=10/niid=1"

reg dir name "/cn=DTL_EI1" attr "/oc=DTL/netaddress=xxx.xxx.xxx.xxx
/rsptimeout=10/niid=1"
                    


---------------------------
BASEstar Open configuration
---------------------------

set scope volatile
!
create node MY_NODE -physical "xxxxx"
!
create protocol_profile AB5_40_PPF \
-maxpdusize 521 -APPLPROFID 81
!
create vmd DTL_EI1 \
-model "PLC_5_40" -vendor "AB" \
-client_acc ("":BSTR_MMS) \
-dvm_acc "/CN=DTL_EI1":AB5_40_PPF
!
create actor /A1
!
create domain /DTM
!
create program /A1/PRG_DVM -program_kind DATADEV
!
create activity /A1/ACT1 \
-program /A1/PRG_DVM \
-STARTUP_PRIORITY 2 \
-SHUTDOWN_PRIORITY 3 \
-STARTUP_TIMEOUT 60 \
-SHUTDOWN_TIMEOUT 30 \
-DOMAINS (/DTM) \
-vmds (DTL_EI1) \
-node (MY_NODE) 
!
exec actor -w
!
create array_datatype string -datatype VISIBLE_CHAR -num_of_elements 8
create array_datatype array_001 -datatype INTEGER_16 -num_of_elements 8
!
! UNNAMED VARIABLES
!
create unnamed_var DTL_EI1.VAR_BOOL \
-access READ -send ALWAYS \
-datatype BOOLEAN -address "B3:0" \
-addrtype UNCONSTRAINED
!
create unnamed_var DTL_EI1.VAR_UN16 \
-access READ -send ALWAYS \
-datatype UNSIGNED_16 -address "N7:1" \
-addrtype UNCONSTRAINED
!
create unnamed_var DTL_EI1.VAR_IN32 \
-access READ -send ALWAYS \
-datatype INTEGER_32 -address "N7:3" \
-addrtype UNCONSTRAINED
!
create unnamed_var DTL_EI1.F001 \
-access READ -send ALWAYS \
-datatype F_FLOAT -address "F8:0" \
-addrtype UNCONSTRAINED
!
create unnamed_var DTL_EI1.STR005 \
-access READ -send ALWAYS \
-datatype string -address "A9:0" \
-addrtype UNCONSTRAINED
!
create unnamed_var DTL_EI1.ARR001 \
-access READ -send ALWAYS \
-datatype array_001 -address "N7:4" \
-addrtype UNCONSTRAINED
!
! DEVICE DATA POINTS
!
CREATE DEVICE_DATA_POINT /DTM/DP_RECEIVE001 \
-VMD_NAME DTL_EI1 \
-VAR_NAME VAR_BOOL \
-VAR_CLASS UNNAMED \
-DATATYPE BOOLEAN \
-DEVICE_ACCESS READ \
-UPDATE_POLICY SOLICITED \
-ACCESS_POLICY ALWAYS
!
CREATE DEVICE_DATA_POINT /DTM/DP_SEND001 \
-VMD_NAME DTL_EI1 \
-VAR_NAME VAR_UN16 \
-VAR_CLASS UNNAMED \
-DATATYPE UNSIGNED_16 \
-DEVICE_ACCESS WRITE 
!

Hi Costanzo,

    About the example of ODS and BASEstar Open configuration working with the 
    DAS for RSLinx.

	When i type the following line: 
    
reg dir name "/cn=DTL_KA1" attr "/oc=DTL/portid=1KA:2
/netaddress=xxx.xxx.xxx.xxx/stationid=001/rsptimeout=10/niid=1"

	the following error occurs:
	"Object class DTL unrecognized"

	Should i define some schema previously ?

	What is defined by the attribute netaddress ?

	How does the B* know that it has to communicate with DAS RSLinx,
instead of another DAS ?

	Thanks for your help,
	Marcius Machado

Hi Marcius, 
    
>    About the example of ODS and BASEstar Open configuration working with the
>    DAS for RSLinx.
>
>       When i type the following line:
>
>reg dir name "/cn=DTL_KA1" attr "/oc=DTL/portid=1KA:2
>/netaddress=xxx.xxx.xxx.xxx/stationid=001/rsptimeout=10/niid=1"
>
>       the following error occurs:
>       "Object class DTL unrecognized"
>
>       Should i define some schema previously ?

This schema is defined by BASEstar Open Server V.3.1 for Windows NT 
Installation

 SOFTWARE REQUIREMENTS for Windows NT Systems:
 o  BASEstar Open Server Development or Run-time for Windows NT Version 3.1
 o  DIGITAL DAS for RSLinx for Windows NT Version 3.1
 o  RSLinx OEM for Allen-Bradley programmable controllers 
    (Rockwell Software Inc.)

>       What is defined by the attribute netaddress ?
This is a pointer to a null-terminated character string that represents
the network's host name. When the network interface is KT, netaddress must
be either a null pointer or a zero-length character string. When the network
interface is Ethernet, netaddress may be either an Ethernet host name
(from the host name database) or an IP address in dot notation.
Both the host name and IP address are character strings.
The Digital DAS for ALlen-Bradley RSLinx supports the following Allen-
Bradley PLCs:
 o  PLC5
 o  PLC2
 o  PLC3
 o  PLC5/250
 o  MicroLogix 1000
 o  SLC 500 processor families

The DAS RSLinx allows you to connect to Allen-Bradley Programmable Con-
trollers via:
 o  Ethernet TCP/IP (PLC-5/80E, PLC-5/40E, PLC-5/20E and the 5820-EI)
 o  Serial DF1
 o  DH+ and DH-485 with 1784-KT, 1784_KTX(D) and 1784-PCMK boards

>       How does the B* know that it has to communicate with DAS RSLinx,
>       instead of another DAS ?
The DAS installation performs some registration (application profile, DAS dll,
...) and with the B* and ODS configurations the B* ddm server knows how to
communicate with a Device.

ODS configuration:
------------------

reg dir name "/cn=DTL_EI1" attr "/oc=DTL/netaddress=xxx.xxx.xxx.xxx
/rsptimeout=10/niid=1"                  (Ethernet connection)
reg dir name "/cn=DTL_KT1" attr "/oc=DTL/portid=1KT:0
/stationid=001/rsptimeout=10/niid=0"    (KT connection)

oc              Object Class DTL
netaddress      This is a pointer to a null-terminated character string
                that represents the network's host name or IP address.
portid          name of the DH/DH+ port
stationid       DH/DH+ station number
niid            Network Interface Identifier
...

BASEstar Open Configuration:
----------------------------

create protocol_profile AB5_40_PPF \
-maxpdusize 521 -APPLPROFID 81

The protocol profile for DAS RSLinx is 81

create vmd DTL_EI1 \
-model "PLC_5_40" -vendor "AB" \
-client_acc ("":BSTR_MMS) \
-dvm_acc "/CN=DTL_EI1":AB5_40_PPF



Best Regards,
Alberto.