About Elleshar

Hi,  in general: everything what you can do via the web-ui, you can also access via a rest api.  So, if you would like to read logbook messages you can do a get query with a rest client to https://<ip of ctrlX CORE>/logbook/api/v2/entries. And with a additional parameter at your query (?unit=<your-snap-name>) you can filter for the unit you like.  I tried this out with the help of the RESTED rest client, which is a add-on for the firefox browser. (There are also similar tools for other browsers as well). And just read out all the messages of the helloworld snap of the SDK.  This is the response I got:    Some additional information: Please remember that you always have to authorize your query with a Bearer Token. Find out more about how to do that and how to use the Rest Api here.  You can set the logbook to persistant for troubleshooting in the logbook settings. But persistent logging should be set only temporarily for troubleshooting and should be deactivated again immediately afterwards, as activating persistent logging causes the logs to be saved on a storage medium shortening the lifetime of the storage medium in case of a permanently high number of log entries!  To store logs persistently over a longer period, you can use 'Remote Logging'.  Additional information about "Remote Logging" to a external server, can be found here.    Best regards,  Nick ... View more

Hello Elleshar, I tested your code and it works like expected. So I can read the input values and can not reproduce your error. I would recommed to look at your fieldbus configuration.  I tested it also with ctrlX CORE V1.14. As EtherCAT Slaves I used a ctrlX IO bus coupler and two DI16 modules.    One side hint:  To print out your uint8_t value in C++ correctly, you can use unsingned() to convert it. result = input->beginAccess(inData, revision); if (STATUS_SUCCEEDED(result)) { std::cout << "first byte of input: " << unsigned(inData[0]) << std::endl; input->endAccess(); }   Best regards,  Nick ... View more

Hello Elleshar,  I checked it with our R&D. This problem gets globally fixed for the ctrlX CORE with the release RM22.03 in end of march.  Therefore you don't have to set your proposed linker setting manually then.  Thank you again for reporting this issue.  Best regards,  Nick ... View more