Data Buffer Tab Sample Clauses

Data Buffer Tab. When running as an ActiveX object instanced from a parent application, the data buffering functions give control over the frequency of signaling to the parent that there is data available for upload from microDAQX. As well as signaling the parent, it is possible to perform rudimentary data logging from microDAQX, writing values to a comma delimited text file. This rudimentary data logging function will work from microDAQX running as a standalone application. The controls are shown in figure 4.6, and detailed in table 4.4 Figure 4.6, The Data Buffer Tab. A buffering cycle comprises a fixed number of data points per channel received from the microDAQ, this number of samples being selected from the 'Samples per Cycle' dropdown. The 'Raise Event' frame controls when microDAQX signals that it has data ready to be read by a parent application in terms of completed buffer cycles. The total data points collected per channel is the product of the samples per cycle and the number of buffer cycles selected. The data passed up to the parent is therefore identical for the two settings examples of 20 cycles of 100 samples or 1 cycle of 2000 samples, though in the case of the latter the parent application will receive only 1 event rather than 20. Buffering may be started and stopped by the two buttons on the form, whose function is replicated as a property over the public interface for parent applications. Alternatively, the buffering may be started and then wait for a trigger of a certain data value on a particular channel before starting the desired buffering regimen. The furthest left indicator in the upper right of the main form shows red for buffering 'on', and the central indicator blinks when a buffer cycle is complete. On the completion of this buffer cycle the signaling event is raised by microDAQX. The 'Log to Disk…' checkbox forces the appending of the last buffered data to the selected logging file whenever the Raise Event condition is met. User Control Function Raise Event options Select how often an event is raised with a parent application, or the last data is written to disk, in terms of buffer cycles. Log to Disk… checkbox Check to append values to the selected CSV file when the raise event condition is met. Start options Choose between simple on/off, or wait for a suitable data value on a channel before starting. Samples per Cycle dropdown The number of data points (per channel) comprising a buffer cycle for the purposes of calculating the Raise Event t...
AutoNDA by SimpleDocs

Related to Data Buffer Tab

  • SHOP DRAWINGS, PRODUCT DATA AND SAMPLES 4.12.1 Shop Drawings are drawings, diagrams, schedules and other, data specially prepared for the Work by the Contractor or any Subcontractor, manufacturer, supplier or distributor to illustrate some portion of the Work.

  • Random Drug Testing All employees covered by this Agreement shall be subject to random drug testing in accordance with Appendix D.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Network Interface Device (NID) 2.7.1 The NID is defined as any means of interconnection of end-user customer premises wiring to BellSouth’s distribution plant, such as a cross-connect device used for that purpose. The NID is a single-line termination device or that portion of a multiple-line termination device required to terminate a single line or circuit at the premises. The NID features two independent xxxxxxxx or divisions that separate the service provider’s network from the end user’s customer-premises wiring. Each chamber or division contains the appropriate connection points or posts to which the service provider and the end user each make their connections. The NID provides a protective ground connection and is capable of terminating cables such as twisted pair cable.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where InterGlobe has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to InterGlobe. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for InterGlobe (e.g. hairpinning):

  • DRUG/ALCOHOL TESTING 11.1 The parties agree that the maintenance of a drug/alcohol free work place is a goal of both the College and the Union. Employees are prohibited from possession, consumption and/or being under the influence of a controlled substance/alcohol while on the College’s premises or during time paid by the employer. Violations of this prohibition may result in a disciplinary action up to and including termination.

  • Supervisory Control and Data Acquisition (SCADA) Capability The wind plant shall provide SCADA capability to transmit data and receive instructions from the ISO and/or the Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected, as applicable, to protect system reliability. The Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected and the wind plant Developer shall determine what SCADA information is essential for the proposed wind plant, taking into account the size of the plant and its characteristics, location, and importance in maintaining generation resource adequacy and transmission system reliability in its area.

  • MSAA Indicator Technical Specification Document This Agreement shall be interpreted with reference to the MSAA Indicator Technical Specifications document.

  • Access to Network Interface Device (NID 2.4.3.1. Due to the wide variety of NIDs utilized by BellSouth (based on subscriber size and environmental considerations), Mpower may access the on-premises wiring by any of the following means: BellSouth shall allow Mpower to connect its loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premise. Mpower agrees to install compatible protectors and test jacks and to maintain the protection system and equipment and to indemnify BellSouth pursuant to Section 8 of the General Terms and Conditions of this Agreement.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

Time is Money Join Law Insider Premium to draft better contracts faster.