Keep Power Profiler powered up when not communcating

[Decee1]

Hello,
I got a Python based test setup where i use a Power Profiler as power supply for my testing.

When i stop communicating with the power profiler it turns off the power supply which is really inconvenient.
Is there a way to fix this?

To be more accurate.
When i stop communicating for some time and not releasing the device(still attached using pyserial) it resets the device which causing the output to be turned off.

What i want is ideally for the device to not reset when the serial communication is stopped/PowerProfiler software is closed 

Best regards,
Stefan

[Sigurd Hellesvik]

Hi

Assuming you are using the PPK2 with https://github.com/IRNAS/ppk2-api-python, use:

ppk2_test.toggle_DUT_power("ON")

ref example.py#L37

Regards,
Sigurd Hellesvik

[Decee1]

Hello,
I am already using this library.
but in my case the power supply turns off and resets(voltage is 0.8V when opening SW) by itself after some time being inactive or you close the communication.

[Sigurd Hellesvik]

Ah, I see your issue.

The PPK2 firmware does only supply power if a serial connection is upheld.

I will ask our developers if there is any way to fix this. I hope to get you an answer by end of tomorrow.

Regards,
Sigurd Hellesvik

[Sigurd Hellesvik]

Hello

I still have gotten no answer from our developers.

I hope they answer me early next week.

Regards,
Sigurd Hellesvik

[Decee1]

Hello.
Thanks for the update, sorry for not replying.
I've figured out that it was not my device that timed out so for my testing this will work.
I still would highly prefer being able to keep the power supply powered opon closing the Software/serial port for debugging but it is not as high a priority as it was when i thought the device timed out and reset

Works really well for my test setup until now! 

[Sigurd Hellesvik]

Hi

I found the guy who wrote the firmware for the PPK2.

The PPK2 does not have functionality for remembering DUT state after Serial disconnect.

This have been added to the list of things to be done, but we can not give a time estimate on when it will be added as functionality.

Good to hear that you are able to figure out some way to do it better in the meantime!

Regards,
Sigurd Hellesvik