Blog.WIZnet.HK

Official Blog of WIZnet HK

[wiznethk]

PoE FeatherWing offers 4W and unique MAC

Patrick Van Oosterwijck and Silicognition are gearing up to launch a new crowdfunding campaign for their PoE FeatherWing, which is capable of providing 4 W of power and offers a globally unique MAC address. Soon to be launched via the Crowd Supply website, anyone interested in being kept up-to-date and notified when the campaign starts can register their details via the link below.

“Adafruit provides an Ethernet FeatherWing for its popular Feather ecosystem—a valuable option for IoT and automation projects. But it has its limitations. The Feather still needs to be powered separately, and no globally unique MAC address is provided for the user, making deployment hard. What if we could fix these issues? What if there was a drop-in replacement that would not only provide Ethernet, but also power your Feather, and give you a globally unique MAC? And still be 100% compatible in size, connections and software support? Enter the PoE-FeatherWing!”

Features of the PoE FeatherWing include :

– PoE: Isolated IEEE 802.3at Class 1, Mode A and Mode B Power over Ethernet, with 4 W of output power available. – Globally unique MAC address: A Microchip 24AA02E48 provides a real globally unique MAC address, allowing actual field deployment. – Works with existing software: A WIZnet W5500 Ethernet controller ensures full compatibility with existing software written for the Adafruit Ethernet FeatherWing. – Drop-in replacement: With board size and connections identical to the Adafruit Ethernet FeatherWing, it’s a true drop-in replacement. – Giant Board compatibility: A solder jumper allows for easy compatibility with the Giant Board Feather form-factor Linux SBC, without needing to add a fly wire for the IRQ (interrupt request signal).

Unfortunately, no information on pricing or worldwide availability has been released as yet for the PoE FeatherWing, but as soon as information is made available, we will keep you up to date as always.

Source : Geeky Gadgets : Crowd Supply  : Adafruit

[wiznethk]

Global Ethernet Controllers Industry Market 2019 IDEC Corporation, Panasonic, Micrel, Microchip, WIZnet Inc

BY AMOL GHATE ON DECEMBER 17, 2019 Global Ethernet Controllers Market Report 2019 to 2028 is an explicit analysis of the global Ethernet Controllers market. The material consists of trending technology, market drivers, regional inclinations, market statistics, market predictions, manufacturers, and equipment vendors. The report provides a detailed analysis of the Ethernet Controllers along with enabling technologies, ongoing trends, opportunities, obstacles, self-governing perspective, deployment models, operator specific situations, future plan of action, supply chain, profiles of leading players in the ecosystem along with policies. The document even provides speculations for Ethernet Controllers from 2019 till 2028. Geographically this Ethernet Controllers market report covers all the major manufacturers from significant continents like Europe, South America, North America, East, and South Africa, and Asia-Pacific. Key players specified in the Ethernet Controllers report: IDEC Corporation, Panasonic, Micrel, Microchip, WIZnet Inc...

https://marketnewsworld24.com/147026/global-ethernet-controllers-industry-market-2019-idec-corporation-panasonic-micrel-microchip-wiznet-inc/

[wiznethk]

IoT iOffload Design Contest

MAY 1 ~ AUG 31

Total Prize $15,000

https://maker.wiznet.io/contests/contest-in-progress/201905-iot-ioffload-contest/

“IoT iOffload Contest” is an international project contest for developers worldwide, powered by WIZnet. This contest gives developers an opportunity to showcase their skills in IoT innovation and competency.

For the first time in the world, “IoT iOffload Contest” is using hardwired TCP/Dual(IPv4/v6) to develop new opportunity. If you want to learn more about IPv6 and hardwaired TCP/Dual, please refer these documents; What is TCP/IPv6, How to use hardwired TCP/Dual.

We can’t wait to see what you make!

[wiznethk]

Enter @WiznetTeam's global design contest with $ 10,000 total prizes. Is the Competition AT & More View all related materials learn the JOIN https://www.hackster.io/contests/wiznet

Even if one write just a simple IoT idea by 4/20, then free IoT kit will be shipped free of charge all over the world! (WIZ750SR-EVB kit, Up to 200 person)

[wiznethk]

Blog.WIZnet.HK turned 2 today! 今天兩週年了！

[wiznethk]

WIZnet HK 發布最新的串口轉以太網模塊

WIZnet H. K. 很快就要有一個新的串口轉以太網模塊。 該模塊被稱為 W5500S2E-S1。由 WIZnet H. K. 的成員製作，它使用了最新的硬件 TCP / IP 核心 W5500 芯片，用於以太網通信的關鍵部分。

該模塊是基於 WIZnet 公司最暢銷的串口轉以太網解決方案 WIZ100SR 來設計而使用 W5500 芯片的類似模塊。請參考此模塊的以下特性：

串口轉以太網模塊基於 W5500 與 Cortex-M3

內建變壓器，引腳頭型模塊

10 / 100Mbps 以太網

最高 1.152Mbps 串行速度

支持 TCP / UDP 操作模式

支持 DHCP，DNS 協議

支持密碼功能

支持網頁配置

