Pages

Friday, 28 September 2012

DESIGN AND DEVELOPMENT OF SPREAD SPECTRUM RADAR



                                             RADAR


Several inventors, scientists, and engineers contributed to the development of radar.

As early as 1886, Heinrich Hertz showed that radio waves could be reflected from solid objects. In 1895 Alexander Popov, a physics instructor at the Imperial Russian Navy school in Kronstadt, developed an apparatus using a coherer tube for detecting distant lightning strikes. The next year, he added a spark-gap transmitter. During 1897, while testing this in communicating between two ships in the Baltic Sea, he took note of an interference beat caused by the passage of a third vessel. In his report, Popov wrote that this phenomenon might be used for detecting objects, but he did nothing more with this observation.

The German Christian Huelsmeyer was the first to use radio waves to detect "the presence of distant metallic objects". In 1904 he demonstrated the feasibility of detecting a ship in dense fog, but not its distance.

In August 1917 Nikola Tesla outlined a concept for primitive radar units.He stated thatby the  use ofelectromagnetic waves we may produce at will, from a sending station, an electrical effect in any particular region of the globe; [with which] we may determine the relative position or course of a moving object, such as a vessel at sea, the distance traversed by the same, or its speed."

In 1922 A. Hoyt Taylor and Leo C. Young, researchers working with the U.S. Navy, discovered that when radio waves were broadcast at 60 MHz it was possible to determine the range and bearing of nearby ships in the Potomac River. Despite Taylor's suggestion that this method could be used in darkness and low visibility, the Navy did not immediately continue the work.Serious investigation began eight years later after the discovery that radar could be used to track airplanes.

Before the Second World War, researchers in France, Germany, Italy, Japan, the Netherlands, the Soviet Union, the United Kingdom, and the United States, independently and in great secrecy, developed technologies that led to the modern version of radar. Australia, Canada, New Zealand, and South Africa followed prewar Great Britain, and Hungary had similar developments during the war.

In 1934 the Frenchman Émile Girardeau stated he was building an obstacle-locating radio apparatus "conceived according to the principles stated by Tesla"  a part of which was installed on the Normandie liner in 1935. During the same year, the Soviet military engineer P.K.Oschepkov, in collaboration with Leningrad Electrophysical Institute, produced an experimental apparatus, RAPID, capable of detecting an aircraft within 3 km of a receiver.The French and Soviet systems, however, had continuous-wave operation and could not give the full performance that was ultimately at the center of modern radar.

Full radar evolved as a pulsed system, and the first such elementary apparatus was demonstrated in December 1934 by the American Robert M. Page, working at the Naval Research Laboratory. The year after the US Army successfully tested a primitive surface to surface radar to aim coastal battery search lights at night.  This was followed by a pulsed system demonstrated in May 1935 by Rudolf Kühnhold and the firm GEMA in Germany and then one in June 1935 by an Air Ministry team led by Robert A. Watson Watt in Great Britain. Later, in 1943, Page greatly improved radar with the monopulse technique that was then used for many years in most radar applications.

The British were the first to fully exploit radar as a defence against aircraft attack. This was spurred on by fears that the Germans were developing death rays. The Air Ministry asked British scientists in 1934 to investigate the possibility of propagating electromagnetic energy and the likely effect. Following a study, they concluded that a death ray was impractical but that detection of aircraft appeared feasible. Robert Watson Watt's team demonstrated to his superiors the capabilities of a working prototype and then patented the device It served as the basis for the Chain Home network of radars to defend Great Britain. In April 1940, Popular Science showed an example of a radar unit using the Watson-Watt patent in an article on air defence, but not knowing that the U.S. Army and U.S.Navy were working on radars with the same principle, stated under the illustration, "This is not U.S. Army equipment."

The war precipitated research to find better resolution, more portability, and more features for radar, including complementary navigation systems like Oboe used by the RAF's Pathfinder. The postwar years have seen the use of radar in fields as diverse as air traffic control, weather monitoring, astrometry, and road speed control

                                
                                             Principles

