dScope Series III FAQ, Tips and Techniques

Installation Questions (click on the '+' to expand the answer)
	+	How do I Install the software from the CD?
Answer Insert the CD into your CD drive. If you have 'Auto-run' enabled, then the installation will start automatically. Follow the on-screen instructions. If 'Auto-run' is not enabled, select the 'Run' option from the Start menu. Type in ' D:\Setup ' (where D is the drive letter of your CD-ROM drive) and click OK to start the installation. Follow the on-screen instructions. Note that on Windows XP, the process is slightly different. See also 'How do I install the software on Windows XP?' (ID = 0002)
	+	How do I install the software from the web download?
Answer Download the ds3_VXXX.exe file (where 'XXX' represents the software version number). Double-click on it. This will extract all the installation files into a temporary directory and then run the 'setup' program. Follow the on-screen instructions. The current release of the sofware is available from the Downloads page. (ID = 0007)
	+	When I plug in the hardware, it brings up the 'Found new hardware' wizard. What do I do?
Answer Firstly, make sure that the dScope software has been installed. If not, then Select 'Cancel' from the wizard and install the software from the CD or the web download. On Windows XP, the 'Found new hardware' wizard will display even if the dScope software has been installed. Simply select 'Next/Finish' for each page of the Wizard, until the installation is completed. (ID = 0008)
	+	How do I install the software on Windows XP?
Answer As with other operating systems you must install the dScope software before connecting the hardware. The installation differs in that Windows XP requires device drivers to be digitally signed by Microsoft, which the dScope drivers currently aren't. After you have installed the dScope software and connected dScope for the first time, Windows XP will bring up the "Found new Hardware" wizard. Simply select "Next" at each point in this wizard to allow the device driver to be automatically loaded. During the installation, you may be warned that the dScope device driver has not passed Windows Logo testing. Simply click "Continue" and the installation process will continue. See also "What is Windows Logo testing, and how does it affect the dScope?" (ID = 0009)
	+	What is Windows Logo testing, and how does it affect the dScope?
Answer For seamless installation into the Windows XP operating system, Microsoft requires that Device Drivers are digitally signed (indicating that they have been approved by Microsoft). The dScope drivers are not currently signed, because the signing process cannot easily be reconciled with the dual-driver "renumeration" process that the dScope uses. This dual driver/renumeration arrangment means that device firmware can be easily downloaded into the dScope in the background when it is first started up. It also allows new firmware to be shipped with new software releases if necessary. We are currently investigating the process for getting our device drivers signed by Microsoft, but for the time being, the installation process will require you to step through the "Found New Hardware" wizard when the software is first installed. During the installation, you may be warned that the dScope device driver has not passed Windows Logo testing. Simply click "Continue" and the installation process will proceed. (ID = 0010)
	+	Why does Windows find the hardware twice when it is first installed?
Answer The dScope system works by behaving as two separate hardware units. When it is first switched on, a loader driver will load (dsloader.sys) which downloads some firmware into the dScope box. The box then tells windows that it is new hardware, and the usual dScope driver (dsusbdrv.sys) will load. In this way, new releases of the firmware can be shipped with software, and the hardware does not need to be upgraded when new firmware becomes available. (ID = 0011)
	+	When I switch on the hardware for the first time, the 'Found New Hardware' wizard tells me it can't install the hardware.
Answer You need to install the dScope software first. Ensure that the hardware is switched OFF while you do so. (ID = 0012)
	+	When I run the dScope software, it can't find the hardware.
Answer Check that the hardware is switched on, and the USB is connected - the 'on' LED should be red. If you plugged in the hardware before installing the software, then Windows will not have linked the dScope hardware to the software correctly. Switch off the hardware, un-install the software, and restart Windows. Then install the software again, and turn on the hardware. If you are still experiencing problems then please contact Prism Sound. If the hardware has been working properly but has since stopped, then see also the FAQ in the "General Questions" section entitled 'My dScope was working properly, but now it can't contact the hardware' (ID = 0013)
	+	I deleted an old version of dScope, and now the software won't install.
