Siemens (S5) IP266 Positioning control Module

Are there any S5 gurus in here?
I have searched the forum for any info about the IP266 module, but found only one thread

We have some banding machines with a push arm controlled by the IP266 module. We had one go down on us yesterday. We have borrowed one from another machine (not running on this shift) to keep us running.

We need to get a replacement, either a new via our siemens supplier for about £1100, or a repair for around £600.

I am trying to establish whether we need to program the IP266 up, or the PLC writes the parameters (or program???) to the card.

I have never used these modules before, so I am trying to learn fast on my feet. I downloaded the manual from Siemens.

http://cache.automation.siemens.com/dnl_iis/jQ4MTA1AAAA_1107380_HB/IP266_%28e%29_OCR.pdf

But, to be brutally honest, some of it may as well be in German!

I also found the following info about the COM266 software:

http://support.automation.siemens.com/WW/skm/frameset.asp?url=%2FWW%2Fllisapi%2Edll%2F19981730%3Ffunc%3Dll%26objId%3D19981730%26objaction%3Dcsopen%26siteid%3Dcseus%26skm%3D1%26lang%3Den&Query=ip266&SearchArea=alle&id=19981730&F11Marker=true&siteid=cseus&query2=&modelled=&lang=en

We do not have this software, and never have. I have checked our old siemens PG and this did not have the software either

I have (as an example)worked out that data is transfered through input blocks (IB) from IP266 to PLC. For example fault codes come into the software on the S5 module via IB83 (as module is in slot 2) as a hex code.

We have virtually no comments in the S5 program file either.

I have found FB14 in the listing that looks to write something to the IP266 module:

FB 14 C:BND550ST.S5D LEN=19
Page 1
Segment 1
Name :EEPROM

:L KF +26
:T QB 80
:
:L KF +0
:T QB 82
:
:BE

Click to expand...

But I am not sure what the KF +26 means.

Also I would have expected the EEPROM FB to be called in OB1

OB 1 C:BND550ST.S5D LEN=43
Page 1
Segment 1
:STL
:C DB 18
:JU FB 242
Name :MUL:16
Z1 : IW 84
Z2 : DW 8
Z3=0 : F 100.7
Z32 : FW 26
Z31 : FW 28
:JU FB 243
Name IV:16
Z1 : IW 86
Z2 : DW 7
OV : F 100.7
FEH : F 100.7
Z3=0 : F 100.7
Z4=0 : F 100.7
Z3 : FW 46
Z4 : FW 48
:L FW 28
:L FW 46
:+F
:T FW 86
:
:***
Segment 2
:AN I 82.0
:S F 13.2
:JC FB 3
Name :BA99SYN
:
:
:
:
:
:JU PB 1
:JU PB 2
:JU PB 4
:BE
OB 21 C:BND550ST.S5D LEN=9
Page 1
Segment 1
:JC FB 2
Name :VERZOEGE
:
:BE
OB 22 C:BND550ST.S5D LEN=9
Page 1
Segment 1
:JC FB 2
Name :VERZOEGE
:
:BE
OB 34 C:BND550ST.S5D LEN=8
Page 1
Segment 1
!
!F 0.7 F 0.7
+---]/[---+---------+---------+---------+---------+---------+---------+--(S )-!
!
!
! :BE

Click to expand...

I am struggling to establish if we need to buy the COM266 software, plus if we can upload from the operating IP266 units.

I have attached a pdf printout of the program. Sorry I could not get it to format to the pages correctly!

Heres hoping sombody can advise me here.

Is there nobody here with knowledge of these S5 modules ?

L KF+26
T QB 80
The above sends the decimal value 26 to the output byte 80.

FB 14 is called from PB 4 segment 50
It is only called for one program scan via F 81.5 going "high"

From your pdf print I can see that the IP266 card is plugged into slot 2 of the rack; hence QB80 (it used Qb80 to QB87).

Have a look in the IP266 manual section 7.2 to 7.4.

Thanks for that, I cannot beleive I did not spot the FB14 call! I did look!

Following the manual then:-

:L KF +26
:T QB 80

Load decimal value of 26 into QB80 (Slot 2 Byte 0 = Mode) = "Mode - RAM EEPROM"

then:

:L KF +0
:T QB 82

Load decimal value of 0 to QB82 (Slot 2 byte 2) = Load Ram into EEPROM

Am I reading this correctly?

Just to add,yes you need the com 266 software to communicate with the IP 266 module. We've encounter this problem also and initially we thought it was an IP266 module problem but it was not. We manage to find a problem on the encoder, we just replaced it and were good. Just to ask upon power reset does the IP 266 module's LED faulted or the fault will occur after initialization of the system? If the fault occurs after initialization you may have a faulty encoder.