release2更新说明

1 / 5 NUUO NVRmini2 Specification NUUO NVRmini 2System DiagramMain Features ‧Linux embedded – free from PC crash and virus attack ‧High throughput for megapixel camera recording ‧Support Stream Profile for remote live view bandwidth control (Original / 300 kbps / 100 kbps) ‧Support mobile client for iPhone / iPad / Android 1 1 Please check the supported camera spec list on website. Besides, to use this feature, you have to enable 2nd stream function on web setting page first.2 / 5 ‧ Panorama 360° PTZ (ImmerVision and VIVOTEK fisheye) ‧Generic dewarp (fisheye) 15 ‧Support camera multi-stream setting 2 ‧Support camera two-way audio 3 ‧ Web-based configuration, live viewer , playback (Recommend on IE 8, 9, 10, 11, Mac Safari v6.1,v7.0 and WindowsChrome) ‧ RAID 0,1,5,10 for maximum capacity or data protection 16‧ Support HDD SMART self-test‧ Onlin e GUI recording schedule‧ Support megapixel cameras and H.264 compression format‧ Digital PTZ and multi-view‧ Real-time digital output, Email alert and push notification on mobile‧ Remote I/O solution and camera I/O integration‧ Up to 128 CH remote live view with multiple monitors‧ Support joystick for easier camera control‧ Playback with 5 types of intelligent event search‧ Point of Sale (POS)‧ E-map with indicator‧ Digital watermark‧ Auto port-forwarding‧ NTP server synchronization ‧ Support over 85 brands of IP cameras and 2151 models 4 (with free monthly update)‧ Alarm source of NUUO Central Management SystemSpecificationsModel NE-2020/NE-2040 NE-4080/NE-4160 Recording Cameras 1~2(4)5 / 1~4 1~8(16)6 / 1~16Playback Channels 2(4) / 4 8 / 16Number of Drives 2xSATA II 4xSATA IIMax Storage Per Drive 4TB 4TBRAID Level RAID 0,1 RAID 0,1,5,1016CPU Marvell 88F6283 1.0GHz Marvell 88F6282 1.6GHzRAM 256MB 512MBI/O Interface 2xUSB 2.0 (for UPS) 2xUSB 2.0 (for UPS);2xeSATA (for DAS)LAN Transmission Speed10/100/1000 Mbps (RJ45 x1) 10/100/1000 Mbps (RJ45 x2)Voltage DC 19V 2.1A DC 19V 4.74A Power Consumption 40W 7 90W 8Device Dimension (HxWxD)140.0 x 109.8 x 219.0 mm 140.0 x 183.4 x 219.0 mmDevice Weight (Without Drive)2.12 kg (4.67lbs) 2.97 kg (6.55lbs)Temperature Operating: 0°C-40°CHumidity Operating: 5%-95%Supported IP Camera Brand(s): 85 brands in v1.7.29ACTi ADT Airlive Alphatech American Dynamics Arecont AMTK ARM Asoni AXIS BASLER Bolide BOSCH Brickcom Bullwark2DP 3.0 or above 3DP 3.1 or above 4The data is updated for DP 2.16. 5NE-2020 can support up to 4 cameras capacity with license activation (license type: 2ch) 6 NE-4080 can possess up to 16ch capacity with license activation (license type: 2/4/8ch) 7 40 W is the maximum power consumption 8 90 W is the maximum power consumption 9 The data is updated for DP 2.16.3 / 5 CentrixCISCO CNB COP CORUM DahuaDigital Watchdog D-Link D-LinkCN DYNACOLOR EneoErnitec Etrovision Everfocus Fine ForenixGE Grandstream Grundig Guardeon GuardlinerHIKVision Histream Honeywell i-Mege IQinVisionJetstor JVC LevelOne LG LilinLinksys Lumenera MegaIP Messoa MilesightMobotix NetworkCamera NTIC On Electronics OnvifPanasonic Pelco PiXORD Planet ProbeRover Saerim Samsung SANTEC SANYOShany Sony StarDot Sunell TelviewTechson Tiandy TOSHIBA TRUEN UDPVideosec Vitek Vision Hi-Tech Vista VIVOTEKYudor Zavio 3M 3Svision CompressionFormatMPEG-4, M-JPEG, H.264, MxPEG (depends on IP camera) RecordingPerformanceAround 60/120fps at 1.3M Total bitrate: 40Mbps Around 240fps at 1.3M Total bitate: 80Mbps Recording TypeContinuous record, record by schedule, event trigger record, digital input trigger record Remote Live ViewControlLive view, preset/go, PTZ, remote I/O, snapshot, multi-view, digital PTZ, advanced E-Map, bandwidth monitoring Audio & VideoRecordingSynchronized audio and video recording POSLive view, record, playback, and search for every transaction Auto BackupAutomatically backup the recorded video of the date before to FTP server Intelligent SearchGeneral motion, missing object, foreign object, lose focus, camera occlusion Remote Live ViewConnectionLive view maximum 64 connections per server at the same time SupportedLanguage English, Croatian, Czech, Deutsch, Dutch, Finnish, French, Hebrew, Hungarian, Italian, Japanese, Korean, Polish, Portuguese (Brazil) , Russian, Simplified Chinese, TraditionalChinese, Serbian, Spanish, Swedish, Thai, and TurkishRemote Client System Minimum RequirementModel NE-2020/NE-2040 NE-4080/NE-4160OS Windows XP (32-bit), Windows 7 (32/64-bit), Windows 8/8.1 (32/64-bit)CPU Intel Core 2 Duo, 2.6GHzRAM 1GBLAN Transmission Speed 10/100/1000 Mbps (RJ45)UI1. Web browser: Internet Explorer 8, 9, 10, 112. NUUO client application program3. NUUO iPhone, iPad, Android mobile live viewer 10Technical Details ‧ System, Setting, Management and Integration⏹ Server-Client Architecture: Centralizes all video data transaction only via NVRmini 2 to remote clients. Withthis centralized structure, total camera loading remains at a stable level, thus ensuring good recording quality even when reaching maximum number of remote client access.⏹ Open Platform: Support over 2151 IP camera models and video servers (encoders) from over 85 brands of major network camera manufacturers.11⏹ Automatic Camera Model Detection: NVRmini 2 can automatically search for IP cameras in the network (camera should support UPnP protocol or should be implemented its brand’s search tool 12). For those 10Please check the supported camera spec list on website. Besides, to use this feature, you have to enable multi-stream function on web setting page first. 11 The data is updated for DP 2.16. 12 Support camera search tools of ACTi, Arecont, D-link, and Sony.4 /5 unsearchable cameras, user can manually insert it. The auto detection function will help the user to find the brand and model of the camera after specifying its IP address.⏹ Storage Optimization: NVRmini 2 supports H.264 compression format which helps increasing the storage efficiency to nearly 600% higher than MJPEG and 150% higher than MPEG-4.⏹ Friendly GUI Recording Scheduler: Graphical user interface to setup recording schedule featuring unique day mode and week mode.⏹ Event & Action: 4 camera events including motion detection (if supported by camera), connection lost and camera input; 1 input event from remote I/O box; 3 system events and daily system report by E-mail; 5 instant alarm responses supporting output, Email, E-map popup, push notification on mobile and NUUO CMS alarm system.⏹ Online RAID Capacity Expansion and Level Migration: Support RAID 0, 1, 5, and 10 for maximum capacity or data protection at the HDD level. 16⏹Point of Sale (POS): POS transactions received through NUUO POS box or Ethernet (TPC/IP client). POS text overlay on live view video and recordings. All recorded POS transactions are searchable in the NVRmini 2 database.⏹ I/O Event Control : With the integration of camera I/O and NUUO I/O Box, system can start recording wheninput triggered, or trigger output as an event happened.⏹ Various Authorities of Different Kinds of Users: Web Viewer logins to NVRmini 2 via 4 different usergroups: administrator, power user, user, and guest. Each user group has its own distinctive privilege in system configuration, live view camera and playback records.⏹ Synchronization with NTP Server: Synchronize time daily/weekly/monthly to keep the accuracy of recordingtime.⏹ Log System: Hardware Log keeps track of system operation; NVR Log for camera status and user access; NVRevent Log for special events; Export and Backup Log for exporting video or video backup action.⏹ User Friendly: Provide users HELP page on the webpage for quick start tips and troubleshooting.⏹ Auto Power-on: The system shall be able to power-on automatically and keep recording after incident poweroutage.‧ Remote Client Operation⏹ Multiple Live View Channel: Up to 64 channels of remote connections per unit. Remote Live Viewer clientsupports 64 channels from multiple servers, and could display up to 128 channels with multiple monitors. In addition, Remote Live Viewer client can access and display live video from any NUUO Mainconsole family servers simultaneously.⏹ Multiple Playback Channel: Up to 16 channels in web playback client/NUUO Playback System.⏹ Monitor Resolution: 800x600, 1024x768, 1200x900, 1280x1024, 1366x768, 1440x900, 1600x1200,1680x1050, 1920x1080, 1920x1200.⏹ Multi-View: NVRmini 2 can duplicate the same live view video onto multiple channels and digitally zoom in tosee the details of different spots on cloned channels without losing the original live view video or using extra camera licenses.⏹ Stream Profile: Live display multiple camera streams with lower bit rate, while still recording at highestpossible quality.⏹ E-Map: Show device indicator on map for easy finding and tracking device location. Furthermore, pop up map5 / 5 to point out the device when an event occurred.⏹ Multiple Mobile Clients: Support mobile live viewer for iPhone, iPad, and Android.13‧ Playback, Search, Export and Secure Data⏹ Post-Recording Processing: Intelligent search, digital PTZ and video enhancement tool.⏹Intelligent Search: Search recorded video for 5 events including general motion, foreign object, missing object, loss focus and camera occlusion. ⏹Video Enhancement: Fine tune the image’s visibi lity, sharpen, brightness, contrast or even grey scale. ⏹Evidence Export: Snapshot and print video image in BMP/ JPEG; backup video in DAT; save video in ASF/AVI. The action exporting video or video backup will be recorded in NVRmini 2’s log system. ⏹Alarm Notification: Notify users on camera and system event through sound, digital output, push notification, E-mail and NUUO CMS alert. ⏹Auto Backup: Automatically backup the recorded video of previous dates to a designated FTP server. ⏹Manual Backup: Manually backup or delete the recordings from any NVRmini 2. ⏹ Watermark: Protect original recordings from alternation with NUUO watermark verification tool.‧ Extended Service⏹ NUUO Central Management System (CMS): Ultimate central monitoring solution for grand scale projectsand projects with multiple sites. Fully compatible with all NUUO Mainconsole family servers.‧ External Device⏹ POS Box (from serial port to Ethernet): NUUO Point of Sales system works on NVRmini 2 by overlaying thetransaction text from cash register or ATM machines onto live video channels. All POS recordings aresearchable.⏹ Remote I/O Box: I/O signals of NUUO I/O Box are converted to Ethernet through converter, which enablesNVRmini 2 to do more sophisticated application, such as starting recording when input triggered, triggering output as an event happened, and much more.⏹ Panorama 360° PTZ: Several modes are supported on live view and playback. Generic dewarp: Original mode, Rectilinear mode, Quad mode and Dual-view panorama mode. ImmerVision 14: Original mode, PTZmode, Quad mode and Perimeter mode. Vivotek: Original mode, Rectilinear mode, Full-view panorama mode, and Dual-view panorama mode.⏹ APC UPS: Continues to feed the NVRmini 2 power in an event of power outage.⏹ Joystick: Joystick support on PTZ cameras and software enabled digital PTZ function are both available inNVRmini 2. Preset points and patrol functions are also available on many camera models.13 Please check the supported camera spec list on website. Besides, to use this feature, you have to enable 2nd stream function on web setting page first. 14 Please refer to ImmerVision’s website for qualified cameras. 15 Fisheye dewarp supported on Internet Explorer only 16 RAID5 is only supported using 1TB Enterprise level HDDs.。

