GlowBallVR
Hi!
this a typical problem of using a young, still under development system. The -r is not even used anymore for calibration! It's not your fault if you get confused. It's just that the wiki was outdated on that part.
I corrected it now.
We are aware that the wiki can still be a little confusing for people without advanced technical knowledge, one of the goals of the beta-testing program is to fix that. By pointing us this confusing parts you help us improving it.
So, back to your situation, starting with a quick review:
The notochord can only run on linux, and is meant to be used on the microcomputer only. This program is responsible for reading the sensors and sending data to blender. So if it is not running you won't receive anything (in the future you will be able to skip this manual execution, and just initialize it from Blender. But for now you have to do it manually).
By running it with the --scan flag it will search for connected K-Ceptors, and start reading them. It will send the data he reads to the ip address you asked for, the address should be the one of your PC, the one that runs Blender.
On Blender, when you press the [RECEIVE] button, it will wait for incoming messages. If nothing is coming it will show no movement. You can turn on debug mode to print all the messages Blender is receiving to the console
(in order to display the debugging console in blender take a look here)
I guess you get up to this point. right?
Thing is: there's a catch on this workflow!
When you use the --scan flag the notochord will assign a name to each KC it found based on the Gate and address of that particular KC. So you will end up with names like kc_CH01-1.
When Blender receives a message from the notochord, it will assign the given rotation to the object or bone with the same name.
The bottom line here is: In order to see the virtual KCeptor rotating in Blender you will have to change it's name to match the one notochord assigned to the sensor you are testing.
You will know the name because notochord will it print upon initialization.
If you are not familiar with Blender and is hard for you to change the name of the object let me know, and I will send you a modified file
This procedure is cumbersome and confusing, we know. We are working on a much more straight forward way to calibrate the sensors and receive automatic visual feedback using the remote console. We are all looking forward for it to be finished 🙂
And regarding your situation with the ENTER key.. It shouldn't be specified: it should be fixed because it's a bug! We were not aware it was happening. Can you report it on the notochord issue tracker?
