\n
This allows scanning each individual logical interface in the vehicle to find connected devices
\nv1.0.1:
\nThis allows scanning each individual logical interface in the vehicle to find connected devices
\nv1.0.1:
\nThis is a docker implementation of a Water Linked DVL A50 and A125 driver as a BlueOS Extension.
\nInstall it from BlueOS extensions tab.
\nThe service will show in the \"Extension Manager\" section in BlueOS, where there are some configuration options.
", + "support": "https://github.com/bluerobotics/BlueOS-Water-Linked-DVL/issues", + "requirements": "core >= 1.1", + "company": { + "about": "", + "name": "Blue Robotics", + "email": "support@bluerobotics.com" + }, + "permissions": { + "ExposedPorts": { + "9001/tcp": {} + }, + "HostConfig": { + "Binds": [ + "/root/.config:/root/.config" + ], + "ExtraHosts": [ + "host.docker.internal:host-gateway" + ], + "PortBindings": { + "9001/tcp": [ + { + "HostPort": "" + } + ] + } + } + } + }, "v1.0.6": { "identifier": "5b72c3c7-cc68-5c2c-9edd-b400daa9070d", "type": "device-integration", @@ -7654,7 +7730,7 @@ } }, "repo_info": { - "downloads": 231853, + "downloads": 231868, "last_updated": "2024-08-29T16:42:47.961975Z", "date_registered": "2022-06-01T23:43:43.19026Z" } @@ -7776,7 +7852,7 @@ } }, "repo_info": { - "downloads": 2112, + "downloads": 2115, "last_updated": "2024-04-23T11:44:14.777434Z", "date_registered": "2023-09-20T20:30:01.66808Z" } @@ -8432,7 +8508,7 @@ } }, "repo_info": { - "downloads": 18072, + "downloads": 18094, "last_updated": "2023-09-06T01:24:53.238154Z", "date_registered": "2023-07-06T13:38:30.979513Z" } @@ -8496,7 +8572,7 @@ } }, "repo_info": { - "downloads": 865, + "downloads": 866, "last_updated": "2023-11-07T01:34:15.374584Z", "date_registered": "2023-11-05T01:19:48.269227Z" } @@ -8569,7 +8645,7 @@ } }, "repo_info": { - "downloads": 1547, + "downloads": 1548, "last_updated": "2023-09-01T21:07:26.318216Z", "date_registered": "2023-09-01T20:11:40.559943Z" } @@ -8641,7 +8717,7 @@ "extra_links": {}, "tag": "v1.2.0", "docs": null, - "readme": "
\n
An intuitive and customizable cross-platform ground control station for remote vehicles of all types. Click here for a demo!
\n\n
See our documentation \ud83d\udcd6
\nCockpit is typically installed as an Electron application or BlueOS Extension, but for development purposes it is valuable to run it locally.
\nTo start, clone the repository and its submodules. The submodules are required components for Cockpit to be able to run:
\ngit clone --recurse-submodules git@github.com:bluerobotics/cockpit.git
Next, install bun. Following their documented instructions is strongly recommended - we have received reports that installing bun from alternatives like Snap did not work properly.
With bun installed, you can enter the repository folder and follow the steps below:
bun install
and then run the server locally with:
\nbun run dev --host
Then you should see a prompt with the local IP and port that can be accessed through a browser, such as localhost:5173.
Cockpit is currently a frontend-only application. That means it relies on data offered by other backend solutions, which are not built-in.
\nIf you have a BlueOS instance running, there's no need to install any backend, as BlueOS already provides everything.
\nIf that's not your case and you want to install the necessary backends, follow the instructions below:
\nmavlink2rest, pointing it to the endpoint provided by the MAVLink router. Remember to serve the API over the 6040 port by running it with --server 0.0.0.0:6040.Follow the instructions provided here to connect Cockpit to your vehicle.
\nIf you're running a BlueOS instance, just put the IP address of it in \"Global vehicle address\" and click the \"apply\" button.
\nIf you're serving mavlink2rest in the same machine as Cockpit, activate the checkmark for \"Mavlink2Rest connection\" and use ws://127.0.0.1:6040/v1/ws/mavlink there (if you're running a mavlink2rest version before 0.11.15, omit the /v1 in the URL).
If you're serving mavlink-camera-manager in the same machine as Cockpit, activate the checkmark for \"WebRTC connection\" and use ws://127.0.0.1:6020 there.
Cockpit provides a simulation environments in a docker compose file. There is an environment provided for ArduSub, ArduCopter, ArduRover and ArduPlane. The compose file uses docker compose profiles to allow you to choose which vehicle you want to simulate. The available profiles are ardusub, arducopter, ardurover and arduplane. You can run a simulation environment by running the following command:
docker-compose -f sim.yml --profile ardusub up
Assuming you have run the bun run dev --host command, you can access the simulation environment by opening the browser and accessing localhost:5173.
\n
An intuitive and customizable cross-platform ground control station for remote vehicles of all types. Click here for a demo!
\n\n
See our documentation \ud83d\udcd6
\nCockpit is typically installed as an Electron application or BlueOS Extension, but for development purposes it is valuable to run it locally.
\nTo start, clone the repository and its submodules. The submodules are required components for Cockpit to be able to run:
\ngit clone --recurse-submodules git@github.com:bluerobotics/cockpit.git
Next, install bun. Following their documented instructions is strongly recommended - we have received reports that installing bun from alternatives like Snap did not work properly.
With bun installed, you can enter the repository folder and follow the steps below:
bun install
and then run the server locally with:
\nbun run dev --host
Then you should see a prompt with the local IP and port that can be accessed through a browser, such as localhost:5173.
Cockpit is currently a frontend-only application. That means it relies on data offered by other backend solutions, which are not built-in.
\nIf you have a BlueOS instance running, there's no need to install any backend, as BlueOS already provides everything.
\nIf that's not your case and you want to install the necessary backends, follow the instructions below:
\nmavlink2rest, pointing it to the endpoint provided by the MAVLink router. Remember to serve the API over the 6040 port by running it with --server 0.0.0.0:6040.Follow the instructions provided here to connect Cockpit to your vehicle.
\nIf you're running a BlueOS instance, just put the IP address of it in \"Global vehicle address\" and click the \"apply\" button.
\nIf you're serving mavlink2rest in the same machine as Cockpit, activate the checkmark for \"Mavlink2Rest connection\" and use ws://127.0.0.1:6040/v1/ws/mavlink there (if you're running a mavlink2rest version before 0.11.15, omit the /v1 in the URL).
If you're serving mavlink-camera-manager in the same machine as Cockpit, activate the checkmark for \"WebRTC connection\" and use ws://127.0.0.1:6020 there.
Cockpit provides a simulation environments in a docker compose file. There is an environment provided for ArduSub, ArduCopter, ArduRover and ArduPlane. The compose file uses docker compose profiles to allow you to choose which vehicle you want to simulate. The available profiles are ardusub, arducopter, ardurover and arduplane. You can run a simulation environment by running the following command:
docker-compose -f sim.yml --profile ardusub up
Assuming you have run the bun run dev --host command, you can access the simulation environment by opening the browser and accessing localhost:5173.
\n
An intuitive and customizable cross-platform ground control station for remote vehicles of all types. Click here for a demo!
\n\n
See our documentation \ud83d\udcd6
\nCockpit is typically installed as an Electron application or BlueOS Extension, but for development purposes it is valuable to run it locally.
\nTo start, clone the repository and its submodules. The submodules are required components for Cockpit to be able to run:
\ngit clone --recurse-submodules git@github.com:bluerobotics/cockpit.git
Next, install bun. Following their documented instructions is strongly recommended - we have received reports that installing bun from alternatives like Snap did not work properly.
With bun installed, you can enter the repository folder and follow the steps below:
bun install
and then run the server locally with:
\nbun run dev --host
Then you should see a prompt with the local IP and port that can be accessed through a browser, such as localhost:5173.
Cockpit is currently a frontend-only application. That means it relies on data offered by other backend solutions, which are not built-in.
\nIf you have a BlueOS instance running, there's no need to install any backend, as BlueOS already provides everything.
\nIf that's not your case and you want to install the necessary backends, follow the instructions below:
\nmavlink2rest, pointing it to the endpoint provided by the MAVLink router. Remember to serve the API over the 6040 port by running it with --server 0.0.0.0:6040.Follow the instructions provided here to connect Cockpit to your vehicle.
\nIf you're running a BlueOS instance, just put the IP address of it in \"Global vehicle address\" and click the \"apply\" button.
\nIf you're serving mavlink2rest in the same machine as Cockpit, activate the checkmark for \"Mavlink2Rest connection\" and use ws://127.0.0.1:6040/v1/ws/mavlink there (if you're running a mavlink2rest version before 0.11.15, omit the /v1 in the URL).
If you're serving mavlink-camera-manager in the same machine as Cockpit, activate the checkmark for \"WebRTC connection\" and use ws://127.0.0.1:6020 there.
Cockpit provides a simulation environments in a docker compose file. There is an environment provided for ArduSub, ArduCopter, ArduRover and ArduPlane. The compose file uses docker compose profiles to allow you to choose which vehicle you want to simulate. The available profiles are ardusub, arducopter, ardurover and arduplane. You can run a simulation environment by running the following command:
docker-compose -f sim.yml --profile ardusub up
Assuming you have run the bun run dev --host command, you can access the simulation environment by opening the browser and accessing localhost:5173.
\n
An intuitive and customizable cross-platform ground control station for remote vehicles of all types. Click here for a demo!
\n\n
See our documentation \ud83d\udcd6
\nCockpit is typically installed as an Electron application or BlueOS Extension, but for development purposes it is valuable to run it locally.
\nTo start, clone the repository and its submodules. The submodules are required components for Cockpit to be able to run:
\ngit clone --recurse-submodules git@github.com:bluerobotics/cockpit.git
Next, install bun. Following their documented instructions is strongly recommended - we have received reports that installing bun from alternatives like Snap did not work properly.
With bun installed, you can enter the repository folder and follow the steps below:
bun install
and then run the server locally with:
\nbun run dev --host
Then you should see a prompt with the local IP and port that can be accessed through a browser, such as localhost:5173.
Cockpit is currently a frontend-only application. That means it relies on data offered by other backend solutions, which are not built-in.
\nIf you have a BlueOS instance running, there's no need to install any backend, as BlueOS already provides everything.
\nIf that's not your case and you want to install the necessary backends, follow the instructions below:
\nmavlink2rest, pointing it to the endpoint provided by the MAVLink router. Remember to serve the API over the 6040 port by running it with --server 0.0.0.0:6040.Follow the instructions provided here to connect Cockpit to your vehicle.
\nIf you're running a BlueOS instance, just put the IP address of it in \"Global vehicle address\" and click the \"apply\" button.
\nIf you're serving mavlink2rest in the same machine as Cockpit, activate the checkmark for \"Mavlink2Rest connection\" and use ws://127.0.0.1:6040/v1/ws/mavlink there (if you're running a mavlink2rest version before 0.11.15, omit the /v1 in the URL).
If you're serving mavlink-camera-manager in the same machine as Cockpit, activate the checkmark for \"WebRTC connection\" and use ws://127.0.0.1:6020 there.
Cockpit provides a simulation environments in a docker compose file. There is an environment provided for ArduSub, ArduCopter, ArduRover and ArduPlane. The compose file uses docker compose profiles to allow you to choose which vehicle you want to simulate. The available profiles are ardusub, arducopter, ardurover and arduplane. You can run a simulation environment by running the following command:
docker-compose -f sim.yml --profile ardusub up
Assuming you have run the bun run dev --host command, you can access the simulation environment by opening the browser and accessing localhost:5173.
\n
An intuitive and customizable cross-platform ground control station for remote vehicles of all types. Click here for a demo!
\n\n
See our documentation \ud83d\udcd6
\nCockpit is typically installed as an Electron application or BlueOS Extension, but for development purposes it is valuable to run it locally.
\nTo start, clone the repository and its submodules. The submodules are required components for Cockpit to be able to run:
\ngit clone --recurse-submodules git@github.com:bluerobotics/cockpit.git
Next, install bun. Following their documented instructions is strongly recommended - we have received reports that installing bun from alternatives like Snap did not work properly.
With bun installed, you can enter the repository folder and follow the steps below:
bun install
and then run the server locally with:
\nbun run dev --host
Then you should see a prompt with the local IP and port that can be accessed through a browser, such as localhost:5173.
Cockpit is currently a frontend-only application. That means it relies on data offered by other backend solutions, which are not built-in.
\nIf you have a BlueOS instance running, there's no need to install any backend, as BlueOS already provides everything.
\nIf that's not your case and you want to install the necessary backends, follow the instructions below:
\nmavlink2rest, pointing it to the endpoint provided by the MAVLink router. Remember to serve the API over the 6040 port by running it with --server 0.0.0.0:6040.Follow the instructions provided here to connect Cockpit to your vehicle.
\nIf you're running a BlueOS instance, just put the IP address of it in \"Global vehicle address\" and click the \"apply\" button.
\nIf you're serving mavlink2rest in the same machine as Cockpit, activate the checkmark for \"Mavlink2Rest connection\" and use ws://127.0.0.1:6040/v1/ws/mavlink there (if you're running a mavlink2rest version before 0.11.15, omit the /v1 in the URL).
If you're serving mavlink-camera-manager in the same machine as Cockpit, activate the checkmark for \"WebRTC connection\" and use ws://127.0.0.1:6020 there.
Cockpit provides a simulation environments in a docker compose file. There is an environment provided for ArduSub, ArduCopter, ArduRover and ArduPlane. The compose file uses docker compose profiles to allow you to choose which vehicle you want to simulate. The available profiles are ardusub, arducopter, ardurover and arduplane. You can run a simulation environment by running the following command:
docker-compose -f sim.yml --profile ardusub up
Assuming you have run the bun run dev --host command, you can access the simulation environment by opening the browser and accessing localhost:5173.
\n
An intuitive and customizable cross-platform ground control station for remote vehicles of all types. Click here for a demo!
\n\n
See our documentation \ud83d\udcd6
\nCockpit is typically installed as an Electron application or BlueOS Extension, but for development purposes it is valuable to run it locally.
\nTo start, clone the repository and its submodules. The submodules are required components for Cockpit to be able to run:
\ngit clone --recurse-submodules git@github.com:bluerobotics/cockpit.git
Next, install bun. Following their documented instructions is strongly recommended - we have received reports that installing bun from alternatives like Snap did not work properly.
With bun installed, you can enter the repository folder and follow the steps below:
bun install
and then run the server locally with:
\nbun run dev --host
Then you should see a prompt with the local IP and port that can be accessed through a browser, such as localhost:5173.
Cockpit is currently a frontend-only application. That means it relies on data offered by other backend solutions, which are not built-in.
\nIf you have a BlueOS instance running, there's no need to install any backend, as BlueOS already provides everything.
\nIf that's not your case and you want to install the necessary backends, follow the instructions below:
\nmavlink2rest, pointing it to the endpoint provided by the MAVLink router. Remember to serve the API over the 6040 port by running it with --server 0.0.0.0:6040.Follow the instructions provided here to connect Cockpit to your vehicle.
\nIf you're running a BlueOS instance, just put the IP address of it in \"Global vehicle address\" and click the \"apply\" button.
\nIf you're serving mavlink2rest in the same machine as Cockpit, activate the checkmark for \"Mavlink2Rest connection\" and use ws://127.0.0.1:6040/v1/ws/mavlink there (if you're running a mavlink2rest version before 0.11.15, omit the /v1 in the URL).
If you're serving mavlink-camera-manager in the same machine as Cockpit, activate the checkmark for \"WebRTC connection\" and use ws://127.0.0.1:6020 there.
Cockpit provides a simulation environments in a docker compose file. There is an environment provided for ArduSub, ArduCopter, ArduRover and ArduPlane. The compose file uses docker compose profiles to allow you to choose which vehicle you want to simulate. The available profiles are ardusub, arducopter, ardurover and arduplane. You can run a simulation environment by running the following command:
docker-compose -f sim.yml --profile ardusub up
Assuming you have run the bun run dev --host command, you can access the simulation environment by opening the browser and accessing localhost:5173.
\n
An intuitive and customizable cross-platform ground control station for remote vehicles of all types. Click here for a demo!
\n\n
See our documentation \ud83d\udcd6
\nCockpit is typically installed as an Electron application or BlueOS Extension, but for development purposes it is valuable to run it locally.
\nTo start, clone the repository and its submodules. The submodules are required components for Cockpit to be able to run:
\ngit clone --recurse-submodules git@github.com:bluerobotics/cockpit.git
Next, install bun. Following their documented instructions is strongly recommended - we have received reports that installing bun from alternatives like Snap did not work properly.
With bun installed, you can enter the repository folder and follow the steps below:
bun install
and then run the server locally with:
\nbun run dev --host
Then you should see a prompt with the local IP and port that can be accessed through a browser, such as localhost:5173.
Cockpit is currently a frontend-only application. That means it relies on data offered by other backend solutions, which are not built-in.
\nIf you have a BlueOS instance running, there's no need to install any backend, as BlueOS already provides everything.
\nIf that's not your case and you want to install the necessary backends, follow the instructions below:
\nmavlink2rest, pointing it to the endpoint provided by the MAVLink router. Remember to serve the API over the 6040 port by running it with --server 0.0.0.0:6040.Follow the instructions provided here to connect Cockpit to your vehicle.
\nIf you're running a BlueOS instance, just put the IP address of it in \"Global vehicle address\" and click the \"apply\" button.
\nIf you're serving mavlink2rest in the same machine as Cockpit, activate the checkmark for \"Mavlink2Rest connection\" and use ws://127.0.0.1:6040/v1/ws/mavlink there (if you're running a mavlink2rest version before 0.11.15, omit the /v1 in the URL).
If you're serving mavlink-camera-manager in the same machine as Cockpit, activate the checkmark for \"WebRTC connection\" and use ws://127.0.0.1:6020 there.
Cockpit provides a simulation environments in a docker compose file. There is an environment provided for ArduSub, ArduCopter, ArduRover and ArduPlane. The compose file uses docker compose profiles to allow you to choose which vehicle you want to simulate. The available profiles are ardusub, arducopter, ardurover and arduplane. You can run a simulation environment by running the following command:
docker-compose -f sim.yml --profile ardusub up
Assuming you have run the bun run dev --host command, you can access the simulation environment by opening the browser and accessing localhost:5173.
\n
An intuitive and customizable cross-platform ground control station for remote vehicles of all types. Click here for a demo!
\n\n
See our documentation \ud83d\udcd6
\nCockpit is typically installed as an Electron application or BlueOS Extension, but for development purposes it is valuable to run it locally.
\nTo start, clone the repository and its submodules. The submodules are required components for Cockpit to be able to run:
\ngit clone --recurse-submodules git@github.com:bluerobotics/cockpit.git
Next, install bun. Following their documented instructions is strongly recommended - we have received reports that installing bun from alternatives like Snap did not work properly.
With bun installed, you can enter the repository folder and follow the steps below:
bun install
and then run the server locally with:
\nbun run dev --host
Then you should see a prompt with the local IP and port that can be accessed through a browser, such as localhost:5173.
Cockpit is currently a frontend-only application. That means it relies on data offered by other backend solutions, which are not built-in.
\nIf you have a BlueOS instance running, there's no need to install any backend, as BlueOS already provides everything.
\nIf that's not your case and you want to install the necessary backends, follow the instructions below:
\nmavlink2rest, pointing it to the endpoint provided by the MAVLink router. Remember to serve the API over the 6040 port by running it with --server 0.0.0.0:6040.Follow the instructions provided here to connect Cockpit to your vehicle.
\nIf you're running a BlueOS instance, just put the IP address of it in \"Global vehicle address\" and click the \"apply\" button.
\nIf you're serving mavlink2rest in the same machine as Cockpit, activate the checkmark for \"Mavlink2Rest connection\" and use ws://127.0.0.1:6040/v1/ws/mavlink there (if you're running a mavlink2rest version before 0.11.15, omit the /v1 in the URL).
If you're serving mavlink-camera-manager in the same machine as Cockpit, activate the checkmark for \"WebRTC connection\" and use ws://127.0.0.1:6020 there.
Cockpit provides a simulation environments in a docker compose file. There is an environment provided for ArduSub, ArduCopter, ArduRover and ArduPlane. The compose file uses docker compose profiles to allow you to choose which vehicle you want to simulate. The available profiles are ardusub, arducopter, ardurover and arduplane. You can run a simulation environment by running the following command:
docker-compose -f sim.yml --profile ardusub up
Assuming you have run the bun run dev --host command, you can access the simulation environment by opening the browser and accessing localhost:5173.
\n
An intuitive and customizable cross-platform ground control station for remote vehicles of all types. Click here for a demo!
\n\n
See our documentation \ud83d\udcd6
\nCockpit is typically installed as an Electron application or BlueOS Extension, but for development purposes it is valuable to run it locally.
\nTo start, clone the repository and its submodules. The submodules are required components for Cockpit to be able to run:
\ngit clone --recurse-submodules git@github.com:bluerobotics/cockpit.git
Next, install bun. Following their documented instructions is strongly recommended - we have received reports that installing bun from alternatives like Snap did not work properly.
With bun installed, you can enter the repository folder and follow the steps below:
bun install
and then run the server locally with:
\nbun run dev --host
Then you should see a prompt with the local IP and port that can be accessed through a browser, such as localhost:5173.
Cockpit is currently a frontend-only application. That means it relies on data offered by other backend solutions, which are not built-in.
\nIf you have a BlueOS instance running, there's no need to install any backend, as BlueOS already provides everything.
\nIf that's not your case and you want to install the necessary backends, follow the instructions below:
\nmavlink2rest, pointing it to the endpoint provided by the MAVLink router. Remember to serve the API over the 6040 port by running it with --server 0.0.0.0:6040.Follow the instructions provided here to connect Cockpit to your vehicle.
\nIf you're running a BlueOS instance, just put the IP address of it in \"Global vehicle address\" and click the \"apply\" button.
\nIf you're serving mavlink2rest in the same machine as Cockpit, activate the checkmark for \"Mavlink2Rest connection\" and use ws://127.0.0.1:6040/v1/ws/mavlink there (if you're running a mavlink2rest version before 0.11.15, omit the /v1 in the URL).
If you're serving mavlink-camera-manager in the same machine as Cockpit, activate the checkmark for \"WebRTC connection\" and use ws://127.0.0.1:6020 there.
Cockpit provides a simulation environments in a docker compose file. There is an environment provided for ArduSub, ArduCopter, ArduRover and ArduPlane. The compose file uses docker compose profiles to allow you to choose which vehicle you want to simulate. The available profiles are ardusub, arducopter, ardurover and arduplane. You can run a simulation environment by running the following command:
docker-compose -f sim.yml --profile ardusub up
Assuming you have run the bun run dev --host command, you can access the simulation environment by opening the browser and accessing localhost:5173.
\n
An intuitive and customizable cross-platform ground control station for remote vehicles of all types. Click here for a demo!
\n\n
See our documentation \ud83d\udcd6
\nCockpit is typically installed as an Electron application or BlueOS Extension, but for development purposes it is valuable to run it locally.
\nTo start, clone the repository and its submodules. The submodules are required components for Cockpit to be able to run:
\ngit clone --recurse-submodules git@github.com:bluerobotics/cockpit.git
Next, install bun. Following their documented instructions is strongly recommended - we have received reports that installing bun from alternatives like Snap did not work properly.
With bun installed, you can enter the repository folder and follow the steps below:
bun install
and then run the server locally with:
\nbun run dev --host
Then you should see a prompt with the local IP and port that can be accessed through a browser, such as localhost:5173.
Cockpit is currently a frontend-only application. That means it relies on data offered by other backend solutions, which are not built-in.
\nIf you have a BlueOS instance running, there's no need to install any backend, as BlueOS already provides everything.
\nIf that's not your case and you want to install the necessary backends, follow the instructions below:
\nmavlink2rest, pointing it to the endpoint provided by the MAVLink router. Remember to serve the API over the 6040 port by running it with --server 0.0.0.0:6040.Follow the instructions provided here to connect Cockpit to your vehicle.
\nIf you're running a BlueOS instance, just put the IP address of it in \"Global vehicle address\" and click the \"apply\" button.
\nIf you're serving mavlink2rest in the same machine as Cockpit, activate the checkmark for \"Mavlink2Rest connection\" and use ws://127.0.0.1:6040/v1/ws/mavlink there (if you're running a mavlink2rest version before 0.11.15, omit the /v1 in the URL).
If you're serving mavlink-camera-manager in the same machine as Cockpit, activate the checkmark for \"WebRTC connection\" and use ws://127.0.0.1:6020 there.
Cockpit provides a simulation environments in a docker compose file. There is an environment provided for ArduSub, ArduCopter, ArduRover and ArduPlane. The compose file uses docker compose profiles to allow you to choose which vehicle you want to simulate. The available profiles are ardusub, arducopter, ardurover and arduplane. You can run a simulation environment by running the following command:
docker-compose -f sim.yml --profile ardusub up
Assuming you have run the bun run dev --host command, you can access the simulation environment by opening the browser and accessing localhost:5173.
\n
An intuitive and customizable cross-platform ground control station for remote vehicles of all types. Click here for a demo!
\n\n
See our documentation \ud83d\udcd6
\nCockpit is typically installed as an Electron application or BlueOS Extension, but for development purposes it is valuable to run it locally.
\nTo start, clone the repository and its submodules. The submodules are required components for Cockpit to be able to run:
\ngit clone --recurse-submodules git@github.com:bluerobotics/cockpit.git
Next, install bun. Following their documented instructions is strongly recommended - we have received reports that installing bun from alternatives like Snap did not work properly.
With bun installed, you can enter the repository folder and follow the steps below:
bun install
and then run the server locally with:
\nbun run dev --host
Then you should see a prompt with the local IP and port that can be accessed through a browser, such as localhost:5173.
Cockpit is currently a frontend-only application. That means it relies on data offered by other backend solutions, which are not built-in.
\nIf you have a BlueOS instance running, there's no need to install any backend, as BlueOS already provides everything.
\nIf that's not your case and you want to install the necessary backends, follow the instructions below:
\nmavlink2rest, pointing it to the endpoint provided by the MAVLink router. Remember to serve the API over the 6040 port by running it with --server 0.0.0.0:6040.Follow the instructions provided here to connect Cockpit to your vehicle.
\nIf you're running a BlueOS instance, just put the IP address of it in \"Global vehicle address\" and click the \"apply\" button.
\nIf you're serving mavlink2rest in the same machine as Cockpit, activate the checkmark for \"Mavlink2Rest connection\" and use ws://127.0.0.1:6040/v1/ws/mavlink there (if you're running a mavlink2rest version before 0.11.15, omit the /v1 in the URL).
If you're serving mavlink-camera-manager in the same machine as Cockpit, activate the checkmark for \"WebRTC connection\" and use ws://127.0.0.1:6020 there.
Cockpit provides a simulation environments in a docker compose file. There is an environment provided for ArduSub, ArduCopter, ArduRover and ArduPlane. The compose file uses docker compose profiles to allow you to choose which vehicle you want to simulate. The available profiles are ardusub, arducopter, ardurover and arduplane. You can run a simulation environment by running the following command:
docker-compose -f sim.yml --profile ardusub up
Assuming you have run the bun run dev --host command, you can access the simulation environment by opening the browser and accessing localhost:5173.
\n
An intuitive and customizable cross-platform ground control station for remote vehicles of all types. Click here for a demo!
\n\n
See our documentation \ud83d\udcd6
\nCockpit is typically installed as an Electron application or BlueOS Extension, but for development purposes it is valuable to run it locally.
\nTo start, clone the repository and its submodules. The submodules are required components for Cockpit to be able to run:
\ngit clone --recurse-submodules git@github.com:bluerobotics/cockpit.git
Next, install bun. Following their documented instructions is strongly recommended - we have received reports that installing bun from alternatives like Snap did not work properly.
With bun installed, you can enter the repository folder and follow the steps below:
bun install
and then run the server locally with:
\nbun run dev --host
Then you should see a prompt with the local IP and port that can be accessed through a browser, such as localhost:5173.
Cockpit is currently a frontend-only application. That means it relies on data offered by other backend solutions, which are not built-in.
\nIf you have a BlueOS instance running, there's no need to install any backend, as BlueOS already provides everything.
\nIf that's not your case and you want to install the necessary backends, follow the instructions below:
\nmavlink2rest, pointing it to the endpoint provided by the MAVLink router. Remember to serve the API over the 6040 port by running it with --server 0.0.0.0:6040.Follow the instructions provided here to connect Cockpit to your vehicle.
\nIf you're running a BlueOS instance, just put the IP address of it in \"Global vehicle address\" and click the \"apply\" button.
\nIf you're serving mavlink2rest in the same machine as Cockpit, activate the checkmark for \"Mavlink2Rest connection\" and use ws://127.0.0.1:6040/v1/ws/mavlink there (if you're running a mavlink2rest version before 0.11.15, omit the /v1 in the URL).
If you're serving mavlink-camera-manager in the same machine as Cockpit, activate the checkmark for \"WebRTC connection\" and use ws://127.0.0.1:6020 there.
Cockpit provides a simulation environments in a docker compose file. There is an environment provided for ArduSub, ArduCopter, ArduRover and ArduPlane. The compose file uses docker compose profiles to allow you to choose which vehicle you want to simulate. The available profiles are ardusub, arducopter, ardurover and arduplane. You can run a simulation environment by running the following command:
docker-compose -f sim.yml --profile ardusub up
Assuming you have run the bun run dev --host command, you can access the simulation environment by opening the browser and accessing localhost:5173.
\n
An intuitive and customizable cross-platform ground control station for remote vehicles of all types. Click here for a demo!
\n\n
See our documentation \ud83d\udcd6
\nCockpit is typically installed as an Electron application or BlueOS Extension, but for development purposes it is valuable to run it locally.
\nTo start, clone the repository and its submodules. The submodules are required components for Cockpit to be able to run:
\ngit clone --recurse-submodules git@github.com:bluerobotics/cockpit.git
Next, install bun. Following their documented instructions is strongly recommended - we have received reports that installing bun from alternatives like Snap did not work properly.
With bun installed, you can enter the repository folder and follow the steps below:
bun install
and then run the server locally with:
\nbun run dev --host
Then you should see a prompt with the local IP and port that can be accessed through a browser, such as localhost:5173.
Cockpit is currently a frontend-only application. That means it relies on data offered by other backend solutions, which are not built-in.
\nIf you have a BlueOS instance running, there's no need to install any backend, as BlueOS already provides everything.
\nIf that's not your case and you want to install the necessary backends, follow the instructions below:
\nmavlink2rest, pointing it to the endpoint provided by the MAVLink router. Remember to serve the API over the 6040 port by running it with --server 0.0.0.0:6040.Follow the instructions provided here to connect Cockpit to your vehicle.
\nIf you're running a BlueOS instance, just put the IP address of it in \"Global vehicle address\" and click the \"apply\" button.
\nIf you're serving mavlink2rest in the same machine as Cockpit, activate the checkmark for \"Mavlink2Rest connection\" and use ws://127.0.0.1:6040/v1/ws/mavlink there (if you're running a mavlink2rest version before 0.11.15, omit the /v1 in the URL).
If you're serving mavlink-camera-manager in the same machine as Cockpit, activate the checkmark for \"WebRTC connection\" and use ws://127.0.0.1:6020 there.
Cockpit provides a simulation environments in a docker compose file. There is an environment provided for ArduSub, ArduCopter, ArduRover and ArduPlane. The compose file uses docker compose profiles to allow you to choose which vehicle you want to simulate. The available profiles are ardusub, arducopter, ardurover and arduplane. You can run a simulation environment by running the following command:
docker-compose -f sim.yml --profile ardusub up
Assuming you have run the bun run dev --host command, you can access the simulation environment by opening the browser and accessing localhost:5173.
\n
An intuitive and customizable cross-platform ground control station for remote vehicles of all types. Click here for a demo!
\n\n
See our documentation \ud83d\udcd6
\nCockpit is typically installed as an Electron application or BlueOS Extension, but for development purposes it is valuable to run it locally.
\nTo start, clone the repository and its submodules. The submodules are required components for Cockpit to be able to run:
\ngit clone --recurse-submodules git@github.com:bluerobotics/cockpit.git
Next, install bun. Following their documented instructions is strongly recommended - we have received reports that installing bun from alternatives like Snap did not work properly.
With bun installed, you can enter the repository folder and follow the steps below:
bun install
and then run the server locally with:
\nbun run dev --host
Then you should see a prompt with the local IP and port that can be accessed through a browser, such as localhost:5173.
Cockpit is currently a frontend-only application. That means it relies on data offered by other backend solutions, which are not built-in.
\nIf you have a BlueOS instance running, there's no need to install any backend, as BlueOS already provides everything.
\nIf that's not your case and you want to install the necessary backends, follow the instructions below:
\nmavlink2rest, pointing it to the endpoint provided by the MAVLink router. Remember to serve the API over the 6040 port by running it with --server 0.0.0.0:6040.Follow the instructions provided here to connect Cockpit to your vehicle.
\nIf you're running a BlueOS instance, just put the IP address of it in \"Global vehicle address\" and click the \"apply\" button.
\nIf you're serving mavlink2rest in the same machine as Cockpit, activate the checkmark for \"Mavlink2Rest connection\" and use ws://127.0.0.1:6040/v1/ws/mavlink there (if you're running a mavlink2rest version before 0.11.15, omit the /v1 in the URL).
If you're serving mavlink-camera-manager in the same machine as Cockpit, activate the checkmark for \"WebRTC connection\" and use ws://127.0.0.1:6020 there.
Cockpit provides a simulation environments in a docker compose file. There is an environment provided for ArduSub, ArduCopter, ArduRover and ArduPlane. The compose file uses docker compose profiles to allow you to choose which vehicle you want to simulate. The available profiles are ardusub, arducopter, ardurover and arduplane. You can run a simulation environment by running the following command:
docker-compose -f sim.yml --profile ardusub up
Assuming you have run the bun run dev --host command, you can access the simulation environment by opening the browser and accessing localhost:5173.
\n
An intuitive and customizable cross-platform ground control station for remote vehicles of all types. Click here for a demo!
\n\n
See our documentation \ud83d\udcd6
\nCockpit is typically installed as an Electron application or BlueOS Extension, but for development purposes it is valuable to run it locally.
\nTo start, clone the repository and its submodules. The submodules are required components for Cockpit to be able to run:
\ngit clone --recurse-submodules git@github.com:bluerobotics/cockpit.git
Next, install bun. Following their documented instructions is strongly recommended - we have received reports that installing bun from alternatives like Snap did not work properly.
With bun installed, you can enter the repository folder and follow the steps below:
bun install
and then run the server locally with:
\nbun run dev --host
Then you should see a prompt with the local IP and port that can be accessed through a browser, such as localhost:5173.
Cockpit is currently a frontend-only application. That means it relies on data offered by other backend solutions, which are not built-in.
\nIf you have a BlueOS instance running, there's no need to install any backend, as BlueOS already provides everything.
\nIf that's not your case and you want to install the necessary backends, follow the instructions below:
\nmavlink2rest, pointing it to the endpoint provided by the MAVLink router. Remember to serve the API over the 6040 port by running it with --server 0.0.0.0:6040.Follow the instructions provided here to connect Cockpit to your vehicle.
\nIf you're running a BlueOS instance, just put the IP address of it in \"Global vehicle address\" and click the \"apply\" button.
\nIf you're serving mavlink2rest in the same machine as Cockpit, activate the checkmark for \"Mavlink2Rest connection\" and use ws://127.0.0.1:6040/v1/ws/mavlink there (if you're running a mavlink2rest version before 0.11.15, omit the /v1 in the URL).
If you're serving mavlink-camera-manager in the same machine as Cockpit, activate the checkmark for \"WebRTC connection\" and use ws://127.0.0.1:6020 there.
Cockpit provides a simulation environments in a docker compose file. There is an environment provided for ArduSub, ArduCopter, ArduRover and ArduPlane. The compose file uses docker compose profiles to allow you to choose which vehicle you want to simulate. The available profiles are ardusub, arducopter, ardurover and arduplane. You can run a simulation environment by running the following command:
docker-compose -f sim.yml --profile ardusub up
Assuming you have run the bun run dev --host command, you can access the simulation environment by opening the browser and accessing localhost:5173.
\n
An intuitive and customizable cross-platform ground control station for remote vehicles of all types. Click here for a demo!
\n\n
See our documentation \ud83d\udcd6
\nCockpit is typically installed as an Electron application or BlueOS Extension, but for development purposes it is valuable to run it locally.
\nTo start, clone the repository and its submodules. The submodules are required components for Cockpit to be able to run:
\ngit clone --recurse-submodules git@github.com:bluerobotics/cockpit.git
Next, install bun. Following their documented instructions is strongly recommended - we have received reports that installing bun from alternatives like Snap did not work properly.
With bun installed, you can enter the repository folder and follow the steps below:
bun install
and then run the server locally with:
\nbun run dev --host
Then you should see a prompt with the local IP and port that can be accessed through a browser, such as localhost:5173.
Cockpit is currently a frontend-only application. That means it relies on data offered by other backend solutions, which are not built-in.
\nIf you have a BlueOS instance running, there's no need to install any backend, as BlueOS already provides everything.
\nIf that's not your case and you want to install the necessary backends, follow the instructions below:
\nmavlink2rest, pointing it to the endpoint provided by the MAVLink router. Remember to serve the API over the 6040 port by running it with --server 0.0.0.0:6040.Follow the instructions provided here to connect Cockpit to your vehicle.
\nIf you're running a BlueOS instance, just put the IP address of it in \"Global vehicle address\" and click the \"apply\" button.
\nIf you're serving mavlink2rest in the same machine as Cockpit, activate the checkmark for \"Mavlink2Rest connection\" and use ws://127.0.0.1:6040/v1/ws/mavlink there (if you're running a mavlink2rest version before 0.11.15, omit the /v1 in the URL).
If you're serving mavlink-camera-manager in the same machine as Cockpit, activate the checkmark for \"WebRTC connection\" and use ws://127.0.0.1:6020 there.
Cockpit provides a simulation environments in a docker compose file. There is an environment provided for ArduSub, ArduCopter, ArduRover and ArduPlane. The compose file uses docker compose profiles to allow you to choose which vehicle you want to simulate. The available profiles are ardusub, arducopter, ardurover and arduplane. You can run a simulation environment by running the following command:
docker-compose -f sim.yml --profile ardusub up
Assuming you have run the bun run dev --host command, you can access the simulation environment by opening the browser and accessing localhost:5173.
\n
An intuitive and customizable cross-platform ground control station for remote vehicles of all types. Click here for a demo!
\n\n
See our documentation \ud83d\udcd6
\nCockpit is typically installed as an Electron application or BlueOS Extension, but for development purposes it is valuable to run it locally.
\nTo start, clone the repository and its submodules. The submodules are required components for Cockpit to be able to run:
\ngit clone --recurse-submodules git@github.com:bluerobotics/cockpit.git
Next, install bun. Following their documented instructions is strongly recommended - we have received reports that installing bun from alternatives like Snap did not work properly.
With bun installed, you can enter the repository folder and follow the steps below:
bun install
and then run the server locally with:
\nbun run dev --host
Then you should see a prompt with the local IP and port that can be accessed through a browser, such as localhost:5173.
Cockpit is currently a frontend-only application. That means it relies on data offered by other backend solutions, which are not built-in.
\nIf you have a BlueOS instance running, there's no need to install any backend, as BlueOS already provides everything.
\nIf that's not your case and you want to install the necessary backends, follow the instructions below:
\nmavlink2rest, pointing it to the endpoint provided by the MAVLink router. Remember to serve the API over the 6040 port by running it with --server 0.0.0.0:6040.Follow the instructions provided here to connect Cockpit to your vehicle.
\nIf you're running a BlueOS instance, just put the IP address of it in \"Global vehicle address\" and click the \"apply\" button.
\nIf you're serving mavlink2rest in the same machine as Cockpit, activate the checkmark for \"Mavlink2Rest connection\" and use ws://127.0.0.1:6040/v1/ws/mavlink there (if you're running a mavlink2rest version before 0.11.15, omit the /v1 in the URL).
If you're serving mavlink-camera-manager in the same machine as Cockpit, activate the checkmark for \"WebRTC connection\" and use ws://127.0.0.1:6020 there.
Cockpit provides a simulation environments in a docker compose file. There is an environment provided for ArduSub, ArduCopter, ArduRover and ArduPlane. The compose file uses docker compose profiles to allow you to choose which vehicle you want to simulate. The available profiles are ardusub, arducopter, ardurover and arduplane. You can run a simulation environment by running the following command:
docker-compose -f sim.yml --profile ardusub up
Assuming you have run the bun run dev --host command, you can access the simulation environment by opening the browser and accessing localhost:5173.
\n
An intuitive and customizable cross-platform ground control station for remote vehicles of all types. Click here for a demo!
\n\n
See our documentation \ud83d\udcd6
\nCockpit is typically installed as an Electron application or BlueOS Extension, but for development purposes it is valuable to run it locally.
\nTo start, clone the repository and its submodules. The submodules are required components for Cockpit to be able to run:
\ngit clone --recurse-submodules git@github.com:bluerobotics/cockpit.git
Next, install bun. Following their documented instructions is strongly recommended - we have received reports that installing bun from alternatives like Snap did not work properly.
With bun installed, you can enter the repository folder and follow the steps below:
bun install
and then run the server locally with:
\nbun run dev --host
Then you should see a prompt with the local IP and port that can be accessed through a browser, such as localhost:5173.
Cockpit is currently a frontend-only application. That means it relies on data offered by other backend solutions, which are not built-in.
\nIf you have a BlueOS instance running, there's no need to install any backend, as BlueOS already provides everything.
\nIf that's not your case and you want to install the necessary backends, follow the instructions below:
\nmavlink2rest, pointing it to the endpoint provided by the MAVLink router. Remember to serve the API over the 6040 port by running it with --server 0.0.0.0:6040.Follow the instructions provided here to connect Cockpit to your vehicle.
\nIf you're running a BlueOS instance, just put the IP address of it in \"Global vehicle address\" and click the \"apply\" button.
\nIf you're serving mavlink2rest in the same machine as Cockpit, activate the checkmark for \"Mavlink2Rest connection\" and use ws://127.0.0.1:6040/v1/ws/mavlink there (if you're running a mavlink2rest version before 0.11.15, omit the /v1 in the URL).
If you're serving mavlink-camera-manager in the same machine as Cockpit, activate the checkmark for \"WebRTC connection\" and use ws://127.0.0.1:6020 there.
Cockpit provides a simulation environments in a docker compose file. There is an environment provided for ArduSub, ArduCopter, ArduRover and ArduPlane. The compose file uses docker compose profiles to allow you to choose which vehicle you want to simulate. The available profiles are ardusub, arducopter, ardurover and arduplane. You can run a simulation environment by running the following command:
docker-compose -f sim.yml --profile ardusub up
Assuming you have run the bun run dev --host command, you can access the simulation environment by opening the browser and accessing localhost:5173.
\n
An intuitive and customizable cross-platform ground control station for remote vehicles of all types. Click here for a demo!
\n\n
See our documentation \ud83d\udcd6
\nCockpit is typically installed as an Electron application or BlueOS Extension, but for development purposes it is valuable to run it locally.
\nTo start, clone the repository and its submodules. The submodules are required components for Cockpit to be able to run:
\ngit clone --recurse-submodules git@github.com:bluerobotics/cockpit.git
Next, install bun. Following their documented instructions is strongly recommended - we have received reports that installing bun from alternatives like Snap did not work properly.
With bun installed, you can enter the repository folder and follow the steps below:
bun install
and then run the server locally with:
\nbun run dev --host
Then you should see a prompt with the local IP and port that can be accessed through a browser, such as localhost:5173.
Cockpit is currently a frontend-only application. That means it relies on data offered by other backend solutions, which are not built-in.
\nIf you have a BlueOS instance running, there's no need to install any backend, as BlueOS already provides everything.
\nIf that's not your case and you want to install the necessary backends, follow the instructions below:
\nmavlink2rest, pointing it to the endpoint provided by the MAVLink router. Remember to serve the API over the 6040 port by running it with --server 0.0.0.0:6040.Follow the instructions provided here to connect Cockpit to your vehicle.
\nIf you're running a BlueOS instance, just put the IP address of it in \"Global vehicle address\" and click the \"apply\" button.
\nIf you're serving mavlink2rest in the same machine as Cockpit, activate the checkmark for \"Mavlink2Rest connection\" and use ws://127.0.0.1:6040/v1/ws/mavlink there (if you're running a mavlink2rest version before 0.11.15, omit the /v1 in the URL).
If you're serving mavlink-camera-manager in the same machine as Cockpit, activate the checkmark for \"WebRTC connection\" and use ws://127.0.0.1:6020 there.
Cockpit provides a simulation environments in a docker compose file. There is an environment provided for ArduSub, ArduCopter, ArduRover and ArduPlane. The compose file uses docker compose profiles to allow you to choose which vehicle you want to simulate. The available profiles are ardusub, arducopter, ardurover and arduplane. You can run a simulation environment by running the following command:
docker-compose -f sim.yml --profile ardusub up
Assuming you have run the bun run dev --host command, you can access the simulation environment by opening the browser and accessing localhost:5173.
\n
An intuitive and customizable cross-platform ground control station for remote vehicles of all types. Click here for a demo!
\n\n
See our documentation \ud83d\udcd6
\nCockpit is typically installed as an Electron application or BlueOS Extension, but for development purposes it is valuable to run it locally.
\nTo start, clone the repository and its submodules. The submodules are required components for Cockpit to be able to run:
\ngit clone --recurse-submodules git@github.com:bluerobotics/cockpit.git
Next, install bun. Following their documented instructions is strongly recommended - we have received reports that installing bun from alternatives like Snap did not work properly.
With bun installed, you can enter the repository folder and follow the steps below:
bun install
and then run the server locally with:
\nbun run dev --host
Then you should see a prompt with the local IP and port that can be accessed through a browser, such as localhost:5173.
Cockpit is currently a frontend-only application. That means it relies on data offered by other backend solutions, which are not built-in.
\nIf you have a BlueOS instance running, there's no need to install any backend, as BlueOS already provides everything.
\nIf that's not your case and you want to install the necessary backends, follow the instructions below:
\nmavlink2rest, pointing it to the endpoint provided by the MAVLink router. Remember to serve the API over the 6040 port by running it with --server 0.0.0.0:6040.Follow the instructions provided here to connect Cockpit to your vehicle.
\nIf you're running a BlueOS instance, just put the IP address of it in \"Global vehicle address\" and click the \"apply\" button.
\nIf you're serving mavlink2rest in the same machine as Cockpit, activate the checkmark for \"Mavlink2Rest connection\" and use ws://127.0.0.1:6040/v1/ws/mavlink there (if you're running a mavlink2rest version before 0.11.15, omit the /v1 in the URL).
If you're serving mavlink-camera-manager in the same machine as Cockpit, activate the checkmark for \"WebRTC connection\" and use ws://127.0.0.1:6020 there.
Cockpit provides a simulation environments in a docker compose file. There is an environment provided for ArduSub, ArduCopter, ArduRover and ArduPlane. The compose file uses docker compose profiles to allow you to choose which vehicle you want to simulate. The available profiles are ardusub, arducopter, ardurover and arduplane. You can run a simulation environment by running the following command:
docker-compose -f sim.yml --profile ardusub up
Assuming you have run the bun run dev --host command, you can access the simulation environment by opening the browser and accessing localhost:5173.
\n
An intuitive and customizable cross-platform ground control station for remote vehicles of all types. Click here for a demo!
\n\n
See our documentation \ud83d\udcd6
\nCockpit is typically installed as an Electron application or BlueOS Extension, but for development purposes it is valuable to run it locally.
\nTo start, clone the repository and its submodules. The submodules are required components for Cockpit to be able to run:
\ngit clone --recurse-submodules git@github.com:bluerobotics/cockpit.git
Next, install bun. Following their documented instructions is strongly recommended - we have received reports that installing bun from alternatives like Snap did not work properly.
With bun installed, you can enter the repository folder and follow the steps below:
bun install
and then run the server locally with:
\nbun run dev --host
Then you should see a prompt with the local IP and port that can be accessed through a browser, such as localhost:5173.
Cockpit is currently a frontend-only application. That means it relies on data offered by other backend solutions, which are not built-in.
\nIf you have a BlueOS instance running, there's no need to install any backend, as BlueOS already provides everything.
\nIf that's not your case and you want to install the necessary backends, follow the instructions below:
\nmavlink2rest, pointing it to the endpoint provided by the MAVLink router. Remember to serve the API over the 6040 port by running it with --server 0.0.0.0:6040.Follow the instructions provided here to connect Cockpit to your vehicle.
\nIf you're running a BlueOS instance, just put the IP address of it in \"Global vehicle address\" and click the \"apply\" button.
\nIf you're serving mavlink2rest in the same machine as Cockpit, activate the checkmark for \"Mavlink2Rest connection\" and use ws://127.0.0.1:6040/v1/ws/mavlink there (if you're running a mavlink2rest version before 0.11.15, omit the /v1 in the URL).
If you're serving mavlink-camera-manager in the same machine as Cockpit, activate the checkmark for \"WebRTC connection\" and use ws://127.0.0.1:6020 there.
Cockpit provides a simulation environments in a docker compose file. There is an environment provided for ArduSub, ArduCopter, ArduRover and ArduPlane. The compose file uses docker compose profiles to allow you to choose which vehicle you want to simulate. The available profiles are ardusub, arducopter, ardurover and arduplane. You can run a simulation environment by running the following command:
docker-compose -f sim.yml --profile ardusub up
Assuming you have run the bun run dev --host command, you can access the simulation environment by opening the browser and accessing localhost:5173.
\n
An intuitive and customizable cross-platform ground control station for remote vehicles of all types. Click here for a demo!
\n\n
See our documentation \ud83d\udcd6
\nCockpit is typically installed as an Electron application or BlueOS Extension, but for development purposes it is valuable to run it locally.
\nTo start, clone the repository and its submodules. The submodules are required components for Cockpit to be able to run:
\ngit clone --recurse-submodules git@github.com:bluerobotics/cockpit.git
Next, install bun. Following their documented instructions is strongly recommended - we have received reports that installing bun from alternatives like Snap did not work properly.
With bun installed, you can enter the repository folder and follow the steps below:
bun install
and then run the server locally with:
\nbun run dev --host
Then you should see a prompt with the local IP and port that can be accessed through a browser, such as localhost:5173.
Cockpit is currently a frontend-only application. That means it relies on data offered by other backend solutions, which are not built-in.
\nIf you have a BlueOS instance running, there's no need to install any backend, as BlueOS already provides everything.
\nIf that's not your case and you want to install the necessary backends, follow the instructions below:
\nmavlink2rest, pointing it to the endpoint provided by the MAVLink router. Remember to serve the API over the 6040 port by running it with --server 0.0.0.0:6040.Follow the instructions provided here to connect Cockpit to your vehicle.
\nIf you're running a BlueOS instance, just put the IP address of it in \"Global vehicle address\" and click the \"apply\" button.
\nIf you're serving mavlink2rest in the same machine as Cockpit, activate the checkmark for \"Mavlink2Rest connection\" and use ws://127.0.0.1:6040/v1/ws/mavlink there (if you're running a mavlink2rest version before 0.11.15, omit the /v1 in the URL).
If you're serving mavlink-camera-manager in the same machine as Cockpit, activate the checkmark for \"WebRTC connection\" and use ws://127.0.0.1:6020 there.
Cockpit provides a simulation environments in a docker compose file. There is an environment provided for ArduSub, ArduCopter, ArduRover and ArduPlane. The compose file uses docker compose profiles to allow you to choose which vehicle you want to simulate. The available profiles are ardusub, arducopter, ardurover and arduplane. You can run a simulation environment by running the following command:
docker-compose -f sim.yml --profile ardusub up
Assuming you have run the bun run dev --host command, you can access the simulation environment by opening the browser and accessing localhost:5173.
\n
An intuitive and customizable cross-platform ground control station for remote vehicles of all types. Click here for a demo!
\n\n
See our documentation \ud83d\udcd6
\nCockpit is typically installed as an Electron application or BlueOS Extension, but for development purposes it is valuable to run it locally.
\nTo start, clone the repository and its submodules. The submodules are required components for Cockpit to be able to run:
\ngit clone --recurse-submodules git@github.com:bluerobotics/cockpit.git
Next, install bun. Following their documented instructions is strongly recommended - we have received reports that installing bun from alternatives like Snap did not work properly.
With bun installed, you can enter the repository folder and follow the steps below:
bun install
and then run the server locally with:
\nbun run dev --host
Then you should see a prompt with the local IP and port that can be accessed through a browser, such as localhost:5173.
Cockpit is currently a frontend-only application. That means it relies on data offered by other backend solutions, which are not built-in.
\nIf you have a BlueOS instance running, there's no need to install any backend, as BlueOS already provides everything.
\nIf that's not your case and you want to install the necessary backends, follow the instructions below:
\nmavlink2rest, pointing it to the endpoint provided by the MAVLink router. Remember to serve the API over the 6040 port by running it with --server 0.0.0.0:6040.Follow the instructions provided here to connect Cockpit to your vehicle.
\nIf you're running a BlueOS instance, just put the IP address of it in \"Global vehicle address\" and click the \"apply\" button.
\nIf you're serving mavlink2rest in the same machine as Cockpit, activate the checkmark for \"Mavlink2Rest connection\" and use ws://127.0.0.1:6040/v1/ws/mavlink there (if you're running a mavlink2rest version before 0.11.15, omit the /v1 in the URL).
If you're serving mavlink-camera-manager in the same machine as Cockpit, activate the checkmark for \"WebRTC connection\" and use ws://127.0.0.1:6020 there.
Cockpit provides a simulation environments in a docker compose file. There is an environment provided for ArduSub, ArduCopter, ArduRover and ArduPlane. The compose file uses docker compose profiles to allow you to choose which vehicle you want to simulate. The available profiles are ardusub, arducopter, ardurover and arduplane. You can run a simulation environment by running the following command:
docker-compose -f sim.yml --profile ardusub up
Assuming you have run the bun run dev --host command, you can access the simulation environment by opening the browser and accessing localhost:5173.
\n
An intuitive and customizable cross-platform ground control station for remote vehicles of all types. Click here for a demo!
\n\n
See our documentation \ud83d\udcd6
\nCockpit is typically installed as an Electron application or BlueOS Extension, but for development purposes it is valuable to run it locally.
\nTo start, clone the repository and its submodules. The submodules are required components for Cockpit to be able to run:
\ngit clone --recurse-submodules git@github.com:bluerobotics/cockpit.git
Next, install bun. Following their documented instructions is strongly recommended - we have received reports that installing bun from alternatives like Snap did not work properly.
With bun installed, you can enter the repository folder and follow the steps below:
bun install
and then run the server locally with:
\nbun run dev --host
Then you should see a prompt with the local IP and port that can be accessed through a browser, such as localhost:5173.
Cockpit is currently a frontend-only application. That means it relies on data offered by other backend solutions, which are not built-in.
\nIf you have a BlueOS instance running, there's no need to install any backend, as BlueOS already provides everything.
\nIf that's not your case and you want to install the necessary backends, follow the instructions below:
\nmavlink2rest, pointing it to the endpoint provided by the MAVLink router. Remember to serve the API over the 6040 port by running it with --server 0.0.0.0:6040.Follow the instructions provided here to connect Cockpit to your vehicle.
\nIf you're running a BlueOS instance, just put the IP address of it in \"Global vehicle address\" and click the \"apply\" button.
\nIf you're serving mavlink2rest in the same machine as Cockpit, activate the checkmark for \"Mavlink2Rest connection\" and use ws://127.0.0.1:6040/v1/ws/mavlink there (if you're running a mavlink2rest version before 0.11.15, omit the /v1 in the URL).
If you're serving mavlink-camera-manager in the same machine as Cockpit, activate the checkmark for \"WebRTC connection\" and use ws://127.0.0.1:6020 there.
Cockpit provides a simulation environments in a docker compose file. There is an environment provided for ArduSub, ArduCopter, ArduRover and ArduPlane. The compose file uses docker compose profiles to allow you to choose which vehicle you want to simulate. The available profiles are ardusub, arducopter, ardurover and arduplane. You can run a simulation environment by running the following command:
docker-compose -f sim.yml --profile ardusub up
Assuming you have run the bun run dev --host command, you can access the simulation environment by opening the browser and accessing localhost:5173.
\n
An intuitive and customizable cross-platform ground control station for remote vehicles of all types. Click here for a demo!
\n\n
See our documentation \ud83d\udcd6
\nCockpit is typically installed as an Electron application or BlueOS Extension, but for development purposes it is valuable to run it locally.
\nTo start, clone the repository and its submodules. The submodules are required components for Cockpit to be able to run:
\ngit clone --recurse-submodules git@github.com:bluerobotics/cockpit.git
Next, install bun. Following their documented instructions is strongly recommended - we have received reports that installing bun from alternatives like Snap did not work properly.
With bun installed, you can enter the repository folder and follow the steps below:
bun install
and then run the server locally with:
\nbun run dev --host
Then you should see a prompt with the local IP and port that can be accessed through a browser, such as localhost:5173.
Cockpit is currently a frontend-only application. That means it relies on data offered by other backend solutions, which are not built-in.
\nIf you have a BlueOS instance running, there's no need to install any backend, as BlueOS already provides everything.
\nIf that's not your case and you want to install the necessary backends, follow the instructions below:
\nmavlink2rest, pointing it to the endpoint provided by the MAVLink router. Remember to serve the API over the 6040 port by running it with --server 0.0.0.0:6040.Follow the instructions provided here to connect Cockpit to your vehicle.
\nIf you're running a BlueOS instance, just put the IP address of it in \"Global vehicle address\" and click the \"apply\" button.
\nIf you're serving mavlink2rest in the same machine as Cockpit, activate the checkmark for \"Mavlink2Rest connection\" and use ws://127.0.0.1:6040/v1/ws/mavlink there (if you're running a mavlink2rest version before 0.11.15, omit the /v1 in the URL).
If you're serving mavlink-camera-manager in the same machine as Cockpit, activate the checkmark for \"WebRTC connection\" and use ws://127.0.0.1:6020 there.
Cockpit provides a simulation environments in a docker compose file. There is an environment provided for ArduSub, ArduCopter, ArduRover and ArduPlane. The compose file uses docker compose profiles to allow you to choose which vehicle you want to simulate. The available profiles are ardusub, arducopter, ardurover and arduplane. You can run a simulation environment by running the following command:
docker-compose -f sim.yml --profile ardusub up
Assuming you have run the bun run dev --host command, you can access the simulation environment by opening the browser and accessing localhost:5173.
\n
An intuitive and customizable cross-platform ground control station for remote vehicles of all types. Click here for a demo!
\n\n
See our documentation \ud83d\udcd6
\nCockpit is typically installed as an Electron application or BlueOS Extension, but for development purposes it is valuable to run it locally.
\nTo start, clone the repository and its submodules. The submodules are required components for Cockpit to be able to run:
\ngit clone --recurse-submodules git@github.com:bluerobotics/cockpit.git
Next, install bun. Following their documented instructions is strongly recommended - we have received reports that installing bun from alternatives like Snap did not work properly.
With bun installed, you can enter the repository folder and follow the steps below:
bun install
and then run the server locally with:
\nbun run dev --host
Then you should see a prompt with the local IP and port that can be accessed through a browser, such as localhost:5173.
Cockpit is currently a frontend-only application. That means it relies on data offered by other backend solutions, which are not built-in.
\nIf you have a BlueOS instance running, there's no need to install any backend, as BlueOS already provides everything.
\nIf that's not your case and you want to install the necessary backends, follow the instructions below:
\nmavlink2rest, pointing it to the endpoint provided by the MAVLink router. Remember to serve the API over the 6040 port by running it with --server 0.0.0.0:6040.Follow the instructions provided here to connect Cockpit to your vehicle.
\nIf you're running a BlueOS instance, just put the IP address of it in \"Global vehicle address\" and click the \"apply\" button.
\nIf you're serving mavlink2rest in the same machine as Cockpit, activate the checkmark for \"Mavlink2Rest connection\" and use ws://127.0.0.1:6040/v1/ws/mavlink there (if you're running a mavlink2rest version before 0.11.15, omit the /v1 in the URL).
If you're serving mavlink-camera-manager in the same machine as Cockpit, activate the checkmark for \"WebRTC connection\" and use ws://127.0.0.1:6020 there.
Cockpit provides a simulation environments in a docker compose file. There is an environment provided for ArduSub, ArduCopter, ArduRover and ArduPlane. The compose file uses docker compose profiles to allow you to choose which vehicle you want to simulate. The available profiles are ardusub, arducopter, ardurover and arduplane. You can run a simulation environment by running the following command:
docker-compose -f sim.yml --profile ardusub up
Assuming you have run the bun run dev --host command, you can access the simulation environment by opening the browser and accessing localhost:5173.
\n
An intuitive and customizable cross-platform ground control station for remote vehicles of all types. Click here for a demo!
\n\n
See our documentation \ud83d\udcd6
\nCockpit is typically installed as an Electron application or BlueOS Extension, but for development purposes it is valuable to run it locally.
\nTo start, clone the repository and its submodules. The submodules are required components for Cockpit to be able to run:
\ngit clone --recurse-submodules git@github.com:bluerobotics/cockpit.git
Next, install bun. Following their documented instructions is strongly recommended - we have received reports that installing bun from alternatives like Snap did not work properly.
With bun installed, you can enter the repository folder and follow the steps below:
bun install
and then run the server locally with:
\nbun run dev --host
Then you should see a prompt with the local IP and port that can be accessed through a browser, such as localhost:5173.
Cockpit is currently a frontend-only application. That means it relies on data offered by other backend solutions, which are not built-in.
\nIf you have a BlueOS instance running, there's no need to install any backend, as BlueOS already provides everything.
\nIf that's not your case and you want to install the necessary backends, follow the instructions below:
\nmavlink2rest, pointing it to the endpoint provided by the MAVLink router. Remember to serve the API over the 6040 port by running it with --server 0.0.0.0:6040.Follow the instructions provided here to connect Cockpit to your vehicle.
\nIf you're running a BlueOS instance, just put the IP address of it in \"Global vehicle address\" and click the \"apply\" button.
\nIf you're serving mavlink2rest in the same machine as Cockpit, activate the checkmark for \"Mavlink2Rest connection\" and use ws://127.0.0.1:6040/v1/ws/mavlink there (if you're running a mavlink2rest version before 0.11.15, omit the /v1 in the URL).
If you're serving mavlink-camera-manager in the same machine as Cockpit, activate the checkmark for \"WebRTC connection\" and use ws://127.0.0.1:6020 there.
Cockpit provides a simulation environments in a docker compose file. There is an environment provided for ArduSub, ArduCopter, ArduRover and ArduPlane. The compose file uses docker compose profiles to allow you to choose which vehicle you want to simulate. The available profiles are ardusub, arducopter, ardurover and arduplane. You can run a simulation environment by running the following command:
docker-compose -f sim.yml --profile ardusub up
Assuming you have run the bun run dev --host command, you can access the simulation environment by opening the browser and accessing localhost:5173.
\n
An intuitive and customizable cross-platform ground control station for remote vehicles of all types. Click here for a demo!
\n\n
See our documentation \ud83d\udcd6
\nCockpit is typically installed as an Electron application or BlueOS Extension, but for development purposes it is valuable to run it locally.
\nTo start, clone the repository and its submodules. The submodules are required components for Cockpit to be able to run:
\ngit clone --recurse-submodules git@github.com:bluerobotics/cockpit.git
Next, install bun. Following their documented instructions is strongly recommended - we have received reports that installing bun from alternatives like Snap did not work properly.
With bun installed, you can enter the repository folder and follow the steps below:
bun install
and then run the server locally with:
\nbun run dev --host
Then you should see a prompt with the local IP and port that can be accessed through a browser, such as localhost:5173.
Cockpit is currently a frontend-only application. That means it relies on data offered by other backend solutions, which are not built-in.
\nIf you have a BlueOS instance running, there's no need to install any backend, as BlueOS already provides everything.
\nIf that's not your case and you want to install the necessary backends, follow the instructions below:
\nmavlink2rest, pointing it to the endpoint provided by the MAVLink router. Remember to serve the API over the 6040 port by running it with --server 0.0.0.0:6040.Follow the instructions provided here to connect Cockpit to your vehicle.
\nIf you're running a BlueOS instance, just put the IP address of it in \"Global vehicle address\" and click the \"apply\" button.
\nIf you're serving mavlink2rest in the same machine as Cockpit, activate the checkmark for \"Mavlink2Rest connection\" and use ws://127.0.0.1:6040/v1/ws/mavlink there (if you're running a mavlink2rest version before 0.11.15, omit the /v1 in the URL).
If you're serving mavlink-camera-manager in the same machine as Cockpit, activate the checkmark for \"WebRTC connection\" and use ws://127.0.0.1:6020 there.
Cockpit provides a simulation environments in a docker compose file. There is an environment provided for ArduSub, ArduCopter, ArduRover and ArduPlane. The compose file uses docker compose profiles to allow you to choose which vehicle you want to simulate. The available profiles are ardusub, arducopter, ardurover and arduplane. You can run a simulation environment by running the following command:
docker-compose -f sim.yml --profile ardusub up
Assuming you have run the bun run dev --host command, you can access the simulation environment by opening the browser and accessing localhost:5173.