Upgrading Mainboard in Lecroy DDA-3000 (aka WavePro 7300a?)

[Converter]

... What kind of CPU load do you see when you use 3D mode like the one you demo in your youtube video? On my WP7K1 with Intel i7-2600 I'm able to bring one of the cores to 100% and it slows down the visuals. I'm curious if it's really CPU-bound or the graphic chip is a culprit?  I'm still using Intel HD graphic chip integrated on the CPU...

-albertr

I'll check later. But I think the problem may also be insufficient bandwidth lines Gigabit Ethernet and expansion slots PCI 2.0 (33 MHz), connecting the motherboard CPU to the  Acquisition Board in the system X-Stream v.1. PCI-slot is the bottleneck.

I noticed that the "interface card LeCroy" has a universal PCI-slot, with two types of slits. It is usually made to be compatible with both PCI standards - 5V / 33MHz and 3.3V / 66MHz. Bandwidth the first type - 133 Mb/s, while the second - 266 Mb/s. Since the manufacturer LeCroy supplied with their devices motherboard i845 and  i865, which having probably only 33 MHz bus, they could not just tell about the possibility of working an interface card at a frequency of 66 MHz.
Someone could test it?

[dxl]

Hi All,

i've added the driver for win7 to this post. There are a few things:

- Serial port for Touchscreen isn't working - will fix that during the weekend, inf file needs to be adjusted
- It will no longer be installed with the AladdinDriverInstaller.exe, as this fails on win7

- Fire up device manager
- Check View->Show Hidden Devices
- Uninstall all lecroy drivers on win7, make sure to check the 'delete driver' checkbox in the uninstall device confirmation.
- after that, you will see a Unidentified device after reboot/rescan
- right click, update driver -> select directory with the extracted zip file
- install driver
- it should automatically install all the other drivers (FrontPanel, I2C, Acquisition, etc). If not, install them as legacy driver by right clicking the computer name on top of the tree.

Hope these quick instructions help.

For the Technically interested, here's the reason why the driver doesn't work on Win7:

The LeCroy PCI card is actually a Multifunction device, but has only one memory range/interrupt which will be shared between drivers. This is done on Windows version <= Windows XP by adding a 'ResourceMap' Entry to the pci card driver inf file. LeCroy installs a filter driver 'LeCAladdinMFResfilter.sys' which fills out the memory ranges that each child driver uses. However, that doesn't seem to work on Windows 7 anymore.

Instead, starting with Windows XP there's  a new inf directive: 'VaryingResourceMap' which we need here. So we have to get rid of the filter driver, and specify the resources for each driver in the pci card inf file with Varying ResourceMap:

before:

Code: [Select]

HKR, LecDevParPort,HardwareID,,MF\ALADDIN_PARPORT_DEV
HKR, LecDevParPort,ResourceMap,1,00
HKR, AladdinFanControllerDrv,HardwareID,,MF\ALADDIN_FAN_CONTROLLER_DEV
HKR, AladdinFanControllerDrv,ResourceMap,1
HKR, I2CDrv,HardwareID,,MF\I2C_DEV
HKR, I2CDrv,ResourceMap,1, 00, 06
HKR, AladdinFrontPanelDrv,HardwareID,,MF\ALADDIN_FRONTPANEL_DEV
HKR, AladdinFrontPanelDrv,ResourceMap,1, 00
HKR, YLecDevAladdinSuperIO, HardwareID,,  MF\ALADDIN_SUPERIO_DEV   ;lpc
HKR, YLecDevAladdinSuperIO, ResourceMap, 1, 00, 06
HKR, ZAladdinAcquisition, HardwareID,,  MF\ALADDIN_AQUISITION_DEV  ;acquisition
HKR, ZAladdinAcquisition, ResourceMap, 1, 04, 06

After modification:

Code: [Select]