LabVIEW Real-Time Module™Release and Upgrade NotesVersion 8.5This document provides system requirements, installation instructions,descriptions of new features, and information about upgrade andcompatibility issues for version 8.5 of the LabVIEW Real-Time Module.Refer to the Getting Started with the LabVIEW Real-Time Module manualfor an introduction to the LabVIEW Real-Time Module. ContentsSystem Requirements (2)Installing the Real-Time Module 8.5 (3)RT Target Configuration (3)Real-Time Execution Trace Toolkit 2.0 (4)Activating the Real-Time Execution Trace Toolkit (4)New Real-Time Module 8.5 Features (5)Multiple CPU Support (5)Timed Loop CPU Assignment (5)Enhancements to the Multiple Variable Editor (5)Real-Time Performance Improvements (6)Linear Algebra Performance Improvements (6)Jitter Reduction in Math and Signal Processing VIs (6)Serial ATA Hard Drive Support (6)Improved Support for RT Desktop PCs (7)On-Screen CPU Monitor (7)Running Real-Time Applications (7)Upgrade and Compatibility Issues (7)RTX Support Discontinued (7)IrDA Support Discontinued (7)Timed Loop Priority Restriction (7)Compatibility with VxWorks 6.1 (8)Front Panel:Open Method Error (8)Real-Time Module Examples (8)Known Issues with the Real-Time Module 8.5 (8)System RequirementsTable1 describes the system requirements to run version 8.5 of theReal-Time Module. The Real-Time Module system requirements are inaddition to the LabVIEW system requirements listed in the LabVIEWRelease Notes.Table 1. System Requirements for the Real-Time Module 8.5Platform Media and SystemRequirements Important NotesWindows 2000/XP/Vista National Instrumentsrecommends that you haveat least 300 MB of diskspace for the minimumReal-Time Moduleinstallation or 750 MB ofdisk space for the completeReal-Time Moduleinstallation, which includesthe Real-Time andEmbedded drivers from theNational InstrumentsDevice Drivers CD.You might need more memory than the LabVIEW-recommended 512 MB of RAM depending on the size of the application you design in LabVIEW on the host computer. To view and control the front panel of a VI running on an RT target remotely using a Web browser, National Instruments recommends Internet Explorer 5.5 with Service Pack 2 or later.Real-Time Module Release and Upgrade © National Instruments Corporation 3Real-Time Module Release and Upgrade NotesInstalling the Real-Time Module 8.5This section includes information about installing the Real-Time Moduleon a development, or host, computer.Note You must install LabVIEW 8.5 before attempting to install the Real-Time Module 8.5. Refer to the LabVIEW Release Notes for the LabVIEW installation instructions.Complete the following steps to install the LabVIEW Real-Time Moduleon the host computer.1.Disable any automatic virus detection programs before you install. Some virus detection programs interfere with the installation program.2.Log on as an administrator or as a user with administrator privileges.3.Insert the LabVIEW Real-Time Module installation CD into theCD-ROM drive. The LabVIEW Real-Time Module installationprogram runs automatically.4.Follow the instructions that appear on the screen.5.Install the Real-Time and Embedded drivers and any other drivers that you require from the National Instruments Device Driver CD.RT Target ConfigurationUse Measurement & Automation Explorer (MAX) to configure RT targetsand to install software and drivers on targets.•Networked RT Targets —Refer to the Max Remote Systems Helpbook in the Measurement & Automation Explorer Help , available byselecting Help»MAX Help from MAX, for information aboutconfiguring networked RT targets.•Desktop PC Targets —Refer to the Using Desktop PCs as RT Targetswith the LabVIEW Real-Time Module document for information aboutconfiguring a desktop PC as a networked RT target. You can access thedocument from Windows by selecting to install the Real-Time Moduledocumentation when you install the Real-Time Module. Select Start»All Programs»National Instruments»LabVIEW 8.5»Manualsto open the labview\manuals directory and then double-clickRT_Using_PC_as_RT_Target.pdfto open the document.Real-Time Execution Trace Toolkit 2.0The LabVIEW 8.5 Real-Time Module includes a 30-day full-featuredevaluation of the Real-Time Execution Trace Toolkit 2.0. The Real-TimeExecution Trace Toolkit includes the Real-Time Execution Trace Tool andthe Execution Trace Tool VIs. You can use the Execution Trace Tool VIsto capture the timing and execution data of VI and thread events forapplications running on an RT target. The Real-Time Execution Trace Tooldisplays the timing and event data, or trace session, on the host computer.In LabVIEW, select Tools»Real-Time Execution Trace Toolkit todisplay the Real-Time Execution Trace Tool.Refer to the Real-Time Execution Trace Toolkit book in the LabVIEWHelp for information about using the Real-Time Execution Trace Toolkit todebug real-time applications. Select Help»Search the LabVIEW Helpto display the LabVIEW Help. In the LabVIEW Help, browse to Toolkits»Real-Time Execution Trace Toolkit to view the Real-Time ExecutionTrace Toolkit book.Activating the Real-Time Execution Trace ToolkitThe Real-Time Execution Trace Toolkit relies on licensing activation. Youhave a temporary license for a 30-day full-featured evaluation period. Ifyou do not activate the Real-Time Execution Trace Toolkit license, thetoolkit functions in evaluation mode for a 30-day evaluation period. Theevaluation period begins the first time you launch the Trace Tool byclicking the Evaluate button in the NI Real-Time Execution TraceToolkit dialog box. When the evaluation period expires, you must activatea valid Real-Time Execution Trace Toolkit license to continue using theReal-Time Execution Trace Toolkit.After you launch the Real-Time Execution Trace Toolkit in evaluationmode, you can click the Purchase button in the NI Real-Time ExecutionTrace Toolkit dialog box to purchase the toolkit.To activate the Real-Time Execution Trace Toolkit, use the serial numberyou receive as part of your installation package. You can activate theLabVIEW license in either of the following ways:•During installation, enter the serial number and select to run theNI Activation Wizard at the end of the installation.•When you launch the Trace Tool, click the Activate button in the NIReal-Time Execution Trace Toolkit dialog box.If you do not activate the Real-Time Execution Trace Toolkit duringinstallation, the Trace Tool prompts you for activation on launch. After youactivate the Real-Time Execution Trace Toolkit license, you no longer seethis prompt. If activation fails, the Real-Time Execution Trace Toolkitremains in evaluation mode until the 30-day evaluation period expires. Real-Time Module Release and Upgrade © National Instruments Corporation 5Real-Time Module Release and Upgrade NotesNew Real-Time Module 8.5 FeaturesThe Real-Time Module includes the following new features. Refer to theLabVIEW Help, available by selecting Help»Search the LabVIEW Help ,for more information about the following new features.Multiple CPU SupportThe Real-Time Module 8.5 supports parallel processing for increasedperformance on ETS targets with multiple CPUs. When multiple-CPUsupport is enabled, the real-time operating system automatically allocatesthreads across CPUs. As a result, many existing applications can realize animmediate performance improvement on multiple-CPU systems.You might be able to achieve further performance improvements byimplementing a pipelined architecture or by manually assigning TimedLoops to particular CPUs. To take advantage of parallel processing on amultiple-CPU system, use the LabVIEW Real-Time Software Wizard inMAX to install the NI RT Extensions for SMP. Refer to the MAX Help forinformation about using the LabVIEW Real-Time Software Wizard. Referto the LabVIEW Help for information about optimizing RT applications forsystems with multiple CPUs.Note Single-CPU systems perform best without the NI RT Extensions for SMP. Also, some applications, such as those that consist mainly of single-point I/O, can achieve lower latency using a single CPU without the NI RT Extensions for SMP. Refer to the National Instruments Web site at /info and enter the info code rtsmp for further details about optimizing RT applications for systems with multiple CPUs.Timed Loop CPU AssignmentThe Real-Time Module 8.5 supports manual CPU assignment for TimedLoops. The Timed Loop now includes an Assigned CPU input that you canuse to optimize an application for execution on systems with multipleCPUs. Refer to the LabVIEW Help for information about manuallyassigning Timed Loops to particular CPUs.Enhancements to the Multiple Variable EditorUse the Multiple Variable Editor window to configure a large number ofshared variables at one time. Right-click a project library or shared variableand select Edit Variables from the shortcut menu to display the MultipleVariable Editor window.The Multiple Variable Editor window includes the followingimprovements:•Edit multiple shared variables at once using the new table format.•Search across several shared variables at once using the new advancedsearch options. Click the Find button to display the search options.•Copy and paste property values across shared variables by clicking theCopy and Paste buttons.•Sort shared variable properties by right-clicking a property column andselecting Sort Ascending or Sort Descending from the shortcutmenu.You no longer need to use the Multiple Variable Editor window toimport or export shared variable configuration information to or from aspreadsheet file. To import the information, right-click a project libraryand select Import Variables from the shortcut menu. To export theinformation, right-click a project library and select Export Variablesfrom the shortcut menu.Real-Time Performance ImprovementsThe Real-Time Module 8.5 includes the following performanceimprovements.Linear Algebra Performance ImprovementsIn addition to the performance improvements documented in the LabVIEWUpgrade Notes, the Real-Time Module 8.5 features significantperformance improvements for the VIs on the Linear Algebra palette.Jitter Reduction in Math and Signal Processing VIsThe Real-Time Module 8.5 includes a new Real-Time Analysis Utilitiespalette that installs as a subpalette of both the Mathematics palette and theSignal Processing palette. You can use the Real-Time Analysis UtilitiesVIs to handle the resource requirements of certain Mathematics and SignalProcessing VIs in a dedicated analysis workspace. To prevent raceconditions, priority inversions, and other undefined behavior, you must usethe Real-Time Analysis Utilities VIs according to a strict set of guidelines.Refer to the Creating Deterministic Applications with the Real-TimeModule topic in the LabVIEW Help for guidelines and information aboutusing the analysis workspace to reduce execution jitter.Serial ATA Hard Drive SupportIn the Real-Time Module 8.2.1 and earlier, you can use Serial ATA(SATA) hard drives only in legacy mode. The LabVIEW Real-TimeModule 8.5 includes native support for SATA drives.Real-Time Module Release and Upgrade Improved Support for RT Desktop PCsThe Real-Time Module 8.5 includes improved BIOS compatibility fordesktop PCs used as RT targets. Also, the Real-Time Module 8.5 supportsnew multiple-CPU systems, ethernet chipsets, and SATA hard drives.Refer to the National Instruments Web site at /info and enter theinfo code etspc for up-to-date information about supported hardware andthe specific specifications that National Instruments recommends.On-Screen CPU MonitorRT targets with the Real-Time Module 8.5 software installed include anon-screen CPU monitor that displays CPU utilization information whenyou connect the target to a monitor. You can use the CPU monitor todiagnose performance issues in RT applications and to help determine theload balance on multiple-CPU systems.Running Real-Time ApplicationsTo run a stand-alone real-time application in the Real-Time Module 8.2.1and earlier, you must right-click the build specification in the ProjectExplorer window, select Set as startup and then Deploy from the shortcutmenu, and reboot the target. In the Real-Time Module 8.5, you can set theapplication to run in one step by right-clicking the application and selectingRun as startup from the shortcut menu. The Run as startup shortcutmenu item sets the application as the startup application, deploys theapplication to the target, and prompts you to reboot the RT target. Upgrade and Compatibility IssuesYou might encounter the following compatibility issues when upgrading tothe LabVIEW 8.5 Real-Time Module.RTX Support DiscontinuedAs of version 8.5, the Real-Time Module no longer supports RTX desktoptargets and no longer contains the Shared Memory VIs. Refer to the UsingDesktop PCs as RT Targets with the LabVIEW Real-Time Moduledocument for information about configuring a PC as an ETS RT target. IrDA Support DiscontinuedAs of version 8.5, the LabVIEW Real-Time Module no longer supports theIrDA protocol and no longer contains the associated IrDAVIs.Timed Loop Priority RestrictionIn the Real-Time Module 8.5, the Timed Loop only supports Priorityvalues less than 65,535.© National Instruments Corporation7Real-Time Module Release and Upgrade NotesCompatibility with VxWorks 6.1When you install the Real-Time Module 8.5 on the host computer, you alsomust install version 8.5 of the Real-Time Module software on cRIO-901xtargets. The Real-Time Module 8.5 updates the operating system oncRIO-901x targets from VxWorks 6.1 to VxWorks 6.3. Some functions inVxWorks 6.3 are not compatible with VxWorks 6.1. If you use custom Ccode in a LabVIEW application running on a cRIO-901x target, you mustrecompile the .OUT files for VxWorks 6.3. Refer to the NI Web site at/info and enter the info code rtvx for more information. Front Panel:Open Method ErrorIn the Real-Time Module 8.2.1 and earlier, the Front Panel:Open methodfailed without returning an error. In the Real-Time Module 8.5, theFP.Open method returns error 53.Real-Time Module ExamplesUse the NI Example Finder, available by selecting Help»Find Examplesfrom LabVIEW, to browse or search for RT example VIs. You also canaccess example VIs from the labview\examples\Real-Time directory. Known Issues with the Real-Time Module 8.5Refer to the readme_RT.html file on the LabVIEW 8.5 Real-TimeModule installation CD for information about known issues with theReal-Time Module 8.5.You also can launch the readme_RT.html file from Windows after youinstall the Real-Time Module. Complete the following steps to access thereadme_RT.html file from Windows.1.Select Start»All Programs»National Instruments»LabVIEW 8.5»Readme to open the labview\readme directory.The labview\readme directory contains the HTML readme files forLabVIEW and any installed LabVIEW modules and add-ons.2.Double-click readme_RT.html to open the LabVIEW Real-TimeModule Readme.National Instruments, NI, , and LabVIEW are trademarks of National Instruments Corporation.Refer to the Terms of Use section on /legal for more information about NationalInstruments trademarks. Other product and company names mentioned herein are trademarks or tradenames of their respective companies. For patents covering National Instruments products, refer to theappropriate location: Help»Patents in your software, the patents.txt file on your CD, or/patents.© 2000–2007 National Instruments Corporation. All rights reserved.371374D-01Aug07。

