I am trying to connect the core to my wifi, via tinker.
The core gets the command from tinker and switches from blinking blue to fast blinking green but stays that way forever…
The SSID and password are correct and the wifi is WPA2, all standard, not behind firewalls or anything of the sort.
I was connected to the cloud via this wifi network in the past, now I can’t.
what should I do?
Hi,
I had this a couple of times with my huawei 4g router, resetting the router helped.
Another possible problem can be the distance between the core and the router. I know it sounds a bit as a put off, but I relocated the router closer to the core and that helped, 10 meters instead of 20…
Further more I tend to see a trend. When you reconnect very often, the connection time seems to increase, and decrease randomly. Resetting the router helps.
Maybe the channel of your router conflicts suddenly with another router nearby. I use an app on my phone to check for conflicting channel assignments.
I also think that the size of the core, and especially it´s antenna, decreases it´s range a bit, especially when you compare this with a laptop that has a full size 1/4 wave length antenna build in the screen.
These problems are not unique to the core, the wifly module also has these problems.
I hope these tips help!
thanks for your reply and help.
I tried resetting the router, which is set to auto channel (non-conflict) but it didn’t help.
the core is about 1.5m from the router… (it’s a netgear)
Hey there,
Are you still having the problem?
If you have spark-cli, place the core in DFU mode (blinking yellow) and run this command spark flash --usb cc3000
OK, a factory reset solved the issue…
do you think I should still do the DFU?
If it connects OK then you can give it a miss 
To all those who are communicating to the core with the help of minicom (fedora18), always ensure that every time you reset the spark core before you give away the WIFI Credentials, otherwise your core won’t respond and your serial device will always exit from the loop even if you configure the port.
Jul 22 11:48:51 anirudh kernel: [ 2954.790042] usb 5-1: new full-speed USB device number 3 using uhci_hcd
Jul 21 11:48:51 anirudh kernel: [ 2954.953054] usb 5-1: New USB device found, idVendor=1d50, idProduct=607d
Jul 21 11:48:51 anirudh kernel: [ 2954.953060] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 21 11:48:51 anirudh kernel: [ 2954.953065] usb 5-1: Product: Spark Core with WiFi
Jul 21 11:48:51 anirudh kernel: [ 2954.953068] usb 5-1: Manufacturer: Spark Devices
Jul 21 11:48:51 anirudh kernel: [ 2954.953071] usb 5-1: SerialNumber: 8D8731855153
Jul 21 11:48:51 anirudh kernel: [ 2954.956147] cdc_acm 5-1:1.0: This device cannot do calls on its own. It is not a modem.
Jul 21 11:48:51 anirudh kernel: [ 2954.956177] cdc_acm 5-1:1.0: ttyACM0: USB ACM device
Jul 21 11:48:51 anirudh mtp-probe: checking bus 5, device 3: "/sys/devices/pci0000:00/0000:00:1d.3/usb5/5-1"
Jul 21 11:48:51 anirudh mtp-probe: bus: 5, device: 3 was not an MTP device
Jul 21 11:48:51 anirudh dbus-daemon[453]: modem-manager[629]: (ttyACM0) opening serial port…
Jul 21 11:48:51 anirudh modem-manager[629]: (ttyACM0) opening serial port…
Jul 21 11:49:03 anirudh dbus-daemon[453]: modem-manager[629]: (ttyACM0) closing serial port…
Jul 21 11:49:03 anirudh modem-manager[629]: (ttyACM0) closing serial port…
Jul 21 11:49:03 anirudh dbus-daemon[453]: modem-manager[629]: (ttyACM0) serial port closed
Jul 21 11:49:03 anirudh modem-manager[629]: (ttyACM0) serial port closed
Jul 21 11:49:03 anirudh dbus-daemon[453]: modem-manager[629]: (ttyACM0) opening serial port…
Jul 21 11:49:03 anirudh modem-manager[629]: (ttyACM0) opening serial port…
Jul 21 11:49:09 anirudh dbus-daemon[453]: modem-manager[629]: (ttyACM0) closing serial port…
Jul 21 11:49:09 anirudh modem-manager[629]: (ttyACM0) closing serial port…
Jul 21 11:49:09 anirudh dbus-daemon[453]: modem-manager[629]: (ttyACM0) serial port closed
Jul 21 11:49:09 anirudh dbus-daemon[453]: modem-manager[629]: (ttyACM0) opening serial port…
Jul 21 11:49:09 anirudh modem-manager[629]: (ttyACM0) serial port closed
Jul 21 11:49:09 anirudh modem-manager[629]: (ttyACM0) opening serial port…
Jul 21 11:49:21 anirudh dbus-daemon[453]: modem-manager[629]: (ttyACM0) closing serial port…
Jul 21 11:49:21 anirudh modem-manager[629]: (ttyACM0) closing serial port…
Jul 21 11:49:21 anirudh dbus-daemon[453]: modem-manager[629]: (ttyACM0) serial port closed
Jul 21 11:49:21 anirudh dbus-daemon[453]: modem-manager[629]: (ttyACM0) opening serial port…
Jul 21 11:49:21 anirudh modem-manager[629]: (ttyACM0) serial port closed
Jul 21 11:49:21 anirudh modem-manager[629]: (ttyACM0) opening serial port…
Jul 21 11:49:27 anirudh dbus-daemon[453]: modem-manager[629]: (ttyACM0) closing serial port…
Jul 21 11:49:27 anirudh modem-manager[629]: (ttyACM0) closing serial port…
Jul 21 11:49:27 anirudh dbus-daemon[453]: modem-manager[629]: (ttyACM0) serial port closed
Jul 21 11:49:27 anirudh modem-manager[629]: (ttyACM0) serial port closed
Jul 21 11:53:52 anirudh dbus-daemon[453]: dbus[453]: [system] Activating service name=‘net.reactivated.Fprint’ (using servicehelper)
Jul 21 11:53:52 anirudh dbus[453]: [system] Activating service name=‘net.reactivated.Fprint’ (using servicehelper)
Jul 21 11:53:52 anirudh dbus-daemon[453]: dbus[453]: [system] Successfully activated service 'net.reactivated.Fprint’
Jul 21 11:53:52 anirudh dbus[453]: [system] Successfully activated service 'net.reactivated.Fprint’
Jul 21 11:53:52 anirudh dbus-daemon[453]: Launching FprintObject
Jul 21 11:53:52 anirudh dbus-daemon[453]: ** Message: D-Bus service launched with name: net.reactivated.Fprint
Jul 21 11:53:52 anirudh dbus-daemon[453]: ** Message: entering main loop
Jul 21 11:54:23 anirudh dbus-daemon[453]: ** Message: No devices in use, exit
Jul 21 11:57:34 anirudh dbus-daemon[453]: dbus[453]: [system] Activating service name=‘net.reactivated.Fprint’ (using servicehelper)
Jul 21 11:57:34 anirudh dbus[453]: [system] Activating service name=‘net.reactivated.Fprint’ (using servicehelper)
Jul 21 11:57:34 anirudh dbus-daemon[453]: dbus[453]: [system] Successfully activated service 'net.reactivated.Fprint’
Jul 21 11:57:34 anirudh dbus[453]: [system] Successfully activated service 'net.reactivated.Fprint’
Jul 21 11:57:34 anirudh dbus-daemon[453]: Launching FprintObject
Jul 21 11:57:34 anirudh dbus-daemon[453]: ** Message: D-Bus service launched with name: net.reactivated.Fprint
Jul 21 11:57:34 anirudh dbus-daemon[453]: ** Message: entering main loop
Jul 21 11:58:04 anirudh dbus-daemon[453]: ** Message: No devices in use, exit
Jul 21 11:58:12 anirudh kernel: [ 3516.000064] usb 5-1: USB disconnect, device number 3