AsyncLabs Forums

[aerodyno]

That's cool that you found a fix!

Hopefully we can get a firmware update to fix this issue -- as it probably occurs in other settings as well. The firmware should be smart and ignore oversized packets (if that's the issue).

-s

[John_Ryan]

I had a strange thing happen today.

My WiShield red LED connection indicator suddenly started flashing on and off for absolutely no reason. Been running the same sketch for days, which is the same one I've been running for months for the yMicros example.

Anyone ever seen that happen before? I reset the board and its now back to normal.

[GregEigsti]

Never seen a flashing connection light; in my experience it is either on or off.

Greg

[John_Ryan]

Yes, same with my past experience also. The LED was tripping out at a steady frequency, maybe once every second. The boards hadn't been moved for months either, they've been parked on a glass top a couple of feet from a mac since I purchased them. It's permanently connected to the mac over usb for its juice and the computer never gets switch off. The room its in is air conditioned and dehumidified 24/7 so there are no wild fluctuations in temperature or condensation.

So I've eliminated the environment as a potential suspect. There are no wires or wiring to examine. And its only happened once so maybe it'll never happen again.

[GregEigsti]

Hmmmm. Memory corruption/leak slowly eating memory or randomly overwriting memory? Are you using WiServer? Are you using my WiServer "fix"? If using my "fix" it almost seems like the connection occurs, is lost and then the connection is reattempted (over and over and over...).

Greg

[John_Ryan]

Yes, using your fix but Id rather wait to see if it happens again before removing that.

[GregEigsti]

Not suggesting you remove it - specially if it helps
Just wondered - since the "fix" can reset the connection. Maybe you got into a state where, for whatever reason, a connection could not be kept for long and the "fix" then caused a reconnect. Would potentially explain the blinking connection LED as your code looped and the connection was lost, reinstated, lost, reinstated, etc...

Just need to figure out what that "state" was...
Greg

[John_Ryan]

For sure, I'd love to see it happen again to investigate it further but it's been sitting here for days behaving itself.

Maybe the LEDs a factory sweep and its failing after months of being on constantly. If it happens again I'll switch on the monitor and see what comes out. Last time I just switched it off then back on again without giving it too much thought. Then after a few minutes had passed I realized its significance doh!

[GregEigsti]

Make sure to get some logging in early! So its there when you really need it

BTW - the external antenna WS 2.0, placed in the problematic spot, is still connected! If I was just smart enough to have it output SNR (or equivalent) I'd really be on top of things

Greg

[GregEigsti]

I played with this a little bit tonight and it is definitely reproducible with a simple app (PC/etc.) that sends a broadcast UDP packet of around 1320 bytes; this will cause a board reset every time that the large broadcast packet is sent. It is only reproducible when running a WiServer based app; the TCP and UDP apps that I tried were all unaffected. Also learned that it does not matter what port the UDP broadcast is sent on.

Greg