2 Circuits 1.2 serial key or number

In computing, a serial port is a serial communication interface through which information transfers in or out sequentially one bit at a time.^[1] This is in contrast to a parallel port, which communicates multiple bits simultaneously in parallel. Throughout most of the history of personal computers, data has been transferred through serial ports to devices such as modems, terminals, various peripherals, and directly between computers.

While interfaces such as Ethernet, FireWire, and USB also send data as a serial stream, the term serial port usually denotes hardware compliant with RS or a related standard, such as RS or RS

Modern consumer PCs have largely replaced serial ports with higher-speed standards, primarily USB. However, serial ports are still frequently used in applications demanding simple, low-speed interfaces, such as industrial automation systems, scientific instruments, point of sale systems and some industrial and consumer products.

Server computers may use a serial port as a control console for diagnostics, while networking hardware (such as routers and switches) commonly use serial console ports for configuration, diagnostics, and emergency maintenance access. To interface with these and other devices, USB-to-serial converters can quickly and easily add a serial port to a modern PC.

Hardware[edit]

In the present day, many devices use an integrated circuit called a UART to implement a serial port. This IC converts characters to and from asynchronous serial form, implementing the timing and framing of data specified by the serial protocol in hardware. The IBM PC implements its serial ports, when present, with one or more UARTs.

Very low-cost systems, such as some early home computers, would instead use the CPU to send the data through an output pin, using the bit banging technique. These early home computers often had proprietary serial ports with pinouts and voltage levels incompatible with RS

Before large-scale integration (LSI) made UARTs common, serial ports were commonly used in mainframes and minicomputers, which would have multiple small-scale integrated circuits to implement shift registers, logic gates, counters, and all the other logic needed. As PCs evolved serial ports were included in the Super I/O chip and then in the chipset.

DTE and DCE[edit]

The individual signals on a serial port are unidirectional and when connecting two devices the outputs of one device must be connected to the inputs of the other. Devices are divided into two categories: data terminal equipment (DTE) and data circuit-terminating equipment (DCE). A line that is an output on a DTE device is an input on a DCE device and vice versa, so a DCE device can be connected to a DTE device with a straight wired cable, in which each pin on one end goes to the same numbered pin on the far end.

Conventionally, computers and terminals are DTE, while modems and peripherals are DCE. If it is necessary to connect two DTE (or DCE) devices together, a cable with reversed TX and RX lines, known as a cross-over, roll-over or null modem cable must be used.

Male and female[edit]

Generally, serial port connectors are gendered, only allowing connectors to mate with a connector of the opposite gender. With D-subminiature connectors, the male connectors have protruding pins, and female connectors have corresponding round sockets.^[2] Either type of connector can be mounted on equipment or a panel; or terminate a cable.

Connectors mounted on DTE are likely to be male, and those mounted on DCE are likely to be female (with the cable connectors being the opposite). However, this is far from universal; for instance, most serial printers have a female DB25 connector, but they are DTEs.^[3] In this circumstance, a gender changer can be used to correct the mismatch.

Connectors[edit]

The only connector specified in the original RS standard was the pin D-subminiature, however, many other connectors have been used, among other reasons to save money or save on physical space. In particular, since many devices do not use all of the 20 signals that are defined by the standard, connectors with fewer pins are often used.

PC serial port colored as specified in the PC 97 standard

The 9-pin DE-9 connector has been used by most IBM-compatible PCs since the Serial/Parallel Adapter option for the PC-AT, where it allowed a serial and parallel port to fit on the same card.^[4] This use has been standardized as TIA

Some miniaturized electronics, particularly graphing calculators^[5] and hand-held amateur and two-way radio equipment^[6], have serial ports using a phone connector, usually the smaller or &#;mm connectors and utilizing the most basic 3-wire interface.

A Cisco rollover cable using the 8P8C Yost standard

8P8C connectors are also used in many devices. The EIA/TIA standard defines a pinout using this connector, while the rollover cable (or Yost standard) is commonly used on Unix computers and many network devices, such as equipment from Cisco Systems.^[7]

Many models of Macintosh favor the related RS standard, mostly using circular mini-DIN connectors, except in the earliest models. The Macintosh included a standard set of two ports for connection to a printer and a modem, but some PowerBook laptops had only one combined port to save space.^[8]

10P10C connectors can be found on some devices. Digital Equipment Corporation defined their own DECconnect connection system which is based on the Modified Modular Jack (MMJ) connector. This is a 6-pin modular jack where the key is offset from the center position. As with the Yost standard, DECconnect uses a symmetrical pin layout which enables the direct connection between two DTEs.^[9]

Another common connector is the DH10 header connector common on motherboards and add-in cards which is usually converted via a cable to the more standard 9-pin DE-9 connector (and frequently mounted on a free slot plate or other part of the housing).^[10]

Countless other connectors have been used for RS connections.

