8000 Using recommended PyMonsoon fork returns huge values for current · Issue #10 · TQRG/physalia · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Using recommended PyMonsoon fork returns huge values for current #10
Open
@odmnk

Description

@odmnk

To install Physalia the GitHub installation section says to install this fork of PyMonsoon before running pip install physalia.

However, if I run Physalia using this version of the PyMonsoon library I get measurements that do not make sense. Profiling for 15 seconds gives me an average current of 27882.41 mA. Which is impossible.

If I instead use the original PyMonsoon library in combination with Physalia my average mA for a 15 seconds profiling session is 208.97 mA. This is acceptable.

The problem is that when I use the original PyMonsoon library I sometimes get the following error when using it with Physalia: msoon/PyMonsoon#35

My questions:

  1. Are these huge, unrealistic currents a known issue?
  2. Why the use of the fork is recommended instead of the original PyMonsoon library? The fork is around 90 commits behind upstream?
  3. If we install Physalia as instructed here it will install the original PyMonsoon library instead of the fork. Which one is preferred?

Thanks a lot!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0