# Call to mmwlan\_scan\_abort() works, but prints error on 2.7.2

**URL:** <https://community.morsemicro.com/t/call-to-mmwlan-scan-abort-works-but-prints-error-on-2-7-2/643>\
**Category:** Software\
**Created:** [June 18, 2025, 8:22pm UTC](https://community.morsemicro.com/t/call-to-mmwlan-scan-abort-works-but-prints-error-on-2-7-2/643 "2025-06-18T20:22:24Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Straff](https://avatars.discourse-cdn.com/v4/letter/s/58f4c7/32.png) [@Straff](https://community.morsemicro.com/u/Straff)\
**Post date:** [June 18, 2025, 8:22pm UTC](https://community.morsemicro.com/t/call-to-mmwlan-scan-abort-works-but-prints-error-on-2-7-2/643/1 "2025-06-18T20:22:24Z")

</div>

In 2.5.2, the call to mmwlan\_scan\_abort() did not cause an error.  
in 2.7.2 we get:  
E 11597 Command 44:120 failed with rc -114 (0xffffff8e)  
E 11598 Failed to execute HW\_SCAN command

Why do we call mmwlan\_scan\_abort() after the scan is complete?  
If we don’t call it, all works well, but it takes a long time for us to bring the link up.  
When we call mmwlan\_scan\_abort(), the link comes up much faster (20 or so seconds faster).  
And as I said above, in 2.5.2 there was no error, now we get an error.  
However, aside from the print out of the error, everything works fine.

So the question is: am I using mmwlan\_scan\_abort() correctly and I can ignore the error?  
I assume so.

Thanks

=================  
More detail:

1. The scan completes  
\* we know the SSID of the AP  
\* and the scan\_complete\_callback() has been called.

2. Then we call mmwlan\_scan\_abort()  
and on 2.7.2, we get the error:  
E 11597 Command 44:120 failed with rc -114 (0xffffff8e)  
E 11598 Failed to execute HW\_SCAN command

---

<div class="post-metadata">

**Author:** ![cmistry](https://avatars.discourse-cdn.com/v4/letter/c/ccd318/32.png) [@cmistry](https://community.morsemicro.com/u/cmistry)\
**Post date:** [June 20, 2025, 1:37am UTC](https://community.morsemicro.com/t/call-to-mmwlan-scan-abort-works-but-prints-error-on-2-7-2/643/2 "2025-06-20T01:37:17Z")

</div>

Hi @Straff , we just released [version 2.8.2](https://github.com/MorseMicro/mm-iot-sdk/releases/tag/2.8.2) if you would like to try that instead

---

<div class="post-metadata">

**Author:** ![Straff](https://avatars.discourse-cdn.com/v4/letter/s/58f4c7/32.png) [@Straff](https://community.morsemicro.com/u/Straff)\
**Post date:** [August 1, 2025, 6:44pm UTC](https://community.morsemicro.com/t/call-to-mmwlan-scan-abort-works-but-prints-error-on-2-7-2/643/3 "2025-08-01T18:44:38Z")

</div>

```auto
/*   
 * We can no longer abort the scan
 *
 * In 2.7.2 
 * we get errors if we call mmwlan_scan_abort();
 * E 11597 Command 44:120 failed with rc -114 (0xffffff8e)
 * E 11598 Failed to execute HW_SCAN command
 *
 * In 2.8.2
 * If we call mmwlan_scan_abort();
 * We no longer get any errors
 * However, if we can this function
 * Association fails
 * power off of MorseMicro chip causes the system to reboot.
 */
// mmwlan_scan_abort();

```

Note: fi we don’t call the mmlan\_scan\_abort(), we can associate, send data, go into WNM sleep, and power off the MorseMicro chip.

---

<div class="post-metadata">

**Author:** ![ajudge](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@ajudge](https://community.morsemicro.com/u/ajudge)\
**Post date:** [August 6, 2025, 3:29am UTC](https://community.morsemicro.com/t/call-to-mmwlan-scan-abort-works-but-prints-error-on-2-7-2/643/4 "2025-08-06T03:29:57Z")

</div>

Hi @Straff

We tried this with one of our example applications in 2.8.2 and did not see the association fail. We’ll continue trying to reproduce it, but if you have code you can share that would be helpful.

Regarding the reboot, that sounds like the system might be faulting? Is it hitting a fault handler?