10-14-2017 05:46 AM
I wanted to play with Channels, and check the Channel bug shown here: https://forums.ni.com/t5/LabVIEW/Messenger-Channel-Wire-ack-read-write-behavior/m-p/3699980/highligh...
Then I realized I see again a strange behaviour which I discovered some time ago. As I remember, I asked about this Channel behaviour in the forum, but somehow i cannot find that post again...
So I just tried to create that example in the above post. I started with that "id ack write" Num control. However, when I simply try to create a "Write ack" node for this U32 control, I get an error. I can only create ACK (Read/write) nodes, if first I create a "normal" Messenger Write node, from this I can create a ACK Read, and finally I can create the ACK Write node.
I accept if this is the expected behaviour (why would someone use ACK without Messenger Write/Read nodes?), but then LabVIEW should tell me some meaningful warning, like "Do not do this, because bla bla bla...". And not this error msg, which does not make any sense to me...
10-27-2017 01:26 AM - edited 10-27-2017 01:33 AM
Hello Blokk
i got the same error, but when i right click on the channel wire message writer function connector wait for ack (F) and then create the channel mesage write with ACK it works.
10-27-2017 01:42 AM
@Duffy2007 wrote:
Hello Blokk
i got the same error, but when i right click on the channel wire message writer function connector wait for ack (F) and then create the channel mesage write with ACK it works.
Exactly. As I mentioned this in my post. Anyway, this is a very corner case, so I do not think it is something to fix now...
10-16-2019 08:13 AM