- This file is summarizing critical points related to the Keysight project.
- Diagram is a crude model representing the entire scope of the project to the best of my knowledge.
- OpenTAP's device under test is the 6G antenna and the cobot is an instrument used to collect data from different angles.
- Our team is initially primarily focused on the connection between OpenTAP and the cobot; everything else, put a pin in it then move it to the side for now.
We want to design plugins that'll extend cobot functionality into OpenTAP which will require a high level of software integration.
- Design should extrapolate to an arbitrary cobot; ROS2 might potentially satisfy this consideration.
- We should initially develop using Universal Robot's cobot and incorporate ROS2 into our design.
- OpenTAP will need to talk with UR Cobot...
- We will need C# or Python for the OpenTAP aspect
- We will need URScript and possibly SCPI for the UR aspect. Alternatively, Python or ROS2 might be a possibility.
- Having them communicate likely won't be too hard; the real issue is designing an interface to allow the operator to control the communication.
- Do we have predefined paths?
- Do we allow them to create their own path?
- How much control should we give them to define a path?
- How would they specify the path?
We need to start small with these essential activities.
- Activity1
- Create scripts for the UR simulator using URScript to perform simple actions.
- Activity2
- Create scripts using the ROS2 driver for the UR simulator to perform simple actions.
- Activity3
- Create a plugin that defines a cobot instrument then have it perform a simple action using activity 1 or 2.