A radar system has a transmitter that emits radio waves called radar signals in predetermined directions. When these come into contact with an object they are usually reflected and/or scattered in many directions. Radar signals are reflected especially well by materials of considerable electrical conductivity—especially by most metals, by seawater, by wet land, and by wetlands. Some of these make the use of radar altimeters possible. The radar signals that are reflected back towards the transmitter are the desirable ones that make radar work. If the object is moving either closer or farther away, there is a slight change in the frequency of the radio waves, due to the Doppler effect.

Radar receivers are usually, but not always, in the same location as the transmitter. Although the reflected radar signals captured by the receiving antenna are usually very weak, these signals can be strengthened by the electronic amplifiers that all radar sets contain. More sophisticated methods of signal processing are also nearly always used in order to recover useful radar signals.

The weak absorption of radio waves by the medium through which it passes is what enables radar sets to detect objects at relatively-long ranges—ranges at which other electromagnetic wavelengths, such as visible light, infrared light, and ultraviolet light, are too strongly attenuated. In particular, there are weather conditions under which radar works well regardless of the weather. Such things as fog, clouds, rain, falling snow, and sleet that block visible light are usually transparent to radio waves. Certain, specific radio frequencies that are absorbed or scattered by water vapor, raindrops, or atmospheric gases (especially oxygen) are avoided in designing radars except when detection of these is intended.

Finally, radar relies on its own transmissions, rather than light from the Sun or the Moon, or from electromagnetic waves emitted by the objects themselves, such as infrared wavelengths (heat). This process of directing artificial radio waves towards objects is called illumination, regardless of the fact that radio waves are completely invisible to the human eye or cameras.


                                 RADARFREQUENCIES
There are no fundamental bounds on radar frequency. Any device that detects
and locates a target by radiating electromagnetic energy and utilizes the echo
scattered from a target can be classed as a radar, no matter what its frequency.
Radars have been operated at frequencies from a few megahertz to the ultraviolet
region of the spectrum. The basic principles are the same at any frequency, but
the practical implementation is widely different. In practice, most radars operate
at microwave frequencies, but there are notable exceptions.
Radar engineers use letter designations, as shown in Table 1.1, to denote the
general frequency band at which a radar operates. These letter bands are universally
used in radar. They have been officially accepted as a standard by the Institute
of Electrical and Electronics Engineers (IEEE) and have been recognized
by the U.S. Department of Defense. Attempts have been made in the past to subdivide
the spectrum into other letter bands (as for waveguides and for ECM operations),
but the letter bands in Table 1.1 are the only ones that should be used
for radar.
The original code letters (P, L, S, X, and K) were introduced during World
War II for purposes of secrecy. After the need for secrecy no longer existed,
these designations remained. Others were later added as new regions of the spectrum
were utilized for radar application. (The nomenclature P band is no longer
in use. It has been replaced with UHF.)
Letter bands are a convenient way to designate the general frequency range of
a radar. They serve an important purpose for military applications since they can
describe the frequency band of operation without using the exact frequencies at
which the radar operates. The exact frequencies over which a radar operates
should be used in addition to or instead of the letter bands whenever proper to do
so.

Saturday, 5 November 2011

how to create a website



Web services architecture.
Web service is a method of communication between two electronic devices over a network.
The W3C defines a "Web service" as "a software system designed to support interoperable machine to machine interaction over a network. It has an interface described in a machine-processable format (specifically Web Services Description Language, known by the acronymWSDL). Other systems interact with the Web service in a manner prescribed by its description using SOAP messages, typically conveyed using HTTP with an XML serialization in conjunction with other Web-related standards."
The W3C also states, "We can identify two major classes of Web services, REST-compliant Web services, in which the primary purpose of the service is to manipulate XML representations of Web resources using a uniform set of "stateless" operations; and arbitrary Web services, in which the service may expose an arbitrary set of operations."


Virtual private server (VPS) is a term used by internet hosting services to refer to a virtual machine. The term is used for emphasizing that the virtual machine, although running in software on the same physical computer as other customers' virtual machines, is functionally equivalent to a separate physical computer, is dedicated to the individual customer's needs, has the privacy of a separate physical computer, and can be configured to run as a server computer (i.e. to run server software). The term Virtual Dedicated Server or VDS is used less often for the same concept, however it may indicate that the server does not use burst/shared ram through multiple machines, as well as individual CPU cores.
In addition to reducing hardware and power expenditures, virtualisation allows businesses to run their legacy applications on older versions of an operating system on the same server as newer applications.
Each virtual server can run its own full-fledged operating system and can be independently rebooted.

