CEP_3.0_UserGuide

合集下载

PlaneVisor 3 User 说明书

SOFTWARE FOR ULTRASONIC LOW-FREQUENCY FLAW DETECTORS А1220 MONOLITH AND А1220 ANKERPLANEVISOR 3USER MANUAL1 Content2 Guideline3 General information4 PC requirements5 Staff requirements6 Installation7 Launching and completion of program8 Connection of the device9 Working with PlaneVisor 31 Guideline1.1 This user manual describes characteristics, installation, settings and operation of the software PlaneVisor 3.2 General information2.1 Software functionPlaneVisor 3 is developed to work with ultrasonic low-frequency flaw detectors A1220 Monolith and A1220 Anchor (then –flaw detector or devise) manufactured by Acoustic Control Systems Ltd.2.2 Software abilities Software allows:- receiving, achieving and printing out data (A-scans, Bands, Maps) from device to PC;- recording configurations from PC to the devise and backwards;- operation with nonvolatile memory;- preparation of inspection reports.3 PC requirementsFor proper work of the program it is necessary to have:3.1 IBM-compliable PC:64 MB RAM;Free 4 MB in the hard disk;CD/DVD-ROM;USB-Port 1.1 or 2.0;OS: MS Windows® 98, Windows® 2000, Windows® XP or Windows® Vista.3.2 Printer (if needed).4 Staff requirement4.1 The operator should have skills of working in MS Windows.5 Installation5.1 USB drivers installationBefore installation of the software, install the drivers for A1220 MONOLITH flaw detectors for proper connection with PC.ATTENTION: DRIVER MUST BE INSTALLED FOR EACH USB-PORT OF PC – SEPARATLY!For driver installation:- Turn on the devise.- Connect the flaw detector to PC. Operation system will automatically recognize the new (unknown) USB-connection and will open the new window of drivers installation.Windows will start the process of recognizing new equipment.The Operator have to:-decline connection to Windows Update Server-indicate the folder with 2 files (drivers)-during installation attention window will appear, choose point “continue anywa y”-press the ready/finish button by the end of installation5.2 Software installationTo install PlaneVisor 3:Run Plane Visor 3 *exe file.- Follow instructions on the screen (fig.1)fig.1Enter personal information and choose directory, where software should be installed (Fig.2)Fig. 2Fig.3The operator can change earlier installation settings by pressing “back” button or continue process pressing “next” button.Fig.4Press “finish” button to comple te the installation. (Fig.5)Fig.5- Software has been installed.5.3 Uninstall.To uninstall program you have to:- Use “Instrument panel→ Install and uninstall software bar” to uninstall PlaneVisor 3.6 Starting and finishing the software6.1 Start the softwareWays of running program:Using shortcut of software: Start → A ll programs → ACS software → PlaneVisor v.3.Run Planevisor3.exe, located X:\Program Files\ACSsoftware\PlaneVisor 3\Planevisor3.exe, X- means hard disc where OS is installed. In successful way, PlaneVisor 3 window will appear.(fig.6)fig.6On the top of the window there are inlays of operation modes, data source bar and control panel. At the bottom there is a status bar, which notify if a flaw detector is connected or not.NOTE: User can run the program before or after connecting the device.In the Example directory there is an example file, which will help to master program easier. On default, directory Examples is located: X:\Program Files\ACS software\Plane Visor 3\Examples\, X- means hard disc where OS is installed.6.2 Exit the softwareBefore exiting the software disconnect the device from the software bypressing (or Ctrl+X). After that the operator can exit the software pressing7 Connecting of the flaw detectorPlaneVisor 3 is compatible with flaw detectors firmware versions V.1.02.04 and higher.7.1 Connecting of the flaw detectorTurn on the device.Use USB cable to connect the instrument to the PC (USB cable is included in basic delivery kit).ATTENTION! Multicontact Lemo jack should be connected to the device, keeping orientation of slots (follow the red dots on both connectors for correct connection).Connect USB cable to the PC.On the display of the flaw detector the operator will find inscription: “PC CONNECTION MODE”.In status bar of the program device information will appear.7.2 Disconnection of the flaw detector.Firstly, close the program, then disconnect the device, or use buttons of safe disconnection.8 Operation of the software PlaneVisor 38.1 Operation modesOperation modes are supported for A1220 MONOLITH: CONFIG, A-SCANS, BANDS, MAPS, FLASH.Two operation modes are supported for A1220 ANKER CONFIG and A-SCANS.Each mode has its inline in the bottom of Plane Visor window.(Fig.7)Fig.7CONFG mode is intended for editing, saving on PC and recording configuration in device.A-SCAN mode is intended for reviewing, printing and saving A-Scans on PC. A-Scans will have the same settings as they had by the moment they were made in the flaw-detector.BANDS mode is intended for reviewing, printing and saving bands of B-Scans on PC. Bands will have the same settings as they had by the moment they were made in the flaw-detector.MAP mode is intended for reviewing, printing and saving maps of C-Scans, B-Scans and D-Scans on PC. Maps will have the same settings as they had by the moment they were made in the flaw-detector.FLASH mode is intended for reviewing memory capacity, amount of recorded information (A-Scans, Bands, Maps) and also free memory. This mode is also used for relocating flash memory. Flash tag appear only when the device is connected.8.2 CONFIG ModeOverview of CONFIG mode window.(fig.8)Fig.88.2.1 Control buttons in CONFIG mode.-Load configurations from the device. Press F1 fast key and F2 fast key to sent selected configurations to the device.-Safety disconnection of the device (CTRL+X).-Load configurations (F3).-Save configurations (F4). PlaneVisor 3 will save configurations as *.ctf file.-Select first available configuration (F5).-Select previous available configuration. (F6).-Select next available configuration (F7)-Select last available configuration (F5).8.2.2 Loading configurationsThe operator should load configurations to start work in that mode.- Press button to load configurations (F4). Choose *.ctf file in the next window.(Fig.9)Fig.9PlaneVisor 3 will open file and show information in data source bar. (fig.10)Fig.10To receive configurations from device press button, which is active only when the flaw detector is connected. Information will appear in status tab.(Fig.11)Fig.118.2.3 CONFIG Mode elements.«CONFIGURATION LIST» - is a table, where a list of available configurations are shown. The operator can change displayed configuration by navigation between the lines. (fig.12)Fig.12Column «№» contains numbers of configurations, which assign automatically.Column «CONFIG Name» contains names of configurations.Column «I» can contain «*», which means that configuration was changed and that configuration is chosen to be set to the device.To choose or cancel process of sending configuration to the device, make double click on the left mouse button in the configuration line in column «I». Double klick in the head of the column «I» mark/cancel symbol «*» to the all column.Double click on the configuration name line allows the operator to change name of configuration. (fig.13)The name can consist of no more then 19 letters, numerals or special signs.Fig. 13«COMMENTS» - empty area, intended for typing comments for every configuration. Comments are saving with configurations on the PC.«CONFIGURATION SETTINGS» - shows current settings of the device that can be changed. Integrated data are the same as in the MENU MODE in the flaw detector.8.2.4 Operating with configurations.Configuration mode is easy to work with big number of configurations, because it allows to edit, correct and save many settings. It is possible to generate up to 20 different configurations.After receiving configurations from the device to PC (8.2.2.) and choosing one of them, it is sent to the flaw detector as a current one. ATTENTION: EVERY CHANGING OR ENTERINNG NEW SETTINGS IN “CONFIGURATION SETTINGS” COLUMN MUST BE CONFIRMED BY PRESSING “ENTER” BUTTON!After editing one configuration, switch over an other.It is necessary to sent earlier changed or new-created configurations to the device, otherwise they will be located only on PC.8.3 A-SCAN MODEOverview of A-SCAN MODE window.(fig.14)8.3.1 Control buttons in A-Scan mode-load A-Scans from the device (F1). "-Safety disconnection of the device (CTRL+X).-load file with A-Scans (F3).-Save A-Scans (F4). Program will save A-Scans as a *.dtf file.-Copy image of selected A-Scan to the clipboard (F5)-Move to the firs A-Scan (F6).-Move to the previous A-Scan (F7).-Move to the next A-Scan (F8).-Move to the last A-Scan (F9).-Enter text comments to A-Scan (F11).-Preview and printing a report of the chosen A-Scan (F12).8.3.2 Loading dataTo start work it is necessary to load information of made A-Scans.To load information from the file the operator should press (F3)In the next window chose *.dtf file. (Fig.15)Fig.15Program will recognize the file and give information about the source in the data source tab.(Fig.16)Fig16Press button to load data from the device (F1). Button is active only when the instrument is connected. Program will identify A-Scans which were saved in the flaw-detector.The device will be shown in the status tag.8.3.3 Elements of A-Scan tab.- «A-SCAN LIST» - received A-Scans are shown in the table.Chosing the image of A-Scan is made by moving between the lines of the table.(Fig.17)Fig.17There is an opportunity to save each A-Scan as separate file. Press right mouse-button on the A-Scan name,which is nessesary to save and chose checkmark “Save selected A-Scan”(Fig.18)Fig.18Enter a route of saving A-Scan file in the next window. (Fig.19)Fig.19There is an opportunity to delete selected A-Scan. Press right mousebutton and click on the “Delete selected A-Scan” checkmark.(Fig.20)Fig.20Confirmation window with help text will appear.(Fig.21)Fig.21Column «№» enclose through numbers of the shots, which assign automatically.Colum n “CONFIG NAME” encloses configuration names, when each A-Scan was made.Column “I” enclose additional numbers. Numbers are set to an each shot when recording to the instrument (automatically or manually).-Results of the measurements- Moving and holding left mouse button on the A-Scan, signal parameters will be shown on the screen. (Fig.22)Fig.22(Fig.23) Ultrasonic signal, horizontal and vertical mark up of the screen, strobe, measuring cursor and icon menu by the moment an A-Scan was made, are shown in the picture. Review and Zoom mode are maintained.Fig.23“CONFIGURATION SETTINGS - device settings by the moment A-Scan was made are shown in the table.8.4 Overview of BANDS MODE windowView of the BANDS mode screen.(Fig.24)Control buttons in BANDS mode.- receive bands from the device (F1)-safety disconnection of the device (CTRL+ X)-save bands (F4). Program will save bands as a *.btf file.-Show first available band (F6).- Show previous available band (F7).- Show next available band (F8).- Show last available band (F9).-Add comments to the current band (F11).-Print report on current band (F12).-Switch B-Scan line weight.-Apply binary b/w threshold scheme.-Apply direct gradient b/w color scheme.-Apply direct gradient b/w color scheme.-Apply ACSYS acoustic color scheme.-Switch between A-Scan/param display.8.4.2 Data loading.Load earlier made bands to start.- Press button to load data files, chose *.btf file.(Fig.25)Fig.25Program will recognize the file and give information about the source in thedata source tab.(Fig.26)Fig.26Press button to load data from the device (F1).Button is active only ifthe instrument is connected. Program will recognize the file and giveinformation about the source in the status tab.«BAND LIST» - List of available bands. (Fig.27)Fig.27There is an opportunity to save each band as a separate file and delete band from the current band list. These directions are the same to the A-Scans and described in the 8.3.3. point.Each line contains:List number of the band (#) – band number, which assigns automatically. Configuration name (CONFIG :) - configuration name, when the band was made.Measurement results - Moving and holding left mouse button on the B-Scan, signal parameters will be shown in the screen.Colorful B-Scan of the band is available. Ultrasonic signal, horizontal and vertical mark up of the screen, measuring cursor -are shown in the picture.(Fig.28)Fig.28«A-Scan/PARAMETRES»Fig.29A-Scan or a table of the band with the settings of the divece when A-Scan was made are shown in the picture.Information about A-Scans number in band and band step is shown in the status bar.8.5 MAP MODEOverview of MAP MODE window.(Fig.30)Fig.30Control buttons of MAP MODE.- receive maps from the device (F1)-safety disconnection of the device (CTRL+ X)-load file (F3)-save maps (F4). Program will save maps as a *.mtf file.-copy images of the current map to the clipboard (F5).-Select first available map (F6).- Select previous available map (F7).- Select next available map (F8).- Select last available map (F9).-Add comments to current map (F11).-Print report on current map (F12).-Switch B-Scan line weight.-Apply binary b/w threshold scheme.-Apply direct gradient b/w color scheme.-Apply direct gradient b/w color scheme.-Apply ACSYS acoustic color scheme.-Switch between A-Scan/param display.8.5.2 Data LoadingTo start working in program it is necessary to load maps. Press button (F3) and choose *.mtf file.(Fig.31)Fig.31Program will recognize the file and give information about the source in the data source tab.(Fig.32)Fig.32PlaneVisor 3Press button to load data from the device (F1).Button is active only if the instrument is connected. Program will recognize the file and give information about the source in the status tab.8.5.3 Map mode tabs.- «MAP LIST» - List of available maps.(Fig.33)Fig.33There is an opportunity to save each map as a separate file and deletemap from the current map list. These directions are the same to the A-Scans and described in the 8.3.3. point.Each line contains:List number of the map (#) – map number, which assigns automatically. Configuration name (CONFIG :) - configuration name, when the mapwas made.Measurement results –settings measurements in the cursor point of intersection.(Fig.34)Fig.34Display shows colorful C-Scan, B-Scan and В-Scan of the current map. Ultrasonic signal, horizontal and vertical mark up of the screen, measuring cursor -are shown in thepicture.(Fig.35)Fig.35«A-Scan/Device Param.».Fig.36A-Scan or tables of the map with the settings of the device when A-Scan was made are shown in the picture.Information about number of bands in the map, colomns in the map and map step is shown in the status bar.8.6 FLASH mode.FLASH mode allows to see capacity of a memory, extracted for each kind of data (A-SCANS, MAPS,BANDS), amount of used memory and also allows to relocate the whole memory between maps and bands.Overview of flash mode window.(Fig.37)Fig.37Control buttons of FLASH mode.-apply new flash markup (F1).-erase all A-Scans from device (F2)-erase all Maps from device (F4)- cancel flash markup(F5).-disconnect device from PC (CTRL+X).8.6.2 Flash mode elements- Circle diagram of flash-memory use. By pressing left mouse button on the sector appropriated to maps or bands (blue and red sectors), hereupon capacity of dedicated sector is changing.(Fig.38)Fig.38Afterwards the made relocation can be saved or canceled. ATTENTION: AFTER RELOCATING MEMORY BEETWEEN BANDS AND MAPS, INFORMATION WILL BE DELETED IRREVOCABLY!To save changes press button. Confirm or cancel changes in the next window.(pc.39)Fig.39Only A-Scans will be saved in the memory after the memory relocation.- «Summary» - shows procent and numeric correlation of extracted memory for each kind of information.Fig.408.6 Report formation, viewing and printing.PlaneVisor 3 allows to make reports for each kind of information.Press button in A-SCAN, BANDS and MAP modes to open window with additional report data input.(41)MAP mode window.Fig.41In the “Report caption” area there is a configuration name and a map number.In the “Report conclusions” area an operator may add any t ext information.After entering information it is possible:To print report immediately. Program will use connected default printer.To preview report before printing.To cancel printing.8.7.1 Report previewingFig.42Buttons of the preview window: - Look of the report:- full screen mode;-fit-to-wide mode;-actual size.Looking through the report:-first page;-next page;-previous page;-last page;-select page; in the opened window an operator can put the number of the page.Printing:-printing setup;-printing current report.Save/load report:-save prepared report;-load prepared report;。

Prior Scientific OptiScan III 电动平台系统用户手册（版本 1.5）说

目录重要安全信息 — 第 1 部分 4系统拆封 — 第 2 部分 62.1 其他选配件 7安装 — 第 3 部分 83.1 拆除现有平台 83.2 安装 OptiScan III 平台 83.3 线缆连接 93.4 聚焦驱动安装 10入门 — 第 4 部分 124.1 USB 操作 124.2 使用控制杆 (CS152DP) 13高级操作 — 第 5 部分 155.1 RS232 命令集 155.2 MACRO 和 SOAK 155.3 SOAK 命令 175.4 OPTISCAN III 和 OPTISCAN II 之间的区别 185.5 常用命令 195.6 平台命令 225.7 Z 轴命令 245.8 图案命令 265.9 Z 错误代码 275.10 CS152DP（控制杆配置） 28故障排除 — 第 6 部分 30系统规格 — 第 7 部分 33 返厂和维修 — 第 8 部分 35附录 — 第 9 部分 36A) 非标准聚焦驱动安装 36B) LEICA DML 系列 H122BL 聚焦设备安装 41C) Leica DML 和 DMR 系列直接联轴节聚焦设备安装 45D) PRIOR TERMINAL 运行说明49E) 兼容 OPTISCAN III 52F) 面向中国客户的相关信息诚挚感谢您选用 OptiScan III 系统，我们期望它实用、可靠，能够有效帮助您完成显微镜检查相关工作。

请在安装和使用系统前务必花时间仔细阅读本手册。

本手册包含重要的安全信息，以及如何正确安装和操作产品以避免损坏的相关建议。

如果您对本产品有任何疑问或问题，请随时联系 Prior。

重要安全信息第 1 部分•本手册包含重要的安全信息和操作说明，请务必妥善保管。

•使用时务必遵照操作说明，否则设备自带的防护可能会遭损坏。

•使用平台系统前，请遵照机身上以及本手册中的所有警告、安全和操作说明。

•本产品的安全操作室温为 5-40°C，相对湿度为 80%。

PNS3.0旗舰版用户手册

QuickDesktop
虚拟桌面快速交付系统软件 V3.0
QuickDesktop 虚拟桌面快速交付系统软件 V3.0 旗舰版使用手册
苏州江波软件技术有限公司
-1-
QuickDesktop
虚拟桌面快速交付系统软件 V3.0
目录
第一章 1.1 1.2 第二章第三章 3.1 3.2 3.3 第四章 4.1 4.2 4.3 4.4 第五章 5.1 5.2 5.3 5.4 第六章 6.1 6.2 6.3 6.4 第七章 7.1 7.2 7.3 7.4 7.5 7.6 7.7 7.8 第八章 8.1 8.2 8.3 8.4 8.5 产品简介 .......................................................................................................................................................... 4 产品概述 ................................................................................................................................................... 4 产品安装环境 ........................................................................................................................................... 4 QUICKDESKTOP 的安装流程说明 ..........................

Scale User's Manual

; Screen shows
detection message
while scale detects
its load and auto‐zero itself.
Power Off
) Press
for 1 second
to power off scale.
; Display shows
power‐off message.
Chinese GB/T 11883‐2002 Class III Equivalent to OIML R76 100% F.S. ±50% F.S. ±2% F.S. 0.5e/s
≤10 seconds
Sable and no action in 3 sec. Sable and no action in 3 min. 100% F.S. + 9e
Â Inspect shackle and hook before using. Â When the scale runs out of power, replace the
battery with full ones.
Â Do NOT use the scale under thunder or rain. Â Do NOT attempt to repair the scale yourself.
1. Introduction
Notice
Before you use the scale, please read this manual through carefully, and keep it properly for future use.
Safety Guide
For good performance and precise measurement, be careful with daily operation and maintenance. Note the following instructions:

Ocean Optics 光谱仪 FPG 固件版本 3.0 及以上的新外部触发选项说明书

