Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Power in/power out information #4

Open
realies opened this issue Dec 5, 2017 · 5 comments
Open

Power in/power out information #4

realies opened this issue Dec 5, 2017 · 5 comments

Comments

@realies
Copy link
Contributor

realies commented Dec 5, 2017

Corsair LINK provides realtime information on the PSU efficiency by having power in and power out readouts. Is it possible to include these in corsairmi or to share the knowledge on how to spoof the data?

Edit: Looking at the output from corsairmi and the LINK app, Corsair might be estimating efficiency by adding output0,1,2 wattage data and relating it to the total watts value. Not able to verify this.

image

@notaz
Copy link
Owner

notaz commented Dec 6, 2017

It's probably adding the outputs, yes. I remember searching exhaustively for all registers and there were no other outputs that looked like Watts.

@realies
Copy link
Contributor Author

realies commented Dec 7, 2017

Would it be sensible to include the sum of outputs and an efficiency value in the output of corsairmi?

Update: When polling corsairmi every 2 seconds, the sum of all output\d watts values would often exceed the total watts value, which in reality should not be possible. This might be due to non-synchronous polling from the PSU sensors or something else along the chain. Thoughts?

@notaz
Copy link
Owner

notaz commented Dec 17, 2017

Hmm not sure how to solve that, might have to do more reversing of windows tools to see how they do it. I don't have motivation for that though as I only need the "power in" reading.

@realies
Copy link
Contributor Author

realies commented Dec 17, 2017

I would be interested in doing so if you can point me in the right direction? :o)

@notaz
Copy link
Owner

notaz commented Dec 17, 2017

Well doing a detailed walkthrough would take more time that just doing it myself.

It goes like this: you start by installing a USB packet sniffer on windows (there are tons of them, can't remember which I used, it's been almost 2 years), then run windows tool that controls the device, start USB packet sniffing, do the operations you want with the tools, stop packet capture and look at the packets for commands that were sent to device.

For doing a disassembly, it's a very long story and if you never tried it, I wouldn't recommend going that way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants