Client: Problem by writing value to custom server

[freeopcua]

Client: Problem by writing value to custom server

[oroulet]

Write a datavalue instead of a variant. Then you have full control. Isn't
it?

On Wed, Jun 17, 2015, 15:51 Denis Štogl [email protected] wrote:

Hi,

I have problem by writing value in custom server based on UA SDK. I get
following error message: The server not does support writing the
combination of value, status and timestamps
provided.(BadWriteNotSupported). The variable is writeable for sure.

I found a problem and it is in Timestamps, if the booth timestamp
(DataValue structure) are set to 0 than works.

Should the user be enable to set custom Timestamp from client API?

—
Reply to this email directly or view it on GitHub
#7.

[destogl]

Yes you are right... Would be than be better to add one more function to node.py with definition:

def set_value(self, datavalue)

or use directly set_attribute (this is a bit dirty)?

[oroulet]

I did not realize that this was an issue with python-opcua!
method overloading is a but messy in python. a method definition with
my_method(_args, *_kwargs) messes up documentation.
but in this particula case I think we should modify the method(and the doc
string!!) to support giving a datavalue as argument.
Do you send a patch?
just add
elig isinstance(value, DataValue):
xxxxx

On Thu, 18 Jun 2015 at 08:38 Denis Štogl [email protected] wrote:

Yes you are right... Would be than be better to add one more function to
node.py with definition:

def set_value(self, datavalue)

or use directly set_attribute (this is a bit dirty)?

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