×

Happy to Help!

This website doesn't store cookies. Enjoy the experience, without worrying about your data!

Great, thanks!

Monthly Archives: June 2020

  • June 22, 2020
  • 0

IoT Cloud Architecture Insights – Why Database Design Matters

Category : iot-insights

 
The Internet of Things (IoT) has penetrated our lives in multiple ways. Some incarnations of these IoT systems are Smart Homes, Connected Cars, Smart Factories, and Smart Grids that consolidate/manage office data.

In all these use cases, an IoT cloud architecture is introduced when there is a need to process and analyse large data sets.

The exceptional opportunities that cloud computing promises, have encouraged organisations to seek implementation of this service in their business operations. However, the vast number of devices and conditions to be satisfied to make IoT work, may be a deterrent in many cases. This is where the services of a reliable full-stack IoT solutions provider can prove to be invaluable.

To achieve the expected results, the IoT cloud platform should be robust, scalable and agile with impeccable security features. The components of the cloud architecture should also work together seamlessly.

Here we explore the various aspects of IoT cloud architecture, with special focus on the database design factors.

Layers of Cloud Architecture for IoT

In an IoT cloud architecture, the data flows across many layers. Although the actual cloud platform configuration may differ between organisations, all these solutions accomplish the same basic objective.

This encompasses allowing different devices to connect to the network, processing the data and utilizing the insights gained for automation. A significant part of the data processing takes place in the cloud databases and reporting layer.

Let us take a look at the basic components of an IoT architecture.

IoT Cloud Architecture

 
 

  1. IoT Devices

    2. The device integrates with sensors or actuators and establish a connection with the IoT Integration Middleware. In some use cases, multiple devices may be grouped together and connected to an IoT gateway infrastructure that transmits device data to the IoT Integration Middleware. The devices have drivers, i.e., software that enables access to the sensors/actuators.

  2. IoT Integration Middleware

    3. The IoT Integration Middleware is an integration layer for various devices when connecting with the cloud. It receives data from the connected devices, processes it and transmits this information to downstream applications. The processing of data may include the evaluation of condition-action rules, and deployment of commands to the device sensors based on the evaluation.

    If the device supports a suitable communication technology (WiFi or IP over Ethernet), a transport protocol such as MQTT or HTTP and a compatible payload format, it can transmit data directly to the Integration Middleware. Otherwise, an IoT gateway has to be installed in between for communication with the middleware platform.
    The middleware broker also ensures that there is no loss of data, since asynchronous communication is established with the connected device.

  3. Cloud Servers

    4. Servers are the most important part of the IoT cloud, as these are needed for providing business services to customers. These are virtual machines linked to individual databases.

  4. Databases

    5. Based on the business requirements for data storage and processing, SQL and No SQL databases can be configured on the IoT cloud. SQL databases store data in the form of two-dimensional tables. The main disadvantage of this kind of database is its performance. No SQL databases are much more efficient and real-time.

  5. Downstream Applications/BI Tools

    6. The cloud servers are connected to third-party apps, mobile/web applications or business intelligence tools through REST API endpoints.

    When a large number of IoT devices and applications are connected to the IoT cloud platform, the cloud application servers will have to transfer a huge amount of data. In order to streamline this, load balancing is enforced. This ensures even distribution of workload across the backend servers and improves efficiency.

 

IoT Cloud Architecture – Database Design Best Practices

While designing the database for an IoT cloud, there are several points to be considered. An experienced IoT cloud architecture development company can help you identify the right kind of database for a specific business use case.

Some technical aspects of designing a cloud database are given below.

  • Questions to be asked while determining the type of database for a cloud architecture are:
    • Is the consistency of data important for the implementation?
    • Is high availability of data a crucial aspect of the project?
    • In case of downtime in data availability, would there be serious repercussions?

    If there is a requirement to handle a large amount of data, No SQL database can be utilized.

  • Another point to be considered when selecting No SQL database is the type of analysis that will be performed with the data.
    • Are we dynamically generating reports from the data/insights?
    • Is there a need to perform time-series analysis of data?

    Sometimes, the data collected is integrated with a Business Intelligence tool for generating insights. In this case, the data can be stored in a cloud database or data lake, and an API can be developed for the BI tool to access the data.

  • At the time of database design, the assessment of value of data should not be missed. For instance, on a telematics platform, accidental alert is critical information. It is important that a reliable protocol is used for communication between the device and the cloud platform to ensure there is no data loss. The asynchronous communication between the devices and cloud servers can be managed efficiently by deploying an MQTT Cluster.

  • Scalability of the IoT cloud platform should also be taken into account when designing the No SQL database. If there is an unprecedented need to integrate a large number of devices in the future, the cloud solution should be able to handle it. Hence, this should be a point in the checklist in the database design phase itself.

  • Optimization is another aspect to be considered while selecting the cloud database. It is crucial to determine the amount of time the data needs to be stored.
    • Is it necessary to store the data for an extended period of time?
    • Does the business requirement include storage of both data and insights?

    Let us examine this in detail. In some use cases, the data collected throughout a couple months can be stored in an SQL database if only the reporting aspect is required. Once the reports are generated, the data can be deleted.

    An example of this is predictive maintenance. In such a setup, there is a need to perform time-series analysis of data. The system collects the health information of the monitored devices on a periodic basis. There will be a large amount of data collected this way. If this information is stored for a year or so and then time-series analysis is performed, it is possible to generate some insights. Following this, the data can be discarded.

    Likewise, there are also use cases where there is no need to store the data beyond a short period of time. For example, if we are tracking the location of a device for 5 days, we can reduce the load on the database by automatically deleting the data after the stipulated time period.