Pinouts[edit]

The following table lists commonly used RS signals and pin assignments.^[11]

The signal ground is a common return for the other connections; it appears on two pins in the Yost standard but is the same signal. The DB connector includes a second "protective ground" on pin 1, which is intended to be connected by each device to its own frame ground or similar. Connecting this to pin 7 (signal reference ground) is a common practice but not recommended.

Note that EIA/TIA combines DSR and RI,^[17][18] and the Yost standard combines DSR and DCD.

Powered serial port[edit]

Some serial ports on motherboards or add-in cards provide jumpers that select whether pin 1 of the DE-9 connector connects to DCD or a power supply voltage, and whether pin 9 of the DE-9 connector connects to RI or a power supply voltage. The power supply voltage can be +5V, +12V, +9V, or ground. (Selection varies by vendor.) The power is intended for use by point-of-sale equipment. Makers include Dell^[19], HP, and others^[20] (This is not an official standard.)

Hardware abstraction[edit]

Operating systems usually create symbolic names for the serial ports of a computer, rather than requiring programs to refer to them by hardware address.

Unix-like operating systems usually label the serial port devices . TTY is a common trademark-free abbreviation for teletype, a device commonly attached to early computers' serial ports, and represents a string identifying the specific port; the syntax of that string depends on the operating system and the device. On Linux, / UART hardware serial ports are named , USB adapters appear as and various types of virtual serial ports do not necessarily have names starting with .

The DOS and Windows environments refer to serial ports as COM ports: COM1, COM2,cromwellpsi.com Ports numbered greater than COM9 should be referred to using the \\.\COM10 syntax.^[21]

Common applications for serial ports[edit]

The RS standard is used by many specialized and custom-built devices. This list includes some of the more common devices that are connected to the serial port on a PC. Some of these such as modems and serial mice are falling into disuse while others are readily available.

Serial ports are very common on most types of microcontroller, where they can be used to communicate with a PC or other serial devices.

Since the control signals for a serial port can be easily turned on and off by a switch, some applications used the control lines of a serial port to monitor external devices, without exchanging serial data. A common commercial application of this principle was for some models of uninterruptible power supply which used the control lines to signal loss of power, low battery, and other status information. At least some Morse code training software used a code key connected to the serial port, to simulate actual code use. The status bits of the serial port could be sampled very rapidly and at predictable times, making it possible for the software to decipher Morse code.

Settings[edit]

Serial standards provide for many different operating speeds as well as adjustments to the protocol to account for different operating conditions. The most well known options are speed, number of data bits per character, parity, and number of stop bits per character.

In modern serial ports using a UART integrated circuit, all these settings can be software-controlled. Hardware from the s and earlier may require setting switches or jumpers on a circuit board.

The configuration for serial ports designed to be connected to a PC has become a de-facto standard, usually stated as /8-N

Speed[edit]

Serial ports use two-level (binary) signaling, so the data rate in bits per second is equal to the symbol rate in baud. A standard series of rates is based on multiples of the rates for electromechanical teleprinters; some serial ports allow many arbitrary rates to be selected, but the speeds on both sides of the connection must match, or data will be received as gibberish.

The capability to set a bit rate does not imply that a working connection will result. Not all bit rates are possible with all serial ports. Some special-purpose protocols such as MIDI for musical instrument control, use serial data rates other than the teleprinter standards. Some serial port implementations can automatically choose a bit rate by observing what a connected device is sending and synchronizing to it.

The total speed includes bits for framing (stop bits, parity, etc.) and so the effective data rate is lower than the bit transmission rate. For example, with 8-N-1 character framing, only 80% of the bits are available for data; for every eight bits of data, two more framing bits are sent.

Bit rates commonly supported include 75, , , , , , , , , and &#;bit/s.^[27]

Crystal oscillators with a frequency of &#;MHz are sold specifically for this purpose. This is 16 times the fastest bit rate, and the serial port circuit can easily divide this down to lower frequencies as required.

Data bits[edit]

The number of data bits in each character can be 5 (for Baudot code), 6 (rarely used), 7 (for true ASCII), 8 (for most kinds of data, as this size matches the size of a byte), or 9 (rarely used). 8 data bits are almost universally used in newer applications. 5 or 7 bits generally only make sense with older equipment such as teleprinters.

Most serial communications designs send the data bits within each byte LSB (least significant bit) first. This standard is also referred to as "little endian."

Also possible, but rarely used, is "big endian" or MSB (most significant bit) first; this was used, for example, by the IBM printing terminal.

The order of bits is not usually configurable within the serial port interface, but is defined by the host system. To communicate with systems that require a different bit ordering than the local default, local software can re-order the bits within each byte just before sending and just after receiving.

Parity[edit]

