The open-source Iot framework ServerSuperIO 3.0 was officially released (C #), cross-platform: Win & amp; Win10 Iot & amp; Ubuntu Mate, a set of device drivers mounted across platforms, attached: development Kit and tutorials .,

The open-source Iot framework ServerSuperIO 3.0 was officially released (C #). cross-platform: Win & Win10 Iot & Ubuntu Mate, a set of device drivers mounted across platforms, attached: Development kits and tutorials .,

Major updates of version 3.0:

1. Added cross-platform capabilities: Win & Win10 Iot & Ubuntu Mate

2. Unified Device Driver Interface: a device driver can be mounted and run across platforms to reduce labor costs and improve development efficiency.

3. added the secondary development kit. The console and UI interfaces are supported.

4. Added configuration tools: parameter configuration, device drive mounting, view mounting, and service instance mounting.

5. fix bugs and optimize code.

SSIO features

1. Light-weight and high-performance communication framework, applicable to a variety of application fields, polling mode, automatic control mode, concurrency mode, and Singleton mode.
2. It is not only a communication framework, but also a coordination mechanism for device drivers, IO channels, and control mode scenarios.
3. Supports protocol drives and can write standard and custom protocols according to specifications.
4. Supports sending data caches, command cache resends, and priority-based sending.
5. Supports protocol filters, filters data by rules, and supports custom filtering through interfaces.
6. Supports receiving data caches to cache data that does not comply with the filter and splice the data received next time.
7. Support scheduling devices by device command priority to ensure that drivers with advanced commands can be sent in a timely manner.
8. Supports one device driver, and supports both the serial port and network communication modes to monitor the data of the I/O channel.
9. One device driver is supported. TCP Server and TCP Client modes are supported during network communication.
10. Multiple devices can share the same I/O channel for communication.
11. Supports timed cleaning of network I/O channels that have timed out.
12. The display view interface is supported to meet different display requirements.
13. Supports service component interfaces to customize the OPC Service, 4-20mA output, LED dashboard display, SMS service, and multi-function gateway service.
14. Multiple service instances can be created to split different services.
15. Supports cross-platform deployment and runs on Linux and Windows systems.
16. device drivers and device drivers. device drivers and servers (on the cloud) can interact with each other in real time to upload data and send commands.

SSIO Overview

The SSIO communication framework is developed on the basis of SuperIO (SiO2) and has no advanced technology, mainly the accumulation of work experience, suitable for Iot data collection and interaction in different application scenarios. SSIO and SiO2 are not simple IO high-performance operations, but a coordination mechanism between device drivers, IO channels, control modes, and actual hardware devices. They can be seamlessly connected and operated in various aspects, it is also a pain point for solving practical work and application scenarios. Data Interaction Between Software and Hardware faces a complex field environment:
(1) complex and diverse communication protocols. There are standard protocols, such as Modbus, and many protocol formats modified according to the standard protocol, as well as custom protocol formats, which are very different. For a poor software architecture, it is difficult to cope with it. To increase the number of devices or protocols, we need to sort out the entire software. New problems or bugs often occur in this process.
(2) Different users have different requirements on the software interface or functions to meet the display requirements of different users and can customize the data display interface. You need to provide a display view interface to interact with the device driver.
(3) Since the data of the on-site equipment is collected, it must be processed, not only for saving, querying, and reporting, but also: data Forwarding and data output (OPC, analog, dashboard, etc. A service interface is required to interact with the device driver.
(4) Diversity of communication links. communication methods such as RS232, RS485, RS422, RJ45, and 3G/4G may be supported for the same device, therefore, a device must correspond to multiple communication methods (Serial Port and Network), which also causes great obstacles to our development.
(5) the link between the device driver, I/O channel, and the actual on-site hardware terminal is complex and may be: one device driver corresponds to one I/O channel, one device driver corresponds to multiple I/O channels, and multiple device drivers correspond to one I/O channel.
(6) since the device interacts with the server, the device's communication status, I/O status, and the status of the device itself should be monitored so that the device can be maintained.
(7) software versions, poor compatibility between software and hardware, and complicated management. When the Framework Platform is stable, you only need to update the device driver.
To solve the above problems, develop a software framework and support secondary development. Without modifying the software framework, you can easily access devices, maintain devices, integrate devices, and process device business data. The software framework is relatively stable, and the easy-to-change part is flexibly designed.

Download: Official ServerSuperIO download

Download: Github download

Serialization Tutorial:

1.4 communication modes
2. Description of service instance configuration parameters
3. Device Drivers
4. For example, develop a device driver that supports both serial and network communication.
5. Polling communication mode development and precautions
6. concurrent communication mode development and precautions
7. Self-control communication mode development and precautions
8. single-instance communication mode development and precautions
9. Protocol filters are used to solve multiple packets of redundant data.
10. Two Methods for continuous transmission of large data streams (for example, files)
11. Implement interaction and cascade control between devices (drivers) and devices (drivers.
12. Service Interface Development and two-way interaction with the cloud
13. Custom View display interface development to meet different display requirements
14. Introduction to preparation tools and mounting of device drivers, view drivers, and service instances

 

 

1. [serialization] C # communication (Serial Port and network) Framework Design and Implementation

2. [Open Source] C # cross-platform Iot communication framework ServerSuperIO (SSIO) Introduction

2. Overall system construction solution using SuperIO and open-source cross-platform Iot framework ServerSuperIO

3. C # technical route of industrial IoT and integrated system solutions (data sources, data collection, data upload and receiving, ActiveMQ, Mongodb, WebApi, and mobile App)

5. ServerSuperIO Open Source Address: https://github.com/wxzz/ServerSuperIO

Internet of Things & integrated technology (. NET) QQ Group:54256083