The essence of a Design model is the following

An in-the-loop testing strategy is often used as itemized below and summarized in Table 2:
1. Simulation test cases are derived and run on the model using Model-In-the-Loop (MIL) testing.
2. Source code is verified by compiling and executing it on a host computer using Software-In-the-Loop (SIL) testing.
3. Executable object code is verified by cross-compiling and executing it on the embedded processor or an instruction set simulator using Processor-In-the-Loop (PIL) testing.
4. Hardware implementation is verified by synthesizing HDL and executing it on an FPGA using FPGA-In-the-Loop (FIL) testing.
5. The embedded system is verified and validated using the original plant model using Hardware-In-the-Loop (HIL) testing.
A requirements-based test approach with test reuse for models and code is explicitly described in ARP4754A, DO-178C, and DO-331, the model-based design supplement to DO-178C.
Introduction to model-based design
With model-based design, UAV engineers develop and simulate system models comprised of hardware and software using block diagrams and state charts, as shown in Figures 1 and 2. They then automatically generate, deploy, and verify code on their embedded systems. With textual computation languages and block diagram model tools, one can generate code in C, C++, Verilog, and VHDL languages, enabling implementation on MCU, DSP[], FPGA[], and ASIC hardware. This lets system, software, and hardware engineers collaborate using the same tools and environment to develop, implement, and verify systems. Given their auto-nomous nature, UAV systems heavily employ closed-loop controls, making system modeling and closed-loop simulation, as shown in Figures 1 and 2, a natural fit.
Testing actual UAV systems via ground-controlled flight tests is expensive. A better way is to test early in the design process using desktop simulation and lab test benches. With model-based design, verification starts as soon as models are created and simulated for the first time. Tests cases based on high-level requirements formalize simulation testing. A common verification workflow is to reuse the simulation tests throughout model-based design as the model transitions from system model to software model to source code to executable object code using code generators and cross-compilers.

refer to:
http://mil-embedded.com/articles/transitioning-do-178c-arp4754a-uav-using-model-based-design/

One of the biggest implications of Industry 4.0

We are facing a potentially exponential increase in the amount of data manufacturing systems will handle as vision systems, batch control, regulatory compliance, quality management and more will mean that the amount of data those networks have to handle is going to rocket.

As a result, we require sufficient bandwidth to allow for this increased use. At present, CC-Link IE is the only industrial automation network technology that can provide a gigabit (1 Gbit/s) of bandwidth, which makes it exceptionally well placed to deal with the demands of Industry 4.0.

To find an example of how data intensive these applications can be one only has to look at the needs of the leading Korean flat panel display manufacturers. Their tolerance for so-called ‘dead pixels’ is almost zero. To put this into perspective, a modern HD screen has 1080 vertical pixels horizontally and 1920 vertically. That’s 2,073,600 pixels on each unit. The manufacturing processes have to check each of these pixels, hundreds of times a day to ensure quality and control yield. It’s easy to see how quickly solutions like this will generate vast volumes of data.

As another example, the global automotive industry produces countless different combinations of each vehicle model at an incredible rate. It’s typical for an assembly plant to produce a complete vehicle at a rate of more than one per minute.

Producing these countless different versions at such a pace demands a huge amount of flexibility and a great deal of bandwidth to cope with both the production instructions and the quality control. Most models today have literally thousands of different model configurations depending on customer option choice. To complicate things further, it’s not uncommon for one assembly plant to produce a variety of models. Again, it’s easy to see how this puts huge demands on the networks that deliver this information to the assembly line systems that ensure the correct parts are fitted on the correct in-vehicle.

refer to:http://www.connectingindustry.com/automation/the-networking-implications-of-industry-40.aspx

To gaining boards conpetence

From the beginning, industrial board manufacturers architectures stressed lowest-cost, low-power hardware, with an emphasis on multimedia and graphics. This led the Raspberry Pi Foundation and BeagleBoard.org to adopt ARM architectures for the processing element in their embedded computer boards, resulting in similar architectures with comparable performance that catered to educational and hobbyist developers. Since then, variants have evolved to increase pin access and optimize performance for a range of development applications.

