So, there can be unforeseen movements; therefore, each step [of the robot] towards the next waypoint is being tested before the entire program runs because there are some [robot] motions, where\u2014and this happened a few times during workshops\u2014the robot chooses a completely different way as one would expect.<\/p>\n<\/blockquote>\n
The problem of unforeseen motion paths is pointed out by the trainer as one potential safety issues occurring during workshops. Unforeseen pathways between predefined waypoints occur because the so-called inverse kinematics algorithms, which compute the six robot joint angles for any given target pose and then rotate the elements of the robot arm until that target pose is reached. This issue is treated differently by the makerspace trainers. The following discussion illustrates this contrast:<\/p>\n
\n Interviewer:<\/em> So with MoveJ [joint based movement, as explained before] or which kind of movement?<\/p>\nTrainer<\/em>: Definitely not linear. I think it must have been MoveJ. For sure.<\/p>\nInterviewer:<\/em> And this happens also when you are running the simulation on the teach pendant first, or\u2026<\/p>\nTrainer<\/em>: This, funnily, we don\u2019t do.<\/p>\nInterviewer:<\/em> Ok.<\/p>\nTrainer<\/em>: We do not watch the simulation [of the movement].<\/p>\nInterviewer:<\/em> \u2026 pause \u2026 Me neither!<\/p>\nTrainer<\/em>: Ok. [Laughing together]<\/p>\n<\/blockquote>\nOne way to avoid unexpected robot pathways is to first simulate them using the robot\u2019s software. Yet, in the makerspace using the simulation to preview the robot\u2019s movements during trainings does not appear to be a common practice. Although intrigued by this answer, we tried to avoid being normative by admitting that simulation is not always necessary. The next excerpt illustrates how unforeseen movements are being perceived by trainer and trainees and how the latter go about explaining what happens behind the scenes:<\/p>\n
\n Interviewer:<\/em> Is this [the unexpected movement] something that disturbs the workshops or is it funny when it happens? What is the effect?<\/p>\nTrainer:<\/em> The effect is mostly \u201coh, I did not reckon with that.\u201d [The trainees] are surprised but they are not scared. [\u2026]<\/p>\nInterviewer:<\/em> And if they ask \u201ewhat just happened?\u201d\u2014How do you explain that?<\/p>\nTrainer:<\/em> We try to find out together, to remove [the problem]. I think I never spoke in a workshop about inverse kinematics. I try to avoid that because, to be honest, I am not knowledgeable enough myself to properly explain that. What I do explain is that, during the different movements\u2014that is, MoveJ\u2014the robot uses the axes in such a way that it is most effect for itself. And in the case of a linear movement, it goes from point to point in a line, which is not the case with MoveJ. So this is my explanation for the two movement types.<\/p>\n<\/blockquote>\nIn this excerpt, the makerspace trainer seems to argue in favor of providing non-expert explanations for unexpected robot movements, while invoking her lack of knowledge concerning inverse kinematics. In these situations, the trainer seeks ways to legitimize simplified explanations over robotics terminology in an attempt to distill the necessary practical knowledge from a theory that is inaccessible to non-experts. Nevertheless, the trainer adopts the technical term \u2018MoveJ\u2019, which we had dropped earlier in the discussion, thus showing how the language exchange takes place. To the question of whether one would gain something by talking about inverse kinematics during the workshops, the makerspace trainer responded:<\/p>\n
\nI don\u2019t think so. I think, to be honest, that inverse kinematics is only relevant when one is really interested in robotics, that is, when one wants to go deeper. But for programming, if one is taught how\u2014and this pertains to intuition\u2014to learn something not through reading but through \u201cdoing\u201d and to understand and for that there are possibilities in the makerspace; and everyone who works with [the robot] knows it that every step that I program must be tried out and not with 100% speed. And I think that this way, one gets a tremendous feeling about what is possible and what is not.<\/p>\n<\/blockquote>\n
The trainer stresses that speaking about this problem using robotics terminology is neither necessary nor desirable. Then, she goes on and sketches the profile of a projected cobot user, who is likely to be encountered in the makerspace. The responsible cobot user is as such becoming defined as a pragmatic individual, who is well-aware of the safety hazards entailed by working with the cobot while nonetheless being more interested in programming the cobot than in learning about its internals. This type of user is expected to benefit from the resources of the makerspace (interested peers, more experienced trainers, other workshops, etc.) to learn about safety and other issues. The makerspace is thereby stipulated as a source of practical knowledge and possibilities\u2014one only needs to ask and come up with ideas, whereby the role of reading is superseded by that of \u201cdoing.\u201d Together with the image of the pragmatic, responsible cobot user, downplaying the importance of robotics theory and terminology may be regarded as an act of resistance to well-established forms of knowledge, learning, and acting that are characteristic for traditional institutions; a resistance articulated around knowledge gained through and (re-)invested in practice rather than theory; and a form of resistance through doing that keeps the power relations between makers and researchers balanced and the principle of symmetry upright. In the next chapter we will explicate however that the makerspace in question itself becomes reconfigured throughout the course of the project.<\/p>\n
5. Reconfiguration<\/h2>\n
In the second part of our analysis we trace how the studied makerspace reconfigured under the influence of other institutional models. By facilitating a trading zone in which the makerspace becomes accessible to research institutes and companies, its activities are increasingly projectified and a process of professionalization is being pursued. We analyze this by going through three different roles of the makerspace, namely: the makerspace as the provider of infrastructures behind this trade, the makerspace as a party with specific interests in the project leading to particular expectations concerning the project\u2019s outcome, and finally the makerspace as a trading partner in exchanges that are supposed to help in the co-construction of cobot technology.<\/p>\n