Forlinx

As engineering vehicles become smarter, onboard dashboards and 360°surround view systems are now standard configuration. The onboard dashboard monitors vehicle status in real-time, while the 360° surround view system offers a complete view of the surroundings, helping drivers better get the vehicle’s surroundings. To meet market demand and enhance the safety performance and operational efficiency of engineering vehicles, we offer the following solutions: onboard dashboard and 360° surround view system for engineering vehicles. Function Description: Real-time Monitoring: Through the onboard dashboard, drivers can instantly access the operational status of engineering vehicles, such as engine speed, vehicle speed, hydraulic oil pressure, etc. Simultaneously, the 360° surround view system can instantly collect image data of the vehicle's surrounding environment, offering a comprehensive perspective to assist drivers in better understanding their surroundings. Data Display and Interaction: The on-board instrument panel has a clear and intuitive interface, which can display various data and information. Drivers can interact with the instrument panel through the touch screen or other input devices to achieve information inquiry, parameter setting, and other functions. Remote Monitoring and Diagnosis: Through the communication module, this solution can achieve communication with the remote monitoring center, upload the vehicle operation status data and image data of the 360° Around View system, and receive remote control commands. This helps the management personnel conduct remote management of vehicles and improve operation efficiency. Stability and Reliability: Both the hardware and software designs of this solution possess high stability and reliability, enabling them to operate stably for a long time in complex vehicle environments without being prone to malfunctions or damage. Easy to Operate and Maintain: This solution offers drivers seamless usage with minimal maintenance costs. Forlinx Embedded recommends the FETT507-C SoM as a hardware solution. Here are the optimizations and extensions of the solution: 1. Support for AHD Analog High-definition Cameras: The FETT507-C SoM integrates AHD analog high-definition camera input and adopts the MIPI_CSI solution to enable signal acquisition from four AHD analog cameras. This not only provides a comprehensive view but also assists drivers in better understanding the surroundings of the vehicle, thereby enhancing driving safety. 2. Stable CAN Data Acquisition: By utilizing a stable and mature SPI-to-CAN conversion solution, real-time vehicle operational data can be collected, providing robust support for vehicle monitoring and data analysis. 3. Flexible Expansion with Multiple Interfaces: Supporting the I2C interface allows for convenient integration of audio chips for in-vehicle audio data acquisition or connection to other external sensors. Additionally, it supports four display output interfaces including RGB, LVDS, HDMI, and CVBS, with a maximum display resolution of 4K, meeting the display needs of different sizes and resolutions. 4. Communication and Positioning Capabilities: The FETT507-C SoM integrates GPS and 4G modules to enable daily vehicle communication, remote access, and positioning functions, providing support for remote vehicle monitoring. 5. Real-time Video Stream Storage: The SoM supports external SD card connection for real-time video stream storage, facilitating easy playback and data analysis. 6. GPIO Interface and Button Functionality: The provision of GPIO interfaces caters to various physical button function requirements, facilitating user operation and control. 7. Support for Multiple Operating Systems: The FETT507-C system on module supports various operating systems, including Linux 4.9 and Android 10.0, offering users greater possibilities for further development.

Dust is an open source of pollution due to dust on the ground, human-driven and driven to fly into the atmosphere, and is an important part of the total ambient air. Suspended particulate matter in the ambient air lasts for a long time and can be inhaled. Once the inhalable particulate enters the human body, it will accumulate in the respiratory system and cause many diseases, which is harmful to human beings. Dust monitoring is a real-time on-line monitoring measure to prevent and control air pollution. The dust monitoring equipment can monitor the atmospheric particulate matter concentration, PM value, temperature, humidity, wind speed, wind direction and other data in real time, and the dust pollution can be prevented and rectified in time by means of real-time data monitoring and alarm. The online monitoring system can save a lot of manpower and material resources and provide quantitative data support for on-site treatment and administrative enforcement. After the online monitoring system is installed, continuous and uninterrupted monitoring will be carried out. It mainly monitors respirable particulate matter and is complemented by a video monitoring system, a noise monitoring system, a meteorological system, a data acquisition system, and a communication system. The online automatic monitoring system is mainly used for online dust, environmental protection, meteorological station, tunnel and other online dust monitoring, unorganized smoke and dust pollution source emissions, residential areas, commercial areas, road traffic, construction areas, etc.; online real-time automatic monitoring of ambient air quality, and can obtain evidence through the camera. The real-time data from the weather station monitoring and the tunnel subway station can be transmitted to the data platform in time through the wired or wireless network for easy management and control. System Components The system consists of a data collector, a sensor, a video monitoring system (optional), a wireless transmission system, a background data processing system and an information monitoring management platform. The monitoring sub-station integrates various functions such as atmospheric PM1.0, PM2.5, PM10 monitoring, ambient temperature and humidity and wind speed and direction monitoring, noise monitoring, video surveillance (optional), etc.; the data platform is a networked platform with Internet architecture, which has the monitoring function of each sub-station and various functions such as alarm processing, recording, querying, statistics, report output, etc. of the data. The system can also be linked with various pollution control devices to achieve the purpose of automatic control. Implementation Scheme The online dust monitoring host can be developed using the FETMX6ULL-C SoM recommended by Forlinx Embedded. Hardware Design: FETMX6ULL-C SoM supports 8 x RS232/RS485/TTL and multi-channel I/O interfaces, which can be connected to dust sensors and other environmental monitoring equipment. At the same time, the industrial design enables it to operate stably in harsh outdoor environment, which ensures the reliability of the monitoring system. Network Communication: FETMX6ULL-C System on Module supports 2 x dual 100m Ethernet and standard TCP/IP and UDP protocol stacks. Monitoring data can be transmitted to the monitoring center or cloud server in real time through the network to realize remote monitoring and management. Wireless Communication: It supports 4G and WiFi wireless communication, and after a long time of stable testing, it can ensure the stable transmission of monitoring data, and even in the absence of wired network, it can also realize the online monitoring function. Screen Display: FETMX6ULL-C supports a variety of LCD screen designs, which enables the monitoring system to select the appropriate display screen according to actual needs, and realize the intuitive display and operation of data. Based on the features of Forlinx Embedded FETMX6ULL-C SoM, the dust online monitoring realization solution can achieve the advantages of rich hardware interfaces, stable network communication, flexible software support, etc. It is suitable for a variety of environmental monitoring scenarios and can meet the needs of the industrial level to guarantee the stability and reliability of the monitoring system.

