ADCON T E L E M E T R Y Base Station Telemetry Gateway A840 and Wireless Modem A440 User Guide valid for A840 firmware release 3.8.
ADCON TELEMETRY GMBH I N K U S T R A S S E 2 4 A-3400 KLOSTERNEUBURG A U S T R I A TEL: +43|2243|38280-0 FAX: +43|2243|38280-6 http://www.adcon.at ADCON INTERNATIONAL INC 2050 LYNDELL TERRACE S U I T E 1 2 0 CA-95616 DAVIS, USA TEL: +1|530|7531458 FAX: +1|530|7531054 http://www.adcon.at Proprietary Notice: The Adcon logo, the A720 and A730 series, addIT™, addWAVE™, the A840 series and Telemetry Gateway, addVANTAGE®, and addVANTAGE Lite are trademarks or registered trademarks of Adcon Telemetry.
Table of Contents Chapter 1. Introduction ________________________________ 9 Conventions __________________________________________ 11 Chapter 2.
Configuring your Telemetry Network _______________ 31 Configure GPRS usage ______________________________ 34 Firmware and Routers ____________________________ 34 Configure the A840 for use with GPRS RTU’s ________ 34 Administering your Telemetry Network ________________ 35 Editing the Base Station’s Properties________________ 35 Adding New RTUs _______________________________ 38 Editing Properties of Existing RTUs _________________ 41 Deleting an RTU _________________________________ 42 Connecting Sensor
REPLACE _______________________________________ DELETE ________________________________________ ROUTE _________________________________________ MASTER________________________________________ ACTIVE_________________________________________ EXTEND________________________________________ POLLCONF _____________________________________ DEV____________________________________________ NPND__________________________________________ NTF____________________________________________ SENDNTF _________________________
REQUEST _______________________________________ 83 RSETIO _________________________________________ 84 PORT___________________________________________ 85 ANALOG _______________________________________ 85 B ______________________________________________ 86 RB _____________________________________________ 86 RBLIST__________________________________________ 86 RSET ___________________________________________ 87 XCONF _________________________________________ 87 XDATA ________________________________________
CHAPTER hermit 1.2 - ARM bootloader_____________________ linux 2.4 - Operating system kernel _______________ glibc 2.1.
CHAPTER
Chapter 1. Introduction This manual describes the use of the A840 Telemetry Gateway and A440 Wireless Modem combination. Due to their general nature, either unit can also be used independently, but such uses are beyond the scope of this manual. The manual teaches you how to use the telemetry gateway and the wireless modem as a base station for an Adcon wireless network.
CHAPTER 1 Introduction bit processor running the Linux operating system. It has 16-MB Flash EPROM acting as a hard disk and 16 MB RAM. The software can be upgraded in the field. Several interfaces are available: Ethernet, V34 modem, RS-232 serial, and RS-485 multidrop serial. A built-in rechargeable battery provides the telemetry gateway with approximately 24 hours of operation without mains power (the number of hours depends on the number of RTUs the gateway has to poll).
CHAPTER 1 Conventions Conventions Certain conventions apply in this documentation. Italics Indicate the text is variable and must be substituted for something specific, as indicated in the explanation. Italics can also be used to emphasize words as words or letters as letters. Bold Indicates special emphasis of the text. Also indicates menu names and items in a window. fixed font Indicates characters you must type or system messages. File Indicates menu selection.
CHAPTER 1 Introduction
Chapter 2. System Setup Package Contents Before proceeding to the installation of your base station, first verify that you received all of the following components: • the A840 Telemetry Gateway • the A440 Wireless Modem • the 30 m (100 ft) connection cable between the A840 and the A440 device • a power cord • a twisted-pair standard Ethernet cable • a serial null modem cable • a whip antenna If any of the above items is missing, contact your dealer.
CHAPTER 2 System Setup Installation The base station has two main components: an indoor unit (the A840) and an outdoor unit (the A440). Before proceeding with the installation, take a moment to plan your network. First, it is essential to realize the importance of selecting a good location for the base station.
CHAPTER 2 Installation sight” distance an addIT can communicate is 800 m (approximately half a mile). This is valid if the partner device is mounted on a 3 m mast (9 ft) and the addIT is mounted on a 30 cm mast (1 ft). The above figures are estimates based on a great deal of experience with installing this kind of equipment and assume a typical height of 3 m (9 ft) for the antennas of the remote measuring stations.
CHAPTER 2 System Setup • Install the indoor unit. • Initialize the base station. Installing the Outdoor Unit Install the outdoor unit on the rooftop of the house where the base station will be located or on top of a nearby mast. After unpacking the components of the base station, identify the device marked “Wireless Modem A440.” This unit has two connectors: one for a whip antenna (also supplied in the package) and a second that accommodates the 30 m (100 ft) connection cable to the indoor unit.
CHAPTER 2 Installation 2. Fasten the antenna to the wireless modem. 3. Plug the proper end of the communication cable into the lower connector of the wireless modem. 4. Secure the mast in its place on the roof. 5. Run the cable to the indoor unit. Note: The cable supplied to connect the outdoor unit to the A840 Telemetry Gateway is 30 m long and cannot be extended. Extending the cable will make your wireless modem inoperable due to the voltage loss on the additional cable length.
CHAPTER 2 System Setup will need to provide your own “crossover” Ethernet cable, which you can find in most computer stores. If you plan to use the base station as a standalone unit (that is, without a computer), you need a telephone line that must be connected to the modem jack of the A840 gateway. Note: Before you operate the base station, Adcon strongly recommends that you charge the internal battery to a level where it can sustain the operation of the gateway.
CHAPTER 2 Installation A730SD Replacement with addVANTAGE 4 Pro Because the addVANTAGE 4 Pro software communicates only via a TCP/IP network, you must first make sure that the networking is enabled and configured on the gateway. By default the gateways are delivered with the networking enabled, so you should be able to skip this section entirely and go to “Configuring the Gateway Using the Configurator” on page 22.
CHAPTER 2 System Setup Network active : no IP-address : 192.168.1.2 Netmask : 255.255.255.0 Gateway : 192.168.1.1 Hostname.Domain : a840 Nameserver IP(s) : 192.168.1.2 Timeservername or IP: Name/IP-Address from outside a NATing router : none Port number of web-server from outside a NATing router : none DHCP server running : no (C)hange/(S)ave/(D)hcp/(Q)uit configuration? [c/s/d/Q] 6. The above configuration shows that the network is not enabled.
CHAPTER 2 Installation Hostname.Domain : my840.domain.com Nameserver IP(s) : 221.38.15.62 Timeservername or IP: Name/IP-Address from outside a NATing router : none Port number of web-server from outside a NATing router : none DHCP server running : no Unsaved changes pending! (C)hange/(S)ave/(D)hcp/(Q)uit configuration? [c/s/d/Q] Type s to save your changes or q to quit the configuration. Note that if you type q, you will be asked if you want to keep the changes and the default answer is Yes.
CHAPTER 2 System Setup Nameserver IP(s) : 192.168.1.2 Timeservername or IP: Name/IP-Address from outside a NATing router : none Port number of web-server from outside a NATing router : none DHCP server running : no (will be started) Unsaved changes pending! (C)hange/(S)ave/(D)hcp/(Q)uit configuration? [c/s/d/Q] Now type s to update the gateway with the displayed parameter information. You might need to configure your PC’s network parameters, but you will have to refer to your PC user guide to do so.
CHAPTER 2 Installation 5. Configure your telemetry network. 6. Configure the modem if your network includes A733GSM/ GPRS RTUs. In order to start and use the Configurator, make sure that your PC and the gateway are connected either directly via a crossover network cable, or via a hub or switch in a LAN.
CHAPTER 2 System Setup Figure 3. Configurator’s Login Window 6. If the login was successful, the Configurator software starts up and by default shows you the actual configuration of your telemetry network: the root device, that is, the gateway itself (the base station), the RTUs (the devices), and their sensors (tags). The Configurator’s graphical user interface (GUI) displays something similar to Figure 4. Figure 4.
CHAPTER 2 Installation 7. Select the TCP/IP tab. Note that all of the IP parameters are displayed, as shown in Figure 5. Click the Distribute IP addresses checkbox to disable this feature for now. Figure 5. TCP/IP Parameters 8. Click Update to confirm the disabling of the automatic IP address distribution. After a short delay, the Update button turns gray, signifying that the operation was successful. 9.
CHAPTER 2 System Setup 1. Select the Date/Time tab to display the window shown in Figure 6. Figure 6. Configure the Date and Time 2. From the Time zone combo box, select your local time zone. Selecting the proper time zone is important for such things as automatically switching to and from Daylight Saving Time. 3.
CHAPTER 2 Installation Figure 7. Configure a Time Server 4. After everything is properly configured, click Update to save the changes. Changing Passwords Your A840 Telemetry Gateway has two accounts: the root (administrator) account and the adv (addVANTAGE user) account. Both accounts have default passwords. You should change these passwords, especially for the root account, if your gateway is connected permanently to the Internet.
CHAPTER 2 System Setup Figure 8. Changing Passwords 3. Type the new password in the edit box, confirm it by typing it again, and then click OK to dismiss the pop-up. 4. Click Update to save the changes in the gateway. You can also change passwords in a terminal session. See “Changing Passwords” on page 55 to do so. Configuring the Modems Your gateway contains a built-in modem. This modem can be used either for dial-in access (the “dumb server” functionality) by an application software e.g.
CHAPTER 2 Installation To configure the modem parameters, click the Modem tab, and then select from the combo box the modem you want to configure. Following is a description of all configurable parameters and their meaning (see Figure 9): 1. In the Dial section, you can configure either Tone (default) or Pulse dialling. Most networks use tone dialling, but if in doubt, ask your telephone provider. 2.
CHAPTER 2 System Setup Note: If you use an external GSM modem, you can add CBST=71,0,1 to the initialization command to tell the GSM modem to use the fully digital V110 mode. This makes setting up a connection much faster than with the standard modem emulation. b. The Modem chat timeout refers to an internal parameter (the time-out associated with the communication between the A733 microprocessor and the on board GSM module); it should not be changed. c. The Cancel the call...
CHAPTER 2 Installation Note: You can also use a terminal to check the log file via the emu3ap utility by typing the command calljournal. Note also that the journal is lost after a reboot. In case you changed various modem parameters and you don’t seem to make the unit properly dial-out anymore, use the Restore defaults button and the factory defaults will be restored.
CHAPTER 2 System Setup the appropriate hardware and software manuals to configure your network. When you have done so, skip the rest of this section and go to “Administering your Telemetry Network” on page 35. With your existing addVANTAGE 3.x installation, you will need to export its data. First, however, you need to upgrade your addVANTAGE Manager software to the latest addVANTAGE 3.x release provided on the distribution CD-ROM (currently, addVANTAGE Manager 3.47). Look for the addVANTAGE 3.
CHAPTER 2 Installation exported from addVANTAGE 3.4x. After navigating to the required directory, select the file config.xml and click OK. Figure 11. The Configurator GUI 9. Your network configuration, including the sensors and the custom sensors you previously had in addVANTAGE 3.4x and in the addVANTAGE Manager, are now uploaded to your gateway. You can quit the Configurator or proceed to further configuration as described in “Administering your Telemetry Network” on page 35.
CHAPTER 2 System Setup You can in fact continue to use both addVANTAGE versions at the same time: addVANTAGE 3.4x over the serial line and addVANTAGE 4 Pro over a TCP/IP network. For installing and configuring addVANTAGE 4 Pro as well as some additional tips about migrating from addVANTAGE 3.4x to addVANTAGE 4 Pro, refer to the User Guide supplied with the addVANTAGE 4 Pro CDROM. Configure GPRS usage Firmware and Routers The A840 Gateway must have an IMG update to allow GPRS connections.
CHAPTER 2 Installation One asterisc means that the IP connection to the GPRS unit will stay open all the time (until an idle timeout occurs, see GPRSTMOUT, or any other condition which disconnects the IP or GPRS connection occurs). Two asteriscs direct the A840 to close the IP connection to the GRPS unit after the poll is done. In this case the next poll will take place when the GPRS unit connects to the A840 the next time.
CHAPTER 2 System Setup After you have started the Configurator and logged in (as described in Step 2 through Step 5 on page 23), select the root element in the tree (the topmost device) and click Properties. You can also right-click the base station and select Properties in the pop-up. Following parameters can be changed: • The name of the server; this has no implications to addVANTAGE or the Internet name of the gateway. • The network operating frequency and the channel spacing.
CHAPTER 2 Installation Figure 12. Base Station Properties • The threshold that defines when data is missing from a certain RTU. If no data is collected from a certain RTU for the specified time interval (in seconds), the data from this RTU will first be signalled in addVANTAGE as missing, then when (and if) later retrieved, marked as being delayed (default 3600). Note: This functionality is supported in addVANTAGE 3.4x only.
CHAPTER 2 System Setup Note: The poll schedule is applicable only to the A733GSM/GPRS RTUs. Adding New RTUs If you need to add new RTUs, you first need to know their serial number, symbolic names (usually the place where they are installed), and the stations through which they have to be routed, if any. For the A733GSM/GPRS RTUs, you don’t need a route, but you will need its data phone number (for more details on the data phone number issue, please consult the addWAVE User Guide).
CHAPTER 2 Installation Figure 13. Adding a new A733 RTU 4. If you plan to use the gateway to initialize the RTU’s internal real-time clock, click the Master checkbox. 5. If you want data from the selected RTU stored on your gateway, click the Retrieve data checkbox (if the RTU is used only as a relay station, do not select this option). 6. You can also use this window to set up a route with your new RTU (applicable only if you selected an A733RTU).
CHAPTER 2 System Setup Figure 14. Adding a new A733GSM/GPRS RTU 8. Select the Poll method: this can be either: a. the default poll interval (as set on the server node, see “Editing the Base Station’s Properties” on page 35), b. a custom poll interval, c. the default poll schedule (as set on the server node). d. or a custom poll schedule. Note: For the standard A733 RTUs, the poll schedule is not applicable; only poll intervals are accepted. 9. When you’re finished, click OK.
CHAPTER 2 Installation data latency and the number of calls per day in order to keep the costs down. In a typical scenario one or two calls per day would be a good compromise. The call itself takes about two minutes to download data collected for one day, assuming a typical sensor configuration. If you have many sensors and/or they are sampled more often that usual (i.e. once every 15 minutes), then you should set your poll schedule more often.
CHAPTER 2 System Setup changes, you must confirm them by clicking Update or selecting File Update. Note: If you change the code of an RTU that is also used as a router for other RTUs, the changes will automatically be performed for all the routes affected. Deleting an RTU If you decide to remove an RTU from your telemetry network, all you have to do is select the RTU in the Configurator window and click Remove in the RTUs section.
CHAPTER 2 Installation 2. Click Connect in the Sensors section (you can also right-click a sensor and select Connect Sensors from the pop-up). The window shown Figure 16 is displayed.From the left pane, select the sensor you want to connect and click the rightarrow button. 3. If you want to edit the name of a sensor already connected, select the sensor, then click the edit button and perform the editing. 4. Click OK when you are finished. 5.
CHAPTER 2 System Setup 2. Click Connect in the Sensors section (you can also right-click a sensor and select Connect Sensors from the pop-up). The window shown Figure 17 is displayed. Figure 17. Connecting SDI-12 Sensors 3. From the left pane, select the sensor you want to connect and click the right-arrow button. 4. If you want to edit the name or the SDI address of a sensor already connected, select the sensor, then click the edit button and perform the editing. 5.
CHAPTER 2 Installation 3. Click OK to confirm the deletion. 4. To confirm the changes, click Update or select File Update. Adding Custom Sensors If you need to connect a sensor to your RTUs that isn’t yet supported by a built-in standard sensor driver, you must first define it in the Configurator. 1. In the Custom sensors section of the Configurator window, click New to display the window shown in Figure 18. Figure 18. Adding an analog custom sensor 2.
CHAPTER 2 System Setup choose an appropriate sensor subclass by selecting the appropriate icon. Note: If you cannot find a suitable EUID for your sensor, contact Adcon Telemetry. • b. Display scale, min and max: type the default values that will be displayed on a trend graph. In most cases these values will be the same as for the Conversion range (see below). Specific entries for analog sensors are: • Converter: select Linear or Tabular.
CHAPTER 2 Installation • Cabling: the pin on the connector of the Adcon RTUs that the sensor cable is connected to (refer to the addIT and addWAVE user manuals for a description of the connectors). WARNING If you plan to add your own sensors to an Adcon RTU, note that the cable between the sensor and the RTU must be shielded, with the shielding properly connected to the casing ground of the RTU. In addition, the maximum cable length should not exceed 10 m (33 ft.). c.
CHAPTER 2 System Setup in the string returned by a multiple values sensor. In case of doubt, consult the sensor manufacturer. • d. Use CRC checkbox: this instructs the RTU to use CRC request commands over the SDI-12 bus. Before enabling this option, make sure that the sensor supports CRC. In case of doubt, consult the sensor manufacturer. If you chose to generate a new combo sensor (see Figure 20), you will have to provide the individual components: Figure 20.
CHAPTER 2 Installation Editing Custom Sensors To edit custom sensors, select a custom sensor driver and click Properties. Most available functions are identical to those offered by the “Add custom sensor” command described on page 45. Deleting Custom Sensors If you don’t need a custom sensor any more, you can delete it simply by selecting it and clicking Remove in the Custom sensors section of the Configurator window. Performing Backups The Configurator allows you to perform backups of the configuration.
CHAPTER 2 System Setup A window similar to the one shown in Figure 21 is displayed. Browse until you find the configuration file that was previously saved from a backup operation, then select the file. Click Open to upload the file to the gateway. Note: The Restore operation is in fact identical to the Import from addVANTAGE 3.46 operation described in Step 8 on page 32. About the LED Indicators The A840 Telemetry Gateway has five LED indicators on its panel.
CHAPTER 2 About the LED Indicators Table 2. The PWR LED Indicator Mains Not present PWR LED Battery ON 15/OFF 1 (2 sec) Full ON 8/OFF 8 (2 sec) Half full ON 1/OFF 15 (2 sec) Almost empty When the mains is not present, the PWR LED blinks at a 2-second rate. The on/off state of the blink shows you how much power is left in the battery. For example, as you can see in Table 2, if the LED is lit for most of the two-second period (on 15/off 1), the battery is full.
CHAPTER 2 System Setup
Chapter 3. Advanced Functions This chapter describes some advanced functions that you can perform on your new base station. If you find that certain functions are too complicated or you don’t understand them, your distributor can do what you need for you.
CHAPTER 3 Advanced Functions Stopping and Starting the Telemetry Gateway The telemetry gateway has a built-in rechargeable battery that is software controlled. If for some reason you need to stop the telemetry gateway (for example, shipping for service or storing for longer time spans), you need to shut it down by switching off the battery internally, then unplugging the power cable. Proceed as follows: 1.
CHAPTER 3 Administrative Tasks at the System Level To start the unit, plug the mains cable into the power outlet. After the boot procedure finishes (which takes about 20 seconds), the unit is fully operational. Changing Passwords For security reasons, Adcon recommends that you change the password of your gateway. The unit comes from the factory with only two users: root and adv. The root user is intended only for administrative tasks, while adv is used by the addVANTAGE software.
CHAPTER 3 Advanced Functions Do not change the user name, but type whatever new password you assigned to the adv user. The two password strings in the hardware and software must be identical, or addVANTAGE will not be able to download data from the base station. Note: Only addVANTAGE 3.45 or higher is compatible with the A840 Telemetry Gateway. If your software is not up to date (check File About in addVANTAGE), download the latest update from Adcon’s web server (http://www.adcon.at).
CHAPTER 3 Administrative Tasks at the System Level stty igncr cd /etc /etc/rc.sysinit 6. Now you can change the root password as described in Step 2 through Step 4 of “Changing Passwords” on page 55. 7. After you get the “Password changed” message, type exec /bin/init. The Linux login prompt is displayed. Now you can log in with your new root password. Software Upgrades Both components of your base station have their software stored in Flash EEPROMs.
CHAPTER 3 Advanced Functions 6. Now type upgrade. 7. The system waits for a file to be sent using the Y-modem protocol. Configure your terminal program to send via the Ymodem protocol, switch your communication program to Send, and send the .hmt file from your computer. 8. After a series of messages, the system asks for confirmation. Press Y. The bootloader will now be replaced. 9. Restart the gateway by typing linux. After Linux finishes booting, the gateway is again ready for use.
CHAPTER 3 Operations at the Application Level procedure is finished, after which you must change the speed of your terminal back to 19200 baud. 9. The system waits for a file to be sent using the Y-modem protocol. Configure your terminal program to send via the Ymodem protocol, switch your communication program to Send, and send the .img file from your computer. The download can take several minutes. 10. After a series of messages, the system asks for confirmation. Press Y.
CHAPTER 3 Advanced Functions In either case, you need to press Enter until you get a message stating that you are in the emu3ap command line interpreter (CLI). Note: You can reach the gateway over the serial port or over the built-in modem. If the network is enabled, you can also reach it over Ethernet. You can have more than one emu3ap process running at the same time.
CHAPTER 3 Operations at the Application Level INSERT [phonenumber] RETURNS OK or an error message. REMARKS A device is a remote measuring station (for example, A730MD, A720, A723, or A733). Once the device has been inserted, various operations can be performed on it. Every 15 minutes, the gateway automatically asks the devices in the list to supply a new slot of data over radio. The 15-minute interval can be changed with the SET SLOT command (see page 70).
CHAPTER 3 Advanced Functions ROUTE DESCRIPTION Sets a route for the target device. PARAMETERS The device ID and the route description (composed of the routing devices’ IDs). To clear a route, provide only the target device ID (in other words, a null route). RETURNS OK or an error message. REMARKS The ROUTE command updates the internal descriptors for the specified target device.
CHAPTER 3 Operations at the Application Level REMARKS When a station has a master flag set, the gateway uses that station for date/time synchronization. It is important to understand that each remote station has an internal real-time clock, used to stamp the stored data. This clock has to be initialized and synchronized, which the gateway does automatically when either of the following occurs: • A station returns invalid time values (null or out of date).
CHAPTER 3 Advanced Functions EXTEND This command is deprecated in emu3ap. It has been included for compatibility purposes, but always returns OK. POLLCONF DESCRIPTION Get/set poll configuration for a specific device. PARAMETERS The device ID and the polling intervall/time. POLLCONF get poll configuration POLLCONF INTERVAL [param] set poll configuration POLLCONF TIMES [param] RETURNS Pollconfiguration or an error message.
CHAPTER 3 Operations at the Application Level DEV DESCRIPTION Gets list of devices. PARAMETERS None. RETURNS A list of devices. The list is self-explanatory. REMARKS None. EXAMPLES dev RTU Notifications pending ---------------------------52 NONE 15636 PORT+ANLG 3768 NONE OK NPND DESCRIPTION Gets list of devices wich have notifications pending. PARAMETERS None. RETURNS List of devices and pending notifications. REMARKS None.
CHAPTER 3 Advanced Functions Enables analog port notifications if the analog value is higher than limit for the given RTU and channel NTF IOA..D 1..3 BELOW [limit] Enables analog port notifications if the analog value is lower than limit for the given RTU and channel NTF IOA..D 1..3 OUTSIDE [lower-limit] [upper-limit] Enables analog port notifications if the analog value is outside the limits for the given RTU and channel NTF IOA..D 1..
CHAPTER 3 Operations at the Application Level SENDNTF DESCRIPTION PARAMETERS To configure how to send notifications from the A840 to you. SENDNTF Queries the configuration SENDNTF SYSLOG Requests notifications to be written to the system log only, which effectively disables sending notifications. SENDNTF SMS [lock-time] [format] [phone-nr] Requests notifications to be sent as SMS, at maximum every "lock-time" seconds, to the given phone number.
CHAPTER 3 Advanced Functions password will be transmitted unencrypted since HTTP is used. You should not use the same username/password combination for other purposes. RETURNS Ok or error. REMARKS None. EXAMPLES SENDNTF SYSLOG Turns off sending notifications SENDNTF SMS 600 NODEID 4366412345678 Requests sending notifications to phone number ++43-66412345678, the time between two SMS sent is at least 600 seconds. Output format is the node ID.
CHAPTER 3 Operations at the Application Level subcommand is typed and the emu3ap application returns the requested information. SET TIME DESCRIPTION Sets the internal real-time clock of the emu3ap. PARAMETERS The time in the following format: dd/mm/yyyy hh:mm:ss (24-hour clock format). RETURNS OK or an error message. REMARKS The year may be sent either in two- or four-letter format (for example, 1999 or 99), but the four-letter format is preferred.
CHAPTER 3 Advanced Functions SET OWNID This command is deprecated in emu3ap. It has been included for compatibility purposes, but always returns OK. The radio network ID is programmed at the factory and resides in the A440 Wireless Modem (as for all RTUs, the network ID is the serial number printed on the RTU’s label). SET SLOT DESCRIPTION Sets the request rate in seconds (the default is 900, or 15 minutes).
CHAPTER 3 Operations at the Application Level delay Interruption delay is 7200 seconds OK SET ECHO/NOECHO This command is deprecated in emu3ap. It has been included for compatibility purposes, but always returns OK. The behavior of the emu3ap software is that ECHO is always on. You can also PING and REQUEST data even for devices that are not shown in the devices list. Data Commands This category included commands that return data from the remote stations.
CHAPTER 3 Advanced Functions 01006F021905640F20361509D7C4F8000056A9830F19005B 02A9830F010060021905640F2F361509C9B2F8000056AA80 0F1A006B02AA8110010075021905641002361509DECAF800 0056AA800F18004F02AA800F010055021905641011361509 D8C1F8000056AA7D0F16004D02AA7E0F0100550219056410 20361509D2BBF8000056A87F0F13004002A8800F01004602 190564102F361509DBB2F8000056A97E0F19005102A97F0F 010059021905641102361509CAB9F8000056A97C0F1E0045 01A97C0F01004E021905641111361509C6B1F8000055A684 0F1A001F01A6840F010020011905641120361
CHAPTER 3 Operations at the Application Level to the current position points in effect to the beginning of the next frame). GETCONFIG-CSV DESCRIPTION Allows the configuration of the text export. PARAMETERS The getconfig-csv CGI script accepts the following URL parameters: errors=yes|no Specifies whether errors are printed as empty fields (default, or errors=no) or printed as error number (errors=yes). lines=yes|no Specifies whether line numbers are printed (lines=yes) or not (default, or lines=no).
CHAPTER 3 Advanced Functions Specifies whether the TAG list is printed (default, or taglist=yes) or not (taglist=no). booleanformat=N|T Specifies whether boolean values are printed as numbers (booleanformat=N) or as strings TRUE, FALSE (default, or booleanformat=T). . RETURNS OK or an error message. REMARKS To use this command, this feature has to be bought aditionally. A special license key is required.
CHAPTER 3 Operations at the Application Level Specifies the field delimiter (default is ";"). All special characters must be URL-escaped (e.g. for the tab character with ASCII code 0x09, you have to write "%09"). lineending=string Specifies the line ending (default is linefeed). All special characters must be URL-escaped (e.g. for the tab character with ASCII code 0x09, you have to write "%09"). quote=string Specifies the string quotation character (default is the double quote).
CHAPTER 3 Advanced Functions • YY for the year without century • M or MM for the month • D or DD for the day of month • h or hh for the hour • m or mm for the minute • s or ss for the second • T or t for the UTC timestamp All other characters are copied verbatim. All special characters must be URL-escaped (e.g. for the tab character with ASCII code 0x09, you have to write "%09"). timeformat=string Specifies the format for the TIME column.
CHAPTER 3 Operations at the Application Level If you choose headerformat=S, a tag name of, for example, "1234 temperature relay 1" would be printed as "1234". outputformat=T|S Specifies the format of the output: a single table with a column for each TAG (outputformat=T) or one section with one table per TAG (outputformat=S). datequote=string Specifies the quote character for the DATE column (same syntax like quote=). Default is the same as the string quote.
CHAPTER 3 Advanced Functions statusformat=N|T Specifies whether the status of a measurement value is printed as a number (statusformat=N) or as strings OK, BAD, MISSING (default, or statusformat=T). bad=yes|no Specifies whether measurement values with status=bad are output (bad=yes) or not (default, or bad=no). missing=yes|no Specifies whether measurement values with status=missing are output (missing=yes) or not (default, or missing=no). RETURNS Text export data.
CHAPTER 3 Operations at the Application Level REMARKS None. EXAMPLE sdichanged 44 SDI configuration changes pending for RTU 44 OK Administrative Commands This category describes the commands that return certain status information. VER DESCRIPTION Returns the current version of the emu3ap software. PARAMETERS None. RETURNS OK or an error message. REMARKS None. EXAMPLE ver Adcon Telemetry emu3ap, version 3.02 OK TYPE DESCRIPTION Returns the hardware platform of the emu3ap. PARAMETERS None.
CHAPTER 3 Advanced Functions REMARKS None. UPTIME DESCRIPTION Returns the amount of time the A440 Wireless Modem connected to the gateway has been operational. PARAMETERS None. RETURNS The amount of time the wireless modem has been in operation. REMARKS None. EXAMPLE uptime Up 230 day(s), 10 hour(s), 14 minute(s) OK NOP This command is deprecated in emu3ap. It has been included for compatibility purposes, but always returns OK.
CHAPTER 3 Operations at the Application Level RETURNS Returns the current time. REMARKS None. EXAMPLE time Local time is: Tue Aug 29 11:28:36 2006 OK UTC DESCRIPTION Get/Set “wireless network uses UTC” flag. PARAMETERS UTC [ON|OFF] RETURNS Returns weather the wireless network uses UTC or not. REMARKS None. EXAMPLE utc Wireless network uses UTC OK POLL DESCRIPTION Requests gateway to poll a specific device as soon als possible. PARAMETERS POLL RETURNS OK or error.
CHAPTER 3 Advanced Functions DIRECT DESCRIPTION Allows to send any availible radio command directly to the specified device. PARAMETERS Device Id, wanted command, command parameters RETURNS Result of sent radio command. REMARKS For details please consult the A73x addWAVE User Guide. EXAMPLE direct 10820 info 10820 info 255 255 29/8/2006 13:09:19 2.6 2 0 0 84 62 232 6:47 42 65 72 4 900 15 12 0 OK Gets the information from the specific device.
CHAPTER 3 Operations at the Application Level • REMARKS RSSI (relative signal strength), PMP (power management parameters), and Slot are the current settings of the device. None.
CHAPTER 3 Advanced Functions request 2006 2/11/95 20:0:0 Dev 2006: incoming RF 255, outgoing RF 251 Time Thu Nov 2 20:12:21 1995 Data FF 00 00 51 72 E1 12 0C AF 04 01 72 E1 10 0C AF 04 01 OK Furthermore, if the INIT parameter is also specified after the date and time, the station’s real-time clock will be resynchronized with that of the gateway’s internal date and time: request 2006 2/11/95 20:0:0 INIT Dev 2006: incoming RF 255, outgoing RF 251 Time Thu Nov 2 20:12:21 1995 Data FF 00 00 51 72 E1 12 0C
CHAPTER 3 Operations at the Application Level and DATA bits must be OR-ed according to the required state of the ports. RETURNS The actual state of the port (in hex). REMARKS This command is deprecated; it is supported only by the A730MD devices and early A720 devices (series 1). New devices use the more advanced PORT command. EXAMPLE rsetio 2003 0 0 DDR 02, REG 5F OK PORT DESCRIPTION Acts upon the I/O ports of a remote device.
CHAPTER 3 Advanced Functions B DESCRIPTION Issues a broadcast request frame that forces all listening devices to answer. PARAMETERS None. RETURNS A list of devices that answered. REMARKS None.
CHAPTER 3 Operations at the Application Level EXAMPLE rblist 9473 Dev 9473: incoming RF 255, outgoing RF 255 Last Broadcast: Mon Jun 19 12:50:31 2000 201: 255 4446: 255 2622: 255 6127: 255 10820: 255 11127: 255 2646: 255 2008: 255 OK RSET DESCRIPTION Issues remote SET commands, which set parameters in the RTUs. Not all the RTUs support these commands, most notably the A730MD devices don’t support it. PARAMETERS The ID of the remote, the set-command, and its parameters.
CHAPTER 3 Advanced Functions XDATA DESCRIPTION This command requests data for a list of logical channels for given timestamps. PARAMETERS XDATA [ [ ] ] RETURNS The requested data if available is returned in the specified format. REMARKS Detailed information about parameters and output formats please infer from the A740 addNODE User Guide.
CHAPTER 3 Operations at the Application Level Phone: Key: Start: Duration: OK 06641111111 123456789 Fri May 5 11:44:38 2006 15 HANGUP DESCRIPTION hang up call to device PARAMETERS Device ID and shared secret RETURNS A list of status parameters. The list is self-explanatory. REMARKS The shared secret is needed to hangup the call.
CHAPTER 3 Advanced Functions REMARKS Get only. EXAMPLE calljournal Start--- Time-- Code Phone------- Status Cause 20060430 17:00:02 7 30150 89.144.206.167 OK NORMAL 20060430 17:30:02 8 30150 89.144.206.167 OK NORMAL 20060430 18:00:02 15 30150 89.144.206.
CHAPTER 3 Operations at the Application Level PARAMETERS None. RETURNS A list of current status parameters. The list is self-explanatory. REMARKS GET only. EXAMPLE gprsstat RTU Address Port NPND POLL TIME --------------------------------------------------34990 172.16.0.66 45964 0 0 43693 OK GPRSDISCONNECT DESCRIPTION Close existing GPRS connection to device. PARAMETERS Device ID. RETURNS OK or error. REMARKS None.
CHAPTER 3 Advanced Functions • 30 — Error receiving a frame (cyclic redundancy check and others) • 31 — An unexpected frame type was received • 32 — False length (type does not fit its length) • 35 — Radio timeout when receiving (no answer after a request • 36 — RF channel in use Frame Types The information in this section is intended to programmers writing their own routines to interface with the A840 Telemetry Gateway. The A840/A440 combination can communicate with various types of RTUs.
CHAPTER 3 Operations at the Application Level }; BYTE PulseCounter1; BYTE BatteryLevel; BYTE Analog1; BYTE Analog2; BYTE Analog3; BYTE Analog4; BYTE Analog5; BYTE Analog6; BYTE Analog7; BYTE Analog8; BYTE Analog9; BYTE Analog10; BYTE Analog11; BYTE Analog12; BYTE Analog13; BYTE Analog14; 93
CHAPTER 3 Advanced Functions DESCRIPTION All values are 8 bits and must be converted accordingly, depending on the sensor connected. Figure 23 shows the placement of various inputs on the connectors.
CHAPTER 3 Operations at the Application Level The RF level is non-linear and results from a table (which you can get from Adcon as an ASCII file). The value of the battery can be computed as follows: • 20Batt [ V ] = BatteryLevel --------------------------------------------255 The digibyte is essentially the reflection of several inputs or internal status bits on the A730MD; its structure is described below: B7 B6 S.C. AUX:4 B4 B3 RAI:3 RAI:4 B5 N.U. S.C.
CHAPTER 3 Advanced Functions }; DESCRIPTION All values are 8 bits and must be converted accordingly, depending on the sensor connected. Figure 24 shows the placement of various inputs on the connectors. Power A720 Analog4 Analog5 DIG1 7 6 5 Power Analog1 Analog2 DIG0 7 1 6 5 2 4 3 PulseCounter1 Ground Analog6 1 2 4 3 PulseCounter0 Ground Analog3 I/O B I/O A Figure 24.
CHAPTER 3 Operations at the Application Level analog values with 10-bit resolution and stores them as 12-bit values. Also, the A723 contains two 16-bit pulse counters, that is, it has more data to send. Due to the limited space available and to minimize the radio traffic, the frames are slightly compressed, in that six 12-bit values are packed in 9 bytes. Type 39 SIZE 22 (including the type byte).
CHAPTER 3 Advanced Functions Figure 25. Type 39 Frame Compression Note: Only Analog1 to Analog6 are packed; the 16-bit Pulse Counters are not. Figure 26 shows the placement of various inputs on the connectors. Power A723 Analog1 Analog2 DIG0 7 6 5 Power Analog4 Analog5 DIG1 7 1 6 5 2 4 3 PulseCounter0 Ground Analog3 1 2 4 3 PulseCounter1 Ground Analog6 I/O B I/O A Figure 26.
CHAPTER 3 Operations at the Application Level space available and in order to minimize the radio traffic, the frames are slightly compressed, in that twelve 12-bit values are packed in nine 16-bit words. Type 37 SIZE 31 (including the type byte).
CHAPTER 3 Advanced Functions Figure 27. Type 37 Frame Compression Note: Only Analog1 to Analog12 are packed; the 16-bit Pulse Counters are not. Figure 28 show the placement of various inputs on the connectors.
CHAPTER 3 Operations at the Application Level For more details, refer to the user manual for the A733 device. Frame Parsing Example To better understand how the retrieved frames must be processed, this section provides an example of such processing. Let’s suppose that we used the GETBLOCK command and retrieved a block of frames of type 37. After parsing the block, we separate it into individual frames as described in “GETBLOCK” on page 71.
CHAPTER 3 Advanced Functions The last step is to convert the analog values to actual engineering units. This is easily accomplished if we know what sensor is connected to each input of the RTU, and its conversion equation. Let’s assume that a temperature sensor is connected to the Analog7 input.
CHAPTER 3 Data Import Data Import Note: The data import to your A840 Telemetry Gateway is only possible when using files exported by a A510 Data Display To perform a data import please connect to your A840 Telemetry Gatway using your webbrowser and selecting the “Import data” option on the welcome page of your A840 Telemetry Gateway Configurator. After entering your A840 Telemetry Gatway username and password correctly into the autentification promt you will be forwarded to the data import interface.
CHAPTER 3 Advanced Functions The data import interface In the data import interface you can choose your desired data file either by entering the filename or by browsing your computer for the file. The data is imported to your A840 Telemetry Gatway by clicking the “Import data” button.
Chapter 4. Appendix Free and Open-Source Software The A840 Telemetry Gateway contains third-party software packages which were made available to the public by their respective copyright owners under license terms which grant additional rights beyond mere usage of the software, such as the right to get, modify and redistribute the sourcecode of these packages. These software packages are commonly called Free and OpenSource Software (FOSS).
CHAPTER 4 Appendix However, there are a few things you have to consider: • Some software packages installed on the gateway are neither derived from nor licensed as FOSS like the bootloader, the data logging andretrieval software and the Configurator application.
CHAPTER 4 Third-party Software glibc 2.1.6 - GNU C Library The GNU C Library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version. q.v. Appendix II LGPL-v2 This product includes software developed by Harvard University and its contributors. Copyright (C) 1991-2005 Free Software Foundation, Inc.
CHAPTER 4 Appendix This library is free software; you can redistribute it and/or modify it under the terms of the GNU Library General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. q.v. Appendix II GPL-v2 md5 - Message digest algorithm The algorithm is due to Ron Rivest. This code was written by Colin Plumb in 1993, no copyright is claimed. This code is in the public domain; do with it what you wish.
CHAPTER 4 Third-party Software putsms - SMS sending utility Copyright (C) 2000 Stefan Frings This program is free software unless you got it under another license directly from the author. You can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation. Either version 2 of the License, or (at your option) any later version. q.v.
CHAPTER 4 Appendix q.v. Appendix II GPL-v2 mini_sendmail - send mails to an SMTP server Mgetty+Sendfax was written by Gert Doering, with many contributions from the Internet. Vgetty was written by Klaus Weidner, Marc Eberhard, Marc Schaefer and also many contributions from the Internet community. The whole package, starting with version 1.1.22, is distributed under the GNU GPL license, found in the accompanying file 'COPYING'. q.v.
CHAPTER 4 Third-party Software GNU bash is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 1, or (at your option) any later version. q.v.
CHAPTER 4 Appendix http://www.isc.org/ wu-ftpd - File transfer protocol daemon wu-ftpd comes under the terms of the WU-FTPD SOFTWARE LICENSE q.v. Appendix II WU-FTPD Software License gdbserver - server stub of the GNU debugger This program is part of the gdb project.
CHAPTER 4 License texts License texts WU-FTPD Software License Use, modification, or redistribution (including distribution of any modified or derived work) in any form, or on any medium, is permitted only if all the following conditions are met: 1. Redistributions qualify as "freeware" or "Open Source Software" under the following terms: a. Redistributions are made at no charge beyond the reasonable cost of materials and delivery.
CHAPTER 4 Appendix Portions Copyright (c) 1993, 1994 Washington University in Saint Louis. Portions Copyright (c) 1996, 1998 Berkeley Software Design, Inc. Portions Copyright (c) 1983, 1995, 1996, 1997 Eric P. Allman. Portions Copyright (c) 1998 Sendmail, Inc. Portions Copyright (c) 1989 Massachusetts Institute of Technology. Portions Copyright (c) 1997 Stan Barber. Portions Copyright (c) 1997 Kent Landfield.
CHAPTER 4 License texts DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 7.
CHAPTER 4 Appendix To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code.
CHAPTER 4 License texts "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you". Activities other than copying, distribution and modification are not covered by this License; they are outside its scope.
CHAPTER 4 Appendix announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.
CHAPTER 4 License texts under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.
CHAPTER 4 Appendix 6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License. 7.
CHAPTER 4 License texts excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License. 9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
CHAPTER 4 Appendix DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
CHAPTER 4 License texts If the program is interactive, make it output a short notice like this when it starts in an interactive mode: Gnomovision version 69, Copyright (C) year name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License.
CHAPTER 4 Appendix [This is the first released version of the Lesser GPL. It also counts as the successor of the GNU Library Public License, version 2, hence the version number 2.1.] Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public Licenses are intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users.
CHAPTER 4 License texts To protect each distributor, we want to make it very clear that there is no warranty for the free library. Also, if the library is modified by someone else and passed on, the recipients should know that what they have is not the original version, so that the original author's reputation will not be affected by problems that might be introduced by others. Finally, software patents pose a constant threat to the existence of any free program.
CHAPTER 4 Appendix In other cases, permission to use a particular library in non-free programs enables a greater number of people to use a large body of free software. For example, permission to use the GNU C Library in non-free programs enables many more people to use the whole GNU operating system, as well as its variant, the GNU/Linux operating system.
CHAPTER 4 License texts associated interface definition files, plus the scripts used to control compilation and installation of the library. Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running a program using the Library is not restricted, and output from such a program is covered only if its contents constitute a work based on the Library (independent of the use of the Library in a tool for writing it).
CHAPTER 4 Appendix (For example, a function in a library to compute square roots has a purpose that is entirely well-defined independent of the application. Therefore, Subsection 2d requires that any application-supplied function or table used by this function must be optional: if the application does not supply it, the square root function must still compute square roots.) These requirements apply to the modified work as a whole.
CHAPTER 4 License texts accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange.
CHAPTER 4 Appendix under terms of your choice, provided that the terms permit modification of the work for the customer's own use and reverse engineering for debugging such modifications. You must give prominent notice with each copy of the work that the Library is used in it and that the Library and its use are covered by this License. You must supply a copy of this License.
CHAPTER 4 License texts For an executable, the required form of the "work that uses the Library" must include any data and utility programs needed for reproducing the executable from it. However, as a special exception, the materials to be distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.
CHAPTER 4 Appendix all its terms and conditions for copying, distributing or modifying the Library or works based on it. 10. Each time you redistribute the Library (or any work based on the Library), the recipient automatically receives a license from the original licensor to copy, distribute, link with or modify the Library subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein.
CHAPTER 4 License texts 12. If the distribution and/or use of the Library is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Library under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License. 13.
CHAPTER 4 Appendix 16.
CHAPTER 4 License texts Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 021101301 USA Also add information on how to contact you by electronic and paper mail. You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the library, if necessary. Here is a sample; alter the names: Yoyodyne, Inc., hereby disclaims all copyright interest in the library `Frob' (a library for tweaking knobs) written by James Random Hacker.
CHAPTER 4 Appendix TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
CHAPTER 4 License texts WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
CHAPTER 4 Appendix Sun RPC is a product of Sun Microsystems, Inc. and is provided for unrestricted use provided that this legend is included on all tape media and as a part of the software program in whole or part. Users may copy or modify Sun RPC without charge, but are not authorized to license or distribute it to anyone else except as part of a product or program developed by the user.
CHAPTER 4 License texts LIABILITY OF ANY KIND FOR ANY DAMAGES WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE. Carnegie Mellon requests users of this software to return to Software Distribution Coordinator School of Computer Science Carnegie Mellon University Pittsburgh PA 15213-3890 or Software.Distribution@CS.CMU.EDU any improvements or extensions that they make and grant Carnegie Mellon the rights toredistribute these changes. The file if_ppp.
CHAPTER 4 Appendix (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. The following license covers the files from Intel's "Highly Optimized Mathematical Functions for Itanium" collection: Intel License Agreement Copyright (c) 2000, Intel Corporation All rights reserved.
CHAPTER 4 License texts The files inet/getnameinfo.c and sysdeps/posix/getaddrinfo.c are copyright (C) by Craig Metz and are distributed under the following license: /* The Inner Net License, Version 2.00 The author(s) grant permission for redistribution and use in source andbinary forms, with or without modification, of the software and documentationprovided that the following conditions are met: 0.
CHAPTER 4 Appendix LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. If these license terms cause you a real problem, contact the author.
CHAPTER 4 License texts 143
CHAPTER 4 Appendix
CHAPTER 4 License texts 145
CHAPTER 4 Appendix
