New Imp - no Wifi - no matter what - SOLVED

edited October 2014 in General
I was so excited to get the imp.

Got it powered up via the Sparkfun breakout board.

Got it to flash orange.

Checked my router, made sure it's only operating in B/G mode, 2.4 ghz, WEP encryption, even named the SSID imp.

Installed Blinkup on my iPhone, entered the SSID, and password.

I've tried everything, when Blinkup flashes, the imp stops, then quickly turns green for 1/2 second then goes to orange
again.

I've even tried the battery, placed the imp right on top of the router.

Unless there's something that I am overlooking, this is a huge disappointment after all the hoopla about this device.

Any suggestions I have not tried in the last 6 hours?.....................
«1

Comments


  • The quick flash of green means the wifi details were successfully sent using blink-up, but now the IMP can't make the wifi connection.

    When I used WEP I had to put the password into blinkup in hex format. Here's a link to convert a key to hex format http://www.dirtymonday.net/key_convert.html

    Easier to just use WPA PSK or WPA2 PSK on your access-point.



  • Thanks rocketfire, unfortunately I tried WPA PSK, WPA-Personal, AES, I tried it without any authentication too.
    I even tried the WPS method.

    The closet I get to green is in the WPS mode, but clicking the router WPS button does nothing.

  • Could always be a faulty imp; after blinkup (and seeing the green flash) the imp should then never be flashing amber, as it has received wifi settings at that point. There's no need to set b/g mode, the imp is b/g/n.

    On WPS: check your router manual. Sometimes the button is disabled (you can re-enable it in a control panel), sometimes you need to press and hold for a couple of seconds and a WPS light will start flashing.

    Sounds like the best idea is to try another imp; PM me with your address.
  • I got a new imp from the electronic store today, the same problems. When I try the WPS method I get confirmation from my router that the device is connected but I don't get a flashing green light on the imp. It flashing amber/red.
  • I made sure my router TCP port 31314 is open, I even assigned an IP address to the MAC address of the imp, (0ca69002b38), I've tried using my wife's and my cellphones as hotspots to use, I've even got a 4G LTE router that I've used, it's definitely something with these imps. The imp is reading Blinkup because it stops flashing when it's receiving the Blinkup, then gives a short green light at the end to confirm it. This is frustrating to say the least.
  • Update: I found that I can ping the imp's ip address and get a reply for about a minute after Blinkup was completed.
  • screenshot of pings, then no reply after. This demonstrates that Blinkup works, my router is obviously set up correctly, why does imp drop the connection??
    Screen Shot 2014-10-11 at 9.19.11 AM.png
    570 x 898 - 95K
  • In such a discussion about failing to get a WiFI connection, somebody usually asks if you are sure that your power supply can provide the peak current that the imp needs to make a WiFi connection (>250 mA). Starting a connection can cause a power droop which then causes the connection to fail, then people find a big capacitor or a better supply fixes the problem. Sorry if this is a red herring, but somebody had to say it.
  • Thanks DrJack, for the help.

    No red herring, all suggestions are thoughtful.

    I have tried two imps, both powered by the USB cable and a battery.

    I used the USB off my iMac.

    On your thoughts, I have now tried the imp being powered by the USB adaptor for my Raspberry Pi.

    Still the same outcome but now I notice something different.

    Before the imp would receive an IP address, I could ping it until the flashing stopped, then about 1 minute after the flashing stops I get Request timeout host is down as per the attached file.

    Far too much work trying to solve this when the customer shouldn't have to figure it out.........


    Screen Shot 2014-10-11 at 5.42.58 PM.png
    534 x 948 - 64K
  • Being available on the network for a minute makes sense if it's associating/DHCP'ing fine but DNS or the connection to the server is failing - it'll be pingable but as it can't reach the server.

    Can you provide any information on the router in use?

    Can you telnet to "imp.electricimp.com" port 31314 from another machine on the network and get connected, or does that time out?

    This is rather an unusual problem; it sounds rather like you are firewalled somehow, but the fact you see it on hotspots too is confusing as *everything* shouldn't be firewalled. Where are you located?
  • I've even tried the battery, placed the imp right on top of the router.

    In my experience, placing the imp too close to the router will cause issues. You may be able to get an initial connection, but would struggle to maintain it.

    Make sure the imp is at least 3+ metres from your router.

    Another suggestion is to set your phone up as a hotspot with the same ssid/pw as your router. Imps generally work really well in this configuration.
  • edited October 2014
    I have a Cisco DPC3825
    Firewall is turned off

    I live in Toronto
    I tried telnet imp.electricimp.com 3134 with no luck

    See attached files.
    Screen Shot 2014-10-14 at 1.26.20 PM.png
    572 x 366 - 33K
  • Houston, we have lift off.

    For some reason, I am now able to telnet to imp.electricimp.com 31314

    I don't why it started working but now the imp takes less than 10 secs to establish a connection.

    Nothing on this side was changed.
  • Telnet success!
    Screen Shot 2014-10-14 at 6.46.35 PM.png
    568 x 370 - 48K
  • Uhh that's very strange. I can assure you we didn't change anything on our side either!

    Generally the imp should be connected in <2s especially if you're in the US. It's typically about 1.1s on our office network or at home for me.
  • Any more info on what can cause this? I've got a network in Cambodia. telnet imp.electricimp 31314 looks fine from my laptop (cmd screen goes blank for a while then reverts to command prompt). But none of my imps can connect to the network. Anyone have tips on further debugging?
  • In my experience, it's because I'm trying to connect to a 5G network. I forget every time. It only works on 2.4G! There should be a larger notice about this please.
  • @jamesb what LED code is the device flashing? (and as @kitty says, check your laptop is on the exact same network/band that the imp is connecting to)
  • And you have to set the BlinkUp app on the PHONE to the SSID/password of the 2.4G network.
  • It would be really helpful if the setup page on the app specified this in bold. :)
  • Unfortunately, iOS doesn't let us know what channel the wifi is on, so we can't tell if the pre-filled (current) network name is one the imp can connect to.

    ...though obviously, if you are blinking up an imp005, then that's fine as it has dual-band wifi :)
  • Thanks for the tip with the band. The internet connection there is very flakey, sometimes it's fine and sometimes it's slow. It took hours to download a new firmware update to the devices. I'm in a different country now, so it's going to be difficult to monitor the blinkup light, but everything is working ok now the firmware updates have been pushed successfully. Thanks.
  • I mean just put a notice/warning on the app page where the wifi settings are entered, such as, "NOTE: Some imps support 2.4GHz only." I think a lot of folks would have a better experience. As in this thread, it's a typical issue that's often overlooked. Just a suggestion! I love the imp, and hope it succeeds!! :) I think just a few tweaks like this would really help. I also think a Visual Studio add-on would make it much more attractive, and I don't think it would be very hard to do. Working in the online IDE is just not a long-term option.
  • edited January 21
    Yes, understood that there are some things that could improve the experience and we have them on our to-do list.

    I believe some people are already using VS to deal with the imp, you can certainly do this. Most serious developers use the command line tools & things like builder or sublime text to do their development.

    btw, there are well over a million devices on impOS :)
  • OK, I'm still having issues with imps connecting to Ubiquiti Nanostation M2 (2.4G only). I can telnet to the network, I can connect using my phone. Some imps connect to the network, and some don't (they all work fine with other wifi routers - eg my phone tethering). Any ideas - has anyone got experience using the Nanostations? Something in the settings that would cause some imps to connect and others not?
  • Not with the nanostation, no, but we use ubiquiti stuff in our offices.

    How close is the imp to the station? Too close can overload the receiver in the imp.
  • Usually about 500metres. So I don't think it's overload. it's on farms, rssi about -80dBm for devices that successfully connect
  • -80 is low, but ok. There will be variation device to device... but when you're low on signal the housing can make a big difference. If you bring a device that works and one that doesn't to a range where they both work, what's the difference in RSSI?
  • edited February 12
    I'll see if I can find an un-deployed device that doesn't connect to do that comparison, thanks for the suggestion.

    But I'm not sure it's RSSI related. I've got other devices that connect fine at -90dBm, even down to -94 for some devices below the crop!

    Will try to gather more information.
  • I think I know what part of the problem is. My Ubiquiti stations have country set to Australia (that's where I am), and sometimes the WiFi channel is 12 or 13. But some of my imps are US and some are "rest of the world". So the US ones are failing to connect. It looks like the imp country can only be set at the factory, so I'll try and change the Ubiquiti frequency list
Sign In or Register to comment.