Hardware build record

cubesky

daylanKifky this one should fix the division by zero error https://gitlab.com/chordata/Blender-addon/-/jobs/1857765609/artifacts/browse

Blender addon works.

cubesky

notochord calibrate seems successful. But mag samples collected is 0.

daylanKifky

Great!

cubesky notochord calibrate seems successful. But mag samples collected is 0.

Yeah, this is a small bug that was never fixed, and now we are putting our efforts on developing the new notochord python module, so small details like this one get a really low priority.
The notochord is in fact collecting samples but displaying the number 0 at the end. You can check the calibration was successful by:

The result offset and matrix are as expected. The offset values should be in the range ±1 gauss, translated to 16bit signed integer values @ total sentitity range of 4 gauss ~= ±4095. They are also very rarely close to zero. The mag calibration matrix is mostly an identity one with small variations.
Try sending the single kceptor values to Blender. Do some 90deg turns in several axis and check that the virtual KCeptor inside blender behaves as the physical one

cubesky

daylanKifky
Oh, That's great. I will calibrate all KCepter these days (calibrate process is so boring, sad) and try to combine them to default biped configuration. Today, I will work with @YJBeetle to validate broken KCepter fix process.

cubesky

By the way, does notochord have functionality to extend device connected to i2c bus but not K-Cepter? We want to connect a finger bending sensor to this motion capture system.

cubesky

I just calibrate all KCepter. And now default biped capture configuration works!

This configuration is missing right leg due to broken KCepter. They will be add soon.

Next, I will add case to KCepter to protect them and find a way to fixing these sensor to my body. (Such as Elastic band or capture suit.)

cubesky

We designed a new K-Cepter case to protect pcbs with elastic band support , it only use about 30g material with FDM 3d print per case.

I plan to make a custom capture suit to use chordata capture system.

cubesky

We found that I2C chip on K-Cepter broken, it maybe cause by RJ12 connector with cable connect sequence. If SDA/SCL/GND connected and VCC not connect, it maybe cause current backflow to destroy i2c chip.
Does Chordata K-Cepter support hot-plug?

daylanKifky

Thanks for the contribution with the KCeptor case!

cubesky We found that I2C chip on K-Cepter broken, it maybe cause by RJ12 connector with cable connect sequence. If SDA/SCL/GND connected and VCC not connect, it maybe cause current backflow to destroy i2c chip.
Does Chordata K-Cepter support hot-plug?

The KCeptor itself does support hotplug but we had several cases of users getting the Hub's power source burn down because of hot plugging, so we currently recommend to plug and unplug the KCeptors R2.3 with Hub not powered.
There are other versions of the hardware currently available that support hotplugging like @valor's mini KCeptor

cubesky

I just remotely debug K-Cepter hardware newly build by @YJBeetle . (SSH to his raspberry pi 3B+)
When buliding notochord, I found scons on his raspberry pi is using Python3 on debian stable system. src/SConscript lib/SConscript SConstruct scons_utils.py need to use 2to3 -f all -f idioms -w to transform python2 to python3.

2to3 -f all -f idioms -w src/SConscript
2to3 -f all -f idioms -w lib/SConscript
2to3 -f all -f idioms -w SConstruct
2to3 -f all -f idioms -w scons_utils.py

and then, modify scons_utils.py these lines.
From if v > self.min_version: to if str(v) > self.min_version:
From version_num = search('\d\.\d\.\d', version) to version_num = search('\d\.\d\.\d'.encode(), version)

This will make scons script run on python3.

cubesky

K-Cepter Case design is open sourced under CC0 license.
https://gitlab.com/chordata-extends/k-cepter-case

cubesky

daylanKifky
Ok, I will take care of it.
Now, @YJBeetle is printing K-Ceptor case with his 3D Printer. He will post some photo soon.

YJBeetle

cubesky

Oh, I have typo in name of K-Ceptor, Gitlab Repo is moved to https://gitlab.com/chordata-extends/k-ceptor-case

YJBeetle

YJBeetle
最后发现出故障的都是焊接方面的问题，我重新进行焊接之后修复了
In the end, it was found that the faults were all welding problems. I fix it after re-welding.

daylanKifky

The case looks really neat!
It's normally advisable not to use metallic screws for the KCeptor, since they alter the magnetic field around it and it might cause heading misalignements. But since you already mounted it give it a try and let us know how it works!
You will need to perform the sensor calibration after putting the KCeptor in the case

cubesky

daylanKifky
We use 304 stainless steel screw, it doesn't has magnetic technically. I will re-calibrate it when I get it.
Or we can use nylon screw instead.

YJBeetle

daylanKifky

你说的对，我给忘了，螺丝必须更换。
可以更换为不锈钢螺丝或者铜螺丝，不过他们都有微弱的磁性，更简单的办法是换成尼龙螺丝。

You are right, I forgot it, the screws must be replaced.
It can be replaced with stainless steel screws or copper screws, but they all have weak magnetism. The simpler way is to change to nylon screws.

daylanKifky

Yeah, nylon is better. Non magnetic metal should work, but we had reports of users having problems with that. Since you have already mounted these ones it would be great if you can perform a calibration now and another one after you change them and compare the results.
If you do that please paste here the calibration offset and matrix that the notochord prints after the procedure

cubesky

daylanKifky
Ok, I will do this when I get them from @YJBeetle . It maybe 2-3 days later, because we don't in the same city, K-Ceptor and case need express delivery.

« Previous Page Next Page »