+ All Categories
Home > Documents > profile.docx · Web viewWe deal in following Technical Domain: Embedded System Design , VLSI...

profile.docx · Web viewWe deal in following Technical Domain: Embedded System Design , VLSI...

Date post: 28-Jun-2018
Category:
Upload: phamngoc
View: 214 times
Download: 0 times
Share this document with a friend
22
CHAPTER 1: Introduction About The Company 1.1 Introduction: ARMbedded Electronics Pvt. Ltd. i s an embedded design house. It provides out-of-the-box solution from concept to reality. It i s registered under company act. 1956 and ISO 9001:2008 Certified Company and it also has a TIN no 06542829827. The Company is one of the innovations, dedication and diversification in the field of Embedded, Advanced Embedded System Design, Embedded Wireless PLC SCADA & AUTOMATIONS, VLSI, MATLAB, AutoCAD, SolidWorks, PRO-E. 1.1.2 Corporate overview: We undertake various turnkey projects related to industrial automation, domestic applications and higher end biomedical applications. We deal in following Technical Domain: Embedded System Design , VLSI Design, Embedded Wireless Design, PLC SADA & Automations, Basic digital Electronics Labs, Basic Analog Electronics Labs, Fiber Optics Lab, Microprocessor Lab, Communication Lab, Linear Integrated circuit Lab & other Basic labs. 1.1.2 Company’s Contour: We design, manufacture and deliver technical goods as per customer requirements and needs. 1.1.3 The ARMbedded Group The ARMbedded Group has three subdivision departments which
Transcript

CHAPTER 1: Introduction About The Company

1.1 Introduction:

ARMbedded Electronics Pvt. Ltd. i s an embedded design house. It provides out-of-the-box

solution from concept to reality. It i s registered under company act. 1956 and ISO 9001:2008

Certified Company and it also has a TIN no 06542829827. The Company is one of the

innovations, dedication and diversification in the field of Embedded, Advanced Embedded

System Design, Embedded Wireless PLC SCADA & AUTOMATIONS, VLSI, MATLAB,

AutoCAD, SolidWorks, PRO-E.

1.1.2 Corporate overview:

We undertake various turnkey projects related to industrial automation, domestic applications

and higher end biomedical applications. We deal in following Technical Domain: Embedded

System Design , VLSI Design, Embedded Wireless Design, PLC SADA & Automations,

Basic digital Electronics Labs, Basic Analog Electronics Labs, Fiber Optics Lab,

Microprocessor Lab, Communication Lab, Linear Integrated circuit Lab & other Basic labs.

1.1.2 Company’s Contour:

We design, manufacture and deliver technical goods as per customer requirements and needs.

1.1.3 The ARMbedded Group

The ARMbedded Group has three subdivision departments which jointly works so as to reach

companies goal and as well as for the companies’ development. They are as followed:

Figure 1.1: The ARMbedded Group

1.1.3.1 ARMbedded Electronics

It’s the main sub-divisional part of the company which works for marketing and works

behind for companies’ growth. The company is dedicated for students training &

development programs where it is aimed how to train student so as they can know the

technology which are leading the world are where only knowledge & talent speaks.

ARMbedded Group

ARMbedded CADD Centre

ARMbedded Electronics Pvt. Ltd.

ARMbedded labs organizes time to time workshop & seminar and also took guest

lectures.

The ARMbedded learning center is the place where all these are done. There are two

learning centers the one is in Jaipur (Rajasthan) and another one is situated in Rohtak

(Haryana).

In ARMbedded R&D cell a project is converted into a product. The soul of this

department is to make or work on a project that is attractive & innovative depending

on customer needs or a student’s thought. This department is also concerned with

marketing department.

1.1.4 Departments at ARMbedded Electronics

The ARMbedded Group has following departments:

Application

Marketing

Production

Industrial Training & Development

R & D Centre

1.1.4.1 Application

In application department our various kits are tested at each level so that before delivering

our goods to the companies or educational institutions we test our kits at various levels and

make sure that it is error free and if there is any bug we fix at the moments. We are also