The aforementioned principles will help in optimizing database design and reducing overall cost of the solution.
 

Conclusion

The use cases covered by IoT will span across commercial, domestic, healthcare and industrial contexts in the future.

While designing a robust IoT infrastructure, it is crucial to lay a lot of emphasis on the IoT cloud architecture and cloud database design. The points mentioned in this article will provide a base for understanding the design requirements of IoT cloud databases. This also helps in mitigating design flaws that may be expensive to resolve in the future.
 

  • June 19, 2020
  • 0

Safety Analysis (FMEA, FMEDA) for ASIL C Compliant Automotive Lighting Solution

Category : Product Engineering , Vehicle Diagnostics

 

About the Customer

Our customer is an automotive Tier-1 supplier of vehicle ECU, lighting and various other automotive parts.

We have had a successful partnership on a futuristic project on automotive lighting. The mutual trust and respect were taken a few notches higher with this ISO 26262 project.

As our customer had previously worked with us, they were aware of our ISO 26262 capabilities and hence, we were the choice partners for this project.
 

Business Challenge

While working on an automotive lighting system, our customer realized the need for its ASIL C compliance. The lighting module’s proposed application in the vehicle system made it a safety-critical component.

Our customer, a pioneer in automotive components development did not have the ISO 26262 processes in place.

Setting up the processes, hiring ISO 26262 consultants, purchasing ISO 26262 qualified tool licenses and training the engineering team on ISO 26262 standard would escalate the project cost and increase time-to-market.

Moreover, the customer was looking for a technology partner that:

  • Could provide support for both qualitative as well as quantitative safety activities
  • Had prior experience of working on ASIL C compliant projects
  • Was able to perform both hardware and software safety analyses
  • Had expertise on ISO 26262 qualified tools like Tessy
  • Had experience of providing safety analysis activities for the entire safety lifecycle- Concept Phase to Product Development

The customer was aware of our maturity in ISO 26262 standard adoption, FuSa expertise and trained engineering team.
 

Embitel Solution

The customer required both qualitative and quantitative analysis of the software and hardware. Our FuSa team figured out that a series of safety analysis activities will need to be performed:

A snapshot of the solution provided by our team:

  • Safety management activities were planned as per ASIL C including safety plan and DIA (Development Interface Agreement).
  • We developed safety compliant hardware and software implementation for master and slave ECUs.
  • Our team performed System Failure Mode and Effects Analysis (FMEA).
  • ASIL C compliant Hardware and Software safety analyses were performed. This included:
    1. Software FMEA
    2. Hardware FMEA
    3. Dependent Failure Analysis (DFA)
    4. Fault Tree Analysis and HW FMEDA
  • Performed Static analysis using Polyspace.
  • Performed Unit testing using Tessy.
ASIL C Compliant Automotive

 

Embitel Impact

As deliverables of the project, we provided the work-products that were required for ASIL C compliance. These work-products included report of FMEA, FMEDA, FTA, DFA and other ISO 26262 compliant safety analysis.

As a result of these safety analyses, we were able to strengthen the existing safety mechanism of the system.

With a fully-trained and well-structured team of ISO 26262 experts, we were able to save a considerable amount of time for the customer. This led to a faster time-to-market for the lighting product.
 

Tools and Technologies

Enco SOX: Used for safety analysis like FMEA, FMEDA, etc.

Vector CANoe: Used to simulate vehicle ECU during functional testing

Polyspace: Helped in static analysis of the code as per the ISO 26262 guidelines

Tessy Tool: An ISO 26262 qualified tool, it is widely-used unit testing tool

  • June 19, 2020
  • 0

Configuration and Integration Support for ECU Communication and Diagnostics Protocols in a Telematics System

Category : Automotive control units-design and development , Product Engineering

 

About the Customer

Our customer is a leader in design and manufacturing of solutions across industries viz. automotive, IoT, healthcare and more.

Their solutions find application in autonomous driving, connected cars, medical devices, etc.

We had the opportunity to collaborate for an innovative Telematics system to power Fleet Management for both commercial and passenger vehicles.
 

Business Challenge

Communication is the backbone of any telematics devices inside a vehicle. Our customer had developed a state-of-the art telematics system to enable fleet management. However, the in-vehicle communication part was posing a challenge.

As the telematics system was designed for both passenger and commercial vehicles, several in-vehicle communication protocols were required to be implemented in the telematics ECU.

Further, the system also had to support older commercial vehicles that used almost obsolete communication protocols.

Developing all these proprietary protocol stacks required a dedicated team with specialized skills, as well as a number of licenses to be bought.

Getting in touch with a technology partner with ready-to-integrate protocol solution would not only reduce the cost but also ensure that the time-to-market is reduced considerably.

And that’s how this collaboration shaped up.
 

Embitel Solution

Following a series of discussions with the tech team of our customer, a list of communication protocols to be integrated was prepared.

Following protocol solutions were configured and integrated with the telematics platform:

  • CAN2.0 250/500
  • SAE J1939
  • SAE J1587 / J1708
  • Single Wire CAN2
  • Low Speed CAN2
  • K-Line
  • ISO9141
  • CAN FD
  • Unified Diagnostic System (ISO 14229)
  • TP2.0
  • Autoprotocol/ AutoBaud Detection
  • OBD Stack – CAN, Kline, ISO9141

