Hello Thomas,

unfortunately there is not a lot you can do from a debugging perspective once the CTT crashes. But actually calling a Method with a custom DataType should be working, as this is being used by another vendor doing internal AutoID testing. For me the easiest thing would be to take a look at the server myself and debug the situation. Would you be able to provide me a demo version of the UA Server which I can use to reproduce the issue?
Of course we can continue the discussion also via mail, just send a mail to compliance@opcfoundation.org and we'll get in contact with you.

Regards,
Alexander Allmendinger

Hello Alexander,

my method call seems not to reach the server. When I put a break point at the server's method handler I don't come so far. I guess it's an issue with encoding?!
My custom data type is a 2D point:

Point2D = {X: UInt16, Y: UInt16}

When I manually (UA Expert) create a node on the server, e.g. X=8, Y=15, I receive these data on reading (JSON like):

UaVariant = {
ArrayType: 0,
DataType: 22,
ExtensionObject: {
Encoding: 1,
TypeId: {
NamespaceUri: "",
NodeId: {
IdentifierType: 0,
NamespaceIndex: 3,
Identifier: 5013
},
ServerIndex: 0
},
Binary: {
Size: 4,
Data: 0x08000F00
}
}
}

The node id "ns=3;i=5013" is the target node "Binary" referenced from my data type "Point2D" following the reference "HasEncoding".

Decoding:
Data[0,1] = "0800" -> UInt16: 8
Data[2,3] = "0F00" -> UInt16: 15

Encoding:
var byteStrForX = new UaByteString();
var byteStrForY = new UaByteString();
byteStrForX.setHexData( "0x0800" ); // 8
byteStrForY.setHexData( "0x0F00" ); // 15

var result = new UaByteString();
result.append(byteStrForX);
result.append(byteStrForY);

var extObj = new UaExtensionObject();
extObj.setBinary(result);
extObj.TypeId = new UaExpandedNodeId();
extObj.TypeId.NodeId = new UaNodeId(5013, 5);
extObj.TypeId.NamespaceUri = "";

Everything seems to be fine, isn't it?

Thomas