• State
  • Locked Locked
  • Replies 13 replies
  • Subscribers 41 subscribers
  • Views 612 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.

CC3235MODAS: Regarding connection between CC3235MODAS and Intel AX211

Take
Prodigy 10 points
Part Number: CC3235MODAS
Other Parts Discussed in Thread: CC3235S, SIMPLELINK-WIFI-DESIGN-REVIEWS

Because it was translated from Japanese to English using Google Translate, there may be some nuances that may not be conveyed well.


I am having trouble connecting a device using CC3235MODAS (hereinafter referred to as CC3235) and a Surface Pro 9 using Intel AX211 (hereinafter referred to as AX211).

There is no problem if the CC3235 and AX211 are placed close together, but if you move them apart, the connection will be broken or the SSID will not be visible on some CC3235s.

Of the recently manufactured devices, 7 out of 48 have connection problems.

It's the same even if you change Surface.

There is no problem if you connect CC3235, which cannot be connected to AX211, to another PC (using Intel AX203, AC3165, AC8265).
I have the same problem on another PC (DELL Latitude 5540) with AX211.

a) Problem only with AX211
b) Problem only with CC3235
c) Problems with the combination of AX211 and CC3235


I think it's one of the above problems, but if it's just a problem with AX211, I think there might be some discussion on the internet about connection problems with Wi-Fi modules other than CC3235, but I can't find any.


Please let me know if you know the reason or solution.

  • 0
    TI__Guru 63006 points

    We'll need to get more information about the connection issue.

    Is CC3235 the station or the AP (or is it a P2P issues)?

    What is the error code you are getting?

    We will also need to see an air (802.11) sniffer and/or NWP log (see chapter 20 in https://www.ti.com/lit/pdf/swru455) to better understand the root cause. 

  • 0 in reply to Kobi Leibovitch
    Prodigy 10 points

    Thank you for your reply.

    > Is CC3235 the station or the AP (or is it a P2P issues)?

    It's AP.


    > What is the error code you are getting?

    Is the error a SimpleLink API error?
    If so, there is no error.


    > We will also need to see an air (802.11) sniffer and/or NWP log (see chapter 20 in www.ti.com/.../swru455) to better understand the root cause.

    The logs obtained with AirPcap+Wireshark are shown below.

    This is the log when you cannot connect even if the SSID is visible.
    AX211 is not receiving ACK (802.11) from CC3235 for "Authentication" from AX211. Also, I know that AX211 is not receiving "Authentication" from CC3235 (there is no ACK (802.11) from AX211).

    Looking at this, it may be that the transmitting power of CC3235 is low or the receiving performance of AX211 is poor, but
    - There is also another CC3235 that can be connected without any problem even if you use the same AX211.
    - CC3235, which causes problems, can be connected to AX211 when it is a few cm away, but cannot be connected when it is 1m away. Also, the CC3235 SSID will no longer be displayed in the AP list on AX211 (Windows).
    - CC3235, which causes not problems, can be connected up to approximately 35m away without any problems.


    I will try to obtain the NWP log from now on.

  • 0 in reply to Take
    TI__Guru 63006 points

    Looks like some kind of RX sensibility issue though 1m is very close and this doesn't make sense.

    Are you using the TI reference Launchpad or a customized board?

  • 0 in reply to Kobi Leibovitch
    Prodigy 10 points

    > Are you using the TI reference Launchpad or a customized board?

    I am using a customized board.

  • 0 in reply to Take
    TI__Guru 63006 points

    Please make sure that you go through the hardware design review (https://www.ti.com/tool/SIMPLELINK-WIFI-DESIGN-REVIEWS).

  • 0 in reply to Kobi Leibovitch
    Prodigy 10 points

    Thank you for your advice.
    The circuit design team performed a review based on SIMPLELINK-WIFI-DESIGN-REVIEWS ("CC3235MODx & CC3235MODAx" sheet) and found no problems.

  • 0 in reply to Take
    TI__Guru 63006 points

    Strange. Please send the full sniffer log and NWP log and i'll try to check if there is something else but this seems like a hardware issue.

  • 0 in reply to Kobi Leibovitch
    Prodigy 10 points

    Thank you for your reply.

    I'm trying to get a sniffer log at the same time as getting the NWP log in the anechoic chamber, but I haven't been able to do it yet.
    We apologize for the inconvenience, but please wait for a while.

    A strange phenomenon has been confirmed.
    In some cases, it was better to connect the Surface and CC3235 by moving them further apart than by bringing them within 3 meters. (I tried 5m and 20m)

  • 0 in reply to Take
    TI__Guru 63006 points

    again, all the RF issues you are reporting would probably mean that the logs will not be helpful. It is possible that the Surface's transmit power is too high. The sniffer log in case of RF issue will show retransmissions (i.e. packets without ack) and the NWP log will not show anything unless there is a protocol issue during the connection.

  • 0 in reply to Kobi Leibovitch
    Prodigy 10 points

    I suspect that the issue is not with the Surface's transmission, but with its reception.
    Or I suspect there is a problem with the CC3235 transmission.

    I only have data from packet captures when trying to connect from Surface to CC3235 and failing. (Sorry. I didn't show it because I thought it would be better to include it with the NWP log)
    Looking at this, you can see that the Surface is not receiving packets.

  • 0 in reply to Take
    TI__Mastermind 46045 points

    Hi Take,

    Do you have a spectrum analyzer by chance?

  • 0 in reply to Dylan Hubbard
    Prodigy 10 points

    Very sorry.

    I may have chosen "Reported as abusive" for my reply.

    Is it possible to correct it?

  • 0 in reply to Dylan Hubbard
    Prodigy 10 points

    From now on, I would like to entrust the handling to our electrical circuit design members. (I'm a software developer)

    I will become an observer for now.
    Thank you for what you have done.