AutomationPrimer said:
...All topics also mention that the Add On Profile has to have been tested by the vendor; why would the vendor make eds files available for Ethernet/IP if you have to create a Generic Module?...
I'll focus on the 501 Series here...
What specific EDS file are you trying to use from Numatics for the 501 Series?
Did you download something from from their website or did someone send you something stating that it's specifically for the 501 Series?
On their
EDS download page, I filtered a search for your product...
File Category: EDS
Protocol: EtherNet/IP
Electronic Platform: G3
Valve Series:
501
Search results:
0
I then searched again with the Valve Series filtered out...
File Category: EDS
Protocol: EtherNet/IP
Electronic Platform: G3
Valve Series:
Show All
Search results:
10
At the bottom of the list is the nearest EDS match to the 501, but it's for the 503 Series. So it appears there is no specific EDS file for the 501 Series?
Are you trying to use the 503 Series EDS file for the 501 Series?
AutomationPrimer said:
...it's hard to tell with the Numatics. It looks like INT based but all numbers are in bytes...
Looking at the EDS file for the 503 Series, it indicates...
Code:
[Params]
Param1 =
0, $ first field shall equal 0
,, $ path size,path
0x0000, $ descriptor
0xC7, $ [B]data type : 16-bit Unsigned Integer[/B]
2, $ data size in bytes
"Output Size", $ name
"", $ units
"", $ help string
0, 504, [B]16[/B], $ min, max, [B]default data values[/B]
0, 0, 0, 0, $ mult, dev, base, offset scaling not used
0, 0, 0, 0, $ mult, dev, base, offset link not used
0; $ decimal places not used
Param2 =
0, $ first field shall equal 0
,, $ path size,path
0x0000, $ descriptor
0xC7, $ [B]data type : 16-bit Unsigned Integer[/B]
2, $ data size in bytes
"Input Size", $ name
"", $ units
"", $ help string
0, 504, [B]16[/B], $ min, max, [B]default data values[/B]
0, 0, 0, 0, $ mult, dev, base, offset scaling not used
0, 0, 0, 0, $ mult, dev, base, offset link not used
0; $ decimal places not used
So, the data type appears to be Integer, which would be Comm Format: "Data - INT".
However, note the default of "16". This is set for 16 integers, or 32 bytes of data for both the Input and Output parameters for this device. This "might" be too high for the lesser 501 Series Manifold? Again, this is only if you are using this specific EDS file. Also, the 501 might not be data type integer, but probably is? I don't think it really matters when all you are dealing with is Discrete I/O. Whether you read/write individual bits in the controller in a SINT, INT, or DINT should not matter so much. The data type can be more for efficient data transfer with Discrete I/O, than anything else, by packing them into larger blocks of transferred data.
Over on the Rockwell Knowledgebase I found this...
459291 - Numatics G3 Series EtherNet/IP module generic profile configuration
Access Level: TechConnect
Date Created: 10/11/2011 11:06 AM
Last Updated:
01/14/2015 03:36 PM
So, as of January this year, it also appears as though they've still not gotten around to creating any specific Add-on Profiles for the Numatics G3 Series manifolds, and advise you to use a Generic Module configuration. Whether they ever intend to do so is debatable?
I would not be "too" concerned with the EDS file route, but more with getting the Generic Module configured correctly for your specific valve setup. You could, without the specific info for the 501 Series, be playing around with EDS file settings for a while before getting it to work, if at all. However, have you tried right-clicking the device in RSLinx Classic to see if you can download the EDS file directly from the device? If you want to continue down the EDS file route, then by all means, work away.
If you use the manual linked in the KB technote...
http://www.numatics.com/common/deliverables/fieldbus/TDG3EPTM1-3EN.pdf
...which I'm sure you already have, then you should be able to deduce the correct I/O sizes to enter into the Generic Module's "Connection Parameters".
Page 83, outlines some data sizes for the different Comm Formats, but these are just starting values to enter, depending on which Comm Format is selected...
The Comm Format selects the communication format, or data type for the module, which appears to be integer in this case, or "Data - INT".
If Data - INT is selected, your I/O entries are at the indicated "16-bit" resolution. If you had 4 bytes of Input data, then you set the Input Size: 2 (16-bit).
As I'm sure you are aware, these manifolds provide a "Valve Side" and "Discrete Side". The Discrete Side allows you to add Discrete I/O Modules, and the Valve Side is where your Valve Solenoids go, obviously. So there is a possible I/O count from both sides, depending on the configuration.
If, for instance, you only have 2 x 16 valve banks, on the Valve Side, and no Discrete I/O Modules on the Discrete Side, then your I/O count is only based on the Valve Side, making it a "bit" simpler.
The total allowed on the Valve Side is 32 Valve Outputs, of which your 2 x 16 are using up. So that's 4 bytes of Output data. But also, for each Valve Output, you can have an enabled Status Input Bit, which means there is also 4 bytes of Input data. So, if you only have 2 x 16 Valves on the Valve Side, then this should be your Valve Side I/O Sizes, 4 bytes Input and 4 bytes Output. That translates to 2 integers Input and 2 integers Output, when set to Data - INT.
If you jump from Page 83 to Page 88, you will see an example of the Generic Module's setup. The Assembly Instances, for Input, Output and Configuration are provided here. Configuration Size should be left at "0".
Skip on again to Page 90 and you get an explanation of what I've outlined above regarding the I/O counts and how they are derived. Page 91 then gives you a Worksheet for toting up the I/O sizes. There is, you'll notice, a default Diagnostic Word of data (2 bytes) sent back no matter what the configuration is. This is probably for the Manifold itself? I've haven't read further on that.
So if you look at Example 2 on Page 96, you will see a setup using all 32 Valve Outputs. So the Valve Side I/O count is as per above. Add the 2 bytes for the Diagnostic Word and you get your total of 6 bytes Input and 4 bytes Output. This translates to 3 integers Input and 2 integers Output when set to Data - INT.
This is what I reckon you should enter for the I/O Sizes if you only have the 2 x 16 Valve banks added to the Valve Side of the Manifold, and have Data - INT selected for the Comm Format. If not INT, then try SINT with 6 Input and 4 Output sizes.
If you are struggling with this, give us the exact part number, or assembled part number of the Numatics G3 manifold configuration (as Ken already requested). The many different options can greatly affect the final I/O sizes you will require.
A side note to your last update...
I haven't looked at anything to do with Phoenix for you with regard to EDS files, but for the Generic Module properties, if a Vendor specifies an Output size of "0", then you must set the Comm Format to "
Input Data - xxxx", as there is no Output data. So if you currently have "Data - DINT", then change it to "Input Data - DINT". This will actually disable the Output field.
Regards,
George