Hello,
again there is a bad issue with entities.
Everything worked well till there was an error stop suddenly.
Issue at fbAIL_ECATRead
It's from IL_ECATSoeRead
There are more used (fbBIL_, fbCIL_, fbDIL_ )and the others have no issue, so the error message of PLC Engineering is NONSENSE!
After renaming to fbEIL_ECATRead everything works -- no issues!
Going back to the name fbAIL_ECATRead error is again!
Such sudden errors are annoying with no sense.
No way to solve such error. No clearing or something helps.
Just a reset of PLC each time!
At the moment it's just a testing and developing system but there is no trust to make a product for customers with such problems.
Hopefully there is solution for this damned problem.
There is no fun to rename functions everyday just to get it working.
ctrlX PLC 1.18.1 is used
It seems to have some analogy to this post:
Variable loosing its status (boschrexroth.com)
And now, even with the other name fbEIL_ECATRead, the same again:
As soon as the Ethercat Read function is executed system stops with error stop.
Sorry, don't see anything wrong. First it works, than, suddenly, it stops.
Maybe one thing: it happends after a log in / online-change and PLCengineering report:
An application is running....
Now, with the name fbFIL_ECAT it is running....
I don't hope to reach fbZIL_ECATRead
Login with download, after going back to the old name there is a error-stop again.
When getting this message then the issue occurs.
Even when doing a clearence and clear all, it's not possible to get it back to work again with original name.
Just with another, new name. And just for this one, with other EatherCat functions is no problem till now.
When doing a download, it doesn't matter if this function is in use or not at the moment. But when it then is used then error-stop.
Yes, with"ja" it is loaded but with error. So if old application is deleted than there shouldn't be an issue with old things....
But what ever, I tried it the way with setting a var with the name.
At the moment, even with an old, corrupted, not working name of the E-Cat-function, it does work now.
Instead of setting MasterName inside of function it is written into string-var outside.
I will take some care if issue comes again.
Thanks a lot till now👍
I don't understand what issue is:
Now, error stop again as soon as execute is set to true - ....bang...stop
Means, when in line 23:
CtrlX PLC looks like this, no further error description
The use of that funciton is:
On a webVisu, there is a "Diagnose"-page. Is this page opened then this program is active. Then the function to read drive paramenter P-0-0190 is started. But with the first call it stops. Suddenly. Currently I was just doing some graphical modifications on visu-pages. Logged in/out several times to see the result. Then, suddenly, no reason, bang - stop -
In ctrlX Core:
Attached is a backup of configuration
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.
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...
- I normally use variables connected to functionblocks, as changes to the value can be made quite fast without recompiling and login. This especially useful while testing phase.
- If a function is used on an input like ADR or SIZEOF also I always use variables. But sometimes constants if the input is a standard type.
- Another aspect is, that many values are needed at several positions in the program and using a variable gives a single point of code changes. That is much faster and fail-safe.
- Using variables also makes you more independent on compiler versions and settings. As it is depending on them how constants are handled.
- At last looking to your code I would suggest to always put your function blocks outside of any if/case/while/for structures, so they will get called in each cycle and not only as long as if statement is true. Only use the in/outputs inside. This will only cost quite less more performance but is also way more fail and process safe. Your "hanging" topic will be solved by this.
In my tests at my machine (version 1.12) I used the read parameter example out of the CXA_EtherCat library and it worked:
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.
I'm terrible sorry, my mistake, forgot to the call of FB.
Now, with call:
Execute is FALSE.
FB is called line 60 => STOP