Parity is a method of detecting errors in transmission. When parity is used with a serial port, an extra data bit is sent with each data character, arranged so that the number of 1 bits in each character, including the parity bit, is always odd or always even. If a byte is received with the wrong number of 1s, then it must have been corrupted. However, an even number of errors can pass the parity check.

Electromechanical teleprinters were arranged to print a special character when received data contained a parity error, to allow detection of messages damaged by line noise. A single parity bit does not allow implementation of error correction on each character, and communication protocols working over serial data links will have higher-level mechanisms to ensure data validity and request retransmission of data that has been incorrectly received.

The parity bit in each character can be set to one of the following:

• None (N) means that no parity bit is sent at all.
• Odd (O) means that parity bit is set so that the number of "logical ones" must be odd.
• Even (E) means that parity bit is set so that the number of "logical ones" must be even.
• Mark (M) parity means that the parity bit is always set to the mark signal condition (logical 1).
• Space (S) parity always sends the parity bit in the space signal condition (logical 0).

Aside from uncommon applications that use the last bit (usually the 9th) for some form of addressing or special signaling, mark or space parity is uncommon, as it adds no error detection information.

Odd parity is more useful than even parity since it ensures that at least one state transition occurs in each character, which makes it more reliable at detecting errors like those that could be caused by serial port speed mismatches. The most common parity setting, however, is "none", with error detection handled by a communication protocol.

Stop bits[edit]

Stop bits sent at the end of every character allow the receiving signal hardware to detect the end of a character and to resynchronise with the character stream. Electronic devices usually use one stop bit. If slow electromechanical teleprinters are used, one-and-one half or two stop bits are required.

Conventional notation[edit]

The data/parity/stop (D/P/S) conventional notation specifies the framing of a serial connection. The most common usage on microcomputers is 8/N/1 (8N1). This specifies 8 data bits, no parity, 1 stop bit. In this notation, the parity bit is not included in the data bits. 7/E/1 (7E1) means that an even parity bit is added to the 7 data bits for a total of 8 bits between the start and stop bits. If a receiver of a 7/E/1 stream is expecting an 8/N/1 stream, half the possible bytes will be interpreted as having the high bit set.

Flow control[edit]

Flow control is used in circumstances where a transmitter might be able to send data faster than the receiver is able to process it. To cope with this, serial lines often incorporate a handshaking method, usually distinguished between hardware and software handshaking.

Hardware handshaking is done with extra signals, often the RS RTS/CTS or DTR/DSR signal circuits. Generally, the RTS and CTS are turned off and on from alternate ends to control data flow, for instance when a buffer is almost full. DTR and DSR are usually on all the time and, per the RS standard and its successors, are used to signal from each end that the other equipment is actually present and powered-up. However, manufacturers have over the years built many devices that implemented non-standard variations on the standard, for example, printers that use DTR as flow control.

Software handshaking is done for example with ASCIIcontrol charactersXON/XOFF to control the flow of data. The XON and XOFF characters are sent by the receiver to the sender to control when the sender will send data, that is, these characters go in the opposite direction to the data being sent. The circuit starts in the "sending allowed" state. When the receiver's buffers approach capacity, the receiver sends the XOFF character to tell the sender to stop sending data. Later, after the receiver has emptied its buffers, it sends an XON character to tell the sender to resume transmission. It is an example of in-band signaling, where control information is sent over the same channel as its data.

The advantage of hardware handshaking is that it can be extremely fast; it doesn't impose any particular meaning such as ASCII on the transferred data; and it is stateless. Its disadvantage is that it requires more hardware and cabling, and these must be compatible at both ends.

The advantage of software handshaking is that it can be done with absent or incompatible hardware handshaking circuits and cabling. The disadvantage, common to all in-band control signaling, is that it introduces complexities in ensuring that a) control messages get through even when data messages are blocked, and b) data can never be mistaken for control signals. The former is normally dealt with by the operating system or device driver; the latter normally by ensuring that control codes are "escaped" (such as in the Kermit protocol) or omitted by design (such as in ANSI terminal control).

If no handshaking is employed, an overrun receiver might simply fail to receive data from the transmitter. Approaches for preventing this include reducing the speed of the connection so that the receiver can always keep up; increasing the size of buffers so it can keep up averaged over a longer time; using delays after time-consuming operations (e.g. in termcap) or employing a mechanism to resend data which has been corrupted (e.g. TCP).

Virtual serial ports[edit]

A virtual serial port is an emulation of the standard serial port. There are several use cases.

Serial port redirection[edit]

Serial port redirection software creates extra virtual serial ports in an operating system without additional hardware installation (such as expansion cards, etc.) in order to split or redirect the data to and from a serial port for a variety of applications.

One option is to share data between several applications. A serial port typically can only be monitored by one device at a time under the constraints of most operating systems, but a serial port redirector can create two virtual ports, for two separate applications to monitor the same data, for instance, a GPS device outputting location data.

Another option is to communicate with another serial device via internet or LAN as if they were locally connected, using serial over LAN.