This document provides firmware update instructions and describes what is new in this firmware version for the SUHD553-L, SUHD653-L, SUHD753-L, SUHD863-L.This is the initial release for the Secure Series II panels (SUHD553-L, SUHD653-L, SUHD753-L, SUHD863-L) for the Scaler firmware v1.0.1.8 and Ethernet firmware v14.Follow these steps to update the scaler firmware.Learn how to update the scaler firmware.Christie recommends updating the scaler firmware using the USB method as it is faster than the webserver update method.1.Upload the firmware for the A/D board.2.Plug in a USB memory to the service terminal.3.Enter the Factory-Menu.To enter the Factory-Menu by remote control:After version 1.0.2.1-114.5.Select USB Update.For compatible USB storage devices a Connected message appears. Proceed to step 5. If the USB storage device is not compatible, proceed to step 6.6.If Connected appears, select USB Update.The firmware is updated automatically and the panel goes into Standby mode after a successfulfirmware update (about 30 seconds).a.Reset the main power switch to turn the panel back on.b.When the firmware update is complete, From the Factory-Menu perform an Initial Setting.c.After Initial Setting, power off the panel using the rocker-switch.d.Wait at least 10 seconds and power the panel back on.7.If the USB storage device is not compatible, a Not Connected USB message appears.8.For the software version to upload correctly, ensure the filename is SUHD983P.bin.Follow these steps to update the Ethernet firmware.1.To use a static IP address, select Disable under DHCP.•The default static IP address is 192.168.10.10.•At initial power on, it may take up to 30 seconds for the IP address to be active.2.Select DHCP Enable to use a dynamic IP address.•If there is router, the IP address starts with 192.166.•If there is no router, the IP address starts with 169.254.1.Go to Local Network Setting > Internet protocol version 4 (TCP/IPv4).2.If DHCP is disabled, set the IP address and Subnet mask.The IP address must be a different address than the display.IP address : 192.168.10.50Subnet Mask : 255.255.255.03.If DHCP is enabled, select Obtain an IP address automatically.The ping test checks the Ethernet connection.1.Press Windows + R.2.Type cmd and click OK.3.Type ping –t 192.168.10.10.4.Replace the IP address with the address of the display panel.A response similar to below indicates the ping test was successful.A response similar to below indicates the ping test failed.Connect to the built-in web server open a Web browser (for example, Internet Explorer, Chrome) and follow the instructions below.1.In a web browser, go to the address of the display panel.The web page provides all menu controls on the on-screen display.2.To set a value, click Apply.3.To display the current value, click Read.4.To upgrade the Ethernet or Scaler firmware, go to the General settings page.•Ethernet firmware update time: approximately 5 minutes.File name : Ethernet_FW_Secure_Series_II_V*.bin•Scaler firmware update time: approximately 8 minutesSecure_Series_II.binIf you updated the scaler firmware using the USB method, it does not need to be updated again inthe web server.Before staring the updates, ensure the following settings are selected in the Setup menu of the WebUI or the on screen display:•Setup > Power Save > Off•Setup > Power Off Mode > StandbyScaler F/W update:The panel turns off approximately three minutes after the update starts. Once the update is complete (takes approximately five to eight minutes) an Update completed. Please reboot. messageappears on the WebUI and the panel powers on.Ethernet F/W update:The panel stays on throughout the update. Once the update is complete (takes approximately five to eight minutes) an Update completed. Please reboot. message appears on the WebUI and thepanel stays on.5.Power off the unit using the remote control.6.Power cycle the panel by turning the rocker switch to the OFF position and back to ON after 15 seconds.7.Power on the panel.8.To confirm version of the firmware, click the About page on the WebUI or the panel on-screen display. For installation, setup, and user information, see the product documentation available on the Christiewebsite. Read all instructions before using or servicing this product.1.Access the documentation from the Christie website:•Go to this URL: https://bit.ly/2VccFTr orhttps:///products/lcd-panels/secure-series-II/•Scan the QR code using a QR code reader app on a smartphone or tablet.2.On the product page, select the model and switch to the Downloads tab.Additional information on the LCD panels is available in the following documents.•Secure Series II LCD Panels Product Safety Guide (P/N: 020-001778-XX)•Secure Series II LCD Display Panels External Commands (P/N: 020-001915-XX)•SUHD553-L LCD Panels Service Guide (P/N: 020-001850-XX)•SUHD653-L LCD Panels Service Guide (P/N: 020-001851-XX)•SUHD753-L LCD Panels Service Guide (P/N: 020-001876-XX)•SUHD863-L LCD Panels Service Guide (P/N:020-001877-XX)Technical support for Christie products is available at:•North and South America: +1-800-221-8025 or ************************************•Europe, Middle East, and Africa: +44 (0) 1189 778111 or ********************************•Asia Pacific•Australia: +61 (0)7 3624 4888•China: +86 10 6561 0240•India: +91 (80) 6708 9999•Japan: 81-3-3599-7481•Singapore: +65 6877-8737•South Korea: +82 2 702 1601•Christie Professional Services: +1-800-550-3061 or ***********************。

基于开源项目二次开发更新方案基于开源项目二次开发更新方案一、引言开源项目是指其源代码已经公开并且可自由使用、修改和分发的软件项目。

随着开源软件的兴起，越来越多的人开始从开源社区中获取软件解决方案，以满足其特定需求。

然而，随着时间的推移，这些开源项目可能会面临更新和维护问题。

为了保持软件的高质量和功能完备性，进行二次开发更新是一种常见的选择。

本文将探讨基于开源项目的二次开发更新方案。

二、评估开源项目在进行二次开发之前，对开源项目进行全面评估是必要的。

以下是对开源项目进行评估的一些建议：1. 功能分析：深入了解开源项目的功能和特点。

了解其是否满足了你的需求，以及项目所需的基本功能是否已经实现。

2. 代码质量评估：对开源项目的代码进行评估，包括代码结构、代码规范、注释质量等。

确保代码质量达到你的要求，并且易于维护和扩展。

3. 社区支持和活跃度：查看开源社区的活跃程度和支持情况。

一个活跃的社区将为你提供及时的技术支持和解决方案。

4. 开源许可证：了解开源项目所使用的许可证，确保你使用的开源项目符合你的需求和法律要求。

三、更新方案基于评估的结果，制定适合的二次开发更新方案是关键。

以下是一些通用的二次开发更新方案：1. 需求确定：根据现有的功能和未来的需求，明确你的二次开发目标。

定义清晰的功能需求和优先级，以使开发过程更有针对性。

2. 模块化设计：根据开源项目的结构和需求，在进行二次开发时采取模块化设计。

这样可以将更新的功能和原有功能分开，减少代码冲突和维护成本。

3. 核心功能优化：针对你的需求，对开源项目的核心功能进行优化和改进。

确保核心功能在更新后仍然稳定和高效。

4. 移植和集成：根据你的系统环境和其他软件资源，对开源项目进行移植和集成。

确保二次开发后的项目与其他系统和软件的兼容性。

5. 测试和验证：在二次开发完成后，进行详细的测试和验证。