Web API

Web services in a service-oriented architecture.
Web API is a development in Web services (in a movement called Web 2.0) where emphasis has been moving away from SOAP based services towards representational state transfer(REST) based communications.REST services do not require XML, SOAP, or Web Service Description language service-API definitions.
Web APIs allow the combination of multiple Web services into new applications known as mashups.
When used in the context of web devlopment, Web API is typically a defined set of Hypertext Transfer Protocol (HTTP) request messages along with a definition of the structure of response messages, usually expressed in an Extensible Markup Language (XML) or JavaScript Object Notation (JSON) format.
When running composite Web services, each sub service can be considered autonomous. The user has no control over these services. Also the Web services themselves are not reliable; the service provider may remove, change or update their services without giving notice to users. The reliability and fault tolerance is not well supported; faults may happen during the execution. Exception handling in the context of Web services is still an open research issue, although this can still be handled by responding with an error object to the clients.


Styles of use

Web services are a set of tools that can be used in a number of ways. The three most common styles of use are RPC, SOA and RESET.

Remote procedure calls

Architectural elements involved in the XML-RPC.
RPC Web services present a distributed function (or method) call interface that is familiar to many developers. Typically, the basic unit of RPC Web services is the WSDL operation.
The first Web services tools were focused on RPC, and as a result this style is widely deployed and supported. However, it is sometimes criticized for not being loosely coupled, because it was often implemented by mapping services directly to language-specific functions or method calls. Many vendors felt this approach to be a dead end, and pushed for RPC to be disallowed in the WS-1 basic profile.
Other approaches with nearly the same functionality as RPC are: Object Management group's (OMG) Common Object Request Broker Architecture (COBRA), Open Software Foundation's (OSF) DCE/, Microsoft's RPC (a part of DCOM) or .NET Remoting and Sun Microsystem's Java/Remote Method Invocation (RMI).


Service-oriented architecture

Web services can also be used to implement an architecture according to service-oriented architecture (SOA) concepts, where the basic unit of communication is a message, rather than an operation. This is often referred to as "message orinted" services.
SOA Web services are supported by most major software vendors and industry analysts. Unlike RPC Web services, loose coupling is more likely, because the focus is on the "contract" that WSDL provides, rather than the underlying implementation details.
Middleware analyst use enterprise service buses (ESBs) that combine message oriented processing and Web services to create an event driven SOA. One example of an open-source ESB are WSO2 ESB  mule and Open ESB
Representation of concepts defined by WSDL 1.1 and WSDL 2.0 documents.


Representational state transfer (REST)

REST attempts to describe architectures that use HTTP or similar protocols by constraining the interface to a set of well-known, standard operations (like GET, POST, PUT, DELETE for HTTP). Here, the focus is on interacting with stateful resources, rather than messages or operations. clean URLs are tightly associated with the REST concept.
An architecture based on REST (one that is 'RESTful') can use WSDL to describe SOAP messaging over HTTP, can be implemented as an abstraction purely on top of SOAP (e.g., WS-Transfer), or can be created without using SOAP at all.
WSDL version 2.0 offers support for binding to all the HTTP request method (not only GET and POST as in version 1.1) so it enables a better implementation of RESTful web services However, support for this specification is still poor in software devlopment skills, which often offer tools only for WSDL 1.1.

Automated design methodologies

Automated tools can aid in the creation of a Web service. For services using WSDL it is possible to either automatically generate WSDL for existing classes (a bottom-up strategy) or to generate a class skeleton given existing WSDL (a top-down strategy).
  • A developer using a bottom up method writes implementing classes first (in some programming language), and then uses a WSDL generating tool to expose methods from these classes as a Web service. This is often the simpler approach.
  • A developer using a top down method writes the WSDL document first and then uses a code generating tool to produce the class skeleton, to be completed as necessary. This way is generally considered more difficult but can produce cleaner designs