HKR, LecDevParPort,HardwareID,,MF\ALADDIN_PARPORT_DEV
HKR, LecDevParPort,VaryingResourceMap,1,00, 70, 01, 00, 00, 04, 00, 00, 00
HKR, AladdinFanControllerDrv,HardwareID,,MF\ALADDIN_FAN_CONTROLLER_DEV
HKR, AladdinFanControllerDrv,VaryingResourceMap,1,00,80,01,00,00,01,00,00,00
HKR, I2CDrv,HardwareID,,MF\I2C_DEV
HKR, I2CDrv,VaryingResourceMap,1, 00, f0, 01, 00, 00, 10, 00, 00, 00
HKR, I2CDrv, ResourceMap, 1, 06
HKR, AladdinFrontPanelDrv,HardwareID,,MF\ALADDIN_FRONTPANEL_DEV
HKR, AladdinFrontPanelDrv,VaryingResourceMap,1, 00, 0e, 01, 00, 00, 02, 00, 00, 00
HKR, YLecDevAladdinSuperIO, HardwareID,,  MF\ALADDIN_SUPERIO_DEV   ;lpc
HKR, YLecDevAladdinSuperIO, VaryingResourceMap, 1, 00, 00, 00, 00, 00, 00, 01, 00, 00
HKR, YLecDevAladdinSuperIO, ResourceMap, 1, 06
HKR, ZAladdinAcquisition, HardwareID,,  MF\ALADDIN_AQUISITION_DEV  ;acquisition
HKR, ZAladdinAcquisition, ResourceMap, 1, 04, 06

And all the references for LeCroyMFResfilter.sys needs to be removed from the inf files.

[dxl]

...made the software complain that the calibration data was moved.

Sven, are you getting the same message about re-calibrating the scope as on the attached screenshot? Let me know if you can figure it out... I'm still struggling with mine.

As far as FP driver goes,  I've noticed that XStream complains about the missing driver version. It might be pure cosmetic and probably doesn't affect its functionality, but maybe you can consider adding VERSIONINFO resource to the driver?

Yes, got exactly the same message. I've now recreated the logical partition, and moved that to the end of the disk. So the position on the disk in terms of sectors doesn't matter, but the partition numbering does.

Code: [Select]

bash-3.2$ strings FrontPanel.mauiLog  | sort | uniq
CFrontPanelServer::Front Panel Version Number invalid: 0x0
Failed to reset the front panel controler
FrontPanel
FrontPanel CMFP414PCIAladdinDrv
MFP Reset Failed
MFP version number failed
MLOG
bash-3.2$


I think i've seen that as well one my scope, but didn't bothered as the driver works quite well for me (now since about 8 months). If i'm bored i'll look into that, but i would rather like to rewrite all the drivers so you can run it on 64 bit windows 7. But that would take some time.

[dxl]

... What kind of CPU load do you see when you use 3D mode like the one you demo in your youtube video? On my WP7K1 with Intel i7-2600 I'm able to bring one of the cores to 100% and it slows down the visuals. I'm curious if it's really CPU-bound or the graphic chip is a culprit?  I'm still using Intel HD graphic chip integrated on the CPU...

-albertr

I'll check later. But I think the problem may also be insufficient bandwidth lines Gigabit Ethernet and expansion slots PCI 2.0 (33 MHz), connecting the motherboard CPU to the  Acquisition Board in the system X-Stream v.1. PCI-slot is the bottleneck.

I noticed that the "interface card LeCroy" has a universal PCI-slot, with two types of slits. It is usually made to be compatible with both PCI standards - 5V / 33MHz and 3.3V / 66MHz. Bandwidth the first type - 133 Mb/s, while the second - 266 Mb/s. Since the manufacturer LeCroy supplied with their devices motherboard i845 and  i865, which having probably only 33 MHz bus, they could not just tell about the possibility of working an interface card at a frequency of 66 MHz.
Someone could test it?

FWIW, i'm using an Asus P8Q77 in my LeCroy, without any problems. Haven't done any graphic performance tests though.

