About alink

Thanks for feedback. I don't like to use a furhter app. But I found the status-word P-0-0115 Bit 13 Drive-Error: 0 = no error 1 = error This is set as soon as there is an issue with engine/drive/feedback -- while PLC / AxisInterface doesn't know anything of that. ... View more

I'm terrible sorry, my mistake, forgot to the call of FB. Now, with call: Execute is FALSE. FB is called line 60 => STOP   ... View more

Interesting, with a manual Excecute: POU is called but ECATRead kept in Execute :=FALSE, but ValueAdr has a value. It is toggeling between 16#7F1C77EF00 (what ever this is) and 16#0 If Execute := TRUE the same: ValueAdr is toggles between 16#7F1C77EF00 and 16#0 But now, even with a new name of FB it doesn't work: And with this kind of coding: It doesn't work as well   But for P-0-0190 there should be this value: I am confused: With my old coding there is an error stop, unexpected and without any reason. If it this is happened, than the name of FB can't be used a second time. The name is more or less 'damaged'. If doing a complete download, a clear all, a restart of ctrlX, a shut off and on, nothing helps. With this name the FB is dead. A new name has to be given till a next, unexpected stop. Then the same procedure.   With another style of coding ther is no stop but the FB is not working, No Done, Error or value or anything. If going step by step, FB is getting parameters correctly. Don't know what to do now. With another writing of code there is no stop but FB doesn't give any result, value.     ... View more

With some other coding and another IDN (S-0-0384) the FB does nothing anymore, it is standing or what ever: The FB is renamed from fbEIL_CATRead to fbAIL_ECATRead. No Done, no Error. Execute stays TRUE, no readings, nothing. But no error at the moment. Now the same S-Parameter as in next ECATReading. And with P-0-0190 the same, FB is not working, while the others are OK   It's really strange... ... View more

Now, did another test: Because a WebVisu-page before there is a ECat reading where to read out drive messages. This side was closed and another without any ECat reading was open. In PLC engineering, with test var, my "diagnose" page was triggered. --bang-- error stop! So there is no competitive action with this FB. If this FB is comment out than it works. Even if all ECat readings FB are running simultaneously, means 4 in two POUs. The only difference between the one which is not working/has issues to the others: The 'problem FB' should read out a P-parameter of drive while all others read a S-Parameter, nothing else. ... View more