配置工具程序和串行 AT 命令

支持本地和遠程固件升級

通過用 WIZ100SR 模塊進行比較，新模塊 W5500S2E-S1 包含標準的 TCP 和 UDP 通信。然而卻提供了多種方法來配置，提高了對使用此模塊的靈活性的模塊。

在本文中，我們將介紹這個模塊的三個主要的配置方法。

1. 這是配置 WIZnet 的解決方案的最常見的方法。所有串口轉以太網模塊都會有自己的配置工具的版本。新模塊的配置工具與同系模塊都具有類似的外觀，可以讓用戶快速適應。然而 W5500S2E-S1 將有它自己的配置工具版本，如下圖所示。

這上面是配置模塊的基本設置 (Basic Setting)。包括通過 W5500S2E-S1 模塊進行通信的串口設置，網絡設置和通信協議。與其他WIZnet公司的串口轉以太網產品一樣，還包括固件升級和恢復出廠設置按鈕，。 由於該模塊是繼承 WIZ100SR，包括數據控制功能，提供能滿足客戶要求通信方法。這些設置位於高級選項 (Advanced Option)，如下圖所示的。

除數據包裝，還包括通信保安及其他功能，允許用戶很容易配置模塊。 欲了解更多信息，請訪問我們的官方網站，參考 W5500S2E-S1 模塊的用戶手冊。

2. 頁面配置 W5500S2E-S1 模塊集成了一個 HTTP 服務器，支持網站訪問配置。 默認信息登錄到網頁配置 A）IP地址：192.168.1.88 B）Netbios（使用的名稱登錄到網頁）：W5500S2E C）端口號：80（它可以改變為其它端口號） D）默認 PW：管理員 登錄後，顯示如下。

由於功能與配置工具完全一樣，用戶可以很容易使用此網頁界面配置或升級固件版本。 3. AT 命令配置（串行接口通信） 近來，WIZnet 公司已經開始使用 AT 命令作為其主要的串行配置方法來配置自己的模塊。這命令比先前串行配置方法更簡單和更用戶友好。 對於這種類型的命令，有幾點用戶應該知道。 它要求用戶在每個命令的前面加上“AT +”。這些命令的列表顯示了此模塊的用戶手冊。 這個串行命令。

在 W5500S2E-S1 的默認設置，模塊在 AT命令模式下啟動。

AT（包含回車）是檢查終端連接到模塊與否。

“+++”（不包含回車）命令將模​​塊從數據模式下更改為 AT命令模式。

AT + EXIT 用於保存 AT 命令設置和退出 AT 命令模式。

下面是通過 AT 命令創建 TCP 服務器連接的例子。

[wiznethk]

WizFi310 Overview

Overview

WizFi250 offers a quick, easy, and cost-effective way for device and appliance manufacturers to add WiFi capabilities to their products. WizFi310 provides UART interfaces which enable connections to any embedded design utilizing an 8/16/32-bit microcontroller via simple AT commands. WizFi310 is an ideal solution for organizations with limited or no WiFi or RF expertise, as it not only reduces RF design time but also removes the burden of testing and certification, allowing customers; allowing customers to focus on their core application, product, or expertise. WizFi310 is compliant with 802.11b/g/n.

Features

◾ Single band 2.4GHz IEEE 802.11b/g/n

◾ Integrated RF power amplifier

◾ 20MHz and 40MHz bandwidth transmission

◾ Maximum data rate 54Mbps in 802.11g and 150Mbps in 802.11n

◾ 1MB Flash Memory, 128KB SRAM, 1MB Serial Flash

◾ Low power consumption & excellent power management performance extend battery life.

◾ Small size suitable for low volume system integration.

◾ Easy for integration into mobile and handheld device with flexible system configuration.

◾ Lead Free design which supporting Green design requirement, RoHS Compliance.

◾ Device Package : –PA: 28x20mm ; ..-CON: 17x20mm

◾ Serial Interface : UART

◾ UART Max Baud : 921600 bps

◾ Powerful Web server provides

◾ Soft AP

◾ Enough memory retention

◾ Wi-Fi Security (WEP, WPA/WPA2PSK)

◾ L2 Switching

◾ OTA(Over The Air F/W Upgrading)

[wiznethk]

A new Serial to Ethernet module is coming out soon in WIZnet HK

Hey, everyone! WIZnet HK is going to have a new Serial to Ethernet module soon. 

This module is called W5500S2E-S1. It is made by WIZnet HK members and it used the latest Hardwired TCP/IP solution W5500 chip as the key section for Ethernet communication. 

This module is based on WIZnet’s best selling Serial to Ethernet solution WIZ100SR to design a similar module in W5500 chip.  Please refer the following features about this module. 

Serial to Ethernet Module based on W5500 & Cortex-M3

Transformer mounted, Pin-header type module

10/100Mbps Ethernet

Max.1.152Mbps serial speed

Support TCP/UDP operation modes

Support DHCP, DNS protocols

Support password function for security 

Support Webpage configuration,

Configuration tool program & Serial AT command.

Support local and remote firmware upgrade

