External OPC client cannot write to Ignition OPC memory Date tag

General Discussion
#1

I am using an OPCUA client (Unified Automation UaExpert) to try to write to an ignition memory tag of type “DateTime”. When I try to write to the tag via the client it fails with “bad” (0x80000000) I believe).
The value updates in the OPCUA client when I change the tag value in the Ignition designer tag tree.

The nodeID:
“ns=2;s=[s1500]Services/Survey_service/survey_status/lastSurvey/timestamp”

The tag is defined within a data type in ignition as a memory tag with type “Date”.

Any ideas ? I am trying to debug a C# client I am writing which has the exact same behavior.

I can read an write Float and string memory tag values in the same UDT with the external OPC client with no problem.

#2

What version of Ignition are you using?

#3

7.9.13

#4

This is likely a bug in the Exposed Tags functionality in 7.9.

I’ll open a ticket to reproduce and fix this in a future 7.9 release.

Exposed Tags was completely rebuilt for 8.0 and it should already work there.

#5

Are you sure this working in version 8? I am running version 8.1.0 and it looks like I have similar problem. I try to write from a external OPC-client and can’t write to a tag of the DateTime type. This client can write to other tags of a different datatype. The setting for the tags appear the same in Ignition (except of course for the datatype). I also tried to write to this tag using UAExpert as a test and can’t write to the tag from there either. It says: BadNotWritable
I am also unable to write to this tag from the Ignition OPC quick client.

Any suggestions?

#6

Hmm, this isn’t fixed in 8.x, I’ll open a ticket for it now.

I’m not sure why in July 2020 I thought it worked.

#7

Thank you very much for the quick response. Any idea how long the fix would take to become available and how I find out? Will you respond here?

#8

Yeah we can respond here. I think we can fix it and put it into a nightly release this week, but it wouldn’t be available in a real release until 8.1.3 or 8.1.4.

#9

This is fixed and will be available in the next nightly release and ultimately released in 8.1.3.

1 Like
#10

Thank you! That is awesome!