Hi So for a number of months I've been playing around with the linux wifi config on the wifi module.. all worked very well, no issues, made some great improvements... then I figured out how to use a serial cable to connect into the wifi module (incase you make a change and wifi does not come back up again). I had to splice into the 6 wire cable that goes from the camera to wifi module, but instead of fixing that cable I bought the cable kit and just put a new cable in its place. Everything has been working great since.... reason I am mentioning this is incase someone says 'hey don't you mess around with the wifi module heaps' :] Anyways so all working 100%... went to USA for 3 weeks and now I've come back used it a few times and all good. Now all of a sudden when I turn the Phantom and RE back on the wifi SSID is visible on my phone or laptop but I can't connect.. it won't get an IP address... after about 30 seconds the SSID dissapears and won't come back.. rarely I've had this problem since day 1.. but usually a reboot fixs it and the SSID is there and you can connect. I've cecked all the connections, everything appears to be firmly connected... The only thing I can think of checking is using the serial cable to connect into the wifi to see if there are any errors coming up... Besides that anyone have any ideas ?? I permanantly have my wifi module set at 17dbm, but I nver left the phanton on for to long without the motors running to provide adequare cooling. Now when peoples wifi modules burn out, its my understanding the video feed stops working but the app still works, or worst case they can atleast join the wifi network ?? Perhaps my understanding is wrong ? Generally if the wifi module burns out can you still connect to the wifi network ? Question is kind of like 'how long is a piece of string' Don't really want to spend $250 on a new wifi module to find out the problem is else where, which I suspect it is... I guess My next course of action should be consoling into the wifi module, atleast then I can see if its even booting up.... The motors still start up etc etc.. Annoying.. because its my bday on Friday and I was going to get a new batttery, but now I might need a new wifi module and new battery, which is like $500AUS for both... a P3 costs $2k so hardly worth the repair costs......... Anyways I find it odd the SSID is seen for 30-60 seconds then dissapears, can't think of why it would be doing that.. aaaah crap!!!!!!!!!!!!!!!!!!!!!!!!!!!!! I just remembered you can't console in unless you modify a file....ser2net.conf needs to be commented out so ttys0 is not part of ser2net.. crap crap crap Unless someone has some suggestions I might be screwed... it sucks as well cause I messed around so much I would of assumed it was me who actually did something to kill it.... not the **** thing just randomly developing some isssue.