I made a new Backbone view in which I want to send data (example: 0x00, 12345, asbcd, Hello, etc.) to the ZentriOs device and receive them in the UART port or in a stream handle.
I tried with websocket and even in the TeraTerm terminal I see the request of the TCP connection and generates the flow controller, but the module does not accept the connection.
How can I send the data with JavaScript from the Backbone view to the device and receive it in UART or in a stream handle?

Where can I find details on the WGM110's power save modes?  The datasheet has just a few words of description for each mode and no information about how to enter or exit the modes.

The API reference manual has only slightly more information.  cmd_system_set_max_power_saving_state seems to be the only relevant command that's documented.  It says the command defines the maximum power saving state the module is allowed to enter.  How do you guarantee that it enters a particular mode?  Do you set the radio off first before allowing EM2?

Presumably the module will also wake on reset, right?

Scott

     In WGM110A, for ADC the reference is set as 3 which corresponds to internal differential 5 volt using the below statement.
     <adc reference="3" />
    The API used for ADC is   call hardware_adc_read(2)(adc_result, 2, adc_value)
     Channel number 2
     12 bit Adc

     Below are the ADC observations

	Vin	Adc value	Adc value
		(Practical )	(Theoritical)
	2.5	946	2048
	3	952	2457.6
	3.4	961	2785.2
	3.8	964	3112.9

 Adc (theoritical) = 4096* Vin/Vref

 
 The adc counts are not as per expected.
  Even after the changing the reference number the ADC value are not approximate.

Please let me know how do I get the correct  Practical ADC counts.

Sir/Madam,

I have to use lcd display of wireless starter kit in wgm110 module. For example, to display the available wifi network.How can i do this. Please help me with this problem.

Sir/Madam,

I have a wifi router with ssid="example" and password="qwert123". Now i have to connect wgm110 to this router. How can i achieve this programatically  using both simplicity studio and BGTool. Please help me with this problem.

Hello,

I have implemented a Wifi AP-station using the WGM110 chip with integrated antenna. The software version of the WGM110 is 1.0.1. The power saving mode ist set to parameter 0.

During bench test I measured a very low signal strength at 2,4 Ghz. When I use a WGM110 starter kit as AP-station instead, the signal strength is as expected. Both devices are waiting for clients to connect. Nothing else will happen.

Then i compared the power consumption on pad 39 of the WGM110, both on my hardware and on the starter kit. The pad 39 is used to supply the Wifi-kernel of the WGM110.

There is a big difference.

The starter kit switches all 100ms the power signal on for about 1,5 ms (see picture A)

On my hardware this happens even although all 100 ms, but the power signal breaks down already after 0,1ms (see picture B).

 

What could be the reason of this behaviour ?

Good morning,

I am currently using WF121 Wireless Development Kit with Bluegiga Wi-Fi Software and SDK v.1.4.1 and I need to use I2C to read data from multiple registers (from RGBW Color Sensor VEML6040). 

For that purpose, I configure I2C to channel 1 and baud rate to 250KHz writing
<i2c channel="1" brg="160" />
into project.xml

and then initialize I2C communication and configure senzor (into register 00h write 00h)
export procedure i2c_init()
  call i2c_start_write(I2C_SLAVE_ENDPOINT, I2C_SLAVE_ADDRESS)
  call endpoint_send(I2C_SLAVE_ENDPOINT, 2, "\x00\x00")
  call i2c_stop(I2C_SLAVE_ENDPOINT)
end

Then I try to read 2 Bytes from register read_reg (measured data are stored in registers 8,9,10 and 11)
export procedure i2c_read_temperature(read_reg)
  call i2c_start_write(I2C_SLAVE_ENDPOINT, I2C_SLAVE_ADDRESS)
  call endpoint_send(I2C_SLAVE_ENDPOINT, 1, read_reg)
  call i2c_stop(I2C_SLAVE_ENDPOINT)

  call i2c_start_read(I2C_SLAVE_ENDPOINT, I2C_SLAVE_ADDRESS, 2)
  call i2c_stop(I2C_SLAVE_ENDPOINT)
end

