Now that I have the system set up and the algorithm almost entirely finished, I have no choice but to go back to my most favorite of activities - trying to get the calibration correct on these k-ceptors.
While my sensors are steady most of the time, I've identified a consistent problem that every one of my k-ceptors has to a degree. They all start to lose calibration when moved to a specific position. For example, I have three k-ceptors all oriented the same way on a long tube for testing. When the tube is still, the k-ceptors do not move at all. I have had the system running the entire time I wrote this post and the k-ceptors haven't moved. When I roll the tube, the k-ceptors perform well, don't have drift issues, and return to their correct places . However when I stand it on one end, two of the k-ceptors immediately start drifting quickly off-axis while the other one drifts if I put the tube on it's other end.
Here is what I have done this time to try to remedy this:
Recalibrated and retested multiple times
Rewired the three sensors in different configurations (0-1-2, 2-1-0, 1-0-2)
Calibrated the sensors in an empty room, standing on a non-metal chair
Calibrated both out and in final enclosures with same issues
Ensured that the phone used to access the pi via SSH was 6+ feet away
Using a magnet, double checked that the brass screws and nuts were not magnetized
Tried calibrating with a different order of moving the faces
Sensors are stored loosely (so as not to torque anything) inside a box, are re-calibrated after being taken out of the box, and are only laid flat in between calibration and testing.
After recalibrating and retesting so many times, I'm finally getting close to having it properly working, I just need to figure out this odd issue. If necessary I can post video of these tests to better illustrate the problem I'm having. Am I just going to have to take them to a park to calibrate without magnetic interference?
P.S. Almost stopped testing because of the very frequent errors in the Blender addon, even without any nodes attached except the Notochord node. If anyone happens across this with the same issue, a patched version is here and works beautifully.
