EXP430FR5739 Sensor Application

Bert Berg

Prodigy 80 points

I want to make my Experimenter Board EXP430FR5739 work with the CC3000 FRAM Sensor Application.

My computer has WinXP Professional Version 2002 Service Pack 3, the firewall is (for this purpose) disabled.

The router is TP-Link Model TL-WR740N, connected to the PC.

The Experimenter Board has an LSR module model TiWi-SL Ref.2 and is connected to the same PC and accessible via COM4.

I can access the Experimenter Board by a monitor program. With "assoc TP-LINK_######" I get the response

Sensor App Version: v1.0.7
WLAN Enabled
Attempting to connect using SSID: TP-LINK_######
Connected to AP: TP-LINK_######
CC3000 MAC Address: ##:##:##:##:##:##
CC3000 IP Address: 192.168.1.101
Starting Server...
Server Initialized on port 1204
Waiting for Clients

The last two lines are repeated every minute. LEDs 1-4 are on.

When I connect to the router with a browser via http://192.168.1.1/, I see under "DHCP --> DHCP Clients list" the MAC and IP of my PC and the Experimenter Board. The board has IP 192.168.1.101. Under "IP & MAC Binding --> Binding Settings" I see the same devices with the same MAC and IP. Under "IP & MAC Binding --> ARP List" I only the MAC and IP of my PC. Under "Wireless --> Wireless Statistics" I see both devices with their MAC Addresses and the number of received and sent packets.

When I now disconnect COM4 from the monitor program and start the CC3000 FRAM Sensor GUI, I press the "Continue" button at the "Automatic Configuration" message box. The program finds the board under COM4 ("Configuration Successful") and opens the "CC3000SensorAppGUI" window. The application does not communicate with the Experimenter Board ("0 Nodes Connected") and after a time a message box appears "A CC3000 device has not been found on the network" etc.

Again looking to the browser under "Wireless Statistics" I see that there are packets sent and received in regular intervals.

So were could be the problem?

Thanks, Bert

over 13 years ago

0 Yael Oz over 13 years ago

TI__Expert 4355 points

Hi Bert,

Is the IP address your PC received is the same as shown on the GUI (in the CC3000SensorAppGUI window) ?

If you choose 'skip' and choose your wireless interface manually, does the application communicate with the CC3000?

Yael

0 Bert Berg over 13 years ago in reply to Yael Oz

Prodigy 80 points

Hello Yael

The IP shown in the GUI window (near the 'sun') is 192.168.1.100, This is the IP, which the PC gets from the TP-LINK.

When I choose 'skip' I get 4 options, all of them don't work.

Bert

0 Yael Oz over 13 years ago in reply to Bert Berg

TI__Expert 4355 points

Hi Bert,

Are you able to send ping the CC3000 from your PC?

Yael

0 Bert Berg over 13 years ago in reply to Yael Oz

Prodigy 80 points

Yes, I can ping the CC3000 under 192.168.1.101

0 Yael Oz over 13 years ago in reply to Bert Berg

TI__Expert 4355 points

Hi Bert,

Are you able to run the sensor application (CC3000 side) in debug mode (with IAR or CCS) and tell me where you are stuck?

Are you able to attach sniffer log of the scenario?

Yael

0 Bert Berg over 13 years ago in reply to Yael Oz

Prodigy 80 points

Hi Yael

I can run the application with CCS5 in debug mode, but then the monitor program cannot connect. So I make debug outputs with "terminalPrint". I can see that in "waitForConnection" of "server.c" the program expects a "clientDescriptor", which is always <0.

How can I produce a sniffer log?

Thanks, Bert

0 Yael Oz over 13 years ago in reply to Bert Berg

TI__Expert 4355 points

Hi Bert,

That means TCP connection is not established. CC3000 is waiting for the PC to connect (initiate the 4way handshake).

Are you at a congested environment?

Are you able to try the same with a different PC?

Yael

0 Bert Berg over 13 years ago in reply to Yael Oz

Prodigy 80 points

Thank you Yael for your efforts so far

I have to leave for today. I try these steps tomorrow.

Bert

0 Bert Berg over 13 years ago in reply to Yael Oz

Prodigy 80 points

Hallo Yael

I unplugged the WAN connection, so the PC, the TP-LINK and the Experimenter Board are alone.

With a packet scheduler (Wireshark) I can see that always when I start the Sensor GUI there is a ping request/reply dialog between 192.168.1.100 (the PC) and 192.168.1.101 (the Experimenter Board), where the PC starts the request.

For now I cannot try on another PC.

Bert

0 Yael Oz over 13 years ago in reply to Bert Berg

TI__Expert 4355 points

Hi Bert,

Do you see any TCP packet (SYN ) from the PC to the Experimenter Board ?

Yael

0 Bert Berg over 13 years ago in reply to Yael Oz

Prodigy 80 points

No, nothing but pings.

0 Yael Oz over 13 years ago in reply to Bert Berg

TI__Expert 4355 points

Bert,

For some reason your PC doesn't initial the TCP connection.

Maybe this is due to a firewall or something similar.

Please try the same with a different PC when available.

Yael

0 Bert Berg over 13 years ago in reply to Yael Oz

Prodigy 80 points

Hello Yael

I tried today with a different PC (with firewall disabled), the problem was the same.

I try to contact the local TI support, whence we got the board. When the problem is solved I'll tell you. Thank you for your help.

Best wishes,
Bert

0 nikit biraj over 13 years ago in reply to Bert Berg

Intellectual 630 points

Read all your posts.

My suggestion is make your Access Point SSID as only TP-LINK. You can check in code as default SSID written TP-LINK with NO security.

CC3000 will automatically connect to AP and LED 1 to 4 will be on.

Then open sensor gui and chose skip and choose your laptop wireless wifi.

You can see in uart client will be connected and gui runs with a red cap showing client connected.

There is no question of firewall disabled and all.

Wi-Fi

Wi-Fi forum

EXP430FR5739 Sensor Application