New External Triggering OptionsInstructions for Spectrometers withFirmware Version 3.0 and Above OverviewOcean Optics spectrometers with FPGA Firmware Version 3.0 and above provide several methods of acquiring data (see table below). In the Normal/Free-Run mode, the spectrometer is “free running.” That is, the spectrometer is continuously scanning, acquiring, and transferring data to your computer, according to parameters set in the software. In this mode, however, there is no way to synchronize the scanning, acquisition, and transfer of data with an external event. However, trigger pulses for synchronizing an external event with the spectrometer are available.To synchronize data acquisition with external events, other modes of acquiring data are available. Each mode involves connecting an external triggering device to the spectrometer and then applying an external trigger to the spectrometer before the software receives the data. The length of the integration time and the source for the integration clock depend upon the mode chosen. All other acquisition parameters are set in the software.Also see the External Triggering Options Instructions for triggering information for other Ocean Optics spectrometers with firmware versions below 3.0.Triggering Mode Description Use This Trigger Mode When You …Normal/Free-Run Spectrometer acquires spectracontinuously.No synchronization to other events is neededSoftware Integration time is set in the software.Software receives a trigger event andtransmits spectra obtained in the dataacquisition cycle in which the triggeroccurred.Are using a continuous illumination source, and the light intensity is constant before, during, and after the trigger.Need to set the integration time in the software.External Triggering Options Instructions for FW3.0and AboveTriggering Mode Description Use This Trigger Mode When You …External Hardware Level Trigger Integration time set via software on achip in spectrometer. The spectrometerwaits for a sharp rise in voltage on thetrigger input pin, and then acquiresspectra until the voltage is removed.Need a continuous acquisitionwhenever a certain condition is met,such as:-when reacting to a sample beingpresent or-when a sample reaches a specificstate that you want to measureExternal Synchronous Trigger Spectrometer acquires data from anexternal trigger event (such as a pushbutton) until the next time the trigger isactivated, at which time thespectrometer ceases spectralacquisition and begins a newacquisition. Integration time cannot beset, since the trigger can fire at randomintervals.Must synchronize your scans to anexternal clock sourceAre using a lock-in amplifierAre using a chopperExternal Hardware Edge Trigger Integration time set via software on achip in spectrometer. The spectrometerwaits for a sharp rise in voltage on thetrigger input pin, and then acquiresspectra.This trigger acquires onespectrum each time that there is asharp rising edge (if an acquisition isnot already in progress).Are using a pulsed excitation source orlight source in your experiment (suchas a laser or flash lamp)Are doing LIF (fluorescence withpulsed excitation) or phosphorescenceexperimentsNeed to synchronize an acquisitionwith an external eventSetting Up for External Triggering IMPORTANT:Voltage RegulationThe maximum recommended voltage on the Triggering Pin is 5.5 V.If your triggering device exceeds this voltage, you must regulate or condition the signal (via transistor buffering, transformer isolation or opto-isolation, for example) or isolate the signal from the spectrometer.NoteTo use one of the External Triggering options, you must know the specifications andlimitations of the triggering device. The design of the triggering device may prevent youfrom using one of the external triggering modes as it is described in these pages.External Triggering Instructions for FW3.0and Above Pinout Diagrams for Ocean Optics SpectrometersHR4000,HR2000+,Maya2000Pro and Maya-LSL and Maya-LSL,NIRQuest,QE65000, QE65Pro, and QE ProFor external triggering,supply a line from Pin 10 of the multi-pin connector on the spectrometer to your triggering device.Be sure to also use the Ground Pin when triggering. See the appropriate spectrometer Data Sheet to locate the ground pin(s).Pin-out Diagram of 30-pin Connector on HR4000,HR2000+,NIRQuest,Maya2000Pro and Maya-LSL,QE65000, QE65Pro,and QE Pro SpectrometersUSB2000+ and USB4000For external triggering, supply a line from Pin 7 of the multi-pin connector on the spectrometer to your triggering device. Be sure to also use Ground Pin 6 when triggering.Pin-out Diagram of 22-pin Connector on USB2000+, Flame-S,USB4000, and Flame-T SpectrometersFlame-S,Flame-T, and Flame-NIRFor external triggering, supply a line from Pin 2of the multi-pin connector on the spectrometer to your triggering device. Be sure to also use Ground Pin 1when triggering.When facing the 40-pin Accessory Connector on the front of the vertical wall of the Flame, pinnumber 1 is on the right.Pin-out Diagram of40-pin Connector on Flame-S,Flame-T and Flame-NIR SpectrometersExternal Triggering Options Instructions for FW3.0and AboveSetting Integration Time in SoftwareSoftware,External Hardware Level Trigger and External Hardware Edge Trigger modes can have the integration time set via OceanView or SpectraSuite.Set Integration Time with OceanViewUse the Main Controls of the Set Acquisition Parameters in OceanView to select the trigger mode and to set the integration time.The Automatic button in the Integration Time control box automatically adjusts the spectrometer’s integration time to bring the highest point of the signal to 85% of full saturation value. This value is represented by the horizontal blue line on the preview graph.External Triggering Instructions for FW3.0and AboveThe integration time may also be set manually by using the numeric spinner control and the drop-down units menu.Note that the Nonlinearity Correction control is grayed out until the Electric Dark control is enabled.Also note that once a triggering mode for the spectrometer has been set, the device will wait for an external trigger before continuing. It will appear as though the spectrometer has locked up and no further data acquisitions will occur until the External Trigger pin on the device receives a signal.External Triggering Options Instructions for FW3.0and AboveSet Integration Time with SpectraSuiteUse the External Trigger selection box on the Trigger toolbar to set the trigger mode of the spectrometer to Software.NoteOnce you select an external trigger mode, your computer will appear unresponsive. Thisis normal, as the computer is waiting for a trigger. You must apply one more trigger tothe spectrometer after selecting a new trigger mode.External Triggering vs. Triggering an External EventThere could be some confusion between the concepts of External Triggering and triggering an external event. The following sections explain each of these concepts:∙External Triggering–An event outside the sampling system (such as a push button, lever activation, or laser pulse) triggers the voltage level on the spectrometer’s trigger pin and instructs the spectrometer to begin spectra acquisition.∙Triggering an External Event–When triggering an external event, the spectrometer instructs an external device (typically a lamp such as the PX-2 or the LS-450) to illuminate immediately prior to spectral acquisition.Trigger Mode DescriptionsThe following sections specify the Trigger modes for Ocean Optics spectrometers with firmware versions 3.0 and above and associated timing sequences.For the Maya2000Pro and Maya-LSL,NIRQuest,Flame-NIR,HR2000+,USB2000+, Flame-S,HR4000, USB4000,and Flame-T,the timing sequences specified are for the trigger mechanism interacting with a single-depth FIFO.The hardware implementing these Trigger modes may enhance the capability and performance by implementing buffering schemes using larger or multiple FIFOs.For the QE65000,the timing sequences specified are for the trigger mechanism interacting with a triple-depth FIFO. The hardware implementing these Trigger modes enhances the capability and performance by implementing a buffering scheme using multiple FIFOs.In addition, the QE Pro has a 15,698-deep buffer.External Triggering Instructions for FW3.0and Above Normal ModeIn the Normal (Free-run) mode, the spectrometer will acquire one spectrum for each “get spectrum”command issued from the host software.The integration time for each spectrum is pre-programmed prior to the host issuing its “get spectrum” command.The spectrometer waits in a repetitive idling loop until it receives the next “get spectrum” command.Once the command is received, the spectrometer exposes the detector for the pre-programmed integration time, and its resulting spectrum is written to an internal FIFO.The spectrometer signals the host that a spectrum is ready, and the host reads out the new spectrum.Upon reading out the new spectrum, the host immediately commands the spectrometer to acquire the next spectrum.In this process, the spectrometer is responding “on-demand”to the host’s “get spectrum” commands.The spectrometer waits in an idle state between each spectrum and the next “get spectrum” command.The spectrometer does not pre-fetch any spectra in anticipation of the next “get spectrum” command.For the QE65000spectrometer, integrations are continuously performed with the most recent three spectra available to the host software. The QE65000 has an internal FIFO which can hold up to three contiguous spectra.To maximize throughput, the QE6500 is constantly pre-fetching spectra back-to-back, independent of the host’s “get spectrum” command.However, if the host fails to issue a “get spectrum” command by the time the third spectrum is pre-fetched, the QE65000 clears its FIFO and starts 3 new acquisitions.In this process, the QE65000 is pre-fetching back-to-back spectra in anticipation of the host’s “get spectrum” command.For the QE Pro, there are no idle cycles that drop new spectra; all new spectra are stored in the buffer and are available to the user (if buffering is enabled). If the buffer limit is exceeded (15,698), the oldest spectrum is automatically discarded to make room for the new spectrum. The user can clear the buffer at any time.External Triggering Options Instructions for FW3.0and AboveNormal Mode Timing SequenceSoftware Trigger ModeIn this level-triggered mode, the spectrometer is “free running,” just as it is in the Normal mode. The spectrometer is continually scanning and collecting data. With each trigger, the data collected up to the trigger event is transferred to the software. If you continuously apply triggers (for example, by holding down the button on via an external switch), this mode is equivalent to operating in the Normal mode.In the Software Trigger mode, you set the integration time (as well as all other acquisition parameters) in the software.The source for the integration clock comes from the A/D converter.External Triggering Instructions for FW3.0and Above If the software trigger is asserted during integration cycle n, the photons from this integration period will be readout and digitized at the start of integration cycle n+1External Software Triggering–Trigger TimingExternal Synchronous Trigger ModeIn the External Synchronous Trigger Mode, two external triggers are required to complete a data acquisition. The first rising edge starts the integration period and the second rising edge stops the integration while starting the next integration. Thus the integration time is the period between the two external trigger pulses. After the each integration period, the spectra is retrieved and written to the FIFO in the FPGA.For the Maya2000Pro and Maya-LSL, HR2000+,USB2000+,Flame-S and Flame-NIR,as in all nonbuffered modes, no further integrations are possible until the software has read the entire contents of the FIFO.For the QE65000, three spectrum buffers provide software with the most recent spectral acquisitions.External Triggering Options Instructions for FW3.0and AboveExternal Synchronous Trigger Mode Timing SequenceExternal Hardware Level Trigger ModeIn the External Hardware Level Trigger mode, a rising edge detected by the FPGA from the External Trigger input starts the Integration Cycle specified through the software interface. After the Integration Cycle completes, the spectrum is retrieved and written to the FIFO in the FPGA. As long as the trigger level remains active in a logic one state, continuous acquisitions will occur with the following exception. Each subsequent acquisition must wait until a minimum CCD Reset Cycle completes. This Reset Cycle insures that the CCD performance uniform on a scan-to-scan basis. The time duration for this reset cycle is relative to the Integration Cycle time and will change if the integration period is changed. So the timing sequence is Trigger, Trigger Delay,Integration Cycle, Read/Write Cycle, Reset Cycle, Idle Cycle(s), and Integration Cycle (if trigger is still high). The Idle Cycle will on last 2µs if the trigger remains high and the FIFO is empty and a spectrum request is active, otherwise the Idle Cycle will continue until all 3 conditions are satisfied.For the Maya2000Pro and Maya-LSL, HR2000+,USB2000+,Flame-S and Flame-NIR, as in all nonbuffered modes, no integrations are possible until the software has read the entire contents of the FIFO.External Hardware Level Trigger Mode Timing SequenceFor the QE65000, three spectrum buffers provide software with the most recent spectral acquisitions.QE65000 Hardware Level Trigger ModeQE Pro Hardware Level Trigger ModeExternal Hardware Edge Trigger ModeIn the External Hardware Edge Trigger mode, a rising edge detected by the FPGA from the External Trigger input starts the Integration Cycle specified through the software interface. After the Integration Cycle completes, the spectrum is retrieved and written to the FIFO in the FPGA followed by a CCD Reset Cycle. Only one acquisition will be performed for each External Trigger pulse, no matter what thepulse’s duration is. The Reset Cycle insures that the CCD performance uniform on a scan-to-scan basis. The time duration for this reset cycle is relative to the Integration Cycle time and will change if the integration period is changed. So the timing sequence is Trigger, Trigger Delay, Integration Cycle, Read/Write Cycle, Reset Cycle, and Idle Cycle(s). The Idle Cycle will until the next trigger occurs.NoteFor the QE Pro, jitter between external edge trigger and start of column binning (ortrigger delay) is 40ns.Maya2000Pro and Maya-LSL,and QE65000 Hardware Edge Trigger Mode Time TableQE Pro Hardware Edge Trigger Mode Time TableHR2000+,USB2000+and Flame-S Hardware Edge Trigger Mode Time TableNIRQuest Hardware Trigger Mode Time TableHR4000,USB4000and Flame-T TimetablesIt is important to note that the trigger timing in the USB4000and Flame-T will vary depending upon the integration time.This is further detailed in the Time Tables that appear below. These tables reveal that the trigger timing will be different for the following ranges of integration times:∙< 3.8 ms∙ 3.8 ms to 199 ms∙200 ms to 2097 ms∙2097 msUSB Command Description for TriggeringThe USB command Set Trigger Mode sets the spectrometer trigger to one of the trigger mode states as shown below.HR2000+,USB2000+and Flame-S Set Trigger ModeData Value = 0→Normal (Free running) ModeData Value = 1→Software Trigger ModeData Value = 2→External Hardware Level Trigger ModeData Value = 3→External Synchronization Trigger ModeData Value = 4→External Hardware Edge Trigger ModeHR4000,USB4000and Flame-T Set Trigger ModeData Value = 0→Normal (Free running) ModeData Value = 1→Software Trigger ModeData Value = 2→External Hardware Level Trigger ModeData Value = 3→Normal(Shutter)ModeData Value = 4→External Hardware Edge Trigger ModeMaya2000Pro and Maya-LSL,QE65000, QE65 Pro, and QE Pro Set Trigger ModeData Value = 0→Normal (Free running) ModeData Value = 1→External Hardware Level Trigger ModeData Value = 2→External Synchronous Trigger Mode*Data Value = 3→External Hardware Edge Trigger Mode*Not yet implemented on the QE ProNIRQuest Set Trigger ModeData Value = 0→Normal (Free running) ModeData Value = 3→External Hardware Edge Trigger Mode。

Trace32 PXROS用户手册和版本帮助（MANUAL）说明书

