Search icone
Search and publish your papers

Development of a simulator for radar interface in Bharat Electronics Limited

Or download with : a doc exchange

About the author

Level
Expert

About the document

Published date
Language
documents in English
Format
Word
Type
thesis
Pages
52 pages
Level
Expert
Accessed
2 times
Validated by
Committee Oboolo.com
0 Comment
Rate this document
  1. Company profile
    1. Development and engineering (D & E) department
  2. Introduction to the project
    1. Objective
  3. Concept of simulation
  4. Rotation
    1. Test equipment and automation
    2. PCB fabrication
    3. Quality control (works)
    4. Works assembly
    5. Magnetic
    6. Microwave lab
    7. P&S electrical
  5. C language
  6. Socket programming
  7. Software engineering paradigm
    1. Object modeling technique (OMT) model
  8. System analysis
    1. Identification of need
    2. Preliminary investigation
  9. Software requirements specification
    1. Components of an SRS
    2. Hardware and software requirements
  10. Object design
    1. Combining three models
  11. Coding
  12. Testing
  13. Future scope of the project
  14. Conclusion
  15. References

Bharat Electronics Limited (BEL) was established in 1954 as a public sector enterprise under the Ministry of Defense. BEL, a premier Professional Electronics Company of India, has established and nurtured a strong in-house R&D base over the years to emerge and remain as a market leader in the chosen areas of business in professional electronics. Each of the nine manufacturing units of BEL has its own in-house R&D Division to develop new products in its field of operations. In its quest for technical excellence, BEL has set up independent R&D divisions in each of its nine units and strengthened them over time. A continuous effort, BEL to improve its technology base has resulted in a wide range of more than 350 products. Realizing the need for an indigenous base for strategic components; design, development and manufacture of defense grade electronic components are taken up, as also general-purpose components for entertainment electronics sector. BEL in association with ?Defense Research and Development Organization' (DRDO) laboratory has made tremendous development in the field of Radar technology. In the defense communication technique, BEL is in the final stages of introducing Radio Communication equipment with frequency hopping for the services. The ability to manufacture command.

[...] This structure holds socket address information for many types of sockets: struct sockaddr { unsigned short sa_family; address family, AF_xxx char sa_data[14]; 14 bytes of protocol address sa_family can be a variety of things, but it'll be AF_INET for everything we do in this document. sa_data contains a destination address and port number for the socket. This is rather unwieldy since you don't want to tediously pack the address in the sa_data by hand. To deal with struct sockaddr, programmers created a parallel structure: struct sockaddr_in for "Internet".) struct sockaddr_in { short int sin_family; Address family unsigned short int sin_port; Port number struct in_addr sin_addr; Internet address unsigned char sin_zero[8]; Same size as struct sockaddr This structure makes it easy to reference elements of the socket address. [...]


[...] It allows you to cut off communication in a certain direction, or both ways (just like close() does.) Synopsis: int shutdown(int sockfd, int how); sockfd is the socket file descriptor you want to shutdown, and how is one of the following: 0 Further receives are disallowed 1 Further sends are disallowed 2 Further sends and receives are disallowed (like close()) shutdown() returns 0 on success, and on error (with errno set accordingly.) If you deign to use shutdown() on unconnected datagram sockets, it will simply make the socket unavailable for further send() and recv() calls (remember that you can use these if you connect() your datagram socket.) It's important to note that shutdown() doesn't actually close the file descriptor--it just changes its usability. [...]


[...] Actually, there's a cleaner interface you can use instead of inet_addr(): it's called inet_aton() ("aton" means "ascii to network"): #include #include #include int inet_aton(const char struct in_addr And here's a sample usage, while packing a struct sockaddr_in (this example will make more sense to you when you get to the sections on bind() and connect().) struct sockaddr_in my_addr; my_addr.sin_family = AF_INET; host byte order my_addr.sin_port = htons(MYPORT); short, network byte order inet_aton(" &(my_addr.sin_addr)); memset(&(my_addr.sin_zero), zero the rest of the struct inet_aton(), unlike practically every other socket-related function, returns non-zero on success, and zero on failure. [...]

Recent documents in computer science category

Net neutrality in United States

 Science & technology   |  Computer science   |  Presentation   |  10/02/2018   |   .doc   |   3 pages

Reconstructing householder vectors from tall-skinny QR

 Science & technology   |  Computer science   |  Presentation   |  04/21/2017   |   .doc   |   4 pages