Here come some answers and further questions to give another troubleshoot try
The current version of the addon requires you to complete the full functional calibration procedure, if you only do the static one it wont run the calibration at all, and what you are seeing is still the uncalibrated armature. Future versions of the addon will allow you to run just the static one, and optionally one or several of the functional ones.
For the static calibration part just a couple of seconds are enough
In the documentation it's stil not clear in which order the calibration should be done, nor when the calibration is completed. Is there a return from it in the console?
There seems to be a problem with one of the feet. It seems to be spinning wildly and then drifting in the video. Did you do the sensor calibration yourself or you are one of our P&P backers? Is it the same KC that was giving connectivity problems before?
I'm a Kickstarter Backer, so I didn't do the single sensors calibration. Should I do that myself of that specific sensor?
Which number are you using for the i2c_baudrate?
I changed it to 30000 as advised.
You should be able to initialze the notochord just by pressing the [Connect] button in blender. There's no need to do it from the remote console (in that case be sure to close the remote console, or all the initialization messages will go there instead of the blender GUI)
Yes, I went to the Console to verify first that the sensors are not giving an error from the very start. The Baud change helped in this sense.
There are some updates available for the notochord, It's advisable to hit the [ Update all ] buttton from the maintenance section of the remote console. Be sure to have internet access on the raspberry for that, the easiest way to achieve it is to connect it to a router using an ethernet cable
I will do this today