确保更新后的功能正常运行，没有引入新的问题或错误。

四、个人观点和理解基于开源项目进行二次开发是一个灵活和高效的方式，可以满足各种特定需求。

BIOS MCSDK 2.0.2Release NotesApplies to Product Release: 02.00.02.14Publication Date: September 08, 2011Document LicenseThis work is licensed under the Creative Commons Attribution-NoDerivs 3.0 Unported License. To view a copy of this license, visit /licenses/by-nd/3.0/ or send a letter to Creative Commons, 171 Second Street, Suite 300, San Francisco, California, 94105, USA.Copyright (C) 2011 Texas Instruments Incorporated - © Copyright 2011 Texas Instruments, Inc.All Rights ReservedContents1 Overview (1)2 Licensing (1)3 Documentation (2)4 Device Support (3)5 Technical Support and Product Updates (3)6 IS NOT (3)7 Installation (3)8 Known Issues (4)9 Releases (4)9.1 Build 2.0.2.14 (4)9.2 Previous Releases (6)9.2.1 Build 2.0.1.12 (6)9.2.2 Build 2.0.0.11 (8)9.2.3 Build 2.0.0.9 (10)9.2.4 Build 2.0.0.8 (13)9.2.5 Build 2.0.0.6 (14)BIOS MCSDK 2.00.02.141OverviewThis document is the Release Notes for Release 2.0.2 of the Multicore Software Development Kit (MCSDK) for the BIOS operating system. This BIOS MCSDK software release gives developers the ability to evaluate the hardware and software capabilities of the evaluation platform and provide core software to rapidly develop a multi-core application.2LicensingThe tables below describe the primary license for the packages that make up the BIOS MCSDK. As shown in the Releases section below, some of these packages are delivered with the Code Composer Studio installer and some are delivered with the BIOS MCSDK installer.IMPORTANT: There may be portions of these packages under other licenses and you should refer to the individual package Software Manifest (after installation) for complete and specific licensing.Target ContentThis is software that runs on the device. For the location, replace <ver> with the version that is part of the component name (e.g., 2.0.0.11, etc.).BIOS MCSDK Release NotesHost ToolsThese are development tools that run primarily on the development host. For the location, replace <ver> with the version that is part of the component name (e.g.,2.0.0.11, etc.).3Documentation•EVM Quick Start Guide: Provides information on hardware setup and running the demonstration application that is loaded on flash. This document is provided as part of the EVM kit.•BIOS MCSDK Getting Started Guide: Provides information on installing the software from the two software packages (MCSDK, CCS), connect to the target EVM using JTAG, load pre-compiled libraries to the EVM, and run theapplication.•BIOS MCSDK Users Guide: Provides detailed information regarding software elements and infrastructure to allow developers to start creating applications.•Image Processing Demonstration Guide: Provides information on the image processing demo including software design, performance results, development concerns.Revision A:4Device SupportThe device and platform supported with this release include:•C6678: This release supports the Texas Instruments TMS320C6678 high performance DSP. The EVM supported by the software is TMDXEVM6678L.•C6670: This release supports the Texas Instruments TMS320C6670 high performance DSP. The EVM supported by the software is TMDXEVM6670L.•C6618: This release supports the Texas Instruments TMS320TCI6618 high performance DSP. The EVM supported by the software is TMDXEVM6618LXE.5Technical Support and Product UpdatesFor technical discussions and issues, please visit•C66x Multicore forum: /support/dsp/c6000_multi-core_dsps/f/639.aspx•BIOS Embedded Software forum:/support/embedded/f/355.aspx•Embedded Processors wiki: /index.php/Main_Page For product updates, please visit•Multicore Software Development Kits:/docs/toolsw/folders/print/bioslinuxmcsdk.htmlThe EVM comes with disks containing the MCSDK software and CCS. You can start with these or go to the MCSDK software download site listed above to check for the latest updates and version. The BIOS-MCSDK release download will also have pointers to applicable CCS and compiler release versions as well. Please review the release notes and software manifest before downloading and/or installing the software.6IS NOT•Support for BIOS5 or older releases•Support for CCS 4.x or older releases•DSP image format other than ELF (e.g., COFF)•Security Accelerator LLD is not included in this package, but has been tested against SA LLD 1.0.1.47InstallationSee the online BIOS MCSDK Getting Started Guide (link) for installation information.BIOS MCSDK Release Notes8Known IssuesThe list of issues can be found online using this link.9Releases9.1Build 2.0.2.14This is the post production release.Revision A:New features:•Linux Installer and Build Support•Added PCIe example for C6670•Updated the CSL, SRIO LLD for C6670 and C6678•Updated Hyperlink LLD for C6678Externally Tracked Issues Fixed:BIOS MCSDK Release Notes Other Issues Fixed:•IPC SRIO examples use wrong datarate: clock is 250MHz, not 312.5MHz for C6670•Simulator target for NDK is broken•Added ability to do NDK loopback under HUA•Reset Isolation needs to be disabled for SRIO sample initialization for C6678•Update of the CSL-RL for EMIF-16 for C6678•Writer utility should strip the carriage return character when parsing the input text file•Platform Lib: C6678 needs to be aligned with the CSL EMIF16 updates for C66789.2Previous Releases9.2.1Build 2.0.1.12This is the post production release of BIOS MCSDK 2.0.1Revision A:New features:•Added Multicore Application Deployment Utilities (MAD-Utils) Externally Tracked Issues Fixed:•MAD tools integration with Image Processing Demo•DSP Code generation tools update to 7.2.4 version•PDK c6670 SRIO and QMSS IPC examples require a clean then rebuild in order to operate correctly9.2.2Build 2.0.0.11This is the production release of BIOS MCSDK 2.0.0New features:•PCIe Boot example added•PCIe LLD added for C6670•Image Processing Demo support for C6670•IPC over SRIO & QMSS transports•SRIO boot exampleExternally Tracked Issues Fixed:Other Issues Fixed:•CSL PDK (C6670): PCIE project fails to compile due to undefined symbol CSL_BootCfgGetPCIEPLLLock•PDK (C6618 simulator): BCP example project for Big Endian and simulator hangs at second test•PDK (C6670): BCP test and example projects for Big Endian fail all tests.•C6670 EVM BE: TCP3E_dblMgzTestProject Big Endian fails on EVM•C6670 EVM BE: TCP3E_exampleProject Big Endian fails on EVM•There is no Readme for shmIpcBenchmark_c6678 – PDK•Platform Library simulator target does not work for NDK•getLibs() added for Platform Library and NIMU should be adopted by all MCSDK components•Fixed issue preventing building EDMA3 LLD examples•HUA: Occasionally Flash Page has nothing after the How It Works text•makefile support for MCSDK components•HUA Demo: Running the Transmit UDP benchmark multiple times crashes the system•IBL need to support I2C boot from multiple device/images based on the dip swich setting•NAND ecc bytes computation needs to be changed for BIOS MCSDK to align with Linux•Provide makefiles for EEPROM/NAND/NOR writers•ibl\src\make\ibl_c661x\i2crom.map.pre defines clocks/plls incorrectly•IBL PLL workaround is too slow for PCIe•TCP3d/TCP3e LLD source files does not build using the external to PDK ED-MA3LLD driver provided by TI-India•NIMU Rx pDataBuffers are not cached aligned•Image processing demo: The edge slices are not cache aligned•PDK (C66x): hyplnk_read_ECCErrors_reg() doesn't work. It accesses the wrong HW register.9.2.3Build 2.0.0.9This is a Beta-2 release.New features•PCIe LLD added for C6678•BCP, TCP3d,TCP3e and FFTC LLDs added for C6670•Multicore System Analyzer (MCSA) supportOther bug fixes:•Going back to the Main Flash Page after a NOR Read or Write Shows the NAND selection•HUA project name should be changed from "hpdspua" to "hua" to align w/ collateral•Import of LLD example projects gives warning and build fails unless a macros.ini is imported manually•Installer sometimes has an error at the end of the installation stage•Browsing the MCSDK help conent (UG and GSG) always crashes my Eclipse..•On the information page the User switch 1/2 display "OFF" even though 1 is ON in static mode.•Can not write HUA to NAND flash•Text in browser after test is run appears chopped.•RBL EMAC boot example and any necessary tools•Eclipse plugin did not work after the new installer update•DOC: Host boot utilities documentation in UG•IBL build instruction/documentation confusion•POST: Can not build Release build configuration for POST•Platform Library: Need C6670-sim target support•HUA : eeprom read causes application to crash on NY•Boot example projects for 6670 are missing•When written to NOR as bootable image on HUA failed to boot.•HUA does not print debug messages on UART•DOC: Need C6670 HW setup guide wiki page•POST: Add ability to indicate SA-enabled device•Nand writer on C6678 not working reliably...•Many MCSDK examples don't work out of box•Image processing demo should print messages in UART console•HUA : Internal RAM test checks for valid core between 1<= core_id < 6 instead of 1<= core_id < 8.9.2.4Build 2.0.0.8This is an update to Beta-1.New features•C6670 EVM support addedIssues fixed in this ReleaseOther bug fixes:•In Eclipse help the release note link for MCSDK is broken•POST does not display FPGA version•PLATFORM LIB: platform_lib_lite needs some documentation on intent/purpose •PDK LLD UserGuide: Documnet the LLD user guide information in wiki Userguide9.2.5Build 2.0.0.6This is the Beta-1 release of BIOS MCSDK 2.0.New features•Initial Multicore SDK for KeyStone devices •C6678 EVM support•C6678/C6670 simulator supportIssues fixed in this Release•None (this is the first release)。

O r a c l e_11g_R e l e a s e2安装手册教程(总15页)1、Oracle 11g R2安装手册(图文教程)For Windows1.下载Oracle 11g R2 for Windows版本，下载地址如下官方网站：解压两个压缩包到同一目录，即"database"，然后单击解压目录下的""文件，如下图所示：3.执行安装程序后会出现如下的命令提示行。

4.等待片刻之后就会出现启动画。

5.稍微等待一会，就会出现如下图所示的安装画面，取消下图所示的选中，然后单击"下一步"继续，同时在出现的信息提示框单击"是"继续。

6.之后就会出现安装选项对话框，默认点击"下一步"继续7．之后会出现安装类型对话框，点击"下一步"继续，如果奔出你是安装在Windows Server上的话就选择服务器类。

8．然后就是安装配置，在这要注意的是：管理口令的格式要至少包含一个大写字母，一个小写字母和一个数字，否则会提示警告，正确输入后点击"下一步"继续。

9. 之后会出现"先决条件检查"对话框，选中"全部忽略"并单击"下一步"以继续。

10．之后点击"完成"就开始安装了11．安装画面如下图所示：12．当上述进度到达100%时会出现线面的对话框，请耐心等待它完成。

13．然后再弹出的确认对话框点击"确定"这时会回到主界面然后再单击"关闭"完成安装。

14．至此，Oracle11g R2已经安装完成，你可以在开始菜单->Oracle - OraDb11g_home1->Database Control - orcl中打开访问网址。