Virtual serial ports ideally emulate all hardware serial port functionality, including baud rate, data bits, parity bits, stop bits, etc. Additionally, they allow controlling the data flow, emulating all signal lines (DTR, DSR, CTS, RTS, DCD, and RI) and customizing pinout.

It is possible to create a large number of virtual serial ports in a PC. The only limitation is the resources, such as RAM and CPU time. Serial port emulators are available for many operating systems including MacOS, Linux, NetBSD and other Unix-like operating systems, and various mobile and desktop versions of Microsoft Windows.

Bluetooth[edit]

Bluetooth implements virtual serial ports over the Serial Port Profile. This is the standard way of receiving data from Bluetooth-equipped GPS modules, for instance.

Softmodems[edit]

The drivers for a software-implemented modem create a virtual serial port for communication with the host operating system, since the modem is implemented entirely in the device driver and therefore there is no point where the serial data would be sent to the physical card.

See also[edit]

References[edit]

Further reading[edit]

• Serial Port Complete: COM Ports, USB Virtual COM Ports, and Ports for Embedded Systems; 2nd Edition; Jan Axelson; Lakeview Research; pages; ; ISBN&#;

External links[edit]

1. Definitions

In addition to the terms defined elsewhere in the Agreement, the following definitions apply:

“Affiliate” means any entity which directly or indirectly controls, is controlled by or is under common control with Unify or Customer, respectively; „control‟ as used herein shall mean the possession of the power to direct, or cause the direction of, the management and the policies of an entity, whether through ownership of a majority of the voting rights or by contract or otherwise.

“Agreement” means the separate agreement (e.g. software license agreement), under which the Customer obtained the Software from Unify or a Unify Partner.

“Base Software” means &#; as opposed to Single User Software &#; Software installed on a server computer, the so-called “host”, which is accessed by Clients in order to make use of the functionalities of the Base Software.

“Client” means a clearly identifiable entity which can access a server computer and one or more of the Product Instance(s) of the Base Software hosted by it. Clients can be, for example and depending on the specific product, users, agents, devices, identities or communication channels. The number and type of Clients authorized to use the Product Instance(s) on a particular server computer is defined in the Agreement.

“Client Access License” or “CAL” means a License that allows a specific number of Client(s) to access and use the Base Software. Depending on the product, a CAL covers at least one (1) Client but may also cover a defined number of Clients (by example and without limitation, 20, 25, Clients) or permit an unlimited number of Clients to access the Base Software.

“Customer” means the party acquiring a copy of the Software, who is neither a Unify Partner nor an Affiliate of Unify.

“Documentation” means the technical and/or functional descriptions provided along with the Software. Documentation may be provided in electronic form or online, e.g. via the Internet. Documentation may also include, among other things, a description of performance characteristics, special features, hardware and software requirements, installation requirements, conditions of use and end user manuals. To the extent required by the respective Freeware vendor or OSS Licensor, the Documentation also comprises of the applicable license terms for Freeware and the relevant OSS Licenses.

“Firmware” means Single User Software which is embedded into the microcontroller of an electronic device (e.g. a telephone-handset).

“Freeware” means a computer program which may be used without payment or other compensation (for example, by advertising). Freeware may be subject to proprietary license terms imposed by the Freeware vendor, which, for example, may limit the right to distribute or redistribute the Freeware. Freeware may have functional limitations which a commercial version does not have. Other than with Open Source Software, the vendor of the Freeware vendor usually does not deliver source code with the Freeware.

“License” means the right to use a particular computer program. A license may be granted permanently for the statutory term of copyright protection and in exchange of a one-time license fee, or it may be time-limited for the term of a subscription arrangement, and against payment of a recurring license fee. The exact kind and scope of the License acquired by the Customer is further defined in the Agreement.

“License Terms” or “EULA” (End User License Agreement) means this document.

“Open Source License” or “OSS License” means license terms for a computer program that, beyond the right to use the computer program without license-fee or royalty, grant the user rights that are usually reserved for the owner of the copyright, e.g. the right to modify the computer program, to merge it with other computer programs or to distribute it, or a modified version thereof, and which require that at least one of the following conditions is met: (a) the source code or design information for the original or modified computer program must be made available to anyone in general, or upon request; (b) the right to create derivative works of the original or modified computer program must be granted; (c) a license to use the intellectual property rights embodied in the computer program must be granted, without a license fee or royalty, to anyone in general, or upon request, (d) the owner of the copyright in the unmodified computer program must be identified (attribution notice). OSS Licenses by this definition are, for example, the GNU General Public License (GPL) family of licenses, the Berkeley Software Distribution (BSD) family of licenses, and the &#;public domain&#; licenses.

“Open Source Software” or “OSS” means a computer program licensed under an OSS License which is available either (a) in source code form only, or (b) where the source code is delivered together with the object code (executable) or (c) where the source code can be obtained for free (handling fee/ shipping costs may apply).

