Want to switch your career in to Autosar? Looking for interview question and answers to clear the Autosar interview in first attempt. Then we have provided the complete set of Autosar interview question and answers on our site page. To be precise about Autosar, AUTOSAR (AUTomotive Open System ARchitecture) is a worldwide expansion partnership of vehicle suppliers, manufacturers, service providers and companies from the automotive electronics, semiconductor and software industry. If you are good at Autosar concepts then there are various leading companies that offers job in various roles like Software Engineer - Embedded/Autosar, Autosar Engineer, Autosar Architect, Autosar COMMS Engineer, Team Lead/Technical Lead, Senior Software Engineer-Autosar and along with that there are many other roles too. For more details on Autosar jobs and interview question and answers visit our site www.wisdomjobs.com.
AUTOSAR (Automotive Open System Architecture) is a standardization initiative of leading automotive manufacturers and suppliers that was founded in autumn of 2003. The goal is the development of a reference architecture for ECU software that can manage the growing complexity of ECUs in modern vehicles.
An SWC file is a package of precompiled Flash symbols and ActionScript code that allows a Flash or Flex developer to distribute classes and assets, or to avoid recompiling symbols and code that will not change. ... They are sometimes referred to as class libraries and cannot be directly executed by the Flash Player.
1. CAN is a multi-master broadcast serial bus standard for connecting electronic control unit (ECUs).
2. Controller–area network (CAN or CAN-bus) is a vehicle bus standard designed to allow microcontrollers a devices to communicate with each other within a vehicle without a host computer.
3. CAN is a message-based protocol, designed specifically for automotive applications but now also used in other areas such as industrial automation and medical equipment.
4. The Controller Area Network (CAN) bus is a serial asynchronous bus used in instrumentation applications for industries such as automobiles.
To minimize the reflection reference, to reduce noise. To ensure that reflection does not cause communication failure, the transmission line must be terminated.
CAN protocol is a message-based protocol, not an address based protocol. This means that messages are not transmitted from one node to another node based on addresses. Embedded in the CAN message itself is the priority and the contents of the data being transmitted. All nodes in the system receive every message transmitted on the bus (and will acknowledge if the message was properly received). It is up to each node in the system to decide whether the message received should be immediately discarded or kept to be processed.
A single message can be destined for one particular node to receive, or many nodes based on the way the network and system are designed. For example, an automotive airbag sensor can be connected via CAN to a safety system router node only. This router node takes in other safety system information and routes it to all other nodes on the safety system network. Then all the other nodes on the safety system network can receive the latest airbag sensor information from the router at the same time, acknowledge if the message was received properly, and decide whether to utilize this information or discard it.
Wired AND logic.
CAN Arbitration is nothing but the node trying to take control on the CAN bus.
CSMA/CD + AMP (Arbitration on Message Priority)
Two bus nodes have got a transmission request. The bus access method is CSMA/CD+AMP (Carrier Sense Multiple Access with Collision Detection and Arbitration on Message Priority). According to this algorithm both network nodes wait until the bus is free (Carrier Sense). In that case the bus is free both nodes transmit their dominant start bit (Multiple Access). Every bus node reads back bit by bit from the bus during the complete message and compares the transmitted value with the received value.
As long as the bits are identical from both transmitters nothing happens. The first time there was a difference – in this example the 7th bit of the message – the arbitration process takes place: Node A transmits a dominant level, node B transmits a recessive level. The recessive level will be overwritten by the dominant level.
This is detected by node B because the transmitted value is not equal to the received value (Collision Detection). At this point of time node B has lost the arbitration, stops the transmission of any further bit immediately and switches to receive mode, because the message that has won the arbitration must possibly be processed by this node (Arbitration on Message Priority)
For example, consider three CAN devices each trying to transmit messages:
• Device 1 – address 433 (decimal or 00110110001 binary)
• Device 2 – address 154 (00010011010)
• Device 3 – address 187 (00010111011)
Assuming all three see the bus is idle and begin transmitting at the same time, this is how the arbitration works out. All three devices will drive the bus to a dominant state for the start-of-frame (SOF) and the two most significant bits of each message identifier.
Each device will monitor the bus and determine success. When they write bit 8 of the message ID, the device writing message ID 433 will notice that the bus is in the dominant state when it was trying to let it be recessive, so it will assume a collision and give up for now. The remaining devices will continue writing bits until bit 5, then the device writing message ID 187 will notice a collision and abort transmission. This leaves the device writing message ID 154 remaining.
It will continue writing bits on the bus until complete or an error is detected. Notice that this method of arbitration will always cause the lowest numerical value message ID to have priority. This same method of bit-wise arbitration and prioritization applies to the 18-bit extension in the extended format as well.
40m @1Mbps and if the cable length increases will decrease the speed, due to RLC on the cable.
Starts from MSB, first nibble is same, Master sends 7, slaves also sends 7 the message with more dominant bits will gain the arbitration, lowest the message identifier higher the priority.
Number of identifiers can be accommodated for standard frame are 2power11.
Number of identifiers more compare to base frame, for extended frame are 2power29.
CAN uses a Non-Return-to-Zero protocol, NRZ-5, with bit stuffing. The idea behind bit stuffing is to provide a guaranteed edge on the signal so the receiver can resynchronize with the transmitter before minor clock discrepancies between the two nodes can cause a problem. With NRZ-5 the transmitter transmits at most five consecutive bits with the same value. After five bits with the same value (zero or one), the transmitter inserts a stuff bit with the opposite state.
Long NRZ messages cause problems in receivers:
• Clock drift means that if there are no edges, receivers lose track of bits.
• Periodic edges allow receiver to resynchronize to sender clock.
The transceiver provides differential transmit capability to the bus and differential receive capability to the CAN controller. Transceiver provides an advanced interface between the protocol controller and the physical bus in a Controller Area Network (CAN) node.
Typically, each node in a CAN system must have a device to convert the digital signals generated by a CAN controller to signals suitable for transmission over the bus cabling (differential output). It also provides a buffer between the CAN controller and the high-voltage spikes that can be generated on the CAN bus by outside sources (EMI, ESD, electrical transients, etc.).
The can transceiver is a device which detects the signal levels that are used on the CAN bus to the logical signal levels recognized by a microcontroller.
LLC (Logical Link Control): Overload control, notification, Message filtering and Recovery management functions.
MAC (Medium Access Control): Encapsulation/ de-capsulation, error detection and control, stuffing and de-stuffing and serialization/de-serialization.
Synchronization is timekeeping which requires the coordination of events to operate a system in unison.
Hard Synchronization to be performed at every edge from recessive-to-dominant edge during Bus Idle. Additionally, Hard Synchronization is required for each received SOF bit. An SOF bit can be received both during Bus Idle, and also during Suspend Transmission and at the end of Interframe Space. Any node disables Hard Synchronization if it samples an edge from recessive to dominant or if it starts to send the dominant SOF bit.
Two types of synchronization are supported:
Functional addressing is an addressing scheme that labels messages based upon their operation code or content. Physical addressing is an addressing scheme that labels messages based upon the physical address location of their source and/or destination(s).
KWP 2000(ISO14230) is a Diagnostic communications standard. Specifies possible system configurations using the K & L lines. As 9141-2 but limited to the physical characteristics. Specifies possible system configurations using the K & L lines.
5 Baud wake up as 9141- 2
New fast initialisation method
On-Board Diagnostics in an automotive context is a generic term referring to a vehicle’s self-diagnostic and reporting capability.
As systems got more complex the link between cause and symptom became less obvious. This meant that electronic systems had to have some level of self diagnosis and to communicate to the outside world. Initially many systems used their own protocols which meant that garages had to have a large number of tools – even to diagnose a single vehicle.
Verification and Validation (V&V) is the process of checking that a software system meets specifications and that it fulfills its intended purpose. It is normally part of the software testing process of a project.
According to the Capability Maturity Model (CMMI-SW v1.1),
Verification: The process of evaluating software to determine whether the products of a given development phase satisfy the conditions imposed at the start of that phase.
Validation: The process of evaluating software during or at the end of the development process to determine whether it satisfies specified requirements.
Verification shows conformance with specification; validation shows that the program meets the customer’s needs.
No that would produce a bus conflict.
• Unless you have middleware that ensures only one node can transmit at a time.
For example: use a low priority message as a token to emulate token-passing.
The baud rate is calculated as:
baud rate (bits per second) = 18.432 x 10^6 / BRP / (1 + TSEG1 + TSEG2)
Two nodes on the network are not allowed to send messages with the same id. If two nodes try to send a message with the same id at the same time arbitration will not work. Instead, one of the transmitting nodes will detect that his message is distorted outside of the arbitration field.
The nodes will then use the error handling of CAN, which in this case ultimately will lead to one of the transmitting node being switched off (bus-off mode).
AUTOSAR Related Tutorials
|Git (software) Tutorial||Software testing Tutorial|
|Puppet (software) Tutorial||Adaptive software development Tutorial|
AUTOSAR Related Interview Questions
|Systems Software Interview Questions||Application Software Interview Questions|
|Git (software) Interview Questions||Software testing Interview Questions|
|Puppet (software) Interview Questions||Eclipse (software) Interview Questions|
|Orbix (software) Interview Questions||Salt (software) Interview Questions|
|Ansible (software) Interview Questions||Embedded C Interview Questions|
|Scalable Software Interview Questions|
All rights reserved © 2020 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.