IC-KP-B7-V95 replaces IPG-G4-B7-V15

Size: px

Start display at page:

Download "IC-KP-B7-V95 replaces IPG-G4-B7-V15"

Jennifer McDonald
5 years ago
Views:

1 IC-KP-B7-V95 replaces IPG-G4-B7-V15 The IPG-G4-B7-V15, a DeviceNet bus coupler for the Pepperl+Fuchs IDENT I System P, has been discontinued. It is replaced with the IC-KP-B7-V95 controller for the modern IDENTControl. Both systems use the same tags and also read and write the data in the same format. All hardware must be changed to go to the new system. Software modifications will be necessary to maintain functionality. The following points should be considered when making the switch: 1. Hardware changes 2. Read head mounting changes 3. DeviceNet mapping changes 4. Software changes 5. Wiring changes 6. Tag type settings 1. Hardware changes Replace all old IDENT I System P components with IDENTControl components. Both systems will read the same tags so the tags are not listed here. All components, including read heads, bases, cables, and controller must be switched. The new IC-KP-B7-V95 controller will not work with the old read heads. OLD Description NEW IDENT I System P IDENTControl IPG-G4-B7-V15 DeviceNet Controller IC-KP-B7-V95 IPT-FP Read head IPH-FP-V1 IPT1-FP Read head IPH-FP-V1 U-P3-R4-V15 Base Not required U-P4-R4-V15 Base Not required V15-G-YE5M-PVC-V15-G- 5m cable V1-G-5M-PUR ABG-V1-W ABG-Y V15-G-YE10M-PVC-V15-G- 10m cable V1-G-10M-PUR ABG-V1-W ABG-Y V15-G-YE25M-PVC-V15-G- ABG-Y 25m to 20m cable V1-G-20M-PUR ABG-V1-W (Other lengths available)

2 Controller changes IPG-G4-B7-V15 IC-KP-B7-V95 Read head change IPT1-FP (or IPT-FP) with U-Px-R4-V15 IPH-FP-V1 7/28/2011 2

You will need to add a 23 mm spacer to the back of the IPH-FP-V1 to move the read head forward.

3 2. Read head mounting changes The mounting holes are the same for the IPH-FP-V1 and the IPT1-FP (or IPT-FP) with U-Px-R4- V15, but the old head is 23 mm thicker than the new one. You will need to add a 23 mm spacer to the back of the IPH-FP-V1 to move the read head forward. This will give the new installation a read/write range that is similar to the old one. IPH-FP-V1:23 mm thinner than old head (use a spacer) IPT1-FP (or IPT-FP) with U-Px-R4-V15 IPH-FP-V1 7/28/2011 3

3. DeviceNet mapping changes A new DeviceNet EDS file will be required. Please download it from our website (www.pepperlfuchs.us).