“Product Instance” means one installed copy of the Base Software.

“Product Instance License Key” or “License Key” means the license key defining the maximum number of CALs assigned to a specific Product Instance.

“Single User Software” is Software intended for use by a single user on a single device, which is not to be used as a server, such as a desktop PC, notebook, smart phone, etc.

“Software” means, collectively, the computer program, files and the media (if any) provided to the Customer under this EULA, and including, if so provided, all Updates, Upgrades, corrections, modified versions, supplements and copies of the Software. The Software may be a computer program from Unify or from a third party supplier, and is, in general, provided in executable (object code) form only. For the purpose of this EULA, the corresponding Documentation is deemed an integral part of the Software. Open Source Software or Freeware delivered together with the Software are, in principle, included in this definition of “Software”, but for them, the respective Open Source Licenses or license terms imposed by the vendor of the Freeware take precedence over this EULA.

“Update” means a release of the Software which primarily addresses bug fixes and, only if necessary, contains minor functional improvements (e.g. additional drivers). Unify may elect at its sole discretion to publish an Update as a full release which allows for a complete installation, or a partial release which implements only the changed code (e.g. a service pack). In any case, an Upgrade requires an existing and properly licensed installation of the Software. Typically, an Update is identified by an increase in the minor release number, within the major version number (e.g. “Version ” instead of “Version ”).

“Upgrade” means a release of the Software which adds new and/or extended functionality and, if necessary, contains bug fixes for older versions. In general, an Upgrade is a full release which allows for a complete installation. In any case, an Upgrade requires an existing and properly licensed, (set of) eligible, older version(s) of the Software that is to be upgraded. Typically, an Upgrade is identified by an increase in the major version number (e.g. “Version ” instead of “Version ”).

“Unify” means the Unify entity indicated in the Agreement.

“Unify Partner” means distributors, resellers, VARs, OEMs and other channel partners authorized by Unify to market the products and services of Unify.

2. General License Terms

The Customer is granted a License to use the Software on the basis of this EULA and only within the scope and terms of the Agreement.

The Software is protected by copyright laws and international copyright treaties as well as other laws and conventions related to intellectual property. In relation to the Customer, the intellectual property rights to the Software remain exclusively with Unify or, where applicable, with Unify’s suppliers, the licensors of the OSS or the vendors of the Freeware.

The Customer shall only install and use the Software if the Customer accepts all licensing terms, including the OSS Licenses and the license terms of the vendors of the Freeware. If the Customer elects to not accept these, the Customer may not install or use the relevant Software. In this case and unless otherwise provided for in the Agreement, the Customer may, to the exclusion of any other claims, withdraw from the Agreement in respect of the Software. The Software and Documentation must then be returned to Unify or the Unify Partner from whom the Customer obtained it. The Customer may only withdraw with respect to the Software. Where it is technically impossible to return the Software, e.g. in case of downloaded Software, the Customer must credibly and in writing (paper) confirm that the Software was not installed and will not be used.

Without limitation to any obligation of Unify under the OSS Licenses, and unless explicitly agreed otherwise, Software shall only be delivered and licensed in object code form i.e. executable, machine-readable form. Customer has no claim to the delivery of source code to such object code.

Unless explicitly otherwise provided for in the Agreement, the Customer shall have a non-exclusive right to use the Software, subject to the provisions of Section 3, to handle Customer’s own internal business purposes and those of Customer’s Affiliates. The use or operation of the Software by third parties is permitted if done solely under the control of the Customer and for Customer’s own internal business purposes (e.g. hosting, outsourcing). Within this scope, the Customer may also, to a reasonable extent, reproduce or copy the Software. All other rights, in particular the right to distribute, translate, modify, re-arrange or publicly broadcast the Software, remain with Unify.

With the exception of OSS, the Customer may not decompile or disassemble the Software, extract any parts of the Software, carry out reverse engineering or otherwise attempt to derive the source code of the Software. The Customer’s right to reverse engineer or decompile the Software according to statutory law/mandatory legal provision, in particular if it is required in order to achieve the contractually agreed functionality or interoperability of the Software with other computer programs, remain unaffected thereby.

Prior to any such action, the Customer must provide written notice to Unify, requiring that Unify provides the necessary information and documents to achieve the contractually agreed functionality or interoperability with other computer programs within a reasonable period of time. Only after the fruitless expiry of that period is the Customer entitled to reverse engineer or decompile the Software within the scope permitted by statutory law.

Neither the Software itself nor the right to use the Software may, without the prior written consent of Unify, be rented-out or leased-out, borrowed-out, sub-licensed or, subject to the provisions of Section , be assigned or otherwise be made available to third parties. The Software may not be duplicated or copied, either in part or in whole, unless expressly permitted under the Agreement or if statutory law allows for backup copies. Unify shall be free to give its consent at its sole discretion.

