PPK "Range not detected" error

[David]

I am using the PPK with SW v1.1.0 on a windows virtual machine on my mac. I'm testing custom hardware using the PPK regulator to supply power to my hardware.

There seem to be a few issues I'm running into:

1. The latency from power consumption events to graph changing seems very high. In particular if I turn my device on it might take 30 seconds to a minute before the graph updates to reasonable values. Same if I turn the device off.

2. After some amount of time (few minutes?) I see "range not detected" printed over and over in the console. Additionally the trigger window values appear to be completely unrealistic (more than 100 mA -- I expect max draw to be ~20 mA).

3. If I set the trigger to -- say 5000 uA -- and hit single it might take ~30 seconds to get the trigger even though the average window shows several spikes well above the trigger threshold.

Is the PC side buffer really large such that the latency is expected?

Is running on a VM not recommended?

I saw this question: devzone.nordicsemi.com/.../

It seems perhaps relevant, but I'm using default slider values.

[wlgrd]

There seems to be an issue with the logging thread working in the background, and a fix is in the works for this. Can you try opening ppk.py in a text editor and commenting out line plotter.start_log_thread() ? Since the PPK relies heavily on the SEGGER driver, I don't know how well that integrates/passes in to a virtual machine instance. If disabling the logger doesn't work, I would advise to try it natively. Also, a downgrade to PPK 1.0.0 could be a good test, to see if it is the update that breaks it.

[David]

Commenting out that line seems to have solved everything. Thank you for the help!

[Rasmus]

I have the same problem. I have tried to commenting out the plotter line, update Jlink driver but nothing helps. I just get the "Range out Detect error" message streaming through the Python console. My readings in the trigger window is spiking around 120 mA Which is 10 times more then what should be possible. I haven´t been aple to find a earlier version of the software (running v1.1.0) so i haven´t tried that. I also have all the latency problems as described. Is there a workaround comming?

[peabody124]

For what it's worth I got the PPK running natively on OSX. That logging code had to be commented out here, too.

github.com/.../master