If you don't see the name of your KC in the drop down of the testcube mode it probably means the messages are not arriving to the add-on.
Try plugging a dump node to the main notochord node and turn on all the streams. You should see messages printed on the blender console

    HalloweenBob guess I don't know how to upload a picture

    You can just paste the URL when you use external images. I edited your post.

    When using the icon below it creates an empty markdown image syntax. The URL goes inside the paréntesis. To upload an image use the upload button

      daylanKifky Thanks for fixing my post. I did use the upload button and it gave me an error. Anyway, being a little slow here, I don't know what a dump node is or where to get one. I must have been absent for that class. I assume that's something I need to do on the Pi and not in blender but I really don't know.

      UPDATE: I just found the Dump Node in blender. I will work on that and report results.


        I don't know if I set it up right, but it doesn't seem to be making any difference. I expected that it would have to come before the Test Cube node, but since it has no output, I had to do it this way. I could have linke it to the Data Out from the test cube, but I don't see how that would help, and I tried it anyway with the same results.

        This is Blender version 2.83

        You could check if the osc stream is even giving an output, that would at least verify if there's any data.

        Instructions here

        Also, the "KCeptor_R1" in the objects panel is just the name of the 3D model and doesn't correspond to kceptor version.

        Thanks for the heads up on the KCeptor_R1 label. I was wondering about that. Regardless, my KCeptor did not show up in the download list. I tried checking the Osc Stream as you suggested but got the following result:

        I tried it both with `/notochord, and with ./notochord just in case it was a typo or something. The result was the same.

        Any other suggestions? This is so close now. The Pi thinks everything is fine, and I can communicate with it through SSH.
        That means that it is communicating with my computer. I'm not sure where to go with it next. I was thinking of trying a different cable to connect the KCeptor to the hum, but if that were the problem, I wouldn't have been able to calibrate it.

        Try this:

        ./notochord/lib/oscpack_1_1_0/bin/OscDump 6565

        And when you run the notochord in another window, make sure it's set to localhost.

        How do I set it to localhost? I'm using PuTTY and I connect by using the IP address of the Pi.

        Make sure to run
        make dump
        in the /oscpack_1_1_0 folder first

        How would anyone ever know to do this stuff? Will I have to do this every time I want to run this? I'll give it a try.

          OK, it finally worked, sort of. It understood the command, but apparently didn't find anything to listen to.

          I left it listening for about 2 minutes before pressing C. Also, During that time, I connected with Blender, and was moving the KCeptor.

          Apologies if the comment that I linked earlier didn't help enough.

          The osc listener runs simultaneously with the notochord and does not connect with blender in any way. In order for it to capture the data, you run the notochord in another window connected in the same way with SSH. Then instead of your computer IP, you use localhost.
          ./notochord --scan localhost
          If the problem is with the communication to blender, you'll see data in OscDump. If the problem is the k-ceptor's communication, you won't.

          HalloweenBob Will I have to do this every time I want to run this?

          The procedure @duncan006 is suggesting can be uses to troubleshoot connection problems like the one you are facing. It doesn't have to be repeated once you get it working.
          I have the feeling there's a firewall blocking the messages. Many windows users reported similar problems, and had to make many attempts to get the firewall configuration right. The oscdump procedure confirms data is coming out from the notochord by redirecting it directly to the raspberry itself, thus avoiding any possible firewall

            OK, just got back to this tonight. I have had some very brief success. I went through everything again, and started notochord, scanned the computer running blender, connected found the right KCeptor and selected it and it started moving exactly as it should in blender!

            That lasted for about 5 seconds then I got the error message I have included here and Blender disconnected. I tried again a dozen times and got disconnected every time, most of the time faster than I could reach for the KCeptor. A few times I got a few seconds before it crashed.

            At least I know I'm connecting correctly and don't have WiFi or Firewall issues.

            Any ideas?

            Tried again just for laughs. This time it started and stopped giving me the error as before, but when I restarted it, things were different. It didn't disconnect, but instead the KCeptor model froze while I was moving the device, and I got this message:

            It doesn't even look like a real sentence and I have no idea what it means.

            Disconnecting and reconnecting made no difference. The KCeptor Model remained frozen and I got this error message again, but it still said it was connected in blender.

              Hi,
              The float division by zero bug is already reported https://gitlab.com/chordata/Blender-addon/-/issues/7
              You should be able to sidestep it for now by unplugging the Stats node.

              Let me know how it goes

              HalloweenBob It doesn't even look like a real sentence and I have no idea what it means.

              It's just the tooltip containing a brief description about the "Connect" operator but written with my terrible english in combination with little attention paid to these details. To anyone willing to start contributing on the code: correcting the many weird sentences that are distributed among all the codebase would be an easy task.

                No problem on the sentence. It was hard for me to tell if there was a thing called a Parses Tree or if something was parsing a tree (Which makes more sense) I will look up how to unplug the Stats node.