15．登陆：在连接身份里选择"SYSDBA",再用户名处输入"sys"，密码为你最初设定的密码，点击"登陆"你就可以访问数据库了2、Oracle 11g R2安装手册(图文教程)For Aix一、确认系统硬件环境Oracle10g最低安装要求：512M物理内存、MIN(RAM*2,2G) SWAP空间、400M /TMP空间、4G Oracle目录空间、64位体系结构下面是确认过程：1、确认内存大小（1G）localhost> /usr/sbin/lsattr -E -l sys0 -a realmemrealmem 1048576 Amount of usable physical memory in Kbytes False这里oracle10g安装文档写错了，将“sys0（数字0）”写成了“sysO（字母O）”。

Third-party add-ons for ThinLinux 2.2 and later versionsDeployment GuideNotes, cautions, and warningsA NOTE indicates important information that helps you make better use of your product.A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid theA WARNING indicates a potential for property damage, personal injury, or death.© 2020 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners.Chapter 1: Introduction (4)Other documents you may need (4)Chapter 2: Citrix add-on installation (5)Download the Citrix packages (5)Install the Citrix package using add-on manager (5)Install the Citrix package using INI parameters (10)Install the Citrix package using Wyse Management Suite (11)Chapter 3: VMware add-on installation (12)Download the VMware packages (12)Convert the Bundle package to Debian package (12)Install the VMware Horizon Client package using add-on manager (13)Install the VMware package using INI parameters (17)Install the VMware package using Wyse Management Suite (18)Chapter 4: Contacting Dell (19)Contents3Introduction DISCLAIMER: The information contained in this document is general purpose information only. Dell assumes no responsibility for errors or omissions in the contents. In no event shall Dell be liable for any special, direct, indirect consequential, or incidental damage or any damage whatsoever. Dell reserves the right to make additions, deletions, or modification to the content at any time without prior notice.This document contains links to external websites that are not provided or maintained by or in any way affiliated with Dell. We do not guarantee the accuracy, relevance, timeliness, or completeness of the information about these external websites. This document helps users get early access to latest third-party applications. The packages (add-ons) created by users by following the instructions are not supported by Dell. Dell is not responsible or liable in any manner for any damage occurring due to the software. Dell will assist customers in installing third-party add-ons, and provide operating system support. Any other support or functionality inquiries may need to be shared with the third-party software vendor. Dell may not assist customers in updating or modifying the third-party add-ons.Dell Wyse ThinLinux simplifies the user management model with application icons to enhance the user experience. The Graphical User Interface (GUI) framework integrates the VDI clients such as Citrix Workspace app and VMware Horizon Client.The third-party add-on releases for Citrix Workspace app and VMware Horizon Client on ThinLinux 2.x will no longer be available on /support. You must download the packages directly from the third-party software vendor website and install the packages on your thin client.This guide provides information about deploying a Citrix add-on for Citrix Workspace app and VMware add-on for VMware Horizon Client using any of the following methods:•If you have knowledge about how to use ThinLinux UI, use the add-on manager method.•If you have knowledge about how to use ThinLinux INI parameter, use the INI parameter method.•If you want to deploy the add-on to multiple thin clients simultaneously, use the Wyse Management Suite version 1.2 or later.The target audience for this guide is customers with administrator privileges. You must have knowledge about the ThinLinux operating system, Wyse Management Suite, usage of INI parameters, and Linux commands.Table 1. Supported platformsPlatform Memory configuration (Flash/RAM)BIOS versionWyse 5070 Celeron Thin Client16 GB or 4 GB 1.3.1 and laterWyse 5070 Pentium Thin Client16 GB or 4 GB 1.3.1 and laterWyse 5070 Extended Thin Client16 GB or 4 GB 1.3.1 and laterWyse 3040 Thin Client16 GB or 2 GB 1.2.5 and laterWyse 5470 Thin Client16 GB or 4 GB 1.1.1 and laterOther documents you may needIn addition to this guide, you can access the following guides available at /support/manuals.•The Dell Wyse ThinLinux 2.2 Administrator's Guide provides information about how to configure the ThinLinux settings using the ThinLinux UI.•The Dell Wyse ThinLinux 2.2 INI Reference Guide provides information about how to configure the ThinLinux settings using INI parameters.•The Dell Wyse Management Suite Administrator's Guide provides information about configuration, and maintenance of the ThinLinux2.2-based thin clients by using the Wyse Management Suite console.4IntroductionCitrix add-on installationThe overall Citrix add-on installation includes the following tasks:1.Download the Citrix UI package, Citrix RTME package, and Citrix Workspace app for Linux Debian package. See, Download the Citrixpackages.2.Install the packages in the order Citrix UI package > Citrix Workspace app for Linux package > Citrix RTME package using anyof the following methods:•Install using Add-on Manager. See, Install and upgrade the Citrix package using add-on manager•Install using INI parameter. See, Install and upgrade the Citrix package using INI parameters•Install using Wyse Management Suite. See, Install and upgrade the Citrix package using Wyse Management SuiteDownload the Citrix packages•Download the Debian version of Citrix Workspace app for Linux package (x86_64) from .•Download the Citrix UI and the RTME packages as follows:1.Go to /support.2.In the Enter a Service Tag, Serial Number, Service Request, Model, or Keyword field, type the Service Tag or the modelnumber of your device, and press Enter or click Search.3.On the product support page, click Drivers & downloads.4.Select the operating system as ThinLinux from the drop-down menu.5.From the list, locate VDI Clients Add-on Package for ThinLinux 2.x.6.Click the download icon and extract the file.The following are the Citrix packages available from the extracted file:Table 2. Citrix packagesFilename Summaryica-ui_2.2.1.0-16_amd64.deb (Citrix UI package)Use this file as the Dell custom UI interface for Citrix ICAclient on ThinLinux 2.x.citrix-rtme_2.8.0-2235-02_amd64.deb (Citrix RTME package)Use this file as the Dell custom Citrix RealTime Media Engine (RTME) plug-in on ThinLinux 2.x.Install the Citrix package using add-on managerSteps1.Go to System settings > INI and select Server and Local as the Configuration Source.Citrix add-on installation5Figure 1. System Settings2.Copy package to the ftp server in wyse/addons/ directory and update the directory file with the add-on available in the add-onmanager list.3.To remove the earlier version of Citrix add-on, do the following:a.Go to System settings > Add-ons and click Manage Add-ons.b.From the add-ons list, select the earlier versions of the Citrix ICA package and the Citrix RTME package.c.Click the Remove button and restart the thin client.6Citrix add-on installationFigure 2. System Settings4.To install the Citrix add-on, do the following:a.Go to System settings > Add-ons and click Install Add-ons.b.From the add-ons list, select the Citrix UI Debian package that you have downloaded.c.Click Install and restart the thin client.Citrix add-on installation7Figure 3. System Settings5.To install the Citrix Workspace app package, open the terminal and run the following command:sudo dpkg -i icaclient_x.x.x.x_amd64.deb6.Restart the thin client after the installation is successful.7.To install the Citrix RTME add-on, do the following:a.Go to System settings > Add-ons and click Install Add-ons.b.From the add-ons list, select the Citrix RTME package that you have downloaded.c.Click Install and restart the thin client.unch the Citrix UI from System Settings > Connections.8Citrix add-on installationFigure 4. System Settings9.Click Create a new Citrix connection, enter the required details, and click Save.Citrix add-on installation9Figure 5. System Settingsunch the Citrix session.Install the Citrix package using INI parametersPrerequisitesIf there is an earlier version of the add-on installed on your thin client, uninstall the add-on by deploying the following INI parameter,in wlx.ini. For example, RemoveAddons=ica_19.12.0.19-01_amd64.deb1.Copy the add-on and the directory file to the <root path>\add-ons folder.2.To install the newer version of the add-on, deploy InstallAddons=<deb file> in wlx.ini INI parameter.To manually configure the INI server details, follow steps 4 to 11. If the DHCP method to add INI server details is configured, then skip steps 4 to 11.3.Log in to the thin client.4.To enter into the Admin mode, click the Switch to Admin button.5.Enter the default password.The default password is admin.6.Click the Settings icon on the desktop.The System Settings page is displayed.10Citrix add-on installation7.Click the Management icon.8.Click INI.The Manage INI Configuration page is displayed.9.From the drop-down list, select the configuration source and provide the server details.10.Click Save.11.Restart the thin client.The installation begins and the add-on is installed.Install the Citrix package using Wyse Management SuitePrerequisites•Ensure that you have added the Debian packages—ica-ui_2.2.1.0-16_amd64.deb, citrix-rtme_2.8.0-2235-02_amd64.deb, and Citrix Workspace app for Linux package—to C:\WMS\LocalReporepository on the Wyse Management Suite server.You must create a separate application policy for each Debian package and deploy the packages in the order•1.Go to ThinLinux policy settings and click Advanced.2.Enter the INI parameter RemoveAddons= <add-on name>.3.Click Save and Publish.Steps1.Log in to Wyse Management Suite 1.2 or later.2.Click Portal Administration, and then click File Repository under Console Settings.3.Select the Local Repository check box.4.Click Apps and Data.The Apps and Data page is displayed and verify the copied package is in the applications list.5.Create a group in the Wyse Management Suite server.6.Click Groups and Configurations.7.Click Plus sign (+) and register your client to the same group.8.Click Apps and Data.9.Click Thin Client under the App Policy.10.To add the policy to the required group, click Add Policy.11.Update the required fields, and then click Save.12.To schedule the policy, click Schedule App Policy and update the required fields.13.Jobs page.The lock screen is displayed during the package installation process on all the thin clients.14.Follow the steps again and install the Citrix Workspace app for Linux package followed by the Citrix RTME package.To verify whether the add-on is installed successfully, go to System Information > Packages and verify the add-on version.For more information on how to deploy the package using the newer versions of Wyse Management Suite, see the latest Dell Wyse Management Suite Administrator's Guide at /support.Citrix add-on installation11VMware add-on installationThe overall VMware add-on installation includes the following tasks:1.Download the VMware UI package and VMware Horizon Client for 64-bit Linux installer bundle. See, Download the VMware packages.2.Convert the VMware Horizon Client installer bundle to the VMware bundle update Debian package. See, Convert the Bundle packageto Debian package.3.Install the packages in the order VMware bundle update package > VMware UI package using any of the following methods:•Install using Add-on Manager. See, Install the VMware Horizon Client package using add-on manager•Install using INI parameter. See, Install the VMware Horizon Client package using INI parameters•Install using Wyse Management Suite. See, Install the VMware Horizon Client package using Wyse Management SuiteDownload the VMware packages•Download the VMware Horizon Client for 64-bit Linux installer bundle file from .•Download the VMware UI package as follows:1.Go to /support.2.In the Enter a Service Tag, Serial Number, Service Request, Model, or Keyword, type the Service Tag or the model numberof your device, and press Enter or click Search.3.On the product support page, click Drivers & downloads.4.Select the operating system as ThinLinux from the drop-down menu.5.From the list, locate VDI Clients Add-on Package for ThinLinux 2.x.6.Click the download icon and extract the file.The following are the VMware packages available from the extracted file:Table 3. VMware packagesPackage name Summaryvmware-viewclient-ui_5.0.0-00.02_amd64.deb (VMware UI package)Use this file as the Dell custom UI interface for VMware View Client on ThinLinux 2.x.vmware-bundle-update_1.0.0-00.03_amd64.deb Use this file as the wrapper package for updating the VMwareView Horizon Client bundle on ThinLinux 2.x. Convert the Bundle package to Debian packagePrerequisitesIf you are installing the package for the first time, use the vmware-bundle-update_1.0.0-00.03_amd64.deb package from /support.Steps1.Log in to a Linux system or a Linux Virtual Machine (VM). For example, Ubuntu.2.Open the terminal window. For example, press Alt+Ctrl+X if you are running Ubuntu.3.Create a directory /tmp/vmware using the following command:mkdir /tmp/vmware4.Copy the Debian package that you have downloaded from Dell support site to the directory using the following command:cp vmware-bundle-update_1.0.0-00.03_amd64.deb /tmp/vmware3 12VMware add-on installation5.Create a directory packagedata inside the /tmp/vmware directory using the following commands:cd /tmp/vmwaremkdir packagedata6.Extract the file system from the Debian package archive into the directory using the following command:dpkg-deb -R vmware-bundle-update_1.0.0-00.03_amd64.deb packagedata7.Remove the previous bundle file using the following command:rm -f packagedata/var/cache/update/vmware/VMware-Horizon-Client-5.4.1-15988340.x64.bundle8.Copy the latest bundle package that you have downloaded from VMware website to—packagedata/var/cache/update/vmware/ using the following command:cp <latest bundle> packagedata/var/cache/update/vmware/9.Edit the filename as follows:a.Run the following vi editor command:vi packagedata/DEBIAN/postinstb.Replace the name VMware-Horizon-Client-5.4.1-15988340.x64.bundle to <new-filename>.bundle and savethe file.10.Edit the version as follows:a.Run the following vi editor command:vi packagedata/DEBIAN/controlb.Change the PKG_RELEASE version to the next version. For example, PKG_RELEASE= 00.03 to PKG_RELEASE=00.04.11.Change the directory to packagedata directory using the following command:cd packagedata12.Build the new Debian package using the following command:dpkg-deb -b ../vmware-bundle-update_1.0.0-00.04_amd64.debNext stepsUse the newly created vmware-bundle-update_1.0.0-00.04_amd64.deb to upgrade the VMware View Horizon client on your thin client. For subsequent VMware Horizon Client installer updates, you can use the vmware-bundle-update_1.0.0-00.04_amd64.deb and follow the steps to convert the VMware Horizon bundle package to Debian package using the steps mentioned in this section.Install the VMware Horizon Client package using add-on managerSteps1.Go to System Settings > INI and select Server and Local as the Configuration Source.VMware add-on installation13Figure 6. System Settings2.To remove the earlier version of VMware add-on, do the following:a.Go to System settings > Add-ons and click Manage Add-ons.b.From the add-on list, select the VMware Debian package.c.Click Remove to uninstall the VMware add-on and restart the thin client.14VMware add-on installationFigure 7. System Settings3.To install the new VMware Debian package, do the following:a.Go to System settings > Add-ons and click Install Add-ons.b.Select the VMware Debian package from the list.c.Click Install button to install the VMware Debian package and restart the thin client.d.Once the thin client restarts, go to System settings > Add-ons and click Manage Add-ons.e.From the add-on list, select the VMware UI Debian package.f.Click Install button to install the VMware UI Debian package and restart the thin client.VMware add-on installation15Figure 8. System Settingsunch the VMware UI from System Settings > Connections.16VMware add-on installationFigure 9. System Settings5.Click Create a new VMware connection, enter the required details, and click Save.unch the VMware session.Install the VMware package using INI parametersPrerequisitesIf there is an earlier version of the add-on installed on your thin client, uninstall the add-on by deploying the following INI parameter,RemoveAddons=<addon-name> in wlx.ini1.Copy the add-on and the directory file to the <root path>\add-ons folder.2.To install the newer version of the add-on, deploy InstallAddons=<deb file> in wlx.ini INI parameter.To manually configure the INI server details, follow steps 4 to 11. If the DHCP method to add INI server details is configured, then skip steps 4 to 11.3.Log in to the thin client.4.To enter into the Admin mode, click the Switch to Admin button.5.Enter the default password.The default password is admin.VMware add-on installation176.Click the Settings icon on the desktop.The System Settings page is displayed.7.Click the Management icon.8.Click INI.The Manage INI Configuration page is displayed.9.From the drop-down list, select the configuration source and provide the server details.10.Click Save.11.Restart the thin client.The installation begins and the add-on is installed.Install the VMware package using Wyse Management SuitePrerequisites•Ensure that you have added the Debian packages—vmware-bundle-update_1.0.0-00.04_amd64.deb and vmware-viewclient-ui_5.0.0-00.02_amd64.deb—to C:\WMS\LocalRepo\repository\thinClientApps repository on the Wyse Management Suite server.You must create a separate application policy for each Debian package and deploy the packages in the order•1.Go to ThinLinux policy settings and click Advanced.2.Enter the INI parameter RemoveAddons= <add-on name>.3.Click Save and Publish.Steps1.Log in to Wyse Management Suite 1.2 or later.2.Click Portal Administration, and then click File Repository under Console Settings.3.Select the Local Repository check box.4.Click Apps and Data.The Apps and Data page is displayed and verify the copied package is in the applications list.5.Create a group in the Wyse Management Suite server.6.Click Groups and Configurations.7.Click Plus sign (+) and register your client to the same group.8.Click Apps and Data.9.Click Thin Client under the App Policy.10.To add the policy to the required group, click Add Policy.11.Update the required fields, and then click Save.12.To schedule the policy, click Schedule App Policy and update the required fields.13.Jobs page.The lock screen is displayed during the package installation process on all the thin clients.14.Follow the steps again and install the VMware UI package.To verify whether the add-on is installed successfully, go to System Information > Packages and verify the add-on version.For more information on how to deploy the package using the newer versions of Wyse Management Suite, see the latest Dell Wyse Management Suite Administrator's Guide at /support.18VMware add-on installation4Contacting Dell Dell provides several online and telephone-based support and service options. Availability varies by country and product, and some services may not be available in your area. To contact Dell for technical support or customer service issues, see /contactdell.If you do not have an active Internet connection, you can find contact information on your purchase invoice, packing slip, bill, or the product catalog.Contacting Dell19。

