FORUM CTRLX AUTOMATION
ctrlX World Partner Apps for ctrlX AUTOMATION
12-16-2021 06:28 PM
It seems that the read/write feature when using bit access for variables does not work. Here is the configuraiton I am using:
When I do something similiar with a UI action it works but this is not a reasonable solution in my application.
Solved! Go to Solution.
12-17-2021 08:44 AM
Hello
Only with virtual items, there is a bug, that writing of bits is not working. I use it with WebIQ 2.10.0 and it works fine.
Your 2 screenshoots works different.
12-17-2021 09:34 AM
For virtual items bit access is not supported. However, as virtual items only exist in the user's browser anyway there is probably no valid reason to use them with bit access.
Also, the additional computational overhead for bit access (though negligible) it way larger than the impact of using bytes with *virtual* items anyway.
Regards,
Sascha Kimmel
12-17-2021 02:57 PM
I understand they are different, I was trying to demonstrate that bit access was possible but that it failed in the first case.
If I upgrade to the latest this problem is gone?
12-17-2021 03:02 PM
Hello,
no, as this is not a bug. Virtual Items do not support bit access. Unfortunately this is not mentioned in the manual.
Regards,
Sascha Kimmel
12-17-2021 03:04 PM
This is not a virtual item. This is linked to a variable on the OPC-server
12-17-2021 03:06 PM
Which version are you using?
12-17-2021 03:48 PM
2.10.0
12-17-2021 03:51 PM
To find out whether a specific issue has been fixed with later versions of WebIQ you can always check the changelog: https://docs.webiq.de/docs/changelog/
12-17-2021 03:55 PM
The only references to "bit access" in that document are from rev 2.6. Is there a newer fix?
12-17-2021 03:57 PM
The latest release of WebIQ is version 2.10.3 - the changelog always lists all releases available. If a problem is not listed there it has not been fixed.
12-17-2021 03:59 PM
To be clear, this is a problem and it is not addressed. Is that correct?
12-17-2021 04:00 PM
Did you follow the suggestions by StefBaro and it still does not work?
12-17-2021 04:06 PM
from StefBaro:
Only with virtual items, there is a bug, that writing of bits is not working. I use it with WebIQ 2.10.0 and it works fine.
Your 2 screenshoots works different.
This is a description of what I was showing in the initial question, not a recommendation for a course of action. I added that image in the original question to demonstrate the error. I want to use the automatic bit access, not the UI linked action.
12-17-2021 04:08 PM
As I wrote before using bit access with virtual items is not currently supported, but not a bug.
StefBaro wrote "When you want the same behavior, you must use for press and release the value 1. Could this be the problem?"
Did you try this?
12-17-2021 04:11 PM
As I wrote before using bit access with virtual items is not currently supported, but not a bug.
How is virtual tag defined? This is not a virtual tag, it is linked to an OPC tag.
StefBaro wrote "When you want the same behavior, you must use for press and release the value 1. Could this be the problem?"
Did you try this?
How is this done without a UI Action? I don't want to use UI actions to set and clear bits in a control word that is configured in OPC-UA, not a virtual tag.
12-17-2021 04:16 PM - edited 12-17-2021 04:16 PM
A virtual item is an item that it listed in the virtual item list in the Process Data Manager:
StefBaro suggested to enter a 1 in the field where a 0 is written:
12-17-2021 04:22 PM
I understood StefBaro to be saying in the second case that I showed another action is required to clear the bit I set on release IF I want it to work like the built in feature shown in the first image I posted (the one that doesn't work).
I can try what you are recommending but this would mean that it does not work like all of the other places that bits are accessed in the application when not using the "Bit Access."
For example, in my application, this works no problem:
and as I showed in the original picture, this does not.
Are you suggesting that in the specific case where Bit access is required then the "Off-Value" must also be set to a value of 1?
12-17-2021 04:24 PM
That's what StefBaro suggested and I justed wanted to make this clear with the screenshot.
12-17-2021 04:25 PM
I can try it.
12-17-2021 04:34 PM
This also does not work:
01-05-2022 04:27 PM
Hello, are there any other recommendations for making this work?
11-28-2022 06:01 PM
Hi @aFouraker , I understand your pain. I am reviewing WebIQ at the moment and fell in to the same hole. For me, the inconvenience is I cannot/ do not want to write the WORD and BITMASK repeatedly. Not sure if it suits you to do the same, but I utilised your UI-actions approach and did a SET on-press and CLEAR on-release. However I did this within a composite and used placeholders and snippets, so that I only need enter the target data once. I then use my composit widget in lieu of the native button.
12-05-2022 04:29 PM
As promised to @HmiGuide, a more detailed explanation of what we are doing to claim bit access does not work:
I create data within PLC, in this case an MLC. Here it is an INT, but I have tried UINT, WORD, UDINT, etc., etc. I then find and add via browser, and the type is shown. The data is now listed in variable menu, not virtual.
Next I create 2 buttons. the first sets a value only. I do this to show that I have got the use of the button correct, such as
I also provide a data field to see whole of iINT. And when I press the button, it can be seen in the HMI and PLC the value changes. So my whole commuincation method is proven at this point.
I then add a second button which instead uses bit access, and do the same operations.
It can be observed here that iINT neither changes in the HMI or the PLC
So please, by all means, point out the blatantly obvious thing I am doing wrong, but from what I can see, specifically bit access is not working for this button.
12-05-2022 04:56 PM
It's always helpful to open the browser console in the HMI (F12, like in any browser) - this will likely show an error like this which I just encountered while trying to reproduce the issue:
This has now been planned to be fixed with WebIQ 2.13 which is scheduled to be released within the next few weeks.
12-05-2022 05:03 PM
Ah, that is a handy hint, thanks.
And good to hear it is noted.
12-06-2022 09:35 AM
I also did not realize, that in the very first entry of this topic you get the information, that writing via "Write on/off values when pressed/released" is not working. But the workaround, by using "Write Item" is shown, too.