Answer If the software is simply deleted rather than un-installed, Windows thinks that the software is still there because it still has references to it in the registry. The new installation tries to un-install it but since it doesn't exist, the installation fails. To fix this, please see this technical tip. (ID = 0014)
	+	During the installation, I get a message that says 'Error 1904.Module C:\Windows\System32\ScriptDlg.dll failed to register. HRESULT -21470224770. Contact your support personnel.'
Answer On Windows 2000 and XP, the ScriptDlg.dll ActiveX control used with the dScope Scripting system can fail to register. This may be because the installation has been performed without Administrator privileges. Try un-installing the software, then log on as an Administrator and re-install the software. Alternatively, you can manually register the DLL after installation. Select 'Ignore' to the error message, and the installation of the rest of the software will continue successfully. After installation, select 'Run' from the Start menu. Type in the following: regsvr32.exe ScriptDlg.DLL to manually register the control. (ID = 0015)
	+	When I run another program, I get a message saying 'dScope Series III -Preparing to install' before the program runs.
Answer This can occur if a previous installation has been cancelled. To fix this problem, you need to clean out the registry entries that make Windows think the old dScope software is still installed. For details of how to do this, please refer to this technical tip. (ID = 0016)
	+	When I switch on the dScope software, it recognises a USB device ' Prism Sound dScope Series III - uninitialised (dsloader.sys)' but then doesn't get any further.
Answer We have found that a certain notebook PC (Compaq Evo N1015v) exhibits this problem. We are not aware of any other machines that this is a problem on. The reason is a high capacitance in the host end of the USB link, and can usually be fixed by using a shorter USB cable. (ID = 0017)
	+	I know there has been a new software release, but I haven't been informed about it.
Answer You need to register your dScope for this to happen. We will then keep you informed of future software releases and upgrades. You can register your dScope here (ID = 0025)
	+	Does dScope work with Windows Vista?
Answer Yes. From version 1.21 dScope will work with Vista. (ID = 0047)
	+	Can I try the software without the hardware?
Answer Yes, although obviously you won't be able to make any measurements. The software is free and running it is one of the best ways of finding out about dScope. It can be easily un-installed using the Windows "add/remove programs" dialogue. You can also have the software installed on as many computers as you like and you don't have to register the installations. You can download the latest version of dScope software here. (ID = 0048)
	+	Do I need to un-install the old software before installing a new version?
Answer No. The installer will update your installation looking after all this for you and will not remove your configurations or scripts etc. If you make changes to the supplied scripts or configurations, however, you should save them with a new name or they will be overwritten when a new version is installed. It is good practice to keep backups of your important files in any case, and we recommend this is done before you upgrade your installation of dScope. Note also that if the dScope is being used in a "mission critical" application, you should test any new software offline with your scripts and configurations before applying it. Note that configurations saved with newer software versions can not normally be loaded into older versions of dScope software, but older configurations can be loaded into newer versions of software. (ID = 0049)
	+	Are dScope Configurations backwards compatible?
Answer Yes, you can load older Configurations into newer versions of dScope software. The reverse is usually not true: Configurations saved with a newer version of software often can not be loaded with older versions of software. (ID = 0050)
	+	What is "Encoded Stream Generation"?
Answer This refers to the ability of the dScope generator to play out digital streams that are encoded with Dolby Digital or DTS. These are stored as wavetables that are pre-encoded and can be selected from an interface that simplifies the selection of the required waveform. Due to its size (in MB), this feature is not automatically included in the dScope software, but is included as a separate download. The download includes an installer that adds the files and the user interfaces to an existing dScope installation. More information is available in the dScope Applications manual which is available from the downloads page. (ID = 0053)
	+	How do I get started with dScope?
Answer For a quick start guide to using dScope for the first time, please see this technical note (ID = 0054)
	+	How do I update the dScope firmware?
Answer You don't need to. The firmware is automatically managed by the software behind the scenes. When you update the software, it will automatically update the firmware if necessary when it is run for the first time. It does this in the few seconds while the "Accessing Hardware" message is on screen when you first start the software. (ID = 0055)

Hardware Questions (click on the '+' to expand the answer)
	+	What is dS-NET?
Answer dS-NET is a communication protocol used by the Prism Sound dScope Series III to control peripherals. It is a proprietary, open protocol which can use RS232 or RS485 hardware. In practice, on the dScope it is normally configured to run with RS232. It is possible to use a PC serial port to control any dS-NET device. For more information, see this technical tip. (ID = 0042)
	+	Can I control dS-NET peripherals from a PC serial port?