By comparing with WIZ100SR module, it contains the standard TCP and UDP communication in the latest module. However, it has provides more kinds of method to configure the module that improves the flexibility on using this module. 

For this article, we will introduce the three main configuration method of this module. 

1. GUI interface in Window OS software - Config tool

This is the most common method for configuring WIZnet’s solution. All the serial to Ethernet module will have their own version of configuration tool. However,  all of these module’s are having a similar appearance that allows user quickly to get used to it . Thus, W5500S2E-S1 will have its own version of configuration tools as the following figure shows.

This above is the basic settings for configure the module. It includes serial settings, network settings and communication protocol that you could use to communicate through W5500S2E-S1 module. It also includes Firmware upgrade and factory reset buttons like the other WIZnet’s serial to Ethernet products. 

As this module is following WIZ100SR, it includes data controlling features for providing a more communication method that could satisfy customer’s requirement. These settings are located on the Advanced Options tab that shows as the following figure.

Except the data packaging, it includes communication security and other additional functions that allows user could easily configure the module. 

For more information, please go our official website to get our user manual of this W5500S2E-S1 module.  

2. Webpage configuration

This module has included a HTTP server for accessing the configuration website to configure W5500S2E-S1 module. 

Default information to login into configuration webpage

a) IP address: 192.168.1.88

b) Netbios (Using name to login into webpage): W5500S2E

c) Port number: 80 (It can be changed to other port number)

d) Deafult PW: admin

After you login, it shows as the result as follow.

As the functionality will be totally the same as configuration tools, user could easily base on the information that provided on the website on configure or upgrading Firmware version using this webpage interface. 

3. AT command configuration (Serial interface communication)

In the recent days, WIZnet has started to use AT command as their main serial configuration method to configure their modules. This command is simple to use and more user friendly than previous serial configuration methods.

For this type of commands, it requires user to add “AT+” in front of each commands. The list of these commands shows in this module’s user manual.

About this serial commands, there are few points that users should know. 

1.  In default setting of W5500S2E-S1, it will starts the module in AT command mode.

2. AT (with enter) is checking the terminal is it connected to the module.

3. “+++” (without enter) command will change the module from data mode to AT command mode. 

4. AT+EXIT is used for save the AT command settings and the way to exit AT command mode.   

The following is an example to create a TCP server connection through AT command.

Thank you for reading this article.

[wiznethk]

Develop HK Traffic System on PushingBox and WizFi250 in Twitter

This time I try to use WizFi250 to upload the weather information and Traffic system status to pushingbox cloud server. The user can receive the message through twitter.

Before you start this selection, you should read the article of “Develop IOT solution by using Pushing box and WizFi250 in Twitter” that will make you more understanding on Pushingbox and WizFi250.

In PushingBox Setting: Enter to My Scenarios, you can find your “Scenario name” & “Device ID”. Press the “Manage” button to enter my service.

Press the “Edit” button in Twitter scenarios to view the internal setting.

Please input your Message format that will show on twitter: Message: 吐露港公路近沙田污水處理廠, Temperature: $temp$ Humidity: $humid$ URL: http://traffic.td.gov.hk/DisplayImage.do?id=041209&time=PzsPeHhm5TvHVSH+eF+V6Q== (PS: URL source from HK Transport Department)

In WizFi250 Setting: Obtain the Xively API sever IP PushingBox API Server : 213.186.33.19 PushingBox API Port: 80

Association to AP in WIZfi250 AT+WLEAVE [OK] AT+WSET=0,wiznet,, [OK] AT+WSEC=0,WPA2,vickitjohn [OK] AT+WNET=1 [OK] AT+WJOIN Joining : wiznet Successfully joined : wiznet [Link-Up Event]  IP Addr    : 10.0.1.5  Gateway    : 10.0.1.1 [OK]

AT+WLEAVE AT+WSET=0,wiznet,, AT+WSEC=0,WPA2,vickitjohn AT+WNET=1 AT+WJOIN AT+SCON=O,TCN, 213.186.33.19,80,,0 AT+SSEND=0,,,132

HTTP Request format for PushingBox When Temperature is 32C and humidity is 71%

The local data save to Twitter through PushingBox AT+SCON=O,TCN, 213.186.33.19,80,,0 [OK] [CONNECT 0] AT+SSEND=0,,,128 [0,,,132] Send “get.txt” to pushing box through WizFi250

Receive from the PushingBox API server

Pushing Box has provided some other API sources code. Please refer the link: https://www.pushingbox.com/api.php

The library for the connection between WizFi250 and Arduino Uno that the source File shows in Github Please refer the link: https://github.com/Wiznet/Arduino_WizFi250/tree/master/Software/WizFi250

Result in Twitter

[wiznethk]

Develop a IOT solution by using W5500 part 2

It has been a week that I didn’t update about IOT application on W5500. Let’s have a look for this weeks article on the second step of IOT application on W5500. 

For this week, we will talk about the google spreadsheet script with W5500 solution.

In the previous article, it shows the following information. 

1. Gather Temperature information & Humidity values from a DHT11 sensors to W5500-EVB

2. Communicate with a cloud server call pushing box for delivery information to a destination location. 

