| T O P I C R E V I E W |
| gmcuser |
Posted - 08/12/2019 : 18:34:52
Is the limitation on sending more than 32 bytes part of the firmware, or is there another way to communicate with the GMC-600? Often I have wifi networks that have a longer sid or especially the wifi password. The current 32 byte limitation prevents the counter from working at all because the user cannot enter the full information either through the form in the GMC data viewer, or using the AT+CWJAP_CUR command. At least with the ESP8266, we know that it is capable of longer sid names and passwords, so is there anyway to program the ESP8266 directly, so that we can make the device useful on wifi networks?
Thanks! |
| 9 L A T E S T R E P L I E S (Newest First) |
| Slyke |
Posted - 09/06/2019 : 16:11:40
From some photos I've seen of people post here, you are using a ESP-12S which is similar to the ESP8266 D1 Mini Pro. I have developed on these before, it supports wifi passwords longer than 32 bytes. It also supports HTTPS! I use the native library for it from https://www.wemos.cc You might consider trying out an ESP8266 and see how well it fairs for future iterations.
I'm not sure how much of the logic you've put on the ESP-12S, but I would imagine you just use it for BT/Wifi communication and use either I2C or SPI to tell it what to send, and where. |
| EmfDev |
Posted - 08/26/2019 : 09:42:52
Yes the 'Connecting' blocks and it won't be executed until the popup is gone.
What about you connect to WiFi with WiFi on. Then you disconnect though AT command and connect through at command again with your desired SSID. You can use hotspot to connect it to WiFi to toggle the variable to ON. |
| gmcuser |
Posted - 08/24/2019 : 11:12:33
I've tried doing a WiFiOn and then waiting for a second and sending the AT commands, but it doesn't seem to work. I think WifiOn may block so by the time I get to execute the the AT commands it has already turned off the Wifi. |
| EmfDev |
Posted - 08/19/2019 : 09:59:01
That's because the <WiFiON>> returns the variable that was when when setting the Wi-Fi ON from the device. Let us think about it maybe there's a workaround. |
| gmcuser |
Posted - 08/18/2019 : 18:45:06
There are a couple of issues regarding setting the wifi directly via the AT commands.
The first problem is just doing it, because the GMC DATA viewer doesn't allow sending more than 32Bytes even with AT commands.
When trying to use a terminal program, I ran into issues - I tried terraterm, putty, minicom, etc... I think something is happening with buffering maybe.
Every time I connected and did <GETVER>> nothing would happen.
I finally just used the python serial libraries to send what I needed, and was able to get GMC-600 to associate by sending it:
<AT+CWJAP_DEF="mysid","mysecurebutlongwifipasswordetc">>
The geiger counter shows up as ESP_A92193 with an IP, and the AT+CWJAP_DEF? shows it associated. Yeah!
However, your firmwire doesn't seem to know that. If I try to test the connection from the GMC-600 it will complain that Wifi is not on.
But when I try to turn it on with <WiFiON>> then my good values are overriden by the GMC settings for wifi, which of course doesn't like more than 32 bytes for some reason.
So I think I'm stuck unless there is a workaround or some firmware fix, beyond downgrading the security of my wifi network. The easy fix would just be to look at the value of the AT+CWJAP_DEF?, and use that if associated. And if not then do as current behavior. |
| gmcuser |
Posted - 08/14/2019 : 15:26:39
Thanks. At least on windows 10, doing it from the GMC Data viewer might be better. When I try to open the COM port with putty or teraterm at 115200,8N1 it does connect but I am not able to send any commands to it, so there may be some issue on Windows 10 using terminal programs. |
| EmfDev |
Posted - 08/14/2019 : 09:58:30
That's true. We will also consider updating the terminal. Also you can use other software you trust to send AT commands to the unit. |
| gmcuser |
Posted - 08/13/2019 : 19:17:42
Thanks. The problem with the AT commands is that the GQ Terminal App also limits those to 32Bytes.
For example if I type AT+CWJAP_CUR in the command text field, and "demosid, longwifipasswordmorethan32byteshere" in the parameter field, then you also get the 32byte error when you click Send command with Paramters.
If this is an artificial limit in the GQ Terminal app, then maybe you could remove that so we can set the WPA password for networks that have long ones. Thanks again. |
| EmfDev |
Posted - 08/13/2019 : 09:19:52
Hi gmcuser, there are limitations on the WiFi only 32 bytes are accepted as of now but we will be working to change it to support more than 32 bytes of data.
As for the AT commands, I believe it can support up to about 256 bytes. |
