FORUM CTRLX AUTOMATION
ctrlX World Partner Apps for ctrlX AUTOMATION
- About therusch
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
About therusch
since
04-28-2023
4 weeks ago
therusch
Established Member
15
Posts
2
Likes
0
Solutions
05-10-2024
10:30 AM
Hi, thank you for your answer. There they really are. 👍 Do you have an idea, how I can get these logs with scripting? Maybe redirect them to the standard output or get the device log via web API somehow? Or is the testresults xml-file written in your case? In my case it is not. Not on my computer and not on the PLC (can't even set a linux style path). I try to include the Test Run into a CI/CD pipeline, so I need the results accessible without UI. Thank you so much for your help.
... View more
05-07-2024
03:14 PM
Hello, I am trying to write PLC unit tests with the codesys unittest framework co♻e. The tests run fine and complete, but there neither is a test result output in the message list, nor a result file. ctrlX is not listed as compatible here: https://forge.codesys.com/lib/counit/apireference/API%20Reference/ Did anyone successfully run co♻e unittests on ctrlX, or is there an alternative testing framework? Thank you and best regards
... View more
05-07-2024
10:13 AM
Oookay! 😄 Classic case of blindness. I really did not see that. Double/Triple checked... Thank you very much.
... View more
04-30-2024
04:25 PM
Hallo, Ich versuche gerade den in diesem Post beschriebenen Prozess in powershell zu implementieren: https://developer.community.boschrexroth.com/t5/ctrlX-WORKS/ctrlX-PLC-Engineering-2-4-Login-and-Download-through-REST-API/m-p/92737#M1270 Nach dem erfolgreichen CommunicatioSettingsJob versuche ich aus Powershell den DeviceUserLoginJob zu starten. Dieser schlägt fehl mit der Meldung "Device Login is not successful". Weitere Fehlermeldungen sind in dem ErrorLog zu finden: Overall: 00:00:00.0191109
**** Finished executing _ICustomizedCommand_ IStandardCommand with Guid={9d09e965-6254-46fd-9c21-b27fd2e97b52}: 'Rexroth.Studio.Common.Commands.plugin.OpenProjectCommand' - finished regularly after 3789 ms.
Rexroth.Studio.Common: [ERROR@Rexroth.Studio.Common.HttpService.DoTryPutPost(:0)] TryPut: HttpResponseCode for https://192.168.1.24/identity-manager/api/v1.0/auth/token is StatusCode: 400, ReasonPhrase: 'Bad Request', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
{
Alt-Svc: h3=":443"; ma=2592000
Information: The routes /identity-manager/api/v1 and /identity-manager/api/v1.0 are deprecated! Please the route /identity-manager/api/v2 instead! Be aware: the response schemas are changed!)
Pragma: no-cache
Cache-Control: no-store, no-cache
Date: Tue, 30 Apr 2024 14:05:58 GMT
Server: Caddy
Content-Length: 60
Content-Type: application/json; charset=UTF-8
} Hier sieht es aus als würde im Hintergrund eine api/v1 gerufen. Mein powershell call geht raus an $Response = Invoke-RestMethod -Uri "http://localhost:9002/plc/engineering/api/v2/jobs" -Method Post -Body $postParams Die Post Parameter, habe ich aus der API-Referenz Doku kopiert. Wenn ich mir über die API-Referenz Doku die Jobs hole, dann sehen die beiden völlig identisch aus, nur dass der eine succeeded und der andere nicht: {
"id": "28eb6bf1f5d4087",
"state": "Failed",
"progress": 100,
"jobType": "DeviceUserLoginJob",
"jobParameters": {
"nodeUrl": "/devices/Device",
"userName": "boschrexroth",
"password": "boschrexroth"
},
"jobResultInfo": "Device Login is not successful"
},
{
"id": "ead6f1710b8e218",
"state": "Done",
"progress": 100,
"jobType": "DeviceUserLoginJob",
"jobParameters": {
"nodeUrl": "/devices/Device",
"username": "boschrexroth",
"password": "boschrexroth"
},
"jobResultInfo": "DeviceUserLoginJob is successful."
} Ich verwende ein VirtualControl der Version 2.4 und ein PLC Engineering der Version 2.4. Was übersehe ich hier? Vielen Dank für die Antwort und viele Grüße
... View more
03-20-2024
02:40 PM
1 Like
Thank you. This will surely help.
... View more
OK
OK