Wi-Fi Combo Forum Discussions

TCP Client

This example uses one ACKme eval board and the ACKme 'WiConnect' serial API.

WiConnect sits on top of WICED and in this example demonstrates how to use the WiConnect TCP client command to download a webpage.

The first step is to establish a TCP connection to the webserver on port 80 using the tcp_client command. Then, the stream_write command is used to send an HTTP GET request. Finally, the stream_poll and stream_read commands are used to check for a response from the server, and to read the webpage.

While this is a perfectly good example of how to use the WiConnect TCP client, if you plan to use HTTP to transfer data around, why not use the in-built HTTP library? The HTTP libary provides ready-made HTTP functions including http_get and http_post.

The full article with commands can be found here: ACKme | How does WiConnect offer TCP client capability?

ACKme NetworksPartnersWICED Wi-Fi

Wireless Serial Port

This application uses two ACKme modules each running WiConnect, a serial API that sits on top of WICED, to demonstrate how to create a wireless serial port. A character typed into the serial port of Module 1 appears instantly at the output of the Module 2 serial port (and vice versa).

Features demonstrated

• Serial Interface Stream Mode
• Use of the WLAN and softAP wireless interfaces
• TCP client and TCP server

Module 1 is a server configured to start the softAP interface and the TCP server feature on boot up. Module 2 is a client configured to use the wlan interface and the TCP client feature to connect to the Module 1 softap and TCP server. The final configuration step places both modules into serial interface Stream Mode. Enough chit-chat, let's get started by configuring each of the modules.

The full article with commands can be found here: ACKme | How can I create a wireless serial port

ACKme NetworksPartnersWICED Wi-Fi

For users that are using ACKme's WiConnect which is a simple API that sits at the front of WICED there are a number of RSS feeds that can help.

• FAQs:                              http://ack.me/FAQs.rss
• Documentation Updates:    http://ack.me/resources/home.rss

of course if you haven't configured your mail application (such as Outlook) to import the feeds then you will need to set that up, there are instructions on how to do that here: http://ack.me/RSS_Feed

If you dont use an RSS aggregator then you can also just visit the webpages themselves but this is alot more manual

• FAQs:                             http://ack.me/FAQs
• Documents                      http://ack.me/resources/show

I hope that helps!

Hello,

I'm using your wifi wiced board with the BCM943362WCDA module.

I succesfully compiled and programmed the latest "demo.temp_control" firmware. After downloaded it in the module, everything works fine and  in fact I'm able to access the webpage with the temperature information  and also I'm able to get the data temperture in the xively website.

After the first power up I never turned off the board (that is supplied by an USB wall adapter)  and what I noticed is that, after some time (1 or 2 days) the board is not able to communicate anymore (I'm not able to get the data by xively neither to access the board webpage) and I have to reset it (by the reset button) to make it to work againg.

When the board was not able to  communicate anymore I checked the AP status and the board is still in the AP client list.

Have you seen a behaviour like this? Is something related to the firmware stack that will be fixed in the future or it related to other issues?

Thanks,

Rosario

Can I make a system as below? (I'm not an engineer)

Automatic Attendance Check System for School or Factory

- Every Student or labor attach WICED Smart based device on the backside of their smartphone.

- Install WICED Bridge and WLAN AP at each classroom or factory site. Teacher or factory manager has monitoring device.

- Indivisual WICED Smart devices send its ID number when it is connected with WICED Bridge. (WICED Bridge should handle more than hundred WICED Smart devices)

- WICED Bridge gethers ID numbers and sends it to monitoring system via WLAN AP.

- When WICED Smart device disconnected with Bridge, it pairing with smartphone and makes the smartphone send its position address(or with google map capture) with WICED Smart device's ID number to someone(student's parents or teacher) periodically. (for their safety)

* WICED Smart device should be thin, light and has longlife bettery.

Hi,

Net_Dut dhcp client in the SDK3.0.0 or later could not get the IP address from some APs, such as Mercury MW300R.

If i used static IP address for testing when using SDK3.0.0, the ping worked fine.

And i captured the wireless packets with Omnipeek, and found the DUT had connected to the AP, but could not get the IP address.

When i use SDK2.4.0 and tested with same AP with same setting, DHCP client worked fine, it could get the ip address.

--------------------------------------- SDK2.4.0  DHCP client work fine---------------------------------------

SDK2.4.0, run snip.apsta, DHCP client work fine.
Platform BCM943362WCD4 initialised
Started ThreadX v5.5
Initialising NetX v5.6
Creating Packet pools
Starting Wiced v2.4.0
WWD SDIO interface initialised
WLAN MAC Address : 40:2C:F4:AF:30:89
------NetX_Duo wiced_network_up
Joining : test_wiced
Successfully joined : test_wiced
Obtaining IPv4 address via DHCP
Setting IPv6 link-local address---2.4.0
IPv4 network ready IP: 192.168.1.110
Pinging 192.168.1.1 every 1000ms with a 900ms timeout.
------NetX_Duo wiced_network_up
Setting IPv6 link-local address---2.4.0
IPv4 network ready IP: 192.168.0.1
Ping timeout
Ping Reply : 6 ms
Ping Reply : 1 ms
Ping Reply : 0 ms
Ping Reply : 5 ms
Ping Reply : 18 ms
--------------------------------------- WICED v3.0.0 DHCP client issue ---------------------------------------

Starting WICED v3.0.0
Platform BCM943362WCD4 initialised
Started ThreadX v5.6
Initialising NetX v5.7_sp1
Creating Packet pools
WWD SDIO interface initialised
WLAN MAC Address : 40:2C:F4:AF:30:89
WLAN Firmware    : wl0: Feb 10 2014 11:29:55 version 5.90.230.7 FWID 01-555f783e
------NeX_Duo wiced_network_up
Joining : test_wiced
Successfully joined : test_wiced
Obtaining IPv4 address via DHCP
Setting IPv6 link-local address----
nx_ip_status_check failed
Pinging 0.0.0.0 every 1000ms with a 900ms timeout.
------NeX_Duo wiced_network_up
Setting IPv6 link-local address----
IPv4 network ready IP: 192.168.0.1
Ping error
Ping error
Ping error
Ping error

--------------------------------------- WICED v3.0.0 static IP work fine---------------------------------------

Starting WICED v3.0.0
Platform BCM943362WCD4 initialised
Started ThreadX v5.6
Initialising NetX v5.7_sp1
Creating Packet pools
WWD SDIO interface initialised
WLAN MAC Address : 40:2C:F4:AF:30:89
WLAN Firmware    : wl0: Feb 10 2014 11:29:55 version 5.90.230.7 FWID 01-555f783e
------NeX_Duo wiced_network_up
Joining : test_wiced
Successfully joined : test_wiced
Setting IPv6 link-local address----
IPv4 network ready IP: 192.168.1.3
Pinging 192.168.1.1 every 1000ms with a 900ms timeout.
------NeX_Duo wiced_network_up
Setting IPv6 link-local address----
IPv4 network ready IP: 192.168.0.1
Ping Reply : 6 ms
Ping Reply : 0 ms
Ping Reply : 2 ms
Ping Reply : 0 ms

Best regards,

CaiX