Answer Yes, however we do not provide any software to do this as the control of the peripherals is integrated into the dScope software. If you wish to do this, you will need to set up the control of the devices manually using the dS-NET protocol which is available here (ID = 0045)
	+	Where can I find details of the dS-NET protocol?
Answer The dS-NET protocol is available here. (ID = 0046)

Scripting Questions (click on the '+' to expand the answer)
	+	How do I get started using VBScript?
Answer To find out how to use the VBScript language, you can download a VBScript help file directly from the Microsoft web site. Please note that this link moves periodically. If it doesn't work, try searching the Microsoft site for script56.chm (ID = 0001)
	+	How do I access the 'My Documents' directory from a script?
Answer You need to use the Windows Shell object from your script, to access the Special Folders. Further information on the Window Shell object can be found in the Microsoft MSDN WshShell Object Documentation (ID = 0003)
	+	Under Asian versions of Windows, the 'Applications' button gives an error message and doesn't run.
Answer The symbol used to denote 'microVolts' (i.e a little 'u' with a tail) is treated together with the character after it as a special symbol (e.g. a Chinese character). When Asian versions of Windows are used to run the script, the character in the script is interpreted as a special symbol, which stops the script from being interpreted correctly. To fix this, open the '<dscope>\Scripts\Automation\AES17\AES17_Useful.dss' script using the dScope Script Edit window. Near the top, you will find a line defining 'strMicro' as a constant. You need to change the line to read: Const strMicro = "u" This will cause the script to use a standard character (the letter 'u'), so it won't be interpreted as a special symbol. (ID = 0004)
	+	How do I use files and folders from my script?
Answer Most of the things you need to do with files and folders can be achieved using the FileSystemObject. For more information, see Microsoft MSDN documentation on the FSO (ID = 0018)
	+	I can't control Microsoft Office applications from my script.
Answer Access and Excel can be automated from the dScope using the DAO (Database Access Objects) object. If scripts using this object do not run correctly, then firstly check that these Office applications were installed with 'Database Access Objects' selected. Older versions of the DAO object could be created using CreateObject("DAO.DBEngine") . This would automatically access the latest version of the engine found on the machine. However, in later versions of Microsoft Office, Microsoft has renamed this object with a specific version number, for example "DAO.DBEngine.35 " or " DAO.DBEngine.36 ". You will need to create this more specific object for the script to work. (ID = 0019)
	+	When I start up the dScope from another application (e.g. Visual Basic), I get a run-time error. Why is this?
Answer When you start the dScope software from another application, you must give it time to initialize before trying to access any of the dScope's properties or methods. To do this, use the 'IsInitialized' function. (ID = 0020)
	+	I need to automate some tests, but I don't have time to write scripts myself. What do I do?
Answer Prism Sound offers an application development service in which staff engineers will assist with code development for test automation. Please contact Prism Sound on 01223 424988, or email us at sales@prismsound.com (ID = 0021)
	+	Where can I find examples of scripts and scripting techniques?
Answer There is a selection of scripts and examples available on the scripting page. (ID = 0043)
	+	Why is my script returning inaccurate results?
Answer If your results retrieved from a script appear to be erratic and variable, check that the "Use settling details when getting Result values from scripts" option is enabled. This is checked by default and there are very few instances when it should be disabled. With this option unchecked, the script will get the first results that the dScope has, without any checking being done that the results are settled. This will tend to give very fast readings, but they might not be stable settled results. This option is found in the "Utility" menu under "Options" in the "Miscellaneous" tab. (ID = 0052)
	+	How do I get started automating dScope?
Answer There is an introduction to dScope scripting and automation available here (ID = 0056)

General Questions (click on the '+' to expand the answer)
	+	I want to open a lot of windows, but don't have enough space on the screen.
Answer The dScope display has five separate 'Pages' that can contain different windows. For example, you may wish to have the Trace window open on one Page, Signal Analysis details on another, and the generator setup on yet another Page. In addition to this, parts of a large settings window can be dragged off using the mouse to create a smaller window containing only the details you are interested in. (ID = 0022)
	+	What is "D/A line-up"?