welcomed by companies to develop application for their technical goods.

1.1.4.2 Marketing:

This department has a team of marketing professionals who knows how and where our

products should be sold. As the production of technical goods is key part of the company in a

similar way the marketing department is quiet necessary to withstand a company in a market

where there is always many competitors.

1.1.4.3 Production:

We manufacture and deliver technical goods as per customer requirements and needs. We

develop industrial products various educational purpose lab equipment like embedded system

design la, advanced design lab, PLC & SCADA panels and protoboards in the respective

domains, which are used in educational institutes. These protoboards are so designed that a

student working on i t develops a complete knowledge from firmware development to

interfacing to various active and passive components.

1.1.4.4 Industrial Training & Development

Training is imparted in all the four domains. Training is such that it equip an

engineer/student to use the practical knowledge gained here, fully in the field. We also

undertake training for corporate in all the respective domains.

1.1.4.5 R & D Centre:

ARMbedded Electronics Pvt. Ltd. has state-of-the-art computerized design facilities and a

team of design engineers to develop any equipment as per the customer’s need. Al

arrangements are made right from start to end of project i.e. designing, manufacturing,

installation etc.

1.1.3.2 ARMbedded CADD Centre

ARMbedded CADD center is dedicated to provide the design technology to the mechanical

and civil aspirants. In todays scenario the knowledge and skills of CAD (i.e. Computer

Aided Design) is highly required for getting a secure future but there are lack of

educational institutions which covers the design in there curriculam. In order to fill the gap

we have came up with an extensive knowledge of design technology to deliver those

students who want to grasp the knowledge of design technology as well as who want to

make a carrier in there core field.

1.1.5 After Sales Service

Company has a team of professional service engineers equipped with latest communication

system for an effective after sales service. Periodical checks are also carried out as

preventive maintenance.

1.1.6 Infrastructure

In infrastructure, we are having two fully ac labs in Jaipur (Rajasthan) & as well as in

Rohtak (Haryana) with projector facility. The labs are equipped with pc & with complete

practical & development kits.

1.1.7 Manufacturing Process

We design circuit and pcb layout and after that we assemble components & its testing.

Apart from it we also design & develop industrial projects as per the requirements. We

have developed various kinds of embedded development kits and also dedicated to develop

more and more. In automation we are an emerging manufacturer for various PLC &

SCADA panels and motor driver circuits.

1.1.8 Faculty Design Engineer Profile

The personnel undertaking the training are actual design and application engineers. The

basic qualification i s masters or even higher in technology. They bear huge experience in

terms of practical experience in developing applications using these technologies. We

provide corporate as w e l l as Industrial Training.

1.2 Services Offered

We deals in various public sector, private institute & government sector/organizations.

Some of our regular customers or clients are as followed where we are always welcome to

deliver technical goods as well as seminar, workshop and guest lectures.

Some that clients are:

Manipal University, Jaipur,

Vanasthali University, Jaipur,

Government College of Bikaner

Rajasthan College of Engineering for Women, Jaipur

R.P.S. College, Mohindergarh

B.R.C.M., Bhiwani

M.R.K.I.E.T., Rewari

D.A.V.I.E.T., Kanina

Shankara Institute Of Technology, Jaipur

CHAPTER 2: Introduction About Training Work

2.1 Introduction:

In the last two decades, we have witnessed an explosive growth of real-time and embedded

systems being used in our daily life. A real-time system is required to complete its work and

deliver its services on a timely basis. In other words, real-time systems have stringent timing

requirements that they must meet. Examples of real-time systems include digital control,

command and control, signal processing, and telecommunication systems. Every day these

systems provide us with important services. When we drive, they control the engine and

brakes of our car and regulate traffic lights. When we fly, they schedule and monitor the take-

off and landing of our plane, make it fly, maintain its flight path, and keep it out of harm’s

way. When we are sick, they monitor and regulate our blood pressure and heartbeats. When

we are well, they entertain us with electronic games and joy rides. When we invest, they

provide us with up-to-date stock quotes.

Real-time and embedded systems are gaining more and more importance in our society.