Our library of pre-tested and ready-to-deploy automotive protocol solutions contains each of these stacks. The task at hand for the engineers was to configure these stacks based on the requirements of the project.

We performed the configuration of the PGNs, CAN messages and other services required for the telematics system to communicate with vehicle ECUs and devices outside of the vehicle.

For instance, Classic CAN messages were configured to the SAE J1939 protocol software with the help of CAN IL tool.

*Our proprietary CAN IL tool automates the configuration process that would otherwise take weeks if performed manually. Result is lesser turn-around time and reduced chance of human error creeping into the configuration process.

Integration support with the Application Layer and the Low-level driver was provided to the customer.

 

Embitel Impact

Our team could save 6 months of man hours for our customers, courtesy our ready-to-deploy protocol solutions and the proprietary CAN IL configuration tool.

As the customer was aiming for a faster time-to-market, we were able to provide all the require support for the same.
 

Tools and Technologies

Freematics: It was used as an OBD simulator that helped our team perform the functional testing of the OBD stack before deployment.

CANoe from Vector: Helped us simulate the other automotive protocol stacks for verification

SAMTEC: Helped us simulate some older protocols like K-Line.

CAN IL Tool: Used to configure required CAN messages in SAE J1939 and other protocol solutions.

  • June 17, 2020
  • 0

Implementation of Omnichannel Commerce Solution for Largest Electronics Retailer in the Middle East

Category : Digital Commerce , Stationery & Electronics

 

About the Customer

Our customer is the leading retailer of electronics and home appliances in the Middle East region. Offering more than 12,000 different products through their online and offline stores, the business has marked an exceptional growth rate in the past. They have more than 44 stores across several countries and have catered to 13 million+ shoppers.
 

Business Challenge

The existing ecommerce platform of the customer was a legacy system and suffered from:

  • Limited features which could not meet the business goals
  • Performance issues, especially during peak hours
  • A very basic UX and UI for both web and mobile apps which did not appeal to the shoppers
  • Scalability issues in terms of operations, features and performance

Our customer understood the need of a well-designed and robust Omnichannel Commerce Solution that could help them support future scalability of their operations, performance and business goals.

Their existing Technology Partner was unable to support the migration of the platform and develop a scalable solution. Embitel took up this challenge and delivered the solution successfully.
 

Embitel Solution

Following a series of discussions with the customer and their existing Technology Partner, Embitel arrived at the key features of the solution that would achieve their business goals:

  • A unified technology platform had to be implemented for the client’s physical Retail Stores, Warehouses and Online Stores.
  • The platform, when built on SAP Hybris and supported by other systems, could achieve the project requirements.
  • A Responsive Web App and Native Mobile Apps (Android & iOS) were to be deployed as the Storefront.
  • Web and Mobile Apps would cater to multiple countries and languages.
  • Integration of engaging UX, rich UI and a seamless experience across the Web App and Native Mobile Apps were required.
  • There was also a need for complex promotions at both product and order levels, integrated with RETEK.

Highlights of the Implementation:

The implementation of the end-to-end solution was extremely complex, and Embitel was able to effortlessly overcome the associated challenges.

An Offshore Delivery Center (ODC) was set up at the headquarters of Embitel Technologies (in Whitefield, Bangalore).

This development center served as a hub for all activities and personal interactions with the customer’s team as well.

During the project requirement gathering & analysis stage, Embitel was able to gauge the skills required for the implementation and deployed more than 40 ecommerce technology experts to the project accordingly. This comprised of:

  • Scrum Masters
  • Business Analysts
  • Technical Architects
  • Test Managers and Testers
  • Android Developers
  • iOS Developers
  • UX & UI Designers

The project was executed in Agile’s Scrum Methodology following all the Scrum Ceremonies.
 

Embitel Impact

The project was a huge undertaking considering the complexity of the technology solution that had to be implemented, cross functional skills that were required, the data across catalogue and customers, and the challenging delivery timelines.

Due to the Agile model, Embitel was able to continuously learn and adapt to challenges and hurdles throughout the project lifecycle.

The project was successfully delivered within the expected timeframe and the customer is now reaping immense benefits from the new platform.
 

Tools and Technologies

  • Ecommerce Platform: SAP hybris
  • PM Tool: JIRA and Confluence
  • June 15, 2020
  • 0

Implementation of Bharat EV Charger Protocol Based on SAE J1939 with CAN

Category : Embedded Blog

The emergence of gas stations has a fair bit of history- evolving from depots with hand-operated suction pumps to facilities with motorized fuel dispensers.

At its current stage, the entire operation of refueling an Internal Combustion (IC) engine car is not very complicated when compared to an Electric Vehicle. It merely requires the oil to be transferred from the underground gasoline tanks to the vehicle’s fuel tank with the help of a hose. There are no compatibility issues related to voltage, current, frequency, etc.

Coming to electric vehicle refueling, or better said, charging, it is a different story altogether. The petrol/diesel dispenser is replaced by an Electric Vehicle Supply Equipment (EVSE).

The battery pack inside the EV, the Charging Management System and the Electric Vehicle Supply Equipment (EVSE)– all three of these must be compatible and understand a common language of communication. Before the charging starts, it has to be ensured that the current, voltage, wattage, etc. are compatible and there is no risk to the safety of the car or its occupants.

