So, I have had my mkII sensor for a few days, and have had absolutely Zero luck getting even a basic scan. I have noticed a few things during the troubleshooting process, and wanted to see if I am alone in this??
Battery life - I can get about 20 minutes MAX during my troubleshooting session before the sensor starts going even MORE unstable (which believe me, is a hard thing to do) and reports that it is low on power necessitating a charge. I do not know what the expected session time is for the sensors, but I have to imagine that 20 minutes or less is not it.
1a. When charging off of any power source (I have tried high Amperage capable chargers just to see if it was hungry) the light moves to a flashing blue as expected, but very quickly, far more quickly than is possible for a full charge, the light will change to a solid blue indicating that it has completed charging. Even so, whether I believe it or not to be full (i.e., whether I let it charge all night or just the time it said) the results are the same, ~20 minutes before going out.
Calibration - I think I know there are a ton of known issues here. the main one I am curious to see if others have, though, is a completely black screen in the end of the process where you would normally do the manual mapping.
Scanning - Even after completing a successful calibration (though without the last manual nudge) I get stuttery (flashing on and off) and sparse hits by the sensor. I am seeing about 5 percent or less hits from the sensor. This means nothing at all is scanable whether it be a room scan or an object scan.
Depth sense - Possibly the cause of the previous two items… I noticed that when I am looking at the depth data returning from the device, it appears to be only seeing the edges of objects, not the faces of them. So, for example, if looking at a tripod it will see the edges of the legs in form, but nothing else (and the edges are spotty as well, but they at least show) Almost the exact opposite of what I would expect. Taking that observation a step further, it appears that it’s not just edges, it looks like like it is behaving almost the opposite of a polarized sensor… it appears the only things that are registering any depth data are those things which are REFLECTING a lot of light (which I suppose partly makes sense since the IR needs that bounce back, but these spots are very specific)
Net result = unusable sensor, has anyone else experienced the above and found a solution?