Mission change by HTTP API
Quote from Adri8 on 07/07/2023, 12:35Hi, is there a way to change between some different missions using the HTTP API and if affirmative, how can I do it?
Thanks
Hi, is there a way to change between some different missions using the HTTP API and if affirmative, how can I do it?
Thanks
Quote from mm_dev on 07/07/2023, 16:17It is possible with some restrictions:
- The current mission must contain a HTTP Server block that you can connect to
- The mission file that should be loaded is located on the system the RTSA is running on
- The current mission will be replaced without any confirmation to the local user
- If anything goes wrong while loading the new mission (or if the new mission does not contain a HTTP Server block) you may be left without remote access (as the old mission with the HTTP Server block may already be unloaded)
- You need to use version 2.2.0.11573 or later of the RTSA-Suite PRO
You need to send a PUT request to the /control endpoint of the HTTP Server block. That request must contain a JSON object with the following properties:
"type": "mission"
"load": true
"file": absolute-path-to-mission-file
E.g. using curl it could look like
curl -X PUT -d '{"type":"mission", "load":true, "file":"d:/http_load_mission_test.rmix"}' http://127.0.0.1:54664/control
It is possible with some restrictions:
- The current mission must contain a HTTP Server block that you can connect to
- The mission file that should be loaded is located on the system the RTSA is running on
- The current mission will be replaced without any confirmation to the local user
- If anything goes wrong while loading the new mission (or if the new mission does not contain a HTTP Server block) you may be left without remote access (as the old mission with the HTTP Server block may already be unloaded)
- You need to use version 2.2.0.11573 or later of the RTSA-Suite PRO
You need to send a PUT request to the /control endpoint of the HTTP Server block. That request must contain a JSON object with the following properties:
"type": "mission"
"load": true
"file": absolute-path-to-mission-file
E.g. using curl it could look like
curl -X PUT -d '{"type":"mission", "load":true, "file":"d:/http_load_mission_test.rmix"}' http://127.0.0.1:54664/control