David Smart
MODIFIED from mbed official WiflyInterface (interface for Roving Networks Wifly modules). Numerous performance and reliability improvements (see the detailed documentation). Also, tracking changes in mbed official version to retain functional parity.
Dependents: Smart-WiFly-WebServer PUB_WiflyInterface_Demo
Fork of
WiflyInterface
by 
mbed official
You are viewing an older revision! See the latest version
Homepage
Robustness testing¶
I've had some mixed behavior with the Wifly module, some of which seems to be traceable to the module itself, and some in my derivative code. The result, after running for minutes, hours, sometimes days, it hangs and I have to reset the module.
To test, I created a fairly simple test program -
- check for Watchdog induced reset and count it.
- initialize the Watchdog for 60 sec timeout.
- Init the Wifly interface and connect to my network.
- Wait 10 seconds and force mbed_reset().
If the Watchdog induces the restart, then it is pretty clear that either:
- The communications hung with the Wifly module causing the failure.
- The Wifly module decided to go unresponsive.
But I can't really pin down which easily. One of the objectives for my revised send( ) is to avoid the c++ string, as that can fragment memory, and it wasn't very well bounded in behavior.
Latest tests:
| Warm Boots | Watchdog Events | Notes |
| 100's | 30 | My derivative WiflyInterface, including my derivative of "send( )" API. Let's call this version 0.1. |
| 2668 | 4 | My derivative WiflyInterface, but with the mbed official "send( )" API. Much improved. |
| 1200 and counting | 0 | version 0.1 of "send( )", but this relative number does not rule out the Wifly module itself. |