If the media provided to the Customer contains Software for different products, the Customer may only use the Software for which the customer acquired use rights. Unbundling or repackaging of the Software for sale or re-sale or the modification of such media or any copy of the Software is not permitted.

If the Software was provided to the Customer under a perpetual License, any resale of the Software and the transfer of the right to use the Software require that the Customer transfers the Software and the use rights exactly in the manner and configuration as they were acquired by the Customer. The Software may only be transferred to a third party in its entirety, and complete with all associated material and CALs. A temporary transfer is not permitted. The assignment of parts of the Software to a third party or a transfer of copies of the same Software to multiple third parties is prohibited.

For each permitted resale of the Software, the Customer shall ensure, and upon Unify’s request, provide evidence in writing, that

• the third party agreed to accept and fully comply with this EULA;
• the Software, all serial number(s), CALs and all other material supplied along with the Software, including pre-installed material, and all copies, Updates, Upgrades and prior versions of the Software in Customer’s possession were transferred to the third party;
• Customer retained no copies, including backups;
• Unify was informed about the transfer, the identity of the transferee and the transferred Software, including the relevant serial numbers and license keys, directly or through the relevant Unify Partner and
• The re-assignment of the serial numbers and license keys to the third party acquiring the Software was arranged with Unify.

Upon the transfer of the Software to the third party, all rights of the Customer to use the Software shall expire. Any such transfer does not automatically include a transfer or assignment of warranty claims or of any maintenance or service agreements that may be in effect between the Customer and Unify. If Customer acquired the Software from a Unify Partner, individual or different arrangements may apply for Customer’s warranty claims or with regard to any maintenance or service agreements concluded with the Unify Partner.

The Customer may create a reasonable number of backup copies of the Software. The Customer shall not remove any alphanumeric identification characters, trademarks and copyright notices which may be present in the Software or on the media, and will copy the Software unaltered. The Customer shall record the whereabouts of all copies, which Unify may examine on request.

Provided that the Software requires activation, e.g. by applying a Product Instance License Key, the Customer shall activate the Software within thirty (30) days of the day of installation. Only then will the installation be technically complete. The necessary information for this must be entered by the Customer in the manner described in the installation sequence of the Software. If changes have been made to the hardware, it may be necessary to reactivate the Software. In the event the activation does not take place within said period, the Software may become disabled for further use. To activate the Software again, a valid activation code is required, which can be requested from Unify or a Unify Partner upon proof of authorization. Individual arrangements on acceptance made in the Agreement shall be unaffected hereby.

Every supplementary program code (e.g. patch, Update) which is made available to the Customer under warranty or as part of a software maintenance contract or other service agreement, and all extensions of the License, e.g. additional CALs, shall be deemed an integral part of the respective Software and be subject to these License Terms, unless otherwise agreed in the individual case.

Upon the installation of an Upgrade or a migration-version of the Software, the right to use the preceding version shall expire. Existing copies, including backup copies, shall either be destroyed, which is to be evidenced by Customer upon request, or be returned to Unify or the relevant Unify Partner, unless the Customer proves that the preceding version is required to meet legal or statutory document retention and documentation requirements, which cannot be fulfilled with the Upgrade- or migration-version of the Software. In any case, this option to retain such a version finally expires once the Software is transferred to a third party.

Unify may terminate the License and the use rights granted to Customer hereunder in writing, in whole or in part, for good cause if the Customer breaches the License Terms to a considerable extent, in particular with regard to the scope of the License, and thereby infringes Unify’s rights to the Software in a manner that would render it unreasonable for Unify to adhere to the grant of rights hereunder, provided the Customer fails to cure the breach within thirty (30) days following receipt of a respective notice by Unify. The right of Unify to take judicial action against infringements, in particular to seek injunctive relief, shall remain unaffected.

For Firmware the provisions of these License Terms shall apply analogously, but Firmware may only be used or be passed on to third parties along with the respective accompanying hardware for which it was released.

3. Open Source Software, Freeware and third-party software components

Some parts of the Software, including third-party software components, Freeware or OSS, may be fully or in part subject to licensing terms of the respective vendor, or to OSS Licenses. The Customer may obtain a copy of the licensing terms from Unify or the relevant Unify Partner prior to entering into the Agreement.

Such licensing terms shall take precedence over this EULA. The licensing terms will be shown during the installation process or they are included in the Documentation.

Some of the OSS licenses or Freeware licenses may contain additional limitations or exclusions of warranties and liabilities, and Unify is obliged to forward these limitations or exclusions to the Customer, whether or not they are effective under the law applicable to the Agreement. Unify recommends that the Customer makes itself familiar with those limitations and exclusions contained therein, and in case of doubt should seek independent legal advice.

