I think I found out what I was doing wrong: I thought I had only 2 options for type: "metadata" or "browse" ... however "--" also seems to do something. When listing the resources via "nodes/datalayer/nodesrt" one of the entries returned was: "fieldbuses/ethercat/master/instances/ethercatmaster/realtime_data/input" and when trying to read that I only got this when reading "metadata": { "type": "object", "value": { "nodeClass": "Folder", "operations": { "read": false, "write": false, "create": false, "delete": false, "browse": true
},
"description": "", "descriptionUrl": "", "displayFormat": "Auto", "extensions": [], "references": [] }
} Which lead me to the impression I couldn't read (as "read" was false for all rt variables I had a look at) However if I run "browse" I get the following: { "type": "arstring", "value": [ "data", "histogram", "info", "map"
]
} So if I append one of these four to my path, I do get sensible data. I would assume, that "map" tells me which fields are stored where in the byte array returned by "data" and what their names are and how to interpret their value. I think I'll be able to continue from here 🙂 Thanks and sorry for all these questions recently.
... View more
