Cannot write to the node of custom server about freeopcua HOT 7 CLOSED

Which SDK are you using? C++ or .net?
Can you send me a log which is failing with FreeOpcUa? And the terminal
output?

from freeopcua.

I am not sure which SDK because our project partners have a licence for this SDK, but I think is .NET.

I tried to extract the Writing event in Wireshark data so I hope it will be easier for you to check it. The variable is writeable (UaExpert says that) and in booth cases I am writing value 512 to variable ns=2; s=3001.Mode.

So here are the logs:

Terminal output

Wireshark log FreeeOpcUa client - only write event

Wireshark log UaExpert - write event begins at 0.0 (and I am not sure when it ends because of keepalive stuff)

from freeopcua.

I had a short look at it. looks like the only difference is that we set the
source timestampt while uaexpert does not. I think I remember something
similar with a plc.
I suppose that you write a variant using SetValue. Try to create a
DataValue object and do not set the variant, but do not set the
sourcetimestamp then write it using SetValue.
Let me know if it works
If it does we will remove this timestampt stuff, it seems many servers do
not support it

On 10 January 2015 at 09:42, Denis Štogl [email protected] wrote:

I am not sure which SDK because our project partners have a licence for
this SDK, but I think is .NET.

I tried to extract the Writing event in Wireshark data so I hope it will
be easier for you to check it. The variable is writeable (UaExpert says
that) and in booth cases I am writing value 512 to variable ns=2;
s=3001.Mode.

So here are the logs:

Terminal output http://marvin.kset.org/%7Edenis/Posao/term_output.log

Wireshark log FreeeOpcUa client
http://marvin.kset.org/%7Edenis/Posao/FreeOpcUa_client.pcapng - only
write event

Wireshark log UaExpert
http://marvin.kset.org/%7Edenis/Posao/UaExpert.pcapng - write event
begins at 0.0 (and I am not sure when it ends because of keepalive stuff)

—
Reply to this email directly or view it on GitHub
#108 (comment).

from freeopcua.

SET the variant and do NOT set the timestamp... I mean

On 10 January 2015 at 10:18, Olivier Roulet-Dubonnet <
[email protected]> wrote:

I had a short look at it. looks like the only difference is that we set
the source timestampt while uaexpert does not. I think I remember something
similar with a plc.
I suppose that you write a variant using SetValue. Try to create a
DataValue object and do not set the variant, but do not set the
sourcetimestamp then write it using SetValue.
Let me know if it works
If it does we will remove this timestampt stuff, it seems many servers do
not support it

On 10 January 2015 at 09:42, Denis Štogl [email protected] wrote:

I am not sure which SDK because our project partners have a licence for
this SDK, but I think is .NET.

I tried to extract the Writing event in Wireshark data so I hope it will
be easier for you to check it. The variable is writeable (UaExpert says
that) and in booth cases I am writing value 512 to variable ns=2;
s=3001.Mode.

So here are the logs:

Terminal output http://marvin.kset.org/%7Edenis/Posao/term_output.log

Wireshark log FreeeOpcUa client
http://marvin.kset.org/%7Edenis/Posao/FreeOpcUa_client.pcapng - only
write event

Wireshark log UaExpert
http://marvin.kset.org/%7Edenis/Posao/UaExpert.pcapng - write event
begins at 0.0 (and I am not sure when it ends because of keepalive stuff)

—
Reply to this email directly or view it on GitHub
#108 (comment)
.

from freeopcua.

It works, and I created Pull-request with a quick hack (#109)

from freeopcua.

I am unsure what is the correct solution here. I think I will just remove
the second argument. it wil simplify the api, and if someone really want to
set the source timestamp they can always use DataValue

from freeopcua.

I am not sure how protocol is defined. I would go for a solution which is more according to the standard....

from freeopcua.