Hi there,
we met the issue on 5 different PCs during I show it to customer. The planet is stuck and going forward and backward repeatedly.
BR.Albin
Martin,
I am really sorry for the issues. We are planning a release before the end of this week that will resolve the issue. Can you wait for it?
Regards,Gustavo
---------------------------------------------------------------------------------------------------------Please click the Verify Answer button on this post if it answers your question.---------------------------------------------------------------------------------------------------------
Gustavo,
I think I can wait until end of the week. Looking forward to see it working soon.
Martin
Hello Gustavo,
I've noticed that there is an updated version (swrc234a.zip) of sensor app on TI wiki page. Unfortunately it dind't solved the problem. Now PC application can't see CC3000 node at all. I tried to run it from bin folder (run_gui.bat) and also in Processing by opening .pde file from source folder, but it behaves same. Console from CC3000 node shows server initialized, waiting for clients, I can see PC and CC3000 connected to TP-Link AP (nodes has assigned 192.168.1.100 and 101 IPs).
The version online that was recently posted was 1.0.4 that did not yet resolve the issue. I have attached the Sensor GUI belonging to version1.0.7 which does have the issue resolved. Please run the CC3000SensorAppGUI.pde using the processing GUI. Let me know how it goes.
1682.CC3000SensorAppGUI.zip
I am sorry to say so, but result is same. PC GUI cannot find CC3000 node.
Thank you for sending the screenshot. It included most everything I needed to see. Your problem is not related to the UNICODE issue that 1.0.6 and above resolve.However, what the issue is I cannot yet tell since the CC3000 seems connected successfully.
From the terminal screen I see that some connection occurs but then disconnects. To be able to udnerstand the issue I would appreciate if you did 2 things:
Enable debugging in the GUI software by changing the line:
final int debugLevel = 0;
to
final int debugLevel = 1;
in the pde file in processing.
You can then run the software and you'll get printouts in the processing screen. It goes by fast, but if you could send me some of those lines it would be very helpful.Especially for anything that says "bad packet" or timeout.
I enabled debug info and played with the code a little bit. It seems to me that PC GUI depends on english when it is trying to ping CC3000 device, because I added a line to scan code to drop debug info in case of success and also in case of fail. (I also shortened scan range from 100-103 to reduce failed messages in debug console)
Look what happend. Ping to IP 192.168.1.101 was successful (in translation it says received 1, loss 0) but debug info still said ping failed (because AddressPing() returned with ap.ping() != true).
Guess what, when I correct it by ping wrapper by
// Check to see if successfull if( (inputLine.indexOf("Received = " + attempts) != -1)
|| (inputLine.indexOf("Pýijat‚ = " + attempts) != -1) ) return true;
And voiala. I know it is not the clean solution (only workaroud for my language), but I am sure it is an useful info for you.
x86Sun Microsystems Inc.1.6.0_24C:\Users\honig\AppData\Local\Temp\CC3000SensorAppGUI857513745450693920temp;C:\Users\honig\Downloads\processing-1.5.1\modes\java\libraries\serial\library\RXTXcomm.jar;C:\Users\honig\Downloads\processing-1.5.1\modes\java\libraries\serial\library\serial.jar;lib;C:\Users\honig\Downloads\processing-1.5.1\java\lib\tools.jar;lib\pde.jar;lib\core.jar;lib\jna.jar;lib\ecj.jar;lib\antlr.jar;lib\ant.jar;lib\ant-launcher.jarC:\Users\honig\Downloads\processing-1.5.1\java\lib\ext;C:\Windows\Sun\Java\lib\extC:\Users\honig\Downloads\processing-1.5.1\javathe file or directory you are searching does not exist : falsehostName honig-pcaddr: /192.168.1.100Starting setupHello from a thread! Try to open socketaddr in discover CC3000 192.168.1.100Octet4: 100Pýˇkaz PING na 192.168.1.101 - 32 bajt… dat:OdpovŘÔ od 192.168.1.101: bajty=32 źas=6ms TTL=64Statistika ping pro 192.168.1.101:Pakety: Odeslan‚ = 1, Pýijat‚ = 1, Ztracen‚ = 0 (ztr ta 0%),Pýibli§n doba do pýijetˇ odezvy v milisekund ch: Minimum = 6ms, Maximum = 6ms, Pr…mŘr = 6ms Ping FailedPýˇkaz PING na 192.168.1.102 - 32 bajt… dat:Vyprçel źasově limit § dosti.Statistika ping pro 192.168.1.102:Pakety: Odeslan‚ = 1, Pýijat‚ = 0, Ztracen‚ = 1 (ztr ta 100%),Ping FailedHello from a thread! Try to open socketaddr in discover CC3000 192.168.1.100Octet4: 100Pýˇkaz PING na 192.168.1.101 - 32 bajt… dat:OdpovŘÔ od 192.168.1.101: bajty=32 źas=4ms TTL=64Statistika ping pro 192.168.1.101:Pakety: Odeslan‚ = 1, Pýijat‚ = 1, Ztracen‚ = 0 (ztr ta 0%),Pýibli§n doba do pýijetˇ odezvy v milisekund ch: Minimum = 4ms, Maximum = 4ms, Pr…mŘr = 4ms Ping FailedPýˇkaz PING na 192.168.1.102 - 32 bajt… dat:Setup completeVyprçel źasově limit § dosti.Statistika ping pro 192.168.1.102:Pakety: Odeslan‚ = 1, Pýijat‚ = 0, Ztracen‚ = 1 (ztr ta 100%),Ping FailedHello from a thread! Try to open socketaddr in discover CC3000 192.168.1.100Octet4: 100Pýˇkaz PING na 192.168.1.101 - 32 bajt… dat:OdpovŘÔ od 192.168.1.101: bajty=32 źas=10ms TTL=64Statistika ping pro 192.168.1.101:Pakety: Odeslan‚ = 1, Pýijat‚ = 1, Ztracen‚ = 0 (ztr ta 0%),Pýibli§n doba do pýijetˇ odezvy v milisekund ch: Minimum = 10ms, Maximum = 10ms, Pr…mŘr = 10ms Ping FailedPýˇkaz PING na 192.168.1.102 - 32 bajt… dat:Vyprçel źasově limit § dosti.Statistika ping pro 192.168.1.102:Pakety: Odeslan‚ = 1, Pýijat‚ = 0, Ztracen‚ = 1 (ztr ta 100%),Ping FailedHello from a thread! Try to open socketaddr in discover CC3000 192.168.1.100Octet4: 100Pýˇkaz PING na 192.168.1.101 - 32 bajt… dat:OdpovŘÔ od 192.168.1.101: bajty=32 źas=7ms TTL=64Statistika ping pro 192.168.1.101:Pakety: Odeslan‚ = 1, Pýijat‚ = 1, Ztracen‚ = 0 (ztr ta 0%),Pýibli§n doba do pýijetˇ odezvy v milisekund ch: Minimum = 7ms, Maximum = 7ms, Pr…mŘr = 7ms Ping FailedPýˇkaz PING na 192.168.1.102 - 32 bajt… dat:Vyprçel źasově limit § dosti.Statistika ping pro 192.168.1.102:Pakety: Odeslan‚ = 1, Pýijat‚ = 0, Ztracen‚ = 1 (ztr ta 100%),Ping FailedHello from a thread! Try to open socketaddr in discover CC3000 192.168.1.100Octet4: 100................................................................................................................
I'm happy to hear you've resolved your issue. Because java does not provide native ICMP ping, a wrapper was created. This wrapper was written for english OS. In your machine, ping operates using non english and therefore although ping itself succeeds, it returns failure. We will look into the issue and will release a fix in the future.
Your fix is fine as long as it works for you.
Hi Gustavo,
Where can customer download the updated PC tool kit from the wiki?
we tried the link, but it can't work.
Albin,
The package is being refreshed at the moment and that link should go back up with version v1.0.7 which resolves the issues you saw previously.
If you have the package yourself I suggest that you provide it to the customer until the link is back up.
Gustavo