OS Awareness Manual PXROS Release 09.2023TRACE32 Online HelpTRACE32 DirectoryTRACE32 IndexTRACE32 Documents ......................................................................................................................OS Awareness Manuals ................................................................................................................OS Awareness Manual PXROS (1)History (3)Overview (3)Brief Overview of Documents for New Users4 Supported Versions4Configuration (5)Quick Configuration Guide5 Hooks & Internals in PXROS6Debug Features (7)Display of Kernel Resources7 Task Stack Coverage7 Task-Related Breakpoints8 Task Context Display9 SMP Support9 Dynamic Task Performance Measurement10 PXROS Specific Menu11Trace Features (12)Task Runtime Statistics12 Function Runtime Statistics13 CPU Load Analysis15 PXROS Specific Menu for Tracing16PXROS Commands (17)TASK.ListmbX Display mailboxes17 TASK.ListObject List objects17 TASK.ListObj.DeLaY Display delay objects18 TASK.ListObj.MailBoX Display mailboxes18 TASK.ListObj.MemClass Display memory classes19 TASK.ListObj.MeSsaGe Display message objects19 TASK.ListObj.OPool Display object pools20 TASK.ListTask Display task table20Version 09-Oct-2023 History08-Oct-19Added support for PXROS v7.OverviewThe OS Awareness for PXROS contains special extensions to the TRACE32 Debugger. This manual describes the additional features, such as additional commands and statistic evaluations.Brief Overview of Documents for New UsersArchitecture-independent information:•“Training Basic Debugging” (training_debugger.pdf): Get familiar with the basic features of a TRACE32 debugger.•“T32Start” (app_t32start.pdf): T32Start assists you in starting TRACE32 PowerView instances for different configurations of the debugger. T32Start is only available for Windows.•“General Commands” (general_ref_<x>.pdf): Alphabetic list of debug commands.Architecture-specific information:•“Processor Architecture Manuals”: These manuals describe commands that are specific for the processor architecture supported by your Debug Cable. T o access the manual for your processorarchitecture, proceed as follows:-Choose Help menu > Processor Architecture Manual.•“OS Awareness Manuals” (rtos_<os>.pdf): TRACE32 PowerView can be extended for operating system-aware debugging. The appropriate OS Awareness manual informs you how to enable theOS-aware debugging.Supported VersionsCurrently PXROS is supported for the following versions:•PXROS 4.x on C166/C167, PowerPC and T riCore•PXROS 5.x, 6.x, 7.x and 8.x on TriCoreConfigurationThe TASK.CONFIG command loads an extension definition file called “pxros.t32” (directory“~~/demo/<arch>/kernel/pxros”). It contains all necessary extensions.TASK.CONFIG ~~/demo/<arch>/kernel/pxros/pxros.t32 [<magic_address>[<args>]]<magic_address>Specifies a memory location that contains the current running task. Thisaddress can be found at “...”.<args>The configuration requires additional arguments, that are:•<sleep>: Currently not used, specify “0”•<dpp>: (only on C166) The first argument configures the datapage settings of the application. Specify a long word which leastsignificant byte is the dpp0 content and which most significant byteis the dpp3 content. E.g. '03060500' means dpp0=0, dpp1=5,dpp2=6 and dpp3=3. If you don't know the dpp settings of yourapplication, just start it for a while and check in the 'register' com-mand the dpp's. Note that the dpp settings must be adapted to everysingle application.•<internal>: The next three arguments are PXROS internal struc-tures. Specify “__PxTasklist __PxTaskRdyFromRdy__PxUsedObjs”.Without any parameters, the debugger tries to locate the internals of PXROS automatically. For this purpose, the kernel symbols must be loaded and accessible at any time the OS Awareness is used (see also “Hooks & Internals”).If you want to display the OS objects “On The Fly” while the target is running, you need to have access to memory while the target is running. In case of ICD, you have to enable SYStem.MemAccess orSYStem.CpuAccess (CPU dependent).Quick Configuration GuideExample scripts are provided in ~~/demo/<arch>/kernel/pxros. It is recommended to take one of these as a starting point and modify it to suit your target and setup.If you already have a setup/configuration script which configures the target and loads the application code and/or symbols, you can add the following lines to your script after the symbols have been loaded: TASK.CONFIG ~~/demo/<arch>/kernel/pxros/pxros.t32MENU.ReProgram ~~/demo/<arch>/kernel/pxros/pxros.menThese lines will automatically configure the awareness and add a custom menu that provides access to many of the features.Hooks & Internals in PXROSNo hooks are used in the kernel.T o retrieve information on the kernel data and structures, the OS Awareness uses the global kernel symbols and structure definitions. Ensure that access to those structures is possible every time when features of the OS Awareness are used.Be sure that your application is compiled and linked with debugging symbols switched on.Debug FeaturesThe OS Awareness for PXROS supports the following debug features.Display of Kernel ResourcesThe extension defines new commands to display various kernel resources. Information on the following PXROS components can be displayed:TASK.ListObject.DeLaY Delay objectsTASK.ListObject.MailBoX or TASK.ListmbX MailboxesTASK.ListObject.MemClass Memory classesTASK.ListObject.MeSsaGe Message objectsTASK.ListObject.OPool Object poolsTASK.ListTask TasksFor a description of the commands, refer to chapter “PXROS Commands”.If your hardware allows memory access while the target is running, these resources can be displayed “On The Fly”, i.e. while the application is running, without any intrusion to the application.Without this capability, the information will only be displayed if the target application is stopped.Task Stack CoverageFor stack usage coverage of tasks, you can use the TASK.STacK command. Without any parameter, this command will open a window displaying with all active tasks. If you specify only a task magic number as parameter, the stack area of this task will be automatically calculated.T o use the calculation of the maximum stack usage, a stack pattern must be defined with the command TASK.STacK.PATtern (default value is zero).T o add/remove one task to/from the task stack coverage, you can either call the TASK.STacK.ADD or TASK.STacK.ReMove commands with the task magic number as the parameter, or omit the parameter and select the task from the TASK.STacK.* window.It is recommended to display only the tasks you are interested in because the evaluation of the used stack space is very time consuming and slows down the debugger display.Task-Related BreakpointsAny breakpoint set in the debugger can be restricted to fire only if a specific task hits that breakpoint. This is especially useful when debugging code which is shared between several tasks. T o set a task-relatedbreakpoint, use the command:Break.Set<address>|<range>[/<option>] /TASK <task>Set task-related breakpoint.•Use a magic number, task ID, or task name for <task>. For information about the parameters, see “What to know about the Task Parameters” (general_ref_t.pdf).•For a general description of the Break.Set command, please see its documentation.By default, the task-related breakpoint will be implemented by a conditional breakpoint inside the debugger.This means that the target will always halt at that breakpoint, but the debugger immediately resumesexecution if the current running task is not equal to the specified task.NOTE:T ask-related breakpoints impact the real-time behavior of the application.On some architectures, however, it is possible to set a task-related breakpoint with on-chip debug logic that is less intrusive. T o do this, include the option /Onchip in the Break.Set command. The debugger then uses the on-chip resources to reduce the number of breaks to the minimum by pre-filtering the tasks.For example, on ARM architectures: If the RTOS serves the Context ID register at task switches, and if the debug logic provides the Context ID comparison, you may use Context ID register for less intrusive task-related breakpoints:eContextID ON Enables the comparison to the whole Context ID register.Break.CONFIG.MatchASID ON Enables the comparison to the ASID part only.TASK.List.tasks If TASK.List.tasks provides a trace ID (traceid column), thedebugger will use this ID for comparison. Without the trace ID,it uses the magic number (magic column) for comparison.When single stepping, the debugger halts at the next instruction, regardless of which task hits thisbreakpoint. When debugging shared code, stepping over an OS function may cause a task switch and coming back to the same place - but with a different task. If you want to restrict debugging to the current task,you can set up the debugger with SETUP .StepWithinTask ON to use task-related breakpoints for single stepping. In this case, single stepping will always stay within the current task. Other tasks using the same code will not be halted on these breakpoints.If you want to halt program execution as soon as a specific task is scheduled to run by the OS, you can use the Break.SetTask command.Task Context DisplayY ou can switch the whole viewing context to a task that is currently not being executed. This means that all register and stack-related information displayed, e.g. in Register , Data.List , Frame etc. windows, will refer to this task. Be aware that this is only for displaying information. When you continue debugging the application (Step or Go ), the debugger will switch back to the current context.T o display a specific task context, use the command:•Use a magic number, task ID, or task name for <task>. For information about the parameters, see “What to know about the Task Parameters” (general_ref_t.pdf).•To switch back to the current context, omit all parameters.T o display the call stack of a specific task, use the following command:If you’d like to see the application code where the task was preempted, then take these steps:1.Open the Frame /Caller /Task <task> window. 2.Double-click the line showing the OS service call.SMP SupportThe OS Awareness supports symmetric multiprocessing (SMP).Frame.TASK [<task>] Display task context.Frame /Task <task>Display call stack of a task.An SMP system consists of multiple similar CPU cores. The operating system schedules the threads that are ready to execute on any of the available cores, so that several threads may execute in parallel.Consequently an application may run on any available core. Moreover, the core at which the application runs may change over time.T o support such SMP systems, the debugger allows a “system view”, where one TRACE32 PowerView GUI is used for the whole system, i.e. for all cores that are used by the SMP OS. For information about how to set up the debugger with SMP support, please refer to the Processor Architecture Manuals.All core relevant windows (e.g. Register.view) show the information of the current core. The state line of the debugger indicates the current core. Y ou can switch the core view with the CORE.select command.T arget breaks, be they manual breaks or halting at a breakpoint, halt all cores synchronously. Similarly, a Go command starts all cores synchronously. When halting at a breakpoint, the debugger automatically switches the view to the core that hit the breakpoint.Because it is undetermined, at which core an application runs, breakpoints are set on all coressimultaneously. This means, the breakpoint will always hit independently on which core the application actually runs.Dynamic Task Performance MeasurementThe debugger can execute a dynamic performance measurement by evaluating the current running task in changing time intervals. Start the measurement with the commands PERF.Mode TASK and PERF.Arm, and view the contents with PERF.ListTASK. The evaluation is done by reading the ‘magic’ location (= current running task) in memory. This memory read may be non-intrusive or intrusive, depending on the PERF.METHOD used.If PERF collects the PC for function profiling of processes in MMU-based operating systems(SYStem.Option.MMUSPACES ON), then you need to set PERF.MMUSPACES, too.For a general description of the PERF command group, refer to “General Commands Reference Guide P” (general_ref_p.pdf).PXROS Specific MenuThe menu file “pxros.men” contains a menu with PXROS specific menu items. Load this menu with the MENU.ReProgram command.Y ou will find a new menu called PXROS.•The Display menu items launch the kernel resource display windows.•The Stack Coverage submenu starts and resets the PXROS specific stack coverage and provides an easy way to add or remove tasks from the stack coverage window.In addition, the menu file (*.men) modifies these menus on the TRACE32 main menu bar:•The Trace, List menu is extended.-“Task Switches” shows a trace list window with only task switches (if any)-“Default and T asks” shows switches together with the default display.•The Perf menu contains additional submenus-“Task Runtime” enables and shows the task runtime analysis-“Task Function Runtime” enables and shows the function runtime statistics based on tasks-“CPU Load” enables and shows the CPU load analysisTrace FeaturesThe OS Awareness for PXROS supports the following trace features.Task Runtime StatisticsNOTE:This feature is only available, if your debug environment is able to trace taskswitches (program flow trace is not sufficient). It requires either an on-chip tracelogic that is able to generate task information (eg. data trace), or a softwareinstrumentation feeding one of TRACE32 software based traces (e.g. FDX orLogger). For details, refer to “OS-aware Tracing” (glossary.pdf).Based on the recordings made by the Trace (if available), the debugger is able to evaluate the time spent ina task and display it statistically and graphically.T o evaluate the contents of the trace buffer, use these commands:Trace.List List.TASK DEFault Display trace buffer and task switchesTrace.STATistic.TASK Display task runtime statistic evaluationTrace.Chart.TASK Display task runtime timechartTrace.PROfileSTATistic.TASK Display task runtime within fixed time intervalsstatisticallyTrace.PROfileChart.TASK Display task runtime within fixed time intervals ascolored graphTrace.FindAll Address TASK.CONFIG(magic) Display all data access records to the “magic”locationTrace.FindAll CYcle owner OR CYcle context Display all context ID records The start of the recording time, when the calculation doesn’t know which task is running, is calculated as “(unknown)”.Function Runtime StatisticsAll function-related statistic and time chart evaluations can be used with task-specific information. Thefunction timings will be calculated dependent on the task that called this function. T o do this, in addition to the function entries and exits, the task switches must be recorded.T o do a selective recording on task-related function runtimes based on the data accesses, use the following command:NOTE:This feature is onlyavailable, if your debug environment is able to trace task switches (program flow trace is not sufficient). It requires either an on-chip tracelogic that is able to generate task information (eg. data trace), or a software instrumentation feeding one of TRACE32 software based traces (e.g. FDXor Logger ). For details, refer to “OS-aware Tracing” (glossary.pdf).; Enable flow trace and accesses to the magic location Break.Set TASK.CONFIG(magic) /TraceDataT o do a selective recording on task-related function runtimes, based on the Arm Context ID, use the following command:T o evaluate the contents of the trace buffer, use these commands: The start of the recording time, when the calculation doesn’t know which task is running, is calculated as “(unknown)”.; Enable flow trace with Arm Context ID (e.g. 32bit)ETM.ContextID 32Trace.ListNesting Display function nestingTrace.STATistic.FuncDisplay function runtime statistic Trace.STATistic.TREEDisplay functions as call tree Trace.STATistic.sYmbol /SplitTASK Display flat runtime analysis Trace.Chart.FuncDisplay function timechart Trace.Chart.sYmbol /SplitTASKDisplay flat runtime timechartCPU Load AnalysisNOTE:This feature is only available, if your debug environment is able to trace taskswitches (program flow trace is not sufficient). It requires either an on-chip tracelogic that is able to generate task information (eg. data trace), or a softwareinstrumentation feeding one of TRACE32 software based traces (e.g. FDX orLogger). For details, refer to “OS-aware Tracing” (glossary.pdf).Based on the recordings made by the Trace (if available), the debugger is able to evaluate the CPU load.The CPU load is calculated by comparing the time spent in all tasks against the time spent in the idle task.The measurement is done by using the GROUP command to group all idle tasks and calculating the time spent in all other tasks.Example: T wo idle tasks named “IdleT ask1” and “IdleT ask2”:; Create a group called "idle" with the idle tasksGROUP.CreateTASK "idle" "IdleTask1"GROUP.CreateTASK "idle" "IdleTask2"; Unmark “idle” and mark all others in redGROUP.COLOR "idle" NONEGROUP.COLOR "other" RED; Merge idle tasks and other tasksGROUP.MERGE "idle"GROUP.MERGE "other"T o evaluate the contents of the trace buffer, use these commands:Trace.STATistic.TASK Display CPU load statistic evaluationTrace.PROfileChart.TASK Display CPU load as colored graph The start of the recording time, when the calculation doesn’t know which task is running, is calculated as “(unknown)”.When CPU load analysis is no longer needed, or if a detailed Task Runtime Statistic is needed, disable the grouping of the tasks with:;commentsGROUP.SEParate "idle"GROUP.SEParate "other"PXROS Specific Menu for TracingThe menu entries specific to tracing are already described in the menu for debug features.PXROS CommandsTASK.ListmbXDisplay mailboxesThis command is just an alias for Task.ListObj.MailBoX. See there for a description.TASK.ListObjectList objectsList PXROS objects. See detailed descriptions below.Format:TASK.ListmbX <mbx_id >Format:TASK.ListObject.[<object>]<object >:MeSsaGe | DeLaY | OPool | MemClass | MailBoXTASK.ListObj.DeLaYDisplay delay objectsDisplays a table of the delay objects in the system.TASK.ListObj.MailBoXDisplay mailboxesWithout any argument, this command displays all system and private mailboxes.With a mailbox a mailbox id as an argument, it shows the specified mailbox with it's pending messages and waiting tasks.Format:TASK.ListObj.DeLaYFormat:TASK.ListObj.MailBoX <mbx_id >TASK.ListObj.MemClass Display memory classes Format:TASK.ListObj.MemClassDisplays a table of the memory classes.The 'type' field contains the memory class type. If this is fixed, the 'blksize' field contains the block size.'fbytes' and 'fblks' contain the free bytes and free blocks in that mc.TASK.ListObj.MeSsaGe Display message objects Format:TASK.ListObj.MeSsaGeDisplays a table of the message objects in the system.The 'data' field shows the pointer to the message data.The 'size' field specifies the message size, while 'buff' is the siye of the entire data area.The 'type' is either 'Req' for 'PxMsgRequest' or Env for 'PxMsgEnvelop'.TASK.ListObj.OPoolDisplay object poolsDisplays a table of the object pools.The 'wait' column contains the number of waiting tasks.TASK.ListTaskDisplay task tableWithout any argument this command displays a list of tasks. For an explanation of the mode bits check the PXmon manual.With an ID or a task name as an argument, you get a detailed description of that task.Format:TASK.ListObj.OpoolFormat:TASK.ListTask <task >。

AVCS-User-Guide