3. Using W5500-EVB as the gateway & pushingbox cloud server to deliver all the sensor information to twitter.

If you have any problems on how to communicate a cloud server with W5500 solution or getting a detail information about this IOT application. Please refer the previous article “Develop a IOT solution by using W5500 part 1″ for more information.

For this article, I’m going to towards one more step to manage these data into google spreadsheet for recording purpose. 

For this part, it includes the following parts need to do. 

1. Create a google spreadsheet 

2. Create a google script by java codes to dump the data into google spreadsheet

3. Set the correct format on pushingbox to delivery the message through google script link.

Create a google spreadsheet:

I think this is the most simple part for this article. As normally, most of the people will have google account or gmail account for searching information or checking emails. 

Anyways, I will still briefly shows the method on creating a google spreadsheet. 

After you had a google or gmail account, it normally includes a google drive storage system for you to save information. 

Please go to google drive page and press “New”, it should directly open a choice for google spread sheet. Please press it and it will open a blank spread sheet. The following figure shows the steps for opening a spread sheet through google drive.

After you created a spreadsheet, please modified as you want. However, the first 3 columns will use for saving the results that collected from the sensors. 

a) Received time     b) Temperature     c) Humidity 

Therefore please keep the first 3 columns for the usage on these information inputs. 

In the figure, it shows the location of ID number, this is for the usage of the script to communication with the spreadsheet. 

Before you start writing your script, please remember to unlock the editing and viewing rights to public. Therefore you could allow the script to modify the spreadsheet. 

Google Script:

For this section, I found a very useful link that I wanted to introduce to you. This developer has develop a google script that is specific for IOT application base on W5100 Ethernet shield. The developer has created a Youtube video and provided his google script to everyone to easily get used on this code. 

For more information, you may visit the following link: 

http://jarkomdityaz.appspot.com/

Scrolling down to the bottom will have all the information that you need.

By having this script, it reduce a lot of workload on developing my version of script with our W5500. Thus, I had made the following modification on the script. 

1. Adding the ID of the spreadsheet from the source code. 

2. Add an extra column for humility value

The following figure shows the modification part of the codes.

Please remember to modify all your settings before you activate these codes into Web app. 

After you had saved all these data, you are required to do the following steps to make sure this script is working normal in web app. 

1. Upload for personal use - Testing the application is it working normally. It requires access to google drive confirmation window. Please press allow to proceed  

After you pressed deploy or update, it will show the following link for you to use. 

2. Copied the link to test the script. It will show  “ok” for result.

3. Change the settings to allow other people to modified 

4. Change the values with the new link and add values into end of the link. 

&tempData=1&column_C=2

The above are the parameters input to the second and third row. (The first row is for received time)

Then, you will see the following result. 

Pushingbox delivery:

Right now, we could go back to pushingbox to put the sensor information to the spreadsheet. 

If you have any problem on this section, please refer my previous article - Develop a IOT solution by using W5500 part 1.

The following are the steps to set an whole scenario. 

1. Create a custom URL link for the location platform

2. Input the link and create a name for this service

3. Set to get format and create this service

4. Create an scenario 

5. Add an action for this scenario and put the custom URL service into this scenario

6. Add the message as below. 

Message : ?tempData=$temp$&column_C=$humid$

As you create the a new scenario, the device ID will be different. Thus, you are required to change the device ID as follow to communicate with the spreadsheet.

After you run the source code, you should see the following information from your spreadsheet.

Reference: http://jarkomdityaz.appspot.com/ 

[wiznethk]

Develop IOT solution by using Pushing box and WizFi250 in Twitter

This time, let’s try to develop a IOT solution based on the following section

1. Communication method between WizFi250 and Pushing box

2. Adding sensors into the device to transmit data to Cloud Server

(by Easy Module Shield and Arduino Uno)

3. WizFi250 send the message to Twitter through Pushing box

PushingBox Cloud Server

This Pushing Cloud server is very simple to register and operate.

Link: https://www.pushingbox.com/

Registration: Using google account to login.

Firstly, you can create a Pushingbox Account

If you have Google account, please press login with Google on the top right hand corner.

Go to “My Services” and “Add a service”  Adding devices means it will add the location platform for pushing those data.

You could choose Twitter, email or even push to a specific link for your own use.

This time we select Twitter and add this service.

Enter to My Scenarios, you can find your “Scenario name” & “Device ID”. After that you press the “Manage” button to enter my service.

You can find that Twitter service is added. And it connects to your Twitter account.

Obtain the Xively API sever IP

PushingBox API Server :  213.186.33.19

PushingBox API Port:        80

 Association to AP in WIZfi250

AT+WLEAVE

[OK]

AT+WSET=0,wiznet,,

[OK]

AT+WSEC=0,WPA2,vickitjohn

[OK]

AT+WNET=1

[OK]

AT+WJOIN

Joining : wiznet

Successfully joined : wiznet

[Link-Up Event]

 IP Addr    : 10.0.1.5

Gateway    : 10.0.1.1

[OK]

 HTTP Request format for PushingBox

When Temperature is 30C and humidity is 70%