Then I try to read data from endpoint
event endpoint_data(endpoint, data_len, data)
  if endpoint = I2C_SLAVE_ENDPOINT
    i2c_temperature = data(0:2)
  end if
end

Function i2c_read_temperature(read_reg) is called periodically from timer (every 1s).

My problem is that I am able to read data only from registers read_reg=8 and read_reg=10. When I try read information from registers 9 and 11, WF121 stops responding (see log below from situation when I2C stop respond). 

2018.06.13 12:11:14.0005 wifi_evt_system_boot major: 1 (0x0001) minor: 4 (0x0004) patch: 1 (0x0001) build: 91 (0x005b) bootloader_version: 5 (0x0005) tcpip_version: 0 (0x0000) hw: 4 (0x0004)
2018.06.13 12:11:14.0005 RX: 880e01000100040001005b00050000000400

2018.06.13 12:11:14.0005 wifi_rsp_i2c_start_write result:0x0000 ['No Error']
2018.06.13 12:11:14.0005 RX: 080208010000

2018.06.13 12:11:14.0005 wifi_rsp_endpoint_send result:0x0000 ['No Error'] endpoint: 4 (0x04)
2018.06.13 12:11:14.0005 RX: 08030500000004

2018.06.13 12:11:14.0005 wifi_rsp_i2c_stop result:0x0000 ['No Error']
2018.06.13 12:11:14.0005 RX: 080208020000

2018.06.13 12:11:14.0005 wifi_rsp_tcpip_mdns_set_hostname result:0x0000 ['No Error']
2018.06.13 12:11:14.0005 RX: 0802040a0000

2018.06.13 12:11:14.0005 wifi_rsp_tcpip_dnssd_add_service result:0x0000 ['No Error'] index: 0 (0x00)
2018.06.13 12:11:14.0005 RX: 0803040d000000

2018.06.13 12:11:14.0005 wifi_rsp_tcpip_dnssd_add_service_instance result:0x0000 ['No Error']
2018.06.13 12:11:14.0005 RX: 0802040e0000

2018.06.13 12:11:14.0005 wifi_rsp_tcpip_dnssd_add_service result:0x0000 ['No Error'] index: 1 (0x01)
2018.06.13 12:11:14.0005 RX: 0803040d000001

2018.06.13 12:11:14.0005 wifi_rsp_tcpip_dnssd_add_service_instance result:0x0000 ['No Error']
2018.06.13 12:11:14.0005 RX: 0802040e0000

2018.06.13 12:11:14.0005 wifi_rsp_tcpip_dnssd_add_service_attribute result:0x0000 ['No Error']
2018.06.13 12:11:14.0005 RX: 0802040f0000

2018.06.13 12:11:14.0005 wifi_rsp_tcpip_dnssd_add_service_attribute result:0x0000 ['No Error']
2018.06.13 12:11:14.0005 RX: 0802040f0000

2018.06.13 12:11:14.0006 wifi_rsp_sme_set_operating_mode result:0x0000 ['No Error']
2018.06.13 12:11:14.0006 RX: 0802030a0000

2018.06.13 12:11:14.0006 wifi_rsp_sme_wifi_on result:0x0000 ['No Error']
2018.06.13 12:11:14.0006 RX: 080203000000

2018.06.13 12:11:17.0669 wifi_evt_sme_wifi_is_on result:0x0000 ['No Error']
2018.06.13 12:11:17.0669 RX: 880203000000

2018.06.13 12:11:17.0669 wifi_rsp_tcpip_configure result:0x0000 ['No Error']
2018.06.13 12:11:17.0669 RX: 080204040000

2018.06.13 12:11:17.0669 wifi_evt_tcpip_configuration address:192.168.1.1 netmask:255.255.255.0 gateway:192.168.1.1 use_dhcp: 0 (0x00)
2018.06.13 12:11:17.0669 RX: 880d0400c0a80101ffffff00c0a8010100

2018.06.13 12:11:17.0669 wifi_rsp_system_set_max_power_saving_state result:0x0000 ['No Error']
2018.06.13 12:11:17.0669 RX: 080201030000

