Open nikolasgd opened 23 hours ago
This is strange, I will check it tonight.
Maybe you can use the Python API to check the raw readings first, as I have not been able to identify any issues from your screenshot.
Is your firmware up to date?
Perhaps this problem is caused by the calibration parameter differences reported by P905 and P906. If possible, you can attach the log file to this issue for me to check.
By setting the system environment variable "MDP_ENABLE_LOG" to "1," the software will create a log file. Perform some operations, and then attach the log file to a comment.
If the problem is finally not found, I can add an option to adjust the calibration parameter, allowing you to manually calibrate the current and voltage readings.
I have installed the latest firmware on the P905.
I am using the Windows packaged version, is it possible at all to set environmental variables? Will the Python API be able to connect to the USB adapter, if I run the application from within WSL2?
I know how to do all this on my M3 Macbook with Mac OS Sonoma, but there seems to be trouble with the CH340 kernel extension, as all I get is "NRF24-Adapter wait timeout".
Thanks for the explanation.
Here is the log file. I set the M905 to 10 Volts and connected a 25W 10 Ohms resistor.
This time I noticed the current (IOUT) value displayed in the application was exactly 2x of the value displayed on my P905. This happens only under load. If the current drops to zero on the P905, it will be reflected correctly in the application.
I will try to get the Python API running on Windows, too, and let you know when I have results.
Hi there. Awesome project!
I got it connected from my Thinkpad to my MDP-P905.
I noticed the reported output current in your application seems to be about 2x what is displayed on the power supply. Is this a calibration issue?