Jump to content

Winterfoot

Members
  • Posts

    18
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Winterfoot's Achievements

Apprentice

Apprentice (3/14)

  • Reacting Well Rare
  • Collaborator Rare
  • Dedicated Rare
  • First Post Rare
  • Conversation Starter Rare

Recent Badges

0

Reputation

  1. flow correction is still not on the available list. sorry missed this thread has a second page
  2. I'll do a deeper dive tomorrow, BUT it appears to be working perfectly now. Base pump speeds (30%) gives a N/A value (minimum detectable rate likely), but once I increase the speed it reports values that seem reasonable for what it is. 35-40% is around 20-30LPH, 100% speed lands around 150LPH.
  3. also kinda interesting, the flow correction disappeared after I set it back to one. I can't put it back
  4. so from the Bios we are at 65-66LPH (pretty sure it was LPH not LPM) @ 3300 Rpm pump speed. Idle at the desktop, with no corrective factor is 0.03 LPH @ 3300 Rpm (before adjusting with fan control
  5. So got the update in, and a quick check is now showing that the numeric behavior is working correctly (E.g. when pump rpm increases, the LPH increases). The reading is still not quite accurate i think as at rest we are at 0.5 LPH and at full RPM (4600) I'm getting approximately 2.5 LPH. I did check to see if the corrective factor from earlier is still in place (x60 due to MSI reading in LPM vs Aida's LPH) and it is still there. I think I should be seeing somewhere above 120LPH since the loop is fairly linear, without a lot of twists and turns to interrupt flow. Would this still be a corrective factor?
  6. so to create load, I was running Black Myth Wukong, Dead Space, and Dragon's dogma 2 simultaneously. I ran it for about 10 minutes before taking the reading, but the fluid temps never climbed too high, so the RPM is still pretty low. Let me know if you need a higher temperature reading for the load side, but this should give you a delta at least. isasensordump-idle 1700RPM.txt isasensordump-load 2200RPM.txt
  7. Interesting, is that a formula you can share, or is it under proprietary agreeement?
  8. Sure thing! I find it kind of fun doing stuff like this. Professionally I'm an engineer, but not in computer sciences. This is all learning for me. That would account for some of the discrepancy with the decimal value not quite matching the UEFI. I was making an assumption that the water pump increased in speed during boot. I'm going to put in the correct ratio value (60x) just so that portion is settled. We can worry about the value direction after. I do know that a lot of these flow units just report in RPM via means of a paddle wheel in the flow stream and a hall effect sensor, and then utilize a conversion calculation to turn it into flow rate, looks like the MSI UEFI does that automatically since I haven't had to enter in anything myself. I believe Aida64 has that capability? I vaguely recall reading a post that you can convert RPM to flow. That would help with the conversion, but not the proportional directionality of the value unfortunately. Not sure I understand that, unless it's a case of switched leads ( like how a three phase motor changes direction if you swap legs) but even then I don't think the pin-out on my flow meter supports that theory
  9. @Fiery did a little more digging. I think there are two separate issues occurring at the same time. So in the bios LPH reports as ~65.5LPh, and as soon as the system starts up about 0.69LPH, so I believe we are off as a factor of 100, which is easily resolved from the preferences menu and the correction factors. What is perplexing me is the secondary issue and I'm not sure how to resolve it from my side. That's the response of the sensor being inverse to what it should be. When the pump speed slows down (via control of a curve programmed in FanControl) the LPH will increase (even though an incorrect value), and when the pump increases in speed the LPH will decrease. Not sure what else I can look at, and searching the forums hasn't yielded anything yet.
  10. did a little playing with it. I am getting a flow reading, but it's off. First I thought it just needed a correction factor since the flow rate is ~0.8LPH with the pump speed at ~2800rpm. I changed the ratio in the settings first to 10, then to 100 since I thought that was just moving the decimal over and that would be good enough (setting aside questions of accuracy and calibration). That gave me a reading of about 80 LPH which seems reasonable for a system at rest. When I put the system under load though, the flow reading gave an inverse effect, dropping down to ~40LPH while the pump speed increased to ~4800RPM. So I think we are halfway there. Doing some googling to see if other people have had this issue before.
  11. Just made the upgrade, you're a genius! Totally works now! Thanks @Fiery! To do my part for the community, is there any testing you want me to do with this?
  12. So, clearly made some mistakes when I built my rig. I'm using an MSI Z690 Unify-X Mobo, and utilized two Corsair Commander Core XT Hubs to control 10 fans. I have the CC hooked onto the Mobo using a JUSB port instead of the JCORSAIR port, although I've been told explicitly by MSI this makes no difference and they do not support Corsair products. I cannot collect the fan RPM data in Aida 64, but it does show up in HWInfo64. I did manage to get away from the iCue software and now use FanControl along with the Aida64 and Corsair plugins, which allow me to see sensor data and fan RPM speed. This seems a positive step since iCue causes known conflicts with other programs; however, I still can't get the fan RPMs to show up on my Aida sensor panel. My thought process was to get rid of iCue, get another program reading and controlling the RPM data, then using Aida to share the info from the control program, but I can't seem to figure out that final step. Is there a way I can capture that RPM data on my sensor panel, or am I looking at swapping hubs, or doing direct connections (with splitters) to the MOBO so I can collect that data? Thanks in advance
  13. @Fieryawesome, thanks for the response! Hopefully msi comes up with something
×
×
  • Create New...