Display Maestro 3 0 80

Display Maestro 3 0 80

Display Maestro 3 0 802
Installation‎ > ‎ 
How to Install Maestro 4.xWhile much of the installation process for Maestro 4 mirrors that for Maestro 3, there are enough differences to merit a separate accounting here. Maestro 4 comes with a very simple installer that copies the required files to the Maestro 'home' directory and creates a Windows registry key with that directory's path. As with the Maestro 3 installation, you must have 'Administrator' privileges to install and configure the RTX64 runtime environment.
Before you begin.Make sure you purchase a workstation that satisfies the system requirements of RTX64 and Maestro 4. In particular, a multi-core (at least 4, preferably 8) processor is a must, with 16GB RAM. Note that the RTX64 3.4 Runtime may not support the latest and greatest Intel processor, so be sure to check RTX64 documentation for processor compatibility! You'll need at least two open PCI-Express (PCIe) slots on the motherboard to hold the PCIe-6363 and the NIC dedicated to the RMVideo link, plus an additional PCIe slot for a second network card if you will integrate Maestro with the EyeLink tracker.Verify that the system's advanced programmable interrupt controller (APIC) and hardware abstraction layer (HAL) are compatible with RTX64. RTX64 does not support Intel's x2APIC specification. Windows 10 may boot into x2APIC mode if the motherboard supports it; in that scenario, you must disable x2APIC in the BIOS (or select xAPIC instead). Chances are the HAL will be 'ACPI x64-based PC', which is compatible with RTX64. 
For more information about the APIC and HAL, and how to verify and/or change the HAL via Windows Device Manager, consult the 'Check the HAL' section in the installation procedures for Maestro 3.x. Be sure to change the HAL before installing RTX64. If you discover that you must change the HAL after installing RTX, be sure to uninstall RTX before proceeding.
Disable Intel SpeedStep, Turbo Boost, Hyper-threading, and C-States in the BIOS. These are various features that have been introduced by Intel in an effort to improve the performance and/or reduce the power consumption of Intel processors. IntervalZero recommends disabling SpeedStep because it may increase timer and interrupt latencies in RTSS applications. In initial Maestro 4 testing we disabled Turbo Boost (which dynamically raises the operating frequency of selected cores to respond to demanding tasks) because it was not needed and it was associated with a badly behaving driver and application (Intel Turbo Boost Max 3.0). Intel's hyper-threading technology is intended to improve performance by creating 2 'logical cores' per physical core in the processor. Thus, an 8-core processor with hyper-threading enabled appears as a 16-core processor to Windows. This is likely helpful only for a highly parallelized software application, which Maestro is not; so we recommend that the feature be disabled. However, if you choose to leave it enabled, IntervalZero strongly recommends that an even number of cores are dedicated to RTX64. Finally, 'C-States' are idle, power-saving processor states; when a core is not being actively used it may enter one of these states (there are several levels). Returning to an active state from a C-state introduces more latencies. Furthermore, in initial testing our Windows 10 workstation would mysteriously reboot itself without warning or a memory dump, and some Intel forums indicated that this might have something to do with C-states on the Skylake-X series processor in our test machine. To be safe, be sure that C-states are disabled in the system BIOS.
Disable the Windows weekly maintenance task that defragments the hard drives. Over two months of testing Maestro 4, we observed that once a week the system would crash a number of times over the course of the day while Maestro was running; otherwise, it ran trials continuously for 8+ hours a day without issue. The periodic nature of the problem eventually led us to disable an automatic maintenance task (that is configured when Window 10 is installed) that would analyze and defragment the system hard drives on a weekly basis -- including the drive to which Maestro was streaming data files during testing. Once that task was disabled, no further crashes occurred. 
To disable scheduled defragmentation, first open the Defragment and Optimize Drives application (from the search bar next to the Start menu). Ensure that 'Scheduled optimization' is turned off. Then open the Task Scheduler application. In the tree view on the right, select the node Task Scheduler Library > Microsoft > Windows > Defrag, select the task labeled 'ScheduledDefrag' and disable it. You should restart the computer to ensure these changes have taken effect. Of course, this also means you may want to manually defragment your hard drives from time to time (but note that solid-state drives do not require defragmentation).
Disable the Windows weekly memory diagnostic task. IntervalZero support engineers recommended that we disable this diagnostic task which, like the defragmentation task, is a part of Windows 'Automatic Maintenance'. To disable it, open the Task Scheduler, find the node Task Scheduler Library > Microsoft > Windows > MemoryDiagnostic, and disable the 'RunFullMemoryDiagnostic' task.
Use default English language pack and system font!Unfortunately, Maestro is NOT an internationalized application. It does not have support for languages other than English, nor fonts other than the default system font.After installing Windows 10, be sure to verify that the language is English and the system font is the default system font. It was recently discovered that the parameters panel on the Trial Definition Form may be cut-off if this is not the case.

