The DigiX > DigiX Support

DigiX WiFi not connecting to my AP

(1/3) > >>

exeng:
With some reluctance I'm appealing to those who have success using DigiX Wifi.  I'm currently battling with the DigiX to get it to connect to my AP and run the BasicClient example as proof that it is working.

Haven't used the DigiX for a few years and recently decided to put it in service for a project that will among other things access Thingspeak to pull down some cloud data that is posted by my Oaks.

Here is the thing. I know that I had DigiX wifi working in the past (3 years ago) as I did run BasicClient and even had it emulating a Lifix bulb that controlled an RGB. So it was working in the past.  Basically I'm getting the impression (evidence suggests) that it's not getting an IP address from my router. That is one thing that has changed (different router).

Am I correct that once configured as STA mode (actully AP+STA so I can see the configuration screens) with the proper credentials, I should see an assigned IP address in the configuration (@10.10.100.254) System screen once it connects?

I can access the DigiX AP, reset Wifi, configre things, but can't seem to get and IP. I tried another standalone router and could see the DigiX connected it (MAC showed up) but no IP listed.

Any help / pointers to things to try would be helpful. I just want it to be a client on my net accessing the internet.

Powering via USB, JACK, JACK+USB does not seem to make a difference.

PeterF:
Oh fine... I had to dig out the DigiX to get you to settle ;-) (never mind the fact it was sat on a shelf in the cupboard about 3m away from my computer table as it had been pulled out recently for something else...  ;D)

So... I tried the WiFi... and I had pretty much the same experience as you... the WiFi signal strengh kept flapping around like a flag in the wind, and I got a super great IP of 0.0.0.0...  :'(

I then went back into the STA settings, and realised that 1) the encryption was wrong, and 2) it had decided that the SSID was "" (blank). I typed it in instead of using the scan button, and set the encryption again, saved it, rebooted, and now have a valid 192.168.0.x address on my network. It is pingable, and is finally visible of my router, so all seems good.The WiFi signal strength is still hopping around a bit between 75-90%, but stays in the high 80s most of the time.

Maybe that will give you some hope for when you get the magic smoke back into the DigiX. btw, this was when powered via microUSB with a roughly 5.1v input voltage... I don't feel the need to smoke test my DigiX just yet! :o

exeng:
Pete, thanks. Part(s) (3) are on order. If I get it down correctly on the first try, I can try my hand at making a Buck converter.

I guess I can try typing the SSID instead of scanning for the SSID but that seems like a long shot. Oh well, let's hope for the best.

I'm thinking that the smoke may have been a result of some high in rush current has instead of unplugging and plugging the PS at the wall, I was simply plugging and unplugging at the barrel jack. Just a guess. In any case that PS will never get near my DigiX again.

exeng:
So while I'm waiting to build the courage and experience to put a new SAM MCU on my DigiX, I've been looking at the WiFi issue that I was chasing before the board fried the buck converter, regulator and MCU. The WiFi chip survived but it is still exhibiting the problem on not connecting to my AP when in AP+STA mode with proper credentials. For the record this was happening before the fry incident while the board was complete and working.

It does not seem to connect to my main router which is not the same router I had a few years ago when DigiX WiFi was working just fine as far as I can tell. I have a second Netgear router that I tried and I can see the MAC on the router but no IP address assigned. I have one more router to try on (the one that it worked on in the past), but I won't be able to access it until, Monday.

BTW, I can access the AP and do all the configuration stuff, so I'm pretty sure that the chip is working. So here is my question... If I configure the WiFi as AP+STA and give it the proper credentials to access my main AP, shouldn't it upon restart should in the config screen that the STA is connected and have an IP assigned? This is all without the DigiX MCU involved. Basically, with the WiFi chip configured and powered on, I'm expecting it to connect to my AP (not the chips AP).

Can any of you DigiX owners confirm or deny this?

PeterF:
That's what I have (had)... once I got past the fact that it didn't seem to want to set the SSID/encryption properly in the first place. I'd picked it from the drop down list, but the SSID was missing on a reboot, so I typed it in manually, and re-picked the encryption type, and it behaved from then onwards. I can run it up again and load some screenshots if you want to see what it looks like on my setup in AP+STA mode...

Navigation

[0] Message Index

[#] Next page