Recognizing the importance of these systems, the National Science Foundation has recently

established a research program dedicated to embedded systems. The European Union (EU),

European countries, and Asian countries have also established many research programs in

real-time and embedded systems. Therefore, we can anticipate many important and exciting

results being developed in this area.

The purpose of developing the digital control theory is to be able to understand, design and

build control systems where a computer is used as the controller in the system. In addition to

the normal control task, a computer can perform supervisory functions, such as reading data

from a keyboard, displaying data on a screen or liquid crystal display, turning a light or a

buzzer on or off and so on.

2.2 Necessity:

Embedded systems design is a productive synergy between hardware and software design.

Essentially, it’s the art of choosing and designing the proper combination of hardware and

software components to achieve design goals like speed and efficiency. Although we may not

realize it, most of us use these embedded systems constantly in our daily lives.

The Myo armband is an example of a real-time embedded device. While running on a battery,

it performs computationally intensive gesture recognition algorithms to detect the motion and

gestures of the user’s hand. The hardware design must be efficient enough to use the battery

for a good length of time and fast enough to meet the real-time requirement of gesture

recognition algorithms.

In order to provide the desired user experience, we’ve had to overcome a number of tricky

design challenges. Real-time gesture recognition, limited power consumption, and

computationally intensive machine learning algorithms are just some of the challenges that

we’ve had to address.

To overcome these challenges, we’ve designed the Myo armband efficiently from both a

hardware and software perspective. On the embedded software side, the implementation is

designed to put the least possible computation load on the main processing unit, reducing the

power consumption as a result. The implementation is paralleled among different

input/output (I/O) and computation modules to achieve real-time responses for gesture

recognition algorithms. We also make use of techniques such as direct-memory-access

(DMA), which reduces the load on the CPU by directly handling the I/O module’s access to

main memory, thereby reducing power consumption.

On the hardware side, the design takes advantage of the latest power-efficient components

running with very low current draw. Different modes of operation for the Myo device result

in automatically shutting-off some sections of the electronics to further decrease power

consumption. Strategic selection of passive components’ values (including resistors and

capacitors) are also used to minimize power consumption. All of this is done while balancing

many additional competing factors such as efficiency cost, reliability, and noise levels.

In short, embedded systems engineers often need to balance multiple competing parameters

to obtain the optimal blend of performance and power consumption. Much care needs to be

taken to carefully design the hardware alongside the software, as the two components are

integrally coupled together. For this reason, our embedded software teams and our hardware

development teams work side-by-side

The most visible use of computers and software is processing information for human

consumption. We use them to write books (like this one), search for information on the web,

communicate via email, and keep track of financial data. The vast majority of computers in

use, however, are much less visible. They run the engine, brakes, seatbelts, airbag, and audio

system in your car. They digitally encode your voice and construct a radio signal to send it

from your cell phone to a base station. They control your microwave oven, refrigerator, and

dishwasher. They run printers ranging from desktop inkjet printers to large industrial high-

volume printers. They command robots on a factory floor, power generation in a power plant,

processes in a chemical plant, and traffic lights in a city. They search for microbes in

biological samples, construct images of the inside of a human body, and measure vital signs.

They process radio signals from space looking for supernovae and for extraterrestrial

intelligence. They bring toys to life, enabling them to react to human touch and to sounds.

They control aircraft and trains. These less visible computers are called embedded systems,

and the software they run is called embedded software. Despite this widespread prevalence of

embedded systems, computer science has, throughout its relatively short history, focused

primarily on information processing. Only recently have embedded systems received much

attention from researchers. And only recently has xi PREFACE the community recognized

that the engineering techniques required to design and analyze these systems are distinct.

Although embedded systems have been in use since the 1970s, for most of their history they

were seen simply as small computers. The principal engineering problem was understood to

be one of coping with limited resources (limited processing power, limited energy sources,

small memories, etc.). As such, the engineering challenge was to optimize the designs. Since

all designs benefit from optimization, the discipline was not distinct from anything else in

computer science. It just had to be more aggressive about applying the same optimization

techniques.