How are all of these aspects managed? The answer is- Electric Vehicle charging protocols/standards

We have a separate blog that discusses the need for such protocols and the challenges in EV charging. You can read it here.

EV Charging Protocols

The communication between an Electric Vehicle and the Electric Vehicle Supply Equipment (EVSE) is based on certain Charging Protocols. Point to be noted here is that when we mention EVSE, it categorically implies public charging stations and not the regular AC charging sockets at home. Such distinction is important to mention as public charging also entails billing, an important factor to be considered. The charging protocols also manage the billing procedures.

Apart from billing, the role of EVSE is to ensure the safety of the car and the passenger during the charging. A threat can come in the form of unintended current flow, voltage fluctuations, or faults in the hardware inside the EV battery charging system.

The EV and EVSE manufactures and vendors require protocols/standards such as Bharat EV, CHAdeMO, CCS, etc. to enable safe connection between EV and EVSE.

These EV charging protocols or standards make sure that all the criteria of safe charging are fulfilled before the charging is initiated. They also monitor the vital parameters while the vehicle is being charged.

Since, there are several EV and EV charging system manufacturers spread across geographies, a number of EV charging protocols have also emerged.

One of these protocols that we will focus on in this blog, is specific to the Indian subcontinent. And hence the name, Bharat EV Charger (BEVC).

So before jumping to the implementation of BEVC, let’s first understand its finer details.

A Brief Overview of Bharat EV Charger Protocol

Bharat EV Charger (BEVC) protocol has been specifically designed for regulating the EV charging ecosystem in India.

This protocol supports both AC and DC charging with specifications clearly spelt out. A public metered AC outlet (PMAO) manages the AC charging with built-in billing module along with the safety and monitoring feature. AC charging (BEVC-AC001) is quite a slow mode of charging with a maximum current output of 15A. It is mostly used in low-powered EVs.

Compared to AC, the DC charging process is faster, and its implementation is also quite interesting.

So, let’s shift our focus to the DC charging specifications of Bharat EV standard and try to understand its implementation.

Understanding the Bharat EV Protocol Architecture

As per Bharat EV specifications, the communication between the EV and the Electric Vehicle Supply Equipment (EVSE)  is powered by GB/T 27390 protocol that is based on SAE J1939 with CAN as physical layer.

GB/T 27390 is a protocol proposed by China Electricity Council (CEC). Its communication is based on SAE J1939, an in-vehicle communication protocol widely used in commercial vehicles as well as a few passenger vehicles.

Bharat EV Charger standard adapts the GB/T 27930 by creating its customized version. Customizing this protocol implies adding certain PGNs in an existing SAE J1939 protocol solution. We will talk about that part in the next section. For now, let’s take a look at the architecture of BEVC.

Bharat EV

  • Communication details for charger(EVSE) is as follows:
    • The communication between the EVSE and battery management system (BMS) present in EV takes place with the help of GB/T 27930 with CAN as its physical layer.
    • Communication between EVSE and central management system(CMS) of the power utility company is through the open charge point protocol(OCPP), which is basically utilised for billing and controlling the charge rate.
    • Communication between user mobile and CMS is over the internet.

How Bharat EV Protocol is Implemented Using SAE J1939 Protocol Software

To establish the communication between the EV and the EVSE and initiate the charging, certain software requirements need to be fulfilled.

Software Requirement Between EVSE and EV:

  • The EVSE and EV communicate with each other for exchanging the initial handshaking messages.   The EVSE knows the type of EV battery using the handshake message. Also, in case the charge is being suspended, the reason is communicated to the EVSE.
  • GB/T 27930 protocol uses some standard defined PGNs for communication between EVSE and EV.

    •  
    GBT 27930

Adapting the GB/T protocol for Bharat EV Charger standard requires the configuration of certain PGNs (Parameter Group Number) and the corresponding SPNs (Suspect Parameter Number) in the SAE J1939 protocol stack.

“PGN is a part of 29 bit identifier that is sent with every CAN message. For example, Engine Temperature is a Parameter Group identified by the number 65262. When an ECU receives a CAN message, it looks up the PGN in the identifier to understand the type of data sent in the message.”

“SPN is a unique number assigned to every parameter within a Parameter Group. In essence, it describes the parameter by providing certain information about the parameter. For example, SPN 110 is the Engine Coolant temperature; hence, it will be a part of the PGN that represents Engine Temperature (PGN 65262).”

SAE J1939 is a widely used CAN based communication protocol and also forms the basis of the GB/T 27930 protocol used in BVEC. Configuration of the required PGNs in the SAE J1939 makes it equivalent to GB/T 27930 while still retaining its uniqueness.

Let’s have a look at the PGNs and SPNs that are configured in J1939 protocol stack.

 

PGN SPN USE
9728(Charger Handshake Message(CHM)) 2600 To differentiate between pure GB/T and proposed Indian version of standard specification of BEVC.
512(Vehicle and BMS Recognition Message(BRM)) 2565 To differentiate between the pure GB/T and Indian version of specification.
2566 To inform battery type
2567 Informs power storage battery system of the whole vehicle with rated capacity
6400(BMS Suspending Charging Message(BST)) 3511 Informs the cause for BMS suspending the charging.
3512 Indicates the fault cause for BMS suspending the charging.
3513 Conveys the error cause for BMS suspending the charging.
6656(Charger Suspending Message(CST)) 3521 Informs the cause for charger suspending the charging.
3522 Indicates the fault cause for the charger suspending the charging.
3523 Conveys the error cause for charger suspending the charging.

 