[albertr]

i've added the driver for win7 to this post. There are a few things:

- Serial port for Touchscreen isn't working - will fix that during the weekend, inf file needs to be adjusted

That was quick! Thanks, Sven!

For a serial driver issue,  can any other serial port can be used instead? Isn't it a matter of reconnecting the serial pass-thru cable from LeCroy "DVI" card?

-albertr

[albertr]

Yes, got exactly the same message. I've now recreated the logical partition, and moved that to the end of the disk. So the position on the disk in terms of sectors doesn't matter, but the partition numbering does.

Ah... so does it have to be a second partition? Logical or physical - does it matter?

-albertr

[dxl]

I'm not sure whether it has to be on a logical partition. I would rather think that they store the partition location during calibration and so it can't be moved later.

[Converter]

Hi All,

i've added the driver for win7 to this post. There are a few things..

Huge respect!

FWIW, i'm using an Asus P8Q77 in my LeCroy, without any problems. Haven't done any graphic performance tests though.

The manufacturer LeCroy declares that the old PCI bus 33 MHz is the bottleneck. Probably in 2001, they did not have other possibility to select a more suitable bus. And it can cause premature slowing of renovation oscillograms in the case of a large array of data (working with a large volume cache). Not by chance in X-Stream2 now uses PCI-e. I still have no way to check, I just wanted to set the controller in the slot of the server board (PCI 66 MHz, 3.3 V) to see if it will work.

[Converter]

i've added the driver for win7 to this post. There are a few things:

- Serial port for Touchscreen isn't working - will fix that during the weekend, inf file needs to be adjusted

That was quick! Thanks, Sven!

For a serial driver issue,  can any other serial port can be used instead? Isn't it a matter of reconnecting the serial pass-thru cable from LeCroy "DVI" card?

-albertr

In fact,it is easy to replaced by usb universal card - controller for 4-pin resistive matrix. It costs $ 5
I physically lost one PCB in my unit (to which connected the original touchscreen), so I experienced Chinese product, and it works well. There Included is a driver for all operating systems.

https://youtu.be/b8R9OBGDLTM

[dxl]

I fixed the touchscreen issue. It's a matter of adding a *PNP0501 device to the inf file. Attached a new version.

[dxl]

Used the Wavepro for a few hours now and haven't seen any problems with the drivers on windows 7. Hope it stays that way 

[Converter]

Used the Wavepro for a few hours now and haven't seen any problems with the drivers on windows 7. Hope it stays that way 