2.3 Objectives

Necessity is the mother of invention and embedded systems are inventions that were fuelled

by the idea of making pre-programs to perform a dedicated narrow range of functions as part

of large systems. Usually with minimal end user interactions, the 'giant leap technology' in

future embedded systems is based on instruction-oriented design but not on design-oriented

instructions. Embedded systems and real time operating systems (RTOS) are fast achieving

ubiquity, blurring the lines between science fiction and hard reality.

In general an RTOS has the following futures:

Multitaskin;

Process threads that can be prioritized;

A sufficient number of interrupt levels.

An embedded system is any device controlled by instructions stored on a chip. These devices

are usually controlled by a microprocessor that executes the instructions stored on a ROM

chip. Embedded systems are used in navigation tools like global positioning system (GPS),

automated teller machines (ATMs), networking equipment, digital video cameras, mobile

phones, aerospace applications, telecom applications, etc. We concern ourselves with the

development and implementation of model-based, real-time, embedded, hybrid control

software. In particular, we target intelligent cruise control applications, including Adaptive

Cruise Control (ACC), in which a forward-looking range sensor (radar or Lidar, usually) is

used to follow a vehicle, and Cooperative ACC (CACC), a variation in which wireless

communications are used to supplement the forward looking sensor. We discuss modeling on

automated vehicles. Our approach emphasizes the maintenance of a single model throughout

the development process, with particular emphasis on "tight-loop."

2.4 Theme

Embedded systems are usually low cost and are easily available off the shelf for most

applications. They usually have low design risks, since it is easy to verify the design using

tools fueling the growth of embedded systems.

Embedded systems have received a major shot in the arm as the result of three developments:

The first was the development of standard run-time platforms like java, which enabled

their use in myriad ways that were unimaginable in the past.

The second was the coming together of embedded systems and the Internet, which

made possible the networking of several embedded systems to operate as part of a

large system across networks.

The third was the emergence of several integrated software environments, which

simplified the implementations of these applications.

During operation, the design structure may be changed as per our tasks. For example,

consider two transistors; we can mould them using other passive elements as emitter coupled

circuit, Darlington pair, etc., as per instruction. Real Time Applications Automobiles: Almost

every car that rolls off the production line these days makes use of embedded technology in

one form or the other; most of the embedded systems in automobiles are rugged in nature, as

most of these systems are made up of a single chip. No driver clashes or 'systems busy'

conditions happen in these systems. Their compact profiles enable them to fit easily under the

cramped hood of a car. These systems can be used to implement features ranging from

adjustment of the suspension to suit road conditions and the octane content in the fuel to

antilock braking systems (ABS) and security systems.

Figure 2.2: Embedded System In A Car

Embedded systems can also make drive-less vehicle control a reality. Major automobile

manufacturers are already engaged in work on these concepts. One such technology is

Adaptive Cruise control (ACC) from Ford. ACC allows cars to keep safe distances from

other vehicles on busy highways. The driver can set the speed of his car and the distance

between his car and others. He can over side the system anytime he wants by braking. Each

car with ACC has a microwave radar unit or laser transceivers fixed in front of it to determine

the distance and relative speed of any vehicle in its path. The ACC computer constantly

controls the throttle and brakes of the car.

Another revolution is the way Internet services will be integrated into the car. So when you

drive past your mechanic's, you will be reminded that that your engine oil needs a refill, and

when you cross the city limits, the toll will automatically get deducted from your bank

account. And while passing the shopping mail, your PDA, which is connected to the Net via

the car, will inform you about a new scale. In fact, the automatic to;l deduction concept is

already in effect in several countries around the globe.

Figure 2.3: Design Flow Chart

Hybrid verification of the controller and analysis of timing properties are conducted through

the use of third party tools. GPS AIR BAG WINDOWS DEEBOSTER AUTOMATIC

TRANSACTION CONTROL ABS The approach is applied to Adaptive Cruise Control

(ACC) and Cooperative ACC systems. While regular cruise control systems track a desired

vehicle speed, Adaptive Cruise Control (ACC) systems adapt their behavior if there is a

