Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11334

  • Joined

  • Last visited

  • Days Won

    476

 Content Type 

Everything posted by Fiery

  1. Fiery
    We've added them in the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta We couldn't add one of them though (MS_9003 / LFP_PanelName), since it's only a generic display that has no proper strings to identify it.
  2. Fiery
    Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works.
  3. Fiery
    Thank you! We've fixed it up in the latest AIDA64 beta update: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works.
  4. Fiery
    Thank you! We've fixed it up in the latest AIDA64 beta update: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works.
  5. Fiery
    Make sure to have the relevant TCP/IP port open on your firewall software (or Windows Defender Firewall) on your Windows PC.
  6. Fiery
    That should be the right DLL for Wallbraun v1 LCDs. I was just wondering whether you're using a v2 or v3 DLL for your v1 device, but it's not the issue. In this case however I have no idea what could be wrong Do you have another software that can handle your display? LCDHype perhaps?
  7. Fiery
    What video card(s) you've got?
  8. Fiery
    Thank you! My best guess is that you're using an incorrect DLL, one that's not designed for your variant of the Wallbraund LCD family. What's the file size of your LUIse.dll file? Is it 110,592 bytes?
  9. Fiery
    Yes, I'm afraid it's normal In Android 7.0 (for whatever reason) Google decided to block apps from accessing several system files that were previously readable. That includes the files apps would need to show thermal sensor readings. Battery temperature reading is still available fortunately.
  10. Fiery
    Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery
  11. Fiery
    Arx can be a bit tricky, but I'm glad you figured it out. We haven't checked GHub yet, but since it supports Arx (and many other standard Logitech API's and SDK's), it should work from out of the box. As for autostart order, I'm not sure what you mean. Can you please explain what would you like to achieve?
  12. Fiery
    I'm afraid for that you need to draw your own gauges at this time. I'm not sure what to do about the gauges, since there are quite a few high-res monitors out there and so we would have to come up with at least 3 new (and bigger) stages for each gauge which would inflate the number of gauges considerably -- as well as inflate the size of the AIDA64 distribution package...
  13. Fiery
    Locking only works by pixel position. So if you regularly change your monitors, it may be annoying having to readjust the SensorPanel position. Unless you make your SensorPanel monitor in a negative position (e.g. left to your main display as seen in the monitors layout in Windows Settings) in which case if you change your other monitors, the SensorPanel monitor should have the same negative pixel positions.
  14. Fiery
    Yes, it's possible. Safari can connect to the RemoteSensor module of AIDA64.
  15. Fiery
    If you run AIDA64 using the SYSTEM user, you may indeed run into such issues. I'm not sure however how to get around it. You may need to use an additional solution to enumerate those software.
  16. Fiery
    I cannot tell you that unless I know a bit more about the actual hardware interface and implementation. First of all, since you're planning to use a 800x480 colour display, the minimum amount of data to be transferred in each cycle would be 800x480x2 (16-bit colour depth) bytes, which is 750 KiloBytes. It means the protocol cannot be classic serial, since it would be too slow to update a frame. You would have to come up with a high-speed USB solution either via USB bulk transfer or HID. I'm not sure if connecting the Arduino is possible using such a high bandwidth USB connection. BTW, rather than reinventing the wheel, why don't you simply pick up a BeadaPanel? Same resolution colour screen than WF70A2SIAGDNN0:
  17. Fiery
    I'm afraid we have no skills in Arduino development, so I cannot help you about that
  18. Fiery
    I can there are 2 possible solutions to your issue/idea: 1) You can either implement an existing protocol on your side, which would mean emulating a protocol that already exists as an external LCD module in AIDA64. This would be the fastest way to get there, considering that it wouldn't require adjusting AIDA64 to make it happen. 2) Or, you can desing your own protocol, write a proper SDK or protocol spec, and we can add your protocol to the external LCD module of AIDA64 as a new protocol. Designing your protocol however would need to take into account what's possible to accomplish at the AIDA64 side, performance considerations, etc. If you can tell me more about your capabilities, the actual display type (pixel resolution? color depth?) and connection interface (USB? HID? connection performance? Serial-to-USB bridge? SPI-to-USB bridge?) you'd like to use, I will be able to provide you with more meaningful feedback.
  19. Fiery
    If anyone knows about the necessary API calls to dock a window onto to Windows Taskbar, please send me a private message
  20. Fiery
    Thank you! I've sent you a private message about this issue.
  21. Fiery
    I'm afraid we've never dealt with either the 64-bit aspects of the SDK or the .NET or C++ development side of it.
  22. Fiery
    BeadaPanel perhaps: https://forums.aida64.com/topic/5149-beadapanel-lcd-device-support/ Also, when it comes to external LCD displays, we keep recommending just picking up a nice 2nd-hand LCD monitor, connect it to your PC via DSub, DVI or HDMI, extend your Windows Desktop onto it, and then you can use the SensorPanel on a large colour display and enjoy the heck out of it
  23. Fiery
    Try to enable Corsair Link sensor support in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64 to apply the changes. Then go to the Computer / Sensor page to verify if the case fans appear there properly.
  24. Fiery
    Check this package: http://users.aida64.com/strike7_api_1_1.zip
  25. Fiery
    With laptops it's usually difficult to measure such values. But, we can try to figure out how it works if you could help us a little bit. Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery
×
×
  • Create New...