2018.06.13 12:11:17.0669 wifi_rsp_sme_set_ap_password status: 0 (0x00)
2018.06.13 12:11:17.0669 RX: 0801030f00

2018.06.13 12:11:17.0669 wifi_rsp_sme_start_ap_mode result:0x0000 ['No Error'] hw_interface: 0 (0x00)
2018.06.13 12:11:17.0669 RX: 0803030b000000

2018.06.13 12:11:17.0669 wifi_evt_flash_ps_key_changed key: 22 (0x0016)
2018.06.13 12:11:17.0669 RX: 880207011600

2018.06.13 12:11:17.0845 wifi_evt_sme_ap_mode_started hw_interface: 0 (0x00)
2018.06.13 12:11:17.0845 RX: 8801030a00

2018.06.13 12:11:17.0845 wifi_rsp_https_add_path result:0x0000 ['No Error']
2018.06.13 12:11:17.0845 RX: 080209010000

2018.06.13 12:11:17.0845 wifi_rsp_https_add_path result:0x0000 ['No Error']
2018.06.13 12:11:17.0845 RX: 080209010000

2018.06.13 12:11:17.0845 wifi_rsp_https_enable result:0x0000 ['No Error']
2018.06.13 12:11:17.0845 RX: 080209000000

2018.06.13 12:11:17.0845 wifi_evt_tcpip_configuration address:192.168.1.1 netmask:255.255.255.0 gateway:192.168.1.1 use_dhcp: 0 (0x00)
2018.06.13 12:11:17.0845 RX: 880d0400c0a80101ffffff00c0a8010100

2018.06.13 12:11:17.0845 wifi_evt_tcpip_dns_configuration index: 0 (0x00) address:208.67.222.222
2018.06.13 12:11:17.0845 RX: 8805040100d043dede

2018.06.13 12:11:17.0845 wifi_evt_tcpip_dns_configuration index: 1 (0x01) address:0.0.0.0
2018.06.13 12:11:17.0845 RX: 880504010100000000

2018.06.13 12:11:17.0845 wifi_evt_sme_interface_status hw_interface: 0 (0x00) status: 1 (0x01)
2018.06.13 12:11:17.0845 RX: 880203070001

2018.06.13 12:11:17.0845 wifi_rsp_hardware_set_soft_timer result:0x0000 ['No Error']
2018.06.13 12:11:17.0845 RX: 080206000000

2018.06.13 12:11:17.0846 wifi_rsp_hardware_io_port_config_direction result:0x0000 ['No Error']
2018.06.13 12:11:17.0846 RX: 080206040000

2018.06.13 12:11:17.0846 wifi_rsp_hardware_io_port_write result:0x0000 ['No Error']
2018.06.13 12:11:17.0846 RX: 080206060000

2018.06.13 12:11:17.0846 wifi_rsp_tcpip_mdns_start result:0x0000 ['No Error']
2018.06.13 12:11:17.0846 RX: 0802040b0000

2018.06.13 12:11:18.0853 wifi_evt_hardware_soft_timer handle: 0 (0x00)
2018.06.13 12:11:18.0853 RX: 8801060000

2018.06.13 12:11:18.0853 wifi_rsp_i2c_start_write result:0x0000 ['No Error']
2018.06.13 12:11:18.0853 RX: 080208010000

2018.06.13 12:11:18.0853 wifi_rsp_endpoint_send result:0x0000 ['No Error'] endpoint: 4 (0x04)
2018.06.13 12:11:18.0853 RX: 08030500000004

2018.06.13 12:11:18.0853 wifi_rsp_i2c_stop result:0x0000 ['No Error']
2018.06.13 12:11:18.0853 RX: 080208020000