User GuideIncluding the ADMIRALTY Information OverlayS-63 Edition 1.11Quick Start Guide 3 Electronic Navigational Charts (ENCs) 3 Before You Start 3 ECDIS Containing Existing ENCs 3 Step 1: Install the Public Key 4 Step 2: Install Permits 4 Step 3: Install AVCS ENCs 4 Step 4: Update AVCS 4 Step 5: Install the ADMIRALTY Information Overlay 5 Step 6: Maintain your Holdings 52ADMIRALTY Vector Chart Service Overview 6 2.1Introduction 6 2.2AVCS Overview 6 2.3Quality 6 2.4Carriage Compliant 6 2.5Electronic Navigational Charts 6 2.6Licensing 63Getting Started 7 3.1General 7 3.2Media formats for AVCS 7 3.3New AVCS Customers 7 3.4The AVCS Licence 83.5The ‘Schedule A’8 3.6Data Cleansing 9 3.7Public Key 94Installing and Maintaining the Chart Outfit 10 4.1New ENC Permits 10 4.2Updating 10 4.3Base Discs 10 4.4README.TXT File 10 4.5Cancelled ENCs 11 4.6Adding Chart Coverage 115ADMIRALTY Information Overlay 126S-58 Recommended ENC Validation Checks 13 6.1Important Information for Users 137Security Scheme Errors (SSE) 14 7.1Common Error Codes 14 7.2Decryption Failure 14 7.3Conversion Errors 148Getting Help 16 8.1Technical Support 16 8.2Feedback 17UKHO 2016 All Rights ReservedThe copyright in this document, which contains information of a proprietary nature, is vested in UKHO. The content of this document may not be used for purposes other than that for which it has been supplied and may not be reproduced, either wholly or in part, in any way whatsoever.1Quick Start GuideThis Quick Start guide is designed to help you to load and maintain your ADMIRALTY Vector Chart Service (AVCS) data easily and quickly. It describes the basic steps necessary to use AVCS in any ECDIS. However the functionality for loading and maintaining AVCS will differ from one ECDIS to another and this guide should be used in conjunction with the User Manual supplied by your ECDIS manufacturer.For a more detailed guide to AVCS installation and troubleshooting information, refer to sections 2 – 8 of this document and the User Manual supplied by the manufacturer of your ECDIS.Electronic Navigational Charts (ENCs)AVCS is comprised entirely of Electronic Navigational Charts (ENCs) issued by Government Hydrographic Offices. It is designed to be used in conjunction with a type approved ECDIS to provide a primary navigation tool that meets the requirements of SOLAS Chapter V.Before You StartWhen subscribing to AVCS for the first time your ADMIRALTY Chart Agent will provide the following materials:CD Users> AVCS User Guide including the Quick Start Guide (this document)> AVCS Base Discs (a set of ‘Base’ CDs)> AVCS Update Disc> ADMIRALTY Information Overlay (AIO) CD (if you have a compatible display system and the Overlay has been added to your licence)> End-User Licence Agreement for digital data servicesDVD Users> AVCS User Guide including the Quick Start Guide (this document)> AVCS DVDs (2 discs containing both base ENCs and updates)> ADMIRALTY Information Overlay (AIO) CD (if you have a compatible display system and the Overlay has been added to your licence)> End-User Licence Agreement for digital data servicesAll usersAn e-mail or hard media containing:> Schedule A (a PDF document listing the Folios and Units that you have licensed, not required if you are using ADMIRALTY e-Navigator Planning Station)> A set of ENC Permit files (PERMIT.TXT and ENC.PMT) for each ECDIS equipment> AVCS Certificate (a PDF or printed document showing your vessel and licence details)ECDIS Containing Existing ENCsIf ENCs are already installed on the ECDIS it is strongly recommended that these are removed from the system database to avoid any conflicts. If the option is available it is also recommended that users should remove any installed permits. Please see your ECDIS User Manual for more information.Step 1: Install the Public KeyIn order to load ENCs from AVCS onto an ECDIS the correct public key must be installed. For AVCS ENCs authenticated using the S-63 1.1 standard the IHO Public Key must be used and the user should check that the IHO Public Key is installed on the ECDIS.New ECDIS are supplied with the IHO Public Key pre-installed. However users transferring from another service may find that the system is using the PRIMAR Public Key. In this case the IHO Public Key must be installed before AVCS ENCs can be loaded.The IHO Public Key is contained in the root folder on any AVCS S-63 1.1 Media.The procedure for installing the Public Key is different on each ECDIS and will be detailed in your ECDIS User Manual. Specific instructions for some common models of ECDIS are available by following this link:/AVCSStep 2: Install PermitsBefore loading AVCS ENCs, the ENC Permits must be installed on the system. The permits are supplied by your ADMIRALTY Chart Agent and consist of 2 files for each ECDIS:> PERMIT.TXT> ENC.PMTAVCS customers with multiple ECDIS on board should be careful to load the correct permits into the corresponding system.Failure to install the correct permit will result in an error being reported similar to the following:> CRC failure permit could not be read> Failure to uncompress ENC data file> Decryption failedStep 3: Install AVCS ENCsThe AVCS data is supplied on CD or DVD. Each Base CD contains ENCs from one or more producer nations (countries) and is labelled with the country names. The DVDs contain worldwide ENCs and all available updates. Note that some countries (such as the United Kingdom) produce data worldwide so the Base discs do not directly correspond to a geographical area.It is only necessary to load the discs that contain licensed ENCs, as listed in the Schedule A or e-Navigator Planning Station. The ECDIS will manage the installation of all ENC cells based on the installed ENC Permits.Customers should be aware that, depending on the manufacturer, ECDIS manage the import of ENCs differently. Step 4: Update AVCSUpdates to the ENCs in AVCS are available free of charge online and on disc.Updates can be downloaded online using e-Navigator Planning Station (which is an integrated catalogue, holdings management, ordering and updating system). Contact your ADMIRALTY Chart Agent.All base ENCs and updates are contained on the AVCS DVDs, which are issued every week. In order to update the ECDIS only the latest AVCS DVDs held should be used and run as an update.Base CDs contain all base charts and updates valid at the time of issue. Subsequent chart editions and updates are contained on the latest Update CD. Both Base CDs and Update CD are labelled with the week number of the data that they contain.Depending on your ECDIS, you now need to load the updates from the Base CDs and the Update CD, or just from the Update CD.Step 5: Install the ADMIRALTY Information OverlayThe ADMIRALTY Information Overlay (AIO) is a digital dataset that is designed to be displayed over ENCs in ECDIS and other chart display systems to provide additional information to the navigator. The Overlay contains all ADMIRALTY Temporary & Preliminary Notices to Mariners (T&P NMs) and ENC Preliminary Notices to Mariners (EP NMs), which highlight navigationally significant differences between ENCs and ADNIRALTY paper charts.The Overlay can be displayed on compatible ECDIS equipment and also in ADMIRALTY e-Navigator Planning Station. Please see the UKHO website at /AVCS for an up to date list of compatible equipment, or consult your ECDIS supplier.The Overlay data is held on a single CD and is installed and updated in the same way as ENCs. Please notify your ADMIRALTY Chart Agent if you wish to use the Overlay on any compatible ECDIS so that the Overlay permit can be added to the ENC Permit files for that equipment.The Overlay permit will be loaded at the same time as the ENC Permits in Step 2. Follow Steps 3 and 4 to install the ADMIRALTY Information Overlay CD.Step 6: Maintain your HoldingsYour ADMIRALTY Chart Agent will supply you with updates to your AVCS data weekly.For customers using the AVCS DVDs, all base charts and updates are contained on the DVDs and new discs are issued every week. In order to update the ECDIS only the latest AVCS DVDs held should be installed.For customers using the AVCS CD each weekly Update CD is cumulative and only the most recent disc should be installed.The AIO CD is cumulative and only the most recent disc should be installed.A new set of ENC Permits will also be supplied by your ADMIRALTY Chart Agent whenever an ENC has a new edition or you are entitled to access additional ENCs. The new permits relate directly to the discs of the same week number. The permits may be received from your ADMIRALTY Chart Agent by e-mail or on hard media.The ENC Permits may be received before you have received the relevant Update discs. It is recommended that you should not install new permits unless they are accompanied by the appropriate DVDs or CDs. The permits will be accompanied by a Schedule A that identifies the week number for which the permits are valid. Failure to use the correct set of permits with an Update disc may result in an error being reported similar to the following:> There is no valid permit for this version of the cell/chart> Edition number is not valid> Permit is for an older version of the cell/chartENC updates are also available by email and over the Internet through ADMIRALTY e-Navigator Planning Station or the AVCS Online Updating Service. AIO updates are also available through e-Navigator.If new ENC Permits have been received, they should be loaded in to the ECDIS before the DVDs or Update CD is loaded.Periodically the AVCS Base CDs are re-issued to free up space on the Update CD. Customers who already subscribe to AVCS should treat these as though they were update CDs and load each in turn. The ECDIS will only load the additional new editions and updates necessary to bring the system database up-to-date.2ADMIRALTY Vector Chart Service Overview2.1 IntroductionThis section of the guide is intended to provide more detailed instructions and troubleshooting information for the ADMIRALTY Vector Chart Service and provide answers to some questions that users may have after installing AVCS.AVCS ENCs are produced and distributed according to well-defined international standards. However each ECDIS manufacturer has implemented the ENC import module of these standards differently.As a result the functionality for loading and maintaining AVCS will differ from one ECDIS to another and this guide provides generic information to assist in managing and maintaining AVCS holdings. This guide should be used in conjunction with the User Manual supplied by your ECDIS manufacturer.2.2 AVCS OverviewThe ADMIRALTY Vector Chart Service (AVCS) brings together Electronic Navigational Charts (ENCs) from national Hydrographic offices around the world and new ENC coverage produced by UKHO in co-operation with Foreign Governments to provide comprehensive, official, worldwide coverage.2.3 QualityAVCS meets customer requirements for a comprehensive, world-wide, fully carriage compliant electronic chart service. AVCS continues to develop in response to customer feedback through an ongoing programme of enhancements.UKHO has instituted a programme of assessment by its professional cartographers where the content of the ENC is compared to relevant paper charts. Any navigationally significant differences are communicated to users of AVCS through AIO. No other electronic chart service offers this level of reassurance.2.4 Carriage CompliantAVCS only contains ENC data that meets Safety of Life at Sea (SOLAS) Carriage Requirements for use within Electronic Chart Display and Information Systems (ECDIS).2.5 Electronic Navigational ChartsElectronic Navigational Charts (ENCs) are digital vector charts produced to the International Hydrographic Organization's (IHO's) standards (S-57 Version 3.1 and ENC Product Specification). They are referred to World Geodetic System 1984 Datum (WGS84) and are regularly updated with official update information distributed digitally.Hydrographic offices do not take any responsibility for the accuracy or reliability of privately produced, unofficial charts.2.6 LicensingThe ENCs in AVCS are provided under a licence agreement that allows their use for defined periods of time. AVCS Folios and ENC Units may be added to an AVCS licence at any time for periods of 3, 6, 9 or 12 months (where data supply agreements allow). This offers maximum choice and the flexibility to match your chart holdings to your operational patterns.You will be provided with an AVCS media pack, containing world-wide AVCS data and receive weekly updates.3Getting Started3.1 GeneralAVCS ENCs are distributed on both CD and DVD media and are encrypted according to the International Hydrographic Organization (IHO) S-63 1.1 Data Protection Scheme.The CD service comprises 9 base discs containing all ENCs and updates held in AVCS at the time of issue, these are issued at intervals of approximately 8 weeks. In each week between bases, a cumulative update disc is issued containing all AVCS updates issued since the most recent base.The DVD service is a snapshot of all data available from AVCS provided on 2 discs on a weekly basis. It contains all base and update cells applicable at the time of issue. In this respect the DVD contents are equivalent to an AVCS base release every week rather than bundling a single base release together with the weekly cumulative update. This simplifies the work for the ECDIS in reading the data into the system.These two AVCS formats are shown in the diagram at 3.2.3.2 Media formats for AVCS3.3 New AVCS CustomersWhen subscribing to AVCS for the first time your ADMIRALTY Chart Agent will provide the following materials:CD Service> AVCS User Guide including the Quick Start Guide (this document)> AVCS Base Discs (a set of CDs labelled ‘Base’)> AVCS Update Disc> AIO CD (if you have a compatible display system and the Overlay has been added to your licence)> End-user Licence Agreement for digital data services (EULA)DVD Service> AVCS User Guide including the Quick Start Guide (this document)> AVCS DVDs (2 discs containing both base ENCs and updates)> AIO CD (if you have a compatible display system and the Overlay has been added to your licence)> End-user Licence Agreement for digital data services (EULA)In addition a number of type specific AVCS Installation Guides are available for download by following the link below and selecting the Display Systems tab: /AVCSThe latest base and update CDs or the latest DVDs will contain all of the ENCs in AVCS. However these cannot be accessed by the ECDIS until valid ENC Permits are installed.3.4 The AVCS LicenceIn addition to the AVCS media your ADMIRALTY Chart Agent will provide you with an AVCS License Pack containing the following:> A ‘Schedule A’ this is a PDF document listing the Folios and ENC Units that the user is licensed to use and which Base CDs must be used to install the user’s licensed ENCs.> A set of ENC Permit files (PERMIT.TXT and ENC.PMT) for each ECDIS on the AVCS Licence.> A Certificate, carrying the UKHO crest, which certifies that all charts supplied in AVCS are ENCs that conform to the requirements of SOLAS Chapter V.Each permit is unique and is the method which gives the user access to the required ENCs.The ENC Permits will be supplied in a zipped file and t he contents of this file will depend on the user’s bridge configuration as each AVCS licence allows for use on up to 5 ECDIS. When extracted one or more set of permit files (PERMIT.TXT and ENC.PMT) will be copied automatically into folder(s) named MASTER, BACKUP, RESERVE1, RESERVE2 and RESERVE3 depending on the number of ECDIS configured on the bridge.The permits may be supplied on physical media, separately by email or directly from e-Navigator. The contents should be extracted to removable media, e.g. USB flash drive, that is capable of being read by the ECDIS system.There are currently 9 AVCS Base CDs and the DVDs contain 9 equivalent Volumes. It is unlikely that users will need to install data from every one of the CDs or the equivalent folders on the DVDs to load all of their licensed ENCs. Reference to the Schedule A can avoid the unnecessary loading of CDs and save the user time.3.5 The ‘Schedule A’The Home CD column of the Schedule A document informs the user which Base CDs or Volumes on the DVDs are required to install all licensed ENCs. A sample of the information contained in the Schedule A is provided below:Cell Title Home CD AVCS UpdateGB301820 Isles of Scilly and Western Approaches AVCS Base 3 N/AGB301840 Land's End to Falmouth AVCS Base 3 AVCS UpdateGB302020 Falmouth to Looe AVCS Base 3 N/ACell Title Home CD AVCS UpdateGB202868 Tokongkemudi to Natuna Utara AVCS Base 9 N/AGB202870 Pulau-Pulau Leman to Badas AVCS Base 9 AVCS UpdateGB202872 Selat Karimata and Approaches AVCS Update N/ANote: If the user does NOT have a copy of the Schedule A they should refer to the media.txt file at the root level of the AVCS disc to determine which Volume contains the data for a given Producer Code. If in any doubt the complete set of AVCS Base CDs must be installed to ensure that all licensed ENCs are imported to the system.3.6 Data CleansingNew AVCS customers who had previously subscribed to other ENC services are strongly recommended to remove (purge) all ENC Permits and ENCs from the system before installing AVCS. Previously installed ENCs may become out of date if they are not licensed in AVCS. If the system is not purged redundant ENCs may remain in the system database (SENC) and be available for use, even if the previous licence has expired. Instructions on how to remove permits and ENCs are described in the ECDIS operator’s manual or the ECDIS specific AVCS Installation guide.3.7 Public KeyBackgroundIn order to load ENCs from AVCS onto an ECDIS the correct Public Key must be installed. This allows the ECDIS to authenticate the source and integrity of encrypted ENCs from Service Providers. For AVCS ENCs authenticated using the S-63 1.1 standard the IHO public key must be used. If the correct Public Key is not installed the ECDIS will report an Authentication Failure.The Public Key can be formatted in one of two ways:> ASCII text file (.PUB)> X509 Certificate (.CRT)Check the Public KeyBefore installing AVCS ENCs encrypted using S-63 1.1 the user must check that the IHO Public Key is installed on the ECDIS. If the IHO Public Key is not present on the system then it will have to be installed before AVCS ENCs can be loaded.New ECDIS are supplied with the IHO Public Key pre-installed. However users transferring from another service may find that the system is using the PRIMAR Public Key. In this case the IHO Public Key must be installed before AVCS ENCs can be loaded.The IHO Public Key is contained in the root folder on any AVCS S-63 1.1 media.The procedure for installing the Public Key is different on each ECDIS and will be detailed in your ECDIS User Manual. Specific instructions for some common models of ECDIS are available by following this link: /AVCS4Installing and Maintaining the Chart Outfit4.1 New ENC PermitsYou will automatically be issued with all necessary ENC Permits for access to new or replaced ENCs on your AVCS license. Please ensure that you load the new permits before installing the latest media to ensure your ECDIS can use the latest ENCs.When updating AVCS new permits should only be installed on the ECDIS when the corresponding media has been received.4.2 UpdatingThe ADMIRALTY Vector Chart Service can be updated in one of four ways:CD Issued weekly, the Update CD contains all the latest ‘Notice s to Mariners’ corre ctions, New Editions and any New Charts issued since the last Base disc.DVD Issued weekly, the DVDs contain all the latest base and update information for AVCS on 2 discs.e-Navigator Planning Station Allows the user to create a custom exchange set cont aining the latest ‘Notice s to Mariners’ corrections, New Editions and New Charts issued since the last time they updated their AVCS holdings.AVCS Online Updating Service Allows the user to create a custom exchange set containing the latest ‘Notice s to Mariners’ corrections, New Editions and New Charts issued since the last time they updated their AVCS holdings.If you are using the AVCS CD or DVD service and you receive multiple discs at the same time, you only need to use the most recent one because they are cumulative.If replacement AVCS Base CDs have been issued, containing New Editions or Updates, subsequent Update CDs cannot be installed until the Base discs have been installed.Stored Routes and UpdatesUpdates applied to the ECDIS may have a navigational impact on an area covered by a stored route. It is important to check the effect of any updates on these routes prior to their use. ECDIS is able to automatically check route safety where licensed AVCS data is available.4.3 Base DiscsFor users of the CD service, the UKHO periodically issues a full set of AVCS Base discs on CD in order to integrate newly available data that has been issued on the Update CD. When this happens, all currently available Base discs are issued simultaneously. All New Editions and updates are then included on the replacement AVCS Base discs and no accompanying Update CD will be issued in that week.On receipt of re-issued AVCS Base CDs, only an update routine needs to be run on each disc and there is no requirement to reload all charts.The AVCS DVDs contain all base ENCs and updates available so there is no distinction between Base and Update discs.4.4 README.TXT FileAll AVCS discs contain a ‘README.TXT’ file which includes important safety information that should be read before using the service. For example it includes a caution concerning ENCs derived from charts which are not on WGS84 or a compatible datum.The file is located in the ENC_ROOT folder and contains the following information:> Specific charting practices of some ENC producers which may be significant to navigation.> Specific updating practices of some ENC producers such as delays between the issue of paper NMs and ENC updates.> Identified overlaps between ENCs which may cause problems in display systems.> ENCs which have been withdrawn from service for any reason and which should not be used (permits will not normally be issued for these ENCs).> Specific licence and disclaimer text required by some ENC producers.The README.TXT file is updated every week and changes are highlighted in a ‘Latest Corrections’ section at the beginning. The file should be read as part of the weekly ENC update process to ensure that all relevant changes are understood.The latest README.TXT file can also be viewed in ADMIRALTY e-Navigator Planning Station.4.5 Cancelled ENCsPeriodically ENCs are cancelled as part of the continuous maintenance of ENC coverage worldwide. Normally cancelled ENCs are automatically replaced and you will experience no loss of coverage in your ECDIS.It is strongly recommended that you choose to delete any cancelled ENCs from the SENC as failure to do so may result in the ECDIS displaying out of date data in preference to more up to date data.4.6 Adding Chart CoverageAdditional AVCS Folios and Units may be purchased during the subscription period through your chosen ADMIRALTY Chart Agent who will supply new ENC Permits to ‘unlock’ the newly added data. These permit files are cumulative so as well as unlocking the new coverage they will also hold the permits necessary to unlock all your existing coverage.5ADMIRALTY Information OverlayThe ADMIRALTY Information Overlay (AIO) is a digital dataset that is designed to be displayed over ENCs in ECDIS and other chart display systems to provide additional information during passage planning. The Overlay contains all ADMIRALTY Temporary & Preliminary Notices to Mariners (T&P NMs) and highlights navigationally significant differences between ENCs and ADMIRALTY paper charts.The Overlay makes passage planning simpler by clearly showing where important Temporary or Preliminary changes may impact a voyage. It also draws attention to areas where differences between ENCs and paper charts may affect the passage plan.All ADMIRALTY T&P NMs that are in force are included in the Overlay. Each NM is displayed as a simple polygon (usually rectangular) with hatched fill which indicates the area affected by the NM. Each NM carries the same NM number that is used in the ADMIRALTY Notices to Mariners Bulletin.The full text of the NM is included as an associated text file which can be displayed by selecting the 'Temporary Notice to Mariners' or 'Preliminary Notice to Mariners' feature in the ECDIS Pick Report. Any associated diagrams can also be viewed through the Pick Report.The T&P NMs that are shown in the Overlay relate specifically to ADMIRALTY paper charts and are overlaid on ENCs to alert users to the availability of this information when passage planning. AIO may not contain all T&P NMs issued by the ENC producer and there may be a time delay between the publication or cancellation of national T&P NMs and the publication or removal of the equivalent ADMIRALTY T&P NMs. Many ENC producers include some or all of their T&P NMs in their ENCs and care should be taken to understand what has already been included in the ENCs in use. A list of ENC producers whose policy is to include T&P NM information in their ENCs can be found at /AVCS and in the \INFO folder on all AVCS discs. Please note that official ENCs remain the primary source of information for navigation at all times.ENC Preliminary (EP) NMs highlight navigationally significant differences between ENCs and ADMIRALTY paper charts. These NMs are displayed in the same way as T&P NMs, as a simple polygon (usually rectangular) with hatched fill which indicates the area affected by the NM. Each NM is allocated a unique EP NM number.The full text of the NM can be viewed in the ECDIS Pick Report against the Information attribute. Where additional information is needed to explain the NM an associated picture file displays an image showing the ENC superimposed over the current paper chart information.The Overlay can be displayed on compatible ECDIS equipment and also in ADMIRALTY e-Navigator Planning Station. Please see the UKHO website at /AVCS for an up to date list of compatible equipment, or consult your ECDIS supplier.The Overlay data is held on a single CD and is installed and updated in the same way as ENCs. Please notify your ADMIRALTY Chart Agent if you wish to use the Overlay on any compatible ECDIS so that the Overlay permit can be added to the permit files for that equipment.6S-58 Recommended ENC Validation Checks6.1 Important Information for UsersThe International Hydrographic Organization (IHO) is aware that some ECDIS system manufacturers have mistakenly incorporated some or the entire suite of ENC validation checks listed in IHO publication S-58 - Recommended ENC Validation Checks. This has resulted in mariners being presented with misleading error messages indicating that officially produced and released ENC data contains errors, when it does not. In some cases, official ENC data is even being reported as not suitable for navigational use.The majority of the checks in S-58 are intended for use in the ENC validation software that is used by Hydrographic Offices or Regional ENC Coordinating Centres. These S-58 checks were not intended to be used in ECDIS software. The introduction to S-58 reads, in part “…specifies the checks that, at a minimum, producers of ENC validation tools should include in their validation software. This software will be used by hydrographic offices to help ensure that their ENC data are compliant with the S-57, Appendix B1 ENC Product Specification...”.Of particular concern are the S-58 checks classified as warnings. These checks are intended to highlight apparent discrepancies in the data so that HO’s or RENCs can investigate them further. Upon inv estigation, the data will usually be found to be correct and no change to the ENC data is required. Such investigations are carried out by the ENC producer, as well as by the Regional ENC Coordinating Centre before the data is released. Once an ENC has been officially released, it is therefore not necessary or recommended that these checks be performed again by ECDIS software, since any warnings of this type that are generated will be incorrect and will be misleading for the user.Many ECDIS manufacturers still implement the full suite of tests identified in S-58. This can result in unnecessary errors and warnings being presented to the user either on screen or in a log file. Users should only report instances where an ENC has failed to load; these are normally identified by the ECDIS as a fatal error or ENC failed import. In these instances the UKHO will seek to resolve this with the ENC producer.。

EpiData3.0使用手册中国疾病预防控制中心编写

Epi Data 3.0软件培训教材中国疾病预防控制中心公共卫生监测与信息服务中心卫生统计研究室北京宣武区南纬路27号 4-25电话：(010)63173960 传真：(010)63173345 Email：wwwjs@ 联系人：王建生Epi Data 3.0软件使用手册目录介绍 (4)E PI D ATA 中数据库创建过程 (4)一、建立数据库结构 (4)二、生成数据文件 (6)三、数据录入 (7)四、添加质量控制文件 (8)变量名称 (9)一、自动生成变量名 (9)二、把第一个词作为变量名 (10)变量标签 (11)更改变量名 (11)修改数据文件 (11)数据文件的纵向连接和横向连接 (12)一、纵向连接 (12)二、横向连接 (13)记录查找 (14)数据双录入和核对 (14)一、选则关键字段 (14)二、选则项： (15)E PI D ATA 中的字段类型 (15)一、自动编码字段 (15)二、数值型字段 (16)三、字符型字段 (16)四、大写型字符字段 (16)五、是否型字段 (16)六、日期型字段 (16)七、今天型日期字段 (16)八、Soundex型字段 (16)九、加密型字段 (17)十、隔位符 (17)常用核对命令 (17)AFTER ENTRY (17)AFTER FILE (17)AFTER RECORD (18)AUTOJUMP (18)AUTOSAVE (18)BEFORE ENTRY (18)BEFORE FILE (19)BEFORE RECORD (19)CLEAR (19)COMMENTS (*) (19)COMMENT LEGAL (19)CONFIRM (20)CONFIRMFIELD (20)DEFINE (21)EXIT (21)GOTO (21)GOTO WRITEREC (21)HELP (21)HIDE, UNHIDE (22)IF..THEN (22)IGNOREMISSING (23)JUMPS (23)KEY (24)LABEL / LABELBLOCK (24)LEGAL (25)LET (25)MUSTENTER (25)NOENTER (25)RANGE (25)RELATE (26)REPEAT (26)TYPE (26)TYPE COMMENT (26)TYPE STATUSBAR (27)WRITENOTE (27)快捷键和鼠标操作 (27)一、快捷键 (28)二、编辑窗口中 (28)三、数据录入窗口中 (28)四、在核对命令编辑窗口 (28)五、数据录入窗口 (29)运算符和函数 (29)一、操作符(计算型、逻辑型) (29)二、数值型函数 (29)三、字符型函数 (30)四、日期型函数 (31)E PI D ATE和E PI I NFO的兼容性 (33)一、字段类型不相同 (33)二、变量名命名规则 (33)三、核对命令 (33)四、在一些计算和表达式方面二者有稍微不同 (33)介绍EpiData 是用于数据录入、数据核对、数据管理和数据报告的自由软件。

free@home 系统访问点固件更新3.0用户界面更改说明书

