1. Manuals
  2. Brands
  3. Intelligent instrumentation Manuals
  4. Control Systems
  5. EDAS CE
  6. Manual

Intelligent instrumentation EDAS CE Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
EDAS CE Manual
www.edasce.com
855M536
Copyright 2001-07 by Intelligent Instrumentation Incorporated, Tucson, Arizona, U.S.A.
All rights reserved.

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the EDAS CE and is the answer not in the manual?

Questions and answers

Summary of Contents for Intelligent instrumentation EDAS CE

  • Page 1 EDAS CE Manual www.edasce.com 855M536 Copyright 2001-07 by Intelligent Instrumentation Incorporated, Tucson, Arizona, U.S.A. All rights reserved.
  • Page 2 Email Support Intelligent Instrumentation’s technical support can be reached via email. When sending an email message, be sure to include complete contact information as well as a detailed description of the problem and the products being used to:...

  • Page 3: Revision History

    Other products or brand names are trademarks or registered trademarks of their respective companies. Use of Equipment Intelligent Instrumentation Inc., assumes no responsibility for any direct, indirect or consequential loss or damages resulting from misuse of the equipment or for improper or inadequate maintenance of the equipment or for any such damage or loss resulting from the use of other equipment, attachments, accessories, and repairs at any time made to or placed upon the equipment or any replacement thereof.

  • Page 4: Table Of Contents

    Table of Contents Chapter 1: Hardware and Installation ......... 1 1.1 Modules..............1 1.1.1 Base Unit ............1 1.1.2 Power Supply ............6 1.1.3 Digital I/O Module ..........8 1.1.4 Analog Input Module ..........12 1.1.5 Digital Input Module ..........17 1.1.6 Digital Output Modules ..........
  • Page 5 4.2.8 Quadrature Functions ..........132 4.2.9 Alarm Functions ........... 141 4.2.10 System and Utility Functions ........152 4.2.11 System Calibration ..........156 4.2.12 Memory Management ..........160 4.3 Return Error Codes for CE Link and EDAS CE API Functions....163 Index ..............179...
  • Page 6 This page intentionally left blank.

  • Page 7: Chapter 1:Hardware And Installation

    Typical EDAS CE System FIGURE 1.1 1.1 Modules An EDAS CE system consists of a power module, a base unit and I/O modules as needed to meet the specific needs of the targeted application. All the modules are plug-and-play, requiring no system configuration.
  • Page 8 Windows 32 API. See Chapter 3: Developing Custom Programs. The EDAS CE includes a program (suprcate.exe) that runs on the EDAS CE as a data server. A PC or other computer can open a connection and issue commands to read and write the EDAS CE I/O points.
  • Page 9 Platform and C on Unix platforms. See the Net Link Manual for more information. 1.1.1.2 EDAS-2000E Base Unit Specifications All specifications are typical at 25° C unless otherwise noted. Parameter Condition Specification Processor AMD Elan SC400 Operating System Windows CE 3.0 DRAM Memory 64 MB 72-pin EDO SIMM 60 ns...
  • Page 10 1.1.1.5 Real-Time Clock Battery The base unit contains a 3.0 V lithium battery that powers the Real-Time Clock when external power is absent. Battery life is approximately two years when the unit is not powered. When the unit is on external power, battery life is longer since the battery does not have an appreciable power draw in this condition.
  • Page 11 1.1.1.6 DRAM The EDAS-2000E can use up to 64 Mbytes of DRAM. The DRAM is industry standard 5 V, 72- pin EDO or FPM. To change the DRAM module, remove the right hand cover of the unit. 1.1.1.7 Compact Flash The EDAS-2000E uses standard Compact Flash memory for non-volatile storage of the operating system and drivers.

  • Page 12: Power Supply

    Power Supply 1.1.2 The EDAS-2001E power supply module provides power for the base unit and attached modules. The EDAS-2001E can accept line voltages of 90 - 260 VAC @ 50 - 60 Hz. EDAS-2001E-1 Power Supply Module FIGURE 1.4 EDAS-2001E-2 and -3 Power Supply Module FIGURE 1.5 Hardware and Installation 6...
  • Page 13 1.1.1.10 EDAS-2001E Power Supply Specifications The EDAS-2001E supplies 5 VDC power to the CPU module which in turn supplies power to the I/O modules. The -2 and -3 have quick a disconnect connector that can be used to pull 5VDC and 12 VDC (-2) or 24 VDC (-3) power from the supply to power other components in your system.

  • Page 14: Digital I/O Module

    Digital I/O Module 1.1.3 The EDAS-2002M Digital I/O Module has 8 digital inputs and 4 digital outputs. The digital inputs and outputs are designed for 24 VDC operation. All of the digital inputs and outputs provide 500 V channel to channel isolation with one return per channel. LEDs provide visual feedback on the channels’...
  • Page 15 EDAS-2002M Digital I/O module FIGURE 1.6 1.1.1.12 Input Functions The Digital I/O Module provides the following digital input functions. The inputs can be configured on a channel by channel basis. o Normal: Reads the current sates of the input (low/high). o Counter: 24 bit up/down counter, 250 Hz maximum count rate.
  • Page 16 o High Speed Counter: Channel 0 only, 16-bit counter at 20 kHz maximum count rate. 1.1.1.13 Output Functions The Digital I/O Module provides the following digital output functions. The outputs can be configured on a channel by channel basis. o Normal: Set output to desired state (open/closed) o Pulsed: Set output active for a specified amount of time.
  • Page 17 EDAS 2002M-1 Digital I/O Module Specifications TABLE 1.3 Hardware and Installation 11...

  • Page 18: Analog Input Module

    Analog Input Module 1.1.4 The EDAS-2003M Analog Input Module can read voltage, current and thermocouple inputs. Voltage, current or thermocouple readings can be configured on a channel by channel basis, allowing one analog input module to read a combination of voltage, current or thermocouple inputs. EDAS-2003M Analog Input module FIGURE 1.7 Hardware and Installation 12...
  • Page 19 The analog input stage consists of a 16 channel multiplexer (MUX), followed by a programmable gain amplifier (PGA), feeding a 12-bit analog to digital converter (ADC). The output of the ADC is isolated and presented to the system bus. The MUX is capable of providing 16 single- ended inputs, 8 differential inputs or a mixed combination to the PGA.
  • Page 20 Enable the CJC circuit (SW3-9). This will connect the CJC circuit to channel 0 to be read as a single-ended analog input. If SW3-10 is turned on with SW3-9, the CJC may be read in differential mode. Switch Number Switch ON Switch OFF SW1-1 GND return for differential Channel A0...
  • Page 21 to control when conversions are started and stopped. This allows for the support of Stop on Trigger, Stop on delay after Trigger, Start on Trigger and N Conversions after Trigger modes. 1.1.1.17 Channel Scanner The Analog Input Module has a hardware channel scanner that scans channels 0 through N.

  • Page 22: Digital Input Module

    Ω 10 G || 3 pF Input Impedance Voltage Mode Ω Current Mode Common-Mode Range ±10 V Common-Mode Rejection Ratio Gain = 1 80 dB Gain = 10 86 dB Gain = 100 92 dB Noise RMS/p-p G=1 0.5 LSB/2 LSB Mono tonicity No missing codes 12 bits...
  • Page 23 Digital Input Module 1.1.5 The EDAS-2004M Digital Input Module provides 16 channels of 5V, 24 V, 120 V or 240 V input. The digital inputs provide 500 V channel-to-channel isolation with one return per channel. The 16 channels are arranged as two 8 bit ports, Port 0 and Port 1.
  • Page 24 1.1.1.20 EDAS-2004M Digital Input Module Specifications All specifications are typical at 25° C unless otherwise noted. Parameter Condition Specification Digital Inputs Opto Isolators 16 inputs EDAS-2004M-1 0-3 V High 9-30 V Current Vin = 24V 2 mA max EDAS-2004M-2 0-20 V High 70-130 V Current...

  • Page 25: Digital Output Modules

    Digital Output Modules 1.1.6 The EDAS-M Digital Output Modules provide 12 channels of open drain, 24 VDC (EDAS-2005M-1) or 360 VDC (EDAS-2005M-2) digital outputs. The digital outputs have 500 V channel-to-channel isolation with one return per channel. The 12 channels are arranged as two ports. Port 0 has 8 channels and Port 1 has 4 channels.
  • Page 26 1.1.1.21 EDAS-2005M Digital Output Modules Specifications All specifications are typical at 25° C unless EDAS-2005M Digital Output Modules Specifications TABLE 1.7 Parameter Condition Specification EDAS-2005M-1 Specification EDAS-2005M-2 Digital Output FET output 12 channels, 27VDC max 12 channels, 360VDC max 0.03 Ω 5 Ω, typ On resistance On current...

  • Page 27: Analog Output Module

    Analog Output Module 1.1.7 The EDAS-2006M Analog Output Module provides 8 channels of 0 to 10 V analog output. This module uses eight 12-bit digital-to-analog converters (DAC). The module has a single LED that will blink when an output is updated.
  • Page 28 1.1.1.22 EDAS-2006M Analog Output Module Specifications All specifications are typical at 25° C unless otherwise noted. Parameter Condition Specification Number of Outputs Resolution 12-bits (2.44 mV) Output Range 0-10 V Output current 10 mA max Accuracy +/- 5.2 LSB (13 mV) Isolation Outputs Bus - Channel...

  • Page 29: Serial Module

    Serial Module 1.1.8 The EDAS-2008M Serial Module provides four RS-232 serial ports. serial ports are interfaced through 9-pin D-subminiature connectors on the bottom of the unit. The EDAS- 2000E base unit can support 6 serial modules for a total of 25 serial ports, one on the base plus 24 on additional serial modules.
  • Page 30 116D x 150H x 42W Temperature Range Operating 0-60° C EDAS-2008M Serial Port Module Specifications TABLE 1.9 1.1.1.24 COM port mappings The COM ports on the serial module are mapped as COM2 through COM9 on the first two serial module, SER1 through SER8 on the next two and ASY1 through ASY8 on the last two.

  • Page 31: Relay Output Module

    Relay Output Module 1.1.9 The EDAS-2010M Relay Output Module provides 12 channels of single- pole/single-throw normally open relay contacts capable of switching 2 A at either 250 VAC or 30 VDC. This module has power-up initialization hardware allowing the configuration of the power-up state of each output. EDAS-2010M Relay Output Module FIGURE 1.12 Hardware and Installation 25...

  • Page 32: Digital Output (Triac) Module

    1.1.1.25 EDAS-2010M Relay Output Module Specifications All specifications are typical at 25° C unless otherwise noted. Parameter Condition Specification Relay Output Contact closure 12 outputs 0.03 Ω Closed resistance Closed current 2.0 A max Voltage 250 VAC max, 30 VDC max Isolation Outputs Channel - Channel...
  • Page 33 Digital Output (Triac) Module 1.1.10 The EDAS-2011M Digital Output Module provides 12 solid state (triac) outputs capable of switching 2 A at 120 VAC. This module has power-up initialization hardware allowing users to configure the power-up state of each output. EDAS-2011M Digital Output (Triac) module FIGURE 1.13 Hardware and Installation 27...
  • Page 34 1.1.1.26 EDAS-2011M Digital Output Module (Triac) Specifications Parameter Condition Specification Triac Output Contact closure 12 outputs 0.03 Ω Closed resistance Switching current 25° C 2.0 A max 60° C 1.0 A max Voltage 24 VAC to 240 VAC Isolation Outputs Channel –...

  • Page 35: Quadrature Module

    Quadrature Module 1.1.11 The EDAS-2015M Quadrature Module provides 2 independent quadrature decoder channels which can also be used as high-speed 32-bit counter channels. Each channel also provides two outputs which can be controlled manually or configured to output counter channel state information. Each channel also provides two inputs which can be used for counter channel control or for general-purpose digital input.
  • Page 36 1.1.1.27 EDAS-2015M Quadrature Module Specifications Parameter Condition Specification Quadrature Inputs/Up-Down 2. Maximum input rate is Counters 500kSteps/second, 2MHz for counting Inputs 24VDC compatible 2 count control per quadrature channel, 2 general purpose, 0-3V low, 9-30V high General-purpose Modes Separately configured for each Latch, preload, enable, general- input purpose...

  • Page 37: Installation

    FIGURE 1.16 Attaching a module to a DIN Rail 1.1.13 The EDAS CE modules are installed one at a time on to the DIN rail and then slid together. Install the Power Supply module first, followed by the Base unit, followed by I/O modules.
  • Page 38 Removing Modules from a DIN Rail 1.1.14 Using a screwdriver, lift the retaining spring until the module releases from the DIN rail. Note: Some modules have two retaining springs. To release the module from the DIN rail, lift both retaining springs. Hardware and Installation 32...

  • Page 39: Chapter 2:Utilities

    Chapter 2:Utilities 2.1 Summary of Utilities The EDAS CE unit is shipped with a number of pre-installed utilities which are summarized in the table shown below. These utilities simplify the development and deployment of applications on the EDAS CE. A brief description of each utility follows the table shown below.

  • Page 40: Monitorce

    With a null modem cable connected between COM1 on the EDAS CE and one of the computer’s serial ports, a communications application, such as HyperTerminal, may be used to configure many of the EDAS CE’s operating parameters.

  • Page 41: Serialsocket

    EDAS CE, a remote computer can open a TCP/IP socket to the EDAS CE and send and receive data to and from the EDAS CE’s serial ports. This is useful for remotely accessing serial devices connected to the EDAS CE’s COM ports.

  • Page 42: Monitorce

    A computer with an RS-232 port and a serial communications program, such as HyperTerminal. Connect the NULL modem serial cable to the EDAS CE base unit’s COM1 port and connect the other end of the cable to any available serial port on the computer.

  • Page 43: Starting A Monitorce Program Session

    EDAS CE powered up, start a MonitorCE program session. Note: From the time power is applied to the EDAS CE it will take approximately 30 seconds before the MonitorCE will be ready to accept a connection. To start a MonitorCE program session: In the serial communications program window, type the special string, @@@@ and press the Enter key.

  • Page 44: Monitorce Program Commands

    In the serial communication program window, to display help information, type h and press the Enter key. The EDAS CE responds with the current command set. Note: The backspace key is not supported in the MonitorCE program. If you use the backspace key the command or parameters will not be correctly processed.
  • Page 45 Real Time Clock: Setting Month: TIOx, where x = value from 1 - 12. Example: 3 = March Setting Day of the Month: TIDx, where x = value from 1 and 31. Setting Year: TIYxxxx, where x = year using four digits. Setting Hours: TIHx, where x = value between 0 and 24.

  • Page 46: Lcmdset

    2.3 LCmdSet The LCmdSet application on the EDAS CE unit acts as a server for the Telnet protocol. This application facilitates an Ethernet connection between a EDAS CE unit running the LCmdSet utility and a computer running a Telnet client application.

  • Page 47: Set Commands

    When the EDAS CE responds with password> type system<enter> You will now be privileged and will be allowed to change the unit’s IP address. To change the IP address, type change ipaddress nnn.nnn.nnn.nnn<enter> where nnn.nnn.nnn.nnn is the new IP address for the unit.
  • Page 48 The optional ADAPTER parameter defaults to zero, which corresponds to the built-in LAN9000-compatible adapter. The values displayed for IP addresses, the subnet mask, DHCP, and DNS and WINS lists may not be the operational settings. The settings are stored in the registry and will be applied at the next reboot. Show Command Function Calls IPADDRESS [ADAPTER n] Displays the IP address of the indicated network adapter.

  • Page 49: Change Commands

    DATETIME Displays the current local date and time of the unit. The date is displayed in mm/dd/yyyy (month/ day/year). TIMEZONE Displays the time zone of the unit, including the offset from GMT. It also displays whether the unit’s time zone is presently observing Daylight Savings Time or Standard Time. PROCESSLIST Displays a list of the processes running on the unit.
  • Page 50 When this option is set to ON, the IP address, subnet mask, and gateway address of the adapter are automatically set to 0.0.0.0. DNSLIST iplist [ADAPTER n] Changes the DNS addresses for a network adapter in the unit. The list can contain multiple IP addresses, separated by semicolons. WINLIST iplist [ADAPTER n] Changes the WINS addresses for a network adapter in the unit.

  • Page 51: Operational Commands

    DEBUGWORKSTATIONS wslist Changes the contents of the debugworkstations.txt file on the \Storage Card to include the specified list of workstation IP addresses and TCP/IP port numbers. The format is nnn.nnn.nnn.nnn[:port] where the port is optional and the default is 5000. The list can contain multiple items separated by semicolons.

  • Page 52: Remote Manager

    Applications such as machine monitoring and remote data logging can be implemented using WebDevice’s scripting language. user can extend the EDAS CE’s embedded Web site by uploading additional HTML pages, images and WebDevice script files. This allows the EDAS CE’s...

  • Page 53: Using The Remote Manager

    Using the Remote Manager 1.1.34 To use the Remote Manager, run a Web browser on a computer and point the browser to the desired EDAS CE unit by entering the EDAS CE unit’s IP address in the browser’s address (URL) window. Troubleshooting Errors If a 404 page not found error occurs: Enter http://IP in the address window, where IP is the EDAS CE unit’s...

  • Page 54: Remote Manager Home Page

    Remote Manager Help pages. Remote Manager Home Page 1.1.35 Access the Remote Manager home page by entering the EDAS CE unit’s IP address in the browser’s URL window. EDAS CE Remote Manager Home Page FIGURE 2.1...
  • Page 55 2.4.1.1 EDAS CE Information The information section of the EDAS CE home page displays the unit’s: o IP Address o Name o Location o Description To edit the name, location, and description information, click any of the links, Name, Location, or Description, to open the information page.
  • Page 56 System Manager - Reboot the EDAS CE. o Security Manager - View and edit user names and passwords. o Update Manager - Access and download software updates to the EDAS CE. o Developers Guide - Access to WebDevice scripting documentation and samples.

  • Page 57: Application Manager

    Application Manager 1.1.36 The Application Manager enables you to view the programs that are currently running on the EDAS CE, terminate a program, run a program and create shortcuts to run programs in the startup folder. Application Manager FIGURE 2.3...

  • Page 58: File Manager

    The File Manager allows a user to view files, download files, upload files, delete files, run programs and WebDevice script’s, create shortcuts to programs in the startup folder, create new folders, delete folders and copy files from one folder to another on the EDAS CE. File Manager FIGURE 2.4...

  • Page 59: Module Manager

    Module Manager 1.1.38 The EDAS CE module manager allows the user to view the attached modules, configure the I/O points on a module and read or write the I/O points EDAS CE Module Manager FIGURE 2.5 Utilities 53...

  • Page 60: System Manager

    System Manager 1.1.39 The System Management page allows the user to reboot the EDAS CE. Remotely Rebooting the EDAS CE FIGURE 2.6 Security Manager 1.1.40 The Security Manager allows a user to modify the access privileges for the EDAS CE through WebDevice.
  • Page 61 To add password protection to a folder, remove protection or edit existing user/password, click on the Edit/Remove link and alter the setting for the desired folder. Security Management main page FIGURE 2.7 Utilities 55...
  • Page 62 The WebDevice Server System Configuration page shown in FIGURE 2.8 WebDevice Server System Configuration page, displays the existing protected folders. Simply use the Edit or Remove link for the desired folder to change its setting. To add password protection to a folder that is not listed, use the Add New Protected Folder link.

  • Page 63: Update Manager

    Update Manager 1.1.41 The Update Manager allows the user to have the EDAS CE check the instrument.com Web site, or a user-created Web site on a corporate server, for new software updates. New updates may be downloaded by the EDAS CE directly from the instrument.com Web site or the corporate site.

  • Page 64: Debuglauncher

    2.5 DebugLauncher In order to download and debug applications on the EDAS CE unit using eMbedded Visual Tools (eVT), a connection must be established between the EDAS CE and your development PC. The program on the EDAS CE that provides this connection is DebugLauncher.exe.

  • Page 65: Changing The Contents Of Debugworkstations

    The debugworkstations.txt file can be changed using the MonitorCE or LCmdSet applications. See section 2.2 MonitorCE or section 2.3 LCmdSet for instructions. After making changes to the debugworkstations.txt file, the EDAS CE unit must be rebooted for the changes to take effect. Utilities 59...

  • Page 66: Timesync

    2.6 TimeSync The TimeSync program allows synchronization of the EDAS CE unit’s clock with an external time standard. The unit supports clock synchronization through the Internet Standard specification RFC 868, also known as the TCP TIME protocol. www.cis.ohio- The time standard obtained from the Web site state.edu/htbin/rfc/rfc868.htm, for example, has a one-second accuracy and a useful...
  • Page 67 Command line arguments once, every, and at can not be used together. Command Line Argument Description Configures TimeSync to run every day at a specific a[t] <time_string> time of day. The time_string field uses a 24-hour format (hh:mm:ss), where h = hour, m = minute, and s = second.

  • Page 68: Serialsocket

    EDAS CE unit. When this application is executed, it listens on TCP/IP sockets corresponding to the EDAS CE serial ports. When a remote host connects to one of the sockets, the application opens the corresponding serial port and establishes a connection between the socket and the serial port.
  • Page 69 EDAS CE serial port (e.g., 3002 for COM2), and press OK. Utilities 63...

  • Page 70: Ceflush

    Saving Registry Settings 1.1.51 The persistent registry settings on the EDAS CE unit are stored on the CompactFlash. The Windows CE operating system and the current registry settings run from DRAM. If a change is made to the registry while the unit is running, the changes are not persistent through a reboot of the unit unless the DRAM-based registry is saved to the CompactFlash card.
  • Page 71 This page intentionally left blank. Utilities 65...

  • Page 72: Chapter 3:Developing Custom Programs

    One of these runs on the EDAS CE and the other runs on PC, another EDAS CE or some other Ethernet connected device. This chapter covers the development of C/C++ applications that are downloaded to and execute on the EDAS CE unit (the servers in the above discussion).

  • Page 73: System Requirements

    Install the EDAS CE SDK (Software Development Kit) after completing the installation of the Microsoft eMbedded Visual Tools. The EDAS CE SDK CD contains the folder sdk_vc, containing the SDK to use with eMbedded Visual C++. Optionally, the SDK can be downloaded from our Web site at: www.edasce.com.

  • Page 74: Setting Up Communications To The Edas Ce

    For the EDAS CE to communicate with the development PC, you must place the IP address of the development PC in the debugworkstations.txt file located in the \Storage Card folder on the EDAS CE unit and then reboot the EDAS CE.
  • Page 75 3.1.1.4 Configuring eMbedded Visual Tools To set up eMbedded Visual Tools to communicate with the EDAS CE, start eMbedded Visual C++ and follow the directions below: In the Tools menu, select the Configure Platform Manager sub-menu item as shown below.
  • Page 76 In the Windows CE Platform Manager Configuration dialog, select EDAS_CE10 (Default Device) and click the Properties button. FIGURE 3.2 Platform Manager Configuration dialog In the Device Properties dialog, select TCP/IP Transport for Windows CE and click the Configure button. FIGURE 3.2 Configuring TCP/IP Transport Developing Custom Programs 70...
  • Page 77 Fixed Port checkbox. In the Port Number field, enter a value of 5000 for the port number, or use the port number set in the debugworkstations file on the EDAS CE unit. Click the OK button. Note: On Windows XP machines port 5000 is typically is use, thus you must use a different port number.
  • Page 78 In the Device Properties dialog, click the Advanced button. In the next Device Properties dialog, select Manual Server and click the OK button. FIGURE 3.2 Device Properties dialog Developing Custom Programs 72...
  • Page 79 In the Device Properties dialog, click the Test button. FIGURE 3.2 Device Properties Dialog In the Manual Server - Action dialog, click the OK button. FIGURE 3.2 Manual Server - Action dialog Developing Custom Programs 73...
  • Page 80 The development computer attempts to establish a connection with the EDAS CE unit as shown below. FIGURE 3.2 Establishing a Platform Manager Connection As soon as the connection to the device is established, the text in the dialog displays a confirmation message as shown below. Click the OK button to close the dialog FIGURE 3.2 Confirming the Device Connection...

  • Page 81: Writing Custom Programs

    This is the recommended procedure for beginning a new programming project for the EDAS CE, as it simplifies the task. To set up a new project for the EDAS CE, start eMbedded Visual C++ and follow the steps below: In the File menu, select New.
  • Page 82 Click the OK button. FIGURE 3.1 Using eVC Wizard to generate a new program Developing Custom Programs 76...
  • Page 83 In the WCE Application - Step 1 of 1 dialog, select A simple Windows CE application, and click the Finish button. FIGURE 3.2 WCE Application dialog The New Project Information dialog displays the settings that you made in the previous dialogs. Click the OK button to continue FIGURE 3.2 New Project Information dialog Developing Custom Programs 77...
  • Page 84 Once the project is created, eMbedded Visual Tools opens the project and displays the ClassView, ResourceView, and FileView tabbed dialogs in the project window. 10. From the Project menus, select Settings... FIGURE 3.2 Project Settings 11. In the Projects Settings dialog, change the Settings For drop down to All Configurations.
  • Page 85 FIGURE 3.2 Project Setting (Link tab) dialog 14. Next select the Debug tab. 15. In the Download directory field, enter the folder on the EDAS CE where you want eVT to download this application. The default Download directory is "\", the root folder of the EDAS CE’s file system.
  • Page 86 16. Press the OK button. FIGURE 3.2 Project Settings (Debug tab) dialog 17. Select the FileView tabbed dialog. 18. Expand the Source Files tree and double clicking on your main .cpp program. FIGURE 3.2 Open the main program 19. In the Select Active Configuration drop-down list, select Win32 (WCE x86) Debug.
  • Page 87 20. In the Select Default Device drop-down list, select EDAS_CE10 (Default Device). FIGURE 3.2 eMbedded Visual C++ Sample Program 21. In the eMbedded Visual Tools window, select the Build menu item and select Rebuild All. FIGURE 3.2 Rebuilding the Program 22.

  • Page 88: Sample Programs

    Manual Server - Action dialog will open, simply press the OK button. FIGURE 3.2 Connection Confirmation Message 23. The first time an application is executed on the EDAS CE you will get the Find Local Module dialog as shown below.

  • Page 89: Loading Custom Programs

    You can use the Tools menu in eMbedded Visual Tools to transfer files using the Remote File Viewer. To transfer files to the EDAS CE unit with the eMbedded Visual Tools: In the Tools menu, select the Remote File Viewer item. The Windows CE Remote File Viewer dialog opens.

  • Page 90: Chapter 4:Ce Link Api For Edas Ce

    API functions. Interfacing to the I/O system 1.1.59 For a program on the EDAS CE to interface with the I/O modules it must implement the following sequence: Initialize the hardware and software. Initialization is done with a single call to the function nsHWInit().

  • Page 91: Function Calls

    Warnings indicate that the API function executed, but that there may be problems you should be aware of. An explanation of the error and warning return values can be found in the list of error codes CE Link API for EDAS CE 85...
  • Page 92 4.3 Return Error Codes for CE Link and EDAS CE API Functions. Most debugging of non-functional CE Link applications consists of tracking down where an error is occurring. To simplify this process, check the return values from all CE Link calls, writing a debug string or otherwise recording the failure.
  • Page 93 For example, the nsAIConfigureData structure is defined as: typedef struct nsAIConfigureData unsigned short count; nsAIList list[2]; }nsAIConfigureData; CE Link API for EDAS CE 87...
  • Page 94 I/O operation. o Failing to allow for the size of the actual array elements. You can use the sizeof operator to specify the number of bytes of data to allocate. CE Link API for EDAS CE 88...

  • Page 95: Header Files

    Other DLLs, such as anlg_inE.dll and dig_ioE.dll, provide specific hardware capabilities for individual module types. The DLLs for CE Link are pre-loaded on the EDAS CE as shipped from the The edasapiE.dll, along with I/O specific DLLs (anlg_inE.dll, factory.

  • Page 96: Registry Entries On The Edas Ce

    Registry Entries on the EDAS CE 1.1.63 The registry on the EDAS CE contains several entries associated with CE Link. The EDASpath entry specifies the location of the CE Link DLLs for the various modules that might be attached to the system. If this entry is missing or empty, the directory where the edasapiE.dll file is located is...

  • Page 97: Ce Link Api Function Descriptions

    Zero value: Indicates the function completed successfully. Non-zero value: Indicates failure. STARTUP_ERR (-5) nsSWDeinit() was called before nsHWInit(). SED_MOD_FAIL_ERR (-6) Module failure. Contact the factory. SED_GEOG_FAIL_ERR (-7) Module mapping failure. Contact the factory. CE Link API for EDAS CE 91...
  • Page 98 Specifies pointer to return information from the call. The nsOpenSessionReturn structure contains a single field, owner, whose value is to be passed to all subsequent CE Link calls. Return Value Error Codes Zero value: Indicates the function completed successfully. Non-zero value: Indicates failure. CE Link API for EDAS CE 92...

  • Page 99: Unpaced Analog Input Calls

    Indicates the function completed successfully. Non-zero value: Indicates failure. Unpaced Analog Input Calls 1.1.65 Analog input functions in CE Link are accomplished through two types of data acquisition, paced and unpaced. Paced acquisitions are performed CE Link API for EDAS CE 93...
  • Page 100 Indicates the session making the call. Pass the value returned by the call to nsOpenSession(). data Specifies an nsAIConfigureData input structure, described below. This parameter is reserved and should be set to NULL (0). CE Link API for EDAS CE 94...
  • Page 101 Example long err; int count = 16; nsAIConfigureData *cf; err = i3malloc(sizeof(short) + count*sizeof(nsAIList),(void **)&cf); cf->count = count; for(i = 0; i < count; i++) cf->list[i].module =1; cf->list[i].channel = i; cf->list[i].gain = 1; CE Link API for EDAS CE 95...
  • Page 102 Supported gains are 1, 10, and 100. o Supported ranges are BIPOLAR_20 ( , UNIPOLAR_10 (0-10 V) and ± 10 V) ZEROto20ma (0-20 mA). When using ZEROto20ma range, differential mode may not be selected. CE Link API for EDAS CE 96...
  • Page 103 Parameters caller Indicates the session making the call. Pass the value returned by the call to nsOpenSession(). data Specifies an nsAIReadData input structure, described below. Specifies an nsAIReadDataReturn returned data structure, described below. CE Link API for EDAS CE 97...
  • Page 104 If the data pointer is not declared as unsigned short, when CE Link API for EDAS CE 98...
  • Page 105 = 100; // 100 samples from the channel. dat.module = 1; dat.channel = 0; dat.count = count; // Read count samples from the channel. dat.tflag = 1; // Read timestamp information for each sample. CE Link API for EDAS CE 99...

  • Page 106: Paced Analog Input Calls

    However, the demand this places on system resources will limit the rate at which the acquisitions can be run, as will other tasks being performed during the acquisition, including other applications which may be running. CE Link API for EDAS CE 100...
  • Page 107 } nsAIHSConfigureData; typedef struct nsAIList unsigned short module; unsigned short channel; unsigned short gain; unsigned short range; unsigned short diff; CE Link API for EDAS CE 101...
  • Page 108 Parameters caller Indicates the session making the call. Pass the value returned by the call to nsOpenSession(). data Specifies the nsAIHSConfigureData input structure, described below. Specifies the nsAIHSConfigureReturn returned data structure, described below. CE Link API for EDAS CE 102...
  • Page 109 Differential mode flag. A value of 1 specifies differential mode; 0 specifies single-ended mode. Values must be the same for all entries in the channel list. zero: Auto-zero correction. Must specify BF_NO_ZERO. CE Link API for EDAS CE 103...
  • Page 110 Function call in C++ long nsAIHSEnable(unsigned int caller, nsAIHSEnableData *data, void *res); typedef struct nsAIHSEnableData short handle; short enable; unsigned long count; unsigned long delay; short clustersize; short free; } nsAIHSEnableData; CE Link API for EDAS CE 104...
  • Page 111 The nsAIHSRead() function returns to the application program the paced analog input data which has been acquired using the nsAIHSEnable() function. Function call in C++ long nsAIHSRead(unsigned int caller, nsAIHSReadData *data, nsAIHSReadReturn *ret); typedef CE Link API for EDAS CE 105...
  • Page 112 DMAword; unsigned long DMAaddr; unsigned long command; short unlatchedwrap; char reserved[132]; } BufInfo; CE Link API for EDAS CE 106...
  • Page 113 Pointer to a data buffer where the process data will be returned to the calling program. The calling program must allocate this data space. The buffer must be at least samples * clustersize bytes long. CE Link API for EDAS CE 107...
  • Page 114 The next cluster to be read, if nsAIHSRead() is called with offset equal to -1. triggercluster: Cluster number (from the beginning of the buffer) corresponding to the occurrence of the trigger, if any. nextcluster: Reserved DMAword: Reserved. DMAaddr: Reserved. command: Reserved. unlatchedwrap: Reserved. CE Link API for EDAS CE 108...
  • Page 115 If you begin to read the data during the data acquisition and the acquired data subsequently wraps around and overwrites past the last data you read back, the status bit HS_BUFFER_WRAPPED will be set. CE Link API for EDAS CE 109...
  • Page 116 Flags indicating the status of the high-speed acquisition. Status bits that may be returned are described with nsAIHSRead() function. Return Value Error Codes Zero value: Indicates the function completed successfully. Non-zero value: Indicates failure. CE Link API for EDAS CE 110...

  • Page 117: Analog Output

    (unsigned int caller, nsAOConfigureData *data, void *res); typedef struct nsAOConfigureData unsigned short count; nsAOList list[2]; } nsAOConfigureData; typedef struct nsAOList unsigned short module; unsigned short channel; unsigned short range; } nsAOList; CE Link API for EDAS CE 111...
  • Page 118 The nsAOWrite() function reads a previously-configured analog output channel. Prior to making this function call, configure the channel using the nsAOConfigureList() call. Function call in C++ nsAOWrite (unsigned int caller, nsAOWriteData *data, void *res); typedef struct nsAOWriteData unsigned short module; CE Link API for EDAS CE 112...

  • Page 119: Digital Input And Output (Port Or Byte)

    (up to 8) in a port. Port operations are limited to reading or writing the current state, 0 or 1, of each of the channels in a port, while individual channel operations can perform other operations, CE Link API for EDAS CE 113...
  • Page 120 Indicates the session making the call. Pass the value returned by the call to nsOpenSession(). data Specifies an nsDIOConfigureData input structure, described below. This parameter is reserved and should be set to NULL (0). CE Link API for EDAS CE 114...
  • Page 121 The module supports two ports, both configured in hardware as outputs. o Port 0 has 8 bits and port 1 has 4 bits. o The configuration function may be called but is not required. CE Link API for EDAS CE 115...
  • Page 122 Pointer to the memory block allocated by the function to contain the returned data. When the data and ft pointers are no longer needed, the caller must use the i3free() function to free the data buffer allocated by this call. CE Link API for EDAS CE 116...
  • Page 123 EDAS-2005M, EDAS-2010M, EDAS-2011M o These output modules have ports that can be read back. The function will return the current output data. o The module supports two ports, both configured in hardware as outputs. CE Link API for EDAS CE 117...
  • Page 124 If ALL_MODULES_S is specified, the same data will be written to all If ALL_PORTS_S is specified, the function will modules in the system. expect enough data for all ports on the module, even if some ports are CE Link API for EDAS CE 118...

  • Page 125: Digital Input And Output (Individual Bit)

    I/O channels to be used in bit-wide operational modes. Several channels can be configured with one call to the function. Function Call in C++ long nsDIOBITConfigureList (unsigned int caller, nsDIOBITConfigureData *data, void *res); typedef CE Link API for EDAS CE 119...
  • Page 126 Indicates the session making the call. Pass the value returned by the call to nsOpenSession(). data Specifies an nsDIOBITConfigureData input structure, described below. This parameter is reserved and should be set to NULL (0). CE Link API for EDAS CE 120...
  • Page 127 - 1). DIOBIT_INPUT_COUNT_EVENT. This mode works very similarly to the DIOBIT_INPUT_COUNT_UP mode, but is capable of counting much higher-speed transitions on the input. Before it can begin counting, it must be enabled by calling CE Link API for EDAS CE 121...
  • Page 128 Pulse Low and Delay Low are initially high, Pulse High and Delay High are initially low. Return Value Error Codes Zero value: Indicates the function completed successfully. Non-zero value: Indicates failure. Hardware Specifics EDAS-2002M o Port 0 is the input port on the module. CE Link API for EDAS CE 122...
  • Page 129 Indicates the session making the call. Pass the value returned by the call to nsOpenSession(). data Specifies an nsDIOBITEnableData input structure, described below. This parameter is reserved and should be set to NULL (0). CE Link API for EDAS CE 123...
  • Page 130 The latch modes are: DIOBIT_INPUT_LATCH_LOW DIOBIT_INPUT_LATCH_HIGH DIOBIT_INPUT_LATCH_STATE_CHANGE For counter input modes, the enable state of the channel determines whether incoming events are counted or ignored. The counter input modes are: DIOBIT_INPUT_COUNT_UP DIOBIT_INPUT_COUNT_DOWN DIOBIT_INPUT_COUNT_EVENT CE Link API for EDAS CE 124...
  • Page 131 Function Call in C++ long nsDIOBITRead(unsigned int caller, nsDIOBITReadData *data, nsDIOBITReadReturn *ret); typedef struct nsDIOBITReadData unsigned short module; unsigned short port; unsigned short portbit; short reset; short tflag; } nsDIOBITReadData; typedef struct nsDIOBITReadReturn unsigned long length; CE Link API for EDAS CE 125...
  • Page 132 Optional timestamp data, returned as the system time in FILETIME format. Return Value Error Codes Zero value: Indicates the function completed successfully. Non-zero value: Indicates failure. CE Link API for EDAS CE 126...
  • Page 133 Indicates the session making the call. Pass the value returned by the call to nsOpenSession(). data Specifies an nsDIOBITWriteData input structure, described below. This parameter is reserved and should be set to NULL (0). CE Link API for EDAS CE 127...
  • Page 134 // Set up the module, port number, and portbit. data->module = 0; data->port = 0; data->portbit = ALL_PORT_BITS; // Fill the data array for all eight bits. data->data[0] = 0; data->data[1] = 1; CE Link API for EDAS CE 128...

  • Page 135: Rate Generator Functions

    Rate generators may be used to provide a timing base for paced analog acquisitions. Function Call in C++ long nsRGConfigure (unsigned caller, nsRGConfigureData *data, void *res); typedef struct nsRGConfigureData unsigned short module; unsigned short channel; unsigned long data; } nsRGConfigureData; CE Link API for EDAS CE 129...
  • Page 136 For other applications you will not need to enable/disable the Rate Generator directly. Function Call in C++ long nsRGEnable (unsigned caller, nsRGEnableData *data, void *res); typedef struct nsRGEnableData unsigned short module; unsigned short channel; unsigned short enable; CE Link API for EDAS CE 130...

  • Page 137: Quadrature Functions

    The channel’s mode, as well as the functions of the associated digital input and output bits, is set through this function call. Function Call in C++ long nsQUADConfigure (unsigned int caller, nsQUADConfigureData *data, void *res); typedef struct nsQUADConfigureData } USHORT module; USHORT channel; CE Link API for EDAS CE 131...
  • Page 138 DIOBIT_INPUT_LATCH_CONTROL – Latch control. When the input goes high, the count value will be latched into the internal latch registers. DIOBIT_INPUT_ENABLE_CONTROL – Enable control. When selected, the counter will CE Link API for EDAS CE 132...
  • Page 139 The digital output bit mode for output bit 0 on the channel. The field can have the same values as output0mode, above. output1InitialState: For general-purpose output mode, the initial state of the output is set by nsQUADConfigure() to this value, 0 for low, 1 for high. CE Link API for EDAS CE 133...
  • Page 140 }nsQUADEnableData; Parameters caller Indicates the session making the call. Pass the value returned by the call to nsOpenSession(). data Specifies an nsQUADEnableData input structure, described below. CE Link API for EDAS CE 134...
  • Page 141 (unsigned int caller, nsQUADReadData *data, nsQUADReadReturn *ret); typedef struct nsQUADReadData { unsigned short module; unsigned short channel; short reset; short tflag; } nsQUADReadData; typedef struct nsQUADReadReturn unsigned long length; unsigned long *data; unsigned long *status; FILETIME *ft; CE Link API for EDAS CE 135...
  • Page 142 The status return array contains one status value for each channel read by the function. The status value is a 32-bit value consisting of 32 ‘flags’ which are defined by the following constants: CE Link API for EDAS CE 136...
  • Page 143 This function configures the interrupt functionality of a quadrature/counter channel. Channels can generate interrupts on the occurrence of a variety of events, including comparison events. Being able to capture such events in an interrupt handler can allow you to CE Link API for EDAS CE 137...
  • Page 144 Values for this mask include: QUAD_INTR_PRELOAD – interrupt generated when the preload hardware signal, CE Link API for EDAS CE 138...
  • Page 145 The value of the callbackParam passed when the interrupt was configured through nsQUADInterrupt(). chn: This parameter is for internal use only. Do not change it or the memory to which it points. CE Link API for EDAS CE 139...

  • Page 146: Alarm Functions

    I/O operation that occurs on another channel on the EDAS device, such as a momentary output on a digital output bit. Additionally, the event may be logged directly to the EDAS CE, or by transmitting data to another device. This section describes the functions used to configure and control alarms in CE Link.
  • Page 147 } nsALARMType; typedef struct nsALARMConfigureData unsigned short type; unsigned short mode; nsALARMType input; nsALARMType output; } nsALARMConfigureData; typedef struct nsALARMConfigureReturn unsigned short alarm; CE Link API for EDAS CE 141...
  • Page 148 Parameters caller Indicates the session making the call. Pass the value returned by the call to nsOpenSession(). data Specifies an nsALARMConfigureData input structure, described below. Specifies an nsALARMConfigureReturn returned data structure, described below. CE Link API for EDAS CE 142...
  • Page 149 Digital input bit terminal count: data1 is the terminal count value. Digital output bit: data1 is the value to be output (1 or 0). Digital output byte: data1 is the value to be output to the port. CE Link API for EDAS CE 143...
  • Page 150 Indicates the session making the call. Pass the value returned by the call to nsOpenSession(). data: Specifies an nsALARMEnableData input structure, described below. res: This parameter is reserved and should be set to NULL (0). CE Link API for EDAS CE 144...
  • Page 151 Parameters caller Indicates the session making the call. Pass the value returned by the call to nsOpenSession(). data Specifies an nsALARMStatusData input structure, described below. Specifies an nsALARMStatusReturn returned data structure, described below. CE Link API for EDAS CE 145...
  • Page 152 *data, void *res, void *fcn); typedef struct nsALARMTransferData unsigned short alarm; char remote[80]; unsigned short xfermode; unsigned short xferport; unsigned short xferdata; unsigned short nbytes; char message[1]; } nsALARMTransferData; CE Link API for EDAS CE 146...
  • Page 153 Specifies an nsALARMTransferData input structure. This parameter is reserved and should be set to NULL (0). Pointer to a network data transfer function if network transfer is desired. Sample code is provided. CE Link API for EDAS CE 147...
  • Page 154 The time is Universal Time. nbytes: This is the length of string message (not including terminating NULL). Indicates the number of bytes of explicit data (a string, for example), contained in the message field, CE Link API for EDAS CE 148...
  • Page 155 If the data options are specified, a large amount of data may be transferred, depending on the system configuration. You may want to define a structure based on your EDAS CE system configuration to aid in interpreting the data. Digital bit data will be allocated for all digital I/O channels that can be configured as bits.
  • Page 156 This parameter is reserved and should be set to NULL (0). Fields nsAlarmFreeData: alarm Identifies the alarm that is being freed. Return Value Error Codes Zero value: Indicates the function completed successfully. Non-zero value: Indicates failure. CE Link API for EDAS CE 150...

  • Page 157: System And Utility Functions

    4.2.1.31 Obtaining System Information The nsSYSInquire() function returns information about the EDAS CE system including the ID, which identifies the type of the unit. Function Call in C++ long nsSYSInquire(void *res, nsSYSInfoReturn *info);...
  • Page 158 PICver; unsigned short moduleID[16]; unsigned long moduleVER[16]; FILETIME systime; char reserved[16]; } nsVERInfoReturn; Parameters This parameter is reserved and should be set to NULL (0). info Specifies an nsVERInfoReturn structure, described below. CE Link API for EDAS CE 152...
  • Page 159 Fields nsVERInfoReturn: EXECver: ROM version (EDAS) or software version (EDAS CE) PICver: PIC version (EDAS) moduleID[16]: Returns module ID information for all installed I/O modules. Module positions which are unoccupied will contain hex values of 0xffff. moduleVER[16]: Module returns version information to the caller.
  • Page 160 If the call specified multiple channels and/or ports to be locked or unlocked, the change in lock status for some channels might have been successful. CE Link API for EDAS CE 154...

  • Page 161: System Calibration

    (unsigned int caller, nsEEReadData *data, nsEEReadReturn *ret); typedef struct nsEEReadData unsigned short module; unsigned short count; unsigned short address; } nsEEReadData; typedef struct nsEEReadReturn unsigned short length; unsigned short *data; } nsEEReadReturn; CE Link API for EDAS CE 155...
  • Page 162 4.2.1.35 Writing Calibration Data The nsEEWrite() function writes calibration data stored in the EE. address range is 0 through 31. Function Call in C++ long nsEEWrite (unsigned int caller, nsEEWriteData *data, void *res); typedef CE Link API for EDAS CE 156...
  • Page 163 Data array to be written to the module. Be sure to allocate enough memory for the number of values to be written. Return Value Error Codes Zero value: Indicates the function completed successfully. Non-zero value: Indicates failure. CE Link API for EDAS CE 157...
  • Page 164 Function Call in C++ long nsDACWrite (unsigned int caller, nsDACWriteData *data, void *res); typedef struct nsDACWriteData unsigned short module; unsigned short count; unsigned short address; unsigned short data[2]; } nsDACWriteData; CE Link API for EDAS CE 158...

  • Page 165: Memory Management

    In order to insure that the memory is returned to the heap from which it was allocated, the memory free utility should be called. The memory allocation utility used internally in the CE Link CE Link API for EDAS CE 159...
  • Page 166 (usually the data array), need be freed. Function Call in C++ long i3free (void *pntr) Parameters pntr Pointer to the memory block to free. The block must have been allocated using the function i3malloc(). Return Value Error Codes CE Link API for EDAS CE 160...
  • Page 167 Indicates the function completed successfully. Non-zero value: Indicates failure. Failure is most likely due to trying to free a pointer that does not point to the beginning of a memory block allocated by i3malloc(). CE Link API for EDAS CE 161...

  • Page 168: Return Error Codes For Ce Link And Edas Ce Api Functions

    4.3 Return Error Codes for CE Link and EDAS CE API Functions This section contains the error codes and their descriptions for the CE Link API functions and by the Net Link API functions. No Errors: Function Successfully Completed NO_EDAS_ERROR: The function completed successfully without any errors.
  • Page 169 SED_INT_FUNCTION_ERR: This is an internal error. A software module does not support an expected API function. SED_MOD_CHANNEL_ERR: This is an EDAS CE channel lookup failure. The module and channel number specified do not exist. SED_MOD_FUNCTION_ERR: This is an EDAS CE function lookup failure.
  • Page 170 WIN_FILE_OPEN_ERR: This is a Windows file open error in Net Link. This error might occur if the drivers do not find a thermocouple table. WIN_FILE_CLOSE_ERR: This is a Windows file close error in Net Link. CE Link API for EDAS CE 164...
  • Page 171 UNIX_FILE_CLOSE_ERR: This is a UNIX file close error in Net Link. UNIX_FILE_READ_ERR: This is a UNIX file read error in Net Link. SED_FILE_ERR: Indicates an EDAS CE error opening a DLL module file or an input or output data file.
  • Page 172 -800 LISTEN_PENDING_WARN: The current listen command is still pending (i.e. the EDAS CE NetLink server is still waiting for a client to call). You must wait for the current listen command to complete before listening again on the same socket.
  • Page 173 AI_ZEROCHANNEL_ERR: This is an illegal auto-zero reference channel. 2015 AI_DATA_LENGTH_ERR: Unexpected returned data length, from old- style Net Link call to EDAS CE. Use new-style calls for multiple modules. 2503 AI_INDEX_ERR: An EDAS CE EE or DAC number error. Analog Input Warning Error Codes: -2000 to -2999...
  • Page 174 7010 DIO_OUTPUT_ONLY_ERR: The specified digital I/O port can only be configured for output. 7012 DIO_DATA_LENGTH_ERR: For the EDAS CE API: Unexpected returned data length, from an old-style call. Use new-style functions for multiple modules. 7013 DIO_STATUS_ERR: For EDAS CE: In-progress bit error (hardware error).
  • Page 175 HS_NOT_CONFIGURED_ERR: The specified paced data acquisition process has not been successfully configured. 14003 HS_START_MODE_ERR: The specified paced data acquisition start mode is invalid. 14006 HS_STOP_MODE_ERR: The specified paced data acquisition stop mode is invalid. CE Link API for EDAS CE 169...
  • Page 176 14017 HS_NO_HANDLE_ERR: There are no more paced data acquisition handles available. 14018 HS_SED_INTERNAL_ERR: This is an EDAS CE paced data acquisition function lookup failure. Contact the factory. 14019 HS_OWNER_ERR: A paced data acquisition using this module has already been configured by another user.
  • Page 177 Error in converting the timestamp data to string date and time. This error occurs in time conversion. 19002 Error in converting the timestamp data to string date and time. This error occurs in date conversion. CE Link API for EDAS CE 171...
  • Page 178 Exception Error Codes: 22000 to 22999 These error codes indicate that an exception occurred in the Net Link command processor (suprcatE.exe) on the EDAS CE. Exceptions are not handled for CE Link applications: you must provide your own exception handling.
  • Page 179 EXCEPTION_STACK_OVERFLOW: The thread used up its stack. Winsock Error Codes: 28000 to 30000 These error codes indicate that a network error occurred in the Net Link command processor (suprcatE.exe) on the EDAS CE. 28004 WSAEINTR: A blocking operation was interrupted by a call to WSACancelBlockingCall().
  • Page 180 WSAEISCONN: A connect request was made on an already connected socket. 28057 WSAENOTCONN: A request to send or receive data was disallowed because the socket is not connected. An address was not supplied when sending on a datagram socket using sendto(). CE Link API for EDAS CE 174...
  • Page 181 WSAECANCELLED: A call to WSALookupServiceEnd was made while this call was still processing. The call has been canceled. 28104 WSAEINVALIDPROCTABLE: The procedure call table is invalid. 28105 WSAEINVALIDPROVIDER: The requested service provider is invalid. CE Link API for EDAS CE 175...
  • Page 182 WSA_QOS_BAD_STYLE: Unknown or conflicting style. 29013 WSA_QOS_BAD_OBJECT: A problem occurred with part of the filterspec or provider specific buffer. 29014 WSA_QOS_TRAFFIC_CTRL_ERROR: Problem with part of the flowspec occurred. 29015 WSA_QOS_GENERIC_ERROR: A general QOS error occurred. CE Link API for EDAS CE 176...
  • Page 183 This page intentionally left blank. CE Link API for EDAS CE 177...

  • Page 184: Index

    147 gain, range, and mode, 90, 97 CE Link paced acquisition buffer organization, debugging applications, 82 DLLs on the EDAS CE, 85 paced acquisition handle, 98 examples paced analog acquisition, 95 see CE Link API examples, 86 pacer, 97...
  • Page 185 counter input data organization, 130 locking I/O channels, 145 enabling and disabling, 128 memory allocation, 152 reading channels, 129 memory de-allocation, 152 date and time stamping, 83 memory management, 152 digital I/O, 107 programming the calibration system, input/output flag, 109 output port data organization, 113 reading calibration data, 147 port configuration, 108...
  • Page 186 37 flow control (serial) reading, 41 reading, 41 reconfiguring, 42 reconfiguring, 43 downloading files folders configuring EDAS CE unit, 65 protected in remote manager, 53 DRAM, 4 gateway address EDAS CE SDK, 63 configuring, 37 installation, 64 reading, 41...
  • Page 187 85 module ID, 145 portbit masks, 113 unit ID, 86, 144 power connector, 7 installation power supply, 6 EDAS CE SDK, 64 specifications, 7 Microsoft eMbedded Visual Tools, 64 process list, 42 IP address program files alarm transfer destination, 141...
  • Page 188 Telnet session, 44 Telnet, 39 sample programs, 79 thermocouple input configuration, 12 saving registry settings, 62 time stamping, 83, 145 SDK for EDAS CE, 63 time synchronization, 59 installation, 64 time zone uninstalling, 65 reading, 41 security...
  • Page 189 reconfiguring, 43 writing custom programs, 72 Index 183...

Table of Contents