Plus from registers 8 and 10 I am reading same value (the values stored in these registers should be different).
The sensor VEML6040 that I use is ok (I'm able to put it into operation using Arduino).

Thank you in advance for your answer.
Regards
Radek Halfar

I cannot find any documentation that mentions the wf121-a-v2c. What does the c suffix mean? Is it 100% compatible with the wf121-a-v2?

Thanks

Hi there... How are you?

I'm facing an error to compile the driver (5.2.2-r3) for the WF111 chip for a ARMv7 (Toradex Colibri VF61).

I've followed the instructions presented in the documentation (AN996), but when I execute the

make install_static ARCH=arm KDIR=... CROSS_COMPILE=arm-linux-gnueabihf-

command, the compilation terminates with the error:

/home/ives/Downloads/wf111-linux-driver_5.2.2-r3_armv7-a/csr/os_linux/driver/../../os_linux/driver/netdev.c: In function 'uf_alloc_netdevice':
/home/ives/Downloads/wf111-linux-driver_5.2.2-r3_armv7-a/csr/os_linux/driver/../../os_linux/driver/netdev.c:378:8: error: 'struct net_device' has no member named 'wireless_handlers'; did you mean 'rx_handler'?
     dev->wireless_handlers = &unifi_iw_handler_def;

I'm using the toolchain gcc-linaro-6.2.1-2016.11-x86_64_arm-linux-gnueabihf. My host is Ubuntu 16.04. I've attached the log.

Any ideas? Is this a known problem?

Thanks in advance,

Ives.

Hi everyone,

I am planning on EMC prescreening test with WF121/WGM110 and hardware engineer asked me to send UDP broadcast data to see only TX EMI.

I think if the modules connect to AP, the module can send broadcast message with cmd_tcpip_udp_connect() + IP address 255.255.255.255. Is it correct?

However, even though my thinking will work, there is a big issue to carry out the test. We can't setup AP test chamber inside.

So, my another question is... Can  WF121/WGM110 send UDP broadcast message (data) without AP connection in station mode?

Here is my last question. How can Wi-Fi module on a board be tested for EMC? Is there AP or some equipment in a chamber?

I am quite a newbie for EMC so I would listen to you guys advice. Thanks.

 

Chris

Our software was developed using version 1.2.0R of the firmware.

Digikey now shipping AMW007_1.3.0R firmware.   

What are the differences?   In particular are there any changes to the firmware that would justify the effort for us to re-certify our code with the new firmware?   

I’m using the WGM110 to periodically send collected data to a central server. Once a minute the MGM is brought out of low power mode by an external MCU, it then sends a UDP packet to a server, waits for a response packet back, and then goes back a low power state.

99% of the time it works fine, however I’ve started to notice that it will occasionally get into a state where the WGM110 doesn’t seem to receive any UDP packets. I’ve verified that the server has received the outgoing packet, plus all the subsequent retries, and send out an acknowledgement for each, but the WGM100 won’t send any “wifi_evt_tcpip_udp_data” events to the MCU.

The problem persists even when closing and reopening the UDP endpoints between upload attempts. I’ve seen it last up to 30min before it seems to fix itself, although restarting the module and reconnecting to the WiFi network also fixes it. DNS lookups seem to be unaffected when in this state.

 

I’m also getting the occasional “0x0187 Hardware failure” error when attempting to send a packet. These aren’t as big of an issue as my code automatically turns the WiFi back on and reconnects, but I’m concerned that they may be related.

Everything in my design seems to conform to the supplied design guidelines and the power rail doesn’t drop below 3V at any time.

 

I'm currently stumped and have run out of ideas. The fact that they're both pretty infrequent and hard to catch in the act doesn't help much.

Hi

What is the speed that data will be send when u use the WGM110 module.

For TCP and UDP , and When u only use BGscript or when you work with an external chip to send commands

Thanks

Brend

Hi

I am testing the wifi_ap bgscript code from the WizardGeckoSDK. When I program the code into the WGM110 module, I can connect with the module but thats it.

I tried to adjust the code so i can send data from the WGM110 module to a PC, but ofcourse I am making a mistake somewere.

Can someone look at my code or send a working example?

I will attach my code to this question

Thanks

Brend

I want to use the command interface in machine mode, but I can’t receive asynchronous messages from AWM007 in important events, for example: new client connection in softAP mode or when the module has a successful connection in WLAN mode. There is a different way of configuration to get this communication way between my MCU and the AWM007?. Additional information: system.cmd.echo=off, system.cmd.mode=machine, system.print_level=4