In addition to these PGNs and SPNs, few others are also configured as per the guidelines issued by the Government of India.

These PGNs can be configured to an existing J1939 protocol stack with the help of J1939 configuration tool and CAN IL tool. As PGNs are part of 29 bit CAN messages, the required PGNs and SPNs are added to the CAN messages required for EV and EVSE to communicate with each other.

Conclusion

SAE J1939 protocol software has been in use for several years now. Having an EV charger standard based on a proven vehicle communication protocol makes it more reliable and less prone to failure. Moreover, the tools for configuration of the required PGNs in an existing J1939 are also widely used and several automotive embedded development companies have such tools developed in-house. Bharat EV Charger standard, thus, appears quite promising in terms of making EV charging a less complicated affair. And in turn, it will steer more buyers towards electric vehicles.

  • June 15, 2020
  • 0

Development of Ecommerce Progressive Web App to Streamline Salesman-Retailer Engagement

Category : B2B & Sports , Digital Commerce

 

About the Customer

Our customer is the Asian subsidiary of a global manufacturer of consumer goods, managing hundreds of brands.

Business Challenge

The customer faced a unique impediment in supply chain management.

  • The products are usually transported from depots to distributors and then to retailers. These products are eventually ordered by end consumers and shipped to them.
  • While distributing products to retailers, salesmen played a crucial role in updating the retailers about ongoing offers, new products, etc. However, the salesmen inevitably spent a lot of time in physically taking the orders from retailers. This hampered the progress of their primary activities related to account management.
  • The retailers were also highly dependent on the salesmen visiting their stores to record orders.

Our vast experience in the digital transformation of global businesses gave confidence to the customer in partnering with us to find a solution for their issue.

Embitel Solution

Our ecommerce consultants analysed the problem and identified a solution to improve the efficiency of the process by streamlining salesman-retailer engagement.

  • We designed and developed a Progressive Web App (PWA) that can be easily used by salesmen and retailers.
  • The app could be effortlessly installed on the mobile phones of the users and would help them in placing/fulfilling orders.

Key Features:

  • The Magento instance we developed for this project supports multiple stores and each store supports multiple languages.
  • A salesman can open the app from the home screen of his mobile phone and log in to the app. He will be able to select retailers mapped to him and view order details, cart and requisition lists.
  • The salesman can add/modify items in the cart/requisition list of the retailer and checkout these items on behalf of the retailer.
  • The retailer can login to his account, browse the catalog, view offers, add items to cart and checkout the items, just like an ecommerce store.
  • The app is also integrated with the SAP ECC ERP system for customer, products and order data. This rendered catalogue data and tracking seamless and real-time.
  • Two carts were available for each retailer based on specific categories.
  • Bar code scanning was available to search for a product.
  • Bulk addition of items to cart is possible.

 

Embitel Impact

  • Our solution helped retailers in tracking purchases and maintaining purchase data. It also increased the RFM of purchases.
  • Since the retailers and salesmen were both empowered to add items to cart and checkout, the order logging process became more seamless and independent.
  • Our solution also enabled the salesmen to focus on more important account management activities.

 

Tools and Technologies

  • Magento EE Cloud
  • Mobile App: Customised PWA
  • PM Tool: JIRA and Confluence
  • June 4, 2020
  • 0

Partners in Innovation: Embitel is Now a Proud Entrant to the WP Engine Partner Network

Category : Press

May XX, 2020

Bengaluru, India

Embitel, a leading Digital Experience Management services provider, has announced its partnership with WP Engine. WP Engine is a WordPress digital experience platform that gives companies of all sizes the agility, performance, intelligence, and integrations they need to drive their business forward faster.

The ‘Digital Experience’ unit of Embitel Technologies joined WP Engine’s Agency Partner Program (APP), the largest of its kind in WordPress. Embitel’s inclusion in WP Engine’s APP opens up new avenues to create personalized digital experiences, delivered lightning fast.

Working together, Embitel and WP Engine have the potential to redefine the Digital Experience paradigm and offer unmatched solutions for their customers. Embitel has been at the forefront of the Digital revolution for more than  14 years now and with this partnership, it looks to reach out to a wider customer base that desires more than merely a digital presence.

With this partnership coming to life, customers can now leverage Embitel’s unmatched domain experience and WP Engine’s robust digital experience platform to develop remarkable digital experiences for their end-users.

“We are in a day and age where a digital experience can make or break a deal. Pairing with a powerful and intelligent digital experience platform like WP Engine, gives us the bandwidth to concentrate more on solution development rather than worrying about the underlying platform and related security and performance aspects. As an implementation partner, we look forward to working closely with WP Engine and creating exceptional digital experiences,” said Manish Narayan, Head of Digital Experience Business Unit, Embitel Tech.

“At WP Engine, we partner with the brightest agency minds that are dedicated to delivering enterprise grade solutions in WordPress. We are focused on building lasting partnerships with some of the world’s most impressive digital agencies and enabling them to deliver their clients a full digital presence. I am excited to see the partnership between Embitel and WP Engine come to fruition and look forward to the the stories we are able to deliver to our clients.” – Maddie Miser, Strategic Alliance Manager for WP Engine

About Embitel