DIGI INTERNATIONAL9350 Excelsior Blvd, Suite 700Hopkins, MN 55343, USA+1 (952) 912-3444 | +1 (877) 912-3444AnywhereUSB Windows Driver Release NotesAnywhereUSB Gen 2Version 3.99 (December 04, 2019)INTRODUCTIONThis is a production release of the AnywhereUSB Generation 2 Windows Driver.SUPPORTED Products∙AnywhereUSB Gen 2 Windows Driver for 32-bit operating systems∙AnywhereUSB Gen 2 Windows Driver for 64-bit operating systemsSUPPORTED Operating Systems∙Windows 7∙Windows 8∙Windows 8.1∙Windows 10∙Server 2008-R2∙Server 2012∙Server 2012-R2∙Server 2016∙Server 2019KNOWN ISSUES∙The Belkin USB 2.0 4-port mobile-powered hub model F5U404BLK sometimes fails to enumerate when connected to AnywhereUSB.UPDATE BEST PRACTICESDigi recommends the following best practices:1.Uninstall the existing driver package via Add and Remove Hardware2.Install the new Windows driver package.TECHNICAL SUPPORTGet the help you need via our Technical Support team and online resources. Digi offers multiple support levels and professional services to meet your needs. All Digi customers have access to product documentation, firmware, drivers, and knowledge base and peer-to-peer support forums. Visit us at https:///support to find out more.CHANGE LOGVERSION 3.99 December 4, 2019NEW FEATURESNoneENHANCEMENTS1.AwUsbApi.dll is now multi-thread safe. This means that library functions can be calledconcurrently from different Windows threads.SECURITY FIXESNoneBUG FIXES1.With Windows 10 builds 1903 and 1908, the host computer would lose connectivity on reboot.This issue was determined to be due to the system network driver not being available at the time the AnywhereUSB system driver started. The “Digi AnywhereUSB Network Service” has been changed so that it works around this problem by disabling and re-enabling the “Network Attached USB Enumerator”. Note that this requires that the Startup Type of this service be configured for “Automatic” (which is the default).NOTE: The Microsoft-certified AnywhereUSB device drivers have not changed since v3.95 and will still show up with a version number of 3.95.2.AwUsbApi.dll AwUsbGetConnectionStatus function incorrectly reportedAWUSB_STATUS_IN_USE instead of AWUSB_STATUS_CONNECTED when the host itself was connected to an AnywhereUSB hub.VERSION 3.96 February 20191.The Windows Installer and the AnywhereUSB Configuration Utility are signed by DigiInternational to eliminate UAC (User Account Control) warning messages about unknown publisher.2.For customers using encrypted AnywhereUSB connections, the encryption service will nowuse certificates from either the Windows Local Machine Trusted Root CA store or theWindows Local Machine Intermediate CA store for authentication server certificates. In the previous 3.95 release, the encryption service only used the Trusted Root CA store.VERSION 3.95 April 20181.Several USB devices (e.g. Dediprog SF100 and Silicon Labs UART) fail to enumerate over ahigh latency WAN link. Fixed by setting ionhub service registry DWORD variableFastStartHub to 1. This variable is off (0) by default.[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ionhub]"FastStartHub"=dword:00000001(JIRA AWUSB-537)2.AnywhereUSB client driver awvusbd.sys blue-screens when connecting to an AnywhereUSBhub. Happens only with XenServer and XenCenter VM's. Fixed. (JIRA AWUSB-550)3.AnywhereUSB driver installer does not support upgrades. Installer now blocks attempts toupgrade over a previous installation. Previous installation must uninstalled first. You maybe prompted to reboot the computer. (JIRA AWUSB-438)ers can now import CA certificates to the Windows Certificate Store to authenticateserver certificates. The CA certificate must be installed on the "Local Computer" in theTrusted Root Certification Authorities store. (JIRA AWUSB-539)1.AwUsbGetConnectionStatus did not handle groups correctly. It also incorrectly reportedAWUSB_STATUS_IN_USE instead of AWUSB_STATUS_CONNECTED for host currentlyconnected to local machine. Fixed. JIRA AWUSB-492.2.On rare occasions the encryption service has stopped and forced users to restart it. It willnow automatically restart. (JIRA AWUSB-513)3.The encryption service now logs critical events which can be viewed from the WindowsEvent Viewer System log. (JIRA AWUSB-514)VERSION 3.91 September 20171.Client to hub connections with lengthy establishment times could lead to a blue screen ifprematurely disconnected by a user. Fixed. (JIRA AWUSB-421)2.Fixed memory leak in encryption service. (JIRA AWUSB-451)3.Disconnecting an AnywhereUSB hub connected to an Axis T8311 joystick caused a bluescreen. Fixed. (JIRA AWUSB-392)VERSION 3.90.223 June 20171.TLS v1.2 and SHA-2 (SHA-256) support. This only affects “Encrypted AnywhereUSB”.SHA-2 (SHA-256) certificates can now be used for authentication. Note that the certificatemust be signed using 2048-bit RSA encryption. Also, SHA-1 based certificates can still beused.Note:TLS v1.2 and SHA-2 support require AnywhereUSB firmware to be updated to at least rev N1(1.93). It still works with older firmware (starting with rev L v1.80) by "falling back" to TLS1.0.ers can specify a certificate "folder" instead of a certificate file when setting up"Encrypted AnywhereUSB" connections. You can specify it from the AnywhereUSBConfiguration Utility (AwUsbCfg.exe) or the console application (AwConsole.exe) just as you specify a file.Please note - to use a folder, each certificate must be renamed after the subject hash.Suppose you had a folder named c:\my-certs with two certificates - CertA.crt and CertB.crt.For example, to rename CertA.crt:a.Download an OpenSSL installer for Windows (version >= 1.0 since pre-1.0 versionsuse an older hash which will not work with AnywhereUSB).b.Open a command prompt from your certificate folder (c:\my-certs)c.Create a subject hash:c:\my-certs> openssl x509 -hash -in CertA.crt –nooutIt outputs an 8-digit hash (e.g. bc35a2e5)d.Rename (or copy) your certificate file with the hash as its base and the zerocharacter as its extension:c:\my-certs> copy CertA.crt bc35a2e5.0VERSION 3.90 January 20171.Support encryption in AnywhereUSB Programming API, AwUsbApi.dll.2.Workaround for Error Code 38. When all of the AnywhereUSB hubs are disconnected, thedevice manager unloads the ionhub.sys and awvusbd.sys drivers, and several outstanding references to the driver objects persist and block it from being removed from memory. Asubsequent attempt to connect to an AnywhereUSB hub will fail with an Error Code 38 and require a reboot in order to recover.To work-around this failure (most likely caused by intrusive third-party software) you must set these two variables to 1:[HKLM\System\CurrentControlSet\Services\AwVusbd]"DoNotUnload" = dword:1[HKLM\System\CurrentControlSet\Services\IonHub]"DoNotUnload" = dword:1Note: This work-around is disabled by default.VERSION 3.82 May 20161.Fix IOCTL Vulnerability - "Secunia advisory SA68000". (JIRA AWUSB-295)2.An unusually long network delay could lead to a BSOD. Fixed. (JIRA AWUSB-259)3.Fix Handle leak in Encryption Service. (JIRA AWUSB-310)VERSION 3.80 July 20151.Installer did not remove pre-InstallShield drivers (such as 3.60) and led to customercomplaints. Fixed.2.Configuration Utility was not remembering group assignment after disconnecting as it haddone in 3.60. Fixed.3.Added support in AwConsole for encrypted connections.VERSION 3.71 Jan 20151.OpenSSL encrypted USB traffic support (AES-128 encryption only). Firmware version 1.81and later is required.2.Optional "tunneling" of TCP connections over a single TCP connection between the hostand the AnywhereUSB remote hub to eliminate network disconnects due to inactivity. Note that tunneling is enabled automatically when data encryption is turned on. Firmwareversion 1.80 and later is required.3.New installer. Uninstalls will be done conventionally from Programs and Features insteadof from the Configuration Utility. However the configuration utility must be used touninstall an older version if you are upgrading. Note that the new installer copies the driver files to C:\Program Files\Digi\AnywhereUSB by default instead of c:\AnywhereUSB.4.The hub driver would sometimes unload with pending network I/O resulting in a bluescreen. Fixed.5.This release no longer supports signed drivers for Windows XP, Server 2003, and Server2008.VERSION 3.60 May 20141.Low and Full Speed devices which are attached to AnywhereUSB via an external USB2.0hub did not enumerate. Fixed. (JIRA AWUSB-77)2.AwUsbView did not show device speeds correctly. Fixed. (JIRA AWUSB-54)3.Add Multi-Host support to AwUsbApi DLL. (JIRA AWUSB-65)4.If a USB string contained zero as a character, AnywhereUSB would incorrectly treat it as aninvalid string. Fixed.5.Removed Reboot and Configure commands from AwConsole (the console configurationapp). (JIRA AWUSB-80)6.Added work-around for Microsoft Windows 8 / Server 2012 bug which kept USB MassStorages devices from working. (JIRA AWUSB-77)7.Fix bug with MultiTT (Multi Transaction Translator) external hub. (JIRA AWUSB-87)8.UnInstaller failed on Windows 8 because of a deprecated registry key. Fixed. (JIRA AWUSB-88)9.UnInstaller failed to bring up log in Windows 8 and Server 2012. Fixed. (JIRA AWUSB-88)10.When certain devices are removed, awvusbd.sys was causing a BSOD. Fixed. (JIRA AWUSB-86)11.Removed firmware and configuration app for legacy AnywhereUSB/5 devices. They will nolonger be supported going forward.VERSION 3.51 January 20131.Fix critical memory leak in awusbsys driver.2.If you put awusbsys and awvusbd under Driver Verifier, it would cause a blue-screenbecause of the DV filter. Fixed.3.The “X” icon at the top-right now closes the AWUSB Configuration Utility. It used tominimize it to the System Tray.4.The Connection List now has Group Number field. This was added to support connectivityto MHC (Multi-Host Connections) capable AnywhereUSB hubs that couldn’t be discovered.5.Event Logging section has been removed from File / Preferences window. Digi tech supportwill provide specific logging methods for troubleshooting if needed.6.Event Log button, which was only for the legacy AnywhereUSB/5, has been removed. Digitech support will provide specific logging methods for troubleshooting if needed.7.The AnywhereUSB Configuration Utility executable and the three AnywhereUSB drivers (.sysfiles) all share the same version numbers now.8.The Configure button is now only used to configure Group Numbers for 2nd generationmodels which are running v1.38 (or newer) firmware. Network configuration and FriendlyName changes are no longer supported with the Configure button. Use the DeviceDiscovery Utility or the AnywhereUSB Web UI to make network configuration changes. Use the AnywhereUSB Web UI to make Friendly Name changes.VERSION 3.50 October 20121.In rare circumstances, the endpoint receiver handler locks up when it receives a partialmessage from TDI. Rebooting the host was the only way to recover from this in a MultiHost environment. Fixed.2.Added a MultiString registry variable, "SkipMsOsDescrDevList", which can be used to defineproblematic USB devices which fail enumeration if they receive a Get String Descriptorrequest for the Microsoft OS Device Descriptor.3.AwUsbCfg.exe - Add Group Number field to Connection List Dialog. This only affects userswho have to connect to a hub on a different subnet.VERSION 3.30 February 20121.Updated driver to use Microsoft's new value of USBD_STATUS_CANCELED. Using the oldvalue caused some devices to hang.2.Initialize the wValue field of the setup packet. This fixed support for Aladin EToken.3. A device with a very long USB serial number string could cause a blue screen. Fixed.4.IonHub ignored IOCTL_INTERNAL_USB_CYCLE_PORT. Fixed. Some USB functional driversdepend on this IOCTL.5.If a functional driver used the WdfDeviceAssignS0IdleSettings/IdleUsbSelectiveSuspendmethod for its device, it failed because IonHub reported that the device could wake fromPowerDeviceD3. It (ionhub.sys) has been fixed by reporting PowerDeviceD2 in DeviceWake.This fixes a problem seen with Texas Instruments umpusbvista.sys functional driver for its 3410 USB to serial converter.6. A column in Configuration Utility that was used to display the address of the host in theHost to group assignments was too narrow for an IP address of 12 digits. This caused aline wrap in the Host Column and all subsequent group assignments were displayed off by one.。