Insofar as the OSS Licenses provide for the provision of source code, Unify may make it available either (a) by including it in the Software delivery i.e. either on the media, separate media, download or on the device, or (b) make it available on Unify’s website and in any case (c) send it on media upon the Customer’s request, in return for reimbursement of handling/shipping cost. Unify shall provide that (b) and (c) for a particular version of the Software are available for at least three (3) years, calculated from the end-of-sale date set for the relevant version as per Unify’s product lifecycle policy.

Any OSS and Freeware are licensed royalty-free i.e., no fees are charged for the provision of the OSS and the Freeware and for exercising the licensed rights. Fees may be charged for reimbursement of costs incurred by Unify for providing the source code of OSS on media.

4. Customer’s usage rights

License for Base Software: A License for a Base Software entitles the Customer to a single installation on a server computer. Depending on the respective Software, a CAL must be acquired for each Client that accesses the Product Instance(s).

License for Single User Software: A License for a Single User Software entitles the Customer to a single installation of the Software on a single computer. In addition, the Customer may install a copy of the Software on a server computer within Customer’s internal network, solely for the purpose of downloading and installing the Software onto other single computers attached to Customer’s internal network and provided that the Single User Software allows such an installation routine. Depending on the Agreement, the number of Licenses for Single User Software acquired by the Customer may also determine the maximum permissible number of installations. Any other use of Single User Software in a network is not allowed.

5. Delivery

Unless agreed otherwise in the Agreement, the delivery of the Software will be made, as chosen by Unify or the relevant Unify Partner at their sole discretion, either by sending the Software on media or pre-installed on a device (e.g. server computer) to the agreed delivery address (physical delivery), or by making the Software available for download by the Customer through an online portal or app store (electronic delivery).

In order to determine compliance with delivery dates and for the passing of risk, in case of physical delivery, the date and time of transfer of the media or device by Unify to the freight agent is determinative, and for electronic delivery, it is the date on which the Software was made available for download and the Customer was informed about this.

Some of Unify’s products may be made available under a Software-as-a-Service (SaaS) licensing and delivery model with the product being centrally hosted and provided to the Customer on a subscription basis. These products will not be delivered physically. No rights of use are granted beyond the right to use that SaaS product.

6. Warranty and Liability of Unify

The Documentation alone is decisive for the required quality and functionality of the Software. Unify is not liable for any other condition of the Software. In particular, Unify does not represent or warrant that (a) the Software works together in a selection or configuration that was not solely and freely determined by Unify, (b) that it will run uninterrupted or error free, or (c) that all Software errors can be eliminated.A technical error in the Software shall only be considered a Defect if it causes the software to not be compliant with the required quality and functionality as determined by the Documentation.

Warranty claims and other liability claims and / or claims for the refund of expenses against Unify will only be available to the Customer if they have been agreed to in an Agreement that was directly concluded between Unify and the Customer. If the Customer acquired the Software through a Unify Partner, the claims of the Customer are determined by the Agreement concluded with the Unify Partner. This does not limit Customer’s claims under applicable product liability laws.

7. Compliance with Export Control and Customs Regulations

All products, including but not limited to items/commodities (“Items”) (goods/hardware, software and technologies and/or Services) may be subject to export laws and regulations and/or to national, foreign and international regulations. The Parties acknowledge that violations to such laws and regulations are prohibited and that compliance with applicable rules and regulations, in particular but not limited to export laws, rules, restrictions or regulations of the Federal Republic of Germany, the European Union or the United States of America, must be ensured at all times.

Unify will perform all necessary and appropriate procedures for requesting any export authorizations required for deliveries to CUSTOMER, provided Unify will be the legal Exporter of Record for the deliveries. CUSTOMER will provide assistance, required documentation and certificates requested by Unify to obtain required authorizations or to review, ensure and document compliance with applicable laws and regulations.

Should any required authorizations not be granted, granted with delay, granted with a reduced scope, be revoked or not renewed, Unify shall not be liable towards Customer. Such events shall be considered as a Force Majeure event.

Customer shall obtain in due time all required import licenses required for the Items imported from Unify. Unify will, on request, provide reasonable assistance and documentation in support of the import licensing process. Customer is aware that Items supplied under Export licenses are provided for a specific and use and End User and may be subject to specific provisos and conditions. Customer will respect the contents of the applicable governmental licenses and authorizations and the certificates signed in the licensing process (e.g. End-User Certificates-EUC). Customer will not sell, transfer or make otherwise available items delivered under Export Licenses to any End User, end use or destination deviating from the contents of the Export License unless such action was authorized by the competent authority issuing the original export authorization.

Customer will only transfer, export or re-export Items received from Unify to reliable partners. Customer will ensure that Items are not made available in any way to parties, destinations and End Uses under embargo, excluded from business or otherwise under relevant sanctions by Germany, the European Union, the USA or the United Nations.

Customer will not re-export any controlled technical information / technology under this Agreement.