The local data save to Twitter through PushingBox

AT+SCON=O,TCN, 213.186.33.19,80,,0

[OK]

[CONNECT 0]

AT+SSEND=0,,,132

[0,,,132]

Send “get.txt” to pushing box through WizFi250

 Receive from the PushingBox API server

Pushing Box has provided some other API sources code. 

Please refer the link: 

https://www.pushingbox.com/api.php

In Arduino Uno Source Code, you must set the  

Device ID: v7A7E2DA2DE9D52F

Dest IP: 213.186.33.19

Server: api.pushingbox.com

And set the correct HTTP request format for PushingBox.

The library for the connection between WizFi250 and Arduino Uno that the source File shows in Github Please refer the link: 

https://github.com/Wiznet/Arduino_WizFi250/tree/master/Software/WizFi250

 Source code

For the source code, we will use the HTTP client reference source code for the this testing.

 About connecting with Easy Module Shield and Arduino Uno, you could also read the previous article for more information:

WizFi250+Arduino Uno+YuRobot with Xively

Please refer the link:  http://blog.wiznet.hk/post/142830911156/wizfi250-arduino-uno-yurobot-with-xivelyenglish

Result in Twitter

[wiznethk]

Compact-sized network module WIZ850io

WIZnet release the network module WIZ850io in 2016.

WIZ850io is an compact-sized network module that includes W5500 (TCP/IP & Ethernet MAC & PHY) & MAG-JACK (RJ45 with X’FMR) with other glue logics. As it is hardware compatible with WIZ820io, you can easily replace the WIZ820io with WIZ850io just by updating the firmware.

WIZnet 公司在2016年發布了新一代網絡模塊 WIZ850io。

WIZ850io 是一個小巧簡潔的網絡模塊，其包括 W5500（TCP / IP，以太網 MAC 和PHY）和 MAG-JACK（RJ45 帶 X'FMR）。由於它是與 WIZ820io 硬件兼容，只需通過更新固件，你便可以輕鬆地把 WIZ820io 更新替換為 WIZ850io。

Key Features

Plugin Network Module.

Hardware compatible with WIZ820io.

Usable without H/W design for W5500, Transformer & RJ45.

Fast evaluation for W5500 & MCU in the target board.

Support high speed SPI interface.

Support power down mode and Wake-on-LAN function

Very small form factor : 23mm x 25mm x 18mm

1 x 6, 2.54mm Pin Header x 2

Pin Assignment

[wiznethk]

Private IP & Public IP network Mult-Wiz107SR

This selection will show you how to use Mult-WIZ107SR connect to internet by using Port forwarding function and show you the different between Public IP and Private IP saturation.

Direct Search, With AP (Search 107 using AP’s Port forwarding)

Port Forwarding Setting

->PC 2 enter the AP webpage(192.168.1.254) to set the port forwarding, then it set the service port and IP address in the AP webpage. In Wiznet Internal Port are 50001. Please note that the AP has port forwarding or DMZ function.

For example, Wiz107SR (Module A) IP address is 192.168.1.101. The service port is 50001-50001 and internal port is 50001. Wiz107SR (Module B) IP address is 192.168.1.102. The service port is 50002-50002 and internal port is 50001.

 Open the ConfigTool WIZ107&108SR 

Wiz107SR (Module A)

Use the TCP unicast direct Search, and then enter AP IP address (10.0.1.60) and service port 50001 to search the Wiz107SR (Module A). At a result, IP address is 192.168.1.101 to display in configuration tool.

Wiz107SR (Module B)

Use the TCP unicast direct Search, and then enter AP IP address (10.0.1.60) and service port 50001 to search the Wiz107SR (Module A). At a result, IP address is 192.168.1.102 to display in configuration tool.

 Direct Search, With AP (Public IP and Private IP is the same saturation )

Since Internet is equal to L2 S/W HUB. The Private IP 10.0.1.2 and 10.0.1.33 can change to Public IP 222.98.xxx.xxx and 203.230.xxx.xxx. Please check your public IP of your AP and PC.

[wiznethk]

Develop a IOT solution by using W5500 part 1

In the previous articles that I had made, it allows us to have the standard understanding on communicate with two types of Cloud server through W5500-EVB. 

This time,  let’s try to  develop a whole IOT solution base on the following section

1. Communication method between WIZnet’s solution and Cloud Server

2. Adding sensors into the device to transmit data to Cloud Server

3. Using Android application to view the data that received from Cloud Server

This is the basic procedure on creating an IOT application. 

In this series of articles, I wanted to add something extra features for this application. 

a) Adding spread sheet script to save all records collected from the sensor.

b) The android application will show the Sensor’s record.

From having the experience on developing source code for communicate with Cloud Servers, I think this is the best time for us to head into creating the whole IOT concept design. 

For the first article, I will show you the basic on communicating with W5500-EVB to another Cloud Server called Pushing box . 

After that, It will connected with DHT11 sensor to publish these data on Twitter. 

The following figure shows the section in this article.  

For this section of development, we required the following items.

1. W5500- EVB (If you don’t know anything about this Evaluation board, you may read my previous article on How to communicate with MQTT server through W5500)

