ESP8266-05 always return +CWJAP:4 on connection to any Wi-Fi network - networking

I am a novice with ESP8266. I have an ESP-05 module connected to my PC USB through CH340 com-port adapter.
I was able to list all networks with AT+CWLAP, but when I put the command to connect to, it shows me a CWJAP:4 error. I tried my home network, the network in my office, and the Wi-Fi network created by my Android phone. The same result always...
AT+GMRAT version:1.3.0.0(Jul 14 2016 18:54:01)
SDK version:2.0.0(5a875ba)
v1.0.0.3
Mar 13 2018 09:35:47
OK
AT+CWMODE=1
OK
AT+CWLAP+CWLAP:(3,"TheSecretChamber",-76,"f0:79:59:d3:00:44",13,68,0)
+CWLAP:(4,"Ufanet_70",-90,"04:5e:a4:76:0d:cf",3,50,0)
+CWLAP:(3,"AndroidAP",-49,"84:98:66:ce:a6:ed",6,66,0)
OK
AT+CWJAP="TheSecretChamber","mypasswordhere"+CWJAP:4
FAIL
The password is 100% valid (I've tried to put the wrong password, in this case, it returns CWJAP:3 as required).
What can be a reason?? Thanks.

I found the solution by myself. It looks like the USB port I used initially has not enough power or it's broken somehow. The network list command is working, but its USB power was not enough to handle transmitting.
I just tried another USB port and it works well.
Thanks all.

Related

Connecting to service provider on SIM7000A chip through Verizon tower

I have a SIM7000A device that sees the Verizon tower. I am using Ting wireless SIM to create an IoT device to send emergency information to a homeowner. The SIM works on T-Mobile and Verizon networks.
You can see the tower:
I have selected the wireless.dish.com APN to connect to.
When I try to connect I get this:
My IMEI number is a registered device with Ting. I've verified that.
Using the AT Command Tester for Simcom Modules I get an error when I try to check the Preferred Operators list. I'm not sure if this has anything to do with it.
It seems like when I try to connect, Verizon is trying to validate my device and halting me. How do I connect "through" Verizon's network to the Ting network?
Well, I figured it out. The SIM7000A is not compatible with the Verizon network. According to the person I spoke with at Ting.com, this device only works on T-mobile. With that network, it is not even worth trying to distribute my product to consumers if it uses this chip. I show AT&T as available from this chip but it won't connect to Ting.com regardless. She said it is only compatible with T-Mobile.
I guess I will have to find a new chip.

Serial Port not working on Surface Book

I have a Microsoft Surface Book that I've dual booted Linux Mint on. I'm writing a program that needs to read in data from a serial port, but my serial ports don't seem to be working. The behavior is consistent across Mint and Windows (Testing done through Cygwin). It gets a bit of data the first 2-5 seconds that the device is plugged in (viewing the data through screen, same thing happens if I just use pyserial to print data incoming from serial port), then nothing.
What could be happening? I think I've isolated the problem to the serial ports - the Surface Book has 2 USB ports and the same thing happens on both of them, and I've tested the hardware that I'm plugging into it on 2 other computers (One Linux and one Mac OS), and it works fine on both of those.
Your MS Surface, seemingly, has a yellow triangle exclamation mark icon (over the adapter icon) without any driver to install/download. And properties in the device status box window say This device cannot start. (Code 10) or A device which does not exist was specified. Right?
If it's so you should wait for an update from MS. It's notorious problem.
I ended up getting the computer replaced on warranty for an unrelated issue months later, and what do you know, on the new computer the serial ports work fine. That indicates to me some sort of hardware problem, given that the issue persisted across OS's.
maybe this will help:
see Arduino examples for serial port communication - search google:
arduino serial c++
arduino serial c#
arduino serial c++ linux
the point is to open port properly you need to open a file, not a port. not with usual c - assembly write to port code.
another option you are using an unintentionally bought fake USB to serial cable with a Fake PL2303 chip
then you need to install the old version of the driver.
search in google:
Fake PL2303 + your os name:
install driver Fake PL2303 windows 10
another option is maybe it conserves energy and closes the port because it feels it is unused.
in windows> device manager,> properties of a device - usually USB root hub > power management - allow the computer to turn off this device to save power - uncheck it.
https://superuser.com/questions/408683/why-my-usb-mouse-gets-suspended-after-3-seconds-of-inactivity
https://blogs.msdn.microsoft.com/usbcoreblog/2013/11/08/help-after-installing-windows-8-1-my-usb-device-doesnt-charge-or-it-disconnects-and-reconnects-frequently/
also, you could look in windows events - to see what happens. usually, failures like this are registered in the events log.
an unlikely option is it consumes too much current, like a short circuit. and the device protection circuit shuts the chip off. also probably it does not have such circuit. one possibility is to try with an external powered hub.
the most probable of these is the power saving mechanism
I was experiencing the same problem - came across the solution on another site. The USB 3 ports on Surface Book aren't compatible with something or other to do with Com Port but running the device through a cheap USB hub solved my problem straight away and it was instantly recognised by the Arduino IDE

What is causing putty to not connect to beaglebone black

I have a Beaglebone Black(rev c),I am trying to connect it to Windows 8 laptop using putty. I am putting IP address as 192.168.7.2 and port as 22,but when I says open to it,putty window will pop-up and after sometime I will get fatal ERROR saying:
"Network connection time-out"
I am new to this, can someone tell me what am i missing?
Seems to indicate the an SSH server is not running on the BBB. Or possibly for some reason the BBB did not take 192.168.7.2 as an IP. Or perhaps you might need to wait a little bit longer for the SSH server to start up.
Short of this, there is not much to go on. One way to trouble shoot the issue would be to get a serial debug cable, connected and working to the BBB. Then you could dmesg | grep ssh or some such and hopefully get closer to what the actual problem is. Sorry if this is not enough for you to go by, but it is really hard to figure out what is going on without more information.
Other potential problems could be as simple as a USB cable that sometimes works or sometimes doesn't.
It may not be this but have you installed the drivers? See step 2 here: http://beagleboard.org/getting-started. If it's not that or you have already installed those then I am not sure sorry. Perhaps someone else has another suggestion.
Is the BeagleBone connected to your network with an Ethernet cable? It will only use 192.168.7.2 for the network-over-usb when there's only a USB cable connected - if you have Ethernet connected it will use DHCP to get an IP from your router, in which case you can check your router page to see what IP it got.
If you do just have USB connected then a driver issue is the most likely culprit, but you could try to ssh to the hostname beaglebone.local instead of the IP.

Arduino yun wifi network not appearing in my available network on windows 8

I'm connecting my Arduino Yún to my laptop via USB cable and as I read in Arduino documentation:
When you first power on the Yún, it will create a WiFi network called
ArduinoYun-XXXXXXXXXXXX. Connect your computer to this network.
But in my case nothing appears and I didn't found anything related to this on the web.
I'm running Windows 8.1 on my laptop.
Any idea how I can solve this problem?
It sounds as if something is wrong with the wifi configuration on the Yún. Has it previously been configured? Try resetting the wifi by pressing the "Wifi RST" button for more than five seconds (but less than 30).
More info here.
The question you asked is already answered by #mellbratt. You have successfully configured Yun and connected it to the network (configuration of WiFi by providing SSID and security key in web panel). The thing you have to do now, is to find what IP your Yun device is assigned on that network. You can use tools like Angry IP Scanner to scan the network and find your IP if you cannot access it from myusername.local. Using that IP you can access the web panel.

Why don't I receive signal and status for WiFi using QSystemNetworkInformation

I wrote a piece of software which does nothing else than reading network status and signal strength for each network mode (gsm, wlan (wifi), bluetooth, ...) on my device (Nokia E51) and printing it out.
My test device is connected to bluetooth, wlan (wifi) and 3G (wcdma), but it's only able to give me the signal strength of 3G (and also returns the correct name of my carrier). for wlan and bluetooth it gives me the undefined state und isn't able to read any signal strenght. But I am able to receive the IP address of the network I'm connected via wlan.
All I do is:
QSystemNetworkInformation::networkSignalStrength(QSystemNetworkInformation::WlanMode);
and calling the method for the network status.
As I said, it works flawless for 3G.
Any ideas? Thanks a lot.
After an SDK update, everything works fine without any code changes. So the problem wasn't in the coede, but in the QtMobility backend.

Resources