|
Re: Auxiliary variables [message #1862729 is a reply to message #1862728] |
Fri, 22 December 2023 23:32 |
|
With the information you provide this is hard to say. In general the input and output blocks will store at there pins the last state. Examples are the wago modular io or embrick.
|
|
|
|
Re: Auxiliary variables [message #1862750 is a reply to message #1862743] |
Wed, 27 December 2023 15:46 |
|
I'm not sure what you mean with auxiliary variables. If you mean global variables, then the answer is no. IEC 61499 does not have global variables in its language definition. However FB hold the variables on their inputs, outputs and their internal variables.
|
|
|
|
|
|
|
|
Re: Auxiliary variables [message #1862831 is a reply to message #1862827] |
Sat, 30 December 2023 21:53 |
|
For reading a button you would have an IX block. You can connect the output of this block to several of your other block to check the value and perform according control actions. The same is for analog inputs where you would have an IW or ID block, followed by an according conversion.
|
|
|
|
|
|
|
Re: Auxiliary variables [message #1862963 is a reply to message #1862962] |
Mon, 08 January 2024 20:01 |
|
Or maybe even a custom AI block with a word input and REAL input for the upper and the lower range of your sensor which is then converting to the REAL value you need. Because I would expect that the analog input is just delivering the ADC value as 16 bit integer or?
|
|
|
|
|
|
Re: Auxiliary variables [message #1863072 is a reply to message #1863055] |
Sun, 14 January 2024 17:13 |
|
Hi André,
not sure if I can answer this in a forum post without more information. Would it make sense that we setup a vritual meeting to discuss a bit more the requirements of your client?
BR,
Alois
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.06841 seconds