Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12405

  • Joined

  • Last visited

  • Days Won

    550

 Content Type 

Everything posted by Fiery

  1. Fiery
    ER-OLEDM032 is a graphical (dot matrix) display that can display any kind of graphics. With such displays you have way more flexibility than with alphanumeric (character) displays that can only display pre-defined or custom characters.
  2. Fiery
    We've found a way to get around the slow serial connection issue about GTT displays, and implemented support for USB-connected GTT devices in the latest AIDA64 beta update:
  3. Fiery
    We've added support for Matrix Orbital GTT color graphical LCD displays. The only connection method currently supported is USB. You can enable the LCD device from AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / Matrix Orbital GTT. You need to have the appropriate Matrix Orbital USB LCD drivers installed, and the LCD to be connected to a USB port. Note: GTT displays implement a slow serial connection which makes frame updates a bit sluggish. You can find the new AIDA64 beta update at: https://www.aida64.com/downloads/latesta64xebeta Please let us know if you find any difficulties enabling or using this new feature. Also let us know if you've got another kind of LCD device that is currently unsupported by AIDA64. Regards, Fiery
  4. Fiery
    We've implemented the requested feature in 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. You can specify the URL or executable file that you want to put on your images as a clickable link in the LCD item / Image property dialog as "URL" parameter.
  5. Fiery
    Thank you. Please 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.
  6. Fiery
    It would be a terribly "user-unfriendly" option, since then cca. a hundred fans would appear with zero RPM for all of them
  7. Fiery
    Once it shows up in the BIOS, it should appear in AIDA64 as well.
  8. Fiery
    DIMM slot numbering depends on the actual motherboard. Many motherboards have them mixed up. It's only a minor cosmetic issue that doesn't need a fix.
  9. Fiery
    AIDA64 doesn't support custom characters for external LCD displays.
  10. Fiery
    Thank you for posting this here. I don't think it's related to Corsair Link. But, he can disable Corsair AXi sensor support, Corsair HXi/RMi sensor support, Corsair Link sensor support in AIDA64 / main menu / File / Preferences / Stability, and try running the GPU stress test again.
  11. Fiery
    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
  12. Fiery
    It isn't compatible, but it's mostly because AFAIK it's not possible to write a generic communication protocol for LCD displays that are connected to a PC USB port via Arduino. However, it should be possible to write an Arduino program (sketch) to emulate an existing LCD protocol to make the Arduino+LCD combo compatible with an existing AIDA64 LCD module.
  13. Fiery
    Your temperatures look normal.
  14. Fiery
    If you want to use the reports for network audit or change tracking purposes, using AIDA64 Business' own modules (Audit Manager and Change Manager), then you don't need to include the Motherboard / ACPI page in your reports in order for the mentioned features to work properly.
  15. Fiery
    Is it possible to somehow stream the bitmap data from a TCP/IP port (of the WiFi layer) into the display? Also, here are 2 projects that may be helpful for you: https://diyprojects.io/esp8266-web-client-sending-data-jeedom-tcp-ip-wireless-json-api/ https://www.dfrobot.com/blog-782.html
  16. Fiery
    Thank you. Strangely, the register that is supposed to hold the W_PUMP+ reading is zero on your system. Can you see the W_PUMP+ reading in the BIOS Setup?
  17. Fiery
    I think you can use VBScript for such purposes. I haven't tried it yet though...
  18. Fiery
    I have no idea where that message comes from No, we don't have a removal tool, since in 99% of the cases it's not necessary to do anything other than using the uninstall tool.
  19. Fiery
    We've ordered a sample of that display, and will implement support for it as soon as it arrives. I'll let you know in this topic when we have a new AIDA64 beta build that you can test on the RoboPeak display.
  20. Fiery
    It means your system no longer has the AIDA64 kernel driver present.
  21. Fiery
    Thank you, but that dump doesn't include EC registers. Please enable status bar in AIDA64 / main menu / View, and on the status bar (which will appear on the bottom of the AIDA64 main window) do a right-click --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post.
  22. Fiery
    Samsung SPF devices are not LCD monitors, but digital picture frames. They simply have an additional feature (mini-monitor mode) that puts them ahead of their competitors. But they're still not intended to be used as a regular PC monitor.
  23. Fiery
    AIDA64 uses its own hardware database to report cache buffer size for SSDs. So the value is not detected at all, and may involve inaccuracies if the original database entry was incorrectly inserted. We'll fix it up in the next AIDA64 beta build. Your SSD is fine, don't worry about it. And don't alert Crucial either, since it's not their fault
  24. Fiery
    No things to worry there. Charge counter is reported with good, acceptable or poor accuracy by many devices. If it doesn't align with your expectations, then the value reported is most likely inaccurate or bogus. You can verify whether AIDA64 reports the proper value (as it is provided by the standard Android Battery API), you can compare the values against the ones reported by Ampere or HWMonitor.
  25. Fiery
    I don't think you can automate that
×
×
  • Create New...