• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 56 subscribers
  • Views 645 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

RTOS/CC1310: Orphan scan not working with custom designed cc1310 boards

Gaurav Sharma23
Intellectual 880 points
Part Number: CC1310

Tool/software: TI-RTOS

Hi,

I have been working on making orphan scan work on my custom designed cc1310 board acting as a sensor and a launchpad as a collector. There is a good difference in. the RSSI levels of my custom designed board and the launchpad but somehow they are working with each other. Sensor sending to collector and vice-versa. Although when I remove the collector and the sensor tries to send orphan scan request, it just does not get re-associated with the collector. The same firmware has been tested with a launchpad[sensor] and other launchpad[collector]. Does it have to do anything with the RX sensitivity of my custom designed boards? If an active scan is working fine then how come an orphan scan be any different? Any inputs in this regard will be appreciated.

Thanks & Regards

  • 0
    TI__Genius 12415 points
    Have you tried using a packet sniffer to see where exactly in the rejoining process this problem is happening?
    Also, by default the sensor project is set up to do an orphan scan every 5 minutes so if you are testing orphan scans make sure you modify CONFIG_ORPHAN_BACKOFF_INTERVAL so the scans happen more often
  • 0 in reply to Hector_r
    Intellectual 880 points
    1.I have modified the CONFIG_ORPHAN_BACKOFF_INTERVAL to 6 seconds for testing and its working fine with the launchpads.
    2. Yes I tried sniffing the packets and I can observe from the logs that the sniffer is receiving a bad FCS at orphan notification. Malformed packets -- 32 bit FCS:0xe935cd2c (Incorrect, expected FCS=0x182d88cf). I think the transmitter is not able to send the orphan notification currently. The reason is unknown to me right now. Any inputs on this?

    Regards
  • 0 in reply to Gaurav Sharma23
    TI__Genius 12415 points
    Not sure why this is happening but it could be your HF crystal in your board
  • 0 in reply to Hector_r
    Prodigy 190 points

    Dear Hector,
    I'm facing the same problems as described in second Guarav post (Orphan notification, Bad FCS) every 5 minutes (according to default CONFIG_ORPHAN_BACKOFF_INTERVAL). When I reset the device manually it reconnects to collector without problems.
    I have to add that these are also custom boards but were working flawlessly with SDK 2.20, problems are with SDK in version 2.40. Changing join permit isn't changing anything.
    The software is based on almost clear Sensor example - my application don't change anything in standard stack behaviour.

    Did you encounter similiar problems?

    Regards,
    Pawel

  • 0 in reply to ppielorz
    TI__Mastermind 23556 points

    Hello,

    Hector is out for now, but I will be helping you with this issue. 

    Can you please recreate this problem using the out of box sensor example on a launchpad and sniff the packets?

    This will help us greatly in solving your problem.

    Regards,

    AB