2.  Ywrobot’s Easy Module Shield’s DHT11 Sensor that records Temperature and Humidity.

3. Cloud Server - This time, I will use Pushing box cloud server. This server is simple to use and it has a function that pushing the received information to the location that you wanted to post.  In example, Twitter.

For this Cloud server, it could only send out only 1000 messages per day.  

PushingBox Cloud Server

This Pushing Cloud server is very simple to register and operate. 

Link: https://www.pushingbox.com/

Registration: Using google account to login. 

As the name of this cloud server is called PushingBox, this cloud will directly push out (Send out) the data received data from the W5500-EVB to the location that you set. 

First, we need to know the location platform to push. This require us to set from “My services” setting. 

About adding devices, it means it will add the location platform for pushing those data. You could choose Twitter, email or even push to a specific link for your own use. 

For this cloud server, you are capable to modified the delivery message to the system. By setting “My Scenarios”, you could changed it in any kind of format.

As there is a default scenario in this server, we will just change this for our testing with Sensor’s result. 

After we pressed the manage button at the right corner, it will show the following information.

As the above figure shows, there are few things that you could be modified.

1. Add an extra platform to received your message. (Please remember to add the platform on My Services)

2. Editing your message

3. It could accept changing variables in certain of format. ($xxx$) 

Now, we could move to the next stage for modifying the source code for W5500-EVB.

Source code

For the source code, we will use the HTTP client reference source code for the this testing. 

The connection method to this cloud server, the IP address could find from the Help section of this website. 

 If you have any difficulties on connecting with the Cloud Server, you may read the previous blog article - How to communicate with Xively server based on W5500 chip.

The next step is changing the HTTP request method for this server. 

For the HTTP request method for PushingBox Cloud server, it is very simple. You are required to send the format as follow will be fine to communicate with the server. 

As the above figure shows, the HTTP request method does not required any key’s or password to login into the Server. 

The only requirement is the Device ID that needs to add before the Changing variables inputs.

The Changing variables name are required to define from the PushingBox "My scenarios” Section and used equal sign for adding the value for that specific variables. 

Pushing Box has provided some other API sources code. 

Please refer the link: https://www.pushingbox.com/api.php

For the method on changing the variables, you could set your code by changing the related variables from the array. The result value from the DHT11 sensor will replace those value as follow. 

About connecting with Easy Module Shield, you could also read the previous article for more information -  How to communicate with Xively server based on W5500 chip.

Finally, you will have the following result on twitter. 

[wiznethk]

How to communicate with MQTT server through W5500

MQTT - Message Queuing Telemetry Transport. This is a light weight,simple message protocol that above TCP/IP protocol. This kind of protocol is good for using IOT related application development. By handling simple structure data, it allows user to monitor their devices easily. 

This article will show you how to use a hardwired TCP/IP solution chip W5500 to communicate with MQTT broker. For giving a better understanding on this article, it presents as a tutorial to allow user to use this solution in a easy way.

Required equipment:

1. W5500 Evaluation Board (EVB)

2. MQTT broker - The server that accept MQTT protocol and delivery messages to other MQTT clients

3. MQTT library from Paho

First of all, we need to have a device and platform for implementing MQTT to operate with W5500 chip. For the device, I had chosen W5500 EVB as the main platform. This board included STM32F103RCT6 that has the ability to handle this simple implementation.   

MQTT: 

MQTT is a application protocol that is above TCP/IP protocol. This kind of protocol is light weight binary protocol. This kind of protocol structure is a lot simple than using HTTP request format.

For MQTT protocol, it is required to have a Server to understand this protocol and deliver these message for monitoring purpose to the users. 

MQTT protocol has used Publish and Subscribe method to delivery message. This means each devices are required to communicate with a MQTT server called MQTT broker. This broker is a agent for managing these information to allow more than 2 devices to exchange information. 

The following figure shows the simple block diagram that explains the communication method in MQTT. 

Thus, the MQTT broker that I’m going to use is trying to develop with CloudMQTT. This broker is easy to register and use, you just need to go to control pannel to register a account will be fine. Please refer the following figure and link to register your account. 

Link: https://www.cloudmqtt.com/

After you had register your account and create your broker, you could start to use this MQTT broker by using publish and subscribe method to manage your devices. 

Before we head into coding, we need to gather some information from this broker. 

Adding MQTT into your source code

As this protocol is a application layer protocol, therefore we could just add this library on your source code without any effect to your setting on TCP/IP protocol layer. 

For my case, I had used Hardwired TCP/IP protocol chip reduces workload on developing TCP/IP protocol. Thus, I just need to add the library directly to my TCP client source code with some extra setting will be fine. 

For the MQTT library, I had used Paho’s C library for this development. 

Please refer the following link for getting the library.

Paho website: https://eclipse.org/paho/

Paho c library: http://git.eclipse.org/c/paho/org.eclipse.paho.mqtt.embedded-c.git/snapshot/org.eclipse.paho.mqtt.embedded-c-1.0.0.zip

The file that you required for this protocol is 