System Access Point Firmware Update 3.0 User Interface ChangesThe Login ScreenThe Login screen offers to choose between the Configuration Mode or the Home owner Mode.In addition the two links in the lower right corner offer a link to the free@home Next App in the according App store.3.1.2.The Main menu is now aligned vertically. It gains the Menu Items:1.free@home configurationThis Menu is meant to be the central starting point for every installation. It offers thepossibility to add wireless devices, check the availability of all devices on the bus, Firmware updates, etc.2.Notification CenterCentral place to check all messages from the system.erOffers options to login/logout of the system, change to a different installation, to start the product assistant, or to change to the Homeowner View mode1.2. 3.4.This Menu merges the options that have been previously available in the settings Menu and combines the with the following new options:1.Menu selector to switch between:a.ABB/ Busch-Jaeger eco-systemAll System settings or other ABB/ Busch-Jaeger systems that are integrated tofree@homeb.Third partyShows all third party Systems that are integrated to free@home (e.g. Sonos,Philips Hue, etc.)c.AddonsShows all installed Addons and allows to install new Addons from a local file.d.Addon storeAllows to browse through all Addons that are provided by ABB/Busch-Jaeger(empty at launch, but will gain content over time).2.free@home Bus DevicesThis Menu offers an overview of all free@home devices that are connected via thefree@home Bus, along with additional information (e.g. operation time, Bus voltage,etc.) The level of detail can be adjusted by the “configure columns” button.3.free@home Wireless DevicesThis Menu offers to start the search for new wireless devices, as well as an overview of all free@home devices that are connected via the free@home Wireless protocol, along with additional information (e.g. operation time, Bus voltage, etc.) The level of detail can be adjusted by the “configure columns” butt on.er administrationThe different authorizations can be adjusted now for each single user separately, instead of having to choose for one profile.House StructureNew levels can now be creates with the “+” icon. The sequence of floors (which is alsothe sequence as shown in the App) can be adjusted by dragging and dropping each floorwith the Icon.Devices Scenes and GroupsFloorplan/ Function ViewAll Integration steps can be either performed in the Floorplan View or the Functions View(which is similar to what is available in the Home Owner View on the Smartphone App).The following applies for what is new in the Floorplan View:1.Basic NavigationThe Floorplan now displays all floorplans of all floors on one flat sheet. The view canbe zoomed in to display one floor or one room by just clicking on it.2.Adding DevicesNew devices can by added by clicking on the “+” Icon. The devices can then bedragged and dropped on to the floor plan.3.Creating and adjusting ScenesWhen Scenes are connected to devices, the option needs to be saved first, before it is possible to adjust the levels of each device in the scene. In addition, each device ina scene now has a slider “Live-Mod e”, which can be activated or deactivated (it isdeactivated by default).An activated Live-Moe will result in the immediate change of the device status, in the scene, but also at the device!This behavior can be unwanted in some situation (e.g. when progr amming an “All-Off” scene). To circumvent that, the Live-Mode can be kept switched off, which will result that the scene can be created without changing the status of the real device.。

蜂鸟派HAT用户手册说明书

GSM/GPRS/GNSS HATUser ManualOVERVIEWThis is a handy, low power Raspberry Pi HAT which features multi communication functionalities: GSM, GPRS, GNSS and Bluetooth.It allows your Pi to easily make a telephone call, send messages, connect to wireless Internet, global position, transfer data via Bluetooth, and so on.FEATURESGENERAL•Raspberry Pi connectivity, compatible with Raspberry Pi 2B/3B/3B+/Zero/Zero W •Supports SMS, phone call, GPRS, DTMF, HTTP, FTP, MMS, email, etc.•Support GPS, COMPASS, Glonass, LBS base station positioning, omni-positioning •Bluetooth 3.0, supports data transferring through Bluetooth•Onboard USB TO UART converter CP2102 for UART debugging•6x LEDs for indicating the module working status•SIM card slot for 1.8V/3V SIM card•RTC with backup battery holder•Baudrate auto detection (1200bps ~115200bps)•Control via AT commands (3GPP TS 27.007, 27.005, and SIMCOM enhanced AT Commands)•Supports SIM application toolkit: GSM 11.14 Release 99•Comes with development resources and manual (examples for Raspberry Pi/Arduino/STM32)GSM/GPRS•Bando GSM 850/EGSM 900/DCS 1800/PCS 1900 MHzo Quad-band auto searcho Compliant to GSM phase 2/2+•Emitting powero Class 4 (2W @ GSM 850/EGSM 900 MHz)o Class 1 (1W @ DCS 1800/PCS 1900 MHz)•GPRS connectivityo GPRS multi-slot class 12 (default)o GPRS multi-slot class 1~12 (configurable)•GPRS data featureo Downlink speed: max 85.6kbpso Uplink speed: max 85.6kbpso Coding schemes: CS-1\CS-2\CS-3\CS-4o Supports PAP (Password Authentication Protocol) for PPP connection o Supports PBCCHo Supports USSD•SMSo Supports: MT/MO/CB/Text/PDU modeo SMS storage: SIM card•Audioo Voice encode/decode mode: Half Rate\Full Rate\Enhanced Full Rate\Adaptive muti rateo Supports echo cancellationo Supports noise reductionGNSS•Receiver typeo33 tracking channelso99 acquisition channelso GPS L1 C/A code•Sensitivityo Tracking: -165 dBmo Cold starts : -148 dBm•Time-To-First-Fixo Cold starts : 28s (typ.)o Hot starts : < 1so Warm starts: 26s•Accuracyo Horizontal position : <2.5m CEPBLUETOOTH1.Integrates AT commandspliant to Bluetooth specification3.0 + EDR3.Supports SPP, OPP, HFP/HSP, etc.MISC•Operating voltage: 5V•Operating temperature: -40°C ~ 85°C •Storage temperature: -45°C ~ 90°C •Dimensions: 30.2mm x 65mmW HAT’S ON BOARD1.SIM868 module2.ZMM5V1: regulator diode3.SMF05C: TVS diode4.CP2102: USB TO UART converter5.MP1482: power chip6.NDC7002N: voltage level translator7.GPS status indicator indicator:•flashes fast when the module starts up•flashes slowly after GSM register succeed9.STA module working status indicator10.SIM868 UART Tx/Rx indicator11.Power indicator12.SIM868 control button: press the button and hold for 1s, to startup/shutdownthe SIM86813.Raspberry Pi GPIO connector14.SIM card slotB TO UART interface16.3.5mm earphone/mic jack17.GNSS antenna connector18.Bluetooth antenna connector19.GSM antenna connector20.CR1220 battery holder: for RTC backup battery21.UART selection switch•A: control the SIM868 through USB TO UART•B: control the SIM868 through Raspberry Pi•C: access Raspberry Pi through USB TO UARTOverview (1)Features (1)General (1)GSM/GPRS (2)GNSS (3)Bluetooth (4)Misc (4)Wha t’s on Board (5)Test on PC (9)Hardware configuration (9)GSM Testing (11)Common AT Commands (11)Take calls (13)Answer calls (14)SMS (14)Receive SMS (15)GNSS Testing (16)Common AT commands (16)Configuration (17)GPRS Testing (19)Common AT Commands (19)Setting local virtual server (20)Searching WAN IP (20)Testing (21)Sending data (22)Receiving Data (22)Deactivate Connection (23)Bluetooth Testing (24)Common AT Commands (24)Setting (25)Connecting (26)Demo code (Raspberry Pi) (29)Hardware Configuration (29)UART Setting (Raspberry Pi) (30)Testing with minicom (31)Demo codes (31)HARDWARE CONFIGURATIONThis module comes with a power adapter, micro USB cable, GSM antenna, GPSantenna and Bluetooth antenna. Besides these you should prepare two more things: ⚫A SIM card, the card should be usable and GPRS access (for testing the GPRS) ⚫ An earphone with a microphone on it (For testing Call function)1. Insert the SIM card to the card slot, plug the earphone and connect the GSMantenna2.Install CP2102 driver, plug the jumper B, and connect the USB to UART interfaceof GSM/GPRS/GNSS HAT to PC with a micro USB cable. Then the PWR indicator will keep bright.3.Open Device Manager to get the corresponding COM port number of CP2102. Forexample, it is COM7 as below. Users need to choose the correct port according to the Manager.4.Press the PWRKEY button and hold for 1s, the NET indicator will blink as below.Generally, the NET indicator will fast flash firstly (1 time per second), which means that the module has not logged in the Network. After logging in, the indicator become to flash slowly (1 time every three seconds). Up to the local GSM network, this process that logging in will last several seconds to dozens of seconds.If you take too much time to log in and failed, please check that whether the GSM antenna is connected correctly, and whether the SIM card is usable and inserted correctly.GSM TESTINGCOMMON AT COMMANDSFor more details of AT commands, please refer to：SIM800 Series_AT Command Manual_V1.09TAKE CALLS1.Insert the SIM card, connect the GSM antenna and TLL serial wires correctly. Thenpower on the board;2.Check whether the indicators blink correctly (PWR and STA keep bright, NETflashes every three seconds).3.Send “AT+CP IN?” and Enter to query the status of SIM card. Getting “+CPIN:READY” if the SIM card is ready4.Call number: for example, “ATD10086;” (10086 is the number of China MobileCommunications Corporation)5.Send “ATH” and Enter to hang up the call, as below:ANSWER CALLS1.Enable CLIP notification: AT+CLIP=1 then Enter2.Answering: ATA and Enter;3.Hang up: ATH then EnterSMS1.Set the local SMSC：AT+CSCA="+86138****5500"thenEnter,getresponse“OK”. No te: The SMSC will be different on different area. Here, it is Shenzhen China as examples.2.AT+CMGF=1: Set SMS to TEXT mode；3.AT+CMGS="xxxxxxxxxxx” then Enter, set the number of receiver, then you will getresponse: >, edit the content of message (needn’t Ent er at the end). After editing,send 1A in HEX format to send the message (0x1A is key value of “CTRL+Z”, it will tell the module to send). If the message is send successfully, module will get the reply +CNGS: 174 as below figures.RECEIVE SMS1. Send a mess age “this is a receive test” to the GSM/GPRS/GSNN HAT from yourphone2. While receiving messages, module will report it to UART: “SM”, 3, it means thatthere are 3 messages in SM, and the message we receive just now is the thirdmessage.3. Reading messages ：AT+CMGR=3 to read the third message (AT+CMGL="ALL" toread all messages)4. Deleting message ：AT+CMGD=3, to delete the message as belowGNSS TESTING COMMON AT COMMANDSFor more details of AT commands, please refer to：SIM868 Series GNSS Application Note V1.00CONFIGURATION1.Connecting the GPS antenna, and place the receiver on open area to receive GPSsignal2.Turn on power of GNSS: AT+CGNSPWR=13.Check the baud rate: AT+CGNSIPR?4.Start to sending data received to UART: AT+CGNSTST=1:5.Close the Com Assistant software SSCOM. Open u-center and set the Port andBaudrate. The Port is the port number recognized by PC. Set Baudrate as the value we got before (You can configure in Receiver option or click icons on tool bar directly):6.Choose Player>, then the GNSS information will be printed as below:GPRS TESTINGCOMMON AT COMMANDSFor more details of AT commands, please refer to：SIM800 Series_AT Command Manual_V1.09SETTING LOCAL VIRTUAL SERVERVirtual server defines the mapping between service ports of WAN and web servers of LAN. All requests from Internet to service ports of WAN will be redirected to the computer (web servers of LAN) specified by the server IP. (Please refer to guide manual of your router)1.Log in Management Console of your router with browser (read your router’sguide manual for specific address)2.Set Port：5000 (The Port can’t be conflict to others. Here we set it to 5000)3.Set LAN IP address for your computer (you can run CMD on your computer, andexecute command ipconfig to enquiry the address of IPv4), 192.168.1.14 asexamplesSEARCHING WAN IPY ou can search “IP” on browser to get WAN IP address of your PC as below: （This method is only workable in China）TESTING1.AT+CSQ to enquiry the quality of signal. The first parameter of response is signalquality (Max is 31). The signal stronger, the value bigger.2.AT+CREG? Check Network registration. If the second parameter of response is 1 or5, it means that Network has been registered successfully3.AT+CGATT? Check the state of GPRS attachment4.AT+CSTT="CMNET" Set the Network according to actual situation. Here we useCMNET5.AT+CIICR Bring up wireless connection with GPRS6.AT+CIFSR Get the local IP address7.AT+CIPSTART="TCP","113.81.232.4",5000 Establish TCP/IP connectionSENDING DATA1.AT+CIPSEND, module is going to send data to server2.After getting the response >, edit the contents of message (has been converted)without Enter at the end. Then send 1A in HEX format as below3.If the data sent successfully, the server will receive the data.RECEIVING DATA1.Choose the IP address of module on Peers input box2.Input the data which you want to send：”hello, i am server, please receive mymessage”3.Click Send button, you can see that module receive the dataDEACTIVATE CONNECTIONSend AT+CIPCLOSE or AT+CIPSHUT to deactivate connection.BLUETOOTH TESTING COMMON AT COMMANDSSETTING1.Connecting the Bluetooth antenna to the GSM/GPRS/GNSS HAT. Open theBluetooth service of your phone and set it visible to all nearby Bluetooth.2.AT+BTPOWER=1, Turn on Bluetooth3.AT+BTHOST? Enquiry the name and MAC address of module, you can also useAT+BTHOST=<Name> Command to change the Bluetooth name ofGSM/GPRS/GNSS HAT4.AT+BTSCAN=1,10 To search available nearby devices. Search time is 10s. Duringsearching, module will print the information of available device to UART.For example, +BTSCAN: 0,2,"H60-L01",50:a7:2b:bb:a4:50,-47“0,2” is the ID of this device;“H60-L01” is name of device;“50:a7:2b:bb:a4:50” is MAC address of device;“-47” is the RSSI value.5.AT+BTPAIR=0,2 , Pair with available device, the second parameter here is the IDwe got at step 4 . If get the response Error, just use AT+BTUNPAIR to delete the pairing data and pair again.6.After sending the pair command successfully, you can see that your telephoneprompt the pair request. Then you need to click Pair to accept the request and send AT+BTPAIR on PC to confirm the pair behavior. With these, module pair with the telephone successfully. If you don’t send the AT command to confirm pairing,the telephone will prompt information that fail to pair after a while. In this case, you need to send the pair command again. You can also use the telephone to send the pairing request, then input AT+BTPAIR=1,1 to confirm it.CONNECTINGTo test Bluetooth of GSM/GPRS/GNSS, you should use the Bluetooth APP.Scanning the QR code below to download the APP, then you can use its Serial function to test. (The APP is just used for simply test)1.Open the APP, click SCAN button on the upper right to scan the available devices.Then choose “SIM868” (“SIM868” is default Bluetooth name ofGSM/GPRS/GNSS HAT) and click UART. Then you will get the information that+BTCONNECTING on the COM assistant, which means there are connectingrequest. If you don’t reply it for a while, the APP will prompt that connectingfailed. And failed information “+BTDISCONN” will be printed on PC2.Connecting again, send command AT+BTACPT=1 to confirm and accept Bluetoothconnection. You can see that +BRCONNECT is printed on PC shows that succeed in SPP connecting. Then you can send data to the module with the APP.3.While receiving the data send from the telephone, the data will be printed with IDof device, the length of string and the content on PC.4.Send AT+BTSPPSEND command to transmit data. After getting the response >,input the content without Enter at the end. Send 1A in HEX begin to transmit the data. Then you can see that the data are received by your phone.HARDWARE CONFIGURATIONTo communicate with Raspberry Pi, you can use USB interface or UART interface.1.Inserting GSM/GPRS/GNSS HAT to Raspberry Pi2.Jumpers Setting:- If you want to use USB interface, connect to USB port of Pi with micro USB cable and set the jumpers to A- If you want to use UART interface, just need to set the jumper to B as below3.Power on your Raspberry Pi and the SIM module:-Manually power on SIM module: Press the PWRKEY button for about 3s-Software power on SIM module: Writing script to pull-down P4 (BCM2835number) for about 3s. (You can use this code as reference)UART SETTING (RASPBERRY PI)To use UART interface of Raspberry Pi, you should first enable the hardware serial of Raspberry Pi:sudo raspi-configChoose Interfaces Options ->Serial ->no->yes. To close serial debug and enable the hardware serial.Restart your Raspberry PiTESTING WITH MINICOM1.Install minicom to your Raspberry Pisudo apt-get install minicom2.Open minicom for testingminicom -D /dev/ttyS0ttyS0 is the serial port of Pi 3B/3B+, ttyAMA0 of Pi 2B/Zero. If you use USBinterface, the port maybe ttyUSB*3.Here we test Bluetooth as exampleDEMO CODESWe provide some python code for testing1.Call_phone.py: edit this code, change the W_buf_phone to the one you want to calland save. Then run the code with command: sudo python call_phone.py2.Send_message.py: change the phone number and the message as well. Then runthe code with the command: sudo python send_message.py3.gps.py: Run this code to get gps information output with command: sudo pythongps.py。

SP++3.0 User Guide

SP++3.0 User Guide张明2011-02同心协力共创开源目录0 SP++导引 (1)0.1 SP++概述 (1)0.2 SP++安装 (CodeBlocks) (1)0.3 SP++安装 (VS2010) (4)0.4 SP++与Matlab混合编程 (8)1 向量类模板 (11)1.1 基本向量类 (11)1.2 常用数学函数的向量版本 (21)1.3 常用的辅助函数 (26)1.4 简单计时器 (36)2 矩阵类模板 (39)2.1 基本矩阵类 (39)2.2 常用数学函数的矩阵版本 (51)2.3 实矩阵与复矩阵的Cholesky分解 (55)2.4 实矩阵与复矩阵的LU分解 (62)2.5 实矩阵与复矩阵的QR分解 (66)2.6 实矩阵与复矩阵的SVD分解 (72)2.7 实矩阵与复矩阵的EVD分解 (78)2.8 矩阵的逆与广义逆 (83)3 线性方程组 (91)3.1 常规线性方程组 (91)3.2 超定与欠定线性方程组 (98)3.3 病态线性方程组 (104)4 非线性方程与方程组 (109)4.1 非线性方程求根 (109)4.2 非线性方程组求根 (110)4.3 Romberg数值积分 (112)5 插值与拟合 (115)5.1 Newton插值 (115)5.2 三次样条插值 (117)5.3 最小二乘拟合 (119)6 优化算法 (123)6.1 一维线搜索 (123)6.2 最速下降法 (123)6.3 共轭梯度法 (125)6.4 拟Newton法 (128)7 Fourier分析 (131)7.1 2的整次幂FFT算法 (131)7.2 任意长度FFT算法 (135)7.3 普通信号FFT使用方法 (142)7.4 FFTW的C++接口 (149)7.5 卷积与快速实现算法 (152)8 数字滤波器设计 (155)8.1 常用窗函数 (155)8.2 滤波器基类设计 (159)8.3 FIR数字滤波器设计 (159)8.4 IIR数字滤波器设计 (162)9 随机信号处理 (167)9.1 随机数生成器 (167)9.2 概率统计中的常用函数 (174)9.3 相关与快速实现算法 (176)10 功率谱估计 (183)10.1 经典谱估计方法 (183)10.2 参数化谱估计方法 (186)10.3 特征分析谱估计方法 (189)11 自适应滤波器 (195)11.1 Wiener滤波器 (195)11.2 Kalman滤波器 (197)11.3 LMS自适应滤波器 (201)11.4 RLS自适应滤波器 (204)12 时频分析 (213)12.1 加窗Fourier变换 (213)12.2 离散Gabor变换 (215)12.3 Wigner-Wille分布 (219)13 小波变换 (227)13.1 连续小波变换 (227)13.2 二进小波变换 (230)13.3 离散小波变换 (233)14 查找与排序 (237)14.1 二叉查找树 (237)14.2 平衡二叉树 (241)14.3 基本排序算法 (248)14.4 Huffman编码 (251)15 参考文献 (257)15.1 书籍 (257)15.2 文章 (258)15.3 网站 (258)16 有感于SP++ (259)16.1 心血来潮 (259)16.2 艰苦历程 (259)16.3 有得有失 (260)16.4 见仁见智 (261)II0SP++导引0.1SP++概述SP++ (Signal Processing in C++) 是一个关于信号处理与数值计算的开源C++程序库，该库提供了信号处理与数值计算中常用算法的C++实现。

Oracle GlassFish Server 3.0.1 监控与脚本客户端发布说明书