Embitel Technologies is a Digital Experience and Product Engineering services company which is at the forefront of developing cutting edge and innovative software solutions, helping our customers in transforming their business ideas into scalable solutions. Futuristic thinking combined with more than a decade of experience in delivering consistent quality services, in the domains of Digital Experience, Automotive, IoT & Digital Commerce, has helped us in carving a niche of our own. Embitel Technologies has headquarters in Bengaluru, India, with offices in Germany, the UK , the US, and Middle East.

 

About WP Engine

The WP Engine WordPress Digital Experience Platform gives companies of all sizes the agility, performance, intelligence, and integrations they need to drive their business forward faster. WP Engine’s combination of tech innovation and an award-winning team of WordPress experts are trusted by over 100,000 companies across 150 countries to provide counsel and support, helping brands create world-class digital experiences. To learn more about WP engine, please visit www.wpengine.com.

 

To learn more about Embitel, Please visit- www.embitel.com

  • June 3, 2020
  • 0

Tessy Tool Powered Unit Testing of ISO 26262 Compliant Automotive Software

Category : Automotive control units-design and development , Product Engineering

 

Our Customers:

We have had the opportunity to partner with some of the biggest automotive Tier-1 suppliers. The end customers of our partners are major OEMs.

Some of the Tessy Powered Unit Testing projects we worked on include ASIL C compliant Automotive Lighting Module, ASIL B compliant Pneumatic System, Powertrain ECUs and more.

We helped our customers with all the required work products for ISO 26262 Compliance.
 

Business Context:

Safety has become the number one priority among the Automotive OEMs and Tier-1 suppliers. As per a project’s specifications, there are several industry safety standards that need to be complied with. And Unit Testing is one major aspect of this compliance.

Our customers often face challenges with ISO 26262 compliant unit testing. For both compliance and certifications, they require the test reports from ISO 26262 qualified Unit testing tool.

There are multiple code coverages including MC/DC that is mandatory for certain ASIL grades.

Safety critical Automotive Applications like powertrain ECU, Body Control Module, Electronic Power Steering, etc. require comprehensive testing as per the ISO 26262 guidelines specified in Part-6 and Part-8.

The Test Reports from ISO 26262 qualified testing tools are sought by the ISO 26262 certifying authorities as evidence.

We have been technology partners to our customers for carrying out automated unit testing and report generation.

And Tessy, being one of the most reliable ISO 26262 qualified tool for unit testing, has been our tool of choice.

Following Test Methods and Test coverages were expected to be fulfilled.

software unit level
Software unit testing

Work-flow of our Unit Testing Methodology

Unit Testing Methodology
  • Tools like DOORS, Polarion help in Requirement Management.
  • Test Cases are prepared within the Classification Tree Editor (CTE) based on the requirement document.
  • Test Cases are reviewed, and a review report is generated.
  • Test Cases are executed in an automated manner.
  • Test Result is recorded and analyzed
  • Code Coverage is analyzed
  • The Test Report is provided as deliverable to the customer
  • Customer updates the code as per the bug report

 

Embitel’s Solution for Unit Testing Using Tessy Tool:

Approach 1 of Unit Testing

Tessy Tool
  • The default GNU GCC compiler will be used to do the compilation.
  • Test Report is generated for each of the software modules and its functions.
  • The Report is shared with the customer to help them rectify the code.

Approach 2 of Unit Testing

Unit Testing Tessy
  • An external Compiler and Debugger will be configured to the Tessy Environment.
  • We have worked on compilers including GHS Green Hills Compiler, Tasking compiler (Tricore V6.3).
  • Test Report is generated for each of the software modules and its functions.
  • The Report is shared with the customer to help them rectify the code.

 

Tools and Technologies:

  • Tessy Tool: For Automated Unit Testing of Software Modules.
  • Tasking Compiler: Used for code compilation and debugging.
  • Lauterbach Debugger: For code debugging; supports multiple Microcontroller Platforms.

 

  • June 2, 2020
  • 0

Android Porting for Embedded Systems

Category : iot-insights

 
The tendency to adopt Android as an operating system for embedded platforms, is on the rise. The automotive OEM community has been progressively shifting towards customising Android for vehicle infotainment systems and head units. Android OS is also the popular choice in the healthcare industry for powering medical devices.

This widespread adoption of Android porting for embedded systems across industries is primarily due to the advantages Android offers over other operating systems. Here, we explore Android porting in detail – the process, the value-addition and much more.

Advantages of Moving Towards Android

Our Android porting experts have successfully delivered projects associated with:

  • Porting Android on embedded platforms running on other operating systems
  • Direct porting of Android on new embedded systems