Matt Monaghan: Chairman, President and CEO Kathy Leneghan: SVP and CFOLois Lee: Director, Treasury and Investor RelationsForward-Looking StatementsThis presentation contains forward-looking statements within the meaning of the“Safe Harbor”provisions of the Private Securities Litigation Reform Act of1995.Forward-looking statements arethose that describe future outcomes or expectations that are usually identified by words such as“will,”“should,”“could,”“plan,”“intend,”“expect,”“continue,”“forecast,”“believe,”and“anticipate”andinclude,for example,any statement made regarding the company's future results.Actual results maydiffer materially as a result of various risks and uncertainties,including those expressed in thecautionary statement in the company’s earnings press release for the second quarter2018posted on/investorrelations,as well as in the company's annual reports on Form10-K,quarterly reports on Form10-Q and other filings with the Securities and Exchange Commission.Thecompany may not be able to predict and may have little or no control over many factors or events thatmay influence its future results and,except as required by law,shall have no obligation to update anyforward-looking statements.Financial results presented are as of June30,2018,unless otherwise noted.Agenda2Q18 FINANCIAL RESULTSSTRATEGY UPDATE2Q18 Highlights versus Last Year❑Reported net sales increased 5.4% to $246.2 million❑Operating loss improved by $8.9 million❑EBITDA of $(3.2) million, an improvement of $8.8 million❑GAAP loss per share was $(0.50) versus $(0.72); adjusted net loss per share was $(0.41) versus $(0.63)❑Free cash flow usage of $24.6 million compared to usage of $22.4 million(in millions USD)2Q182Q17$ Change% ChangeReported Net Sales$246.2$233.5$12.6 5.4%Constant Currency Net Sales$232.3$233.5$(1.2)(0.5)%Gross Margin % of Net Sales27.4%27.8%---40 bpsGross Profit$67.3$65.0$2.3 3.5%Constant Currency SG&A$70.7$75.7$(5.1)(6.7%)Operating Loss$(6.8)$(15.7)$8.956.7%Free Cash Flow$(24.6)$(22.4)$(2.2)(9.6)%EBITDA$(3.2)$(12.0)$8.873.5%Segment Performance –Europe($M)2Q182Q171Q18% /$∆YOY%/$ ∆SeqReported Sales138.9128.5131.38.1% 5.8% Mobility & Seating58.453.551.89.1%12.8% Lifestyles69.664.168.08.6% 2.4% Respiratory 6.5 6.6 6.8(2.3)%(4.2)% Other 4.4 4.2 4.8 4.5%(8.4)% Operating Income 5.27.1 6.6$(1.9)$(1.4)❑Constant currency net sales down 2.3% compared to last year as a result of thegradual transformation in Europe, which is expected to continue through theremainder of 2018❑Gross profit improved as a result of favorable foreign exchange partially offset by unfavorable manufacturing variancesand expedited freight costs, to addressbacklog during initial phase of EU facilityconsolidation, and increased R&D expense❑Operating Income decreased $1.9 million due to lower gross profit and increasedSG&A expenseSegment Performance –NA/HME($M)2Q182Q171Q18% /$∆YOY%/$ ∆SeqReported Sales79.977.779.8 2.8%0.1% Mobility & Seating31.127.229.214.3% 6.5% Lifestyles31.631.030.6 1.7% 3.1% Respiratory17.018.819.7(9.9)%(14.1)% Other0.30.60.3(58.0)%8.4% Operating Loss(8.4)(12.4)(8.1)$4.0$(0.3)❑Reported sales increased 2.8% compared to last year❑Constant currency net sales increased 2.3% with greater than 10% increase in Mobility and Seating compared to last year andincreased 0.3% sequentially❑Decline in stationary concentrators and HomeFill® product partially offset by anincrease in portable oxygen concentrators❑Gross profit declined due to increased freight costs partially offset by reducedwarranty and R&D expense and net salesgrowth❑Operating Loss improved $4.0 million compared to last year, a 32% increase,primarily due to reduced SG&A expenseand net sales increasesSegment Performance –IPG($M)2Q182Q171Q18% /$∆YOY%/$ ∆SeqReported Sales13.715.314.9(10.6)%(7.9)% Operating Income 1.2 1.5 1.6$(0.3)$(0.4)❑Reported sales and constant current net sales both declined compared to last year principally due to lower bed product sales as a result of a now-resolved supplydisruption❑Operating income declined compared to last year principally due to a decline in net sales partially offset by reduced SG&A and warranty expense❑This segment is transitioning regarding its channel strategySegment Performance –Asia Pacific($M)2Q182Q171Q18% /$∆YOY%/$ ∆SeqReported Sales13.712.011.113.8%23.5% Mobility & Seating8.47.1 6.918.9%22.6% Lifestyles 2.7 2.6 2.3 3.8%20.8% Respiratory0.50.30.170.6%321.0% Continuing Care0.40.70.3(33.4)%55.7% Other 1.5 1.3 1.517.8% 1.5% Operating Income (Loss) 1.6(0.1) 1.0$1.7$0.6❑Reported sales increased compared to last year and sequentially in all product linesprimarily driven by Mobility and Seating❑Constant currency net sales increased13.1% compared to last year and 27.7%sequentially❑Gross profit and gross margin as a % of sales improved compared to last yeardriven by net sales growth, favorablemanufacturing variances and reduced R&D expense❑Operating Income improved as a result of gross profit improvementSelected Balance Sheet MetricsFree Cash Flow❑Free cash flow usage greater than last year primarily related to increasedworking capital related to inventory and higher interest payment❑Total cash flow usage and seasonality for 2018 expected to be similar to2017 including higher Capex❑In 2018, additional cash flow will be invested in capital expenditures andincreased working capital as revenues grow, which we expect will be offset by anticipated improvements in operating income Cash:❑Cash balances decreased due to negative free cash flow driven by operatinglosses and increased working capital; expect seasonal 2H18 improvement Total Debt:❑Total Debt: $270.0 million in convertible debt and $30.3 million of otherdebt, primarily leases❑Zero drawn on revolving credit facilities with availability of $38.7 million, asof 6/30/18Capital Structure:❑Based on current expectations, the company believes its cash balances andthe available borrowing capacity under its credit facilities should be sufficient to fund its transformation$300.3$301.4$122.4$176.5$0$50$100$150$200$250$300$3502Q184Q17(i n m i l l i o n s )Debt and CashTotal Debt Cash & Equivalents($M)2Q182Q17Free Cash Flow (24.6)(22.4)Cash Conversion Days69.180.6Agenda2Q18 FINANCIAL RESULTSSTRATEGY UPDATEOn Track to $100M EBITDA Run Rate in 3Q 2020Region Components & Interim Update ContributingBenefit *Additional Sales *Europe Sales Growth❑2018 minor pruning with growth expected in 2019Cost Reduction❑Completed transfer of manual wheelchair manufacturing from Sweden and to an existing facility in France with expected annualized savings of $1.6 million❑Announced transfer of manual wheelchair manufacturing from Switzerland toFrance by 3Q18 with expected annualized savings of $1.7 million $12.5M$12.5M$25-$40MN/ANorth America Mobility and Seating Sales Growth❑Unrestricted sales from US facilities and new wheelchair with Informatics❑Good alignment and favorable formulary position with top customers❑Power products on Federal Supply Schedule for Veterans Administration$25M$50-$80MNorth America Post-Acute Care and Respiratory Sales Growth❑Introduced the world’s first portable oxygen concentrator with Connectivity❑Strong clinical value of product and service offering for sales in care settings❑Working with channel partners to drive growth$25M$50-$80MNorth America Cost Reductions❑Optimizing operations, aligning employee roles, streamlining customerinteractions; annualized savings of $24.2 million from actions since October 2016$25M N/A* For illustrative purposes only; not projected resultsSummaryVisionLeverage the company’s strong technical capabilities for solving clinically complex needs and making life’s experiences possible for the people who use our productsGoalExecuting well with clinically meaningful products, sound and efficient operations to enable solid financial performance Progress as of 2Q18:❑Year-over-year and sequential sales growth in mobility and seating products on consolidated basis and NA/HME –an indicator of theprogress of our transformation. While it takes time to win back market share, we are pleased with the growth realized in this product category❑Significant improvements in operating income and EBITDA compared to 2Q17 and first six months of 2018❑European segment focused on margin expansion, execution of restructuring programs and reduction in sales for the remainder of 2018 as we apply the company’s transformation to this segment.❑Work-in-process for improved channel performance in IPG segment and Respiratory offering❑Free cash flow for FY 2018 expected to be consistent with 2017 –anticipated improvement in operating performance of the segments as compared to 2017 offset by increased investment in capex and working capital with growthAppendixTransformation to Invacare 2.0❑Leverage commercial improvements❑Optimize the business for cost andefficiency ❑Continue to improve quality systems ❑Launch new clinically product platforms ❑Expand talent management and culture ❑Lead in quality culture andoperations excellence ❑Grow above marketPhase 1 –Assess and ReorientPhase 3 –GrowPhase 2 –Build and Align20152019+❑Increase commercial effectiveness ❑Shift and narrow the productportfolio ❑Focus innovation on clinicallycomplex solutions ❑Accelerate quality efforts on qualityand excellence ❑Develop and expand talentResults: Reduced non-core sales, gross margin % improvements, SG&A investments and cash flow usageExpected Outcome: Growth in sales and gross profit dollars; operating income and free cash flow turningExpected Outcome: Margins,operating income reflect leverage on business infrastructureMid-way through Phase Two commercial transformationGoal is to leverage the company’s strong technical capabilities for solving clinically complex needs to generate better returns for re-investment and growthPhase 1 and 2 Indicators1Q162Q163Q164Q161Q172Q173Q174Q171Q182Q18Constant Currency Net Sales (a)(b)(c)(4.8)%(1.6)%(4.5)%(8.1)%(4.4)%(9.3)%(4.5)%(2.3)%(4.4)%(0.5)%Gross Margin Percentage of Net Sales (a)(b)+90 bps+120 bps+/-0 bps-60 bps+180 bps+100 bps+80 bps-60 bps+/-0 bps-40 bpsGross Profit (a)(b)$(3.7)M $2.1M $(4.2)M$(12.1)M $(2.7)M $(8.6)M $(2.7)M $(0.4)M $1.4M $2.3M Constant Currency SG&A (a)(b)(c) 1.3% 2.7%0.8%(2.3)% 2.7%(0.4)%(1.9)%(5.0)%(6.6)%(6.7)%Free Cash Flow (d)$(40.2)M $(17.4)M$1.5M $(10.6)M $(33.4)M $(22.4)M $(4.8)M $20.6M $(26.7)M $(24.6)M Operating (Loss) Income (d)$(5.1)M $(5.8)M $2.6M $(6.9)M $(10.7)M $(15.7)M $(5.9)M $(7.9)M $(5.1)M $(6.8)M EBITDA (d)$(1.4)M$(2.2)M$(1.1)M$(3.2)M$(7.1)M$(12.0)M$(2.2)M$(3.9)M$(1.0)M$(3.2)M%$Recent Performance –Key Expectations(a)Compared to same period prior year.(b)The comparative periods for Q116 and Q216 exclude the divested rentals businesses.(c)The comparative periods for Q416, Q117, Q217 and Q317 exclude divested Garden City Medical.(d)Amounts shown represent actual results achieved, not comparison to same period prior year.“Say -Do” Ratio: Results are tracking with key indicatorsReconciliation of Non-GAAP Performance Metrics to GAAP Financial Measures(Dollars in millions)2Q171Q182Q18Net Loss($23.5)($14.1)($16.5) Income Taxes 2.2 2.3 3.0 Loss Before Taxes(21.3)(11.8)(13.6) Interest Expense 4.67.07.0 Interest Income(0.0)(0.2)(0.1) Net Gain (Loss) on Convertible Debt Derivatives 1.1(0.1)(0.0) Operating Loss(15.7)(5.1)(6.8)Operating Loss(15.7)(5.1)(6.8) Depreciation and Amortization 3.7 4.1 3.6 EBITDA(12.0)(1.0)(3.2)Net Cash Provided by Operating Activities(20.1)(24.7)(22.4) Plus: Sales of Property and Equipment(0.2)(0.0)(0.0) Less: Purchases of Property and Equipment(2.5)(2.1)(2.2) Free Cash Flow($22.4)($26.7)($24.6)Reported Net Sales % Change-15.1% 2.3% 5.4% Less: Foreign Exchange Impact-2.9% 6.7% 5.9% Less: Impact of Divested Entities-2.9%0.0%0.0% Constant Currency Sales % Change-9.3%-4.4%-0.5%Reported SG&A % Change-3.8%-1.7%-2.6% Less: Foreign Exchange Impact-2.0% 4.9% 4.1% Less: Impact of Divested Entities-1.4%0.0%0.0% Constant Currency SG&A % Change-0.4%-6.6%-6.7%Non-GAAP Financial MeasuresSome of the information in this presentation is derived from the company’s consolidated financial data but not presented in its financial statements prepared in accordance with U.S.generally accepted accounting principles(GAAP).Certain of these data are considered “non-GAAP financial measures”under Securities and Exchange Commission rules.These non-GAAP financial measures supplement the company’s GAAP disclosures and should not be considered an alternative to the GAAP measure.The reconciliations to their most directly comparable GAAP financial measures are included in Appendix A.The company uses non-GAAP financial measures including the following:❑“Constant currency net sales”,which is net sales excluding the impact of foreign currency translation.❑"Constant currency sequential net sales“,which is a given period's net sales as compared to the most recent prior period's net sales with each period's net sales translated at the foreign exchange rates for the quarter ended March31,2018.❑“Constant currency SG&A”,which is SG&A excluding the impact of foreign currency translation.❑“Free cash flow”,which is net cash provided(used)by operating activities less purchases of property and equipment plus proceeds from sales of property and equipment.❑“EBITDA”,which is net earnings(loss)from continuing operations plus:income taxes,interest expense-net,net gain or loss on convertible debt derivatives,gain on sale of business,asset write-down to an intangible asset,and depreciation and amortization.❑“Adjusted net earnings(loss)”,which is defined as net loss before income taxes net of adjusted income taxes.。