Recomputed Hexapod is sometimes not equal to Updated Hexapod. Why? #41

Activity

1. mithi

   added

   bugSomething isn't workingSomething isn't working

   help wantedExtra attention is neededExtra attention is needed

   PRIORITYThis should be addressed firstThis should be addressed first

   on Apr 13, 2020
2. mithi

   changed the title [-]Recomputed Hexapod != Updated Hexapod[/-] [+]Why is Recomputed Hexapod != Updated Hexapod ????[/+] on Apr 13, 2020
3. mithi commented on Apr 13, 2020

   

   mithi

   on Apr 13, 2020

   OwnerAuthor

   More actions

   The legs are sinking. Problem in
   inverse_kinematics_update(), see image below
   
4. mithi

   pinned this issue on Apr 14, 2020
5. mithi

   changed the title [-]Why is Recomputed Hexapod != Updated Hexapod ????[/-] [+]Recomputed Hexapod not equal to Updated Hexapod. Why?[/+] on Apr 14, 2020
6. mithi commented on Apr 14, 2020

   

   mithi

   on Apr 14, 2020

   OwnerAuthor

   More actions

   
7. mithi commented on Apr 15, 2020

   

   mithi

   on Apr 15, 2020

   OwnerAuthor

   More actions

   

   
8. mithi

   changed the title [-]Recomputed Hexapod not equal to Updated Hexapod. Why?[/-] [+]Recomputed Hexapod is sometimes not equal to Updated Hexapod. Why?[/+] on Apr 15, 2020
9. mithi

   unpinned this issue on Apr 15, 2020
10. mithi

    removed

    PRIORITYThis should be addressed firstThis should be addressed first

    on Apr 16, 2020
11. mithi

    pinned this issue on Apr 16, 2020
12. mithi

    unpinned this issue on Apr 16, 2020
13. mithi commented on May 2, 2020

    

    mithi

    on May 2, 2020

    OwnerAuthor

    More actions

    There must be a wrong assumption in the IK algorithm here...
14. mithi

    removed

    bugSomething isn't workingSomething isn't working

    help wantedExtra attention is neededExtra attention is needed

    on Jun 18, 2020