• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 42 subscribers
  • Views 601 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.

CC3100: CC3100

eli
Guru 13485 points
Part Number: CC3100

 Got below  issue:

we designed  IoT Camera which transmit images to a Gateway computer over WiFi,  we used IMx 6 as a CPU and C3100 as WiFi component. The operation method is - The camera is in power off most of the time and wake up to take a picture and transmit it to a Gateway computer which is on the same WiFi network.

 

We tested the design and it seem to work OK on TP-Link routers and on Cisco routers.

 

We installed the camera on the customer site which using HP AP-425 connected to HP2920 switches running in L2 (no routing) and we experience a lot of communication problems which causing failures in transmitting the images to the gateway computer.

 

After making some tests we understood that even a simple PING from the Gateway computer to the camera takes between 70,00~100,000 ms !!!??

 

Another important note is that if we take a WiFi extender and use it as a buffer between the camera and the HP AP we get good communication (ping less than 10 ms) and all the images transmitted to the Gateway computer with no issues,  so we believe this  could be an issue between the C3100 and the HP AP or Switch.

 NEED URGENT HELP

  • 0
    Guru 79905 points
    Hi,

    As first thing please try this:
    - update CC3100 to Latest Service pack (if you already not have it)
    - try set power policy to SL_ALWAYS_ON_POLICY

    Jan
  • 0 in reply to Jan D
    Guru 13485 points

    Hi

    Thanks.

    The installation is in England.they made the update according to your recommendation and will send dedicated engineer to check it.

    Will have answer/feedback,by this afternoon

    Since it urgent and high costly  procedure,please advise for additional solution you think of 

  • 0 in reply to eli
    Guru 79905 points
    Hi,

    Many additional thing can be also investigated, but I am not sure if this can be done at end user side. I think best way will be borrow problematic AP from end customer and simulate problem at your office. Also will be good to know exact firmware number inside problematic AP. Maybe TI guys will be able check interoperability with this particular AP.

    Few other points:
    - capture NWP log processors.wiki.ti.com/.../CC3100_&_CC3200_Capture_NWP_Logs
    - capture WiFi communication by wireless sniffer
    - capture network communication by Wireshark software

    Jan
  • 0 in reply to Jan D
    TI__Mastermind 28285 points
    Eli,

    I agree with the debugging steps Jan recommended. We can take a look at the sniffer captures to help narrow down the culprit for the problem.

    VR
  • 0 in reply to Vincent Rodriguez
    Guru 13485 points

    Hi

    I am happy to say that we solved the issue, it was the SL_ALWAYS_ON_POLICY .

    Could you please share what is the use of this mode and how it will affect our power consumption (we are using batteries)

     

  • 0 in reply to eli
    Guru 39650 points

    Hi,

    Detail information can provide you TI guys.

    ALWAYS_ON_POLICY significantly increase power consumption. But I don't know how much will be consumption increased.

    To decrease power consumption it is used "trick" with DTIM. This allows wifi client goes to sleep and this save power. In ALWAYS_ON_POLICY is CC3100 always on and this decrease latency and improve network performance.
    But there can be problem with SL_NORMAL_POLICY (default) or SL_LONG_SLEEP_INTERVAL_POLICY and APs which not properly follow standards. This is a probably problem of your customer.

    Jan