Hello,
In your log I see only messages to WizFi360 but there are not shown responses from our module.
Do you process responses from WizFi360?
CIPSENDBUF will return “>”, and then it is possible to enter message to be sent.
Hello,
We do get responses from WizFi but we can only read from one side currently, so it’s ready what the MCU is sending. We will try to make it so we are able to read from both sides.
Yes, we are waiting for “>” to return, if we didn’t then the message wouldn’t be sent, or it would send something else other than what we needed it to send.
The Delay only happens if the WizFi is connected to an AP, if it couldn’t connect to an AP on power up, then the delay doesn’t happen at all and everything works well. But if its connected to an AP then the delays start happening.
Hello,
We have ordered another WizFi360 so we can use it to test it without an MCU, but with a serial-USB USB-UART converter to send it the commands.
If it ends up working with the same settings but not with an MCU then what would that mean?
Hello,
I have conducted many tests and tried to search for anything that could cause these delays, but unfortunately couldn’t find any.
In my opinion it might be caused by library from chip manufacturer. I will try to ask them if they had this issue.
Hello,
But if it is caused by code, then why does it work properly when Wizfi STA isn’t connected to an Access Point?
Hi,
It might be caused by library from chip manufacturer too and we are not able to debug it. I am trying to contact them at the moment. Please test without MCU and let me know.
Hello,
By that you mean WizFi Firmware Library?
I will test it without MCU when the new WizFi360 arrives later this week.
Hello,
WizFi360 is a module that is built on W600 chip from WInnerMicro. Our firmware utilizes its library to operate with chip. It looks to me like this issue is caused by their library, and we at WIZnet are not able to fix it. That’s what I was trying to explain.
Hello,
I understand, than you for explaining. I will wait for more news then, in the mean time I will test it without MCU when the new WizFi360 arrives.
Hello,
Have you got any news about this problem?
Hello,
I’m still waiting on an update on this.
Hi,
Unfortunately, there was no reply from chip manufacturer…
Were you able to test using WizFi360 without MCU?
Hello,
Yes I was able to test WizFi360 without MCU and the results are the same, the messages still get delayed.
(11:04:26.832) AT+CIPMUX=1
(11:04:26.896) AT+CIPMUX=1
(11:04:26.896)
(11:04:26.896) OK
(11:04:37.039) AT+CIPSERVERMAXCONN=3
(11:04:37.116) AT+CIPSERVERMAXCONN=3
(11:04:37.116)
(11:04:37.116) OK
(11:04:46.888) AT+CIPSERVER=1,5000
(11:04:46.972) AT+CIPSERVER=1,5000
(11:04:46.972)
(11:04:46.972) OK
(11:04:49.110) 0,CONNECT
(11:04:53.307) AT+CIPSENDBUF=0,10
(11:04:53.414) AT+CIPSENDBUF=0,10
(11:04:53.414) 1,0
(11:04:53.414)
(11:04:53.414) OK
(11:04:53.414) >
(11:04:53.492) 0123456789
(11:04:53.570)
(11:04:53.570) busy s…
(11:04:53.570)
(11:04:53.570) Recv 10 bytes
(11:04:53.570)
(11:04:53.570) 0,1,SEND OK
(11:04:54.211) AT+CIPSENDBUF=0,10
(11:04:54.275) AT+CIPSENDBUF=0,10
(11:04:54.275) 2,1
(11:04:54.275)
(11:04:54.275) OK
(11:04:54.275) >
(11:04:54.381) 0123456789
(11:04:54.391)
(11:04:54.391) busy s…
(11:04:54.391)
(11:04:54.391) Recv 10 bytes
(11:04:54.391)
(11:04:54.391) 0,2,SEND OK
(11:04:55.643) AT+CIPSENDBUF=0,10
(11:04:55.762) AT+CIPSENDBUF=0,10
(11:04:55.762) 3,2
(11:04:55.762)
(11:04:55.762) OK
(11:04:55.762) >
(11:04:55.879) 0123456789
(11:04:56.004)
(11:04:56.004) busy s…
(11:04:56.004)
(11:04:56.004) Recv 10 bytes
(11:04:56.004)
(11:04:56.004) 0,3,SEND OK
(11:04:56.995) AT+CIPSENDBUF=0,10
(11:04:57.165) AT+CIPSENDBUF=0,10
(11:04:57.165) 4,3
(11:04:57.165)
(11:04:57.165) OK
(11:04:57.165) >
(11:04:57.254) 0123456789
(11:04:57.416)
(11:04:57.416) busy s…
(11:04:57.416)
(11:04:57.416) Recv 10 bytes
(11:04:57.710)
(11:04:57.710) 0,4,SEND OK
(11:04:58.663) AT+CIPSENDBUF=0,10
(11:04:58.767) AT+CIPSENDBUF=0,10
(11:04:58.767) 5,4
(11:04:58.767)
(11:04:58.767) OK
(11:04:58.767) >
(11:04:58.943) 0123456789
(11:04:59.108)
(11:04:59.108) busy s…
(11:04:59.108)
(11:04:59.108) Recv 10 bytes
(11:04:59.108)
(11:04:59.108) 0,5,SEND OK
(11:04:59.595) AT+CIPSENDBUF=0,10
(11:04:59.709) 0123456789
(11:04:59.792) AT+CIPSENDBUF=0,10
(11:04:59.792) 6,5
(11:04:59.792)
(11:04:59.792) OK
(11:04:59.792) >
(11:04:59.792)
(11:04:59.792) busy s…
(11:04:59.792)
(11:04:59.792) Recv 10 bytes
(11:05:01.604)
(11:05:01.604) 0,6,SEND OK
(11:05:06.187) AT+CIPSENDBUF=0,10
(11:05:06.291) AT+CIPSENDBUF=0,10
(11:05:06.291) 7,6
(11:05:06.291)
(11:05:06.291) OK
(11:05:06.291) >
(11:05:06.460) 0123456789
(11:05:06.626)
(11:05:06.626) busy s…
(11:05:06.626)
(11:05:06.626) Recv 10 bytes
(11:05:13.171)
(11:05:13.171) 0,7,SEND OK
(11:05:15.509) AT+CIPSENDBUF=0,10
(11:05:15.621) AT+CIPSENDBUF=0,10
(11:05:15.621) 8,7
(11:05:15.621)
(11:05:15.621) OK
(11:05:15.621) >
(11:05:15.710) 0123456789
(11:05:15.877)
(11:05:15.877) busy s…
(11:05:15.877)
(11:05:15.877) Recv 10 bytes
(11:05:18.373)
(11:05:18.373) 0,8,SEND OK
(11:05:19.963) AT+CIPSENDBUF=0,10
(11:05:20.101) AT+CIPSENDBUF=0,10
(11:05:20.101) 9,8
(11:05:20.101)
(11:05:20.101) OK
(11:05:20.101) >
(11:05:20.230) 0123456789
(11:05:20.397)
(11:05:20.397) busy s…
(11:05:20.397)
(11:05:20.397) Recv 10 bytes
(11:05:20.397)
(11:05:20.397) 0,9,SEND OK
(11:05:22.107) AT+CIPSENDBUF=0,10
(11:05:22.291) AT+CIPSENDBUF=0,10
(11:05:22.291) 10,9
(11:05:22.291)
(11:05:22.291) OK
(11:05:22.291) >
(11:05:22.387) 0123456789
(11:05:22.468)
(11:05:22.468) busy s…
(11:05:22.468)
(11:05:22.468) Recv 10 bytes
(11:05:22.633)
(11:05:22.633) 0,10,SEND OK
(11:05:25.131) AT+CIPSENDBUF=0,10
(11:05:25.227) AT+CIPSENDBUF=0,10
(11:05:25.227) 11,10
(11:05:25.227)
(11:05:25.227) OK
(11:05:25.227) >
(11:05:25.394) 0123456789
(11:05:25.560)
(11:05:25.560) busy s…
(11:05:25.560)
(11:05:25.560) Recv 10 bytes
(11:05:25.560)
(11:05:25.560) 0,11,SEND OK
(11:05:29.499) AT+CIPSENDBUF=0,10
(11:05:29.628) AT+CIPSENDBUF=0,10
(11:05:29.628) 12,11
(11:05:29.628)
(11:05:29.628) OK
(11:05:29.628) >
(11:05:29.790) 0123456789
(11:05:29.878)
(11:05:29.878) busy s…
(11:05:29.878)
(11:05:29.878) Recv 10 bytes
(11:05:30.085)
(11:05:30.085) 0,12,SEND OK
(11:05:31.448) AT+CIPSENDBUF=0,10
(11:05:31.632) AT+CIPSENDBUF=0,10
(11:05:31.632) 13,12
(11:05:31.632)
(11:05:31.632) OK
(11:05:31.632) >
(11:05:31.726) 0123456789
(11:05:31.811)
(11:05:31.811) busy s…
(11:05:31.811)
(11:05:31.811) Recv 10 bytes
(11:05:32.127)
(11:05:32.127) 0,13,SEND OK
(11:05:32.260) AT+CIPSENDBUF=0,10
(11:05:32.315) AT+CIPSENDBUF=0,10
(11:05:32.315) 14,13
(11:05:32.315)
(11:05:32.315) OK
(11:05:32.315) >
(11:05:32.324) 0123456789
(11:05:32.334)
(11:05:32.334) busy s…
(11:05:32.334)
(11:05:32.334) Recv 10 bytes
(11:05:32.446)
(11:05:32.446) 0,14,SEND OK
(11:05:41.398) AT+CIPSENDBUF=0,10
(11:05:41.549) AT+CIPSENDBUF=0,10
(11:05:41.549) 15,14
(11:05:41.549)
(11:05:41.549) OK
(11:05:41.549) >
(11:05:41.680) 0123456789
(11:05:41.771)
(11:05:41.771) busy s…
(11:05:41.771)
(11:05:41.771) Recv 10 bytes
(11:05:41.771)
(11:05:41.771) 0,15,SEND OK
(11:05:43.747) AT+CIPSENDBUF=0,10
(11:05:43.888) AT+CIPSENDBUF=0,10
(11:05:43.888) 16,15
(11:05:43.888)
(11:05:43.888) OK
(11:05:43.888) >
(11:05:43.935) 0123456789
(11:05:44.181)
(11:05:44.181) busy s…
(11:05:44.181)
(11:05:44.181) Recv 10 bytes
(11:05:44.181)
(11:05:44.181) 0,16,SEND OK
(11:05:44.779) AT+CIPSENDBUF=0,10
(11:05:44.915) AT+CIPSENDBUF=0,10
(11:05:44.915) 17,16
(11:05:44.915)
(11:05:44.915) OK
(11:05:44.915) >
(11:05:44.964) 0123456789
(11:05:45.122)
(11:05:45.122) busy s…
(11:05:45.122)
(11:05:45.122) Recv 10 bytes
(11:05:45.122)
(11:05:45.122) 0,17,SEND OK
(11:05:46.531) AT+CIPSENDBUF=0,10
(11:05:46.691) >
(11:05:46.691) AT+CIPSENDBUF=0,10
(11:05:46.691) 18,17
(11:05:46.691)
(11:05:46.691) OK
(11:05:46.783) 0123456789
(11:05:46.946)
(11:05:46.946) busy s…
(11:05:46.946)
(11:05:46.946) Recv 10 bytes
(11:05:46.946)
(11:05:46.946) 0,18,SEND OK
(11:05:47.787) AT+CIPSENDBUF=0,10
(11:05:47.882) AT+CIPSENDBUF=0,10
(11:05:47.882) 19,18
(11:05:47.882)
(11:05:47.882) OK
(11:05:47.882) >
(11:05:48.055) 0123456789
(11:05:48.220)
(11:05:48.220) busy s…
(11:05:48.220)
(11:05:48.220) Recv 10 bytes
(11:05:48.220)
(11:05:48.220) 0,19,SEND OK
(11:05:49.267) AT+CIPSENDBUF=0,10
(11:05:49.407) AT+CIPSENDBUF=0,10
(11:05:49.407) 20,19
(11:05:49.407)
(11:05:49.407) OK
(11:05:49.407) >
(11:05:49.537) 0123456789
(11:05:49.705)
(11:05:49.705) busy s…
(11:05:49.705)
(11:05:49.705) Recv 10 bytes
(11:05:49.705)
(11:05:49.705) 0,20,SEND OK
(11:05:50.995) AT+CIPSENDBUF=0,10
(11:05:51.133) AT+CIPSENDBUF=0,10
(11:05:51.133) 21,20
(11:05:51.133)
(11:05:51.133) OK
(11:05:51.133) >
(11:05:51.292) 0123456789
(11:05:51.456)
(11:05:51.456) busy s…
(11:05:51.456)
(11:05:51.456) Recv 10 bytes
(11:05:51.456)
(11:05:51.456) 0,21,SEND OK
And the time stamped messages when they arrived:
As you can see, the delay is still there in some of the messages. even without an MCU.
Hello,
What bothers me is that you are getting “busy s…” message every time. It might be caused by CR LF settings in your terminal. Please check if possible.
Hello,
I’m not quite sure what you mean by that, but my text settings for YAT is this:
I don’t see how this would cause that.
Hi,
You have set for Tx EOL sequence.
When sending command through YAT, if you have another \r\n at the end, this could cause getting “busy s…” messages. But that wouldn’t be the cause of delay, in my opinion.
Have you tried using other CIPSEND commands?
Hello,
I did try the other CIPSEND commands, but CIPSENDEX isn’t good since some of the messages we need to send contains \0 NULL characters, and normal CIPSEND command isn’t good since I have to wait for SEND OK before I can send the next message, so if I have to send more messages in quick succession after each other I won’t be able to do it and I am unable to store the messages to send them later.
Hello,
Is there any news regarding this problem?
The best service provider which is roadrunner email support it provides 24*7 support service regarding roadrunner email customer service.
Hello,
I guess there is still no answer?