Install the RTX64 3.4 runtime environmentFollow instructions provided with the RTX64 3.4 runtime package (through Update 1 dtd 20 Jul 2018) from IntervalZero. As mentioned in the System Requirements section, you'll need a runtime license that supports 2 or more dedicated RTSS cores (with the rest dedicated to Windows); you'll also need a companion license to use the RT-TCP/IP stack. For a quad-core system we recommend the Entry edition (1-2 RTSS cores); for an 8-core system we suggest the Professional edition (up to 7 RTSS cores). There is no need to purchase the far more expensive SDK license, unless you plan to do code development with the RTX64 software development kit.
After the RTX64 package is installed, you will be asked to activate it by entering the license keys -- one for the RTX64 runtime and one for the RT-TCP/IP stack (activation requires an Internet connection). You then define how many cores are dedicated to RTSS and how many to Windows, and restart the computer. You'll now have two boot configurations: Win10 + RTX64 and Win10 only. When running Maestro, of course, you must always use the former configuration, which is the default.
After the restart, open the RTX64 Control Panel to configure RTX64 as follows:
Configure the RTSS Subsystem > Change internal system behavior: Set startup type to Automatic. Ensure the HAL timer period is 100us, and the default thread time quantum is 0. Check Free the Stack on TerminateThread call and Use priority inversion.
Configure the RTSS Subsystem > Configure Memory Allocation Behavior: Select Request from Windows. This should be the default. Leave the other settings unchanged. Note that this is contrary to IntervalZero's recommendation for deployed applications. However, Maestro has very modest memory requirements, allocates all memory at startup, and does not require any additional memory over the course of its operation.
Configure the RTSS Subsystem > Configure the RTSS Watchdog Timer: Disable the watchdog timer.
Configure the RTSS Subsystem > Configure Exception Support: Check Use Structured Exception Handling and Terminate the Faulting Process.
Configure the RTSS Subsystem > Configure Power Management Settings: Ensure that Windows idle detection is disabled. In addition, click on Windows Power Management and verify that the system is configured with the RTX64-Recommended power plan, which should be created when RTX64 is installed. This power plan disables hibernation, sleep, and other power-saving features that could impact real-time performance. For more information, see the page Real-Time Subsystem > Hardware Considerations > Causes and Management of Interrupt Latencies in the RTX64 Runtime Help.
Configure the RT-TCP/IP Stack > Configure RT-TCP/IP Stack Behavior: Ensure that the stack always starts with the RTSS subsystem by checking the box at the top of this page. Leave all other settings on this page alone. However, if you have problems connecting to RMVideo when you run Maestro, you might want to check the Run in Verbose mode box. Doing so will post information and error messages from the RT-TCP/IP Stack in the RTX Server Console window.
Unless explicitly addressed in the above list, you should leave all other settings in the RTX64 Control Panel unchanged. You will need to specify the interface for the RMVideo NIC, but that will be done in a later step (see below).
Install MaestroContents of Maestro's Home Directorymaestro.exe : The main application. It runs as a standard, user-mode Windows process, manages all interactions with the user via a graphical user interface, and communicates with a separate hardware controller over interprocess shared memory.
cxdriver.rtss : Maestro's 'hardware controller', running as a separate process within the RTX real-time subsystem. Spawned by the main application during startup.
eyelink_core64.dll : This DLL comes with the SDK for the Eyelink 1000+ eye tracker. Maestro requires this DLL to run, even if the eye tracker will not be used. It is provided as part of the Maestro installation so that it will not be necessary to install the Eyelink SDK separately.
version.html : A small HTML file that includes version information as well as a link to this online user's guide.
/drivers : This folder contains two files, ni6363_rtx64.inf and ni6363_rtx64.cat, that are required in order to transfer the PCIe-6363 DAQ card from Windows to RTX64 control.
Download the Maestro 4.x archive from the file cabinet on the Downloads page, unzip it, then open the resulting folder and run the self-extracting installer, Maestro4Setup.exe. The installer copies the Maestro program and support files to a 'home directory' you specify on the local hard drive, sets up the program group for the application, and stores several Maestro-specific settings in the Windows registry. It also registers an uninstaller tool with the operating system.
After installation, you will find a shortcut to the main application executable in the Windows Start menu program group 'Maestro.4x'; you can elect to pin this shortcut to the Start menu or the task bar. Since the installer modifies the Windows registry, you will probably need Administrator privileges to run it. [NOTE: If the installer fails to write the registry correctly, Maestromight start but it will expect the program files to be in a (hard-coded) default directory, C:Maestro. If that directory does not exist, the application will be unable to find and start its RTX64-based hardware controller. Worse yet, if it does exist but contains an incompatible version of the hardware controller, you'll get some odd behavior or a system crash!] 
As of version 4.1.1, Maestro gives the user a modicum of control over the timing of the three device-level register writes required to deliver a 16-bit 'latched' digital command to any external device in the Maestro DIO interface rack (write DO<15.0>, set the active-low TTL 'DataReady' latching signal to 0V, then restore it to 5V). Prior to this change, there was only a hard-coded software busy wait of 2.5 µs inserted after the second write in an effort to ensure that the DataReady pulse was at least that long. However, testing showed that, under certain circumstances, a register write could be delayed on the order of several microseconds. As a consequence, the three register writes were apparently 'queued up' and then executed in rapid succession -- so that the DataReady pulse was less than 0.2 µs long. While this may not be an issue for the DIO interfaces in use in the Lisberger lab, it is a problem in labs using a different DIO interface design. If a latched digital device fails to detect an incoming command, you'll see missed marker pulses or rewards, problems synchronizing with the Plexon or Optiplex system, etc. 
To address this issue, the installer includes a wizard page that lets you specify the busy wait duration after each of the three stages of a DO command. Each busy wait time is specified in microseconds, between 0 and 20; the default values are 0.5, 2.5 (for the DataReady pulse length), and 0.5. The busy waits are stored in the Windows registry; Maestro retrieves them each time it launches.
To uninstall Maestro, go to the Start menu and open the Settings panel. Select System, then Apps & features. [Another way to get here is to use the search bar to find 'Add or remove programs'.] You'll see a list of applications installed on your workstation. Scroll down the list until you find the entry for Maestro. Click on that item and select Uninstall.
Note that, as of version 4.1.1, you do NOT have to uninstall Maestro prior to installing a new release. The installer will detect the existing installation and simply replace the program files in the existing home directory, then update the Maestro registry settings as needed. However, if you want to move the installation to a different directory on the hard drive, or downgrade to an older release, be sure to uninstall Maestro first.
Maestro Registry SettingsMaestro's installer stores several settings under the HKEY_LOCAL_MACHINESOFTWAREHHMI-LisbergerLabMaestro key in the Windows registry. There you will find three string-valued (REG_SZ) entries:Home: This is the full file system pathname for the installation directory. At startup, Maestro reads this registry entry so that it can find the other program files needed to launch its RTX64-based runtime engine, cxdriver.rtss.
Version: The version string '4.x.x' for the installed version.
SetDOBusyWaits: A list of three comma-separated numbers specifying the software busy wait after each of 3 stages in the delivery of a 16-bit digital command to external devices in the DIO interface.
You should never need to use a registry editor to modify or remove any of these values. The installer takes care of this for you.
Install and configure hardware
Background. Prior to Maestro 3, successfully installing and configuring the DAQ and network cards in the computer proved to be the most elusive step in getting the program up and running. This is because we had to ensure that the DAQ board and the network card linked to RMVideoeach had exclusive access to an interrupt request (IRQ) line. With IRQs a scarce PC resource, this was often difficult to do. This problem went away with the advent of devices supporting message-based signal interrupts (MSI). The current required hardware boards all support MSI.
Hardware vendors typically recommend that you install their device driver and support software before you install the device itself. However, Maestro does not rely on any vendor-supplied device drivers; its RTX hardware controller talks directly to each device using RTX device-management functions. For this to work, the device must be transferred from Windows to RTX64 control. For any RTX64-supported network adapter, this transfer is very easy because the necessary driver INF (setup information) and CAT (security catalog) files come with the RTX64 runtime installation. The CAT file is appropriately signed and cross-signed, a Windows requirement since Windows Vista.
For the PCIe-6363, we generated the ni6363_rtx64.inf file based on an IntervalZero-supplied template; this essentially maps the PCIe-6363 device to the generic RTX64 plug-n-play driver (rtx64pnp.sys). Using the Windows Driver Kit tool inf2cat.exe, we created the corresponding security catalog file, ni6363_rtx64.cat. However, Windows 10 will not accept the CAT file unless it is signed and cross-signed using a code-signing certificate with Windows Authenticode support. In lieu of applying for and purchasing a code-signing certificate, we elected to leave the CAT file unsigned and circumvent the issue by temporarily disabling the driver signature enforcement. This complicates the procedure, detailed below, for transferring the PCIe-6363 to RTX64 control. 

Steps to install and configure Maestro-specific hardware:
Turn off the computer. Carefully install PCIe-6363 DAQ card and Intel Gigabit CT Desktop adapter (or any other RTX64-supported NIC that will serve the Maestro-RMVideo communication link). The PCIe-6363 and the Intel CT are installed in PCI-Express x1 slots (you can use a x4, x8 or x16 PCIe slot if necessary). If you plan to use Maestro with the EyeLink tracker, you'll need a second network card for that connection. We do this separately (see step 5) because it may be difficult to identify which NIC is which in the Windows Device Manager, especially if they are the same brand. Restart the computer.
Transfer ownership of the Intel Gigabit CT adapter from Windows to RTX64. Open the RTX64 Control Panel and click on Manage RTX64 devices to open the Device Manager. Find the device node for the Intel CT under the Network Adapters section; it will be labelled 'Intel 82574L Gigabit Ethernet Controller' or 'Intel Gigabit CT Desktop Adapter'. Right-click the node and select Update Driver Software. In the popup dialog, choose Browse my computer for driver software, choose Let me pick from a list of device drivers on my computer, choose Have Disk. and use the browse controls to select the file rtxpnpnet.inf in the inf folder within the RTX64 runtime's installation directory. This the setup information file for the RTX64-supplied NIC driver. Choose Next, and Windows will automatically install the RTX64-compatible NIC driver, which is labelled 'Intel 82574L Gigabit Ethernet Controller (RTX64)' for the Intel Gigabit CT. The NIC is now under RTX64 control. The same process applies to any RTX64-compatible NIC; only the device driver names are different.
Disable driver signature enforcement in Windows 10Driver signing in Windows 10 can be temporarily disabled to allow installation of a hardware device driver that is not signed. Although disabling signing does not persist after reboot, previously installed unsigned drivers remain unaffected.
To install a driver that is not digitally signed, follow these steps:
Click the Start menu and select Settings.
Click Update and Security.
Click Recovery.
Click Restart now under Advanced Startup.
Click Troubleshoot.
Click Advanced options.
Click Startup Settings.
Click on Restart.
The computer restarts. When it boots back up, a Startup Settings screen appears. On this screen, press 7 or F7 to disable driver signature enforcement.
Your computer will then complete startup and you will be able to install non-digitally signed drivers. Once you restart your computer again, the driver signature enforcement will be re-enabled.
Temporarily disable driver signature enforcement, then transfer ownership of the PCIe-6363 to RTX64. As described above, we need to disable driver signature enforcement since the driver security catalog file we supply, ni6363_rtx64.cat, is not digitally signed. The required steps are outlined in the text box on the right; it requires a system reboot. When the system comes back up, follow the same procedure outlined for the network card in step (2). The PCIe-6363 device node will likely be located in a section called Other devices or Unknown devices. Right-click the node and select Update Driver Software, choose Browse my computer for driver software, then use the browse controls to find the drivers folder in Maestro's installation directory. The required driver files are in this folder. Choose Next, and Windows will automatically install the RTX64 generic plug-and-play driver as the driver for the PCIe-6363. It will be labelled 'National Instrument PCIe-6363 (RTX64)' and will be found under the RTX64 Drivers section in Device Manager. The DAQ card is now under RTX64 control, although it's a good idea to reboot the computer after completing this step. 
Configure the RT-TCP/IP subsystem to use the Intel Gigabit CT network adapter. Open the RTX64 Control Panel and navigate to the page Configure the RT-TCP/IP Stack > Manage Interfaces and Filters. All network interfaces in use are listed on the left-hand side of the page, while the properties for a selected interface are shown on the right side. RTX64 comes with a virtual network adapter, RtVirtualNic, which Maestro does not use. Ensure that interface is disabled. Next, click the black '+' icon to add the interface for the Intel Gigabit CT. In the popup dialog, select Device Name = 'Intel 82574L Gigabit Ethernet Controller (RTX64)'; the Driver Name will be 'RtE1000.rtdll' (of course, these entries will be different if you elect to use another NIC). Set the Ipv4 address to 10.1.1.2, which is the only IP address from which RMVideo will accept a client connection (the NIC on the RMVideo side must be assigned to 10.1.1.1). Set the Netmask to 255.255.255.0 and leave the Location unchanged. Click OK to confirm the entries and add the interface. You should now see the RtE1000 interface in the right-hand list and it should be enabled. Verify that the interface has these property values (these are all defaults, so you should not have to make any changes!): Interrupt thread priority = 64; MTU = 1500; receive thread priority = 63; # of receive buffers = 256; # of transmit buffers = 256; interrupt type = MSI-X (or MSI). To ensure the changes take effect, you must restart the RT-TCP/IP Stack.
If you plan to use the EyeLink 1000+ eye tracker with Maestro, you will need to install a second network card for the Ethernet connection to the EyeLink's Host PC. Turn off the computer, install a suitable NIC (such as the Intel Gigabit CT) in an available slot (and label it on the outside of the computer!), and restart. Windows will automatically install the driver for the NIC. However, you'll need to manually set the IP address for that NIC to 100.1.1.2. In Windows 10, go to Control Panel > Network and Internet > Network and Sharing Center. Click on Change adapter setting, double-click on the network card icon that represents the NIC you just installed, and select the Properties button. Select the list item 'Internet Protocol Version 4' and click the Properties button below the list. In the pop-up dialog, select 'Use the following IP address' and enter 100.1.1.2. Enter a subnet mask of 255.255.255.0. Leave the default gateway and all other settings blank. Click 'OK' (several times) to save the changes.
NOTE: Network adapters and the EyeLinkIf you will use the EyeLink tracker with Maestro, the Maestro workstation will need at least two separate network ports -- one each for the EyeLink and RMVideo connections. You may also want a third network port to connect to your laboratory's local area network (LAN), but beware: When the EyeLink system is streaming raw pupil samples to Maestro during a recording, the processing threads that service the EyeLink network adapter and provide the sample stream to Maestro require regular CPU access on a millisecond-to-millisecond basis.If you have a third active network port connected to your LAN, the low-level processes that service that port could interrupt timely processing of the EyeLink stream -- especially since a LAN is busy all the time, and you never know when Windows is going to use it to download some updates or such!
Therefore, if you have a third network port connected to a LAN, we recommend that it be disabled whenever you are using Maestro with the EyeLink. We also suggest using a single-port network card for the EyeLink connection; avoid adapters with multiple ports. [These recommendations are based on at least one user's frustrating experience in which Maestro's EyeLink 'tracker service' thread repeatedly failed during recording, or Maestro would be unable to connect to the EyeLink at all.]
Run Maestro and verify operation 
Start the program and wait for the main frame window to come up. Open up the Message Log (if it is not already open) and check the startup messages. Ensure all of the boards you installed have been recognized and are available for use. Both Trial and Continuous operational modes should be enabled.
Mode 80,r,t The display mode is set to 80 characters-per-line and the display is shifted two character positions to the right. The test pattern is displayed so that you can shift the display again without re-entering the command. If your monitor display needs aligning, you may want to put a form of this command in your AUTOEXEC.BAT file.
Hardware-wise, you have the Maestro TX (Central) featuring 4 HDMI inputs, 1 HDMI video output with scaling option and 1 dedicated HDMI full audio output at 720p or 1080p, LAN Control, HDbaseT output, RS232, L/R stereo or Optical 5.1 output, IR TX, IR RX, IR sensor, IR window, OLED display and 4 buttons on the side allowing to enter/exit.
Installation‎ > ‎ 
How to install Maestro 3.xInstalling Maestro without hardware, RTXMaestro can still run on a system lacking the Real-Time Extension to Windows and/or the required hardware devices, but it can only be used to create and edit experimental protocols. This 'edit-only' installation is useful because it allows users to view and modify their experimental protocols on any Windows workstation -- they are not tied to the workstation that is integrated with the laboratory apparatus. The only file required in this configuration is the main application file maestro.exe, which can be stored anywhere on the hard disk at the user's discretion.
Maestro 3.x does not come packaged with an installer utility, but setting up the program itself is simply a matter of copying the required files to a selected directory in the host system and making one change in the Windows registry. In order to run experiments, of course, you will need to install the RTX runtime environment and all of the required hardware, but you need not install the drivers for these devices. You must have 'Administrator' privileges to perform the installation.
Ensure the host machine satisfies Maestro's system requirementsA minimum 3GHz quad-core processor (Intel i5/i7) is recommended, with 2-4GB RAM. You'll need at least two open PCI-Express (PCIe) slots on the motherboard to hold the PCIe-6363 and Intel Gigabit CT network card, plus an open PCI slot for the Detroit C6x (and that slot must conform to PCI specification 2.2 or older; the PCI 2.3 and later specs do not allow 5V-only cards like the Detroit). An additional PCI or PCIe will be needed for a second network card if you will integrate Maestro with the EyeLink tracker. As the older PCI slot is being phased out in favor of the faster and more versatile PCIe standard, you may have to shop around for a vendor that supplies workstations with PCI. Finally, be sure that the 32-bit version of Windows 7 is installed on the system. The current version of RTX (RTX 2011) does not yet support Windows 7 64-bit.
If you plan to use any legacy hardware, particularly any ISA-based devices, then you will have to look even harder for a computer to meet your needs. ISA devices are very old; the ISA bus was no longer included in mainstream PCs manufactured after January 2000. However, as recently as Mar 2009 we were able to purchase workstations with PCI and ISA slots from Orbit Micro.
Check the HALThe Hardware Abstraction Layer is a low-level software component through which the operating system communicates with the hardware devices installed in the machine. IRQ assignment and handling is part of the HAL's job. Windows supports a number of different HALs, and the one that is installed on a machine depends on whether the motherboard/chipset sports a standard programmable interrupt controller (PIC) or the newer advanced PIC (APIC), whether or not it supports the Advanced Configuration and Power Interface (ACPI) specification, and whether or not it has multiple processors. The most basic HALs are the 'Standard PC' (hal.dll) and 'Advanced Configuration and Power Interface (ACPI) PC' (halacpi.dll). These lack support for the APIC (not ACPI! yes, it's confusing!), while the 'ACPI Uniprocessor PC' (halaacpi.dll) and 'ACPI Multiprocessor PC' (halmacpi.dll) support it. If either of these HALs are installed, you'll potentially have more flexibility with IRQs since the APIC supports up to 24 interrupt lines. The latest HAL and the one you're most likely to see in Windows 7 PCs with multi-core processors is the 'ACPI x86-based PC' HAL.
RTX provides a real time-enabled extension to the HAL; it is compatible with all of the standard Windows HALs listed above. We recommend using the 'ACPI x86-based PC' HAL, which supports message-signaled interrupts. Avoid the 'ACPI Uniprocessor PC' and 'ACPI Multiprocessor PC' HALs. While testing a newly configured Maestro 2.x-era machine, we found that an RMVideo trial would consistently abort after 5-7 seconds on a 'duplicate frame error'. This indicated that Maestro failed to provide frame update information in time to draw the next display frame. While we don't know for sure, we believe this is due to a delay in the RTX TCP-IP stack when the HAL is either 'ACPI Uniprocessor PC' or 'ACPI Multiprocessor PC'; when we changed the HAL, the problem went away.
To check the HAL, open the Windows Device Manager. Click on the Computer node in the device tree to expose the HAL type. To change the HAL, right-click on the HAL node and select Update Driver from the context menu. The 'Hardware Update Wizard' appears. Choose option 'No, not this time' and click Next; then choose option 'Install from a list or.' and click Next; then choose option 'Don't search. I will choose.' and clickNext. In the next stage, make sure the 'Show compatible hardware' box is checked; all compatible HALs should then be listed. Choose one of these HALs, if available, in descending order of preference: 'ACPI x86-based PC', 'Advanced Configuration and Power Interface (ACPI) PC', or 'Standard PC'. Click Next to install the selected HAL. Click Finish and restart the machine. Upon restart, Windows will complete the HAL conversion and you'll have to restart once more. Be sure to change the HAL before installing RTX. If you discover that you must change the HAL after installing RTX, be sure to uninstall RTX before proceeding.
Install the RTX runtime environmentFollow instructions provided with the RTX runtime package from IntervalZero (formerly known as Ardence, Inc.). As mentioned in the System Requirements section, you'll need an RTX 2011 Runtime license. We recommend the Basic edition, which supports a quad-core processor. There is no need to purchase the far more expensive SDK license, unless you plan to do code development with the RTX software development kit.
After installing RTX, it must be configured appropriately to run Maestro's RTSS driver. Open the System tab on the RTX Properties panel and set the Startup Type to 'PnP Automatic' so that the RTX subsystem starts at boot time. On the same tab, open the Behavior Settings dialog and set the HAL Timer Period to 50µs and check the box 'Free stack on TerminateThread calls'. On the Control tab, verify that two of the available processors are dedicated to RTX, and the rest to Windows (remember, your system should at least be quad-core). On the Starvation tab, configure RTX so that it yields to Windows after a 5-second starvation timeout. Finally, on the TCP/IP tab, be sure to enable the RTX-TCP/IP stack and specify the full path to the configuration file for the network adapter that will connect to RMVideo (see below for details). If your particular installation will not use RMVideo, you can use the default 'configuration file' provided by RTX. However, you still must enable TCP/IP support, or Maestro's hardware interface controller (cxdriver.rtss) will fail to load.
Maestro program filesmaestro.exe : The main application. It runs as a standard, user-mode Win32 process, manages all interactions with the user via a GUI, and communicates with a separate hardware controller over interprocess shared memory. Any convenient desktop shortcuts should point to this executable.
cxdriver.rtss : Maestro's 'hardware controller', running as a separate process within the RTX real-time subsystem. Spawned by the main application during startup.
eyelink_core.dll : This library is part of the SDK for the Eyelink 1000+ eye tracker. As of v3.2.0, Maestro requires this library to run, even if the eye tracker will not be used. It is provided as part of the Maestro installation so that it will not be necessary to install the Eyelink SDK separately.
xydetroit.out : Firmware image that implements XYScope controller functionality on the Detroit C6x DSP board. Loaded onto the Detroit during application startup. Optional in systems that do not use the device.
xydakar.out : Firmware image that implements XYScope controller functionality on the Dakar DSP board. Loaded onto the Dakar during application startup. Optional in systems that do not use the device.
m62evtmr.out : Firmware image that implements the event timer & digital I/O functionality on the M62 DSP board. Loaded onto the M62 during application startup. Optional in systems that do not use the device.
rmvideo : The RMVideo executable file. As of version 2.5.1, Maestro can automatically update RMVideo at startup. After opening a session with the RMVideo host, Maestro checks the RMVideo program version. If it does not match the current expected version, it will download this copy of the program, and the currently running RMVideo will replace the old executable image with the file downloaded. Maestro then issues a 'restart' command, waits 10 seconds for it to start, then begins a new command session with the updated RMVideo. If this auto-update process fails, you can manually copy this file onto the RMVideo workstation (use a CD or a second Ethernet connection) and restart the program. NOTE: As of v 3.2.1, the 'auto-update' feature has been removed and this file is no longer present in the installation ZIP archive.
version.html : A small HTML file that includes version information as well as a link to this online user's guide. It is not required for the installation.
rmvnic_*.ini : Sample RTX TCP-IP configuration files. Use as a template; you'll need to set the Ethernet address field (EA) to reflect the value for your NIC.
[Caveat: The layout and content of the RTX Properties panel changes from version to version. These instructions apply to RTX 2011; you may have to hunt around to find the particular settings in your version.]
Install Maestro program filesCopy Maestro's executable and support files to a selected 'home directory' on the local hard drive. The required program files are listed in the side panel and are available for download as a ZIP archive. Unzip the archive and copy the files therein to the designated directory.IMPORTANT: If you're updating your machine to a new Maestro release, you will likely copy the program files into an existing Maestro home directory, overwriting the files representing a previous release. If you do this, please take care with the RMVideo NIC sample files. Those should NOT be copied, as they are merely templates. The .ini file that pertains to the network card in your machine has been modified so that the 'EA' entry is set to the Ethernet address of that particular card. I strongly advise using a different name for this .ini file, rather than one of the names of the NIC sample files listed in the side panel. Users have made this mistake before, and discover that their updated Maestro no longer runs properly!
Using the Windows registry editor (regedt32.exe), store the full pathname of the chosen directory in the REG_SZ-valued registry entry 'Home' under the key HKEY_LOCAL_MACHINESOFTWAREHHMI-LisbergerLabMaestro. Finally, as a convenience to users, create a desktop shortcut to the main application executable, maestro.exe. [NOTE: If you fail to create the registry entry correctly, Maestro might start but it will expect the program files to be in a (hard-coded) default directory, c:Maestro. If that directory does not exist, the application will be unable to find and start its RTX-based hardware controller. Worse yet, if it does exist but contains the incorrect version of the hardware controller, you'll get some odd behavior!] 
Install and configure hardware
Prior to Maestro 3, successfully installing and configuring the AI, AO and other devices in the computer proved to be the most elusive step in getting the program up and running. This is because we had to ensure that the AI board and the network card linked to RMVideo each had exclusive access to an interrupt request (IRQ) line. With IRQs a scarce PC resource, this was often difficult to do. This problem goes away with the advent of devices supporting message-based interrupts (MSI). The currently recommended hardware configuration supports MSI.
Hardware vendors typically recommend that you install their device driver and support software before you install the device itself. You may wish to do so for the PCIe-6363, since National Instruments provides software tools by which you can re-calibrate the analog input and output subsystems of the board, if necessary. Since Windows will find and install most network drivers automatically, there's no need to pre-install a driver for the Intel Gigabit CT or whatever network adapters you use to connect to the RMVideo and EyeLink tracker PCs. Do NOT install device drivers for the Detroit C6x DSP card or any of the still-supported legacy hardware. These drivers can sometimes cause problems; in at least one case, a Windows driver - RTX conflict caused the system to crash when Maestro started up.
Keep in mind that Maestro does not rely on any vendor-supplied device drivers; its RTX hardware controller talks directly to each device using RTX device-management functions. If you install the Windows driver for a Maestro device, you must transfer 'ownership' of the device from Windows to RTX so that Maestro's hardware controller (an RTSS process) can communicate with the device without conflicting with the Windows driver. By transferring ownership, you ensure the Windows driver is not loaded at boot time. If you do not install a Windows driver (and Windows does not install one itself), then the device is disabled from Window's point of view, and you may not have to transfer ownership to RTX. [As of v3.2.0, there's one exception to this rule: communications with the EyeLink 1000+ eye tracker uses a network card that remains under Windows control and is handled by a Win32 thread that runs with time-critical priority in Maestro's GUI process.]
Step-by-step for the recommended hardware configuration:
(Optional) Install the device driver and support software for PCIe-6363, if you wish. You will be transferring control of the device from Windows to RTX (see below), so the National Instruments' driver won't be loaded. If, at some later time, you wish to use NI tools to re-calibrate the analog subsystems on the PCIe-6363, you'll need to temporarily transfer device ownership to Windows, perform the calibration, then transfer ownership back to RTX before running Maestro again.
Turn off the computer. Carefully install the PCIe-6363, the Intel Gigabit CT adapter, and -- optionally -- the Detroit C6x. The PCIe-6363 and the network card are installed in PCI-Express x1 slots, while the Detroit requires a PCI slot. If you plan to use Maestro with the EyeLink tracker, you'll need a second network card for that connection. We do this separately (see step 7) because it may be difficult to identify which NIC is which in the Windows Device Manager, especially if they are the same brand.
Turn on the computer. Windows will likely find and load the driver for the Intel network adapter. If you installed the NI driver, the same will be true for the PCIe-6363. If Windows cannot find a driver for any device you added, a 'Found New Hardware' wizard may pop up. You can cancel out of this wizard. From Windows' point of view, the device is unavailable.
Transfer ownership of the PCIe-6363 from Windows to RTX. Open the RTX Properties panel. From the Hardware tab, open the PnP Device Settings dialog. In the dialog's tree view, expand the Windows node and look for the entry identifying the PCIe-6363. Right-click on the entry and select Add RTX INF Support. Then click the Apply button. Next, use the push-button on the dialog to open the Windows Device Manager. Find the node for the PCIe-6363 in the Windows device tree, right-click on it, and choose Uninstall from the context menu. The device node will disappear. Now select Action|Scan for hardware changes from the Device Manager's menu. The 'Found New Hardware' wizard appears. Select option 'No' for the 'Can Windows connect to.' question, then hit Next. If Windows finds more than one driver for the device (eg, the Windows driver and the generic RTX INF version), it will ask you to select one. Be sure to select the entry that includes the phrase 'RTX Supported'. Complete the installation of the RTX driver, then return to the PnP Device Settings dialog and hit the Refresh button. The PCIe-6363 should now be under the RTX node; RTX now 'owns' the device. Right-click on the PCIe-6363 node and choose Properties. If installation was successful, the Status message should read 'Device is MSI capable and should work properly for message-based interrupts'. You do NOT need nor want to obtain a line-based IRQ resource for the PCIe-6363. You may have to reboot the computer at least once to complete this process.
Transfer ownership of the Intel Gigabit CT adapter from Windows to RTX. Add RTX INF support as you did for for the PCIe-6363. Then, instead of uninstalling the adapter, right-click on its node in the Device Manager and select Update Driver Software. In the popup dialog, choose Browse My Computer for Software, then Let me pick, then choose the 'RTX Supported' entry from the device driver list. (If you try to uninstall the adapter and then scan for hardware changes as in Step 4, Windows simply reinstalls the original Intel driver and the device is not transferred to RTX ownership.) Like the PCIe-6363, the CT adapter supports MSI. 
Sample RTX TCP/IP configuration files3C905B-TX-NM
 Intel PRO/100 S
 Intel Gigabit CT
[TCP/IP]
MemoryInK=256
TimerPriority=61
TickInterval=200
MaxSockets=30
NumStartupEvents=20
[rtnd0]
Driver=RT3C905
IPAddr=10.1.1.2
Netmask=255.255.255.0
EA=000103DCE3DE
InterruptPriority=11
ReceivePriority=10
NumRecvBuffers=16
NumXmitBuffers=16
LatencyRecvUpdated=0
[TCP/IP]
MemoryInK=256
TickInterval=200
MaxSockets=30
TimerPriority=61
NumStartupEvents=20
[rtnd0]
Driver=RT8255X
IPAddr=10.1.1.2
Netmask=255.255.255.0
EA=00508B09A652
InterruptPriority=11
ReceivePriority=10
NumRecvBuffers=16
NumXmitBuffers=16
LatencyRecvUpdated=0[TCP/IP]
MemoryInK=256
TickInterval=200
MaxSockets=30
TimerPriority=66
NumStartupEvents=20
[rtnd0]
Driver=RTE1000
IPAddr=10.1.1.2
Netmask=255.255.255.0
EA=001B21C760AA
InterruptPriority=64
ReceivePriority=63
LineBasedOnly=0
PreferMsi=1
NumRecvBuffers=48
NumXmitBuffers=48
LatencyRecvUpdated=0

Configure the RTX TCP/IP subsystem to use the Intel Gigabit CT network adapter. On the TCP/IP tab of the RTX Properties panel, enable RTX TCP/IP support and specify the full path to the .INI configuration file for the Intel CT adapter. This configuration file tells the RTX TCP/IP subsystem which network adapter in the computer should be used and defines a number of driver and protocol parameters. For a full discussion of the configuration file, see the RTX documentation. The right-side panel includes three examples of actual configuration files for different network adapters that have been used in the Lisberger lab. Some of the key parameters in the configuration file: Driver is the name of the IntervalZero-supplied NIC driver to be used; EA is the unique Ethernet address of the adapter (so RTX TCP/IP can find it in a machine that might have more than one NIC installed); IPAddr is the IP address assigned to the adapter. Regardless the particular NIC installed, IPAddr must be set to 10.1.1.2, which is the only IP address from which RMVideo will accept a client connection. The NIC on the RMVideo side must be assigned the IP address 10.1.1.1. Note that both IP addresses are in an address range reserved for private use; they were chosen precisely for this reason -- they are never routed onto the Internet. It is important that the RMVideo-Maestro link not carry any broadcast garbage coming across the Internet or a local intranet via a second NIC installed in either machine! Finally, for the MSI-capable Intel Gigabit CT adapter, it is important to include the parameters LineBasedOnly=0 and PreferMsi=1. The first ensures that RTX uses message-based interrupts for the Intel CT, and the second ensures that MSI mode is used rather than MSI-eXtended mode. In early testing we found that the IntervalZero-provided RTE1000.dll driver for the Intel CT (and other network cards using the Intel 82574 chip set) failed frequently if the card was used in MSI-X mode. Also for the Intel Gigabit CT, note the priority levels assigned to the timer (66), interrupt (64), and receive (63) threads. These are RTX-specific priority levels, and we recommend that you use these specific values. In any event, they should all be greater than 50, the RTX priority assigned to the main worker thread in Maestro's hardware device controller, cxdriver.rtss.
If you plan to use the EyeLink 1000+ eye tracker with Maestro, you will need to install a second network card for the Ethernet connection to the EyeLink's Host PC. Turn off the computer, install a suitable NIC (such as the Intel Gigabit CT) in an available slot (and label it on the outside of the computer!), and restart. Windows will automatically install the driver for the NIC. However, you'll need to manually set the IP address for that NIC to 100.1.1.2. In Windows 7, go to Control Panel > Network and Internet > Network and Sharing Center. Click on 'Change adapter setting', double-click on the network card icon that represents the NIC you just installed, and select the 'Properties' button. Select the list item 'Internet Protocol Version 4' and click the 'Properties' button below the list. In the pop-up dialog, select 'Use the following IP address' and enter 100.1.1.2. Enter a subnet mask of 255.255.255.0. Leave the default gateway and all other settings blank. Click 'OK' (several times) to save the changes.
NOTE: Network adapters and the EyeLinkIf you will use the EyeLink tracker with Maestro, the Maestro workstation will need at least two separate network ports -- one each for the EyeLink and RMVideo connections. You may also want a third network port to connect to your laboratory's local area network (LAN), but beware: When the EyeLink system is streaming raw pupil samples to Maestro during a recording, the processing threads that service the EyeLink network adapter and provide the sample stream to Maestro require regular CPU access on a millisecond-to-millisecond basis.If you have a third active network port connected to your LAN, the low-level processes that service that port could interrupt timely processing of the EyeLink stream -- especially since a LAN is busy all the time, and you never know when Windows is going to use it to download some updates or such!
Therefore, if you have a third network port connected to a LAN, we recommend that it be disabled whenever you are using Maestro with the EyeLink. We also suggest using a single-port network card for the EyeLink connection; avoid adapters with multiple ports. [These recommendations are based on at least one user's frustrating experience in which Maestro's EyeLink 'tracker service' thread repeatedly failed during recording, or Maestro would be unable to connect to the EyeLink at all.]
If you will be using any supported legacy hardware in your Maestro setup, then the basic procedures above still apply. However, if you are using the PCI-6070E for analog input or an RMVideo NIC that does not support message-based interrupts, then you have some extra work to do to ensure that both devices get exclusive access to an IRQ line.
Before installing any hardware, you should go into the system BIOS and disable non-essential motherboard devices such as the USB, serial, and parallel ports. You'll likely have to disable the sound card and the 'SMBus controller'. You can live without all of these, and disabling them will free up some precious IRQ lines.
Next, install only the PCI-6070E, then reboot the computer and go through the process of transferring device ownership from Windows to RTX. Once RTX has control of the device, and if the system HAL supports the Advanced Configuration and Power Interface (ACPI) standard, you may be able to manually reassign the device to an available IRQ. Right-click on the device entry under the RTX node in the PnP Device Settings dialog and select Properties. If the device is properly configured, the popup dialog will tell you so. If the system is ACPI-compatible, you may be able to change the IRQ line and its disposition (shared or exclusive); otherwise, these widgets are disabled. If you are unable to assign an exclusive IRQ to the board, then you will have try it in different PCI slots until an exclusive IRQ is found. This process typically requires one or more reboots.
Once you've successfully installed the PCI-6070E, then you'll have to go through the same process for the NIC that will connect to RMVideo.
Finally, install all remaining Maestro devices (AO board, XYScope controller DSP card, etc.). After installing the board(s) and rebooting, cancel out of the 'Found New Hardware' wizard that should come up when Windows starts. You'll want to disable these devices in the Windows Device Manager; otherwise, the hardware wizard will appear every time you restart the machine. It does not matter if they are disabled in Windows; Maestro's RTX-based driver will still be able to communicate with these boards, and it will disable their interrupts to ensure they do not interfere with the AI or NIC boards. Open the RTX Properties panel and ensure that the PCI-6070E and, if applicable, the RMVideo NIC are still properly configured with exclusive-access IRQs.
Run Maestro and verify operation 
Start the program and wait for the main frame window to come up. Open up the Message Log (if it is not already open) and check the startup messages. Ensure all of the boards you installed have been recognized and are available for use. Both Trial and Continuous operational modes should be enabled.

Display Maestro 3 0 802Kazino igri besplatno. Groupspro 3 2 – contact groups and mailing list management. https://dbcbpn.over-blog.com/2021/02/stellaris-buildings.html. Discover Curio Cabinets on Amazon.com at a great price. Our Living Room Furniture category offers a great selection of Curio Cabinets and more. Free Shipping on Prime eligible orders.