Post by Max on Mar 13, 2018 0:39:26 GMT -7
The confusing part is about the registers. I can't figure out what you mean by that. Heat sinks on motor drivers?
First thing Sdk does is read accelerometers to establish frame of reference, otherwise commands like moveTo(x,y,z) make no sense as it doesn't know where end effector starts.
And that is the part that hangs firmware when accelerometers are nowhere to find.
If you look at Sdk implementation you can see how to set initial arm angles statically so that it can skip requesting accelerometers.
If the driver example moves motors infinitely until you stop the script then everything except accelerometers works as expected.
Don't forget to buy ferrite beads, you'll need them to make GY-521 work. Otherwise there is too much interference from motors.
First thing Sdk does is read accelerometers to establish frame of reference, otherwise commands like moveTo(x,y,z) make no sense as it doesn't know where end effector starts.
And that is the part that hangs firmware when accelerometers are nowhere to find.
If you look at Sdk implementation you can see how to set initial arm angles statically so that it can skip requesting accelerometers.
If the driver example moves motors infinitely until you stop the script then everything except accelerometers works as expected.
Don't forget to buy ferrite beads, you'll need them to make GY-521 work. Otherwise there is too much interference from motors.
