About CodeShepherd

CodeShepherd · ‎03-25-2021

You are using a PUT command but as I mentioned in my instructions above you have to do a POST. And please beware that you will always have to send an actual valid bearer token in the authorization header.

CodeShepherd · ‎03-25-2021

The port is only needed if your ctrlX COREvirtual is running in port forwarding mode because, like the name already says, the communication is routed via these ports. Then your IP should look like on my picture above: 127.0.0.1:8740. Please add this by hand. The drop down menu just shows the already insert values. When the ctrlX COREvirtual is running in network adapter mode the needed IP is just the IP of the control (e.g. 192.168.1.1) without the port because an windows network adapter is used.

CodeShepherd · ‎03-24-2021

You simply do not need it in the axis profile. This interface is only needed to connect the real axes to the virtual motion object. But your parameters will be available in the ctrlX Data Layer, and so in other apps like the PLC, independent of the this connection.

CodeShepherd · ‎03-23-2021

I can reproduce the behavior here but will need some time to investigate. I will respond here as soon as possible.

CodeShepherd · ‎03-23-2021

The path you try to command to must be the command itself and also the payload has to look different. Path: POST https://localhost:8443/automation/api/v1.0/motion/axs/AxisX/cmd/power Payload: {"value":true,"type":"bool8"} There is an how to use the REST API in the blog area. Please have a look there for further hints. Also the documentation of the ctrlX Data Layer will be improved with the new release RM21.03 ( version 1.8).

About CodeShepherd

Re: use REST API to set axis command (i.e.:power on axis )

Re: Error While logging in with PLC Engineering while VPN is active

Re: Mapping additional values (torque, speed) in Motion Axis Profile

Re: Robot blending error using PlcOpen Library function block

Re: use REST API to set axis command (i.e.:power on axis )