Thank you for good news.
You have used the latest version X-Stream 8.1.0.1 with LeCroy site?(http://teledynelecroy.com/support/softwaredownload/documents.aspx?sc=11)
This software contains everything you need to install on pure operating system and the full functionality of your drivers (without upgrade pre-installed older versions Xstream)? Just someone who wrote that latest version of update does not contain some important parts required for a clean installation.
(If it had been possible to use Xstream64 8.0.1.2  )

[albertr]

I fixed the touchscreen issue. It's a matter of adding a *PNP0501 device to the inf file. Attached a new version.

Thanks, Sven! You rock! 

-albertr

[albertr]

I'm not sure whether it has to be on a logical partition. I would rather think that they store the partition location during calibration and so it can't be moved later.

Sorry for keeping beating up the dead horse - but can you detail what did you do to fix this problem? I've just tried to move my calibration partition around, it's used to be the third physical partition, now it's the second one. The first physical partition is the boot partition with Win XP installed. Still getting the same error. Here's my partitions layout:

Code: [Select]

root@WP7K1:~# fdisk -l /dev/sda
Disk /dev/sda: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00091b8b

Device     Boot     Start       End   Sectors  Size Id Type
/dev/sda1  *         2048 200706047 200704000 95.7G  7 HPFS/NTFS/exFAT
/dev/sda2       200706048 282628095  81922048 39.1G  b W95 FAT32
/dev/sda3       282628096 483332095 200704000 95.7G  7 HPFS/NTFS/exFAT
/dev/sda4       483332096 500117503  16785408    8G 83 Linux
root@WP7K1:~#

Is your calibration partition formatted as FAT32 or NTFS? Any help is greatly appreciated!

-albertr

[albertr]

Well, it's rather interesting... I changed my calibration partition to be the second partition. Tried as both physical partition and as an extended partition. Formatted as either FAT32 or NTFS. Still getting the same error. Obviously, it's always mounted on drive D:\ and has "USERDATA" as a volume name. I have verified that XStream is reading and writing the config files to this filesystem. In fact, I can back up and restore the calibration data back using XStream "Critical files backup" procedure which is the official procedure to restore calibration data when changing the hard drive. I'm starting to suspect that it's going to be something else... what am I missing?

I've checked all XStream log files, and the only errors I see are the following ones from BoardTest log file:

Code: [Select]

0       2.25.2017  16:57:29     Informational   FeBTDC1 Read From Disk Image D:\Calibration\FeBTDC1.btd successful     
 1      2.25.2017  16:57:29     Warning FeBTDC1:UpdateBtdInEEpromFromEEprom     Board Test Structure not Identified!!   Thermal_Tail20M*
 2      2.25.2017  16:57:29     Warning FeBTDC1:UpdateBtdInEEpromFromEEprom     Board Test Structure not Identified!!   Thermal_Tail200M
 3      2.25.2017  16:57:29     Warning FeBTDC1:UpdateBtdInEEpromFromEEprom     Board Test Structure not Identified!!   Thermal_Tail1G**
 4      2.25.2017  16:57:29     Warning FeBTDC1:UpdateBtdInEEpromFromEEprom     Board Test Structure not Identified!!   Thermal_Tail3G**
 5      2.25.2017  16:57:29     Warning FeBTDC1:UpdateBtdInEEpromFromEEprom     Board Test Structure not Identified!!   Thermal_Tail5G**
 6      2.25.2017  16:57:29     Warning FeBTDC1:UpdateBtdInEEpromFromEEprom     Board Test Structure not Identified!!   Improved_WM_FE**
 7      2.25.2017  16:57:29     Warning FeBTDC1:UpdateBtdInEEpromFromEEprom     Board Test Structure not Identified!!   RelayClicks*****
 8      2.25.2017  16:57:29     Error   FeBTDC1 UnIdentified Structures !!      No of Identified structures        : 30
No of UnIdentified structures  : 7
 9      2.25.2017  16:57:29     Warning FeBTDC1:UpdateBtdInEEpromFromEEprom     Board Test Structure not Identified!!   Thermal_Tail20M*
 10     2.25.2017  16:57:29     Warning FeBTDC1:UpdateBtdInEEpromFromEEprom     Board Test Structure not Identified!!   Thermal_Tail200M
 11     2.25.2017  16:57:29     Warning FeBTDC1:UpdateBtdInEEpromFromEEprom     Board Test Structure not Identified!!   Thermal_Tail1G**
 12     2.25.2017  16:57:29     Warning FeBTDC1:UpdateBtdInEEpromFromEEprom     Board Test Structure not Identified!!   Thermal_Tail3G**
 13     2.25.2017  16:57:29     Warning FeBTDC1:UpdateBtdInEEpromFromEEprom     Board Test Structure not Identified!!   Thermal_Tail5G**
 14     2.25.2017  16:57:29     Warning FeBTDC1:UpdateBtdInEEpromFromEEprom     Board Test Structure not Identified!!   Improved_WM_FE**
 15     2.25.2017  16:57:29     Warning FeBTDC1:UpdateBtdInEEpromFromEEprom     Board Test Structure not Identified!!   RelayClicks*****
 16     2.25.2017  16:57:29     Error   FeBTDC1 UnIdentified Structures !!      No of Identified structures        : 30
No of UnIdentified structures  : 7
...

Can someone please check to see if you are getting the same error messages logged to D:\Logs\Boardtest.mauiLog file?

Here's my current partition layout with the calibration partition being on the extended partition:

Code: [Select]

DISKPART> list part

  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    Primary             96 GB  1024 KB
  Partition 2    Extended            39 GB    96 GB
  Partition 3    Logical             39 GB    96 GB
  Partition 4    Primary             96 GB   135 GB
  Partition 5    Unknown              8 GB   230 GB

DISKPART>


Code: [Select]

Command (m for help): p
Disk /dev/sda: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00091b8b

Device     Boot     Start       End   Sectors  Size Id Type
/dev/sda1  *         2048 200706047 200704000 95.7G  7 HPFS/NTFS/exFAT
/dev/sda2       200706048 282628095  81922048 39.1G  f W95 Ext'd (LBA)
/dev/sda3       282628096 483332095 200704000 95.7G  7 HPFS/NTFS/exFAT
/dev/sda4       483332096 500117503  16785408    8G 83 Linux
/dev/sda5       200708096 282628095  81920000 39.1G  7 HPFS/NTFS/exFAT

Partition table entries are not in disk order.

Command (m for help):

-albertr

[dxl]

Used the Wavepro for a few hours now and haven't seen any problems with the drivers on windows 7. Hope it stays that way 

Thank you for good news.
You have used the latest version X-Stream 8.1.0.1 with LeCroy site?(http://teledynelecroy.com/support/softwaredownload/documents.aspx?sc=11)
This software contains everything you need to install on pure operating system and the full functionality of your drivers (without upgrade pre-installed older versions Xstream)? Just someone who wrote that latest version of update does not contain some important parts required for a clean installation.
(If it had been possible to use Xstream64 8.0.1.2  )

Hi,

it should work to install a clean Win7, the XStream drivers afterwards, and than the LeCroy XStream 8.1 Release. However i didn't test this as i did all driver debugging/inf file rewriting on my scope, so i don't have a fresh copy of Win7. And i'm to lazy to erase the Win7 and reinstall everything again . So it would be nice if users report whether the package works for them or whether there are still some problems. Oh, and i'm using the XStream 8.1 32 bit software on my scope.

I also noted that i didn't put my version of the frontpanel driver in the last zip, so here's another one

[dxl]

Well, it's rather interesting... I changed my calibration partition to be the second partition. Tried as both physical partition and as an extended partition. Formatted as either FAT32 or NTFS. Still getting the same error. Obviously, it's always mounted on drive D:\ and has "USERDATA" as a volume name. I have verified that XStream is reading and writing the config files to this filesystem. In fact, I can back up and restore the calibration data back using XStream "Critical files backup" procedure which is the official procedure to restore calibration data when changing hard drive. I'm starting to suspect that it's going to be something else... what am I missing?

I've checked all XStream log files, and the only errors I see are the following ones from BoardTest log file:

Code: [Select]

0       2.25.2017  16:57:29     Informational   FeBTDC1 Read From Disk Image D:\Calibration\FeBTDC1.btd successful     
 1      2.25.2017  16:57:29     Warning FeBTDC1:UpdateBtdInEEpromFromEEprom     Board Test Structure not Identified!!   Thermal_Tail20M*
 2      2.25.2017  16:57:29     Warning FeBTDC1:UpdateBtdInEEpromFromEEprom     Board Test Structure not Identified!!   Thermal_Tail200M
 3      2.25.2017  16:57:29     Warning FeBTDC1:UpdateBtdInEEpromFromEEprom     Board Test Structure not Identified!!   Thermal_Tail1G**
 4      2.25.2017  16:57:29     Warning FeBTDC1:UpdateBtdInEEpromFromEEprom     Board Test Structure not Identified!!   Thermal_Tail3G**
 5      2.25.2017  16:57:29     Warning FeBTDC1:UpdateBtdInEEpromFromEEprom     Board Test Structure not Identified!!   Thermal_Tail5G**
 6      2.25.2017  16:57:29     Warning FeBTDC1:UpdateBtdInEEpromFromEEprom     Board Test Structure not Identified!!   Improved_WM_FE**
 7      2.25.2017  16:57:29     Warning FeBTDC1:UpdateBtdInEEpromFromEEprom     Board Test Structure not Identified!!   RelayClicks*****
 8      2.25.2017  16:57:29     Error   FeBTDC1 UnIdentified Structures !!      No of Identified structures        : 30
No of UnIdentified structures  : 7
 9      2.25.2017  16:57:29     Warning FeBTDC1:UpdateBtdInEEpromFromEEprom     Board Test Structure not Identified!!   Thermal_Tail20M*
 10     2.25.2017  16:57:29     Warning FeBTDC1:UpdateBtdInEEpromFromEEprom     Board Test Structure not Identified!!   Thermal_Tail200M
 11     2.25.2017  16:57:29     Warning FeBTDC1:UpdateBtdInEEpromFromEEprom     Board Test Structure not Identified!!   Thermal_Tail1G**
 12     2.25.2017  16:57:29     Warning FeBTDC1:UpdateBtdInEEpromFromEEprom     Board Test Structure not Identified!!   Thermal_Tail3G**
 13     2.25.2017  16:57:29     Warning FeBTDC1:UpdateBtdInEEpromFromEEprom     Board Test Structure not Identified!!   Thermal_Tail5G**
 14     2.25.2017  16:57:29     Warning FeBTDC1:UpdateBtdInEEpromFromEEprom     Board Test Structure not Identified!!   Improved_WM_FE**
 15     2.25.2017  16:57:29     Warning FeBTDC1:UpdateBtdInEEpromFromEEprom     Board Test Structure not Identified!!   RelayClicks*****
 16     2.25.2017  16:57:29     Error   FeBTDC1 UnIdentified Structures !!      No of Identified structures        : 30
No of UnIdentified structures  : 7
...

Can someone please check to see if you are getting the same error messages logged to D:\Logs\Boardtest.mauiLog file?

I've seen them on my scope before, but right it doesn't show them. So i guess they only appear if the caldata is invalid. In which Tab of the Log files do you see that log?

[joeqsmith]

 

[albertr]

I've seen them on my scope before, but right it doesn't show them. So i guess they only appear if the caldata is invalid. In which Tab of the Log files do you see that log?

It's Utilities->Service->Production->Show all logs->Boardtest tab or you can access it directly as D:\Logs\Boardtest.mauiLog file.

Sven, thank you very much for your work on Windows 7 support!  I'm happy to report that it works beautifully on my WP7K1 (non "A" model) just as you described. Better yet, my high CPU load problem in "3D" persistence mode under Win XP is totally gone under Win 7! I guess the Intel HD graphic drivers in Win XP might be the ones to blame for high CPU usage? Anyways, if I was working for LeCroy, I would hire you without hesitation for for all your work you did to make these fine scopes even better. I hope someone from LeCroy is reading this forum and taking notes 

Also, my calibration issue is somehow resolved after installing XStream under Windows 7. I'm using the same calibration partition mounted as "D:\" drive in both Win XP and Win 7, but after installing XStream software under Win 7, I'm not seeing this error any more. If I re-boot back into Win XP, the error comes back. Weird... I guess during XStream installation they store calibration partition info somewhere? If anyone wants to look further into it, I'm attaching my Boardtest logs below...

Anyways, now with Sven's wonderful work on Windows 7 support, I'm not looking back to Win XP.  Bye-bye XP, welcome Win 7! 

-albertr

[dxl]

Glad to hear that Windows 7 works for you and the calibration issue is resolved . Now if anyone feels like stepping into a new adventure, he can install Windows 8 

[albertr]

...
I also had some graphics issues, in particular with the 3D display mode... but these went away with the upgrade to Windows 7...

Ah just noticed that old post from darkstar49... He's using WR6050, but I guess it could be the same issue with Intel HD graphic under Win XP?

-albertr

[Converter]

...
I also had some graphics issues, in particular with the 3D display mode... but these went away with the upgrade to Windows 7...

Ah just noticed that old post from darkstar49... He's using WR6050, but I guess it could be same issue with Intel HD graphic under Win XP?

-albertr

And why you did not use the opportunity to apply discrete graphics cards that have never had a problem with the drivers? In addition, there are much easier to connect internal display in the additional connector low-profile graphics card.
In attachment the example of upgrading my generator LeCroy LW420A

[albertr]

Well, it looks like the Intel HD graphic performance issue is isolated to Windows XP and has been already addressed in Win 7, so it's not an issue anymore... 

PCI-e graphic card is definitely an option, do you know of any card that has both LVDS and DVI (or DP) output ports?

-albertr

[Converter]

PCI-e graphic card is definitely an option, do you know of any card that has both LVDS and DVI (or DP) output ports?

Sir, you never need to search "lvds" on the graphics card or motherboard. lvds-serial differential signal usually form discrete modules "LCD Controller" (scaler). In these at the input signal VGA (D-Sub 15) or DVI, and the output you get a 6-bit or 8-bit (or 2 ? 6 bits) LVDS-signal, or a parallel TTL-signal format for older models LCD-matrix . You can easily buy them separately: http://www.ebay.com/sch/i.html?_from=R40&_trksid=p2050601.m570.l1313.TR0.TRC0.H0.TRS0&_nkw=VGA+LCD+Controller&_sacat=0
The same modules you can see inside any external monitor. I about it wrote earlier that I use scaler-modules from old monitors 15 "1024x768. Resolution format scaler and LVDS-connector the PIN-format should sootvetsvovat your matrix. But there are also universal scalers, where you can set the desired resolution using the jumpers, or change the firmware ROM.
For modern DP LCD-matrix scalers-module is not needed. Enough to buy a graphics card with the DP-output and adapter for ribbon cable matrix.

Was once I had a problem to set in the old logic analyzer Tektronix TLA704 more modern LCD-matrix LTM10C348F - 10,4 "800x600 from the laptop Fujitsu LIFEBOOK B2154 (generally I also replaced the motherboard from there TLA721, thus completely converting TLA704 to TLA715).
The problem is that the video system was built with a parallel TTL output signal on the motherboard. To convert TTL to LVDS was purchased "converter board TTL / LVDS ID250" ($ 12.00), based on SN75LVDS83 chip (http://ibt.ca/v2/items/id250/index.html).
And it worked perfectly. Attaching photo.

[albertr]

Sir,

Mozhno i na ty... 

I see your point. A little bit of history... When I got this scope about a month ago I didn't know much about it. Then I found Sven's post about upgrading his motherboard/CPU on this forum. That got me started. If I was about to do it all over again, would I use the same motherboard-CPU? Probably not... I think anything more than 2 cores is useless for XStream, in fact I ended up disabling two cores on my i7-2600 CPU for very same reason. Do I need an industry-grade motherboard with integrated LVDS output? Probably not, any micro-ATX board with at last one PCI slot would do. Why I was using a motherboard with integrated LDVS port? Because I was able to find a used one dirty cheap on EBay with free shipping. I'm not using any of its 6 serial ports, nor programmable watchdog timer or 6 programmable GPIO pins... As a matter of fact, the only useful feature of this "industry-grade" board I'm using is a Win32 library to adjust backlight intensity of LCD screen.

But you are absolutely right, it should be possible to convert video signal from DVI to LVDS LCD, assuming you have time to find (or build) a converter board which will work with your LCD screen (6 vs 8 bit per color, screen resolution, etc). And you will need to make the backlight inverter work too.

-albertr