Serialization | Iot framework ServerSuperIO tutorial-13. Custom View display interface development to meet different display requirements

Serialization | Iot framework ServerSuperIO tutorial-13. Custom View display interface development to meet different display requirements

1. C # Introduction to cross-platform Iot communication framework ServerSuperIO (SSIO)

Serialization | Iot framework ServerSuperIO tutorial 1.4 communication modes and mechanisms.

Serialization | Iot framework ServerSuperIO tutorial 2. service instance configuration parameters

Serialization | Iot framework ServerSuperIO tutorial-3. Device Driver Introduction

Serialization | Iot framework ServerSuperIO tutorial-4. For example, you can develop a device driver that supports both serial and network communication.

Serialization | Iot framework ServerSuperIO tutorial-5. Polling communication mode development and precautions.

Serialization | Iot framework ServerSuperIO tutorial-6. concurrent communication mode development and precautions

Serialization | Iot framework ServerSuperIO tutorial-7. Self-control communication mode development and precautions

Serialization | Iot framework ServerSuperIO tutorial-8. single-instance communication mode development and precautions

Serialization | Iot framework ServerSuperIO tutorial-9. protocol filter to solve multiple packet-related, sticky packet, and redundant data

Serialization | Iot framework ServerSuperIO tutorial-10. Two Methods for continuous transmission of large data streams (such as files)

Serialization | Iot framework ServerSuperIO tutorial-11. Implement device (driver) and device (driver) interaction and cascade control.

Serialization | Iot framework ServerSuperIO tutorial-12. Service Interface Development and bidirectional interaction with the cloud

 

Contents

13. Custom View display interface development to meet different display requirements... 2

13.1 overview... 2

13.2 View display interface... 2

13.3 device driver development and precautions... 4

13.4 running results... 5

13. Custom View display interface development, meeting different display requirements 13.1 Overview

If ServerSuperIO is deployed on the server, there is no need to develop View display on the SSIO View Interface. You can use the WEB terminal to do this. If ServerSuperIO is deployed on a PC or embedded host with an on-site display screen, a real-time display interface is required to meet different needs of on-site users. To address this problem, ServerSuperIO provides a view display interface. After the device driver extracts the data, it can transmit the data to the View Interface in real time to display the data immediately or cache the data first, the data of several device drivers can be displayed in one view or all device drivers can be displayed in one view. Example:

 

13.2 View display interface

View abstract class GraphicsShow inherits from the IGraphicsShow interface. Secondary Development can inherit GraphicsShow abstract class. After the View Interface is developed on ServerSuperIO, it can be mounted and run under the secondary development kit (download the secondary development kit ). Pay special attention to the following points during secondary opening:

The GraphicsShow interface code is defined as follows:

Public interface IGraphicsShow: IPlugin {// <summary> // view Key, which must be unique // </summary> string ShowKey {get ;} /// <summary> /// view name /// </summary> string ShowName {get ;} /// <summary> /// display form /// </summary> /// <param name = "windows"> </param> void ShowGraphics (IWin32Window windows ); /// <summary> ///// </summary> void CloseGraphics (); /// <summary> /// update the device /// </summary> /// <param name = "devCode"> device code </param> /// <param name = "obj"> device object </param> void UpdateDevice (string devCode, object obj ); /// <summary> /// remove the device /// </summary> /// <param name = "devCode"> device code </param> void RemoveDevice (string devCode ); /// <summary> /// when the form event is closed /// </summary> event GraphicsShowClosedHandler GraphicsShowClosed; /// <summary> /// right-click, call the context menu /// </summary> event MouseRightContextMenuHandler MouseRightContextMenu; /// <summary> /// whether it is released /// </summary> bool IsDisposed {get ;}}

13.3 device driver development and precautions

List<string> list = new List<string>();list.Add(_devicePara.DeviceCode);list.Add(_devicePara.DeviceName);list.Add(_deviceDyn.Dyn.Flow.ToString());list.Add(_deviceDyn.Dyn.Signal.ToString());OnDeviceObjectChanged(list.ToArray());

2. display the context menu. The MouseRightContextMenu of the View Interface calls the ShowContextMenu interface function of the device driver. The Code is as follows:

 public override void ShowContextMenu()        {            this._contextMenuComponent.ContextMenuStrip.Show(Cursor.Position);        }

13.4 Running Effect

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 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