Synergy Demo. WiFi Communication

Transcription

1 1. Introduction This Demo illustrates the WiFi communication between a PE-HMI board and a SK-Kit over Ethernet with a Route: the PE-HMI board works as client and the SK-Kit as Server. The PE- HMI board sends the actual time and the information of the sine curve to the SK-Kit every second, so that there are the same time and sine curve on the displays of the both kits. The application also includes key elements to demonstrate how they work together in a typical design, including: ThreadX RTOS, WiFi stack, Ethernet Server and Client, LCD driver, GUI design/ Animation, etc.. On the PE-HMI board, there is a WiFi Module GT202 mounted which is conneced with S7 MCU over SPI (please see Fig. 2). The SK-Kit connects with the Route over Ethernet cable. These three kits build a samll WiFi communication system. 1 Fig.1 The Hardware of this Demo

2 Fig. 2 Synergy PE-HMI board with WiFi Module GT202

3 Fig. 3 The displaying on PE-HMI board (as client) Fig. 4 The displaying on Start-Kit (as server)

4 Fig. 5 The used Route 2. Connect to the Board This section describes how to connect the board to power, the J-Link debugger to the PC, and the connection of the both kits. Refer to the Quick Start Guide for PE-HMI1, DK-S7G2, DK-S3A7, or SK-S7G2 for setting up the power connection and the J-link debugger connection from your PC to the JTAG connector on the target board 2. The SK-Kit connects with the Route over Ethernet cable 3. Import the Project into e2 studio These zipped demo project files can be copied from: XXX Refer to the "Synergy Project Import Guide" 2 (r11an0023eu0100_synergy_ssp.pdf) for instructions on importing the project into e2 Studio and building/running the project. When debugging, use the PE_HMI_S7_WiFi_Framework_1_2_0 Debug and project Debug configuration. The following tools should be used for compile and debug: e2 studio V SSP V1.3.0 GNU V GUIX V Wi-Fi application

5 Fig. 6 Control Flow details with different modules The software structure of WiFi is descripted as above figure. The software of Wireless Device Driver, WMI, HTC, BMI and Wireless Firmware come from the company Longsys Electronics Co. who provides also the hardware GT202. The Express Logic s NetX is used as the networking stack to handle all the TCP/IP communication. Following are the explanation of these interfaces: Wireless Device Driver /Wireless Module Interface: When the wireless application needs to send control messages to the chipset it calls into the WMI layer to create the messages. This layer understands the host/target WMI protocol. Host/Target Communication (HTC): The wireless device driver calls into the HTC layer to handle message transport. HTC handles the flow control and knows the hardware address for read and write operations. The Hardware interface is the layer between the driver and the RSPI hardware interface. The driver calls into this layer when it needs to access the register and memory access of the wireless controller. RSPI is the standard interconnect (SPI) used for communicating to the wireless controller. With the RSPI, higher speed can be achieved. Following is the configuration of Wi-Fi application. Because we use the DHCP to get the dynamic IP address, so there is a DHCP Client component integrated.

6 5. Architecture Fig.7 The configuration of WiFi Application A high-level view of the architecture of this application is shown below.

7 5.1 Client tcp Thread Time update: TimeUpdate() Events to HMI Thread: gx_system_event_send() WiFi Thread Wifi provision: net_wifi_provision() Init DHCP: nx_dhcp_start() Get IP address: nx_ip_address_get() Info to Client: nx_tcp_socket_send () HMI Thread Events receiving, text update, display update: optional1() Sine chart drawing: chart_window_draw() 5.2 Server RTC Thread Info from Server: nx_tcp_socket_receive() Events to HMI Thread: gx_system_event_send() HMI Thread Events receiving, text update, display update: optional1() Sine chart drawing: chart_window_draw() 5.3 Function description of the Client In the Client of this demo, the Time Thread, WiFi Thread and HMI thread are added.

8 In the Time thread, the function rtc_thread_entry() provides a system clock from RTOS that the function TimeUpdate() uses to generate the new clock and sine information, it sends also an event with the clock and sine chart information to the HMI thread every second through using system function gx_system_event_send(). In WiFi Thread, the function WiFi_thread_entry() sends this clock and sine chart information that are generated by Time thread every second to Server over WiFi interface through calling nx_tcp_socket_send (). To build the connection with the Server, it calls also some system functions such as nx_tcp_socket_create(), nx_tcp_client_socket_bind(), nx_tcp_client_socket_connect(), nx_tcp_client_socket_unbind(), etc. In WiFi Thread, there are additional two tasks: 1) Wi-Fi provisioning through calling net_wifi_provision(), the Network Name (SSID) and Passphrase should be inputted at first. 2) Getting the dynamic IP address through call nx_dhcp_start() and nx_ip_address_get(). The SSID and Passphrase should be written into the line 3 and 4 of file wifi_thread_entry.c. The Server can use any other IP address than the Client, but its first 3 bytes should be the same as Client! The IP address of Client should be written into the line 154 of file wifi_thread_entry.c In HMI Thread, the function options1() receives the events that come from Time Thread, and from them it gets the clock information and shows them on TFT in time; at the same time, through calling the function chart_window_draw() and using the information coming from Time Thread it updates the sine chart which moves left about PI/6 at every update. 4.4 Function description of the Server In the Server of this demo, the RTC Thread and HMI thread are added. In RTC Thread, through calling the function nx_tcp_socket_receive() continuously, the Server gets the new clock and sine chart information every second, these information are also sent to the HMI thread every second through using system function gx_system_event_send(). To build the connection with the Client, it calls also some system functions such as nx_tcp_socket_create(), nx_tcp_server_socket_listen(), nx_tcp_server_socket_accept(), nx_tcp_socket_disconnect(), etc. The IP address of Client should be written into the line 67 of file demo_nx_http_dhcp_application.c In HMI Thread, the function options1() receives the events that come from RTC Thread, and from them it gets the clock information and shows them on TFT in time; at the same time, through calling the function chart_window_draw() and using the information coming from RTC Thread it updates the sine chart which moves left about PI/6 at every update. 4.5 Function description of GUI and LCD The screen of the both Server and Client is similar, so their GUI design and their software also are similar.

9 Through using the GUIX, the screen is defined which includes the both widgets Text und window which are used to show the clock information and Sine chart, it includes also a wallpaper on which our company symbol is showing. To display the text and the sine chart, some GUI functions are used such as gx_canvas_line_draw, gx_prompt_text_set, gx_system_dirty_mark, etc.. To use the TFT and GUI, man should at first initiate them, which can be seen in function hmi_thread_main(). 6. Application Features This section describes the key features of this demo application and the steps needed to run the application. This demonstration application illustrates the WiFi communication between the two Synergy kits over WiFi/Ethernet through these four functions: Create a server interface and write its application software in the start- kit Create a client interface and write its application software in PE- HMI kit Including features such as Wi-Fi provisioning, initiating DHCP, etc. Write the software to display a clock and the sine curve on the TFT of the both kits Synchronize the time and the sine curve in both kits To run the demonstration application: 1. Click Resume twice. 2. If the connection is broken, on PE- HMI kit the time and the sine curve are updated every second, but on start- kit, the both information are frozen; after the both kits are connected again, the time and the sine curve are updated on both kids every second and these information should be always identified. 3. Click Terminate to close the debugger. 1. If you have any questions or want to get the source code of this demo, please do not hesitate to contact Mr. Weizhong Xu, Weizhong.Xu@rutronik.com. 2. This file / these files can be found under the path XXXX