NJ / Netbiter Ethernet Communication

[dbones 1]

Wondering if anyone has set up Ethernet communication from an NJ (I'm using an NJ101-9000) to a Netbiter EC350? Netbiter does not support implicit messaging and therefore do not have an .eds file for their hardware. I started by trying to explicit message using the CIPUCMMSEND function block but had no success. I have since been using a generic .eds file to set up Ethernet communication through the connection settings in Sysmac. I did have success sending one value (UINT) across to the Netbiter this way but I am trying to send 34 pieces of data and I'm having trouble scaling my success. The problem (I believe) is that the generic .eds file is set up for input and output instances. I am only looking for output instances. In order to successfully get the one value to transmit I had to create a dummy input variable to associate to the input instance that is created when adding the target device (adds 1 input and 1 output instance). I then thought I'd create 34 dummy input variables but I then hit the ceiling for number of tag sets. I also attempted to modify the .eds file. Although I managed to eliminate the input from the target setup, it still shows an input and output when you add the target to the connection. I've listed the text in the original .eds file (which I received from Omron tech support). Does anyone know how to modify this so that I only get output instances? Thanks $ EZ-EDS Version 3.9 Generated Electronic Data Sheet [File] DescText = "New Description"; CreateDate = 08-22-2015; CreateTime = 11:01:10; ModDate = 08-22-2015; ModTime = 11:01:18; Revision = 1.0; [Device] VendCode = 0; VendName = "Omron Generic EIP"; ProdType = 0; ProdTypeStr = "Control Station"; ProdCode = 0; MajRev = 0; MinRev = 0; ProdName = "Omron Generic EIP"; [Device Classification] Class1 = EtherNetIP; [Params] Param3 = 0, $ reserved, shall equal 0 ,, $ Link Path Size, Link Path 0x0000, $ Descriptor 0xC7, $ Data Type 2, $ Data Size in bytes "Output Assembly Number", $ name "", $ units "Output Assembly Number", $ help string 0,65535,0, $ min, max, default data values ,,,, $ mult, div, base, offset scaling ,,,, $ mult, div, base, offset links ; $ decimal places Param4 = 0, $ reserved, shall equal 0 ,, $ Link Path Size, Link Path 0x0000, $ Descriptor 0xC7, $ Data Type 2, $ Data Size in bytes "Output Size (Bytes)", $ name "", $ units "Output Size (Bytes)", $ help string 0,65535,0, $ min, max, default data values ,,,, $ mult, div, base, offset scaling ,,,, $ mult, div, base, offset links ; $ decimal places [Connection Manager] Connection1 = 0x04010002, $ 0-15 = supported transport classes $ 16 = trigger: cyclic $ 17 = trigger: change of state $ 18 = trigger: application $ 19-23 = trigger: reserved $ 24 = application type: listen-only $ 25 = application type: input-only $ 26 = application type: exclusive-owner $ 27 = application type: redundant-owner $ 28-30 = reserved $ 31 = Direction: Client = 0 / Server = 1 0x44440405, $ 0 = O->T fixed size supported $ 1 = O->T variable size supported $ 2 = T->O fixed size supported $ 3 = T->O variable size supported $ 4-5 = O->T number of bytes per slot (obsolete) $ 6-7 = T->O number of bytes per slot (obsolete) $ 8-10 = O->T Real time transfer format $ 11 = reserved $ 12-14 = T->O Real time transfer format $ 15 = reserved $ 16 = O->T connection type: NULL $ 17 = O->T connection type: MULTICAST $ 18 = O->T connection type: POINT2POINT $ 19 = O->T connection type: reserved $ 20 = T->O connection type: NULL $ 21 = T->O connection type: MULTICAST $ 22 = T->O connection type: POINT2POINT $ 23 = T->O connection type: reserved $ 24 = O->T priority: LOW $ 25 = O->T priority: HIGH $ 26 = O->T priority: SCHEDULED $ 27 = O->T priority: reserved $ 28 = T->O priority: LOW $ 29 = T->O priority: HIGH $ 30 = T->O priority: SCHEDULED $ 31 = T->O priority: reserved ,Param4,, $ O->T RPI, size, format ,, $ proxy config size, format ,, $ target config size, format "Discrete Exclusive Owner", $ Connection Name "", $ help string "20 04 24 01 2C [Param3]"; $ Path

[Crossbow 295]

If it doesn't support implicit messages, then there is no need of an EDS file and Network Configurator. Explicit messaging you need to use CIPUCMMWRITE and tell it how much data to read and from where. The manuals are pretty clear on how to use CIPUCMMWRITE. CIPUSMMSEND is used to send CIP commands, not really as much for data.