Oracle®GlassFish Server3.0.1Monitoring Scripting Client Release NotesPart No:821–1767–10June2010Copyright©2010,Oracle and/or its affiliates.All rights reserved.This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law,you may not use,copy,reproduce,translate,broadcast,modify,license, transmit,distribute,exhibit,perform,publish,or display any part,in any form,or by any means.Reverse engineering,disassembly,or decompilation of this software, unless required by law for interoperability,is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors,please report them to us in writing. If this is software or related software documentation that is delivered to the ernment or anyone licensing it on behalf of the ernment,the following notice is applicable:ERNMENT RIGHTS Programs,software,databases,and related documentation and technical data delivered to ernment customers are “commercial computer software”or“commercial technical data”pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such,the use,duplication,disclosure,modification,and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract,and,to the extent applicable by the terms of the Government contract,the additional rights set forth in FAR52.227-19,Commercial Computer Software License(December2007).Oracle America,Inc.,500Oracle Parkway,Redwood City,CA94065.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications,including applications which may create a risk of personal injury.If you use this software or hardware in dangerous applications,then you shall be responsible to take all appropriate fail-safe,backup,redundancy,and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle and Java are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.AMD,Opteron,the AMD logo,and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices.Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International,Inc.UNIX is a registered trademark licensed through X/Open Company,Ltd.This software or hardware and documentation may provide access to or information on content,products,and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content,products,and services.Oracle Corporation and its affiliates will not be responsible for any loss,costs,or damages incurred due to your access to or use of third-party content,products,or services.100616@24378Contents1Oracle GlassFish Server Monitoring Scripting Client3.0.1Release Notes (5)Revision History (5)About Monitoring Scripting Client (6)Requirements for Obtaining and Using Monitoring Scripting Client (6)Monitoring Scripting Client Documentation (6)Known Issues (6)Omission of DynamicImport-Package entry in manifest causes probes for the JavaMailservice not to fire(Issue11069) (7)Keep-alive probes for network listeners are not fired as expected(6886579) (7)Jersey probes are not fired(6908856) (7)Invalid script causes run-script to throw an exception(6906040) (7)How to Report Problems and Provide Feedback (8)Additional Resources (8)Third-Party Web Site References (8)Accessibility Features (9)341C H A P T E R1Oracle GlassFish Server Monitoring ScriptingClient3.0.1Release NotesOracle GlassFish Server3.0.1Monitoring Scripting Client Release Notes provide late-breakinginformation about the software and documentation for the Monitoring Scripting Client.Thedocument includes requirements for obtaining and using Monitoring Scripting Client.Descriptions and workarounds for known issues and limitations are also provided.Read this document before installing,setting up,and using Oracle GlassFish Server MonitoringScripting Client3.0.1.The following topics are addressed here:■“Revision History”on page5■“About Monitoring Scripting Client”on page6■“Requirements for Obtaining and Using Monitoring Scripting Client”on page6■“Monitoring Scripting Client Documentation”on page6■“Known Issues”on page6■“How to Report Problems and Provide Feedback”on page8■“Additional Resources”on page8■“Third-Party Web Site References”on page8■“Accessibility Features”on page9Revision HistoryThis section provides a record of changes in these Release Notes.TABLE1–1Revision HistoryDate Description of ChangesDecember2009Initial release.5About Monitoring Scripting ClientAbout Monitoring Scripting ClientMonitoring Scripting Client provides support for clients that are written in the JavaScriptprogramming language to provide monitoring data about Oracle GlassFish Server.Requirements for Obtaining and Using Monitoring Scripting ClientMonitoring Scripting Client is integrated with Oracle GlassFish Server and is installed whenOracle GlassFish Server is installed.If you are using GlassFish Server Open Source Edition,you can obtain this feature separately bypurchasing a right-to-use.Monitoring Scripting Client is available to customers who havepurchased a right to use either as a patch from the SunSolve program site or as an add-oncomponent from Update Tool.For information about how to download Monitoring Scripting Client,see“Downloading andInstalling Monitoring Scripting Client”in Oracle GlassFish Server3.0.1Monitoring ScriptingClient Installation and Quick Start Guide.Before downloading Monitoring Scripting Client,ensure that you have your account username and password.Monitoring Scripting Client3.0.1requires Oracle GlassFish Server3.0.1.The remaining hardware and software requirements for Monitoring Scripting Client areidentical to the requirements for using Oracle GlassFish Server3.0.1.For more information,see“Hardware and Software Requirements”in Oracle GlassFish Server3.0.1Release Notes.Monitoring Scripting Client DocumentationFor information about installation and basic use of Monitoring Scripting Client,see OracleGlassFish Server3.0.1Monitoring Scripting Client Installation and Quick Start Guide.For information about GlassFish Server,see the Oracle GlassFish Server3.0.1documentation(/coll/1343.13).Known IssuesThis section lists the following known issues with Monitoring Scripting Client:■“Omission of DynamicImport-Package entry in manifest causes probes for the JavaMail service not to fire(Issue11069)”on page7■“Keep-alive probes for network listeners are not fired as expected(6886579)”on page7■“Jersey probes are not fired(6908856)”on page7■“Invalid script causes run-script to throw an exception(6906040)”on page76Oracle GlassFish Server3.0.1Monitoring Scripting Client Release Notes•June2010Known Issues Omission of DynamicImport-Package entry in manifest causes probes for the JavaMail service not to fire(Issue11069)DescriptionThe DynamicImport-Package:org.glassfish.flashlight.provider entry is omitted from the manifest for the mail.jar file.As a result,the probes for the JavaMail service are not fired. For details,see GlassFish project Issue11069(https:///issues/ show_bug.cgi?id=11069).WorkaroundNone.Keep-alive probes for network listeners are not fired as expected(6886579)DescriptionWhen an HTTP request with the connection header Connection:keep-alive is sent to a network listener for whose HTTP protocol Comet support is enabled,keep-alive probes are not fired.WorkaroundNone.Jersey probes are not fired(6908856)DescriptionThe following Jersey probes are not fired:■glassfish:jersey:server:requestStart■glassfish:jersey:server:requestEnd■glassfish:jersey:server:ruleAcceptWorkaroundNone.Invalid script causes run-script to throw an exception(6906040)DescriptionWhen run-script is run with an invalid script,an exception is thrown.Ideally,run-script should display a suitable error message and not throw an exception stack trace.Chapter1•Oracle GlassFish Server Monitoring Scripting Client3.0.1Release Notes7How to Report Problems and Provide FeedbackWorkaroundExamine the stack trace for information that might help identify errors in the script.How to Report Problems and Provide FeedbackIf you have problems with Oracle GlassFish Server Monitoring Scripting Client3.0.1,providefeedback through one of the following mechanisms:■Feedback Submittal form(/contact/products/index.jsp)—A form for submitting feedback on the GlassFish Server product■Java Technology Forums(/)—An interactive message board for sharing knowledge and questions about Java technologies and programming techniques;use the Java EE SDK forum for discussions related to the Oracle GlassFish Server3.0.1product■Oracle Support services(/us/support/index.htm)—Links to the Knowledge Base,Online Support Center,and Product Tracker,as well as to maintenanceprograms and support contact numbersSo that we can best assist you in resolving problems,please have the following informationavailable when you contact support:■The telephone dispatch number associated with your maintenance contract■A description of the problem,including the situation where the problem occurs and itsimpact on your operation■Machine type,operating system version,and product version,including any patches and other software that might be affecting the problem■Detailed steps on the methods you have used to reproduce the problem■Any error logs or core dumpsAdditional ResourcesUseful information can be found at the following locations:■GlassFish Community(https:///)■Oracle Developer Information(/)■Oracle GlassFish Server product page(/goto/glassfish)■Sun Developer Support Services(/services/index.jsp)■Oracle product documentation(/)Third-Party Web Site ReferencesThird-party URLs are referenced in this document and provide additional,related information. 8Oracle GlassFish Server3.0.1Monitoring Scripting Client Release Notes•June2010Accessibility Features Note–Oracle is not responsible for the availability of third-party Web sites mentioned in thisdocument.Oracle does not endorse and is not responsible or liable for any content,advertising,products,or other materials that are available on or through such sites or resources.Oracle willnot be responsible or liable for any actual or alleged damage or loss caused by or in connectionwith the use of or reliance on any such content,goods,or services that are available on orthrough such sites or resources.Accessibility FeaturesOur goal is to make Oracle products,services,and supporting documentation accessible to allusers,including users that are disabled.To that end,our documentation includes features thatmake information available to users of assistive technology.This documentation is available inHTML format,and contains markup to facilitate access by the disabled community.Accessibility standards will continue to evolve over time,and Oracle is actively engaged withother market-leading technology vendors to address technical obstacles so that ourdocumentation can be accessible to all of our customers.For more information,visit the OracleAccessibility Program Web site at /accessibility/index.html.Chapter1•Oracle GlassFish Server Monitoring Scripting Client3.0.1Release Notes910。

TRACE32测试软件及操作说明书

T raining Simulator and Demo SoftwareRelease 09.2023TRACE32 Online HelpTRACE32 DirectoryTRACE32 IndexTRACE32 Training ............................................................................................................................Training Simulator and Demo Software (1)About the Demo (3)Starting the TRACE32 Simulator (3)User Interface - TRACE32 PowerView (4)TRACE32 Command Line and Softkeys6 Window Captions - What Makes Them Special in TRACE327Debugging the Program (8)Basic Debug Commands8 Debug Modes9 Displaying the Stack Frame11Breakpoints (12)Setting Breakpoints12 Listing all Breakpoints13 Setting Read/Write Breakpoints14Variables (15)Displaying Variables15 Displaying Variables of the Current Program Context16 Using the Symbol Browser16 Formatting Variables17 Modifying Variables18Memory (19)Displaying Memory19 Modifying Memory20Version 10-Oct-2023About the DemoWhat is this? This is a guided tour through TRACE32 - a tutorial. We use a simple program example in C to illustrate the most important debug features, and give lots of helpful tips & tricks for everyday use.How long does this tutorial take? 0.5 to 1 hrs.How can I learn most from this tutorial? Work completely through all chapters in sequence and then do the quiz at the end.Where can I download the TRACE32 Simulator for the hands-on debug session? From:https:///download.html . You do not need any hardware for this tutorial.Starting the TRACE32 Simulator1.Unzip the downloaded file. Y ou do not need to install the TRACE32 Simulator.2.Double-click the t32m <architecture>.exe file (e.g. t32m arm .exe ) to start the demo debug session. When the TRACE32 Instruction Set Simulator starts, a start-up PRACTICE script that sets up a debug session is automatically executed.Y ou can manually execute the same start-up PRACTICE script by choosing File menu > Run Script .PRACTICE, the Lauterbach script language, is used for automating tests, configuring the TRACE32 PowerView GUI and your debug environment.For our demo debug session, the PRACTICE start-up script armc.cmm loads the application program armle.axf and generates a TRACE32 internal symbol database out of the loaded information.By default, TRACE32 executes the autostart.cmm script on start-up.User Interface - TRACE32 PowerViewThe graphical user interface (GUI) of TRACE32 is called TRACE32 PowerView.The following screen shot presents the main components of the user interface.We’ll briefly explain the GUI using the List command and List window as an example.A video tutorial about the TRACE32 PowerView GUI is available here:/kb/articles/introduction-to-trace32-gui Do one of the following to open the List window:•Choose View menu > List Source•or, at the TRACE32 command line, type: List (or L )Main Menu Bar Main Tool BarC o n t e x t M e n uLocal ButtonsMessage Line SoftkeyLine State LineWindow AreaCommand LineThe List window displays the code in assembler mnemonic and HLL (HLL stands for High-Level Language and means the programming language of your source code).In the List window, the gray bar indicates the position of the program counter (PC). Right now, it is located on the symbolic address of the label main .A video tutorial about the source code display in TRACE32 is available here:/kb/articles/displaying-the-source-codeT o summarize it, you can execute commands in TRACE32 PowerView via the usual suspects:1.Menus on the menu bar2.Buttons on the main toolbar and the buttons on the toolbars of TRACE32 windows3.Context menus in TRACE32 windowsAdditionally in TRACE32, you can execute commands via the TRACE32 command line.Opens the List windowProgram counter (PC)TRACE32 Command Line and SoftkeysTRACE32 commands are not case sensitive: register.view is the same as Register.view UPPER CASE letters indicate the short forms of commands and must not be omitted. All lower case letters can be omitted. This makes short forms an efficient time saver when you are entering frequently-used commands in the command line. Examples:•Instead of the long form Register.view type just the short form r or R •Instead of the long form List type just the short form l or LThe softkeys are below the command line. The camel casing (i.e. upper and lower case letters) on any softkey tells you the long form of a command. The softkeys guide you through the command input, displaying all possible commands and parameters.Example - To assemble the Data.dump command using the softkeys:1.Click Data .2.Click dump .3.Type the <range> or <address> you want to dump. For example, 0x1000--0x20004.Click [ok] to execute the command. The Data.dumpwindow opens.SoftkeysCommand lineWindow Captions - What Makes Them Special in TRACE32The command with which you open a window will be shown as the window caption. The parameters and options are also included in the window caption.You can re-insert a command from a window caption (a) into the command line (b) in order to modify the command. Let’s do this with the Register window.1.Choose View menu > Register . 2.Right-click the window caption (a).3.Modify the command, e.g. by adding the /SpotLight option: It will highlight changed registers.4.Click [ok] to execute the modified command.5.Click Single Step on the TRACE32 toolbar. Changed registers are highlighted immediately.(a)(b)Debugging the ProgramBasic Debug CommandsThe basic debug commands are available via the Run menu, the toolbar of the List window, the main toolbar, and via the TRACE32 command line.Single steppingis one of the basic debug commands.TRACE32 provides also more complex debug control commands. Y ou can step until an expression changes or becomes true.Example: Var.Step.Till i>11. single-steps the program until the variable i becomes greater than 11. Please note that TRACE32 uses a dot to denote decimal numbers.Step over function calls or subroutinesGo to the next code line written in the program listing Go Return / Go to the last instruction of the current functionUseful e.g. to leave loopsSingle StepStop the program executionGo / Start program executionGo Up / return to the caller functionStep till next unreached lineDebug ModesT ake a look at the state line at the bottom of the TRACE32 main window:6.On the toolbar of the Listwindow, clickMode to toggle the debug mode to HLL .The state line tells you:A The (symbolic) address of the current cursor position.The program counter (PC) is highlighted in gray.B The state of the debugger: stopped means program execution is stopped. Y ou can now, for example, inspect or change memory.C The state line displays the currently selected debug mode: The code display will beHLL (High Level Language) or ASM (assembler) or a MIX ed mode with HLL and its corre-sponding assembler mnemonic.AB CDebug mode HLLDebug mode MIXStep.7.ClickThe step you are taking is debug mode HLL goes to the next source code line.8.ClickMode again to toggle the debug mode to MIX.Step.9.ClickThis time, the step executes one assembler line.10.Right-click a code line, and then select Go Till.The program execution starts. It stops when the program reaches the selected code line.Displaying the Stack FrameFor the following example, let’s assume we have the following call hierarchy: main() calls func2() and func2() calls func1():Choose Show Stack in the Var menu. The Frame.view window displays the call hierarchy.•The /Locals option shows the local variables of each function.•The /Caller option shows a few source code lines to indicate where the function was called.This screenshot corresponds to the calling hierarchy shown above.BreakpointsVideo tutorials about breakpoints in TRACE32 are available here:/kb/articles/using-breakpoints-in-trace32Setting BreakpointsLet’s set a breakpoint to the instruction prime = i + i + 3 and the instruction k += prime1.Double-click a code line to set a program breakpoint.2.Make sure to click the white space in the code line, and not the code literal.All code lines with a program breakpoint are marked with a red vertical bar.T o set a breakpoint to an instruction that is not in the focus of the current source listing1.Choose Var menu > Show Function.The sYmbol.Browse.Function window opens.2.Select the function you are interested in e.g. sieve.The List window opens, displaying this function. This window is now fixed to the start address ofthe function sieve and does not move with the program counter cursor.Listing all Breakpoints1.Choose Break menu > List to list all breakpoints.The Break.List window opens, providing an overview of the set breakpoints.2.On the toolbar, clickGoto start the program execution. 3.When the program execution stops at a breakpoint, it is highlighted in the Break.List window.A Address of the breakpoint.B Breakpoint type.C Breakpoint method: SOFTware, ONCHIP or DISABLED.D Symbolic address of the breakpoint. Example:•sieve\11 means source code line 11 in function sieve .AB C DSetting Read/Write BreakpointsY ou can set a breakpoint that stops the program execution at a read or write access to a memory location(e.g. global variable). T o set a breakpoint on the array flags for instance, do a right mouse click on thearray name in the List window then select Breakpoints > Write.VariablesVideo tutorials about variable display in TRACE32 are available here:/kb/articles/variable-logging-and-monitoring-in-trace32Displaying VariablesLet’s display the variables flags, def, and ast.1.Choose Var menu > Watch...The Var.AddWatch window opens, displaying the variables known to the symbol database.2.Double-click the variable flags.The Var.Watch window opens, displaying the selected variable.steps:3. Alternative-In the Var.Watch window, click Watch, and then double-click the variables def and ast to add them to the Var.Watch window.-From a List window, drag and drop any variable you want into the Var.Watch window.-In a List window, right-click any variable, and then select Add to Watch window from the context menu.-If you want to display a more complex structure or an array in a separate window, choose Var menu >View.Displaying Variables of the Current Program Context1.Set the program counter (PC) to sieve() by typing at the TRACE32 command line:2.Choose Var menu > Show Current Vars .The Var.REF window opens, displaying all variables accessed by the current program context.3.Click Step on the TRACE32 toolbar to execute a few single steps. TheVar.REFwindow is updated automatically.Using the Symbol BrowserThe symbol browser provides an overview of the variables, functions, and modules currently stored in the symbol database.1.ChooseVar menu > Watch...The Var.AddWatch window lets you browse through the contents of the symbol database. Global variables are displayed in black and functions in gray. By double-clicking a function, its local variables are displayed.2.In the Var.AddWatch window, double-click func2.Register.Set PC sieve ;The command short form is: r.s pc sieveTo format the display of variables - global settings:1.Choose Var menu > Format.2.In the SETUP.Var window, make your settings. Decimal and Hex are useful global settings.TRACE32 applies your settings to all Var.view windows that you open afterwards.To format the display of an individual variable:1.At the command line, type: Var.view ast (The variable ast is included in this demo.)2.In the Var.view window, right-click ast, and then click Format.The Change Variable Format dialog opens.3.Select the Type check box to display the variable ast with the complete type information.4.Click Apply. The format of ast in the Var.view window is updated immediately.5.For more complex variable select TREE in the Change Variable Format dialog box.Click + and - to expandand collapse the tree.1.Double-click the variable value to modify the value. The Var.set command will be displayed in thecommand line. The short form of the command is V or v2.Enter the new value directly after the equal sign and confirm with [ok].MemoryDisplaying Memory1.To display a memory dump in a Data.dump window, do one of the following:-Choose View menu > Dump,-or click Memory Dump on the toolbar,-or, at the TRACE32 command line, type: Data.dumpY ou can also specify an address or symbol directly, e.g.: Data.dump flags2.In the Data.dump dialog, enter the data item, e.g. flags-Alternatively click to browse through the symbol database.3.In the Browse Symbols window, double-click the symbol flags to select it, and then click OK.Double-click flags.In the following screenshot, theData.dump window is called via the TRACE32 command line.There are different ways to define an address range:•<start_address>--<end_address> (SD is an access class)•<start_address>++<offset>Modifying Memory1.In a Data.dumpwindow, double-click the value you want to modify.A Data.Set command for the selected address is displayed in the command line. The short form of the command isD.S or d.s2.Enter the new value directly after %LE , and then confirm with [ok].(%LE stands for Little Endian).Data.dump SD:0x5530--SD:0x554FData.dump cstr1++0x1f /Byte ;start at cstr1 plus the next 0x1f bytesAccess Class + AddressHEX ASCIITraining Simulator and Demo Software | 21©1989-2023 L auterbach。

TestMaster3.0使用说明书

目录1.前言 (1)2.简介 (2)2.1.系统需求 (2)2.2.软件简介 (2)2.2.1.功能强大 (2)2.2.2.扩展方便 (3)3.软件安装与卸载 (4)3.1.安装 (4)3.2.卸载 (6)4.软件主界面 (7)4.1.启动 (7)4.1.1.开机顺序 (7)4.1.2.登录 (7)4.1.3.联机设置 (8)4.1.4.联机后下发控制器参数 (9)4.2.主界面 (10)4.2.1.工具栏 (10)4.2.2.试验选择界面 (11)4.2.3.状态栏 (11)4.2.4.界面布局管理 (12)4.2.5.关于 (13)5.控制面板 (15)5.1.控制面板【电拉】 (15)5.1.1.参数设置 (16)5.1.2.操作区 (17)5.2.控制面板【伺服】 (19)5.2.1.参数设置 (19)5.2.2.操作区 (21)6.校准与检定 (22)6.1.校准前准备 (22)6.2.选择校准对象与加载方式 (23)6.2.1.校准对象 (23)6.2.2.控制参数 (23)6.2.3.加载方式 (26)6.2.4.加载方式的选择 (27)6.3.输入待校准值及次数 (28)6.4.校准 (29)6.4.1.手动校准 (29)6.4.2.手动快慢速校准 (29)6.4.3.自动快慢速校准 (30)6.5.修正校准表 (30)6.6.参数备份 (32)7.试验 (33)7.1.试验简介 (33)7.2.试验流程 (34)7.2.1.选择试验 (34)7.2.2.新建试验 (34)7.2.3.试验前准备 (35)7.2.5.结束试验 (37)7.2.6.试验后整理 (39)7.2.7.继续运行同组的其他试件 (39)7.2.8.打印报告 (39)7.2.9.查询查看分析试验 (39)7.3.试验结果与报告 (40)7.3.1.工具栏 (40)7.3.2.试验数据分析 (41)7.3.3.曲线分析 (43)7.3.4.报表设置 (44)7.4.试验界面的说明与管理 (51)7.4.1.通用模板界面 (51)7.4.2.拉伸模板界面 (54)8.试验管理 (56)8.1.试验列表 (56)8.2.工具栏 (56)8.2.1.导出试验 (56)8.2.2.导入试验 (57)9.系统设置 (59)9.1.手自切换【伺服】 (59)9.2.位移切换【屛显】 (60)9.3.设备管理 (60)9.3.1.界面简介 (61)9.3.2.控制器 (62)9.3.3.通道 (63)9.3.4.传感器 (65)9.4.软件激活 (69)9.4.1.设置控制器编号 (69)10.结束语 (70)11.附录 (71)11.1.工具软件UTMTopTest (71)11.1.1.软件的打开 (71)11.1.2.控制器IP修改 (72)1.前言✧感谢您对本公司产品的信任！✧本使用说明书中加粗字体的地方，请您特别注意并仔细阅读。

User Guide

User GuideTable of ContentsWrite:OutLoud To Go Toolbar. . . . . . . . . . . . . . . 3One-Click Access to Common Tasks. . . . . . . . . . . . . . . . . 3Text Navigation and Selection Buttons. . . . . . . . . . . . . . . 3Speech Buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Tool Buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Text Buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Write:OutLoud To Go Menus. . . . . . . . . . . . . . . . 6File Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Edit Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Tools Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Text Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Options Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Speech Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Keyboard Shortcuts. . . . . . . . . . . . . . . . . . . . . . . 14Write:OutLoud®To Go TrademarksThe Don Johnston logo and Write:OutLoud are registered trademarks and TheLeader in Learning Intervention Resources is a trademark of Don JohnstonIncorporated.Dana is trademark and AlphaSmart is a registered trademark ofAlphaSmart, Inc.Macintosh is a registered trademark of Apple Computer, Inc.Windows is a registered trademark of Microsoft Corporation.Adobe and Reader are either registered trademarks or trademarks of AdobeSystems Incorporated in the United States and/or other countries.Graffiti is a registered trademark of Palm, Inc.All other product or corporate names are trademarks or registered trademarks oftheir respective companies and are used for explanation only and to the owner'sbenefit, without intent to infringe.Write:OutLoud To Go © Copyright 2004, Don Johnston Incorporated.All rights reserved.User Guide Write:OutLoud to Go © Copyright 2004Don Johnston Incorporated. All rights reserved.The Spelling portion of this product is based on Proximity Linguistic Technology.®THE PROXIMITY/FRANKLIN DATABASE © 1994, Franklin Electronic Publishers,Inc. All rights reserved, Proximity Technology Inc. Geographical Supplement© Copyright 1990/1994 Merriam-Webster® Inc./Franklin ElectronicPublishers, Inc. © Copyright 1994. All rights reserved, Proximity Technology Inc.THE PROXIMITY/FRANKLIN DATABASE © Copyright 1997, Franklin ElectronicPublishers, Inc. © Copyright 1998. All rights reserved, Proximity Technology Inc.Write:OutLoud To Go contains PrintBoy by Bachmann software.Published by:Don Johnston Incorporated26799 West Commerce DriveVolo, IL 60073800.999.4660 (USA/CANADA)847.740.0749Technical SupportSupport@800.889.5242 (USA/CANADA)Printed in the United States of America, September 2004Write:OutLoud To Go ToolbarWrite:OutLoud To Go is a talking word processor filled with features thatincrease its ease of use. Many functions can be carried out by simply clicking the toolbar at the top of the Write:OutLoud To Go screen, making importantword processing features immediately available without using pull-down menus.Writers click buttons to navigate through text, check spelling and more.One-Click Access to Common TasksWhen you activate Write:OutLoud To Go, you're ready to type and createdocuments immediately. For ease of use, the buttons on the toolbar are grouped according to tasks.Text Navigation and Selection ButtonsTools for text navigation and selection help writers quickly and efficientlymove through and review their writing.These self-explanatory tools are designed for ease of use by students. There are many more keyboard shortcuts for text navigation and selection listed in Keyboard Shortcuts at the end of this User Guide.BeginningTap Beginning to move your cursor to the beginning of the document.Use this to reread the work.MoveTap Move to move your cursor to the next sentence. Use this to quickly navigate through a document for reading and revising the work.3Write:OutLoud ®To Go© Don Johnston Incorporated USER GUIDENavigation Speech Tools Text AppearanceMoves cursor to the beginningMoves cursor tothe next sentence Selects the next sentence Moves cursor to the end of document Note:A sentence must end with a period,question mark or exclamationpoint in order for Write:OutLoud To Go to recognize it as a sentence.Write:OutLoud®To Go SelectTap Selectto highlight the next sentence. Use this to quickly select “chunks”of text for reading aloud or revising sentence-by-sentence.EndTap End to move directly to the end of the document. Use this to quickly getto the end of a document to add to existing work.Speech ButtonsSpeech feedback gives writers immediate auditory reinforcement of what they havejust typed, the opportunity to self-correct based on what they hear and motivatingauditory support during the revision process.SpeakTap Speak to hear the highlighted text or the sentence containing the cursor.Tap again to hear the next sentence spoken. Use this to read through thedocument sentence-by-sentence for more effective revision.Write:OutLoud To Go speaks highlighted text or, if no text is highlighted, speaksthe sentence containing the cursor.Select again and the next sentence is spoken. With this feature, you can movethrough your entire document sentence-by-sentence, speaking each sentence as you go.To speak specific words or sentences, highlight the text first, then tap Speak.To speak the entire document, choose Select All in the Edit menu and tap Speak.RepeatTap Repeat to hear again what was just spoken. Use this to repeat what wasjust heard to facilitate accurate proofreading and effective revision.StopTap Stop to stop the current speech. Use this to immediately interruptspeech during revision.© Don Johnston Incorporated USER GUIDE4Note:If your cursor is in the middle of a sentence,Select highlightswords from the cursor to the end of the sentence.Speak sentenceor selectionRepeatStop speakingNote:Sentences are spoken until sentence-ending punctuation or new paragraphsare encountered.5Write:OutLoud ®To GoWrite:OutLoud To Go includes many more speech options that you can turn on and off to meet writers' needs. SeeWrite:OutLoud To Go Menus,for more information.Tool Buttons Print One Tap Print One to print one copy of the current document. Use thisto bypass choosing any print settings.Check SpellingOften, struggling writers write very little text because of poor spelling or vocabulary. The Check Spelling Tool feature in Write:OutLoud To Go helps writers with editing for mechanics.Tap Check Spelling from anywhere in the document to begin the Franklin Spell Checker. Write:OutLoud To Go always checks the entire document for spelling errors.Write:OutLoud To Go displays the Spelling dialog when it finds a word that is not in either the regular Franklin or User dictionaries.The spell checker displays the sentence containing the unknown ormisspelled word (highlighted) along with suggested known orcorrect words.To hear the word in question spoken in context, tap the first .To hear suggested words, tap the second to speak the new word. To select the word suggested in the “Change To” box, tap . To select a word other than the one suggested in the “Change To” box,tap one of the alternate suggested words to select it. Then, tap . To leave the word in question as it is and search for the next word in question, tap .© Don Johnston Incorporated USER GUIDETo hear words in question and suggested words spelled out letter-by-letter,check the box next to Read Word Spelling.When you are finished with the spell checker and want to return to the document, tap .All spelling changes are in the document.Text ButtonsWrite:OutLoud To Go's Text buttons encourage writers to change the way their document looks. These tools give writers control over font size.Grow & Shrink TextTap Grow or Shrink to change the font size. Each time you tap Grow or Shrink , the font for all the text changes to the next available font size.Continue tapping until you get the size you want.Write:OutLoud To Go MenusThe Write:OutLoud To Go Menu Bar appears.To view a drop-down menu, tap the desired menu heading.To make a selection from a drop-down menu, tap the action you desire.Write:OutLoud ®To Go© Don Johnston IncorporatedUSER GUIDE 6Grow text size Shrink text size7Write:OutLoud®To GoFile MenuNewCreates a new document. The new document uses the current default settings.OpenOpens an existing document. Write:OutLoud To Go displays an Open dialog box. Choose a file.CloseCloses the current document.SaveSaves changes to document and allows you to continue working. If thedocument is untitled, the Save As window displays so you can give it a name. Save As…Saves document with a new name and allows you to continue working. The original document remains intact.© Don Johnston Incorporated USER GUIDEWrite:OutLoud®To Go Delete FileOpens a Delete File dialog box.Select the document to be deleted. Alert message appears to verify that you want to delete the selected document.Beam FileAllows you to beam files between the Dana™by AlphaSmart ®and a desktop or laptop computer or between Danas. You cannot beam the application.Print OnePrints one copy of the document without prompting for settings.PrintOpens the Print Dialog box.© Don Johnston Incorporated USER GUIDE8Note:Delete File will only delete the selected document file.It will not delete other Dana files (i.e. F1,F2,etc.).Type a title for your document Choose print specifications from theprint window and send documentto the printer Add a header to your document(see Header Dialog Box)9Write:OutLoud®To Go Header Dialog BoxAvailable as an option from the Print Dialog box. Allows you toadd a name, date and any other class information required inyour document into the heading.ExitExits the program.Edit MenuUndoCancels your last action. This item is unavailable if your last actioncannot be undone.CutRemoves selection from document. Cut may be used with Paste.CopyDuplicates selection. Copy may be used with Paste.PastePlaces cut or copied selection in your document at the cursor.ClearRemoves selection from document. Not used with Paste.Select AllHighlights all text in the document.© Don Johnston Incorporated USER GUIDEFind…Locates a specific word or group of words in text. Write:OutLoud To Go displays the Find dialog box.Go to Start of DocMoves the cursor to the top of the first page of the document. Works exactly like in the toolbar.Go to Next SentenceMoves the cursor to the beginning of the next sentence.Works exactly like in the toolbar.Select SentenceHighlights the next sentence. Works exactly like in the toolbar. If the cursor is at the end of a sentence, it highlights the whole next sentence. If the cursor is in a sentence, it highlights from the insertion point to the end of the sentence.Go to End of DocMoves the cursor to the bottom of the last page of the document. Works exactly like in the toolbar.Tools MenuCheck SpellingSelect Check Spelling from anywhere in the document to begin the Franklin Spell Checker. Works exactly like in the toolbar. Write:OutLoud ®To Go © Don Johnston Incorporated USER GUIDE10Stops speech Displays the sentence containingthe “found” word with the “found”word highlighted Type in the word to be found Finds the next instance of the wordReads the sentence that contains the“found” wordReads the word(s) to be foundCloses the dialog box and allows the userto continue working in the documentWrite:OutLoud®To GoCue Misspelling…When toggled on, displays the number of spelling errors in the right, topcorner of the application window. If an error is corrected or deleted, thecounter reflects the change.Text MenuThe Text menu lets you make changes to the font and size of text inyour document.FontChoose the font, style and size of text for your document.Grow SelectionIncreases the size of all words in the document.Works exactly like in the toolbar.Shrink SelectionDecreases the size of all words in the document.Works exactly like in the toolbar.Note:Multiple fonts cannot be used with a document.Write:OutLoud®To Go Options MenuShow/Hide ToolbarShows or hides the toolbar at the top of the Write:OutLoud To Godocument.Speech MenuSet Speech On/OffToggles all speech options On and Off. When turned off, theand are not active in the toolbar.Tap Set Speech On to activate your speech settings again.SpeakSpeaks text. Works exactly like in the toolbar.RepeatRepeats last spoken text. Works exactly like in the toolbar.Stop SpeechImmediately stops the current speech.Works exactly like in the toolbar.Speak LettersWhen checked, speaks each letter as it is typed. Tap Speak Lettersto uncheck.Speak WordsWhen checked, speaks each word as it is completed. A word must befollowed by a space, punctuation or a paragraph return beforeWrite:OutLoud To Go can speak it. Tap Speak Words to uncheck.Write:OutLoud®To Go Speak SentencesWhen checked, speaks each sentence as it is completed. A sentence mustbe followed by punctuation (period, exclamation point or question mark)before Write:OutLoud To Go can speak it. Choose Speak Sentences touncheck.Speak ParagraphsWhen checked, speaks each paragraph as it is completed. There mustbe a return for the paragraph to be spoken. Tap Speak Paragraphs touncheck.Word HighlightWhen checked, individual words are highlighted as they are spoken.Tap Word Highlight to uncheck.Voice SettingsAdjusts speed and voice volume.To increase voice volume, move the volume slide bar to the right.To decrease the voice volume, move the volume slide bar to the left.To increase the speed of the voice, slide the speed bar to the right.To decrease the speed of the voice, slide the speed bar to the left.Choose OK to accept any changes and return to the document.Choose Cancel to return to the document without any changes.Write:OutLoud®To Go Keyboard ShortcutsKeysFileNew CMD + NOpen CMD + OClose CMD + WSave CMD + SSave As CMD + HDelete CMD + JBeam File CMD + BPrint One CMD + IPrint CMD + PExit CMD + QEditUndo CMD + ZCut CMD + XCopy CMD + CPaste CMD + VClear CMD + USelect All CMD + AFind…CMD + FGo to Start of Doc CMD + (Go to Next Sentence CMD + #Select Sentence CMD + %Go to End of Doc CMD + )ToolsCheck Spelling CMD + GTextGrow Selection CMD + ]Shrink Selection CMD + [OptionsShow/Hide Toolbar CMD + ;Write:OutLoud®To Go SpeechSet Speech On CMD + DSpeak CMD + TRepeat CMD + RStop Speech CMD + .Speak Letters CMD + KSpeak Words CMD + ESpeak Sentences CMD + MSpeak Paragraphs CMD + \Word Highlight CMD + ,Voice Settings CMD + /WindowAbout CMD + YOtherSpell Checker DialogLearn CMD + LNext Word Alt + [Close window CMD + !Select Characters Beside and Above CMD + *Select Characters Beside and Below CMD + @Select Next Character CMD + >Select Previous Character CMD + <Write:OutLoud®To Go Limited WarrantyDon Johnston Incorporated warrants software for one year from date of purchase.This warranty is valid against manufacture defects and malfunctions not the result ofabuse or mishandling. Except for the above, Don Johnston makes no warranties,express or implied, including warranties as to the merchantability or as to the fitnessof this product for any particular purpose, and shall not be liable for any loss ordamage, directly or indirectly, arising from the use of this software product or forconsequential damages.Don Johnston Incorporated reserves the right to make any changes, additions orimprovements to software or documentation at any time without notice to anyperson or organization.The manuals and the software described in them are copyrighted, with all rightsreserved. Under the copyright laws, the manuals or the software may not be copied,in whole or in part, without written consent of Don Johnston, except in the normaluse of the software. The same proprietary and copyright notices must be affixed toany permitted copies as were affixed to the original. This exception does not allowextra copies to be made for others, whether or not sold, but all the materialpurchased (with all backup copies) may be sold, given, or loaned to another person.Under the law, copying includes translating into another language or format.You may use the software on any computer owned by you, but extra copies cannotbe made for this purpose.DON JOHNSTON INCORPORATED MAKES NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, REGARDING THE SOFTWARE. DON JOHNSTON'S LICENSOR(S) DOES NOT WARRANT, GUARANTEE OR MAKE ANY REPRESENTATIONS REGARDING THE USE OR THE RESULTSOF THE USE OF THE SOFTWARE IN TERMS OF ITS CORRECTNESS, ACCURACY, RELIABILITY, CURRENTNESS OR OTHERWISE. THE ENTIRE RISK AS TO THE RESULTS AND PERFORMANCE OF THE SOFTWARE IS ASSUMED BY YOU. THE EXCLUSION OF IMPLIED WARRANTIES IS NOT PERMITTED BY SOME JURISDICTIONS. THE ABOVE EXCLUSION MAY NOT APPLY TO YOU.IN NO EVENT WILL DON JOHNSTON'S LICENSOR(S) AND THEIR DIRECTORS, OFFICERS, EMPLOYEES OR AGENTS (COLLECTIVELY DON JOHNSTON'S LICENSOR) BE LIABLE TO YOU FOR ANY CONSEQUENTIAL, INCIDENTAL OR INDIRECT DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, AND THE LIKE) ARISING OUT OF THE USE OR INABILITY TO USE THE SOFTWARE EVEN IF DON JOHNSTON'S LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. BECAUSE SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE ABOVE LIMITATIONS MAY NOT APPLY TO YOU.Don Johnston's Licensor's liability to you for actual damages from any cause whatsoever, and regardlessof the form of the action (whether in contract, tort (including negligence), product liability or otherwise),will be limited to $50.。

DroolsFusion（CEP）定义及使用方法讲解

DroolsFusion（CEP）定义及使⽤⽅法讲解从 Drools 统⼀⾏为建模平台的视野看，Drools Fusion 是负责启⽤事件处理⾏为的⼀个模块。

定义⽀持复杂事件处理，是⽐简单的理解事件是什么要更多得多，cep场景具有⼏个共同⽽明显的特点：通常需要处理巨量的事件，但是只有少部分事件是真正关⼼的。

事件通常是不变的，因为它们是状态改变的⼀条记录。

通常有关事件的规则和查询必须是运⾏在被动模式(reactive modes)，即，对事件模式(patterns)的检测作出反应。

通常在相关的事件之间有强烈的时间关系。

个别事件通常是不重要的。

系统关⼼相关事件的模式(patterns)和它们的关系通常，要求系统执⾏组合和聚合的事件。

⽤fusion,要把插⼊drools的数据声明为事件。

drools处理数据有两种⽅式，云模式和流模式，默认是云模式，⽤fusion,需要设置为流模式。

流模式，插⼊的数据叫事件，有时间顺序，云模式没有，流(stream)⽀持⼤部分 CEP ⽤例必须处理事件流(stream)。

流的特性：在流中的事件通过时间戳被排序。

事件的数量(volumes)总是很⾼的。

原⼦事件⾃⼰是很少有⽤的。

通常根据多个事件之间的相关性或流或其他来源提取含义。

流可以是相似的，即包含单⼀类型的事件;或者是异类的，即包含多种类型的事件。

声明流模式在kmodule.xml 中添加配置 eventProcessingMode=“stream” 为流模式<kbase name="fusionAge" eventProcessingMode="stream" packages=".fusion"><ksession name="fusionAgeKS" type="stateful"/></kbase>事件声明⽤fusion,要把插⼊drools的数据声明为事件，声明事件使⽤@role标签@role把@role元数据标签指派给该事实类⾏例如：Person 为java bean 也就是⼀个事实类型declare Person@role(event)endPerson 的属性如下：public class Person {private String name;private Integer age;private String like;private String sex;private String desc;private String address;private Date createTime;// getter setter 省略@timestamp每⼀个事件都要有⼀个关联的时间戳指派给它。

Altronic CPU-95EVS程序说明书

1.0 DESCRIPTI O N1.1The Altronic CPU-95EVS program operates from a standard PC andpermits the operator to program a standard or custom configuration.With the Altronic CPU-95EVS Terminal Program software, the user can obtain the full benefit of the capability designed into the CPU-95EVS system. Custom timing curves, offset timing on an individual cylinder basis, and advanced features can be programmed. A data sheet can be printed showing, in table form, the engine firing pattern resulting from the information entered as well as other programming information. There is a monitor mode that the operator can use to monitor an existing installation and access most keypad configurable settings via the RS-485 serial link.1.2The following Altronic material is required:CPU-95EVS Terminal ProgramAvailable from /catalog-downloads.shtml 1.3The following user-supplied hardware is required:Computer: IBM-compatible PC, Windows™ XP, 7, 8, 10Hard drive (10 Mb of free disk space required)CD-ROM drive1 RS-232 serial portSVGA graphics (800x600 or greater preferred)Color monitorPrinter: Selections on screen for windows printerSerial Converter: RS-485 to RS-232 serial converter for PC interface.Two wire, half duplex, multidrop, binary communications,RTS controlled.2.0 INSTALLATI O N2.1The program can be downloaded from Altronic’s website at http:///catalog-downloads.shtml. A minimum of 10 megabytes of free disk space is required.2.2Installation of the Altronic Terminal program requires “AdministrativePrivilege”.Once Setup_CPU95EVS_Vxx.exe has been downloaded from the Al-tronic Website, run the file as Administrator. The install program will prompt you for a destination folder where the program will be installed.The default folder is C:\Altronic LLC\Altronic CPU-95EVS Ignition Sys-CPU-95EVS TERMINAL PROGRAMFORM CPU-95EVS PI 10-17CPU-95EVS DIGITAL IGNITION SYSTEMtem Terminal Program Vx.x. After the install completes, you can run the program from the Start Button, Programs M enu, Altronic LLC, CPU-95EVS, CPU-95EVS menu selection.3.0 PROGRAM OPERATION, CPU-95EVS3.1LOAD PROGRAM: Once installed, to load the program, click on the CPU-95EVS icon.3.2LOGIN FORM: Following the opening pictorial screen, the Login formappears. Type in your initials or code. Select the PC communications port to which the RS-485 Converter will be connected to. (COM1 – COM10). If the COM Port has a non-standard interrupt or address, these can be edited. Enter the Node number of the unit you want to communicate with. A Node number of 0 (zero) will allow you to query the unit for the programmed node number.3.3MAIN FORM: 6 OptionsA. Monitor: allows the operator to monitor a unit and adjust valuesvia the serial link.B. Configure: allows the operator to configure the CPU-95EVS foroperation.C. Print: allows the operator to print out a stored program sheet.D. Exit: Quits program.E. Help Menu: About CPU-95EVS; displays version information ofthe Terminal Program and CPU-95EVS firmware.4.0 PROGRAM EEPROM4.1The TAB/SHIFT-TAB or RETURN will move the cursor between fields.4.2Enter the Node number of the unit to be programmed. Values can be1 – 254.4.3Select the type of Ignition Module to be used from the drop down list.4.4Select the Firing Pattern Code. These are found in Application List,form CPU-95EVS AL. Pressing Enter or Double Clicking on this field will bring up the list box of firing pattern selections.4.5Enter the number of teeth or holes; the limits are 90-500. Some fir-ing patterns will have limited options as the number of teeth increases vs. firing angles.4.6Select the choice for Current Loop type:X - No current loop will be used.A - Standard 48 degree curve.B - Standard 36 degree curve.C - Standard 24 degree curve.D - Standard 16 degree curve.E - Standard 8 degree curve.SPECIAL - Denotes user-entered special curve.PROGRAMMING INSTRUCTIONS 4.7Select the choice for RPM Curve:NO - No RPM Curve desired.YES - Enter an RPM curve; this makes the memory an “N” type, so aversion number will have to be specified, if not already defined.Follow the instructions on screen for completing the table.4.8Select the choice for Advanced Features:NO - No, use default choices (one-step retard active through M isc.terminal).YES - Yes, choose Advanced Features.Follow the instructions on screen for completing the table.4.9Select the choice for Cylinder Offsets (permanent modification of fir-ing pattern):NO - No Cylinder Offsets desired.YES - Yes, define Cylinder Offsets; this makes the memory an “N”type, so a version number will have to be specified, if not al-ready defined. Follow the instructions on screen for completingthe table.4.10INITIAL USER SETTINGS: These include Overspeed Setting, Energy Level,Multifire option, and Reset Pin Position. Select the desired values foreach field.4.11COMMENTS: These fields are to store site-specific data in the EEPROM.Engine location, number and model can be stored along with fourlines of user comments.4.12SAVING DATA: After completing the above information, pressing the AC-CEPT button saves the input screen information. A display form willthen show all selected values. To return to the input screen, press thePREVIOUS SCREEN button. To print a data sheet, press the PRINTbutton. It is recommended that data sheets for all generated memoriesbe kept on file for easy reference. Pressing the PROGRAM button ac-cepts the display sheet information and will generate the memory file.4.13PROGRAMMING EEPROM: The Shutdown Lead must be grounded to pro-gram the EEPROM. Follow the instructions on the screen to completethe programming cycle and return to the Main Form.5.0 MONITOR MODE5.1On systems which have no Display Module or where the 791902-xDisplay Module is being used, the communication link must be es-tablished by directly connecting the computer to the Ignition Module.If the 791902-x Display Module is used it must be temporarily dis-connected to use the computer monitor. The monitor program is ac-cessed by clicking on the CPU-95EVS icon from the opening screenof the programming program. SEE SECTION 3 for details. The defaultlocation for this program is C:\Altronic LLC\Altronic CPU-95EVS Igni-tion System Terminal Program Vx.x\CPU95EVS.exe.The option of a dual port Display M odule part number 791908-1has been added to allow for the simultaneous connection of both theCPU-95EVS DIGITAL IGNITION SYSTEMDisplay Module and a customer computer or PLC via Modbus. When the 791908-1 unit is used, the computer is connected to the auxiliary output port of the Display Module and the monitor function is accessed by running a special program. To install the M onitor program for use with the 791908-1 display, run the setup file CPU-95EVSdpd_setup.exe.The default location of this program is C:\PROGRAM FILES\CPU-95EVS DUAL PORT DISPLAY MODBUS MONITOR\CPU-95EVSDPD.EXE.5.2To select the Monitor function, click on the Monitor selection on thetop edge of the Windows™ tool bar. On screen directions are provided to help guide the user through the Monitor program. Any field that has adjacent up/down arrows can be modified while the unit is be-ing monitored. Use the mouse or TAB/SHIFT TAB keys to move the screen cursor to the field to be modified. Clicking on or pressing the ENTER key while the cursor is on either the UP or DOWN ARROW will cause the arrow to turn black for a moment and execute the appropri-ate request. The UP ARROW will increase a value or turn an option on.The DOWN ARROW will decrease a value or turn an option off.Values which can be adjusted from this screen include:⏹Ignition Timing⏹Energy Level⏹Multistrike Operation⏹Overspeed Setting⏹Reset Pin Position⏹Value Protection5.3Pressing EXIT will take the user back to the Main form. Like keypad opera-tions, most changes are retained by the unit until changed again.5.4DIAGNOSTIC BUTTON: brings up the diagnostic monitor screen. This al-lows the operator to view coil and spark plug diagnostics.A. Diagnostic field characters:“.” indicates normal operation“X” indicates a faulted conditionB. VIEW/ADJUST DIAG SETPOINTS button — will open the View/Adjust Diagnostic Setpoints screen.C. AUTOCAL COILS button — allows the user to equalize each cyl-inder diagnostic number.D. RESET SPARK DIAG Button — resets the spark diagnostics.E. PRINT button — will print out current spark diagnostic data.F. EXIT button — will exit back to the system monitor screen.5.5VIEW/ADJUST DIAGNOSTIC SETPOINTS SCREEN: This screen allows the op-erator to adjust the spark diagnostic setpoints.A. Any field that has adjacent up/down arrows can be modified. Usethe mouse or TAB/SHIFT TAB keys to move the screen cursor tothe field to be modified. Clicking ON or pressing the ENTER keywhile the cursor is on the UP or DOWN ARROW will cause thearrow to turn black for a moment and execute the appropriate re-quest. The UP ARROW will increase a value or turn an option on.The DOWN ARROW will decrease a value or turn an option off.B. The EXIT button will exit back to the diagnostic monitor screen.PROGRAMMING INSTRUCTIONS5.6AUTOCAL COILS SCREEN: Allows the operator to equalize coil diagnosticnumbers.A. Enter TARGET VALUE – The valid range is listed below the boxand is dependent on the current range of diagnostic numbers.B. EQUALIZE COIL button – automatically adjusts the coil offsets tomatch the cylinder diagnostic number to the target value. Offsetscan also be manually adjusted by using the UP/DOWN Arrow keysadjacent to each offset value.C. ZERO OFFSET button – resets all offsets to zero.D. RESET SPARK DIAG button – resets the spark diagnostics.E. EXIT button – will exit back to the diagnostic monitor screen.6.0 SPECIAL FEATURES ON 791908-1 AND 791909-1DUAL PORT DISPLAYS6.1In addition to all of the features available with the 791902-x Dis-play Module, the 791908-1 Dual Port Display Module adds Modbuscommunications using an industry standard Modicon Modbus RTUprotocol. The Modbus communication parameters are user selectablefrom either the front keypad of the module itself or by selecting theModbus option from the Windows tool bar. Selections are availablefor Baud Rate, Parity, Stop Bit, etc. For a complete listing of Modbusregisters, see the CPU-95EVS Modbus.pdf file on the CD.6.2 A datalogging capability has been built into the 791908-1 DisplayModule which allows the user to access up to 100 historical datalogsrecording the operating RPM of the engine, the value of the sparkreference numbers, the ignition timing and the presence of any diag-nostic messages. These datalogs are taken at a pre-determined timeinterval which is user selectable. In addition to the standard timebased datalogs, the occurrence of alarms or shutdowns triggers animmediate time stamped datalog. To access the datalogs from theopening screen, click on the Datalog option on the Windows tool bar.6.3When using the CPU-95DPD terminal program, a number of addi-tional options are also available to the CPU-95EVS user with the791908-1 Display Module. These include password protection of ad-justments from the keypad, the elimination of the test function, theadjustment of the time and date, the retention of datalogs on powerloss, and the datalogging interval. To access these user selectableoptions click on the Configure option on the Windows™ tool bar.6.4The 791909-1 includes the features of the 791908-1 with the addi-tion of USB and more flexible programming options for the attachedignition module. See form CPU-95EVS OI-E (operating instructions)for further details on these features.CPU-95EVS DIGITAL IGNITION SYSTEM7.0 TROUBLESHOOTING7.1COM485 ERRORA. RS232-RS485 Converter not connected or not working7.2NO REPLY IN 13 mSecA. CPU-95EVS node selection incorrectB. CPU-95EVS not connectedC. CPU-95EVS not powered7.3INVALID RS-232 ADDRESSIf the message Invalid RS-232 Address is received when selecting the serial port in the CPU-95EVS terminal program, the following proce-dure is required.On your PC desktop, go to Start, Run and type in “regedit.exe”.Then successively choose the following path names:HKEY_L O CAL_MACHINESystemCurrentControlSetServicesVxDVC O MMThen change the binary data value for the EnablePowerManagementregistry location from 01 00 00 00 to 00 00 00 00.MICROSOFT WARNING: Using Registry Editor incorrectly can cause seri-ous problems that may require you to reinstall your operating system.Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the Changing Keys and Values Help topic in Registry Editor (Regedit.exe) or the Add and Delete Information in the Registry and Edit Registry Data Help topics in Regedt32.exe.IMPORTANT: This article contains information about editing the registry.Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the Restoring the Registry Help topic in Regedit.exe or the Restoring a Registry Key Help topic in Regedt32.exe.。

CEP3.0FAQ

编译cep3提示gcc有问题解决办法：Gcc要设置为英文加载启动sql时出现timeout解决办法：1.检查master是否启动2.检查系统资源是否足够3.重新加载sql（因为加载时对内存的消耗非常大，这里存在可能的问题）4.如果还是timeout，停掉master，执行./cep clean-state,然后重启master，再次加载Dataload日志出现有字符集问题解决办法：1.找到该文件，目测找到有乱码的那一行记录，提取到ue编辑器中，将“，”替换为“^p”(即横变竖)，然后跟数据库内的表结构进行比对找到有问题的字段2.一般在ztpclient里面的类型为text的才能进行结构转换，具体的转换在define的目录中，根据具体对应的协议，类似图中的，那就要修改/servobj/users/define/define_dr_http_tdr.sql,修改方法如下图3.还有一种情况就是第一步比对的时候发现dataload日志中load语句的结构体跟数据库内表的结构不一致，如果是已经升级到CEP 3.0 11版本的现场，并且是根据filesender pe 生成的表，那就需要把数据库表drop掉，由cep重新建立（这个问题一般出现在gppartition和cep自动建表的切换过程中，如果用11版本替代gppartition，建议将数据库内已经生成的明日的表drop掉）4.如果确认错误数据量不大，没有大的影响是，可以修改dataload.properties的gprejectcount，这是容错记录数，即配置条数范围内的错误，都会忽略掉，不影响文件入库加载sql或者启动master找不到Host解决办法：1.记录下该机器的hostname2.Root用户登录vi /etc/hosts，将对应的机器IP和hostname写入3.切换回cep用户，重新启动加载sql提示VM错误该问题是虚拟机内存的问题解决办法：1.检查cat /etc/sysctl.conf | grep overcommit_memory结果2.Root用户登录，修改为2Xdr_output下文件积压问题解决办法：1.确认目录名称是filesender的，才是需要进行入库，该目录下的文件默认是写10分钟，在io不忙，等待不超过3%的情况下，往dataload/pipes传送文件，因为要先读取文件，所以对io有所要求2.Filesender目录下的文件为空，要保证表的建立，之前讨论是4个小时写一个空文件，保证表的存在3.非filesender目录，可能是需要进行相互关联的文件目录，例如上网日志分两个部分，相互之间要用内网IP进行关联得到，具体的配置sql中有体现，要保存5个小时Dataload 0点数据不入库河北出现了此问题，导致0点时段的数据无法入库解决办法：1.检查对应的加载sql的filesender，里面定义了多少小时一个分区，时分区，但是分区表的起点时刻还是要以数据库的为准。

eSchoolPLUS - LEA User Guide

Assigning Points of Contact (POC) in eSchoolPLUSLEA User GuideT ABLE OF C ONTENTSOverview (2)Login to eSchoolPLUS (2)Adding New Staff (2)Assigning POC to Existing Staff (5)Further Assistance for Users (5)Frequently Asked Questions (FAQs) (5)O VERVIEWThis guide outlines steps for the LEA Data Manager to add and assign a Point of Contact (POC) role at the LEA or school in eSchoolPLUS. LEA staff designated as the LEA Data Manager have the ability to add staff to eSchoolPLUS. If the LEA Data Manager needs access to eSchoolPLUS, please submit a ticket in the OSSE Support Tool. All LEAs must enter and update their LEA POC’s for each school year. Changes in school staff may also require updates to POC roles in eSchoolPLUS during the school year.Login to eSchoolPLUS1.Go to https:///eSchoolPLUS/Account/.2.Login to eSchoolPLUS using your eSchoolPLUS username and password.A DDING N EW S TAFF1.Go to https:///eSchoolPLUS and login.2.In the Quick Search box, type the ‘Staff’.3.The Staff Search page opens.4.Click the Add () icon.5.In the Last Name field, enter the person’s last name and hit the Reload ()icon. The applicationsearches for the staff member to ensure the name does not already exist.a.If results are returned and the person is listed, click the Building number link to edit the staffrecord and follow step #15 below.b.If results are returned but the person is not listed, click the Add () icon to add a staff recordand follow step #6 below.c.If no results are returned, the Staff District Information page opens and follow step #6 below.6.Enter the required Staff ID, First Name, Last Name and Email fields for the new staff record.7.Click the Save () icon.8.On the Building Information panel, click the Add a Row () icon.9.The Staff Building Information page opens.10.In the Staff Identification panel, click the dropdown for the Building field to select the 9000 for LEA-level assignment or the school ID for school-level assignment.NOTE: Follow step #6 below to add more schools.11.Click the Save () icon.12.To add more schools, click the Previous Page () icon otherwise skip to step #15.13.The Staff Building Information page opens.14.On the Building Information panel, click the Add a Row () icon and follow steps 10 and 11.15.In the District-Defined panel click the Point of Contact link.NOTE: The Point of Contact hyperlink will not appear on the staff information page unless a Building is assigned to the user.16.The Point of Contact page opens.17.In the Contact Title file, enter the person’s job title at the LEA.18.In the Point of Contact Fields panel, click the dropdown for the first available Position field to select thePOC for the person. Repeat this step to assign additional POCs.A SSIGNING POC TO E XISTING S TAFF1.Go the Quick Search box, type the ‘Staff’.2.Locate the person’s name in the Staff Name column.3.Click the Building number for the person’s name.4.The Staff Building Information page opens.5.In the District-Defined panel, click the Point of Contact link.6.The Point of Contact page opens.7.In the Point of Contact Fields pane, click the dropdown menu for the first available Position.8.Click the Save () icon.F URTHER A SSISTANCE FOR U SERSFor any questions, concerns or further assistance, please submit a ticket through the OSSE Support Tool (OST).F REQUENTLY A SKED Q UESTIONS (FAQ S)Q: How can the LEA Data Manager get access to eSchoolPLUS?A: LEA staff considered the LEA Data Manager has the ability to add and modify LEA POC’s in eSchoolPLUS. If the LEA Data Manager needs access to eSchoolPLUS, please submit a ticket in the OSSE Support Tool.Q: Why are new POC roles added to eSchoolPLUS?A: OSSE is centralizing LEAs’ POCs collection in eSchoolPLUS to minimize multiple sources for LEA contacts. Different divisions at OSSE may request a new eSchoolPLUS POC role to streamline regular communications. Q: When are new eSchoolPLUS POC roles announced to LEAs?A: New eSchoolPLUS POC roles are announced in the Data, Assessment and Research Monthly Data Discussion meetings with LEA Data Manager. Also, communications are sent by the OSSE division who added the eSchoolPLUS POC role.Q: How does OSSE use eSchoolPLUS POC roles?A: OSSE will send communications to the eSchoolPLUS POCs. Also, access to applications i.e. Qlik, Box and others are granted based on the eSchoolPLUS POCs roles. Please ensure this information is accurate and up to date for the LEA.Q: When is Box (a secure data transfer system), access updated based on eSchoolPLUS POCs?A: Access to Box is granted to specific eSchoolPLUS POCs, the next day. The person’s email address must be entered in eSchoolPLUS to ensure Box access is granted. Please ensure this information is accurate and up to date for the LEA.。