diff --git a/README.md b/README.md index d619973295f2a5c81443b82313a70d934aa71d8e..a3d2e503d68e56a0aa900b3edda68f74160eb50d 100644 --- a/README.md +++ b/README.md @@ -1,92 +1,9 @@ -# robot_fdm_print_setup +# Setup for FDM printing using ABB robot at LTH Robotlab +## Hardware +TK -## Getting started +## Software -To make it easy for you to get started with GitLab, here's a list of recommended next steps. - -Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)! - -## Add your files - -- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files -- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command: - -``` -cd existing_repo -git remote add origin https://gitlab.com/maef-lth/robot_fdm_print_setup.git -git branch -M main -git push -uf origin main -``` - -## Integrate with your tools - -- [ ] [Set up project integrations](https://gitlab.com/maef-lth/robot_fdm_print_setup/-/settings/integrations) - -## Collaborate with your team - -- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/) -- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html) -- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically) -- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/) -- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html) - -## Test and Deploy - -Use the built-in continuous integration in GitLab. - -- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html) -- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/) -- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html) -- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/) -- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html) - -*** - -# Editing this README - -When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template. - -## Suggestions for a good README -Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information. - -## Name -Choose a self-explaining name for your project. - -## Description -Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors. - -## Badges -On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge. - -## Visuals -Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method. - -## Installation -Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection. - -## Usage -Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README. - -## Support -Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc. - -## Roadmap -If you have ideas for releases in the future, it is a good idea to list them in the README. - -## Contributing -State if you are open to contributions and what your requirements are for accepting them. - -For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self. - -You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser. - -## Authors and acknowledgment -Show your appreciation to those who have contributed to the project. - -## License -For open source projects, say how it is licensed. - -## Project status -If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers. +- [ABB Robotstudio with 3DP Power Pac](./robotstudio) diff --git a/robotstudio/README.md b/robotstudio/README.md new file mode 100644 index 0000000000000000000000000000000000000000..1f525d703a9dcd69b37b3d39690461bf7deb5b92 --- /dev/null +++ b/robotstudio/README.md @@ -0,0 +1,71 @@ +# ABB Robotstudio with 3DP Power Pac + +## Install ABB Robotstudio + +[Download installer for ABB RobotStudio](https://new.abb.com/products/robotics/robotstudio) + +You need to provide personal information to download the software. + +Extract the zip file after the download has finished and run setup.exe in the +RobotStudio folder. + + +During setup when asked for license, either use the trial (30 days) or the +license server at LTH (robotstudio.cs.lth.se). If you are not at LTH you will +need to use [LTH's +VPN](https://luservicedesk.service-now.com/support_en?id=kb_article_en&sys_id=3fcba671db7c6c506452cd4d0b96198c). + +If you use the license server at LTH you will need to have access to the license +server whenever you run Robotstudio, unless you "check-out" a license[^footnote-robotstudio-check-out]. + +## Install RobotStudio 3D Printing PowerPac + +To find the download link go to [RobotStudio® 3D Printing +PowerPac](https://new.abb.com/products/robotics/application-software/3d-printing-powerpac) +and scroll down to "Downloads for 3D Printing PowerPac". Select software in the +column to the left and download the latest version. + +Extract the zip file. + +Open RobotStudio: In the Ribbon find `Add-Ins > Packages > Install` and then +locate the installation file from the extracted zip file with the file extension `.rspak`. + +You will find a new icon named 3D printing in the Add-on ribbon after a restart of RobotStudio[^footnote-find-3dp-button]. + +## Setting up robot station + +There's a [prepared "pack-and-go" file that you can "unpack-and-work" with in +this directory](./V_LTH2400_RW612.rspag). + +Before unpacking though you will need to make sure that you have the correct +RobotWare version installed. + +You will find RobotWare version 6 and 7 in `Add-ins > Gallery`. It's usually the +first two ones. Select "Robotware for IRC5". In side panel to the right select +`6.12.04` and click `Add`. + +After you have installed this you can go ahead and open the pack-and-go file. Go +to `File > Share > Unpack and work`. + +After clicking through the wizard and waiting a bit you'll see "Controller +status: 1/1" in green in the bottom right controller. + +You can find manuals and tutorials under `File > Help`. Both the RobotStudio +help here as well as the manuals for IRC5 are helpful. + +## Starting 3DP PowerPac + +In your station (created from the pack-and-go file) you can now open the 3DP +tool. Go to `Add-Ins > PowerPacs > 3D Printing`. + +Instructions on how to use the PowerPac can be found in the 3DP ribbon under +`3DP Help > Application manual`. + +[^footnote-robotstudio-check-out]: You can check out a license for up to 90 +days. This allows you to run RobotStudio even when offline. You can check out a +license using the Activation Wizard found under `File > Options > Licensing`. + +[^footnote-find-3dp-button]: If not, make sure to check that RobotStudio has + found your license server (or that you have a valid checked out license or + trial license). You will find messages regarding licensing in the tab + labelled output near the bottom of the screen in RobotStudio. diff --git a/robotstudio/V_LTH2400_RW612.rspag b/robotstudio/V_LTH2400_RW612.rspag new file mode 100644 index 0000000000000000000000000000000000000000..7d801bbc0d64c777075e1ce6821230c6c7ccfa2f Binary files /dev/null and b/robotstudio/V_LTH2400_RW612.rspag differ