A. Folder: c:\your downdload path\org.eclipse.paho.mqtt.embedded-c-1.0.0\MQTTPacket\src

B. Files: c:\your downdload path\org.eclipse.paho.mqtt.embedded-c-1.0.0\MQTTClient-C\src MQTTClient.c & .h files.

After we had implemented library into the source code, we need to add a interface to allow both our codes could combine together. 

For more information you may download my source code. 

https://drive.google.com/file/d/0B0GWlyVLRcvNYVVhZXhXVXB2NDA/view?usp=sharing

The file that I had add are the MQTT_interface.c & MQTT_interface.h as the follow figure.

If you wanted to make your own library or using another solution that you directly send MQTT data to the broker, I suggest that you to refer the following link. 

http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html

Testing MQTT server: 

Before we use the broker’s information for testing MQTT, we need to have identify and create two devices for Publisher and Subscriber with MQTT broker. 

In this test, I used a MQTT testing program (MQTT Fx) as the Publisher.

MQTT fx : http://mqttfx.jfx4ee.org/

The W5500 EVB will be the subscriber that received information from the Publisher.  

Please add the IP address, port number, user name, password for connect to MQTT. 

Finally, create the same topic for subscriber and publisher for communication purpose. 

It will the result as follow.

[wiznethk]

How to communicate with MQTT on WizFi250

Block Diagram:

This post will fully introduce how to use at command of Wiznet module(WizFi250) to communicate with MQTT Server.  After read the article, you can get more understanding on the relationship between Publisher and Subscriber on MQTT with WizFi250. 

Block Diagram2:

Step 1: Create your own Cloud Server. For example: https://www.cloudmqtt.com/

After you created your cloud server, you will get your server detail.

Step 2: Create the TCP connection between the client and broker

AT Command for making the Client as Station mode and TCP client: 

at+wset=0,SSID

at+wsec=0,,PASSWORD

at+wnet=1

at+wjoin

---------Join AP------------

at+scon=SO,TCN, broker IP,port,,1

-----------Connect to Broker-------------

Right now, client is connecting to broker with TCP connection.

Server: m10.cloudmqtt.com Server IP: 54.92.237.174 Port: 10250

Step 3: Create the MQTT “Connect” between the client and broker

AT+SCON=SO,TCN,54.92.237.174,10250,,1

104400044d51545404c6003c|0017|Handkie8911111111111111|0003|ABC|0002|hi|0008|ynxbaern|000c|cctdGq-Go7Ce

Fixed Header:          0x10,0x34

Variable Header:    0x00, 0x04, 0x4d, 0x51, 0x54, 0x54, 0x04, 0xc6,

0x00, 0x3c

Payload:

Client ID:                   0x00, 0x07, 0x48, 0x61, 0x6e, 0x64, 0x6b, 0x69,

0x65 (Handkie)

Will Topic:                 0x00, 0x03 0x41, 0x42, 0x43 (abc)

Will Message:          0x00, 0x03, 0x65, 0x6e, 0x65 (end)

Username:                0x00, 0x08, 0x79, 0x6e, 0x78, 0x62, 0x61, 0x65,

0x72, 0x6e (ynxbaern)

Password:                 0x00, 0x0c, 0x63, 0x63, 0x74, 0x64, 0x47, 0x71,

0x2d, 0x47, 0x6f, 0x37, 0x43, 0x 65(cctdGq-Go7Ce)

PS: For each items of payload need to add 1 byte of MSB and LSB

CONNECT coding (in HEX):

103500044d51545404c6003c000748616e646b696500036162630003656e640008796e78626165726e000c6363746447712d476f374365

 Respond in Serial Terminal:

5MQTT?<HandkieabcenynxbaerncctdGq-Go7Ce  

Step 4: Subscribe the Topic (refer to Block Diagram2)

Topic1:    0x57, 0x69, 0x7a, 0x46, 0x69, 0x32, 0x35, 0x30(WizFi250)

Topic2:     0x57, 0x69, 0x7a, 0x46, 0x69, 0x32, 0x37, 0x30(WizFi270)

 SUBSCRIBE coding (in HEX):

820D0004000857697a466932353000

820D0004000857697a466932373000

 Respond in Serial Terminal:

5MQTT?<HandkieabcenynxbaerncctdGq-Go7Ce ?WizFi250??WizFi270?

Step 5: Publish the message to Topic

Topic1:        0x57, 0x69, 0x7a, 0x46, 0x69, 0x32, 0x35, 0x30(WizFi250)

Message1:   0x68, 0x61, 0x6c,0x6c, 0x6f(hallo)

Topic2:        0x57, 0x69, 0x7a, 0x46, 0x69, 0x32, 0x37, 0x30(WizFi270)

Message2:   0x68, 0x69 (hi)

 PUBLISH coding (in HEX):

300F000857697a466932353068616c6c6f

300C000857697a46693237306869

 Respond in Serial Terminal:

5MQTT?<HandkieabcenynxbaerncctdGq-Go7Ce ?WizFi250??WizFi270?WizFi250halloWizFi250halloWizFi270hiWizFi270hi

The Received messages in Websocket UI:

Publish message in Serial Terminal

