Shalaka offers a wide range of hardware & software solutions for the automotive telematics, including car’s remote diagnostics and monitoring tools, and automated emergency call and roadside assistance (eCall, ERA GLONASS), telematics units (TUs), engine control units (ECUs), fleet management, Internet of Things (IoT), and more. We help process the sensor data and perform data analytics, business intelligence and data visualisation.
Our engineering team is working along side many experts to develop design telematic systems to be launched globally.
Benefits of working with Shalaka:
- 15 years of experience in developing sophisticated infotainment systems for the world-leading automakers
- In-house R&D lab that has developed award-winning product platforms
- Strong cross-company competencies, including IoT, Big Data, cloud, mobility and more
- Shalaka’s unique expertise in eCall / ERA GLONASS emergency response system
Shalaka provides full-cycle automotive-grade embedded hardware & software development and integration service. We offer a holistic approach to creating a digital experience in a car that encompasses in-vehicle systems, brought-in smart devices, and cloud. Offers years of in-depth knowledge in all aspects of in-vehicle software engineering, with a focus on the following these main areas:
- In-Vehicle Infotainment
- Head Units
- Digital Instrument Clusters
- Rear Seat Entertainment (RSE) systems
- Driver and passenger multimedia and entertainment
- NDS mapping
- Routing and guidance solutions
- Car remote diagnostics
- Monitoring tools
- Automated emergency call and roadside assistance (eCall, ERA GLONASS)
- Wired and wireless technologies
- Smartphone integration
- Embedded Blink browser
- Integration with Internet of Things
- ADAS Integration
- Computer Vision engine
- Augmented Reality
On Board Diagnostics
The OBD (On-Board Diagnostic) connector is a hard-wired communication link to the ECU (Electronic Control Unit) for connected car industry only, through which is allowed access to read and reset a vehicle’s fault codes. In today’s vehicles, there are more various on-board computer modules, dedicated to different tasks throughout the vehicle. Also, the access to that different diagnostic information of the modules is via the diagnostic connector. In most vehicles, there is only one OBD-II connector in the vehicle through which all systems can be diagnosed and programmed.
We provide services in Telematics alongside automotive electronics.
We offer more than just in car Wi-Fi and offer the following features:
Built-in GSM, GPS & G-force sensors
Vehicle location, status and condition (alerts, reporting & recording)
Driver behaviour (analytics, scoring, alerts & reporting)
Driver & vehicle health alerts
OBD Level 1 & Level 2 Diagnostics
Remote vehicle diagnostics
Online consultation with service technicians
Social platforms & smartphone apps
On-board Wi-Fi Hotspot
Live vehicle tracking
E-Zones – alerts when entering or leaving user define areas such as work/home
Security alerts – notification when car starts or is moving
Recorded journeys with playback
Driver behaviour & fuel efficiency
Vehicle status and health reports
DPF regen due in X miles, etc.
Vehicle status alerts
DTCs, battery voltage, seat belts use, etc.
Driver smartphone apps
Driver feedback (driving style, behaviour and fuel efficiency)
Brief about OBDII Below
OBD-II Diagnostic Connector Pin Layout
Since the introduction of the OBD-II standard, the connector, and the pin-out arrangement are now the identical in all vehicles. Figure 1 shows the standard female 16 pin (2 rows of 8 pins) J1962 interface connector, and assignment.
Some pins are standard and required by all manufacturers while others (Manufacturer Specific) are left to the individual discretion of manufacturers. The communication bus lines are used for data transmission, ISO lines provide data transfer for many vehicles, and the manufacturer specific terminals can be used for any purpose the manufacturer chooses.
Figure 1. OBD-II Connector Interface and Pin Layout:
Pin 1. Manufacturer Specific
Pin 2. Bus (+) Positive Line
Pin 3. Manufacturer Specific
Pin 4. Chassis Ground
Pin 5. Signal Ground
Pin 6. CAN High
Pin 7. ISO K Line
Pin 8. Manufacturer Specific
Pin 9. Manufacturer Specific
Pin 10. Bus (–) Negative Line
Pin 11. Manufacturer Specific
Pin 12. Manufacturer Specific
Pin 13. Manufacturer Specific
Pin 14. CAN Low
Pin 15. ISO L Line
Pin 16. Battery Voltage
OBD Diagnostic Connector Location
Typically OBD-II connector is located on the driver’s side of the passenger compartment, close to the steering wheel or gear-stick center console for easy access by the diagnostic technicians from both, the passenger’s side, as well from outside the vehicle. Unlike OBD-II connector where it’s standardized to be within 0.6 m (24 inch) of the steering wheel area or within reach of the driver, an OBD-I connector may be located in other areas, such as under the hood in engine compartment nearby the brake booster for example.
OBD-II Fault Codes Explained
Fault codes also known as diagnostic trouble codes (DTCs) typically are made up of a letter followed by four numbers, so each code has a total of five characters.
Here is an identification of the used characters:
Bxxxx – Body Systems (lighting, airbags, climate control system, etc.)
Cxxxx – Chassis Systems (anti-lock brake system, electronic suspension and steering systems, etc)
Pxxxx – Powertrain Systems (engine, emission and transmission systems)
Uxxxx – Network Communication and Vehicle Integration Systems (controller area network wiring bus and modules, etc)
x0xxx – Standardized ISO/SAE Code
x1xxx – Manufacturer Specific Code
x2xxx – Manufacturer Specific Code or ISO/SAE Code
x3xxx – Manufacturer Specific Code or ISO/SAE Code
xx0xx – Overall System
xx1xx – Secondary Air Injection System
xx2xx – Fuel System
xx3xx – Ignition System
xx4xx – Exhaust Monitoring System
xx5xx – Idle Speed Control or Cruise Control
xx6xx – Input / Output Signal from Control Units
xx7xx – Transmission System
xx8xx – Transmission System
xx9xx – Transmission System
Fourth and Fifth Character:
xxxXX – Refers to the actual component that the ECU has identified with a fault.
Figure 2. OBD-II Code Reader – How to Read Fault Codes
Let’s look at the code P0302 as an example:
• The first character of the code is a letter designation to indicate the general subsystem that sets the code. In this case (P) indicate to powertrain.
• The second numeric character (0) shows that this is a generic (SAE or ISO) code.
• The third numeric character denotes the subsystem affected. In this case, (3) indicates an ignition system misfire.
• The final two numeric characters indicate a code number that identifies a specific fault in a circuit or component, and will often define the type of fault being experienced. In this case, (02) indicates for misfire detected in the 2nd cylinder
ADAS & Autonomous Driving
Shalaka’s Computer Vision and Augmented Reality solution is a combination of software framework and engineering services. The software framework is optimized for embedded hardware that helps implement a wide range of in-car Advanced Driver Assistance Systems (ADAS) and autonomous driving functionality quickly and cost-efficiently.
Incorporating artificial intelligence, pattern recognition, image processing, real-time signal processing and more, the feature-rich and robust solution encompasses augmented navigation, advanced parking assistance and adaptive cruise control, driver infographics and lane keeping, driver health monitoring, support of low visibility mode and autonomous driving. The framework augments drivers’ visual reality with supplementary objects in real time, and works with various output devices such as head unit displays, digital clusters, head-up and optical head-mounted displays.
Quality Assurance (QA) Services
Quality is critical in the automotive sector; therefore, Shalaka is committed to quality.
Shalaka uses and applies the Automotive Process Assessment Model for software process capabilities. We have an independent test team and test laboratories where we conduct our research and perform the manual and automated testing for every module, system, and solution we develop for our partners. Shalaka also tests products developed by our partners. The testing of the third-party automotive technology algorithms, modules, and systems is one of the most valuable elements of Shalaka’s services for the automotive sector.
Performance testing and hardware/software optimization are standard validation services, along with the design and development of background diagnostics and runtime modules such as POST. Shalaka provides premium vehicle hardware support and testing for our hardware designs.
Shalaka has established comprehensive, automated test standards for most vehicle platforms and technologies and our test laboratories are equipped with the most advanced optimizers, CAN simulators, Bluetooth sniffers, signal analyzers and other test units required for successful testing of complex automotive solutions. It is our investment in the safety and quality of automotive technologies.