RTOS / CC1310：Ti 15.4 stack solitary node problem?

I am a bit confused here, What exactly is the issue you are experiencing?

In sensor and collector communication, collector power off. Sensor receives callbacks
pData->status==E8


if(((pData->scanType == ApiMac_scantype_orphan) && (pData->status
== ApiMac_status_noBeacon))){

}

After the connection, the power cut callback is EA

After the data, the power cut callback is E8

Should there be a problem?

/*! The API function parameter is out of range */
ApiMac_status_invalidParameter = 0xE8,

Why is this out of range?

How to Find the Reasons for the Wrong Callback Status?

Could you share a little bit more details of how this is happening?
Are you seeing this callback status with the default out of the box examples or have you done any modifications?

As the name of the error code implies, this error code will be received if the API(in this case scan request API) was called with an invalid parameter.

For example if you call scan request with a PHY ID that is not valid then you will receive something like this.

I will try to reproduce this behavior and report back to you

#define CONFIG_PHY_ID (APIMAC_GENERIC_CHINA_433_PHY_128)

In normal data interaction, collector is suddenly powered off, sensor sends solitary node requests after three judgements, then enters the scan callback, and callback status is E8. There is no code change in this process. The sendorphan parameters are normal.

How does the callback of collector after power failure change?

What version of the SDK are you using?

simplelink_cc13x0_sdk_2_40_00_20

ok, I will run some tests and let you know if I can reproduce this behavior

Thank you for waiting for the good news.

Hi I tried to replicate your setup but I never get status 0xE8, I only get status 0xEA

I have not modified any code in the sensor or collector, The only thing that I changed was the PHY to APIMAC_GENERIC_CHINA_433_PHY_128

Then I pair the sensor with the collector
once they are paired, I turn off the collector.
This triggers the sensor to do an Orphan scan.
I check the status of all orphan scans and they all have status 0xEA

Are you sure you haven't made modifications to other parts of the code?

Hello, I test the connection and then power off. The result of this callback is correct.



When I cut off the power after sending the data, the above phenomena will occur.

My own cycle time for sending data is 15S

I cannot reproduce this on my side with the default examples.

Can you share a packet sniffer log so I can have a better idea of how and when exactly this is getting triggered

No feedback，Packet grabbing tool, did not grab the solitary node request package, but sensor sent

Okay, I'm debugging it myself. I'll give you feedback if there's a problem.

Another question for consultation.

In Features. h, I used FEATURE_ALL_MODES, and now there is a memory crisis, and I want to use the non-beacon mode, FEATURE_ALL_MODES instead of FEATURE_NON_BEACON_MODE, is that all right?

Yes you should be able to remove the features that you are not using and only leave the ones that you need