vehicle ahead on the roadway, and follow the leader vehicle at a driver requested time gap

using line-of-sight sensors such as radar and/or Lidar. When there is no "leader" vehicle

present, ACC defaults to conventional cruise control and reverts to the driver-set speed. ACC

systems are now available on several production cars, including the Nissan Q45 and FX45,

the Mercedes S-class, the Lexus 330 and 430, the Audi A8, and select Jaguar and Cadillac

models. These production ACC systems obtain their distance and closing rate information

about the leading vehicle through the use of their forward-looking sensor. These sensors are

typically subject to noise, interference, false alarms and dropouts, and their use requires

heavy filtering. This in turn introduces delays into the system, and limits the ability of the

ACC-equipped vehicles to follow the leader vehicle closely or respond quickly to change in

its speed. A variant of this is Cooperative ACC (CACC), where the forward-looking sensor is

complemented by a wireless communication link that provides hop-by-hop, leader-to-

follower updates of critical information. Such a system can be designed to follow vehicles

with higher accuracy and faster response than traditional ACC systems, and should allow for

freeway throughput capacity increases. In addition, the CACC system can be designed to

have proven string stability, so it could contribute to dampening shock waves in the freeway

traffic stream.

CHAPTER 3: Training Work

3.1 What Is An Embedded System

An embedded system is a special-purpose system in which the computer is completely

encapsulated by the device it controls. Unlike a general-purpose computer, such as a personal

computer, an embedded system performs pre-defined tasks, usually with very specific

requirements. Since the system is dedicated to a specific task, design engineers can optimize

it, reducing the size and cost of the product. Embedded systems are often mass-produced, so

the cost savings may be multiplied by millions of items.

Handheld computers or PDAs are generally considered embedded devices because of the

nature of their hardware design, even though they are more expandable in software terms.

This line of definition continues to blur as devices expand.

The first recognizably modern embedded system was the Apollo Guidance Computer,

developed by Charles Stark Draper at the MIT Instrumentation Laboratory. Each flight to the

moon had two. They ran the inertial guidance systems of both the command module and

LEM.

At the project's inception, the Apollo guidance computer was considered the riskiest item in

the Apollo project. The use of the then new monolithic integrated circuits, to reduce the size

and weight, increased this risk.

The first mass-produced embedded system was the Automatics’ D-17 guidance computer for

the Minuteman missile, released in 1961. It was built from discrete transistor logic and had a

hard disk for main memory. When the Minuteman II went into production in 1966, the D-17

was replaced with a new computer that was the first high-volume use of integrated circuits.

This program alone reduced prices on quad NAND gate ICs from Characteristics. Embedded

systems are designed to do some specific task, rather than be a general-purpose computer for

multiple tasks. Some also have real-time performance constraints that must be met, for reason

such as safety and usability; others may have low or no performance requirements, allowing

the system hardware to be simplified to reduce costs.

For high volume systems such as portable music players or mobile phones, minimizing cost

is usually the primary design consideration. Engineers typically select hardware that is just

“good enough” to implement the necessary functions. For example, a digital set-top box for

satellite television has to process large amounts of data every second, but most of the

processing is done by custom integrated circuits. The embedded CPU "sets up" this process,

and displays menu graphics, etc. for the set-tops look and feel.

The software written for embedded systems is often called firmware, and is stored in ROM or

Flash memory chips rather than a disk drive. It often runs with limited hardware resources:

small or no keyboard, screen, and little RAM memory.

Embedded systems reside in machines that are expected to run continuously for years without

errors and in some cases recover by them if an error occurs. Therefore the Software is usually

developed and tested more carefully than that for Personal computers, and unreliable

mechanical moving parts such as Disk drives, switches or buttons are avoided. Recovery

from errors may be achieved with techniques such as a watchdog timer that resets the

computer unless the software periodically notifies the watchdog.

3.2 User Interfaces:

Embedded systems range from no user interface at all - dedicated only to one task - to full

user Interfaces similar to desktop operating systems in devices such as PDAs. In between are

devices with small character- or digit-only displays and a few buttons. Therefore usability

