Hardware build record

daylanKifky

It doesn't look like a pose calibration process, since it calculates the quaternion value just once and then applies it to the whole calibration session. You cannot get a rotating sensor as a result of a bad pose calibration.

It seems like the values coming from the sensor and fed into the kalman filter inside the notochord are not good.
Did you get the change to re-calibrate the sensor or replace it?

cubesky

daylanKifky
I randomly switch k-ceptor with another k-ceptor, but it seems it doesn't matter. Rotation error is randomly appear on random K-Ceptor node, everytime reset pose and restart calibrate process on blender will change the result.

cubesky

daylanKifky
It seems recalibrate the K-Ceptor itself doesn't work.

daylanKifky

cubesky
what about replacing it?

if you can post a dump of the raw values of the sensor while it rests on a table I can try to spot errors. IF you do so please use an external service like pastebin.com and include the link here

cubesky

daylanKifky
I don't have replacement sensor this time, COVID-19 is affect express delivery this time in my country. But I can dump raw values of sensor, I will use Gitlab snippets to post data.

cubesky

daylanKifky
I just collect all 15 K-Ceptor data, here is the debug log. I notice some K-Ceptor has wrong initial orientation. Maybe it needs recalibration.

cubesky

cubesky A K-Ceptor output wrong orientation, when I place it facing south, it output facing west. This error maybe affect the pervious foot rotation problem.

daylanKifky

Hi everyone!
Sorry for missing these posts. In fact the spam is terrible lately. We are looking for alternative systems to filter them since the current ones are not working. As cubesky suggested they are probably hand posted by humans.

cubesky I notice some K-Ceptor has wrong initial orientation. Maybe it needs recalibration.

Can you point which ones had this initial wrong orientation?

cubesky

@daylanKifky
And I think chordata team need to clean up this forum by removing spam threads and add effective captcha system to avoid spam thread.

NakedRabbit

cubesky I'm doing all I can to flag them, but the robots will beat me every time.

cubesky

NakedRabbit I see.... It seems reCaptcha can not detect them... Maybe they are manually operation by human?

cubesky

daylanKifky
It's KC-l-foot, it totally rotate 90 deg. When I place it facing south, its output facing west.

daylanKifky

Hello cubesky,
Sorry I missed your answer. The spam really flooded the front page of the forum.

I was trying to troubleshoot your problem, but need some additional info to understand it correctly.
We have to find out if it's a pose calibration problem or a sensor problem.

cubesky It's KC-l-foot, it totally rotate 90 deg. When I place it facing south, its output facing west.

Is this happening when you run the default_biped confirguration with the avatar and perform the pose calibration or you get this result with the single sensor using the Test Cube node?

If it's the sensor alone then it's probably a hardware problem which is really difficult to solve (if I get it correctly you already tried re-calibrating the KCeptor, right?)

Also: what happened with the one which was spinning all the time in the video you sent? Is is the same KCeptor?

cubesky

daylanKifky Yes, it's the same KCeptor spinning all the time. I test this KCeptor alone, it has rotation issue, so this KCeptor is sending to YJBeetle to change a chip.

cubesky

The LSM9DS1 chip on these K-Ceptor is replaced by @YJBeetle. Beacuse of COVID-19 and other activity in my city, express delivery is delayed about 3 weeks. Now, I get the fixed K-Ceptor (but not calibrate and test yet.).

« Previous Page Next Page »