Embedded Android has a host of advantages as indicated below:

  1. Rich User Interface – The flexibility that Android provides in building high quality user interfaces is inimitable. Through the inclusion of various APIs into applications, highly immersive UI is delivered. Another highlight is the fact that the embedded application will reflect the UI patterns that users of Android phones/tablets are already familiar with.
  2. Free Source Code – Google releases the source code for core Android as Android Open Source Project (AOSP). The permissive open source licenses associated with this makes it easy to modify the code and incorporate it in products without making it public.
  3. Standardisation – Prior to Linux or Android being adopted as primary operating systems for In-Vehicle Infotainment (IVI) units, OEMs were using customised platforms for this purpose. This led to a lack of standardization in the industry. Since the advent of Linux and Android, OEMs can use the free source code and build unique applications with it. This reduced the overall cost of development. The movement of the industry towards Linux and Android also brought about a distinctive level of standardisation.
  4. Stability/Security – Since Android powers millions of devices globally, it is a well-tested and secure platform. Google also endeavours to continue the progressive development of Android to maintain its superior quality standards.
  5. Easy to develop applications – Google provides a good amount of support for the Android operating system. The programming interface for Android is also well documented. Additionally, it is easier to find experienced engineers to work on Android applications these days. All of this makes Android-based application developmenteasier. OEMs that were previously reliant on custom IVI platforms are now transitioning to Android to open up their platforms to third-party applications. The support of the larger worldwide community is an added advantage.
  6. Futuristic platform – Investors in Android applications are delighted by the modularity and extensibility offered by Android platforms. This is precisely where the overall development process is headed towards in the future.
  7. Underlying Linux Kernel – Since Android is essentially based on the Linux kernel, it is possible to run Linux applications in parallel. It is also feasible to use the Linux development tools here.
  8. Highly customisable – This is a key advantage of the Android platform, when compared to other operating systems. Since Linux is the base, it is possible to integrate open source drivers to Android and create customised framework and application over it.
  9. Free Tools for Programming – Google offers a wide range of free programming and debugging tools for developing Android applications. Android Studio is one such tool that enables programming in C++ and Java. Third-party tools that allow programming using other languages and environments are also available.

 

Android Automotive – A Brief Overview

Android Automotive is a base Android platform that operates automotive In-Vehicle Infotainment systems and head units. It can be customised and scaled to suit specific use cases.

Android Automotive utilises the same codebase as that on the operating systems of Android phones or tablets. There is added support for automotive-specific features and requirements. It enables auto manufacturers to create compelling infotainment systems that deliver unparalleled experiences.

 

Android Porting Project Process Flow

  • The first step in the execution of an Android porting project is the analysis of the granular requirements to identify the hardware and Board Support Package (BSP) required.
  • Analysis of the customisation needed for Android is done (modification of drivers, peripherals, etc.) so that key project requirements are met.
  • Once this is accomplished, the application team can make use of the framework and start working on application development. In parallel, the BSP team can work on the development of lower layers.
  • The completion of the application layer development and BSP development will result in the final product.
  • The next step is the exhaustive testing of the product.
    • Manual testing is usually performed, and there is limited dependency on testing tools. One of the few testing tools used is the Compatibility Test Suite (CTS) that executes test cases directly on an emulator or attached devices. The intent of using this tool is to reveal incompatibilities early on in the development cycle so that the software is compatible throughout the process.
    • The BSP and application teams conduct testing and validation of their code separately.
    • The BSP team may utilize third-party applications for testing their components.
    • Integration testing is then performed to assess end-to-end functionality.
  • When multiple drivers are integrated and several applications start running on the system, there is a possibility of excessive memory usage or memory leaks. Tools such as Valgrind and meminfo can be utilised to assess the system performance. In case the system gets slower after a short period of usage, these tools help in identifying areas where the system can be finetuned. It is also possible to optimise the system following this diagnosis.

 

Embedded Android Porting – A Comparison Between Automotive Industry and Others

When Android porting is done for automotive systems, there are certain standards to be followed. In other industries, the standards would vary.

For instance, in an automotive application the sensors engaged in collecting data may have to integrate with CAN based in-vehicle network . This communication might not be relevant for a consumer electronic product or a healthcare product. The interface, sensors and communication network in such use cases would be completely different.

There would also be a noteworthy difference on the application side. The HMI of a vehicle dashboard is distinct from that of a medical or consumer electronics device. So, the application layer and above would depict these subtle differences. The lower layers, however, would remain the same across domains.

Apart from the aforementioned variations, the overall effort in Android porting remains more or less the same across industries.
 

Security Features to Consider

Apart from Android security patches, the Android Porting engineers developing a complete product may have to integrate the system with the cloud platform. In this scenario, development of a custom security layer is inevitable.

The custom security layer will prevent unauthorized access to the system and the cloud. Kits with SSL certificates, Azure certificates, etc. can be used for the same.

Apart from security considerations, it is important to incorporate FOTA update features into the system. This enables the remote device to be updated with new features at an overall system level or at a specific component/application level.

Conclusion

The popularity of integrating Android OS with embedded systems is likely to continue in the future. Android has also found acceptance among developers and embedded engineers beyond the mobile market. Since the structure of the platform is quite complex, it is best to engage experienced professionals in the execution of Android porting projects for embedded systems.

Explore our expertise in the successful execution of Android Porting projects here.
 

  • June 2, 2020
  • 0

How IoT in Sports and Gaming has Opened Up a World of Endless Opportunities

Category : Embedded Blog

The sports industry has been adapting to an increasingly digital world. The Internet of Things (IoT) has left a significant mark in the way athletes train. The method of operations of sports teams and engagement with fans have also transformed due to the integration of IoT in sports.

IoT in sports

 
IoT has had a notable impact on gaming as well. Social distancing during quarantine has made it difficult for us to play outdoor sports. However, the second-best thing to playing outdoor games is playing indoor games, especially mobile and console games. IoT has made it possible for online and mobile games to be played solo or with a group of people from across the room or anywhere across the globe.

How IoT has Revolutionized the Gaming Industry

IoT in gaming has catapulted online and mobile gaming to new heights over the past few years as gaming has transformed from a solitary pursuit to social activity. Gone are the days when only a few could afford to buy video or console games and invite a friend over to play for a couple of hours at home. Nowadays, anyone and everyone, from kids to adults can afford to indulge in a few hours of stress-relieving games whether it is played on the mobile or console.