“All of the DIY ARM boards have broadly the same architecture – a System-on-Chip (SoC), which contains the processing, multimedia, and I/O in a networking appliance configuration, and one or two external chips to provide functionality that is missing from the core SoC,” says Eben Upton, Executive Director, Raspberry Pi Foundation. “There are a number of boards based on a couple of different SoCs that use Cortex-A8 cores at around 1 GHz; these can get ahead of the Raspberry Pi a little on integer and networking appliance, but lag behind on floating-point performance and multimedia, as A8s have a very weak Floating-Point Unit (FPU).”

refer to:
http://embedded-computing.com/articles/diy-pushes-open-hardware-kindergarten-kickstarter/

Fine positioning for the automation actuator market

In the "Drive to end position" duty, individual settings are available for technology end position. Depending on the settings, the motor either remains on or is switched off as soon as the actuator reaches its defined position and the brake is applied to stop the motor. With the help of the breakaway function, the embedded systems can make up to 200% of its rated torque or rated force available in the end position areas. This allows single board computer to be safely moved out of their end position. For most control loops, minimal valve movements near the end position make little sense from a technical perspective. If, however, process variables change at this actuating element position, the actuator will follow the resulting control commands and there is a danger that the single board computer will sustain permanent damage if it is approached too often. There is also a danger that valve positions very close to the end positions will cause technology cavitation.



refer to: http://www.power-eng.com/articles/print/volume-117/issue-8/features/opportunities-to-improve-efficiency.html

Automation service availability

JR Automation,  in business since 1980, is a rapidly expanding embedded system automation company with experience in creating a wide range of solutions, from stand-alone operator assist stations to highly automated assembly lines. JR will service and support customers in the US, Canada, and Mexico, and AWL will support customers in Europe and China. Both experts in the design and build of automated equipment  and industrial computer for the automotive and general industries, the pairing will now have the added ability to focus on their respective regions exclusively, giving the customer increased support and service availability.

refer to: http://www.automation.com/jr-automation-and-awl-techniek-join-forces

Barry Lock on the upcoming debug forum

Much of the content will be based around the embedded computers development and validation of Autosar compliant code and the development of code for specific devices such as the BOSCH GTM, the AURIX and Freescale's Nexus based Qorivva solutions. Some of the presentations will also touch on the debugging of code on multicore systems. Delegates will also have the opportunity to discuss their specific challenges and requirements. Furthermore, "For anyone working in the development of code for the automotive sector, this should prove a very useful day," said Barry Lock, UK Manager of Lauterbach. "There will be a lot of embedded computers expertise at this event, and the presenters will be discussing the very latest developments in chip technology, software solutions and debug tools."

refer to: http://embedded-computing.com/news/lauterbach-software-debugging-workshops/

WI-FI CERTIFIED Miracast in global in-vehicle market

The WI-FI CERTIFIED Miracast specification enables car manufacturers to wirelessly mirror smartphone screens to in-dash LCDs, creating an immediately personalized interface in the dashboard. Additionally, this in-vehicle standards-based technology allows consumers to safely control smartphones through the dashboard so they can answer calls and check text messages. Although NFC is often associated with cashless payments, its ability to deliver security features to IVI systems is instrumental in providing an optimal end-user experience. Digital Content Protection (HDCP) 2.0. Many of the device and in-vehicle discovery components of the protocol are built around the previously released Wi-Fi Direct specification. The WI-FI CERTIFIED Miracast specification enables car manufacturers to wirelessly mirror smartphone screens to in-dash LCDs, creating an immediately personalized interface in the dashboard. Additionally, this in-vehicle standards-based technology allows consumers to safely control smartphones through the dashboard so they can answer calls and check text messages.

refer to: http://embedded-computing.com/articles/wireless-accelerate-next-wave-in-vehicle-innovation/