2Presentation Highlights IntroductionSlotServer Product OverviewConfiguring the Driver interfaceConfiguring the ControlLogix interfaceQ&A Session
3Introducing the SlotServer Direct connection from Allen Bradley ControlLogix PLC and another networkStandard 1756 format plugging directly into the Allen Bradley ControlLogix rackRS-485 port for devices/networks using RS-485 protocolsEthernet port for Configuration Utilities & Ethernet devices/networkStandard LonWorks TP/FT-10 interface for LonWorks devices/networkInstalling the SlotServer module is a very simple procedureLonWorks TP/FT-10 interface
4SlotServer Hardware Features Plug the SlotServer directly into the ControlLogix Communications rackScrolling text display with 3 status LED’s provides card status at a glanceA bank of six LED’s provides communications status at a glance, as well as additional diagnostic indicationsEthernet port for advanced troubleshooting purposesService Pin for LonWorks commissioningDiagnostic displaysService PinTrade Port
5SlotServer Hardware Features Hardware Specifications:Backplane Load: 0.6ASlot width: 1Operating Temperature: -40 to 185 Deg. FHumidity: 5-95% (non-condensing)
6SlotServer Software Features Transfer up to 6000 points between ControlLogix and many third party interface.Configure the SlotServer to communicate with many different protocols, including LonWorks, BACnet, Metasys and Modbus.Flexible configuration architecture allows for creative connectivity options.Use the Standard SlotServer profiles for connection without SlotServer
7SlotServer Software Features Control communications in the ControlLogix software using standard generic message blocksExample message block code provided in an ACD file with the SlotServer
8SlotServer Selling Features SlotServer allows connection of a Third Party Network to a ControlLogix system without the use of external gatewaysSlotServer sits in the ControlLogix rack, thereby preserving cabinet “Real Estate”SlotServer provides generic profiles (such as LonWorks Open Interface) or custom profiles (with configuration), allowing for a choice between ease and flexibility.
9SlotServer Data Transfer Data Arrays.Map Third party points into and out of these data arrays and let the Logix driver do the rest.Multiple blocks exist so that the data can be mapped through the limited IO Buffer on the backplane using multiplexing.
10SlotServer Logix Driver The Logix driver is the driver that connects the SlotServer to the ControlLogix CPU via the backplaneThe Logix Driver is configured in Config.csv in the SlotServerStandard FieldServer Configuration principles apply
11SlotServer Logix Driver Logix Connection ConfigurationConfiguration of the Logix Connection is standard as follows://================================================================================//// Client Side ConnectionsConnectionsAdapterControlNet// Client Side NodesNodesNode_Name ,Node_ID ,Protocol ,Timeout ,Retry_Interval ,Recovery_IntervalSlotServer_CPU , ,Logix_SS ,0.5s ,0.1s ,0.5s
12SlotServer Logix Driver Logix Driver MappingLogix Input/Output Buffers are mapped to Data Arrays with the following Map Descriptors:Map_DescriptorsMap_Descriptor_Name ,Scan_Interval ,Function ,Node_Name ,IO_Data_Type ,DA_Name_Start ,DA_Count ,Protocol_Type_IDInput_BP_Image ,0.2s ,WRBC ,SlotServer_CPU ,REAL ,In_ , ,0Output_BP_Image ,0.2s ,RDBC ,SlotServer_CPU ,REAL ,Out_ , ,0Custom value. Expected to be used for indicating third party protocol.Name of First Data ArrayRate at which data is transferred between Data Arrays and Buffers.Number of Buffers and Data Arrays to Auto Create. DA Names are In_2, In_3, etc.
13Connecting the SlotServer Example: Connecting the SlotServer to LonWorks using Lon Open ProfileSample Mapping:The points below show a sample of Lon Points that are mapped into the Data Arrays that get multiplexed in and out of the Backplane buffers.Map_DescriptorsMap_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Lon_Function, Function, Node_Name, SNVT_TypenvoVolt1_ ,Out_ , ,NVUOIMX ,WRBX ,Lon_Srv_1 ,SNVT_voltnvoVolt2_ ,Out_ , ,NVUOIMX ,WRBX ,Lon_Srv_1 ,SNVT_voltnviAmp1_ ,In_ , ,NVUI ,Server ,Lon_Srv_1 ,SNVT_ampnviAmp2_ ,In_ , ,NVUI ,Server ,Lon_Srv_1 ,SNVT_ampData Arrays Assigned to I/O Buffers by Logix driverStandard LonWorks Driver Mapping
14Connecting SlotServer to LonWorks Example: Connecting the SlotServer to LonWorks using Lon Open ProfileProcedure outline:Wire up the LonWorks network to the SlotServerCommission SlotServer into the LonWorks network using a NetWork Manager and the SlotServer service pinBind the points available in the SlotServer to points in the rest of the network
15Commissioning with LonMaker Example: Commissioning with LonMaker:Step 1: Open a project in LonMakerStep 2: Drag device into Visio drawing.
16Commissioning with LonMaker Step 3: Give the device a name & select the “commission device” option
17Commissioning with LonMaker Step 4: For XIF definition, select “Upload From Device”
18Commissioning with LonMaker Step 5: For Device Channel, select “Auto Detect”
19Commissioning with LonMaker Step 6: Leave “Device Properties” as isStep 7: For Device Identification Method, select “Service Pin”
20Commissioning with LonMaker Step 9: Do not “Load Application Image” (Leave unchecked)Step 10: For State, select “Online” and leave the rest as is
21SlotServer LonWorks Open Profile Function Block SlotServer LonWorks Open Profile has 25 input function blocks, and 25 output function blocksThe points in each function block are identical. Outputs differ from inputs only in directionThe SNVT types used are intended to represent the most common SNVT types found in the Building Automation IndustryLonSNVT TypeSNVTQuantitySNVT_amp2SNVT_chlr_sts1SNVT_count_fSNVT_count_inc_fSNVT_flow_fSNVT_freq_hzSNVT_hvac_modeSNVT_hvac_statusSNVT_lev_contSNVT_obj_statusSNVT_occupancySNVT_lev_percent8SNVT_ppmSNVT_pressSNVT_temp_setptSNVT_state4SNVT_switchSNVT_temp_pSNVT_tod_eventSNVT_volt_acSNVT_volt
22Programming ControlLogix Step 1: Add a PLC project in RSLogix
23Programming ControlLogix Step 2: Add the SlotServer to the I/O list as a Generic 1756 Module
24Programming ControlLogix Step 3: Configure the Generic Module for SlotServer settings. Select the rack slot for SlotServer
25Programming ControlLogix Step 4: Add user defined data types for storing LonWorks data
26Programming ControlLogix Step 5: Configure MESSAGE tags to manage the message blocks
27Programming ControlLogix Step 6: Configure the Message block for communication with the SlotServer
28Programming ControlLogix Step 7: Add the Data Tags using the user defined data types
29Programming ControlLogix Step 8: Add SlotServer Data Array names to the DA_Name portion of the Data TagsStep 9: Create Logic to control the execution of the Message blocks
30Programming ControlLogix OR……If this is too much work…..Then do the alternative steps…
31Programming ControlLogix Alternative Steps:Load the example ACD (RSLogix) file supplied with the SlotServerUse all the pre-programmed examples, including message blocks, tags, user defined data types and example logic
32Custom Profile vs. Open Profile SlotServer can ship default with generic open profile or can be shipped as the configurable version.The generic profile eliminates the need for messing with config.csv, thus reducing commissioning time.Creating a custom profile with config.csv allows for more flexibility to suit the specific applicationFieldServer offers custom profiling services if needed.