Has anyone messed with the new "Custom Sensor" feature of the 3.01.01.07 firmware for SDM3065X? I haven't found documentation on it yet. I think I've figured it out but I'm getting some odd behavior, so I'm not sure if it's just me or if I've found a bug.
I'm measuring a photodiode in photovoltaic mode, so zero applied voltage. Spec says 0.4A/W response with 1.2mm^2 active area. I measure it with regular DCI mode on 3065 DMM and get +/- 0.8nA when the sensor is in a dark box, and around 1.5uA with sensor pointed at ambient lighting. Those numbers seem reasonable to me with a little noise around zero. Turning on statistics with averaging puts "zero" at about 0.1nA, which is decently accurate in my book.
With the custom sensor mode, you can select DCI as the sensor type, which I did, and you enter a few Measurement->Result data points into a table for the DMM to interpolate, which I did. But the sensor results I'm seeing appear to have 2 separate issues that might be bugs. First, the interpolated displayed result of a current sensor measurement in ambient light seems close but not accurate to what I calculate it to be. This might be a misunderstanding on my part, but I havent found docs on this feature yet. The other issue is when you change Temp mode (with custom sensor selected) to display both measured value and interpolated result, the current reading from the sensor is showing around -170nA for "zero light", which I already measured with the same DMM at 0.1nA. Changing back to normal DCI mode instead of Temp mode shows the expected 0.1nA. The other issue I found is not enough significant digits in the table entry, +/-000.000001 is the smallest you can enter, so I can't just manually force an offset adjustment to work around the wierd "-170nA" reading issue. I'm not positive, but auto-zeroing seems like it might be turned off in Temp mode with a DCI mode sensor.
So... Am I hitting bugs, or am I just not doing something right?