China
Africa
Explore chapters and articles related to this topic
Embedded Real-Time Operating System
Published in Yi Qiu, Puxiang Xiong, Tianlong Zhu, The Design and Implementation of the RT-Thread Operating System, 2020
Yi Qiu, Puxiang Xiong, Tianlong Zhu
An embedded operating system is an operating system that is used in an embedded system. Embedded systems are widely used and easier to understand. All computers are embedded devices except servers, personal computers, and mobile devices. Embedded systems are everywhere in our lives, from military equipment to civilian affairs, from industrial control to network applications. The following are some typical embedded device examples; Figure 1.1 also lists some embedded operating system applications.
Smart, connected open architecture product: an IT-driven co-creation paradigm with lifecycle personalization concerns
Published in International Journal of Production Research, 2019
Pai Zheng, Yuan Lin, Chun-Hsien Chen, Xun Xu
Apart from the mechanism of IoT by providing a ubiquitous connectivity at a low cost for information transmitting, SCP represents the third wave of IT-driven competition. It changes the way how value is created (Porter and Heppelmann 2015) by embedding IT into the products. According to Porter and Heppelmann (2014), SCPs are mainly composed of three key elements: Physical components comprising the product’s mechanical and electrical parts as usual products (UP).Smart components consisting of the microprocessors, sensors, controls, data storage, software, and, especially, an embedded operating system and enhanced user interface. Software often can replace some hardware components or allow a single physical device to perform well at multi-levels.Connectivity components which contain the antennae, ports, and protocols enabling wireless or wired connections with the product. They enable not only information exchange between the product and the operating environment, but also ‘product cloud’ functions existing outside the product.
Monitoring of an experimental motorway section
Published in Road Materials and Pavement Design, 2019
Juliette Blanc, Pierre Hornych, Ngoc Son Duong, Jean-Yves Blanchard, Pierre Nicollet
This platform is modular to fit various needs without a long and costly development process (Le Cam, Cottineau, Lemarchand, & Bourquin, 2008). This modular concept comprises a “mother board”, which integrates some redundant needs (computation, communication and data storage) and a set of pluggable “daughter boards”, which integrate some specific application needs like sensitive elements (accelerometer, temperature, pressure, etc.), and their specific conditioning design like hardware filters and analog to digital converters. The PEGASE platform includes the following characteristics (Le Cam, Lemarchand, Martin, & Bonnec, 2010): the use of TCP/IP/Wi-Fi as wireless protocol; an Analog Device low-power Blackfin BF537 core processor; a small and low-power GPS receiver for localisation and above all absolute time synchronisation up to a few µs; uClinux as the embedded operating system. All of that provides a high level of abstraction, whereas PEGASE algorithms are programmed using standard ANSI C language.
HardOps: utilising the software development toolchain for hardware design
Published in International Journal of Computer Integrated Manufacturing, 2022
Julian Stirling, Kaspar Bumke, Joel Collins, Vimal Dhokia, Richard Bowman
The DVCS repository is the centre of the HardOps workflow, with each repository having its own issue tracker, permissions, automation scripts etc. However, for complex projects it does not always make sense to have a single repository for all files. The OpenFlexure project, for example, has separate repositories for hardware, software, embedded operating system, electronics, project website, failure mode analysis, and more. These repositories are grouped together so issues can be linked, share labels, and be managed in the same milestones. Managing all these aspects of the project with the same tools creates a highly integrated workflow. This allows a small team, such as the academic group that runs the OpenFlexure project, to effectively manage a complex project.