Jump to content

Supported Hardware Model List (External LCD Displays)


Recommended Posts

Hi, I've seen the list of supported external LCD manufacturers at the bottom of the External Displays page.  However is there a device matrix that shows manufacturer, model, dimensions, interface, etc. of supported devices?  I've been searching each of the manufacturers manually, but am having a hard time finding a display that will meet my needs.

I'd like to mod an LCD\OLED display on the front of my Corsair Air 240 case, to display AIDA64 stats.  However it's a Mini-ITX and only has room for a 3.5"x 2" display, or a 3"x3" display:
corsair_air240.jpg
I'd like to stick to a USB display for ease.  Having a matrix of supported external devices would help narrow the list down. 

Also, I see that Adafruit displays are supported; is that a specific device or all?  Curious if this device works: https://www.adafruit.com/product/3315

Thanks!

 

Link to post
Share on other sites

The following document should help you:

http://download.aida64.com/resources/lcd/aida64_lcd_guide.pdf

As for the mentioned device, that is not supported by AIDA64 currently.  To me it looks like a SPI connected device, in which case you need to find a way to connect it to your computer at first.  Most likely you would want to connect the device to a USB port, using e.g. a FTDI FT232H bridge chip.

Link to post
Share on other sites
  • 2 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Similar Content

    • By Rich83
      hi all, newbie here! this is my first post so i hope it has landed in the correct place..  be gentle!

      i have installed the 'simple' version of a64, is it possible to run multiple instances of the sensor panel? i have the sensor panel running in a 5 inch screen located inside my case but have a room change planned which will put the case high on a shelf out of my eye sight so i would like a second display for stats placed under my main monitor. i plan to use a larger screen say a 10.1 'ultrawide (if thats the correct term) as i like the extra real-estate. what are my options?
      on a similar topic, is it possible to create an 'unpublished' senor panel before removing the currently used panel? or would i have to save the current panel to file or something then start a new panel?
      also can anyone point me to gauge resources, ie pre made gauges? or an easy to understand tutorial for how to diy them? total novice here, but can follow an idiots guide!

      i have included the final evolution of my first attempt using the provided gauges etc, it took me ages to get rid of the green dials.. i finally gave up trying to figure it out in a64 so i just changed the hue on the 5inch monitor lol. really hoping to learn the skills to create something like i have seen on here.. some really nice work on the share your panel thread, some of those must have taken ages!!! impressive. 
      any advice greatly received, but remember your talking to an a64 absolute novice!!
      Thanks folks. 




    • By -Vulture-
      Hey guys!
      Im hoping for some input regarding my question. I saw, AIDA64 is supporting a lot of different displays and interfaces. Now which one to choose? Heres some more input from me about what im looking for:
      [Mandatory] 5-8 inch LCD display [Mandatory] only USB powered [Mandatory] black frame design to match my case, if possible [Optional] A flat, not too thick one [Optional] small bezels if possible [Optional] No buttons neccessary, i want to place it inside of my case. [Optional] an internal USB connector to directly connect it to the motherboard At the moment im using some Aquacomputer Vision OLEDs which are working fine. But i can already see some burn in and they are pretty small. Since theres no LCD coming from Aquacomputer anytime soon, im thinking about using AIDA64 to get my data on screen. I have 3 of those OLED on each of the drive bay covers, this is more or less the space i have available
      I have attached a screenshot of the system with the OLEDs and their current placement for you to visualize.
       
      Thank you for your suggestions!


    • By Koithim
      Hey there,
      Installed the new card but i do not see all the sensors, like i did on my 2080 ti.
      Also, when the GPU is idle (low clock) the GPU Clock field on my sensor panel and LCD appear and disappear sometime. Also,
      app takes way longer to load.
      If any logs are needed just let me know.
      Cheers!
      K
       
    • By Renrut23
      Hey, new to Aida64 so be gentle,
      I have 2 Raspberry Pi 7" touchscreen display. One has a pi connected to it and the other is just the panel. The panel has just a usb port and a micro usb port. What's the easiest way to get this up and running as an external monitor? I've been running ModBros but I'm looking for something more customizable. 
       
      Also, other then the one forum post, is there anywhere to get templets to get a start from and build off of that?
    • By Irios
      After coming across this post on the AutoIt forums while researching how to access shared memory of processes in AutoIt, I decided to have a go at translating the Delphi example code.
      Below is a function w/ a working example showing how to access the AIDA64 shared memory.
      First enable shared memory here: Preferences > Hardware Monitoring > External Applications > Enable Shared Memory
      The length of the data depends on the number of active sensors and their content. As AIDA64 does not provide a buffer size value, we use _WinAPI_GetSystemInfo() <WinAPISys.au3> to get dwPageSize ($aArray[1]). This value is then used as an address offset, and we continue reading chunks of data until we encounter a 0x00 NUL character.
      Based on the Delphi example found in the AIDA64 documentation: https://www.aida64.co.uk/user-manual/external-applications
      Feedback appreciated, especially as all this shared memory stuff is not my ordinary cup of... cake. And regarding this whole ordeal of reading data without knowing the exact length; I'm suspecting my solution to read chunks of data like done below is not by the book, and I'm concerned what might happen if the final chunk is exactly 4096 bytes in length. Will there still be a NUL terminator there? Hmm.
       
      #NoTrayIcon #include <WinAPIFiles.au3> #include <WinAPISys.au3> ; #INDEX# =========================================================================================================================== ; Title .........: AIDA64 Shared Memory access for AutoIt3 ; Author(s) .....: demux4555 ; Reference .....: https://www.aida64.co.uk/user-manual/external-applications ; =================================================================================================================================== Global $vSharedmem_data ; The variable used to store the data we read from the shared memory Global $return = ExtApp_SharedMem_ReadBuffer_v2($vSharedmem_data) ; Now, let's see what happens when we run the function... If @error Then _Echo("! ExtApp_SharedMem_ReadBuffer_v2(): @errror = " & @error) If IsBinary($vSharedmem_data) Then ; Convert type Binary to actual human readable text. We also remove the excess of trailing 0x00 characters. $vSharedmem_data = StringStripWS(BinaryToString($vSharedmem_data), $STR_STRIPLEADING+$STR_STRIPTRAILING) EndIf _Echo() _Echo("> return = " & $return) ; The return value. Will be True if everything went ok. _Echo("> length = " & StringLen($vSharedmem_data)) ; The number of characters read from shared memory. _Echo("> data = " & $vSharedmem_data) ; The actual data. _Echo("> data(40) = " & "..." & StringRight($vSharedmem_data, 40)) ; shows the 40 right-most characters, and _should_ show the very end of the data at this point. _Echo() Exit ; #FUNCTION# ==================================================================================================================== ; Name ..........: ExtApp_SharedMem_ReadBuffer_v2 ; Description ...: AIDA64 Shared Memory Example for AutoIt3 ; Syntax ........: ExtApp_SharedMem_ReadBuffer_v2(Byref $_dOutput[, $_sSharedmemName = "AIDA64_SensorValues"]) ; Parameters ....: $_dOutput - [in/out] Variable to store the read data. ; $_sSharedmemName - [optional] Name of the AIDA64 shared memory. Default is "AIDA64_SensorValues". ; Return values .: Success: True. $_dOutput will be type Binary, containing a string of the XML values of the active sensors. ; Failure: False. ; Author ........: demux4555 ; Reference .....: https://www.aida64.co.uk/user-manual/external-applications ; =============================================================================================================================== Func ExtApp_SharedMem_ReadBuffer_v2(ByRef $_dOutput, $_sSharedmemName = "AIDA64_SensorValues") Local $_bReturn = False Local $_aGSI = _WinAPI_GetSystemInfo() ; Retrieves information about the current system... Ref: https://docs.microsoft.com/en-us/windows/win32/api/sysinfoapi/nf-sysinfoapi-getsysteminfo Local $_iPageSize = $_aGSI[1] ; ... the page size and the granularity of page protection and commitment. Usually it is 4096, but we read it anyway. Ref: https://docs.microsoft.com/en-us/windows/win32/api/sysinfoapi/ns-sysinfoapi-system_info Local $_hMapping = _WinAPI_OpenFileMapping($_sSharedmemName, $FILE_MAP_READ) ; Opens a named file mapping object. Ref: https://docs.microsoft.com/en-us/windows/win32/api/memoryapi/nf-memoryapi-openfilemappingw If Not IsPtr($_hMapping) Then Return SetError(-2, 0, $_bReturn) Local $_pMappedData = _WinAPI_MapViewOfFile($_hMapping, 0, 0, $FILE_MAP_READ) ; Pointer to the start address. Maps a view of a file mapping into the address space of a calling process. Ref: https://docs.microsoft.com/en-us/windows/win32/api/memoryapi/nf-memoryapi-mapviewoffile If @error Or Not IsPtr($_pMappedData) Then Return SetError(-2, 0, $_bReturn) ; Now we loop until we reach the end of the data. Local $_tData, $_dBuffer While 1 $_tData = DllStructCreate("BYTE[" & $_iPageSize & "]", $_pMappedData) ; Note: we use type BYTE[] (AutoIt type Binary) instead of CHAR[] (AutoIt type String). This allows us to look for value 0x00 (NUL termination of the data). If @error Then ExitLoop $_dBuffer = DllStructGetData($_tData, 1) ; The returned value is type Binary. If @error Or ($_dBuffer==0) Or (BinaryLen($_dBuffer)=0) Then ExitLoop ; Pretty sure $_dBuffer==0 can not happen, so just in case. $_dOutput = Binary($_dOutput & $_dBuffer) ; Add the read data to the end of the output variable. If StringRight($_dBuffer, 2)=="00" Then ExitLoop ; Look for NUL termination of the string data. $_pMappedData += $_iPageSize ; We change the address by using the page granularity value (i.e. 4096) as the offset. WEnd ; Quick cleanup $_bReturn = _WinAPI_UnmapViewOfFile($_pMappedData)=1 ; Unmaps a mapped view of a file from the calling process's address space. Ref: https://docs.microsoft.com/en-us/windows/win32/api/memoryapi/nf-memoryapi-unmapviewoffile _WinAPI_CloseHandle($_hMapping) Return $_bReturn EndFunc; Func _Echo($_data = "") ConsoleWrite($_data & @CRLF) EndFunc  
×
×
  • Create New...