Jump to content
  • Forum Statistics

    7,465
    Total Topics
    40,754
    Total Posts
  • Member Statistics

    47,735
    Total Members
    16,800
    Most Online
    TammyAFoster
    Newest Member
    TammyAFoster
    Joined

Teszty66

Members
  • Content Count

    72
  • Joined

  • Last visited

  • Days Won

    8

Everything posted by Teszty66

  1. LOL, well the pumps might be different but mine runs at 3000RPM on average load. And I think about 1500-1800 on idle. Also mine is setup differently, I have a dedicated pump port on my motherboard and Ive set the PWM curve to be always 100%, so it always gets full voltage, and then the RPM is controlled by the software/the pump itself based on temperature. Maybe it was not getting enough voltage on your previous BIOS settings and it was starting and stopping.
  2. Well, I dont know then. IMO it should not be doing that. Maybe the pump provides the wrong RPM values, or maybe HWMonitor is reading it wrong, or maybe the motherboard is providing the wrong value. There is a lot of stuff that could be wrong but it seems its just a problem with the values, if you dont feel the pump stopping and starting then the pump is fine. But for example my AIO spins the pump up and down depending on the load. If yours does not do that, your motherboard might not be controlling the pump correctly, or its by design and the pump always runs at static RPM. But that would be #### design from TT. You could read on how to connect AIO pump to your motherboard and how to setup PWM speed control in BIOS.
  3. Hmm how about service stopped and official software running? I dont think it should be doing that.
  4. That might just be the way the controller is programmed, since you cant pass to the controller how many leds a device has, so I think it also assumes 12 leds per device. Thats why I said to try with the full black, maybe it detects the black as limit for leds. Hmm that sounds like it does not set the speed then. Unfortunately the old app only sets the speed by percent. The RPM going to 0 and back might be a conflict with another software, at least this is what was happening to RPM of my fans when I had the service and the official app running, they were both writing to the controller and it was freaking out. If the fans also see this behavior check if the official software is running. Aida64 added support for TT fans some time ago and it also causes this issue. Ooh I see, so the pump is also connected to the PWM of the motherboard. I guess that means you can only configure rgb on the AIO and the pump is controlled by the motherboard speed controller. But that does not explain why it goes to 0 RPM. Does it also happen when you stop the service? Maybe you can control the speed but the TT controller and the motherboard controller are interfering with each other. Dont know if I will be making a GUI for the new one since its a lot more complex. And you should check github if you want updates about the new version, I wont be posting about it here. Yes they should work fine. Although they have 9 leds and the software assumes 12 leds so some rgb modes might behave weird.
  5. @Zeonymous Wow yea antivirus be like that sometimes. Glad you figured it out. Im also using PIN and never had to disable it, so I dont know whats up with that, probably also the av. You could try changing the install to custom user/LocalService depending on which one you use now. And about the AIO, if I understand correctly you are saying that the AIO has 6 leds but the fans have 12, so the rgb modes are not displaying correctly, right? Yes, that is the limitation of the old version of the software, because when I was writing it I thought only fans would be supported. Now I know that all TT RGB Plus devices use the same commands to control the speed/rgb, so while the rgb will work on all devices, it thinks all of them have 12 leds. Although I think you could try setting the last 6 led colors to full black (RGB 0,0,0), maybe this will trick the controller. Also please note that I have not tested any pumps, so I dont know if the command that is sent to the controller is the correct one. Try setting the speed to manual and changing it from 20% to 100% and see if it makes a difference in sound/vibration etc. There are 2 commands, one sets speed by percent and one that sets speed by RPM. The pumps might use the second one. The new version on github allows you to specify how many leds are on each connected device, and a lot more features. But it might be hard to configure right now because it does not have GUI.
  6. First release of the new app added on github if you dont want to compile yourself.
  7. They new one has no gui yet. I dont know if I will make one because I added a lot of features that will make gui very complex. But I will see. You can download the old one in the first post. It works fine and has gui, but the code got a little messy from features some people requested.
  8. Initial code for the new version posted on github if anyone wants to compile it.
  9. Yea try v1.7, it has no port detection that seems wonky on some setups. I will try disconnecting my pc from power and see if this will reproduce the issue. The new app also has no port detection, you configure each port manually by setting its name/led count/led rotation/led reverse and other stuff. Also at first the service will have no gui, only json file config.
  10. Small demo from the new app using custom effect featuring fan led offset/rotation and led reversing: Effect is configurable from json file: "RgbEffect": "SnakeEffect", "RgbEffectConfig": { "Length": 5, "SnakeColor": [219, 78, 78], "BackgroundColor": [16, 16, 16] }
  11. Yup, totally doable but requires manually setting the leds from software, there is no support for it in the firmware so you just cant change the currently available effects. Unless of course they update the firmware. Once I rewrite the app you will be able to do anything you want with custom effects. Im actually thinking about abandoning future updates to the current version and just start writing the new one. The hacks are getting ridiculous.
  12. You mean RGB direction or the fan spin direction? Either way I can only add what the controller firmware supports.
  13. Yea, but the thing is before v1.7 the service was detecting the fans by its RPM so it shouldn't matter if your fans were at 20% or 30%. I guess it might not return correct values if its 20%? But that seems weird. In v1.7 I removed the empty port check and just added all ports no matter what, and they still have some fans missing. And there is literally no reason they should be missing. It seems that testing software only on one PC is a bad idea lol. It works just fine on my PC when shutting down, going to sleep or hibernating. You can try going services.msc and stopping the service manually. It should switch to shutdown mode. I think I should add heavy logging to help debug all of these problems people are having. It must be just hardware differences. Hmm, yea good idea, Ill see what can be done.
  14. Nah, this has to be fixed. But im running out of ideas as ty why it does not show all the fans. Clearly it was not a problem with empty port detection. It might be because of the LocalService, maybe it starts earlier than user service and that causes issues?
  15. Thanks! If you need help with something feel free to post here. Ok, if this happens more, please try to reinstall the service as custom user. Maybe that is the issue because I have mine running as custom user. If that doesnt help I guess its just the controller firmware is as bad as their windows app. As for other rgb modes, currently I do not plan to add them to this version of the software, they will be in the rewrite if I decide to do it. The reason is that the currently supported modes are in the controller firmware, meaning I just send it a command to set specific fan to a specific mode only when you click the save button or when the service loads. Any other mode that is in the official app is done by constantly manually setting the leds. That would mean a big rewrite of the app to change from updating the rgb mode "one time" vs "realtime". Nice, im glad its working. BTW, if you still have v1.6 and you run as LocalService, do you mind testing if installing as custom user will still sometimes not show all fans?
  16. @Ghosty031@ZOOTS I do not understand why it would do that... I never had that happen. Do you guys install the service as LocalService or custom user? I assume you are sure you are not also running the official software? Also the recent updates to Aida64 added riing fan support and it breaks the service. The delayed start could help but it delays for 2 minutes, so thats no good. I guess I'll just disable the empty port check. It will show all ports all the time, kinda like official software, this should also enable rgb support for aio pump. edit: Added v1.7
  17. I dont have the pump to test but I'll try to make this work. Can you run the attached app and PM me the output? But make sure you stop the service first. I think what is happening is that the pump does not report its speed/rpm so the service thinks the port is not used. The solution will be to add config to disable this check for selected ports. tt_info.zip
  18. Oh thats weird, maybe it thinks the app is not supported, Ill read up on that. Thanks for reporting.
  19. Duh, sorry I compiled with debug config, so you would need debug version of vc++ redist. I recompiled as release, please try again. Thanks.
  20. Yea, its basically the default speed (only static %) and rgb mode the fans will run with without any controlling software. It is saved to the controller box. Well, depends on your setup, but you could just have one BOOT profile with all fans in it. It will switch each fan to the assigned NORMAL mode when the service starts. You shouldn't have to save BOOT then save NORMAL. When you are saving BOOT profiles the service sets that profile for a brief moment then notifies the controller box to save that settings internally. Once its saved it will revert to the NORMAL profile for each fan if available. If it doesn't do that, it means there is a bug. BTW I noticed that you controller version is displayed incorrectly. Do you mind running the attached program? It will dump some data about the controller and what stuff it returns. Make sure the service is not running first, then PM me the output. Thanks.
  21. Yea, there was a bug when setting the fan to 0% speed, thanks. Try v1.6. BTW there is no in between speeds from 0% to 20%, so you can either have the fan at 0% or at 20%. Looking at your PWM graph, the most left and right points are not necessary, they are automatically included, and you can remove/add points by double clicking. So it could be done with just 2 points. I would want to inform you that you need to be careful when setting the curve with 0% speed. If you set it wrong your fan will constantly spin up and down (fan on -> low temperature -> fan off -> high temperature -> fan on -> ...), that might heavily lower the lifespan.
  22. There is brightness control. You can set it using the third slider, using the "B" input box, using the hex input box (for example #808080 is white with 50% brightness) or by using the saturation/brightness box (Y axis is brightness).
  23. @visualarts Try v1.5 for multiple temperature sensor mixing.
  24. I pm'd you the debug version of the service.
  25. Thats interesting, Ill test that. Thats even more interesting. If you click on the fan, does it update the speed and rpm in the stats section correctly? Or does it sometimes show all 0 values? I assume you are not running the official software at the same time? Make sure it does not autostart with windows. Also, are you running any hardware monitoring software like aida? I know that new aida added support for riing fans, but it screws with my app and I assume with official one too. Try, v1.4 there was a bug in detecting empty ports, which could explain long startup and missing fans. If this will not work Ill send you a debug version with more logging and will see.
×
×
  • Create New...