Fiery Posted August 2, 2015 Author Share Posted August 2, 2015 Thank you. It seems your iMon is not like most iMon devices Most iMons have USB HID devices, and even though yours share USB ID with "regular" iMons, it works differently. Can you please send me a download link to the official drivers and software for your device? We have to check what driver does it have installed, to see what interface/API should we use to talk to the device. Also, drop me a private message in case you know another one for sale I've tried it on the 'bay, but with no luck... Quote Link to comment Share on other sites More sharing options...
cqman Posted August 2, 2015 Share Posted August 2, 2015 Thank you. It seems your iMon is not like most iMon devices Most iMons have USB HID devices, and even though yours share USB ID with "regular" iMons, it works differently. Can you please send me a download link to the official drivers and software for your device? We have to check what driver does it have installed, to see what interface/API should we use to talk to the device. Also, drop me a private message in case you know another one for sale I've tried it on the 'bay, but with no luck... I downloaded the official drivers and software here: http://www.soundgraph.com/forums/showthread.php?t=9857. It's the latest version for years , works fine under Win10 x64 preview. Quote Link to comment Share on other sites More sharing options...
Fiery Posted August 2, 2015 Author Share Posted August 2, 2015 Thank you. Can you please check what driver is installed for your device? Open Device Manager, double-click on the device named "SG Remote Control Device", select the Driver tab, and push the Driver Details button. Only the filename is important, the full path (directory) is not that much. I wonder if your device uses the driver called iMON_PAD.sys. Quote Link to comment Share on other sites More sharing options...
cqman Posted August 3, 2015 Share Posted August 3, 2015 Thank you. Can you please check what driver is installed for your device? Open Device Manager, double-click on the device named "SG Remote Control Device", select the Driver tab, and push the Driver Details button. Only the filename is important, the full path (directory) is not that much. I wonder if your device uses the driver called iMON_PAD.sys. mmm, this thing uses the iMON_x64.sys Quote Link to comment Share on other sites More sharing options...
Fiery Posted August 3, 2015 Author Share Posted August 3, 2015 mmm, this thing uses the iMON_x64.sys Thank you, that's fine too I've just dropped you a private message about this. Quote Link to comment Share on other sites More sharing options...
cqman Posted August 3, 2015 Share Posted August 3, 2015 Thank you, that's fine too I've just dropped you a private message about this. Thank you. I can handle it now. Quote Link to comment Share on other sites More sharing options...
Fiery Posted August 3, 2015 Author Share Posted August 3, 2015 Thank you. I can handle it now. Thanks for the test runs, the improved SoundGraph LCD/VFD support module will of course be implemented in the next AIDA64 beta update, and also the next AIDA64 stable update. The stable update is currently scheduled to be rolled out in late September -- not written in stone though Quote Link to comment Share on other sites More sharing options...
geekay Posted October 26, 2015 Share Posted October 26, 2015 Thank you for the dump. Is this the one with the 7-inch touchscreen LCD? If yes, then I'm afraid it's not supported by AIDA64 right now, since we've got absolutely no information on how to handle that LCD. Do you have a software that could handle that? Apart from the Soundgraph iMON package? Hi, really sorry for the delayed answer! I have no other software to handle this monitor. I thought this would be like a standard device for aida64 Quote Link to comment Share on other sites More sharing options...
Fiery Posted October 26, 2015 Author Share Posted October 26, 2015 Hi, really sorry for the delayed answer! I have no other software to handle this monitor. I thought this would be like a standard device for aida64 Thank you for the info. And no, I'm afraid AIDA64 doesn't support that device, and we have no technical information/details that we could use to start working on it either Quote Link to comment Share on other sites More sharing options...
fp777 Posted March 16, 2016 Share Posted March 16, 2016 Hello! I have a microcontroller BV514 http://www.bypic.byvac.com/index.php/BV514 Can I use this LCD to AIDA64? Dump: ------[ AIDA64 Extreme v5.60.3700 ]------ ------[ Microsoft Windows 10 Pro 10.0.10586.162 (64-bit) ]------ ------[ USB Devices ]------ Стандартный раÑширенный PCI - USB хоÑÑ‚-контроллер - [Port 2] Generic USB Hub - - [Port 2] < No Device Connected > - - [Port 3] USB Serial Converter (FT232R USB UART) - - - USB Serial Port (COM3) ------[ USB Serial Converter]------ Device Description : USB Serial Converter Device ID : 0403-6001 Device Class : FF / FF Device Protocol : FF Manufacturer : FTDI Product : FT232R USB UART Serial Number : A101LTBW Supported USB Version: 2.00 Current Speed : Full (USB 1.1) ------[ DevClass / USB Devices ]------ <DESC>USB Serial Converter</DESC><DEVPATH>\\?\usb#vid_0403&pid_6001#a101ltbw#{a5dcbf10-6530-11d2-901f-00c04fb951ed}</DEVPATH><INSTANCE>USB\VID_0403&PID_6001\A101LTBW</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000003</ADDR> ------[ DevClass / COM Ports ]------ <DESC>USB Serial Port (COM3)</DESC><DEVPATH>\\?\ftdibus#vid_0403+pid_6001+a101ltbwa#0000#{86e0d1e0-8089-11d0-9ce4-08003e301f73}</DEVPATH><INSTANCE>FTDIBUS\VID_0403+PID_6001+A101LTBWA\0000</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000003</ADDR> ------[ FTD2xx Devices ]------ Device Description : FT232R USB UART Device ID : 0403-6001 Device Index : 0 Device Location : 1059 Device Type : FT232R Serial Number : A101LTBW Associated COM Port: COM3 Thank you Quote Link to comment Share on other sites More sharing options...
Fiery Posted March 16, 2016 Author Share Posted March 16, 2016 Thank you for the dump. Based on that, it uses an industry standard FT232 USB->Serial bridge chip. The "issue" is behind that chip, ie. how to talk to the LCD using serial commands passed to the FT232 chip. EDIT: I've found some material Let us check how it works, and I will report back in this topic. Quote Link to comment Share on other sites More sharing options...
fp777 Posted March 16, 2016 Share Posted March 16, 2016 BV514 understands VT100 terminal command. I tried to display different text and graphics. But I have a little experience for independent programming.I look forward to your advice. Quote Link to comment Share on other sites More sharing options...
Fiery Posted March 17, 2016 Author Share Posted March 17, 2016 We've checked what's available online, but it doesn't seem to be clear at all. Is it possible to handle the device in graphics mode, without writing the bitmap frames to the built-in SD card? Writing one frame per second (or more frequently) to the SD card would destroy the card in a few hours, so it's not feasable. If you're looking for a solution to handle the device in alphanumeric (character) mode, then please let me know what character resolution does your device support, what are the VT100 commands to use to move the cursor to a specific position, how to send text (if there's an escape code to display text), what's the command to clear the display, what's the command for contrast and brightness adjustment, and the bit rate (baud) to use with the additional COM port settings like parity, stop bits, etc. Or, in case there's a single document to explain all that, let me know where can we download it from. I couldn't find one for your specific device that would include programming details and protocol description. Thanks, Fiery Quote Link to comment Share on other sites More sharing options...
fp777 Posted March 17, 2016 Share Posted March 17, 2016 del Quote Link to comment Share on other sites More sharing options...
fp777 Posted March 19, 2016 Share Posted March 19, 2016 We've checked what's available online, but it doesn't seem to be clear at all. Is it possible to handle the device in graphics mode, without writing the bitmap frames to the built-in SD card? Writing one frame per second (or more frequently) to the SD card would destroy the card in a few hours, so it's not feasable. If you're looking for a solution to handle the device in alphanumeric (character) mode, then please let me know what character resolution does your device support, what are the VT100 commands to use to move the cursor to a specific position, how to send text (if there's an escape code to display text), what's the command to clear the display, what's the command for contrast and brightness adjustment, and the bit rate (baud) to use with the additional COM port settings like parity, stop bits, etc. Or, in case there's a single document to explain all that, let me know where can we download it from. I couldn't find one for your specific device that would include programming details and protocol description. Thanks, Fiery Product BV4629 V2 (compatible BV514) http://doc.byvac.com...oduct_BV4629_V2 Escape Codes and other http://www.byvac.co....2 DataSheet.pdf (page 9) Quote Link to comment Share on other sites More sharing options...
romP44 Posted December 19, 2016 Share Posted December 19, 2016 Hello, I'm new in the forum but I'm very interested by this software ! I would like to use a OLED display with AIDA64. The controller is SSD1322. It's possible to communicate by parallel port 6800 or 8080 mode, or by SPI. You can find enclosed a lot of information. I hope it is enough to develop a driver for this controller. Thank you very much for your support ! SSD1322.zip Quote Link to comment Share on other sites More sharing options...
Fiery Posted December 20, 2016 Author Share Posted December 20, 2016 16 hours ago, romP44 said: Hello, I'm new in the forum but I'm very interested by this software ! I would like to use a OLED display with AIDA64. The controller is SSD1322. It's possible to communicate by parallel port 6800 or 8080 mode, or by SPI. You can find enclosed a lot of information. I hope it is enough to develop a driver for this controller. Thank you very much for your support ! SSD1322.zip What interface will you use to connect your OLED display to your PC? Quote Link to comment Share on other sites More sharing options...
romP44 Posted December 20, 2016 Share Posted December 20, 2016 2 hours ago, Fiery said: What interface will you use to connect your OLED display to your PC? I have a parallel port on my computer, so I will go for 6800 or 8080 parallel interface. But as parallel port is now obsolete, USB-SPI would be great, by using a FTDI chip FT220X for example. It would be perfect if this new driver can works with LCDHype ! Quote Link to comment Share on other sites More sharing options...
Fiery Posted December 21, 2016 Author Share Posted December 21, 2016 22 hours ago, romP44 said: I have a parallel port on my computer, so I will go for 6800 or 8080 parallel interface. But as parallel port is now obsolete, USB-SPI would be great, by using a FTDI chip FT220X for example. It would be perfect if this new driver can works with LCDHype ! Let me know if you settled on a single interface and a single display protocol, and then we can start working on the implementation Quote Link to comment Share on other sites More sharing options...
romP44 Posted December 21, 2016 Share Posted December 21, 2016 2 hours ago, Fiery said: Let me know if you settled on a single interface and a single display protocol, and then we can start working on the implementation Then, let's go for SPI with FT220X chip. (I haven't the display yet, but it is ordered). Quote Link to comment Share on other sites More sharing options...
Fiery Posted December 23, 2016 Author Share Posted December 23, 2016 On 2016. 12. 21. at 5:55 PM, romP44 said: Then, let's go for SPI with FT220X chip. (I haven't the display yet, but it is ordered). Once you have the display assembled and connected to your PC, 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. Quote Link to comment Share on other sites More sharing options...
romP44 Posted January 2, 2017 Share Posted January 2, 2017 Here is the USB dump with only the UMFT220XB connected, not the OLED display. Anyway, it will be connected by SPI to the UMFT220XB, so I guess it will not change the USB dump: ------[ AIDA64 Extreme v5.80.4000 ]------ ------[ Microsoft Windows 10 Pro 10.0.14393.576 (64-bit) ]------ ------[ Motherboard Info ]------ Motherboard ID : 63-0100-000001-00101111-121412-Chipset$1AQQW036_BIOS DATE: 04/01/15 11:17:33 VER: V3.10B0 Motherboard Model : MSI B85-G43 (MS-7816) Motherboard Chipset : Intel Lynx Point B85, Intel Haswell DMI MB Manufacturer : MSI DMI MB Product : B85-G43 (MS-7816) DMI MB Version : 1.0 DMI MB Serial : To be filled by O.E.M. DMI SYS Manufacturer: MSI DMI SYS Product : MS-7816 DMI SYS Version : 1.0 DMI SYS Serial : To be filled by O.E.M. DMI BIOS Version : V3.10 ------[ USB Devices ]------ Contrôleur hôte Intel(R) 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] < No Device Connected > - [Port 7] 802.11n USB Wireless LAN Card (802.11 n WLAN) - - Microsoft Wi-Fi Direct Virtual Adapter - [Port 8] Microsoft Mouse and Keyboard Detection Driver (USB) (Microsoft® Nano Transceiver v2.0) - - Clavier USB Microsoft Hardware - - - Microsoft USB Dual Receiver Wireless Keyboard (Mouse and Keyboard Center) - - Périphérique d’entrée USB - - - Périphérique de contrôle consommateur conforme aux Périphériques d'interface utilisateur (HID) - - - Souris HID - - 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 de contrôle consommateur conforme aux Périphériques d'interface utilisateur (HID) - - - Périphérique fournisseur HID - [Port 9] Périphérique d’entrée USB (Thrustmaster dual analog 3.2) - - Contrôleur de jeu HID - [Port 10] USB Serial Converter (UMFT220XB) - [Port 11] < No Device Connected > - [Port 12] < No Device Connected > - [Port 13] Unknown Device - [Port 14] Unknown Device - [Port 15] Unknown Device - [Port 16] < No Device Connected > - [Port 17] < No Device Connected > - [Port 18] < No Device Connected > - [Port 19] < No Device Connected > - [Port 20] < No Device Connected > - [Port 21] < No Device Connected > Intel(R) 8/C220 USB EHCI n° 2 - 8C2D - [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(R) 8/C220 USB EHCI N° 1 - 8C26 - [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 > ------[ 802.11n USB Wireless LAN Card]------ Device Description : 802.11n USB Wireless LAN Card Device ID : 148F-5370 Device Class : FF / FF Device Protocol : FF Revision : 0101h Manufacturer : Ralink Product : 802.11 n WLAN Serial Number : 1.0 Supported USB Version: 2.00 Current Speed : High (USB 2.0) ------[ Microsoft Mouse and Keyboard Detection Driver (USB)]------ Device Description : Microsoft Mouse and Keyboard Detection Driver (USB) Device ID : 045E-0800 Device Class : 03 / 01 (Human Interface Device) Device Protocol : 01 Revision : 0934h Manufacturer : Microsoft Product : Microsoft® Nano Transceiver v2.0 Supported USB Version: 2.00 Current Speed : Full (USB 1.1) ------[ Périphérique d’entrée USB]------ Device Description : Périphérique d’entrée USB Device ID : 044F-B315 Device Class : 03 / 00 (Human Interface Device) Device Protocol : 00 Revision : 0101h Manufacturer : Thrustmaster Product : Thrustmaster dual analog 3.2 Supported USB Version: 1.10 Current Speed : Low (USB 1.1) ------[ USB Serial Converter]------ Device Description : USB Serial Converter Device ID : 0403-6015 Device Class : FF / FF Device Protocol : FF Revision : 1000h Manufacturer : FTDI Product : UMFT220XB Serial Number : FTWCTB7R Supported USB Version: 2.00 Current Speed : Full (USB 1.1) ------[ Unknown Device]------ Device Description : Unknown Device Device ID : 0000-0000 Device Class : 00 / 00 Device Protocol : 00 Revision : 0000h Supported USB Version: 0.00 Current Speed : Low (USB 1.1) ------[ Unknown Device]------ Device Description : Unknown Device Device ID : 0000-0000 Device Class : 00 / 00 Device Protocol : 00 Revision : 0000h Supported USB Version: 0.00 Current Speed : Low (USB 1.1) ------[ Unknown Device]------ Device Description : Unknown Device Device ID : 0000-0000 Device Class : 00 / 00 Device Protocol : 00 Revision : 0000h Supported USB Version: 0.00 Current Speed : Low (USB 1.1) ------[ Generic USB Hub]------ Device Description : Generic USB Hub Device ID : 8087-8008 Device Class : 09 / 00 (Hi-Speed Hub with single TT) Device Protocol : 01 Revision : 0005h Supported USB Version: 2.00 Current Speed : High (USB 2.0) ------[ Generic USB Hub]------ Device Description : Generic USB Hub Device ID : 8087-8000 Device Class : 09 / 00 (Hi-Speed Hub with single TT) Device Protocol : 01 Revision : 0005h Supported USB Version: 2.00 Current Speed : High (USB 2.0) ------[ DevClass / USB Hubs ]------ <DESC>Concentrateur USB racine</DESC><DEVPATH>\\?\usb#root_hub20#4&1562e2ff&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><INSTANCE>USB\ROOT_HUB20\4&1562E2FF&0</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000000</ADDR> <DESC>Concentrateur USB racine</DESC><DEVPATH>\\?\usb#root_hub20#4&32c041a6&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><INSTANCE>USB\ROOT_HUB20\4&32C041A6&0</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000000</ADDR> <DESC>Generic USB Hub</DESC><DEVPATH>\\?\usb#vid_8087&pid_8008#5&28ee202c&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><INSTANCE>USB\VID_8087&PID_8008\5&28EE202C&0&1</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000001</ADDR><REV>0005</REV> <DESC>Generic USB Hub</DESC><DEVPATH>\\?\usb#vid_8087&pid_8000#5&644aeca&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><INSTANCE>USB\VID_8087&PID_8000\5&644AECA&0&1</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000001</ADDR><REV>0005</REV> <DESC>Concentrateur USB racine (xHCI)</DESC><DEVPATH>\\?\usb#root_hub30#4&37aa32b8&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><INSTANCE>USB\ROOT_HUB30\4&37AA32B8&0&0</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000000</ADDR> ------[ DevClass / USB Devices ]------ <DESC>802.11n USB Wireless LAN Card</DESC><DEVPATH>\\?\usb#vid_148f&pid_5370#1.0#{a5dcbf10-6530-11d2-901f-00c04fb951ed}</DEVPATH><INSTANCE>USB\VID_148F&PID_5370\1.0</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000007</ADDR><REV>0101</REV> <DESC>Microsoft Mouse and Keyboard Detection Driver (USB)</DESC><DEVPATH>\\?\usb#vid_045e&pid_0800#5&2c60a704&0&8#{a5dcbf10-6530-11d2-901f-00c04fb951ed}</DEVPATH><INSTANCE>USB\VID_045E&PID_0800\5&2C60A704&0&8</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000008</ADDR><REV>0934</REV> <DESC>Périphérique d’entrée USB</DESC><DEVPATH>\\?\usb#vid_044f&pid_b315#5&2c60a704&0&9#{a5dcbf10-6530-11d2-901f-00c04fb951ed}</DEVPATH><INSTANCE>USB\VID_044F&PID_B315\5&2C60A704&0&9</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000009</ADDR><REV>0101</REV> <DESC>USB Serial Converter</DESC><DEVPATH>\\?\usb#vid_0403&pid_6015#ftwctb7r#{a5dcbf10-6530-11d2-901f-00c04fb951ed}</DEVPATH><INSTANCE>USB\VID_0403&PID_6015\FTWCTB7R</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>0000000A</ADDR><REV>1000</REV> ------[ DevClass / Human Interface Devices ]------ <DESC>Périphérique fournisseur HID</DESC><DEVPATH>\\?\hid#vid_045e&pid_0800&mi_02&col03#7&2f1e99&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_045E&PID_0800&MI_02&COL03\7&2F1E99&0&0002</INSTANCE><BUSNUM>00000002</BUSNUM><ADDR>0000000A</ADDR><REV>0934</REV> <DESC>Périphérique de contrôle consommateur conforme aux Périphériques d'interface utilisateur (HID)</DESC><DEVPATH>\\?\hid#vid_045e&pid_0800&mi_02&col01#7&2f1e99&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_045E&PID_0800&MI_02&COL01\7&2F1E99&0&0000</INSTANCE><BUSNUM>00000002</BUSNUM><ADDR>0000000A</ADDR><REV>0934</REV> <DESC>Contrôleur système HID</DESC><DEVPATH>\\?\hid#vid_045e&pid_0800&mi_02&col04#7&2f1e99&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_045E&PID_0800&MI_02&COL04\7&2F1E99&0&0003</INSTANCE><BUSNUM>00000002</BUSNUM><ADDR>0000000A</ADDR><REV>0934</REV> <DESC>Microsoft USB Dual Receiver Wireless Keyboard (Mouse and Keyboard Center)</DESC><DEVPATH>\\?\hid#vid_045e&pid_0800&mi_00#7&1569b024&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_045E&PID_0800&MI_00\7&1569B024&0&0000</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000008</ADDR><REV>0934</REV> <DESC>Contrôleur de jeu HID</DESC><DEVPATH>\\?\hid#vid_044f&pid_b315#6&37aad13e&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_044F&PID_B315\6&37AAD13E&1&0000</INSTANCE><BUSNUM>00000005</BUSNUM><ADDR>00000009</ADDR><REV>0101</REV> <DESC>Périphérique de contrôle consommateur conforme aux Périphériques d'interface utilisateur (HID)</DESC><DEVPATH>\\?\hid#vid_045e&pid_0800&mi_02&col02#7&2f1e99&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_045E&PID_0800&MI_02&COL02\7&2F1E99&0&0001</INSTANCE><BUSNUM>00000002</BUSNUM><ADDR>0000000A</ADDR><REV>0934</REV> <DESC>Souris HID</DESC><DEVPATH>\\?\hid#vid_045e&pid_0800&mi_01&col01#7&2899cc62&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_045E&PID_0800&MI_01&COL01\7&2899CC62&0&0000</INSTANCE><BUSNUM>00000001</BUSNUM><ADDR>00000009</ADDR><REV>0934</REV> <DESC>Périphérique de contrôle consommateur conforme aux Périphériques d'interface utilisateur (HID)</DESC><DEVPATH>\\?\hid#vid_045e&pid_0800&mi_01&col02#7&2899cc62&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_045E&PID_0800&MI_01&COL02\7&2899CC62&0&0001</INSTANCE><BUSNUM>00000001</BUSNUM><ADDR>00000009</ADDR><REV>0934</REV> ------[ HID Device Info / Périphérique fournisseur HID ]------ Device ID : 045E-0800 Revision : 0934h Device Instance : HID\VID_045E&PID_0800&MI_02&COL03\7&2F1E99&0&0002 Usage : 0088h Usage Page : FFBCh Input Report Byte Length : 2 Output Report Byte Length : 0 Feature Report Byte Length: 0 ------[ HID Device Info / Périphérique de contrôle consommateur conforme aux Périphériques d'interface utilisateur (HID) ]------ Device ID : 045E-0800 Revision : 0934h Device Instance : HID\VID_045E&PID_0800&MI_02&COL01\7&2F1E99&0&0000 Usage : 0001h Usage Page : 000Ch Input Report Byte Length : 32 Output Report Byte Length : 0 Feature Report Byte Length: 32 ------[ HID Device Info / Contrôleur système HID ]------ Device ID : 045E-0800 Revision : 0934h Device Instance : HID\VID_045E&PID_0800&MI_02&COL04\7&2F1E99&0&0003 Usage : 0080h Usage Page : 0001h Input Report Byte Length : 2 Output Report Byte Length : 0 Feature Report Byte Length: 0 ------[ HID Device Info / Contrôleur de jeu HID ]------ Manufacturer : Thrustmaster Product : Thrustmaster dual analog 3.2 Device ID : 044F-B315 Revision : 0101h Device Instance : HID\VID_044F&PID_B315\6&37AAD13E&1&0000 Usage : 0005h Usage Page : 0001h Input Report Byte Length : 8 Output Report Byte Length : 5 Feature Report Byte Length: 0 ------[ HID Device Info / Périphérique de contrôle consommateur conforme aux Périphériques d'interface utilisateur (HID) ]------ Device ID : 045E-0800 Revision : 0934h Device Instance : HID\VID_045E&PID_0800&MI_02&COL02\7&2F1E99&0&0001 Usage : 0001h Usage Page : 000Ch Input Report Byte Length : 8 Output Report Byte Length : 0 Feature Report Byte Length: 0 ------[ HID Device Info / Périphérique de contrôle consommateur conforme aux Périphériques d'interface utilisateur (HID) ]------ Device ID : 045E-0800 Revision : 0934h Device Instance : HID\VID_045E&PID_0800&MI_01&COL02\7&2899CC62&0&0001 Usage : 0001h Usage Page : 000Ch Input Report Byte Length : 3 Output Report Byte Length : 0 Feature Report Byte Length: 2 ------[ DevClass / COM Ports ]------ < No COM Port Found > ------[ DevClass / LPT Ports ]------ <DESC>Port imprimante (LPT1)</DESC><DEVPATH>\\?\acpi#pnp0400#4&37e68bcf&0#{97f76ef0-f883-11d0-af1f-0000f800845c}</DEVPATH><INSTANCE>ACPI\PNP0400\4&37E68BCF&0</INSTANCE><BUSNUM>00000000</BUSNUM> ------[ DevClass / Modems ]------ < No Modem Found > ------[ DevClass / SideShow Devices ]------ < No SideShow Device Found > ------[ DevClass / GX3 Devices ]------ < No GX3 Device Found > ------[ DevClass / USBXpress Devices ]------ < No USBXpress Device Found > ------[ LibUsb0 Devices ]------ < No LibUsb0 Device Found > ------[ CH341 Devices ]------ < No CH341 Device Found > ------[ FTD2xx Devices ]------ Device Description : UMFT220XB Device ID : 0403-6015 Device Index : 0 Device Location : 26 Device Type : X-Series Serial Number : FTWCTB7R ------[ SiUSBXp Devices ]------ SiUSBXp.dll Path = < No SiUSBXp Device Found > ------[ T-Balancer Devices ]------ < No T-Balancer Device Found > ------[ Koolance TMS-200 Devices ]------ < No T-Koolance TMS-200 Device Found > Quote Link to comment Share on other sites More sharing options...
Fiery Posted January 3, 2017 Author Share Posted January 3, 2017 13 hours ago, romP44 said: Here is the USB dump with only the UMFT220XB connected, not the OLED display. Anyway, it will be connected by SPI to the UMFT220XB, so I guess it will not change the USB dump: Thank you. Do you have an idea on the amount of data that needs to be transferred in each cycle to update the OLED screen content? The pixel data alone seems to be 30 KiloBytes, plus the overhead of the command issuing, etc. What is the speed of the SPI connection that your device would utilize? I'm a bit concerned about the whole thing being too slow. We consider a display too slow when the update rate cannot be kept at an acceptable level, like twice a second. Quote Link to comment Share on other sites More sharing options...
romP44 Posted January 3, 2017 Share Posted January 3, 2017 According the specification of SSD1322, the minimum period for the clock is 80ns (40ns x 2) => 25MHz without taking into account the rise and fall time. The FT220X can generate clocks of 24, 12 or 6MHz. 24MHz would be too fast for the SSD1322 if we take into account the rise and fall time. So, 12MHz must be used. Each pixel has 4 bits (16 gray levels). My OLED display ER-OLEDM032-1W has 256x64 = 16384 pixels. => 1 frame is 65536 bits. If "address increment mode" is activated (command A0h of the SSD1322), the pointer to the RAM adress is automaticaly incremented, so it's not needed to send a command between each pixel data. => 12MHz / 65536 bits = 183 frames per second. It seems OK to me (for info, with 480x128 pixels, the maximum supported by SSD1322 => 48,8 frames per second). Quote Link to comment Share on other sites More sharing options...
Fiery Posted January 4, 2017 Author Share Posted January 4, 2017 You seem to know your stuff, so let me ask you a few further deep technical questions, to make sure we initialize your device in a way it's expected. 1) What baud rate shall we use when calling FT_SetBaudRate? 2) What argument values shall we use when calling FT_SetDataCharacteristics, FT_SetFlowControl and FT_SetTimeouts? 3) Can you please provide the exact command bytes we need to issue at the OLED init, and the command bytes we need to use at each frame update? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.