View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0005786Compliance Test Tool (CTT) Unified Architecture1 - Script Issuepublic2020-07-07 15:222021-07-09 15:43
ReporterJochen Baier Assigned ToSebastian Allmendinger  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
Product Version1.04.09.396 
Fixed in Version1.03.341.399 
Summary0005786: Base Information->Base Info Server Capabilities->006.js conflicts with View Services->View TranslateBrowePath->Err-014.js
Description

I cannot get both of these test green at the same time:

  • Base Information->Base Info Server Capabilities->006.js and
  • View Services->View TranslateBrowePath->Err-014.js:

Depending of the value for address space node Server_ServerCapabilities_MaxStringLength (value set in SDK startup settings)

  • Server_ServerCapabilities_MaxStringLength = 16646145 (default and suggested value):

    • Base Information->Base Info Server Capabilities->006.js: red with BadOutOfRange because the configured S7-String allows only 254 chars but 10000 is used.
    • View Services->View TranslateBrowePath->Err-014.js: green

  • Server_ServerCapabilities_MaxStringLength = 254:

    • Base Information->Base Info Server Capabilities->006.js: green
    • View Services->View TranslateBrowePath->Err-014.js: red with BadEncodingLimitsExeeded because a relativePath part has a text length of 600.

I have mapped Settings.ServerTest.NodeIds.Static.AllProfiles.Scalar.String to string on a PLC. In this case the length is limited to 254.
So the test Base Information->Base Info Server Capabilities->006.js will always fail with default SDK settings for MaxStringLength of 16646145 (which i should not change).

How should I handle this conflict?

TagsNo tags attached.
Files Affected

Activities

Jochen Baier

2020-07-08 06:53

reporter   ~0012565

One 'solution' could be to skip the test Base Information->Base Info Server Capabilities->006.js if
the value of address space node 'Identifier.Server_ServerCapabilities_MaxStringLength' is larger then the max string length specified in the CTT settings value
'/Server Test/Capabilities/Max String Length'.

Sebastian Allmendinger

2021-06-16 10:05

developer   ~0014568

Specifications Part 5, Section 6.3.2 defines the required behavior and the intended use of the MaxStringLength property in the ServerCapabilitiesType:

"The MaxStringLength Property indicates the maximum number of bytes in Strings supported by Variables of the Server. Servers may override this setting by adding the MaxStringLength Property defined in OPC 10000-3 to an individual DataVariable. If a Server does not impose a maximum number of bytes or is not able to determine the maximum number of bytes this Property shall not be provided."

So you can add a MaxStringLength property to the DataVariables of the DataType String. The latest version of the CTT (1.03.341.398, 1.04.9.398) first checks whether this property is available on the node before writing a value with the length of the value of the MaxStringLength property in the ServerCapabilities. If the property is available AND its value is smaller than the value of the MaxStringLength node in the ServerCapablities, test case Base Info Server Capabilities / 001 will be skipped instead of throwing an error.

The CTT setting '/Server Test/Capabilities/Max String Length' is only used if the MaxStringLength property is not available in the address space of the server.

Paul Hunkar

2021-07-09 15:43

administrator   ~0014684

review in cmp call, agreed that comments on issue were enough and nothing to fix

Issue History

Date Modified Username Field Change
2020-07-07 15:22 Jochen Baier New Issue
2020-07-08 06:53 Jochen Baier Note Added: 0012565
2020-07-10 15:33 Paul Hunkar Assigned To => Alexander Allmendinger
2020-07-10 15:33 Paul Hunkar Status new => assigned
2021-06-16 10:05 Sebastian Allmendinger Note Added: 0014568
2021-06-16 10:05 Sebastian Allmendinger Assigned To Alexander Allmendinger => Sebastian Allmendinger
2021-06-16 10:05 Sebastian Allmendinger Status assigned => resolved
2021-06-16 10:05 Sebastian Allmendinger Resolution open => no change required
2021-06-16 10:05 Sebastian Allmendinger Fixed in Version => 1.03.341.399
2021-07-09 15:43 Paul Hunkar Status resolved => closed
2021-07-09 15:43 Paul Hunkar Note Added: 0014684