If Items are exported directly to a country outside the EU under Customer’s responsibility, Customer guarantees direct export out of the EU or the country of dispatch without undue delay no later than thirty (30) days after handover of the items to Customer or its designated freight forwarder and during the validity period of the export authorization applicable to the individual export. Customer will only designate reliable freight forwarders (example: AEO certified) who participate in AES (Automated Export System – an automated European Union Customs process). Customer guarantees correct closure of the respective customs procedure on leaving the European Union or the country of dispatch. In case of non-compliance, Customer shall be liable for any additional costs – freight and other &#; and charges imposed on Unify by the national tax administration.

Shipments may not be re-routed to other destinations than those given in the shipment documentation. Such documentation may not be removed or replaced before the shipment has reached its originally declared destination.

In case of re-export of the Items by Customer and unless Unify is the legally defined Exporter of Record, Customer shall be responsible for the overall export process. Customer shall bear all costs related to export control for such re-export.

For the avoidance of doubt and subject to the terms and conditions of this Agreement, Customer transfers the Items delivered by Unify or works and services (including all kinds of technical support) performed by Unify to a third party worldwide, CUSTOMER is solely responsible to comply with all applicable national, EU and international import, export and re-export control regulations, if any.

  Customer shall indemnify and hold harmless Unify from and against any claim, proceeding, action, fine, loss, cost and damages arising out of or relating to any noncompliance with export control regulations by Customer, and Customer shall compensate Unify for all losses and expenses resulting thereof.

Customer warrants that the Items shall not be used for design, development, or production of any nuclear, military, ballistic, biological or chemical weapons. Customer undertakes to inform Unify immediately in case of breach of the said regulations and/or an investigation lead by according relevant national authorities.

If due to circumstances attributable to Customer, Unify is questioned by judicial or administrative authorities, Customer shall be held responsible and may be required to compensate Unify for damages caused.

Unify shall not be held responsible of any regulatory evolution, including but not limited to revoked authorizations.

Customer shall flow down the obligations under this Clause 7 to Customer Affiliates at all levels by incorporating all requirements under this clause, in all agreements signed with End-Customers.

8. Evaluation License Terms

The terms of this Section apply in the event the Customer obtained the Software for evaluation purposes, and take precedence over the rest of the EULA. Any provision of Software for evaluation purposes shall be temporary only.

The Customer may use the Software only for testing and evaluation purposes, and only for the evaluation period agreed with Unify or the Unify Partner from whom the copy of the Software was obtained. The Customer may terminate the evaluation period prior to its expiry at any time by destroying all copies of the Software or by returning them to Unify or the Unify Partner.

Any right to use the Software shall expire automatically upon (a) the Customer not complying with the terms of this EULA and (b) upon the expiry of the evaluation period. Customer acknowledges that some products come with time-limited license keys and will automatically disable themselves upon the expiry of the evaluation period.

Unless otherwise agreed, the Customer is not entitled to receive any form of support from Unify or the Unify Partner during the evaluation period.

The Customer may, at any time during the evaluation period, upgrade to a regular version. Details of the upgrade shall be arranged with Unify or the Unify-Partner.

Evaluation copies of Software obtained from Unify are provided “as is” and without any warranty whatsoever. The Customer uses the Software during the evaluation phase at its own risk, expense and liability. Unify and its suppliers do not provide any warranty for the performance or the results arising from the use of the Software or the accompanying material. Unify nor its suppliers do not accept any warranty or guarantee that third-party proprietary rights are not infringed upon, nor that the Software is marketable or suitable for any specific purpose. The Customers statutory rights in case of fraud or intent shall not be limited thereby.

Any claims of Customer for damages or compensation, regardless of their legal basis, and in particular claims arising from production stoppage, loss of profit, loss of information and data or subsequent damage are excluded.

9. General terms

If individual terms of this EULA are fund to be legally ineffective or impracticable on legal grounds, the validity of the remaining License Terms shall not be affected thereby. The parties will conclude an agreement that will cause the ineffective or impractical term to be replaced by a term that is as equivalent as possible in economic terms.

 These License Terms are governed by the substantive law of the country/State which govern the Agreement and excluding the UN Convention on Contracts for the International Sale of Goods (CISG).

The place of jurisdiction shall be as determined in the Agreement, unless another court venue is mandatory by applicable law.

 Assent to be bound

Customer agrees to be bound by the terms of this EULA and acknowledges that Customer is entering into a legally binding contract by one or more of the following methods: a) executing this EULA, b) clicking to accept or agree where this option is made available to Customer or c) by actually using the Software. Customer should print or save a copy of this EULA for Customer’s records. If Customer does not agree with any part of this EULA, Customer is not authorized to access or use the Software.

Published in: IEEE Journal of Solid-State Circuits ( Volume: 51 , Issue: 12 , Dec. ) IEEE RFIC Virtual Journal