Announcement

Collapse
No announcement yet.

motion/angles/roll issue

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • motion/angles/roll issue

    Dear Camille,

    sometimes osculator stops receiving ROLL data from MotionPlus. I don't understand.

    I have two wiimotes and three motionPlus, and all of them sometimes stops receiving motion/angels/roll.

    Do you have any idea?


    OSCulator
    Version 2.12.7 (20130308)
    OSX Mountain Lion 10.8.3
    Wiimote+motionPlus (without nunchuk)


    ScreenShots:




    Thanks,
    Jong

  • #2
    only the problem is "motion/angels/roll".

    its really annoying me...

    Comment


    • #3
      I'm using osculator with PD. In PD shows the data. It stops always at -1

      https://dl.dropboxusercontent.com/u/...2005.13.02.png

      Comment


      • #4
        Hi Jong,

        This seems very weird, I don't understand too.
        I never seen this problem before, and when a motion plus OSC message is sent, every values are sent at once (roll is handled no differently than pitch or yaw for example).

        Can you please confirm that every OSC Routing has <all args> as the only rewrite token?
        Also, could you try to set the default OSC target to an unused slot, like 7 ?
        It would be useful to print a log in PureData of the OSC messages it receives.

        Best,
        Camille

        Comment


        • #5
          Hi Camille,

          thanks for your answer.

          some questions:

          1.
          Can you please confirm that every OSC Routing has <all args> as the only rewrite token?
          >I don't understand, how to do that? Could you give me more detail?

          2.
          Also, could you try to set the default OSC target to an unused slot, like 7 ?
          > I did, but it isn't works.

          3. a log in Pd

          motion/angles
          pitch, roll, yaw

          print: 0.512486 nan 0.109231
          print: 0.506721 nan 0.109244
          print: 0.511635 nan 0.109265
          print: 0.5128 nan 0.109284
          print: 0.512597 nan 0.10929
          print: 0.512479 nan 0.10928
          print: 0.512477 nan 0.109262
          print: 0.506721 nan 0.109249
          print: 0.511621 nan 0.109246
          print: 0.507033 nan 0.109254
          print: 0.511735 nan 0.109268
          print: 0.507023 nan 0.109284
          print: 0.511717 nan 0.109303
          print: 0.507017 nan 0.109325
          print: 0.505951 nan 0.109352
          print: 0.511913 nan 0.109379
          print: 0.512885 nan 0.109398
          print: 0.506826 nan 0.109409
          print: 0.511606 nan 0.109412
          print: 0.512791 nan 0.109409
          print: 0.512594 nan 0.109404
          print: 0.512479 nan 0.109405
          print: 0.512476 nan 0.109413

          the nan must be an float, but nan... what is nan? really I don't know...

          Thanks,
          Jong

          Comment


          • #6
            Hi Jong,

            NaN means "Not a Number", which typically happens when there is a math error.
            I will check why this could happen and come back to you.


            Best,
            Cam

            Comment


            • #8
              Maybe need you something more? I can tell you more detail, if you need more.

              I really want to fix it.

              Comment


              • #9
                I think I found a solution to this problem, thank you for pointing that out.
                I will send you a fix in the next minutes.

                Comment


                • #10
                  good news. I'm waiting for it

                  Comment

                  Working...
                  X