considerations vary widely.

On larger screens, a touch-screen or screen-edge soft buttons also provides good flexibility

while minimizing space used. The advantage of this system is that the meaning of the buttons

can change with the screen, and selection can be very close to the natural behavior of

pointing at what's desired.

So, user interface of embedded system is very friendly and can be easily understand by user

due to its nature.

3.3 Application of Embedded System:-

Automatic teller machines (ATMs)

Avionics, such as inertial guidance systems, flight control hardware/software and

other integrated systems in aircraft and missiles

Cellular telephones and telephone switches

Computer equipment such as routers and printers

Engine controllers and antilock brake controllers for automobiles

Home automation products, like thermostats, air conditioners, sprinklers, and security

monitoring systems

Handheld calculators

Household appliances, including microwave ovens, washing machines, television sets,

DVD players/recorders

Medical equipment

Handheld computer

Videogame consoles

3.4 Which processor should we use?

When desktop developers first think about working with embedded systems, there is a

natural inclination to stick with what they know and look for a book which uses Pentium

processors or other devices from this family (such as the 80486, or the Intel 188).

However, if we open up the engine management unit or the airbag release system in our

car, or take the back off our dishwasher, you will not find any of these processors sitting

inside, nor will there be anywhere to plug in a key-board, graphics display or mouse.

Typical desktop processors cost more than $100.00 a piece (often much more). This cost

puts them out of reach of all but the most expensive embedded application. (Who would

pay more than $100 for a TV remote-control unit?) In addition, a desktop processor

requires numerous external support chips in order to function: this further increases the

cost. The additional components also increase the physical size of the system, and the

power consumption: both of these factors are major problems for battery-powered

embedded devices. (Who would buy a portable music player that requires ten large

batteries to run, and needs a trolley to transport it?)

Overall, the state-of-the art technology used in desktop processors matches the needs of

the PC user very well: however, their key features – an ability to execute industry-

standard code at a rate of more than 1000 million instructions per second – come with a

heavy price tag and are simply not required in most embedded systems.

3.5 Which programming language should we use?

processor as the basis of your embedded system, the next key decision that needs to be

made is the choice of programming language. In order to identify a suitable language

for embedded systems, we might begin by making the following observations:

Computers (such as microcontroller, microprocessor or DSP chips) only accept

instructions in ‘machine code’ (‘object code’). Machine code is, by definition, in

the language of the computer, rather than that of the programmer. Interpretation

of the code by the programmer is difficult and error prone.

All software, whether in assembly, C, C++, Java or Ada must ultimately be trans -

lated into machine code in order to be executed by the computer.

There is no point in creating ‘perfect’ source code, if we then make use of a poor

translator program (such as an assembler or compiler) and thereby generate

executable code that does not operate as we intended.

Embedded processors – like the 8051 – have limited processor power and very

limited memory available: the language used must be efficient.

To program embedded systems, we need low-level access to the hardware: this

means, at least, being able to read from and write to particular memory loca tions

(using ‘pointers’ or an equivalent mechanism).

The language chosen should be in common use. This will ensure that we can

continue to recruit experienced developers who have knowledge of the language.

It will also mean that our existing developers will have access to sources of

information (such as books, training courses, WWW sites) which give examples

of good design and programming practice.

From one point of view, only machine code is safe, since every other language involves

a translator, and any code you create is only as safe as the code written by the

manufacturers of the translator. On the other hand, real code needs to be maintained and

re-used in new projects, possibly on different hardware: few people would argue that

machine code is easy to understand, debug or to port.

3.6 Why C language is mostly preferred for programming

It is ‘mid-level’, with ‘high-level’ features (such as support for functions and

modules), and ‘low-level’ features (such as good access to hardware via pointers).

It is very efficient.

It is popular and well understood.

Even desktop developers who have used only Java or C++ can soon understand C

syntax.

Good, well-proven compilers are available for every embedded processor (8-bit to 32-

bit or more).

Experienced staff are available.

Books, training courses, code samples and WWW sites discussing the use of the

language are all widely available


Recommended