I selected a WIFI network SSID showing up in the neighbourhood to which i dont have the password (i.e. NETGEAR68).

I noticed that the always GREEN flashed slowly during the [Associating to NETGEAR68] stage 

then later it reverted to flashing at a medium rate. The Yellow was always flashing very fast

I want to know the clear distinction between:

GREEN LED - Documentation states this is for the Wifi status

and

YELLOW LED - Documentation states this is for the Network status

When we have connectivity to the network, both LEDS flash at about a 1 second rate.

We have a situation where the GREEN led flashes at about a 1 second rate, but the YELLOW one flashes at a fast rate.

What does that actually mean?

Thanks

David

Can you suggest a possible replacement for our current use of the AMW006 wifi module as a tcp server:

a) a u.FL connection

b) Can be configured as a TCP server.

Thanks

David Nyarko

Can you suggest a possible replacement for our current use of the AMW006 wifi module as a tcp server:

a) a u.FL connection

b) Can be configured as a TCP server.

c) MCU connection is via UART

Thanks

David Nyarko

Followup to a previous post:

We have AMW006 modules configures as TCP servers (default port : 3000) and on occasion these would hung up where the TCP client cannot connect to it.

However when we run a ping command, we do get a response. It seems the TCP server portion is non-responsive. Power cycling the wifi module clears the problem.

The client communication is about 100 bytes every 6 seconds.

The OS is still "WiConnect-2.4.1.5". I had an issue upgrading ( as per some of my previous posts)

Could there be an option i am configuring wrongly?

Below is the result of the "get tcp.server" command

> get tcp.server
tcp.server.auto_interface: default
tcp.server.auto_start: 1
tcp.server.connected_gpio: -1
tcp.server.data_gpio: -1
tcp.server.idle_timeout: 0
tcp.server.max_clients: 8
tcp.server.port: 3000
tcp.server.tls_cert:
tcp.server.tls_enabled: 0
tcp.server.tls_key:
tcp.server.tls_verify_peer: 0
>

Sorry for the very late response. We thought just a periodic reboot would solve this.

Below is the result of the "get tcp.server" command

> get tcp.server
tcp.server.auto_interface: default
tcp.server.auto_start: 1
tcp.server.connected_gpio: -1
tcp.server.data_gpio: -1
tcp.server.idle_timeout: 0
tcp.server.max_clients: 8
tcp.server.port: 3000
tcp.server.tls_cert:
tcp.server.tls_enabled: 0
tcp.server.tls_key:
tcp.server.tls_verify_peer: 0
>

Hi,

We have AMW006 modules configures as TCP servers (default port : 3000) and on occasion these would hung up where the TCP client cannot connect to it.

However when we run a ping command, we do get a response. It seems the TCP server portion is non-responsive. Power cycling the wifi module clears the problem.

The client communication is about 100 bytes every 6 seconds.

Is it possible to setup a service/server on the wifi module (configured as a tcp server) to act similar to an Administrative mode that can be communicated with via the Wifi side ( Not MCU) to reboot the wifi module.

The OS is still "WiConnect-2.4.1.5". I had an issue upgrading ( as per some of my previous posts)

Thanks

David

I also tried using my phone hotspot and this is what i got.

> ota
TCP server stopped
[2019-11-22 | 13:57:21: Disassociated]
Connecting to network
Security type from probe: WPA2-AES
Request POST /ota/0641304100000000630033000351353034373336/0
Connecting (https): ota.ack.me:443
Starting TLS
Failed to retrieve fw bundle manifest
OTA failed to update firmware
[Ready]

Hi Ayman,

I am located in Calgary, Alberta, Canada.

An older module (not part of the 35 modules order)  which i had updated to Zentrios works on the same Network with the 'ota' command.

> version
ZENTRI-AMW006-3.6.3.0, 2018-09-13T04:57:09Z, ZentriOS-W-3.6.3.0, Board:AMW006-A1W.2

> ota
TCP server stopped
[2019-11-18 | 14:42:14: Disassociated]
UUID: 0641304100000000410035001351353033363530
Connecting to network
Request POST /ota
Connecting (https): ota.zentri.com:443
Starting TLS
Bundle size: 0, Free space: 819200, Core size: 0
Firmware already up-to-date
[Ready]