300F000857697a466932353068616c6c6f

300C000857697a46693237306869

 Timeout and Disconnect If there is no message send out or receive, it will timeout and disconnect.

Will Topic:                 0x00, 0x03 0x41, 0x42, 0x43 (abc)

Will Message:          0x00, 0x03, 0x65, 0x6e, 0x65 (end)

Keep Alive Timer MSB:     0x00

Keep Alive Timer LSB:              0x3c

[wiznethk]

如何用W5500芯片和Xively溝通

現今世代, 人們開始將生活事務推向網絡化. 因為這種想法, 現時開始產生了一種科技上的新思維叫做IOT. IOT的意思是把所有普通實品網上化,因此可以方便人們去管理. 感應品因通過以太網的TCP/IP協議和不同的雲端交換資訊成為此應用上一個相當重要的部分.

在文章中, 我會用W5500一個硬件TCP/IP協議棧跟一個雲端(Xively)溝通. 因為想把這個文章更有意思, 我會加上一個YwRobot Easy module shield. 這個模塊內有溫度和濕度感應器, 因此把此數據通過W5500的TCP/IP協議放上雲端展現出來.

所需的設備：

1. W5500-EVB - W5500芯片 評估板

2. YwRobot Easy Module Shield - 包括一個DHT11溫度和濕度傳感器。

3. Xively個人賬戶

首先，我們需要一個 使我們能夠從傳感器接收數據的電路板，並通過W5500芯片提供這種信息給服務器。在這種情況下，我用了W5500-EVB做這個測試。它有STM32F103RCT6 MCU，並擁有董事會外部引腳，可以方便地與易模塊屏蔽線連接。 下圖是本文的W5500評估板

連接到服務器Xively： 我們開始談論該計劃為這個應用程序之前，我們需要創建一個 Xively 個人賬戶。 為了創建自己的帳戶，請訪問以下鏈接：

https://personal.xively.com/signup/

你已經創建的帳戶後，請按照下列步驟來創建你自己的服務器，可以與您的設備進行通信

步驟1:按"跳到添加設備"部分

步驟2:按"添加設備"創建自己的設備

步驟3:請設置為公共設備，讓您的設備可以訪問。

創建設備後，它允許你創建渠道接收數據，請創建2個通道用於接收濕度 和溫度值。 前往我們的程序之前 ，我們需要收集一些信息。 1.設備ID號 2. API密鑰 3.2通道的ID名稱 - 在本應用筆記中，我將使用W5500_test_1和W5500_test_2接收這些值 4.服務器的域名和IP地址 下圖顯示了，你可以從你的設備的Xively頁面找到所需的信息。

源代碼：

通過使用這些信息，我們可以把它提供給W5500-EVB的HTTP客戶端參考源代碼。請查找以下鏈接下載修改後的源代碼。

https://drive.google.com/file/d/0B0GWlyVLRcvNRTl0ZUNZQzFSV28/view?usp=sharing/

Xively服務器使用HTTP請求的格式與服務器進行通信。有跡象表明，可以教你詳細了解如何通過使用HTTP請求格式與服務器通信API文檔。

https://personal.xively.com/dev/docs/api/

源代碼已被修改以Xively服務器格式進行通信。然而，此源代碼不包括DNS的功能。因此，請使用命令來ping Xively的API服務器並檢查IP地址。

下圖顯示了修改Xively服務器的IP地址在main.c文件的位置。

下述圖顯示了使用HTTP PUT請求來同時更新2個通道的HTTP請求方法。

有關本例中的HTTP請求方法的詳細信息，請參考以下鏈接：

https://personal.xively.com/dev/docs/api/data/write/single_datapoint_to_each_datastream/

連接 YwRobot Easy Module Shield 和與Xively服務器進行通信： 對於這種應用，我用了YwRobot容易模塊盾的傳感器DHT11本文收集的溫度和濕度。

通過連接VCC和GND到屏蔽它提供電源到屏蔽正常激活。在那之後，我們需要W5500-EVB的PA12引腳顯示以下數字引腳連接。

下圖顯示了需要與W5500-EVB連接引腳

將要連接到Easy Module Shield 上W5500-EVB 引腳 。

這兩個引腳連接後，您可以使用W5500 EVB 上GPIO引腳上收集從DHT11傳感器上的讀數 。

以下源代碼是連接並收集來自DHT11傳感器的讀數。

該已對下述代碼值是 通道的更新值。保存這組字符串為字符上傳到雲端前，您應把這些值修改 。

下圖顯示了這個W5500-EVB的TCP/ IP通信方法的基礎。

你對修改傳感器的值之後，你可以用上面的方法使用TCP/ IP連接到Xively服務器發送更新的值。

結果：

從Xively服務器結果：

串行消息結果：

HTTP/1.1 200 OK

Date: Thu, 07 Apr 2016 03:44:01 GMT

Content-Type: application/json; charset=utf-8

Content-Length: 0

Connection: keep-alive

X-Request-Id: ebd5af90501c53b20961de636cdc0a4a68e8460f

Cache-Control: max-age=0

Vary: Accept-Encoding