Answer The D/A line-up enables the dScope to show analogue amplitudes in digital units, or vice versa. To do this, it needs to know the analogue equivalent of a full-scale digital signal (0dBFS). The D/A line-up field allows this to be specified. For example, if your Equipment Under Test (EUT) has a maximum output level of 24dBu, you could generate or analyze signals at -1dBFS, which would be 1dB below the maximum output level of the device. For a fuller discussion of D/A line-up, see this technical tip. (ID = 0023)
	+	My dScope was working properly, but now the computer can't seem to connect to the dScope hardware.
Answer This is most likely to happen in Windows XP when the power management settings allow the operating system to turn off the power to the USB ports. To fix this, open the Device Manager (either using the System icon in the Control Panel, or by right-clicking on the My Computer icon on the Desktop. In the Device Manager, select 'Universal Serial Bus Controllers > USB Root Hub > Power Management' and UNCHECK the box labelled "Allow the computer to turn off this device to save power". Ensure that you do this for all "USB Root Hub" entries in the "Universal Serial Bus" section of the tree. (ID = 0024)
	+	No signal/the wrong signal is coming out of the dScope's outputs.
Answer Check that the outputs are turned on. This may be done using the Signal Generator panel, which has On and Off buttons for each channel. If the digital outputs are not working, then open the Digital Outputs panel and check that they are not muted. For analogue outputs, open the Analogue Outputs panel and check that they are not muted. If using BNC connectors, check that they are plugged into the correct digital or analogue output connectors (and not the Monitor Outputs, which also have BNC connectors). (ID = 0026)
	+	How do I configure the dScope inputs and outputs for balanced/unbalanced operation and grounding?
Answer The dScope has very flexible input and output circuitry and it is important to make sure that it is configured correctly for the measurement you wish to undertake. For more details, please see this technical tip. (ID = 0028)
	+	dScope FFT measurements are very slow or not triggering
Answer There are a couple of things that can cause this. The most obvious is that large FFTs take longer to capture and process (also check the trigger parameters to make sure that the signal will actually trip the trigger) Another possibility is that, with analogue signals with significant variation in amplitude, the auto-ranging is preventing the device from capturing a whole buffer of data before the input range changes. The dScope automatically rejects any buffer of data that contains a gain range change. If the signal varies in level rapidly such as white or pink noise, it may make it difficult for the dScope to get a clean buffer. To prevent this, you can set the auto-ranging step size to medium (6dB) or coarse (20dB) in the Analogue Inputs dialogue or turn auto-ranging off altogether. (ID = 0044)
	+	Can I measure phantom power with the dScope?
Answer No. The dScope inputs are AC coupled. You can however measure phantom power with the dS-NET IO Switcher. Phantom power will not damage the dScope outputs provided the series current limiting resistor is in place, and measurements can typically be made with phantom power turned on. You will not be able to measure phantom power with the device connected to the dScope output unless the analogue outputs are muted. Even if the output is muted, there will still be a 50 Ohm resistance between pins 2 and 3. See also the analogue outputs architecture page. (ID = 0051)

More information:
dScope III Audio Analyzer - dScope III system home page
Features and Screenshots - a long list of dScope capabilities and screenshots
Technical Specifications - detailed technical specifications of the dScope System III
Software and Manuals - download the latest software, manuals, help files and more
Architecture Guide - a quick way to find out about how the dScope III works
Download brochure (920k PDF) - download the dScope Series III product brochure

My problem is not listed here - what should I try next?

Contact your local distributor for help. Prism Sound distributors

Contact tech.support@prismsound.com for specific problems not found above.

Trademark Acknowledgements:
Access, ActiveX, Excel, Microsoft, MSComm, MS-DOS, Visual Basic, VB, VBA, VBScript, Visual C++ and Windows are trademarks of Microsoft Corporation.
Borland and Delphi are trademarks of Borland Software Corporation.
Dolby and the double-D symbol are registered trademarks of Dolby Laboratories.
LabVIEW and LabWindows/CVI are trademarks of National Instruments Corporation.
Alesis and ADAT are trademarks of Alesis Corporation.
TASCAM, TDIF and DA-88 are trademarks of TEAC Corporation.

All trademarks acknowledged