4 3. DeviceNet mapping changes A new DeviceNet EDS file will be required. Please download it from our website ( The produced and consumed sizes of the old IPG-G4-B7-V15 were 9 bytes in and 9 bytes out. The new controller has configurable assembly instances so that you can change the produced and consumed sizes to meet your needs. The assembly instances should be modified based on the tag type used because an IPC03 will work perfectly with 8 bytes in/out but a tag type IPC02 requires 5 bytes of data and needs the 12bytes in/out assembly. The assembly instances can be changed on the graphical display using the push buttons or by changing the DeviceNet parameters in RSNetworx. Make sure the controller is power cycled after any changes are made. The size of the mapped data is adjusted based on the assembly instances chosen. Change the assembly instance on the display using the, and ESC keys. Find out what the model number (e.g. IPC02-50P) of the tag you are using is before proceeding. Write it here: TAG TYPE: Assembly Instance Suggestions Here are the suggested assembly instances settings based on the tag type you are using. The tag type can be found by looking at the model number of the tag or transponder being used. The model 7/28/2011 4

5 number IPC03-54 for example would have a tag type IPC03. An IPC02-50W tag would have tag type IPC02 For tag type IPC03: Assembly instances 100d out and 150d in: For tag type IPC02: Assembly instance 101d out and 151d in: 8 bytes in and 8 bytes out (default) 12 bytes in and 12 bytes out EDS File: Assembly Instance Changes on the Controller If you are using the tag model number IPC02 then the assembly instance must be modified on the controller. The setting can be changed on the graphical display of the controller, IC-KP-B7-V95 or by DeviceNet parameter. Change Using Display If you are going to use the graphical display to make the change then the display can be navigated like this: Navigating the menu of the new IC-KP-B7-V95 Change using Parameter The assembly instances can also be changed by going online with the controller, IC-KP-B7-V95, in RSNetworx and changing parameter number 2. Make sure the controller is power cycled after this 7/28/2011 5

6 parameter change is made. Assembly instance changed using DeviceNet parameters 7/28/2011 6

RSNetworx Mapping Changes Once the assembly instance has been changed on the controller the RSNetworx mapping must be updated. Here are the update recommendations based on the tag type used.

7 RSNetworx Mapping Changes Once the assembly instance has been changed on the controller the RSNetworx mapping must be updated. Here are the update recommendations based on the tag type used. Using IPC03 tags Use the default produced and consumed size of 100/150. This will change the data mapping from 9 bytes in/out to 8 bytes in/out. Remove the IPG-G4-B7-V15 from the scan list and insert the IC-KP- B7-V95 such that the first 8 bytes are mapped in the same location. Also, make sure that the mapping for other devices has not changed. Old New Using IPC02 tags When reading IPC02 tags, 5 bytes of data are returned. In order to get all of this information, an assembly instance of 101/151 is required. This assembly instance will create 12 bytes of in and out data. Because you only need 9 bytes, manual mapping may be required. This is how it is done with an Allen-Bradley PLC. If the previous data mapping was DINT aligned you could map all 12 bytes without issue. Mapping all 12 bytes instead of 9 bytes The following screen shots show how the new mapping will look when you manually change the produced and consumed size from 8 bytes in / 8 bytes out to 12 bytes in and 12 bytes out. No manual mapping will be required if all devices are DINT aligned. If the data is SINT or INT aligned or you only want to map 9 bytes please see the next example. 7/28/2011 7

8 1. Remove IPG-G4-B7-V15 2. Add the new controller IC-KP-B7-V95 to list 7/28/2011 8

3. Click on Edit I/O parameters and change the

that the mapping of the new controller is in

9 3. Click on Edit I/O parameters and change the data to be mapped to 12 bytes in and 12 bytes out. Click yes on all of these warning messages After the above procedure is followed verify that the mapping of the new controller is in the same location as the old controller. 7/28/2011 9

Old New 12 bytes mapped with DINT alignment in

10 Old New 12 bytes mapped with DINT alignment in ControlLogix PLC Configuring RSNetworx to only map 9 bytes of data If you want, or need, to map 9 bytes exactly because of the alignment of the data then follow these steps. > 1. Remove IPG-G4-B7-V15 2. Uncheck Automap on Add 7/28/

11 3. Add IC-KP-B7-V95 4. Choose Edit I/O Parameters and change the produced and consumed size to 12 bytes in/out. 7/28/

12 5. Choose advanced mapping, select the DWord or WORD where the data will be mapped, and change the length to 72 bit. 6. Do the same for the output data. 7/28/

4. Software changes Typical Command layout Typical response layout The protocols used to talk to both the IPG-G4-B7-V15 and IC-KP-B7-V95 are almost the same.

Certain differences in the way the execution counter is used, the head number is defined and the response length is mapped need to be considered. Software changes to be aware of include: 1.

13 4. Software changes Typical Command layout Typical response layout The protocols used to talk to both the IPG-G4-B7-V15 and IC-KP-B7-V95 are almost the same. The format of the data on the RFID tag will be the same. Certain differences in the way the execution counter is used, the head number is defined and the response length is mapped need to be considered. Software changes to be aware of include: 1. The head number(<channel> number) designation has changed. a. IPG-G4-B7-V15 head 1 = (000b), head 2 = (010b), all = (100b) b. IC-KP-B7-V95 head 1 = (001b), head 2 = (010b), head3 = (011b), head 4 = (100b), all = (111b) (Note: If you want to replace 4 single head IPG units then use separated mode. In this special case the head 1 number is defined by the memory mapping and will be (000b) instead of (001b). See the section Application Notes for detail) 2. The execution counter (<Reply couter>) has changed. On the IPG-G4-B7-V15 this counter resets on every new command and only counts up when a tag is present. The IC-KP-B7-V95 will count up on every status change including status FFh, 05h.Any status change will count up! The IC-KP-B7-V95 will count up to 255 and then roll over to 1. Also the counter on the IC-KP-B7-V95 will not reset when issuing a new command. 3. WordNum which is the data length to read or write (in 4 byte double words), is returned in the response from the ID system. In the IPG-G4-B7-V15 this returned <WordNum> is always the same as the value sent to the ID system. In the IC-KP-B7-V95 this <WordNum> 7/28/

14 refers to the amount of data read. So when the first status FFh (command Pending) is returned or a status 05h (No tag) is returned the <WordNum> response is always AR (Auto Read) and BR (Buffered Auto Read) commands are not available. Switch to ER (Enhanced Read). Example single read head 1 (IPG-G4-B7-V15): No tag IPG-G4-B7-V15 command: 16#0000_1010 (toggle bit off) IPG-G4-B7-V15 response 1: 16#00FF_1010 (Status FFh (Command pending), WordNum response = 1, Reply counter = 00, head 1, toggle bit off) IPG-G4-B7-V15 response 2: 16#0005_1010 (Status 05h (No tag), WordNum response = 1, Reply counter = 00, head 1, toggle bit off) Tag Present IPG-G4-B7-V15 command: 16#0000_1110 (toggle bit on) IPG-G4-B7-V15 response 1: 16#00FF_1110 (Status FFh (Command pending), WordNum response = 1, Reply counter = 00, head 1, toggle bit on) IPG-G4-B7-V15 response 2: 16#0100_1110 (Status 00h (tag present), WordNum response = 1, Reply counter = 01, head 1, toggle bit on) Example single read head 1 (IC-KP-B7-V95): No Tag IC-KP-B7-V95 command: 16#0000_1210 (toggle bit off) IC-KP-B7-V95 response 1: 16#05FF_0210 (Status FFh (Command pending), WordNum response = 0, Reply counter = 05, head 1, toggle bit off) IC-KP-B7-V95 response 2: 16#0605_0210 (Status 05h (No tag), WordNum response = 0, Reply counter = 06, head 1, toggle bit off) Tag Present IC-KP-B7-V95 command: 16#0000_1310 (toggle bit on) IC-KP-B7-V95 response 1: 16#07FF_0310 (Status FFh (Command pending), WordNum response = 0, Reply counter = 07, head 1, toggle bit on) IC-KP-B7-V95 response 2: 16#0800_1310 (Status 00h (tag present), WordNum response = 1, Reply counter = 08, head 1 toggle bit on) All read/write commands will change in this way! Common commands Here is a list of the most commonly used commands. All data has been displayed in a 32bit Hexadecimal format as it would be displayed in an Allen Bradley ControlLogix PLC. These 7/28/

15 examples are for. All commands here assume that both the tag and head are present. Other statuses are possible including 05h (no tag), 06h (no head), or 04h (bad command). A command pending, status FFh, will precede every response given on this page, and is not listed. Changes in the display format depending on the PLC ControlLogix PLC = 16#0000_0102 SLC500 = Key xx = Execution counter count up for each new response aaaa = the start address on the tag, this is the same for old or new T = Toggle bit value Description Old IPG command Old IPG Response New B7 Command New B7 Response Quit head 1, T on 16#0000_ #0000_ #0000_ #xx00_0302 Quit head 1, T off 16#0000_ #0000_ #0000_ #xx00_0202 Quit head 2, T on 16#0000_ #0000_ #0000_ #xx00_0502 Quit head 2, T off 16#0000_ #0000_ #0000_ #xx00_0402 Change tag type 1, T on, IPC02 16#3230_ #0000_ #3230_ #xx00_0304 Change tag type 1, T off, IPC02 16#3230_ #0000_ #3230_ #xx00_0204 Change tag type 2, T on, IPC02 16#3230_ #0000_ #3230_ #xx00_0504 Change tag type 2, T off, IPC02 16#3230_ #0000_ #3230_ #xx00_0404 Change tag type 1, T on, IPC03 16#3330_ #0000_ #3330_ #xx00_0304 Change tag type 1, T off, IPC03 16#3330_ #0000_ #3330_ #xx00_0204 Change tag type 2, T on, IPC03 16#3330_ #0000_ #3330_ #xx00_0504 Change tag type 2, T off, IPC03 16#3330_ #0000_ #3330_ #xx00_0404 SF 1, T on 16#0000_ #0100_ #0000_ #xx00_0301 SF 1, T off 16#0000_ #0100_ #0000_ #xx00_0201 SF 2, T on 16#0000_ #0100_ #0000_ #xx00_0501 SF 2, T off 16#0000_ #0100_ #0000_ #xx00_0401 AF 1, T on 16#0000_ #0100_0108 Use SF or EF Use SF or EF AF 1, T off 16#0000_ #0100_0008 Use SF or EF Use SF or EF AF 2, T on 16#0000_ #0100_0508 Use SF or EF Use SF or EF AF 2, T off 16#0000_ #0100_0408 Use SF or EF Use SF or EF BF 1, T on 16#0000_ #xx00_0109 Use EF Use EF BF 1, T off 16#0000_ #xx00_0009 Use EF Use EF BF 2, T on 16#0000_ #xx00_0509 Use EF Use EF BF 2, T off 16#0000_ #xx00_0409 Use EF Use EF EF 1, T on 16#0000_011D 16#xx00_011D 16#0000_031D 16#xx00_031D EF 1, T off 16#0000_001D 16#xx00_001D 16#0000_021D 16#xx00_021D EF 2, T on 16#0000_051D 16#xx00_051D 16#0000_051D 16#xx00_051D 7/28/

16 Description Old IPG command Old IPG Response New B7 Command New B7 Response EF 2, T off 16#0000_041D 16#xx00_041D 16#0000_041D 16#xx00_041D SR 1, T on, length 1 16#aaaa_ #0100_ #aaaa_ #xx00_1310 SR 1, T off, length 1 16#aaaa_ #0100_ #aaaa_ #xx00_1210 SR 2, T on, length 1 16#aaaa_ #0100_ #aaaa_ #xx00_1510 SR 2, T off, length 1 16#aaaa_ #0100_ #aaaa_ #xx00_1410 AR 1, T on, length 1 16#aaaa_ #0100_1120 Use SR or ER Use SR or ER AR 1, T off, length 1 16#aaaa_ #0100_1020 Use SR or ER Use SR or ER AR 2, T on, length 1 16#aaaa_ #0100_1520 Use SR or ER Use SR or ER AR 2, T off, length 1 16#aaaa_ #0100_1420 Use SR or ER Use SR or ER BR 1, T on, length 1 16#aaaa_ #0100_1130 Use ER Use ER BR 1, T off, length 1 16#aaaa_ #0100_1030 Use ER Use ER BR 2, T on, length 1 16#aaaa_ #0100_1530 Use ER Use ER BR 2, T off, length 1 16#aaaa_ #0100_1430 Use ER Use ER ER 1, T on, length 1 16#aaaa_ #xx00_ #aaaa_ #xx00_1319 ER 1, T off, length 1 16#aaaa_ #xx00_ #aaaa_ #xx00_1219 ER 2, T on, length 1 16#aaaa_ #xx00_ #aaaa_ #xx00_1519 ER 2, T off, length 1 16#aaaa_ #xx00_ #aaaa_ #xx00_1419 SW 1, T on, length 1 16#aaaa_ #0100_ #aaaa_ #xx00_1340 SW 1, T off, length 1 16#aaaa_ #0100_ #aaaa_ #xx00_1240 SW 2, T on, length 1 16#aaaa_ #0100_ #aaaa_ #xx00_1540 SW 2, T off, length 1 16#aaaa_ #0100_ #aaaa_ #xx00_1440 AW 1, T on, length 1 16#aaaa_ #0100_1150 Use SW or EW Use SW or EW AW 1, T off, length 1 16#aaaa_ #0100_1050 Use SW or EW Use SW or EW AW 2, T on, length 1 16#aaaa_ #0100_1550 Use SW or EW Use SW or EW AW 2, T off, length 1 16#aaaa_ #0100_1450 Use SW or EW Use SW or EW BW 1, T on, length 1 16#aaaa_ #0100_1160 Use EW Use EW BW 1, T off, length 1 16#aaaa_ #0100_1060 Use EW Use EW BW 2, T on, length 1 16#aaaa_ #0100_1560 Use EW Use EW BW 2, T off, length 1 16#aaaa_ #0100_1460 Use EW Use EW EW 1, T on, length 1 16#aaaa_111A 16#xx00_111A 16#aaaa_131A 16#xx00_131A EW 1, T off, length 1 16#aaaa_101A 16#xx00_101A 16#aaaa_121A 16#xx00_121A EW 2, T on, length 1 16#aaaa_151A 16#xx00_151A 16#aaaa_151A 16#xx00_151A EW 2, T off, length 1 16#aaaa_141A 16#xx00_141A 16#aaaa_141A 16#xx00_141A 7/28/

Old V15-G-YExM-PVC-V15-G-Y New V1-G-5M-PUR-ABG-V1-W The DeviceNet and power cables IPG-G4-B7-V15: Single micro style DeviceNet connection. Power is pulled directly from the DeviceNet trunk/drop line.

17 5. Wiring Changes Read head cables The read head cables of both systems have the same pin outs but the shield connections are different. The new cables have the shield connected to the coupling nuts on both ends. The old ones cables have the shield connected to pin 5. Old cables cannot be used and must be replaced by new cables. Old V15-G-YExM-PVC-V15-G-Y New V1-G-5M-PUR-ABG-V1-W The DeviceNet and power cables IPG-G4-B7-V15: Single micro style DeviceNet connection. Power is pulled directly from the DeviceNet trunk/drop line. IC-KP-B7-V95: Micro style for power connector. Powers the controller completely and must be connected to a 24 VDC power source using pin 1 brown +24V and pin 3 blue -. The DeviceNet connect is mini style. If the DeviceNet connection is micro on the DeviceNet trunk line, you will need an adapter cable to convert the 5-pin MINI connector on the controller to the Micro style of the DeviceNet network. IPG-G4-B7-V15 wiring 7/28/

18 IC-KP-B7-V75 wiring 7/28/

19 6. Tag type settings The new controller, IC-KP-B7-V95, requires that the tag type is programmed into its EEPROM memory for each read head used. The tag type can easily be found by looking at the RFID tag being used in the installation. For example, if the tag IPC03-50P is used, then the tag type is 03. The tag type is always the first two digits after the IPC. Change the tag type on the display using the, and ESC keys. Application notes: Replacing 4 IPG-G4-B7-V15 single head units with 1 IC-KP-B7-V95 Other assembly instances could be very useful if you want to replace four IPG-G4-B7-V15 units that were connected to a single head to one IC-KP-B7-V15. The reason this is an especially good fir for the new controller is because the old head number designation for head one was (000b). The new controller, when running in separated mode, does not use a head number in the command field and will except any head number designation. The controller, IC-KP-B7-V95, knows which head number to issue a command to by the data mapping. The first head mapped is head one, second head mapped is head two and so on. It is suggested to use assembly instance 105/155 that will map 48 bytes of data in/out. Another alternative would be to use 104/154 if a tag type IPC03 is being used. In this case only 8 bytes would be mapped per head. Even though the controller, IC-KP-B7- V95, does not use the head number in the command, the response will include this information. PLC logic, which evaluates the head number in the response, may have to be changed. (Before mapping the data in RSNetworx make sure the assembly instances have been changed using 7/28/

20 the graphical display or DeviceNet parameter) Old method New method with four heads going to one controller 7/28/

21 Manual mapping of read head data for four heads in RSNetworx Mapping of four IPG-G4-B7-V15 7/28/

22 Steps to map one IC-KP-B7-V95 like four IPG-G4-B7-V15 units using assembly 105/ Remove IPG units from scan list 2. Uncheck Automap on Add 7/28/

3. Add IC-KP-B7-V95 to the scan list and change the produced and consumed sizes to 48 bytes Do an advanced mapping with these parameters (Your program map may have a different DWORD start address).

23 3. Add IC-KP-B7-V95 to the scan list and change the produced and consumed sizes to 48 bytes Do an advanced mapping with these parameters (Your program map may have a different DWORD start address). It will require four maps. After each map is filled out press apply mapping and then highlight and configure the next map. Byte 0 DWORD 0 Length 72 Byte 12 DWORD 3 Length 72 Byte 24 DWORD 6 Length 72 Byte 36 DWORD 9 Length 72 7/28/

24 Map 1 Map 2 7/28/

25 Map 3 Map 4 7/28/

26 Conclusion Pepperl+Fuchs understands that converting from an old systems to a new one can be difficult. We have a technical support staff in house that can assist you with picking components, checking availability and programming. We have a SLC500, MicroLogix 1500, ControlLogix, and CompactLogix PLCs and RSLogix 500, RSLogix 5000 and RSNetworx software to help evaluate and suggest changes to your PLC programs. We may not be able to do the programming changes for you but we can make it easier to transition to the new components. Technical Support line ext:1023 7/28/

FACTORY AUTOMATION MANUAL IC-KP-B6-V15B IC-KP-B6-2V15B IC-KP-B6-SUBD

FACTORY AUTOMATION MANUAL IC-KP-B6-V15B IC-KP-B6-2V15B IC-KP-B6-SUBD Communication in "IRI-B6" and "IVI-B6 mode With regard to the supply of products, the current issue of the following document is applicable: