Jump to content
AIDA64 Discussion Forum
Fiery

New LCD device support: Samsung SPF Digital Photo Frames

Recommended Posts

about the

right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB Dump. Copy-paste the full results into this topic.

the problem is that under windows 10 there is no bottom bar anymore in aida64 ^^

I know :) You can still enable it from main menu / View ;) Or, you can press Ctrl+D on the main window to get to the debug menu.

Edit: Thank you for the data. Rough calculations say the JPEG image size limit is 256 KB on your SPF-83H device. We'll add that to the next AIDA64 beta update that is rolled out in a few hours from now. After upgrading to that, make sure to deactivate random image mode via the AIDA64.INI file, and feel free to set the JPEG compression quality to 99. The image size limiter should be able to calibrate the right file size on-the-fly.

Share this post


Link to post
Share on other sites

We've implemented automatic JPEG image size limiter for SPF-83H and SPF-105P devices in the following new beta update to AIDA64 Extreme:

http://www.aida64.com/downloads/latesta64xebeta

We've set the following limits so far:

- 800P/800PE [04E8-2038] (our own device): < no need to limit JPEG size >

- SPF-75H [04E8-200F] (our own device): 400 KB

- SPF-83H [04E8-200D] (Xixou): 256 KB

- SPF-105P [04E8-201B] (Spaljeni): 500 KB

- SPF-107H [04E8-2036] (Mrshilov): 604 KB

There's a slim chance those limits are still a bit higher than the actual limit used by the SPF firmware, so please let us know if you still experience image corruption or device disconnection issues while using the latest AIDA64 beta.

Share this post


Link to post
Share on other sites

It froze at 99%, did not really time after how long (maybe an hour, maybe less)

So I set the compression to 90% and it is working so far.

Using the latest Beta update ofcourse.

Share this post


Link to post
Share on other sites

I know :) You can still enable it from main menu / View ;) Or, you can press Ctrl+D on the main window to get to the debug menu.

Edit: Thank you for the data. Rough calculations say the JPEG image size limit is 256 KB on your SPF-83H device. We'll add that to the next AIDA64 beta update that is rolled out in a few hours from now. After upgrading to that, make sure to deactivate random image mode via the AIDA64.INI file, and feel free to set the JPEG compression quality to 99. The image size limiter should be able to calibrate the right file size on-the-fly.

Indeed this gives me this:

 

------[ Samsung SPF-83H Digital Photo Frame]------
 
Device Description   : Samsung SPF-83H Digital Photo Frame
Device ID            : 04E8-200D
Device Class         : FF / 00
Device Protocol      : 00
Manufacturer         : SAMSUNG
Product              : SAMSUNG Digital Photo Frame
Serial Number        : MP612B
Supported USB Version: 2.00
Current Speed        : High  (USB 2.0)
 
 
I will also try 90%.
 
The aida64 GUI was terribly slow before, with this change it is much faster for some reason.

Share this post


Link to post
Share on other sites

Hi, this time lcd did not start on windows 10 starup.

I saw in the usb dump that the lcd descriptor is incorrect, so bad usb enumeration that explains why lcd is black:

 

------[ Périphérique USB inconnu (échec de demande de descripteur de périphérique)]------
 
Device Description   : Périphérique USB inconnu (échec de demande de descripteur de périphérique)
Device ID            : 0000-0000
Device Class         : 00 / 00
Device Protocol      : 00
Supported USB Version: 0.00
Current Speed        : High  (USB 2.0)
 
 
Nothing aida64 can do about it, crap lcd frame.
 
 
 
Below the entire dump:
 
------[ AIDA64 Extreme v5.30.3516 Beta ]------
 
------[ Microsoft Windows 10 Home Single Language 10.0.10240.16430 (64-bit) ]------
 
------[ Motherboard Info ]------
 
Motherboard ID      : 63-0100-000001-00101111-010914-Chipset$0AAAA000_BIOS DATE: 05/15/15 09:49:33 VER: 05.06.05
Motherboard Model   : Asus X99-Deluxe
Motherboard Chipset : Intel Wellsburg X99, Intel Haswell-E
 
DMI MB Manufacturer : ASUSTeK COMPUTER INC.
DMI MB Product      : X99-DELUXE
DMI MB Version      : Rev 1.xx
DMI MB Serial       : 140830274200341
DMI SYS Manufacturer: ASUS
DMI SYS Product     : All Series
DMI SYS Version     : System Version
DMI SYS Serial      : System Serial Number
DMI BIOS Version    : 1801
 
------[ USB Devices ]------
 
Contrôleur hôte Intel® USB 3.0 eXtensible - 1.0 (Microsoft)
- [Port 1] < No Device Connected >
- [Port 2] < No Device Connected >
- [Port 3] < No Device Connected >
- [Port 4] < No Device Connected >
- [Port 5] < No Device Connected >
- [Port 6] Bluetooth USB module
- - Énumérateur Microsoft Bluetooth LE
- - Énumérateur Microsoft Bluetooth
- - - Bluetooth L2CAP Interface
- - - Audio Bluetooth
- - Bluetooth Device (Personal Area Network)
- - Bluetooth Device (RFCOMM Protocol TDI)
- [Port 7] < No Device Connected >
- [Port 8] < No Device Connected >
- [Port 9] Concentrateur USB générique
- - [Port 1] < No Device Connected >
- - [Port 2] Concentrateur USB générique
- - - [Port 1] < No Device Connected >
- - - [Port 2] < No Device Connected >
- - - [Port 3] < No Device Connected >
- - - [Port 4] < No Device Connected >
- - [Port 3] < No Device Connected >
- - [Port 4] < No Device Connected >
- [Port 10] Concentrateur USB générique (ASM107x)
- - [Port 1] < No Device Connected >
- - [Port 2] Périphérique USB composite (USB Keyboard)
- - - Périphérique d’entrée USB
- - - - Périphérique clavier PIH
- - - Périphérique d’entrée USB
- - - - Contrôleur système HID
- - - - Périphérique de contrôle consommateur conforme aux Périphériques d'interface utilisateur (HID)
- - [Port 3] Eaton UPS 0463-L (Ellipse PRO)
- - [Port 4] Périphérique USB inconnu (échec de demande de descripteur de périphérique)
- [Port 11] Périphérique USB composite (2.4G Wireless Device)
- - Périphérique d’entrée USB
- - - Périphérique clavier PIH
- - Périphérique d’entrée USB
- - - Contrôleur système HID
- - - Périphérique de contrôle consommateur conforme aux Périphériques d'interface utilisateur (HID)
- - - Périphérique fournisseur HID
- - - Périphérique fournisseur HID
- - - Souris HID
- [Port 12] < No Device Connected >
- [Port 13] < No Device Connected >
- [Port 14] < No Device Connected >
- [Port 15] < No Device Connected >
- [Port 16] < No Device Connected >
- [Port 17] < No Device Connected >
- [Port 18] < No Device Connected >
- [Port 19] < No Device Connected >
- [Port 20] Concentrateur USB SuperSpeed générique
- - [Port 1] < No Device Connected >
- - [Port 2] < No Device Connected >
- - [Port 3] < No Device Connected >
- - [Port 4] < No Device Connected >
- [Port 21] Concentrateur USB SuperSpeed générique
- - [Port 1] < No Device Connected >
- - [Port 2] < No Device Connected >
- - [Port 3] < No Device Connected >
- - [Port 4] < No Device Connected >
Intel® C610 series/X99 chipset USB Enhanced Host Controller #2 - 8D2D
- [Port 1] Generic USB Hub
- - [Port 1] < No Device Connected >
- - [Port 2] < No Device Connected >
- - [Port 3] < No Device Connected >
- - [Port 4] < No Device Connected >
- - [Port 5] < No Device Connected >
- - [Port 6] < No Device Connected >
- [Port 2] < No Device Connected >
Intel® C610 series/X99 chipset USB Enhanced Host Controller #1 - 8D26
- [Port 1] Generic USB Hub
- - [Port 1] < No Device Connected >
- - [Port 2] < No Device Connected >
- - [Port 3] < No Device Connected >
- - [Port 4] < No Device Connected >
- - [Port 5] < No Device Connected >
- - [Port 6] < No Device Connected >
- - [Port 7] < No Device Connected >
- - [Port 8] < No Device Connected >
- [Port 2] < No Device Connected >
Contrôleur hôte ASMedia USB 3.0 eXtensible - 1.0 (Microsoft)
- [Port 1] < No Device Connected >
- [Port 2] < No Device Connected >
- [Port 3] < No Device Connected >
- [Port 4] Périphérique USB composite (Skullcandy GMX Dolby Transmitter)
- - Skullcandy GMX Dolby Transmitter
- - - Haut-parleurs (Skullcandy GMX Dolby Transmitter)
- - - Microphone (Skullcandy GMX Dolby Transmitter)
- - Périphérique d’entrée USB
- - - Périphérique de contrôle consommateur conforme aux Périphériques d'interface utilisateur (HID)
- - - Périphérique fournisseur HID
 
------[ Bluetooth USB module]------
 
Device Description   : Bluetooth USB module
Device ID            : 0B05-180A
Device Class         : FF / 01
Device Protocol      : 01
Supported USB Version: 2.00
Current Speed        : Full  (USB 1.1)
 
------[ Concentrateur USB générique]------
 
Device Description   : Concentrateur USB générique
Device ID            : 174C-2074
Device Class         : 09 / 00 (Hi-Speed Hub with multiple TTs)
Device Protocol      : 02
Supported USB Version: 2.10
Current Speed        : High  (USB 2.0)
 
------[ Concentrateur USB générique]------
 
Device Description   : Concentrateur USB générique
Device ID            : 05E3-0608
Device Class         : 09 / 00 (Hi-Speed Hub with single TT)
Device Protocol      : 01
Supported USB Version: 2.00
Current Speed        : High  (USB 2.0)
 
------[ Concentrateur USB générique]------
 
Device Description   : Concentrateur USB générique
Device ID            : 174C-2074
Device Class         : 09 / 00 (Hi-Speed Hub with multiple TTs)
Device Protocol      : 02
Manufacturer         : ASUS TEK.
Product              : ASM107x
Supported USB Version: 2.10
Current Speed        : High  (USB 2.0)
 
------[ Périphérique USB composite]------
 
Device Description   : Périphérique USB composite
Device ID            : 1C4F-0024
Device Class         : 03 / 01 (Human Interface Device)
Device Protocol      : 01
Manufacturer         : SIGMACHIP
Product              : USB Keyboard
Supported USB Version: 1.10
Current Speed        : Low  (USB 1.1)
 
------[ Eaton UPS 0463-L]------
 
Device Description   : Eaton UPS 0463-L
Device ID            : 0463-FFFF
Device Class         : 03 / 00 (Human Interface Device)
Device Protocol      : 00
Manufacturer         : EATON
Product              : Ellipse PRO
Serial Number        : G360F18144
Supported USB Version: 1.10
Current Speed        : Low  (USB 1.1)
 
------[ Périphérique USB inconnu (échec de demande de descripteur de périphérique)]------
 
Device Description   : Périphérique USB inconnu (échec de demande de descripteur de périphérique)
Device ID            : 0000-0000
Device Class         : 00 / 00
Device Protocol      : 00
Supported USB Version: 0.00
Current Speed        : High  (USB 2.0)
 
------[ Périphérique USB composite]------
 
Device Description   : Périphérique USB composite
Device ID            : 25A7-2433
Device Class         : 03 / 01 (Human Interface Device)
Device Protocol      : 01
Manufacturer         : 2.4G
Product              : 2.4G Wireless Device
Supported USB Version: 1.10
Current Speed        : Full  (USB 1.1)
 
------[ Concentrateur USB SuperSpeed générique]------
 
Device Description   : Concentrateur USB SuperSpeed générique
Device ID            : 174C-3074
Device Class         : 09 / 00 (Hub)
Device Protocol      : 03
Supported USB Version: 3.00
Current Speed        : Super  (USB 3.0)
 
------[ Concentrateur USB SuperSpeed générique]------
 
Device Description   : Concentrateur USB SuperSpeed générique
Device ID            : 174C-3074
Device Class         : 09 / 00 (Hub)
Device Protocol      : 03
Supported USB Version: 3.00
Current Speed        : Super  (USB 3.0)
 
------[ Generic USB Hub]------
 
Device Description   : Generic USB Hub
Device ID            : 8087-800A
Device Class         : 09 / 00 (Hi-Speed Hub with single TT)
Device Protocol      : 01
Supported USB Version: 2.00
Current Speed        : High  (USB 2.0)
 
------[ Generic USB Hub]------
 
Device Description   : Generic USB Hub
Device ID            : 8087-8002
Device Class         : 09 / 00 (Hi-Speed Hub with single TT)
Device Protocol      : 01
Supported USB Version: 2.00
Current Speed        : High  (USB 2.0)
 
------[ Périphérique USB composite]------
 
Device Description   : Périphérique USB composite
Device ID            : 9886-0004
Device Class         : 01 / 01 (Audio Control)
Device Protocol      : 00
Manufacturer         : Skullcandy, Inc.
Product              : Skullcandy GMX Dolby Transmitter
Supported USB Version: 1.10
Current Speed        : Full  (USB 1.1)
 
------[ DevClass / USB Hubs ]------
 
<DESC>Concentrateur USB SuperSpeed générique</DESC><DEVPATH>\\?\usb#vid_174c&pid_3074#5&1cc0e58a&0&20#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><INSTANCE>USB\VID_174C&PID_3074\5&1CC0E58A&0&20</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000014</ADDR>
<DESC>Concentrateur USB générique</DESC><DEVPATH>\\?\usb#vid_174c&pid_2074#5&1cc0e58a&0&9#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><INSTANCE>USB\VID_174C&PID_2074\5&1CC0E58A&0&9</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000009</ADDR>
<DESC>Concentrateur USB racine</DESC><DEVPATH>\\?\usb#root_hub20#4&35abf192&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><INSTANCE>USB\ROOT_HUB20\4&35ABF192&0</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000000</ADDR>
<DESC>Concentrateur USB générique</DESC><DEVPATH>\\?\usb#vid_174c&pid_2074#5&1cc0e58a&0&10#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><INSTANCE>USB\VID_174C&PID_2074\5&1CC0E58A&0&10</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>0000000A</ADDR>
<DESC>Concentrateur USB générique</DESC><DEVPATH>\\?\usb#vid_05e3&pid_0608#6&16396d6c&0&2#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><INSTANCE>USB\VID_05E3&PID_0608\6&16396D6C&0&2</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000002</ADDR>
<DESC>Concentrateur USB SuperSpeed générique</DESC><DEVPATH>\\?\usb#vid_174c&pid_3074#5&1cc0e58a&0&21#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><INSTANCE>USB\VID_174C&PID_3074\5&1CC0E58A&0&21</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000015</ADDR>
<DESC>Generic USB Hub</DESC><DEVPATH>\\?\usb#vid_8087&pid_8002#5&2d364466&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><INSTANCE>USB\VID_8087&PID_8002\5&2D364466&0&1</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000001</ADDR>
<DESC>Generic USB Hub</DESC><DEVPATH>\\?\usb#vid_8087&pid_800a#5&8df2a5&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><INSTANCE>USB\VID_8087&PID_800A\5&8DF2A5&0&1</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000001</ADDR>
<DESC>Concentrateur USB racine</DESC><DEVPATH>\\?\usb#root_hub20#4&12773313&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><INSTANCE>USB\ROOT_HUB20\4&12773313&0</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000000</ADDR>
<DESC>Concentrateur USB racine (xHCI)</DESC><DEVPATH>\\?\usb#root_hub30#4&34be82cc&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><INSTANCE>USB\ROOT_HUB30\4&34BE82CC&0&0</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000000</ADDR>
<DESC>Concentrateur USB racine (xHCI)</DESC><DEVPATH>\\?\usb#root_hub30#5&9b0b1eb&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><INSTANCE>USB\ROOT_HUB30\5&9B0B1EB&0&0</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000000</ADDR>
 
------[ DevClass / USB Devices ]------
 
<DESC>Bluetooth USB module</DESC><DEVPATH>\\?\usb#vid_0b05&pid_180a#40e23013aa74#{a5dcbf10-6530-11d2-901f-00c04fb951ed}</DEVPATH><INSTANCE>USB\VID_0B05&PID_180A\40E23013AA74</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000006</ADDR>
<DESC>Périphérique USB composite</DESC><DEVPATH>\\?\usb#vid_9886&pid_0004#6&1f61d461&0&4#{a5dcbf10-6530-11d2-901f-00c04fb951ed}</DEVPATH><INSTANCE>USB\VID_9886&PID_0004\6&1F61D461&0&4</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000004</ADDR>
<DESC>Périphérique USB composite</DESC><DEVPATH>\\?\usb#vid_1c4f&pid_0024#6&1e95266d&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}</DEVPATH><INSTANCE>USB\VID_1C4F&PID_0024\6&1E95266D&0&2</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000002</ADDR>
<DESC>Eaton UPS 0463-L</DESC><DEVPATH>\\?\usb#vid_0463&pid_ffff#g360f18144#{a5dcbf10-6530-11d2-901f-00c04fb951ed}</DEVPATH><INSTANCE>USB\VID_0463&PID_FFFF\G360F18144</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000003</ADDR>
<DESC>Périphérique USB composite</DESC><DEVPATH>\\?\usb#vid_25a7&pid_2433#5&1cc0e58a&0&11#{a5dcbf10-6530-11d2-901f-00c04fb951ed}</DEVPATH><INSTANCE>USB\VID_25A7&PID_2433\5&1CC0E58A&0&11</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>0000000B</ADDR>
 
------[ DevClass / Human Interface Devices ]------
 
<DESC>Périphérique de contrôle consommateur conforme aux Périphériques d'interface utilisateur (HID)</DESC><DEVPATH>\\?\hid#vid_9886&pid_0004&mi_03&col01#8&84226f5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_9886&PID_0004&MI_03&COL01\8&84226F5&0&0000</INSTANCE><BUSNUM>00000002</BUSNUM><ADDR>00000007</ADDR>
<DESC>Souris HID</DESC><DEVPATH>\\?\hid#vid_25a7&pid_2433&mi_01&col01#7&332dbdd5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_25A7&PID_2433&MI_01&COL01\7&332DBDD5&0&0000</INSTANCE><BUSNUM>00000001</BUSNUM><ADDR>0000000C</ADDR>
<DESC>Contrôleur système HID</DESC><DEVPATH>\\?\hid#vid_25a7&pid_2433&mi_01&col02#7&332dbdd5&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_25A7&PID_2433&MI_01&COL02\7&332DBDD5&0&0001</INSTANCE><BUSNUM>00000001</BUSNUM><ADDR>0000000C</ADDR>
<DESC>Périphérique clavier PIH</DESC><DEVPATH>\\?\hid#vid_25a7&pid_2433&mi_00#7&31c5705b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_25A7&PID_2433&MI_00\7&31C5705B&0&0000</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>0000000B</ADDR>
<DESC>Périphérique de contrôle consommateur conforme aux Périphériques d'interface utilisateur (HID)</DESC><DEVPATH>\\?\hid#vid_25a7&pid_2433&mi_01&col03#7&332dbdd5&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_25A7&PID_2433&MI_01&COL03\7&332DBDD5&0&0002</INSTANCE><BUSNUM>00000001</BUSNUM><ADDR>0000000C</ADDR>
<DESC>Périphérique de contrôle consommateur conforme aux Périphériques d'interface utilisateur (HID)</DESC><DEVPATH>\\?\hid#vid_1c4f&pid_0024&mi_01&col01#8&2faa4d0e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1C4F&PID_0024&MI_01&COL01\8&2FAA4D0E&0&0000</INSTANCE><BUSNUM>00000004</BUSNUM><ADDR>00000003</ADDR>
<DESC>Périphérique fournisseur HID</DESC><DEVPATH>\\?\hid#vid_25a7&pid_2433&mi_01&col04#7&332dbdd5&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_25A7&PID_2433&MI_01&COL04\7&332DBDD5&0&0003</INSTANCE><BUSNUM>00000001</BUSNUM><ADDR>0000000C</ADDR>
<DESC>Contrôleur système HID</DESC><DEVPATH>\\?\hid#vid_1c4f&pid_0024&mi_01&col02#8&2faa4d0e&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1C4F&PID_0024&MI_01&COL02\8&2FAA4D0E&0&0001</INSTANCE><BUSNUM>00000004</BUSNUM><ADDR>00000003</ADDR>
<DESC>Périphérique fournisseur HID</DESC><DEVPATH>\\?\hid#vid_25a7&pid_2433&mi_01&col05#7&332dbdd5&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_25A7&PID_2433&MI_01&COL05\7&332DBDD5&0&0004</INSTANCE><BUSNUM>00000001</BUSNUM><ADDR>0000000C</ADDR>
<DESC>Périphérique fournisseur HID</DESC><DEVPATH>\\?\hid#vid_9886&pid_0004&mi_03&col02#8&84226f5&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_9886&PID_0004&MI_03&COL02\8&84226F5&0&0001</INSTANCE><BUSNUM>00000002</BUSNUM><ADDR>00000007</ADDR>
<DESC>Périphérique clavier PIH</DESC><DEVPATH>\\?\hid#vid_1c4f&pid_0024&mi_00#8&bd30f4c&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1C4F&PID_0024&MI_00\8&BD30F4C&0&0000</INSTANCE><BUSNUM>00000003</BUSNUM><ADDR>00000002</ADDR>
 
------[ DevClass / COM Ports ]------
 
< No COM Port Found >
 
------[ DevClass / LPT Ports ]------
 
< No LPT Port Found >
 
------[ DevClass / Modems ]------
 
< No Modem Found >
 
------[ DevClass / SideShow Devices ]------
 
< No SideShow Device Found >
 
------[ DevClass / GX3 Devices ]------
 
< No GX3 Device Found >
 
------[ LibUsb0 Devices ]------
 
Device Description      : \\.\libusb0-0001--0x0463-0xffff
Device ID               : 0463-FFFF
Device Number           : 1
Device Class            : 00 / 00
Device Protocol         : 00
Manufacturer            : EATON
Product                 : Ellipse PRO
Serial Number           : G360F18144
Supported USB Version   : 1.10
 
------[ CH341 Devices ]------
 
< No CH341 Device Found >
 
------[ FTD2xx Devices ]------
 
< No FTD2xx Device Found >
 
------[ SiUSBXp Devices ]------
 
SiUSBXp.dll Path = 
 
< No SiUSBXp Device Found >
 

Share this post


Link to post
Share on other sites

Thank will try it now !

Looks good at 99% now !

Just got one glitch in about 1 hour.

Let me know about your long-term experiences about the current solution. We may have to lower the 256KB limit by a few KB's to make it more stable. But it's a good sign if the glitches become rare.

Share this post


Link to post
Share on other sites

It froze at 99%, did not really time after how long (maybe an hour, maybe less)

So I set the compression to 90% and it is working so far.

Using the latest Beta update ofcourse.

I hope it will work out. In your case I'm not at all sure about the 500KB limit. It may be lower, like 448KB, but it's not easy to calculate those limits without actually counting the displayed pixel lines on the LCD in the SPF random mode :) And we don't want to specify a too low JPEG size limit, since then AIDA64 may force you into a position of using too low JPEG quality resulting in low quality displayed images :( Of course it's still possible to define a JPEG quality manually, but even if you define 99%, the limiter will cut it back to fit the JPEG in the file size limit.

Share this post


Link to post
Share on other sites

Hi, this time lcd did not start on windows 10 starup.

I saw in the usb dump that the lcd descriptor is incorrect, so bad usb enumeration that explains why lcd is black:

 

------[ Périphérique USB inconnu (échec de demande de descripteur de périphérique)]------

 

Device Description   : Périphérique USB inconnu (échec de demande de descripteur de périphérique)

Device ID            : 0000-0000

Device Class         : 00 / 00

Device Protocol      : 00

Supported USB Version: 0.00

Current Speed        : High  (USB 2.0)

 

 

Nothing aida64 can do about it, crap lcd frame.

I think it's more about Win10 and the way it handles USB devices. We've also seen that issue coming up sometimes after restarting Win10. You can try connecting the SPF to a port that belongs to another USB controller, or try to use a USB hub. But I'm not sure if any of those would help :(

I'm starting to feel like we would be better off by purchasing a dozen of very affordable 8 or 10-inch Android based tablets, connect it to the USB port, and develop a special firmware that would kick the Android out and replace it with our own solution for SPF-like usage :) Too bad there's no considerable market (ie. thousands of guys interested) for such a special "AIDA64 Hardware".

Share this post


Link to post
Share on other sites

Could you create a version with the max size reduced by 2 to test if the remaining glitches are due to the  data size ?

About the lcd items related to network, there is a problem in the french translation:

NIC download = NIC taux de téléchargement (currently it is translated as télécharger taux)

NIC upload = NIC taux d'envoi (currently it is translated as téléchargement taux)

Share this post


Link to post
Share on other sites

Could you create a version with the max size reduced by 2 to test if the remaining glitches are due to the  data size ?

Yes, of course :) I'll send you a download link soon.

 

About the lcd items related to network, there is a problem in the french translation:

NIC download = NIC taux de téléchargement (currently it is translated as télécharger taux)

NIC upload = NIC taux d'envoi (currently it is translated as téléchargement taux)

Thank you. Can you please provide direct fix for the following 4 lines, for the whole expressions? It would help us to fix the issues in the French language module.

NIC1 Download Rate=NIC1 Télécharger taux

NIC1 Upload Rate=NIC1 Téléchargement taux

NIC1 Total Download=NIC1 Télécharger Total

NIC1 Total Upload=NIC1 Téléchargement Total

I think I'm right about feeling that the last line is not accurate either ;)

Share this post


Link to post
Share on other sites

That remember's me the time when I translated msi afterburner ^^

note; same for nic1,2,3,4 ..

 

NIC1 Download Rate=NIC1 Taux de téléchargement
NIC1 Upload Rate=NIC1 Taux d'envoi
NIC1 Total Download=NIC1 Téléchargement total
NIC1 Total Upload=NIC1 Envoi total

Share this post


Link to post
Share on other sites

That remember's me the time when I translated msi afterburner ^^

note; same for nic1,2,3,4 ..

 

NIC1 Download Rate=NIC1 Taux de téléchargement

NIC1 Upload Rate=NIC1 Taux d'envoi

NIC1 Total Download=NIC1 Téléchargement total

NIC1 Total Upload=NIC1 Envoi total

Merci ;)

Share this post


Link to post
Share on other sites

Also, any chance of getting the FPS info from RivaTunerStatisticsServer?

The requested feature will be implemented in the next AIDA64 beta update due in a few days from now ;)

Share this post


Link to post
Share on other sites

Strange since latest beta my lcd is dimming and I have to push the contrast every day.

Is it going to die or are some usb data packet controlling the contrast ?

Share this post


Link to post
Share on other sites

Strange since latest beta my lcd is dimming and I have to push the contrast every day.

Is it going to die or are some usb data packet controlling the contrast ?

AFAIK SPF devices do not feature a software method to adjust contrast. There's an interface to control brightness, but we haven't found a SPF device yet where that would work :) That's why on the AIDA64 / Preferences / Hardware Monitoring / LCD / Samsung page you cannot see brightness or contrast sliders -- while you can see that for other LCD devices like LCD2USB.

Share this post


Link to post
Share on other sites

What other photo frame (second hand) I could buy to replace the samsung one ? equal size and quality (or more) if possible ? Samsung 800P as yours ?

Do you support the more recent NIX photo frames    http://www.amazon.co.uk/NIX-Digital-Frame-automatically-nearby/dp/B008MW6Y12/ref=sr_1_2?s=electronics&ie=UTF8&qid=1439715350&sr=1-2&keywords=NIX    ?

 

Or the cheap kitvision ?

 

http://www.amazon.co.uk/KitVision-Digital-Built--Supporting-Memory/dp/B001FBXM6C/ref=sr_1_1?s=photo&ie=UTF8&qid=1439715436&sr=1-1&keywords=NIX

Share this post


Link to post
Share on other sites

What other photo frame (second hand) I could buy to replace the samsung one ? equal size and quality (or more) if possible ? Samsung 800P as yours ?

800P works fine, that's all I can tell about it. There's no real alternative though, since the only other DPF that AIDA64 supports is the AX206 based firmware hacked picture frames, which are small devices, like 2.4 inch and so.

Most of the picture frames simply do not implement a feature to push image data through the USB connection and get it displayed directly, without altering the on-board flash memory. Samsung SPF devices are really unique, so if you're looking for a large diagonal picture frame to display real-time sensor data, there's no real alternative to that. Unless of course you would get a cheap Android tablet and use RemoteSensor, Logitech Arx or Odospace with it.

Share this post


Link to post
Share on other sites

I hope it will work out. In your case I'm not at all sure about the 500KB limit. It may be lower, like 448KB, but it's not easy to calculate those limits without actually counting the displayed pixel lines on the LCD in the SPF random mode :) And we don't want to specify a too low JPEG size limit, since then AIDA64 may force you into a position of using too low JPEG quality resulting in low quality displayed images :( Of course it's still possible to define a JPEG quality manually, but even if you define 99%, the limiter will cut it back to fit the JPEG in the file size limit.

Loking at the photo I sent you  the screen is not 50% covered, so it might actually be closer to 448 Kb or even less.

Anyway I had to set it back to 85% to work fluidly which causes quite a bit of JPEG compression artifacts on the bars.

I might rethink and redesign the whole thing with less bars and images.

 

 

The requested feature will be implemented in the next AIDA64 beta update due in a few days from now ;)

Thank you. Too many monitoring apps on this PC anyway. RTSS is mandratory with MSI AB, having Fraps also installed is a mess, and then there is also Speedfan.

You will just need to let me know how to configure RTSS to display FPS on the screen.

Share this post


Link to post
Share on other sites

Loking at the photo I sent you  the screen is not 50% covered, so it might actually be closer to 448 Kb or even less.

Anyway I had to set it back to 85% to work fluidly which causes quite a bit of JPEG compression artifacts on the bars.

I might rethink and redesign the whole thing with less bars and images.

Yes, it's less than 50%. The fully random image that you've used to test the JPEG size limit was 1088 KB long. What's unclear to us at this point is whether the SPF JPEG size limit is always a multiply of 64 KB or 100 KB. We have to do more test runs, and also have to get more SPF devices.

 

Thank you. Too many monitoring apps on this PC anyway. RTSS is mandratory with MSI AB, having Fraps also installed is a mess, and then there is also Speedfan.

You will just need to let me know how to configure RTSS to display FPS on the screen.

Please find the mentioned new AIDA64 Extreme beta update at:

http://www.aida64.com/downloads/latesta64xebeta

Simply add the new RTSS FPS item to your LCD layout, and start RTSS. That's all you have to do basically :)

Share this post


Link to post
Share on other sites

Yes, it's less than 50%. The fully random image that you've used to test the JPEG size limit was 1088 KB long. What's unclear to us at this point is whether the SPF JPEG size limit is always a multiply of 64 KB or 100 KB. We have to do more test runs, and also have to get more SPF devices.

Anything I could do to help with this?

 

Please find the mentioned new AIDA64 Extreme beta update at:

http://www.aida64.com/downloads/latesta64xebeta

Simply add the new RTSS FPS item to your LCD layout, and start RTSS. That's all you have to do basically :)

It is working :D

I was thinking, any way to make the text change color according to value?

Share this post


Link to post
Share on other sites

Good my lcd is not about to die,

for some reason the default constrast was set low in the lcd parameters menu.

This can only be accessed when usb cable is removed.

Share this post


Link to post
Share on other sites

Good my lcd is not about to die,

for some reason the default constrast was set low in the lcd parameters menu.

This can only be accessed when usb cable is removed.

Yes, you need to access the "onboard" firmware and buttons to make any changes to contrast / brightness.

Whics means you have to disconnect the USB cable and let the display boot into photo frame mode.

I think this is the same for all SPF devices.

Share this post


Link to post
Share on other sites

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 Roy
      Hi,
      it would be nice if there was the possibility to send sensor values unformatted as a number or percentage, via a serial port.
      Similar to the LCD displays, only without formatting, or pure numbers with separators.
      Together with a small GUI.
      Background is the simple evaluation of the data with a microcontroller and display in different ways.
      I imagine not only LCD or OLED, but rather seven segment display, nixi tubes or an analog pointer display. That would create a lot of possibilities.
    • By Wampo
      Hey Aida Team,
      i have some issues with this Adafruit LCD wich is recomended. On the two Pictures you can see what aida should do and what can i see on the Display. The First line is completely erased and the screen is flickering. The Adafruit Backpack is set to 20x4 LCD. When the Display is updating you can see the right setting for a millisecond.
      But if i change the LCD Setting in AIDA to 16x2, and leave the Backpack in 20x4 mode,  the Screen isn flickering and the first line is there. I think you got a little problem with the 20x4 Driver. I have Searched for the code but i cant find it, to edit it if i found the failure. 
       
      Please give me response for this BUG. I have extra ordert this overpriced 50€ LCD for it. 
      Greetings Daniel from Germany


      VID_20181129_160917.mp4
    • By Fiery
      We've added support for RoboPeak RPUSBDisp color graphical USB-connected LCD display.

      You can enable the LCD device from AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / RoboPeak. Currently there is no Windows driver made specifically for RoboPeak displays.  But there's a workaround: you can use the AlphaCool LCD driver (Version 2.1).  The driver installation has to be forced due to the USB device ID mismatch (between AlphaCool and RoboPeak displays).
      The driver installation works as:
      Open Device Manager --> Other devices --> double-click on rp-usbdisp --> Update Driver button --> Browse my computer for driver software --> Let me pick from a list of available drivers on my computer --> Show All Devices --> Next button --> Have Disk button --> Browse button --> select acusbdisplay.inf file from the AlphaCool LCD driver folder --> Next button --> press Yes button on the Update Driver Warning message box.

      You can order a RoboPeak display from DFRobot at:
      https://www.dfrobot.com/product-1062.html#.UqfXHfSnoqX
      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
    • By Fiery
      We've added support for several Matrix Orbital USB character based and monochrome graphical LCD displays, including LK, MX, PK, VK, GLK, GLT, GX Typhoon, and their drive-bay and external variants as well.
      You can enable the LCD device from AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD. The only thing needed to enable this feature is having the appropriate Matrix Orbital USB LCD drivers installed, and the LCD to be connected to a USB port. You can verify if your device is supported by AIDA64 by finding the device on the Devices / USB Devices page in AIDA64, and checking its Device ID. It should be one of the following IDs:
      0403-FA01
      0403-FA02
      0403-FA03
      0403-FA04
      0403-FA05
      1B3D-011F
      1B3D-0120
      1B3D-0121
      1B3D-0123
      1B3D-0125
      1B3D-0127
      1B3D-012C
      1B3D-0134
      1B3D-013E
      1B3D-013F
      1B3D-0140
      1B3D-0141
      1B3D-0155
      1B3D-0156
      1B3D-0157
      1B3D-0158
      1B3D-015E
      1B3D-0161
      1B3D-016A
      1B3D-016B
      1B3D-016C
      1B3D-0176
      1B3D-017B
      1B3D-01F0
      1B3D-01F1

      Due to their interface bottleneck BGK, EGLK, GLK and GLT displays perform display updates quite slowly, so visual discrepancies may be experienced when using the GLK (graphics) protocol on these displays. It is possible to use the LK (character based) protocol on GLK displays as well, which will work much faster. In order to switch between the GLK and LK protocols, you need to first disable the GLK protocol (in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD), and then enable the LK protocol on the same page. Ignore the error, and restart AIDA64 to apply the switch.
      You can find the new AIDA64 beta update at:
      http://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. BTW, Abacom, AlphaCool, Digital Devices, LCD2USB, Mad Catz Venom, and SDC Megtron LCDs are also supported now by the latest AIDA64 beta.
      Regards,
      Fiery
    • By Fiery
      We've added support for the built-in 160x32 pixel monochrome LCD screen of EVGA Z10 gaming keyboard.  You can enable the LCD device from AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / EVGA.
      [/
      Currently AIDA64 communicates with the LCD directly, using USB HID interface.  It collides with EVGA's own software (EVGA Unleash), so it's recommended to close that software before enabling EVGA Z10 support in AIDA64.  EVGA will soon develop a proper SDK/API for their keyboard, much like the LCD API of Logitech gaming keyboards, so that multiple software can put information on the LCD the same time, without collisions.
      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
×
×
  • Create New...