IoT in gaming industry has helped game developers, designers, and manufacturers make use of the advanced software and hardware available in smartphones to develop a plethora of IoT gaming projects, market them to a wider audience, and enhance their gaming experience.

How IoT in Gaming Works

You can connect your gaming device, say a console, desktop, laptop, smartphone, or tablet to a friend’s gaming device via IoT and continue to play games with him or her at any time and from anywhere.

  • The devices have chips and sensors that are used to connect to other devices via the internet.
  • The sensors in the devices collect data and transmit it to the cloud platform through a secure gateway.
  • The collected data of user experiences is then analyzed to help developers and manufacturers keep track of the online gaming activities, make improvements to the games, and also penetrate other aspects of a gamer’s life to bring about a wholesome effect.

Online casino games are a fan favorite and a good example of IoT in gaming.

Modern smartphones have hardware and software such as pressure and touch sensors, accelerometers, heart rate monitors and cameras that collectively gather data on user experience. Analysis of this information yields valuable insights on how customers behave while playing online games. Just like casinos that assess reactions of players through their facial expressions, mobile devices can estimate player satisfaction during a game, without compromising on player privacy.

An example of IoT in mobile gaming is the Zombies, Run! mobile game. The game connects with the player’s fitness tracker and smartphone to bring entertainment into a person’s cardio workout wherein he or she is fighting zombies while also making strides in their morning workout.

Similarly, IoT and gaming have made learning easier for children who like it when some form of fun is incorporated into their academic lessons. The same goes for learning apps that incorporate games into the user’s lessons by offering tests, competitions and rewards to keep the learning process progressive and engaging.

Impact of IoT in Sports

Considering the amount of time and money invested in major sports around the world, it is certain that we can expect to see increased use of IoT technology in this domain. Here’s how IoT applications in sports are benefitting athletes, fans, and sports organizations:

Smart Stadiums

Investors are already making headway in IoT projects in sports like building smart stadiums. A couple of examples of smart stadiums include Golden 1 Center and Levi’s stadium in the US.

  • A smart stadium integrates several sensors, digital signs, and cameras which are connected to both wireless and wired networks to collect and transmit data to IoT platforms.
  • The collected data is then analyzed and put to better use for enhanced fan engagement and stadium maintenance.
  • The stadium’s ventilation, heating, and electronic systems can be monitored and maintained via IoT sensors.
  • It can also be used to conserve resources by tracking water and electricity consumption, locating empty parking spaces in the stadium, and asserting crowd control at the food and merchandise stands.

IoT Devices in Sports Equipment and Uniforms for Athletes

IoT devices in sports help ensure both athlete safety and enhanced training. For example, IoT sensors in smart insoles and smart fabrics of an athlete’s shoes can collect data on his or her training regime, performance, health, and injuries for analytics purposes.

Player development is a key area of focus and data collected by sensors worn by players can be processed to derive insights on player efficiency. This, in turn, helps to formulate effective in-game strategies.

Wearable IoT sensors provide the following types of insights:

  • Effort exerted by players during a match
  • Efficiency of the player and key areas to improve on
  • Health of the player and recovery time needed
  • Weaknesses in the body and prediction of injuries
  • Patterns in player performance

The above data helps in the selection of players for each game in a strategic manner. IoT sports analytics helps trainers and coaches to customize and streamline training modules and game plans for athletes. This ensures enhanced athlete training and safety.

Moreover, sports manufacturers can use the data collected by IoT sensors to develop customized products to meet each athlete’s specific needs.

IoT sensors also help in tracking the distance travelled, speed and position of a player in a real-time game scenario. These real-time insights help the coach in guiding players and making smarter decisions when it matters the most.

An example of IoT sports equipment is the smart cricket bat being developed by Microsoft. The IoT-powered bat has a sensor that will collect data like swing speed, impact, distance and angle which will then be analyzed to get an insight into a player’s batting style.

IoT Sensors Sports Apps for Fans

IoT used in sports also benefits ardent fans around the world. Fans can use apps that will offer personalized experiences whether they are watching the game from their home or stadium.

Furthermore, collecting data on fans’ preferences can enable advertisers and sports organizations to offer fans customized product packages, thus, giving them good value for their money. This also results in better fan engagement and more ticket sales.

IoT for Sports – What to Expect

Given the revolutionary changes brought about by modern technologies in most industries, IoT for sports is a trend that will only evolve further. Therefore, it’s crucial for sports organizations to realize its potential and prepare for the change by taking steps to properly invest in IoT sensors for sports projects.

Having said that, IoT in sports is relatively new, so, sports companies shouldn’t blindly invest in IoT without doing in-depth research. This includes hiring experts in modern technologies like Artificial Intelligence (AI) and Machine Learning for designing strategies, setting aside budgets for infrastructure upgrade, updating existing systems for IoT integration, building frameworks for testing IoT solutions, educating employees on the operation and use of IoT in the workplace, and so on.

P.S. Whether it is IoT and sports or IoT and gaming, regardless of the endless possibilities presented by this modern technology, it’s important to consider cyber security/safety when it comes to sharing personal and social information. While registering to play a game, you are required to give access to your data and media, hence, always ensure the permission settings are set to safeguard your interests.

Archives

Contact Us

© 2018 Embitel. All Rights Reserved