Command 1. The video recording was unsuccessful with the command ffmpeg -framerate 25 -f v4l2 -i /dev/video4 recording1.mp4 . According to the official ffmpeg documentation, -r and -framerate have the same function, but the actual test shows that they are different. -framerate is used to limit the input while -r is used to limit the output 2. Video can be recorded with the command ffmpeg -r 25 -f v4l2 -i /dev/video4 recording1.mp4 , but problems such as frame error and frame repetition will occur. 3. Use ffmpeg -f v4l2 -r 25 -thread_queue_size 128 -i /dev/video4 -vcodec libx264 -b:v 800k-preset ultrafast recording1.mp4 to achieve dual camera video recording at the same time. Parameter Description: ⚫ -f Set the output format, the output format is v412 frame (The commands found earlier all use the framework avfoundation, a full-featured framework for handling multimedia data on iOS, macOS, watchOS, and tvOS. The v412 framework used in this command is a framework for video device drivers in the Linux kernel, which provides a unified interface to the application layer and supports flexible expansion of various complex hardware). ⚫ -r Set frame rate, set frame rate to 25fbs. ⚫ -thread_queue_size (The thread _ queue _ size is applied to the first input specified after it. The term "thread_queue_size" can be applied to all inputs and determines at the application level. How many packets from that input can be queued while waiting for ffmpeg to receive and process them on its main thread. A few capture devices, primarily dshow, use "rtbufsize" to store incoming frames while waiting for them to be transferred to the application-level queue for that input. These two options do not adjust the value of the other, so they should be set manually. The default is 8. Common Warnings: Thread message queue blocking; consider raising the thread_queue_size option (current value: 8). To solve this problem, the official explanation: This option sets the maximum number of packets queued when reading from a file or device. (In low-latency/high-rate real-time streams, packets may be dropped if they are not read in a timely manner; increasing this value prevents this.) ⚫ -i Set input stream, set input from video4 ⚫ -vcodec Set the video encoder，（-vcodec and-codec:v equal in value） Encoders are library files that implement a certain encoding format. Encoding and decoding of video/audio in a certain format can only be achieved if an encoder for that format is installed. Here are some of FFmpeg's built-in video encoders. libx264: The most popular open source H.264 encoder NVENC: NVIDIA GPU-based H.264 encoder libx265: Open source HEVC encoder libvpx: Google's VP8 and VP9 encoders libaom:AV1 Encoder ⚫ -B:v Video bit rate ⚫ -preset specifies the output video quality, which will affect the file generation speed. The following values are available: Ultrafast,superfast,veryfast,faster,fast,medium,slow,slower,veryslow,placebo from fast to slow, the ultrafast transcoding rate is the fastest, and the video is often the most blurred. ⚫ recording1.mp4 Name and file type of the output videoYou can use ffmpeg-formats to get all the file types supported by ffmpeg, where the annotation before the file is as follows: D.=Demuxing supported（Support for video/audio encapsulation） .E=Muxing supported（Support decapsulation of video/audio） Method： Software: ⚫ Ubuntu： 1.Devepoment board networking 2. sudo apt-gat update upgrades apt-gat to the latest version (optional) 3. sudo apt-get install ffmpeg uses apt-gat to obtain ffmpeg 4. Enter relevant commands Hardware: Connect the Forlinx self-made analog camera module to support two cameras. Video4-7 are nodes generated by the TVIN, with the upper left corresponding to video7, lower left corresponding to video6, lower right corresponding to video5, and upper right corresponding to video4. Select according to the actual situation.

Taking the FETMX6ULL-C platform as an example, if you want to use VPN, you need to open the tun configuration in the kernel in the following way: Kernel Compilation Choose either of the two methods below: 1. Modify the.config file directly Locate the.config file in the kernel source path. Find the CONFIG _ TUN in the file and modify it as follows: Replace the kernel's config file with .config. * Subject to actual use. Recompile the kernel. 2. Configure the TUN using the graphical configuration interface Make menuconfig. Locate the following locations: Save and exit after modification, which can be seen in.config Replace the kernel's config file with .config. * Subject to actual use. Recompile the kernel. Update kernel: The arch/arm/boot/zImage file is generated after compilation, and the kernel can be replaced either by updating the kernel separately or by re-burning it. Use this file to replace the file with the same name in the target path of the flashing tool. Refer to the single-step kernel update chapter of the FETmx6ull-c User's Manual to replace the zImage file separately. Compilation module: In the kernel source code, some of the drivers are compiled in the form of modules, which are loaded from the specified path by the kernel version number when the system boots. When we recompile the kernel and update the kernel, the kernel version number in the system will be changed, the kernel version number can be viewed through the uname -r command. When you update the kernel, the uname -r version number changes, but the version number in the path where the module is stored (/lib/modules/) does not change. It may cause the module to fail to load, typically after updating the kernel, WiFi cannot be used. As seen below, the name under uanme -r and the name under /lib/modules/ are not the same, so you can't load the module when you go to the/lib/modules/$(uname -r) directory when booting up, and you need to change both names to be the same. You can solve this problem in two ways: 1. Modify the module load path and change to the version number of the kernel; 2. Repackage modules; The first method has two disadvantages: a. Not suitable for batch modification; b. Not suitable for changing the module driver; So it is possible to repackage the module when compiling the kernel: After executing the above operation, .tmp/root/modules.tar.bz2 will be generated, which can replace the file with the same name under the target path in the flashing tool. It is also extracted directly in the file system:

Edge Computing Access Screen is designed to provide an edge computing-based solution for access control systems. It can realize face recognition, data processing, fingerprint recognition and other functions, and improve the security and convenience of the access control system. In terms of application scenarios, intelligent monitoring and access control system is an important part of intelligent building security. The application of edge computing technology can increase the monitoring effect and response speed, avoid the security risks in the process of data transmission, and protect the privacy of users. Edge computing devices can process authentication faster and improve the response speed and security of access control systems. Hardware requirements for edge computing access control screen (1) Processor Select a high-performance and low-power embedded processor, the processor itself needs to come with arithmetic power to meet the needs of edge computing. (2) Memory Configure appropriate memory and flash for system and application data. (3) Interface Provide necessary interfaces between the carrier board and other devices, such as GPIO, UART, I2C, SPI, etc. (4) Communication module Support Wi-Fi or 4G to facilitate data transmission with the cloud platform. (5) Sensor Integrate multiple sensors, such as face recognition, fingerprint recognition, and RF card reader. Edge Computing Access Control Screen Design The FET3568-C SoM is recommended to be used as the hardware platform of edge computing access control screen. The system on module has a quad-core ARM Cortex-A55 processor with a main frequency of 2.0 GHz, and its own NPU has a computing power of 1TOPS, which can meet the needs of lightweight edge computing tasks. Memory: FET3568-C SoM supports LPDDR4 and eMMC storage, and can be configured with appropriate memory and flash memory to meet the needs of the access control system. Interface: Native GPIO, UART, I2C, SPI, Gigabit port, etc. can communicate with other lines. Communication module: FET3568-C supports wireless communication technologies such as Wi-Fi, Bluetooth, and GPS. The appropriate communication module can be selected according to the requirements. Sensors: FET3568-C supports multiple sensor interfaces, such as GPIO, I2C, SPI, etc., and can easily integrate multiple sensors, including face recognition, fingerprint recognition modules, etc. Power supply module: According to the requirements of the access control system, the appropriate power supply chip can be selected to provide stable and reliable power supply for the entire carrier board. Peripheral expansion: USB and SD card slots are convenient for secondary development and function expansion.

Overview Description In modern urban public transport, bus scanning and swiping machines are a convenient and fast payment method that allows passengers to pay their fares more conveniently and quickly, avoiding the problem of finding change as well as the time and security problems associated with cash transactions; it can automatically calculate fares and facilitate statistics and analysis of data, which largely improves the efficiency of bus operation and management; the device not only provides passengers with convenient and efficient bus payment and information services but also enhances the experience of public transportation services. The intelligent bus card reader is equipped with a universal NFC card reader module and an embedded QR code scanner, which can be compatible with the recognition of both public transportation IC card payments and QR code scanning for payment. The system has an open interface for secondary development and docking. Passengers can use smart cards for payment, mobile NFC payment, and QR code scanning payment. It can have an embedded PSAM card slot and can be compatible with universal transit cards, UnionPay, credit cards, and other payment methods, making it a vehicle terminal that supports all payment methods and can be applied globally. What is even more remarkable is that it comes with a high-definition facial recognition camera, which enables in-vehicle mobile facial payment functionality. In particular, with the trend towards autonomous buses in the future, multi-functional vehicle terminals can also be effectively utilized. Features: Two-dimensional code scanning: Support a variety of common two-dimensional code formats.Credit card payment: Support multiple payment methods such as bus card, bank card, IC card, NFC, etc. Information display: Provide high-definition display screen, real-time display of the welcome message, ticket price, deduction status, etc. Audio prompt: Built-in speaker supporting functions such as payment success notification. Data statistics: Payment data can be uploaded to achieve real-time statistics and analysis of data, providing a basis for the optimisation of the public transport system. Remote Positioning: Support remote GPS positioning. Main Functional Interface Programme: Integrated Barcode/IC Card Scanner for Buses Based on FET113i-S - Overall Solution Recommendation: FET113i-S SoM is developed based on the industrial-grade processor Allwinner T113-i, with a main frequency of 1.2GHz, equipped with a multi-core and multi-architecture design: integrating dual-core Cortex-A7 CPU, 64-bit XuanTie C906 RISC-V CPU, and DSP; On-board 256MB + 256MB and 512MB + 8GB configurations to meet product planning options; Support a variety of peripheral interfaces: USB, CAN, I2S, GPIO, UART, SPI; can connect camera module, card module, speaker, 4G/5G, GPS, etc.; Powerful multimedia audio and video processing capabilities, support a variety of display interfaces, including RGB, MIPI-DSI, LVDS interfaces, support H.265 (4K@ 30fps), MPEG-4 (1080p @ 60fps), JPEG (1080p @ 60fps) and other full-format decoding. JPEG/MJPEG (1080p @ 60fps) format encoding; supports 8-bit parallel CSI, CVBS video input, CVBS, RGB, 2-channel LVDS, 4-channel MIPI DSI video output; also suitable for audio-related applications through DSP support.

Due to individual differences in oral structure, some traditional oral dental films are difficult to fully adapt to the special conditions of the patient's mouth and may require multiple adjustments and break-ins, and traditional mass production methods cannot meet the demand for personalized dental films. The traditional approach relies heavily on mold production, but this makes it difficult to respond to the needs of individual patient variability. Manufacturing methods usually require a long production cycle, with patients needing to obtain, fit, and adjust the model throughout multiple visits, which increases the time cost of the entire process, and a cumbersome fabrication process that involves multiple processes, including model acquisition, plaster model fabrication, and dental film fitting, which makes the entire fabrication process more costly, including material and labor costs. Meeting the personalized and customized needs of dental health-care is the basis of dental film manufacturing, which happens to be a perfect match for the technical characteristics of 3D printing, thus creating a rapid growth of the dental 3D printing market, as well as fierce competition. A good 3D printing device must have a convenient and user-friendly human-machine interface that allows doctors or technicians to easily operate and monitor the printer status. Not only that but also a wealth of peripheral interfaces, such as USB, RS232/485, CAN, I2C, etc., can fully meet the needs of a variety of external devices and sensors, etc., to set aside enough scalability. To meet the hardware requirements of the main control board for dental and dental 3D printers, Flying Embedded has introduced the FET3568-C platform, which has a rich set of peripheral interfaces including USB, RS232/485, CAN, I2C, etc., and provides powerful connectivity for dental and dental 3D printers. At the same time, the chip platform reserves enough scalability to meet the needs of external devices and sensors, and provides flexible expansion space for the functions of dental equipment. Details of the scheme for realizing the 3D printer in the stomatology department: ARM architecture processor: FET3568-C is based on Rockchip's RK3568 core processor, providing powerful computing capabilities and low power consumption design, suitable for efficient control of oral and dental 3D printers. Motion control and sensor interfaces: The abundant peripheral interfaces of RK3568 chip are used to connect stepper motors, temperature sensors and so on, so as to realize motion control and real-time monitoring of system status. HMI: Equipped with a 7-inch or 10.1-inch high-resolution capacitive touch screen, it provides a convenient and friendly user interaction interface. The touch screen is designed according to the current user's operating habits, making the operation more intuitive and easy to use. 4K display support: Additional interfaces support 4K display, such as HDMI and eDP, for external high-resolution display devices. This ensures clarity and precision of the print control operation. Optical connection: Integrated external optical interface for print control to ensure accuracy and efficiency of dental and dental 3D printers. Network connection and communication interface: The network function of FET3568-C platform is used to realize the remote monitoring and upgrading of equipment. At the same time, other devices and sensors are connected through USB, RS232/485, CAN and other interfaces. Summary: The FET3568-C-based dental and dental 3D printer implementation takes full advantage of the platform's powerful performance and rich peripheral interfaces. The optimization of the human-machine interface, the support of a 4K display, and the connection of multiple sensors ensure efficient, convenient, and precise operation of the equipment, providing advanced digital solutions in the field of oral dentistry.

Against the backdrop of rapid development in communication and networking technologies, smart factories are gradually achieving data-driven, networked, and intelligent management. In this trend, the utilization of the Industrial IoT has become an indispensable key step in achieving industrial data collection and control. Traditional industrial data collection and control systems typically require connection to multiple data collection devices, perform high-speed communication, handle complex data processing, and achieve high-definition multimedia display functions. The embedded system based on ARM+FPGA architecture has rich peripheral interfaces, high-definition display high-speed transmission, and other functions, which are more capable of high-speed industrial data acquisition tasks. The flexibility and performance of this embedded system make it an ideal choice to meet the needs of smart factories, which can effectively improve the efficiency and accuracy of industrial data processing. In the industrial data acquisition and control system, high-speed data acquisition system and embedded human-computer interaction system cooperate closely to build an intelligent industrial management system. The main task of the high-speed data acquisition system is to collect the key data in the industrial production process in real time and ensure the accuracy and timeliness of the data. This involves high-speed communication with multiple data acquisition devices, as well as sophisticated data processing and multimedia display capabilities. As the main control center, the embedded human-computer interaction system coordinates and manages each module and resource, and is responsible for receiving the data from the FPGA terminal. It not only visualizes the data to the user, but also achieves more flexible control through human-computer interaction. The system also realizes the connection with the industrial MES + ERP system through the communication module, and transmits the collected data to the cloud for storage. This design not only improves the efficiency of data processing, but also greatly reduces the risk of manual data entry, and realizes the intelligent management of industrial data. The whole system architecture provides a more comprehensive and efficient data management solution for enterprises. This not only helps to reduce human errors in the production process, but also makes better use of human resources and improves production efficiency. With the continuous development of communication and network technology, such industrial data acquisition and control system will become an important support for industrial intelligence in the future. The main control device of the industrial data acquisition control system can adopt Forlinx Embedded FET6254-C SoM, which is based on TI's AM62x series industrial processor design, with the main frequency up to 1.4GHz, is a multi-core heterogeneous processor, adopting the Cortex-A53+Cortex-M4F combination of processing core + control core architecture; the functional safety features can be realised by the M4F core and its dedicated peripherals, and the startup and operation of the M4F core no longer depend on the A53 core. The M4F core and its dedicated peripherals enable functional safety features, and the M4F core is no longer dependent on the A53 core for startup and operation. It can provide excellent data processing capability and human-computer interaction experience, and can control the motor drive module in real time to meet the requirements of data processing, task scheduling and human-computer interaction of the real-time control system. It support parallel bus support for ARM high-speed communication with the FPGA to provide access. FET6254-C supports TI processor-specific general-purpose memory controller interface GPMC, high data read and write rate of up to 100MB / s, support for multiple chip selection, the configuration is more flexible, and at the same time can provide a variety of methods to connect with the peripheral devices and a wide range of external devices can be communicated. The FET6254-C SoM integrates a rich set of functional interfaces. It supports two Gigabit Ethernet with TSN support, which provides fast data transmission and connection capability to meet the demand of industrial data acquisition and control systems for high bandwidth and low latency; it also supports three communication interfaces, such as CAN FD, I2C, I2S, which provide a reliable, high-speed and real-time data transmission method for the normal operation and efficient performance of industrial data acquisition and control system; with rich interface resources such as USB, UART, PWM, SPI, etc., it can be used to connect various sensors, actuators, motor drive modules, and mouse and keyboard devices. The control system provides support for normal operation and efficient performance; with rich interface resources such as: USB, UART, PWM, SPI, etc., can be used to connect a variety of sensors, actuators, motor drive modules, as well as the mouse, keyboard devices, etc., can be achieved in industrial data acquisition and control of a variety of signals and data, to achieve the monitoring and control of the production process; the SoM adopts an industrial-grade temperature and wide range of design, to ensure that the stability and reliability of the product to meet the requirements of industrial application environment.

The FET113i-S SoM is developed and designed based on Allwinner T113-i industry processor, with a main frequency of 1.2GHz. It is equipped with multi-core and multi-architecture: integrated dual-core Cortex-A7,CPU64-bit XuanTie C906RISC-VCPU and DSP, which not only provides efficient computing power, but also has rich multimedia functions and complete interface resources; stamp hole design makes product more durable, and the development board draws out as much processor core resources as possible, which is a cost-effective choice for key areas such as industry, power, transportation and so on! This article will briefly share the process of adapting Forlinx T113i-S development board to LVDS screen display. Development platform: Forlinx T113i-S development board To modify the T113i screen, you need to modify the kernel and uboot respectively. Take the LVDS 1024 * 600 screen as an example. 1. Enter the following path; 2. Open OK113I-C-Linux.dts; 3. Modify the resolution parameters as shown in the figure below (for specific parameters, please refer to the screen manual of the screen you are using): 4. Save and exit after modification, and then start to modify uboot and enter the following path; 5. Open display-menu.c; 6. Modify the resolution parameters as shown in the figure below: 7. After modification, compile uboot under the initial path of the source code; 8. Complete compilation after successful compilation./build. Sh.; 9. After successful execution. /build.sh, pack image burned to the board to observe the phenomenon. Our above parameter modification can be successfully adapted to a new display, of course, the specific operation of different master control platform boards will be different, but the overall idea is the same, specific can be based on the corresponding platform to view the relevant information to determine the specific steps.

An intelligent service robot is a robot that integrates advanced technologies such as artificial intelligence, perception technology, and machine learning. Its purpose is to provide a variety of services and support to meet the needs of people in daily life, business, and industrial fields. These robots can sense the environment, understand speech and images, perform tasks, and interact naturally and intelligently with human users. Areas of Application: Business Services: It includes services such as reception, shopping assistance, and information inquiry, and can be used in places such as shopping malls, hotels, and exhibitions. Health Care: It provides services such as drug delivery, patient companionship and health monitoring for hospitals and nursing homes. Educational Assistance: It is used in educational scenarios to provide auxiliary teaching, answering questions and other services. Family Services: Provide cleaning, handling, home control and other services to improve the quality of life. The hardware structure of the service robot includes several key components. The functions and roles of these hardware components are as follows: Controls: As the core of the robot, the control device is responsible for receiving and processing the data provided by the sensors, executing the corresponding algorithms, and issuing instructions to the driving device to achieve the various functions of the robot. High-performance, low-power ARM chips are often chosen for the control unit, ensuring that the robot has sufficient computational and storage capacity. Drive unit: This includes motors and drivers, which are used to execute the motion and action commands of the robot. The motor is responsible for providing power, while the driver converts electronic signals into mechanical motion. This part is the motion system of the robot, which determines the execution of actions such as walking, turning, and the mechanical arm. Camera: As the ''eyes'' of the robot, the camera is used to capture images and facial information of the external environment. These image data can be used for tasks such as environmental perception, navigation, target recognition, allowing the robot to better understand and adapt to the surrounding environment. Sensors: Sensors provide the robot with various perceptual abilities, including vision, touch, hearing, and distance sensing, among others. Angle sensors and current sensors reflect the robot's own state, while temperature sensors, laser sensors, ultrasonic sensors, infrared sensors, etc. are used to collect external environmental information, allowing the robot to perceive and understand the surrounding situation more comprehensively. Display and Audio: As an important part of human-computer interaction, display and audio devices realize the presentation and interaction of user interface. The touch display provides an intuitive graphical user interface, while the voice interaction system enables the robot to understand the user's instructions and respond accordingly, thus better communicating with the human user. Folinx Embedded has launched the FET3588J-C SoM as the main control platform for this intelligent inspection robot product to meet customers' needs for machine vision and high-speed interfaces. FET3588J-C SoM is developed and designed based on Rockchip's RK3588 processor, integrating Cortex-A74-core-6 + 4-core Cortex-A55 architecture. The main frequency of A76 core is up to 2.4GHz, and the main frequency of A55 core is up to 1.8GHz, which can efficiently process the information collected by patrol inspection; The built-in NPU with comprehensive computing power of up to 6 TOPS greatly improves the calculation speed and energy efficiency of neural networks,providing robots with powerful AI learning and edge computing capabilities, enabling them to intelligently adapt to different work scenarios. RK3588J supports a 48-megapixel ISP3.0, which enables lens shading correction, 2D/3D noise reduction, sharpening and haze removal, fish eye correction, gamma correction, wide dynamic range contrast enhancement, and other effects. This significantly enhances the image quality. With abundant interface resources, it meets the robot's access requirements for various sensors. More sensor access helps the device to collect environment data more comprehensively. This platform also supports external storage interfaces such as SATA3.0, USB3.0, allowing data to be locally stored. It also supports wireless communication methods such as WiFi, 4G, and 5G, making it convenient for users to query device information on mobile devices. The rich functionality enables robots to perceive and understand the surrounding environment more comprehensively. It also has high stability. The platform’s SoM has undergone rigorous environmental temperature and pressure tests, and can operate for long periods in harsh industrial environments ranging from -40°C to +85°C, adapting to applications in various scenarios.

After checking the schematic of the OK1028A-C and the "QorIQ LS1028 AReference Manual", it is found that there are 8 FlexTimers (FTM) available by defaultLS1028on the board, with each FTM having 8 pwm channels. The default backlight uses the pwm generated by FTM1, and we use FTM7 to do the pwm test. As shown in the figure below: LS1028 RCWSR12 registers 12-14 are pin multiplexed for I2C4. As shown in the figure below: The I2C4 pin can be multiplexed into six pin functions. The OK1028A-C sets the pins to rx and tx of can2 , you can see T6_CAN2_RX, U7_CAN2_TX in the schematic "OK1028A-C_V1.1". We can set I2C4 to the pwm pin by modifying the rcw file. OK1028A-C supports the pwm function by default, so we do not need to transplant the driver. All we need to do is to modify the pinmux and add the corresponding device node of pwm in the device tree. Modify packages/firmware In the /rcw/ls1028ardb/RSQPP0x85bb/rcw1500gpu600.rcw file, the setting for IIC4_PMUX is to configure the pin as a pwm output. Change IIC4 _ PMUX = 2 to IIC4 _ PMUX = 4 As shown in the figure below: After completing the above settings, we need to modify the device tree code and add pwm configuration. The path of our modified file is as follows: packages/linux/linux/arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi. Then add the pwm7 device Pwm7: pwm@2860000 { compatible = "fsl,ls1028a-ftm-pwm"; reg =; #pwm-cells =; clock-names = "ftm_sys"; clocks = <&ftm_sysclk>; }; As shown in the figure below: ▐ Start the OK1028A-C system root@forlinx:~#cat /sys/kernel/debug/pwm View our current pwm devices As shown in the figure below: We have now opened a pwm controller and can see that FTM1 supports 8 channels, with the backlight using pwm channel 1. Compile the modified device tree file and firmware, burn them intoFolinx EmbeddedLS1028A-CDevelopment Board, and boot up the system. root@forlinx:~#cat /sys/kernel/debug/pwm View our current pwm devices. As shown in the figure below: At this time, although the pwm device we added is turned on, it is still different from the pwm0 device. Each channel of the newly added pwm device has no set period and duty cycle. So in the next step, we do not need to add driver code, but use sys to set pwm parameters directly. Pwmchip8 is the pwm device we added. ▐ Enable pwm channel used root@forlinx:~#echo 1 > /sys/class/pwm/pwmchip8/export Initialize pwm channel 1 root@forlinx:~#echo 2 > /sys/class/pwm/pwmchip8/export Initialize pwm channel 2 root@forlinx:~#cat /sys/kernel/debug/pwm CommandCheck out our current pwm devices: If you want to cancel the corresponding pwm channel, you can use "echo 1 > /sys/class/pwm/pwmchip8/unexport". “echo 2 > /sys/class/pwm/pwmchip8/unexport” command. Since we can only enable pwm one way at a time, configure and turn on pwm1 first. root@forlinx:~#echo 1000000 > /sys/class/pwm/pwmchip8/pwm1/period Configure the pwm1 period to be 1000000 in ns, which is 1kHZ. root@forlinx:~#echo 500000 > /sys/class/pwm/pwmchip8/pwm1/duty_cycle Configure the duty_cycle to 500000, the on time in a cycle is the duty cycle, the unit is ns, and the duty cycle is 50%. root@forlinx:~#echo 1 > /sys/class/pwm/pwmchip8/pwm1/enable Enable root@forlinx:~#cat/sys/class/pwm/pwmchip8/pwm1/{enable,period,duty_cycle}Command to view our pwm enable status, period, and duty cycle. As shown in the figure below: ▐ Test the 1khz square wave generated by T6_CAN2_RX with oscilloscope Since we can only enable one pwm at a time, we need to turn off pwm1 first if we want to enable pwm2. root@forlinx:~#echo 0 > /sys/class/pwm/pwmchip8/pwm1/enable root@forlinx:~#echo 1000000 > /sys/class/pwm/pwmchip8/pwm2/period Configure period to 1000000 root@forlinx:~#echo 500000 > /sys/class/pwm/pwmchip8/pwm2/duty_cycle Configure duty_cycle to 500000. root@forlinx:~#echo 1 > /sys/class/pwm/pwmchip8/pwm2/enable Enable root@forlinx:~#cat/sys/class/pwm/pwmchip8/pwm2/{enable,period,duty_cycle} ▐ Test the 1khz square wave generated by U7_CAN2_TX with oscilloscope When we use OK1028A-C single board computer, due to pin multiplexing, the pins of many functional modules are not led out, but the driver of the module is supported. In this case, we only need to modify the corresponding pinmux configuration and device tree file of rcw to use the corresponding function.

Forlinx Embedded OK113i-S development board has gained a lot of attention since it came into the market for some time, and it has also become a high-quality choice for many customers to select projects. In the actual project development, engineers may need to migrate some tools or protocols in the file system, so how to migrate them? We can port new functions in the Buildroot of the OK113i-S development board by adding the package configuration. This article will show you how to port the MQTT protocol in the Buildroot of the T113-i development board. Part 1 Configuration File Introduction First, take a look at the configuration files involved in porting functionality in Buildroot. View the existing configuration files in the source code of the embedded OK113i-S development board. The following files are included in the path: buildroot/buildroot-201902/package/mosquitto: Config.in mosquitto.mk mosquitto.hash mosquitto.service S50mosquitto ① Config.in The Config.in file informs Buildroot which package needs to be included in the compilation using BR2_PACKAGE_** as a switch. The switch is assigned in the OK113I_linux_defconfig configuration file located in buildroot/buildroot-201902/configs/, similar to the Kconfig file in the kernel. For example: The calling relationship is written in the package/Config.in source "package/mosquitto/Config.in"； The BR2_PACKAGE_MOSQUITTO information is written in package/mosquitto/Config.in. ② demo.mk This file declares some package information, such as the version of the specified package, the package source download link, the storage path, the compilation rules, the toolchain, and so on. When compiling, the source code package will be downloaded to the specified path according to the download address and version in this file, and then compiled and copied, which is equivalent to a Makefile file. For example: mosquitto.mk The software package version and download address are written at the beginning of the file, and we can find the corresponding version of the software package by visiting the address in the browser. When compiling, if the file is not in the source code, it will be downloaded automatically. mosguitto-1.5.8.tar.gz mosguitto-1.5.8.tar.gz.asc In addition, other compilation rules are defined in the file, including the file copy path and so on. ③ demo.hash This file will record the hash check code of the downloaded source code package to prevent errors in the downloaded source code package. ④ demo.service This file serves systemd. After systemd is started, the demo service will be started according to this file. The source path and installed path of this file will be specified in the demo.mk. The OK113i-S development board does not currently use this service, so it can be left alone. ⑤ S50demo It is a demo.service, which is the boot service type currently used by the OK113i-S development board. Among the above 5 kinds of files Config.in and demo.mk is required, and other files can be configured as needed. The specific configuration contents can be written according to the existing documents or the actual situation. Mosquitto already has a written configuration file, which can be used directly. Generally, the configuration file is provided by the maintainer or developer of the project. If there is no configuration file in the file you migrate, you can refer to the existing configuration file to write one. Part 2 Execution We need to generate in buildroot/buildroot-201902 make OK113I_linux_defconfig And then generate in make menuconfig ARCH=arm. Configure in the graphical configuration interface (if an error is reported during execution, please install the command first: sudo apt-get update and sudo apt-get install ncurses). After entering the graphic configuration interface, enter "/" to search for the function to be configured. As shown in the figure, search for the information seen by Mosquitto. Select "1" according to the prompt to enter the target option. Press "Space" to save and exit. After the configuration is complete, execute. /build.sh in the current directory to compile the file system, and then check if there are already corresponding files in the files system. (Note: If there is no network, the source code package cannot be automatically downloaded during compilation. You need to manually download the source code package from the download address and put it in the source code package storage path.) Part 3 Test verification of MQTT Modify the /etc/mosquitto/mosquitto.conf file of the OK113i-S development board, add a line user root after #user mosquitto, and reboot the service or development board. You can also kill the process and re-execute it: /usr/sbin/mosquitto -c /etc/mosquitto/mosquitto.conf Then test—— Subscribe to the test topic: mosquitto_sub -t test & Release the test topic: mosquitto_pub -t test -m "hello world" If you can see the word hello world returned, it means that the migration is successful. Above is the method to port MQTT protocol in Buildroot of Forlinx Embedded OK113i-S development board for engineers in front of the screen.

Install Wire Guard in the RK3588 Forlinx Desktop image Solution: Mount the Forlinx Desktop image file into the development environment for installation. (1) Download qemu-user-static in the development environment sudo apt-get install qemu-user-static (2) Mount the img image of Forlinx Desktop to a directory, I have mounted it to the test directory. sudo mount focal-rootfs.img test/ (3) Use the chroot command to enter the test directory sudo chroot test/ (4) Install WireGuard apt-get install wireguard-dkms wireguard-tools wireguard Solutions that cannot be used after installation: To add the TUN and WireGuard options to the kernel, proceed as follows: 1. Modify the build. Sh in the SDK to add the $KMAKE menu config; 2. Execute. /build.sh, search for TUN and wireguard in the graphical configuration interface and check them off; Save and Exit. 3. Overwrite OK3588-Linux _ defconfig with.config 4. Re-flash the image; 5. Set the IP.

The default display orientation for the Android interface on the Forlinx Embedded i.MX8MP platform is landscape, but some products may require a portrait display. To address this requirement, Forlinx Embedded provides the following methods for modification: The Android system controls the screen orientation through the persist.vendor.orientation property, which can have values of 0, 90, 180, or 270. Configuration path: frameworks/native/services/su**ceflinger/Su**ceFlinger.cpp Modify in processDisplayHotplugEventsLocked: Su**ceFlinger::processDisplayHotplugEventsLocked() { continue; } + /* Rotate desktop */ + char rotationvalue[PROPERTY_VALUE_MAX] = "";; + property_get("persist.vendor.orientation", rotationvalue, "-1"); + int rotation = atoi(rotationvalue); + ALOGI("Primary Display Orientation is set to rotation %2d.", rotation); + switch (rotation) { + case 0: + internalDisplayOrientation = ui::ROTATION_0; + break; + case 90: + internalDisplayOrientation = ui::ROTATION_90; + break; + case 180: + internalDisplayOrientation = ui::ROTATION_180; + break; + case 270: + internalDisplayOrientation = ui::ROTATION_270; + break; + default: + break; + } + const DisplayId displayId = info->id; const auto it = mPhysicalDisplayTokens.find(displayId); After modification, you need to add the relevant configuration in the environment variable. Path: device/nxp/imx8m/evk_8mp/system.prop persist.sys.timezone=Asia/Shanghai persist.sys.language=zh persist.sys.country=CN +persist.vendor.orientation=90 Rotate 90 degrees here to write 90, 180 degrees to write 180, 270 degrees to write 270. If you encounter a failure to set the value of a property: Add the followings in device/nxp/imx8m/sepolicy/property_contexts; +persist.vendor.orientation u:object_r:debug_prop:s0 vendor.wc_transport. u:object_r:vendor_wc_prop:s0 persist.vendor.usb.config u:object_r:vendor_usb_config_prop:s0 vendor.usb.config u:object_r:vendor_usb_config_prop:s0

A blood cell analyzer is one of the widely used instruments in clinical laboratory testing in hospitals. It classifies white blood cells, red blood cells, and platelets in the blood using the resistance method. It can also provide data related to blood such as hemoglobin concentration and hematocrit. In clinical applications, it can be used for white blood cell counting, neutrophil counting, lymphocyte counting, red blood cell counting, and other clinical tests. It is an important reference for doctors to diagnose patients' conditions. Function requirements Detection parameters: The instrument should be able to detect common blood parameters including red blood cells, white blood cells, platelets, hemoglobin, and white blood cell differentials. Sample handling: The instrument should be capable of automated sample loading, sample distribution, cleaning, and waste disposal. Accuracy: The instrument should have high measurement accuracy and repeatability to meet clinical diagnostic requirements. Usability: The instrument should have a user-friendly interface that is easy to operate, allowing laboratory personnel to use it with ease. Data analysis: The instrument should have the capability to automatically generate test reports and perform basic data analysis based on the test results. Hardware design requirements Controller: A high-performance microprocessor is used as the main controller of the instrument, which is responsible for realizing various control logic and data processing. Power supply module: Use a stable power supply module to ensure consistent instrument performance in various environmental conditions. Detection Module: According to the blood indexes to be detected, design the corresponding detection module, such as optical detection module, electrical detection module, etc. Detection Module: According to the blood indexes to be detected, design the corresponding detection module, such as optical detection module, electrical detection module, etc. Human-computer interaction: Use a touch screen as the operation interface, which is convenient for laboratory staff to use. At the same time, it has a printing function, which can print out the test results. Data storage: Data can be stored through built-in memory chip and SD card. Design scheme For the functional characteristics of the blood analyzer, Forlinx Embedded recommends the FETMX8MM-C system on module as the hardware development platform, which is equipped with ARM Cortex-A53*4+Cortex-M4 processor with 1.8GHz main frequency. It supports LPDDR4 and eMMC storage to configure the appropriate memory and flash on demand. i.MX8MM SoM With multiple interfaces: It includes display interface, supports external screens of various specifications and sizes, and is compatible with resistive capacitive touch, providing excellent human-computer interaction experience. USB interface is convenient to connect external devices, such as U disk, mouse, WiFi, 4G, printer, etc. The network interface includes 10/100/1000M Ethernet, 4G module and WiFi module to realize efficient communication with hospital HIS and laboratory information system LIS. The SPI bus is used to extend the FPGA to support various applications such as motor control, gate valve control, and AD sampling. The serial port is used to communicate and control with the bar code machine, the lower electromechanical structure and other equipment. For external storage, TF and SD cards are supported for storing computing data, analyzing results, and so on. The FETMX8MM-C Core board has a wide range of applications in the medical field, providing high-performance and multi-functional processing power for medical devices, and helping to realize a smarter and more convenient medical information system.