Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Warnings from the XRegisterData logger will look similar to those shown below:

Code Block
NFO   | jvm 1    | 2023/01/11 18:22:22 | W [c.c.e.a.d.r.p.x.XRegisterData ] [00:22:22]: Failed to set data point Int64 Template-9 of type INT64 - there is no data from the ABB Totalflow device. - X_REGISTER_DATA: [AppSlot#=10, Array#=7, Register#=1, NumberOfRegisters=9, status=Valid Frame]
INFO   | jvm 1    | 2023/01/11 18:22:22 | W [c.c.e.a.d.r.p.x.XRegisterData ] [00:22:22]: Failed to set data point Uint64 Template-3 of type UINT64 - there is no data from the ABB Totalflow device. - X_REGISTER_DATA: [AppSlot#=10, Array#=8, Register#=1, NumberOfRegisters=9, status=Valid Frame]
INFO   | jvm 1    | 2023/01/11 18:22:22 | W [c.c.e.a.d.r.p.x.XRegisterData ] [00:22:22]: Failed to set data point Float64 Template-9 of type DOUBLE - there is no data from the ABB Totalflow device. - X_REGISTER_DATA: [AppSlot#=10, Array#=9, Register#=1, NumberOfRegisters=9, status=Valid Frame]
INFO   | jvm 1    | 2023/01/11 18:22:22 | W [c.c.e.a.d.r.p.x.XRegisterData ] [00:22:22]: Failed to set data point Float Template-0 of type FLOAT - there is no data from the ABB Totalflow device. - X_REGISTER_DATA: [AppSlot#=10, Array#=200, Register#=0, NumberOfRegisters=10, status=Valid Frame]
INFO   | jvm 1    | 2023/01/11 18:22:22 | W [c.c.e.a.d.r.p.x.XRegisterData ] [00:22:22]: Failed to set data point Signed Int16 Template-0 of type INT16 - there is no data from the ABB Totalflow device. - X_REGISTER_DATA: [AppSlot#=10, Array#=201, Register#=0, NumberOfRegisters=10, status=Valid Frame]
INFO   | jvm 1    | 2023/01/11 18:22:22 | W [c.c.e.a.d.r.p.x.XRegisterData ] [00:22:22]: Failed to set data point Unsigned Int16 Template-0 of type INT16 - there is no data from the ABB Totalflow device. - X_REGISTER_DATA: [AppSlot#=10, Array#=202, Register#=0, NumberOfRegisters=10, status=Valid Frame]
INFO   | jvm 1    | 2023/01/11 18:22:22 | W [c.c.e.a.d.r.p.x.XRegisterData ] [00:22:22]: Failed to set data point Signed Int32 Template-0 of type INT32 - there is no data from the ABB Totalflow device. - X_REGISTER_DATA: [AppSlot#=10, Array#=203, Register#=0, NumberOfRegisters=10, status=Valid Frame]
INFO   | jvm 1    | 2023/01/11 18:22:22 | W [c.c.e.a.d.r.p.x.XRegisterData ] [00:22:22]: Failed to set data point Unsigned Int32 Template-0 of type INT32 - there is no data from the ABB Totalflow device. - X_REGISTER_DATA: [AppSlot#=10, Array#=204, Register#=0, NumberOfRegisters=10, status=Valid Frame]
INFO   | jvm 1    | 2023/01/11 18:22:22 | W [c.c.e.a.d.r.p.x.XRegisterData ] [00:22:22]: Failed to set data point Byte Template-0 of type BYTE - there is no data from the ABB Totalflow device. - X_REGISTER_DATA: [AppSlot#=10, Array#=205, Register#=0, NumberOfRegisters=10, status=Valid Frame]
INFO   | jvm 1    | 2023/01/11 18:22:22 | W [c.c.e.a.d.r.p.x.XRegisterData ] [00:22:22]: Failed to set data point String Template-0 of type STRING - there is no data from the ABB Totalflow device. - X_REGISTER_DATA: [AppSlot#=10, Array#=206, Register#=0, NumberOfRegisters=10, status=Valid Frame]
INFO   | jvm 1    | 2023/01/11 18:22:22 | W [c.c.e.a.d.r.p.x.XRegisterData ] [00:22:22]: Failed to set data point Register Template-0 of type Register - there is no data from the ABB Totalflow device. - X_REGISTER_DATA: [AppSlot#=10, Array#=207, Register#=0, NumberOfRegisters=10, status=Valid Frame]

This should help identify points in the Array-Register template that cause this warning. For example if we look at the first entry shown above, we get the following register set:

AppSlot#: 10

Array#: 7

First Register#: 1

NumberOfRegisters: 9

Now, we should find the AppSlot# 10 in the list of the Totalflow applications as shown below:

The application name is ‘Operations’ and its AppEnum# is 18. So now we should look at Array-Register templates and find a template for AppEnum# 18 as shown below:

The template name is ‘Dflt. Operations App’ and if we open it, we can examine Array.Registers 7.1 through 7.9 as shown below:

Note that we don’t really need this information we can disable any individual entry or entire register 7.1 – 7.9 set.

Image Added

The logged warning includes details that will help in identifying the points in the Array-Register template that are cause this warning. 

  • The message is prepended with the Device Name, Hostname and TCP Port
  • The message is appended with the X_REGISTER_DATA showing the AppSlot#, Array#, Register#, NumberOfRegisters and status

For example if we look at the highlighted entry shown above, the warning is coming from the Device Name of ABB-TF G4 and a Hostname of 192.168.168.190 and X_REGISTER_DATA of [AppSlot#=10, Array#=7, Register#=1, NumberOfRegisters=9, status=Valid Frame]

Now, we should find the AppSlot# 10 in the list of the Totalflow applications by navigating to Config > Opcua > Devices and selecting Totalflow Applications from the More dropdown for your device. This will display similarly to below: Image Added

Note that the application name is ‘Operations’ and its AppEnum# is 18.


Next we need to look at the Array-Register templates and find a template for AppEnum# 18 by navigating to Config > Opcua > Devices and selecting Array-Register Templates from the More dropdown for your device.

This will display similarly to below where the AppEnum is the identified as part of the Totalflow Application name.Image Added

If you are not using the template associated with the AppEnum, in our example it is Dflt. Operations App, you can simply disable this template to remove the warning messages.

If you are using only some of the registers within this template, select Edit Array_Register Template Contents. This will display similarly to below and we can disable the array registers identified in the warning message.

In our example of X_REGISTER_DATA: [AppSlot#=10, Array#=7, Register#=1, NumberOfRegisters=9, status=Valid Frame] we would be looking at Array 7 Registers 1 through 9.

Image Added


If you are using the template associated with the AppEnum, then there will be additional work with both the INI file, which you can open by selecting the View INI Files link, and the flow computer configuration. 

Additional details to follow



Excerpt Include
CLD80:FAQ: Ignition Modules
CLD80:FAQ: Ignition Modules
nopaneltrue
Also we can examine respective INI file. The user can get the name of the file used by clicking on the ‘View INI Files Link’ in the ‘Dflt. Operations App’ template row.