01-13-2016 04:02 PM
01-13-2016 04:27 PM
Ryleck, welcome to the forums. It really depends on what your robotic arm is and how the motors on them work. Are you trying to make your own arm? Any hardware to work off of?
01-13-2016 06:40 PM
Some other people in my group are making the arm i dont know what the arms hardware is beacause they havent finished it yet
01-13-2016 08:19 PM
01-14-2016 07:39 AM
When you have a team working on a project where vaious individuals or subgroups work on different aspects of the project, it is essential that careful planning and decision making takes place before work on the specific tasks begins. That planning must include definition of the interfaces between the portions of the project. It must also include a clear indication of who will resolve differences between the subgroups.
To use your project as an example: The project could be divided into these sections: The framework of the arm, the pneumatic actuators for the arm, the electrical interface between the actuators and the controller, and the control program. The interface between the framework and the actuators will be defined by the required, forces, speed, and available space. The interface between the actuators and the electrical interface will likely be limited by the types of actuators types of power sources available The interface between the electrical interface and the controller defines the type of DAQ or communications hardware and protocols need to connect the computer to the hardware. FInally the design of the control program itself includes the user interface, the operational requirements of the system, the nature of the interface to the controllers, and safety requirements. Some safety requirements amy need to be implemented at the electrical or pneumatic hardware levels rather than in software.
Lynn
01-14-2016 10:15 AM
Lynn gave you a great reply above. Good job on thinking about the programming piece of the project so far ahead. A good programming practice is to plan out all the functionality that you want on a higher level before going into the actual programming. With a higher level of planning, you can determine what your system needs as a whole, and from there figure out how you will implement the functionality that you want. Since your group has not decided on hardware yet, that is even better, because a high level of planning will help you decide on what type of hardware you need and how you will control the hardware with software. It sounds like you are still early enough in the project that there are still many options open. If you are stuck in the planning stage, you might be able to get some inspiration from looking up some videos or papers of robotic arms that people have made. There are quite a few neat videos out there.
01-14-2016 03:23 PM