CC1352P7: PAN Advertising Solicit- Wi SUN node

Someone will be assigned to look into this. In the meantime, please provide information regarding what SDK version you are using.

BR

Siri

I am using SDK 13xx (newest) one

Hi,

After the router node sends the PAN Advert solicit, the next step is for the BR or any other router in the network to send a PAN Advert. You can see the full flow diagram in the User's Guide:

https://dev.ti.com/tirex/explore/content/simplelink_cc13xx_cc26xx_sdk_5_30_01_01/docs/ti_wisunfan/html/wisun-stack/MAC.html#join-process

If the BR does not reply with a PAN advertisement, it sounds like it might not have received the PAN Advert Solicit. Can you check that all parameters are the same on your two devices:

- Wi-SUN Mode

- Frequency band

- Channel map

Cheers,

Marie H

Hi Marie,

Thank you. I do the test again, but It looks like it just only not works with regulatory domain EU. Idk Does it have any restriction on EU domain from TI?

Hi,

All modes you can find in SysConfig are tested and certified.

Did you remember to change the mode on the BR side as well?

Cheers,

Marie H

Hi,

Yup, Both config on Node side and Border Router side matched. Another domain such as NA or JP works so far, just exception on EU domain.

Hi,

I don't have a Silicon Labs BR so I'm not able to test on my side.

As previously stated all our PHYs are certified with the Wi-SUN Alliance and so there should be no issue on the PHY level.

In addition our stack is certified with the Wi-SUN alliance so there should be no issue in the stack level.

Not sure if there any any application level configurations that could explain the issue you are seeing?

Cheers,

Marie H

Hi Marie,

I just found out that with the packet PAN Advertisement Solicit send from CC1352P7 with EU domain (Here I tested again at Mode 1b-class 3 or even mode 2a-2 EU), Channel Control gives weird information. I think It suppose to show the information about Regulatory Domain and Operating Class which here is European.

Part Number: CC1352P7

Hi

Hi I would ask about the setting on "channel plan and excluded channels" of WI-SUN mode. It has differentiated on the bit used in  WI SUN mode 1a and 1b. Could I modify it?

Hi GP,

Please can you elaborate on what exactly you want to modify? Maybe a screenshot if it is sysconfig? 

Regards,

Sid

Hi,

I have seen the difference in setting bit of the channel plan and excluded channels. As the screenshot below, the left one I used mode 2a-2, the right one is mode 1b-1. Which is mode 1b-1 give information base on the SUN PHY profile (regulatory domain, operating class). 

So, Could I modify those bits on mode 2a/1a/3 to have the same behavior with mode 1b/2b?

any solution from TI side?

Not yet, but you can change SL device to use explicit channel plan. The problem I found that TI mode 1a-1 has a bug in channel spacing, so you can use mode 2a-2 or 3-2 instead. However, TI node takes around 15-20 minutes to join the network and suddenly disassociation after a while. So the link is not reliable.

Hi Bijendra,

Since we don't have a BR from Silicon Labs we haven't been able to reproduce the issue GP is seeing. Without reproducing here it's difficult to find the root cause of their issue. (Testing with BR from TI there is no issue.)

Are you also working with a BR from Silicon Labs or are you seeing a slightly different issue?

Cheers,

Marie H

Hi GP,

I am able to reproduce what you are seeing in the PAS packet for PHY mode 3 (AKA operating mode #2a.) I have filed a ticket with the SW team.

However I'm not sure whether this is actually causing your IOP issue.

Cheers,

Marie H

Hi Marie,

Thanks for your help, I just noted that mode 1a-1 has a bug with channel spacing and my interoperability test already works in mode 2a-2 even it is not stable. But in TI side, it would be really help if you can show me how to change the bit on channel plan and excluded channel.

Hi,

Thanks for letting me know. I already checked, they (Silicon Labs) also used 863.1 MHz for EU bands

Hi,

When you use channel plan = 1, the spec does not require (or allow) regulatory domain or operating class bits. Please see Technical Profile Specification
Field Area Network, section 6.3.2.3.2.1.4 Field Definitions. 

In order to help you solve your IOP issue: Can you post a sniffer log of the peer device packets:

- The failed process

- PA packets from the peer device.

Cheers,

Marie H

Thanks, yup I understand if channel = 1 then we do not need a regulatory domain and operating class. Therefore, I ask you if you can provide me the method to change the channel plan to 0.

I do not know that the difference in channel plan is the reason for my issue or not. But, If I change "channel plan" on vendor's device to 1, all device makes the connection. However, the connection time takes too long (around 15' minutes) and disassociate after a while.

I attached 2 sniffer logs as below:

GAK: 0e:e4:2b:31:31:dd:e5:b2:c1:00:00:1a:c2:7a:c0:f1

The failed process mode 2a-2 SDK 5.40 

 INTERO-BR489-R48F-R6742.zip

The success process in which to change the channel plan on the Border router of the provider to 1. But there is still problem as mentioned above.

15-3-INTERO-TI 5.zip

Hi,

I think channel plan = 1 is for the EU domain, for the NA domain channel plan is 0 and 1 both support. And the channel plan ID in Sysconfig only had to do with changing the number of channels and the center frequency, channel spacing required by the user. So in this case it doesn't help interoperability with other vendors while they're setting the channel plan to 0. So, I think it's clear if 2 devices using a different channel plan they can't pair.

Hi,

Thank you, So, It means that the TI device cannot pair with other vendor from the differences on channel plan (1 or 0)

Hi,

If you specify the following we can look into adding support for additional Chanel Plan ID:

- Channel Plan ID

- Channel 0 frequency

- Number of channels

- PHY

Cheers,

Marie H

Hello,

I believe even you support for Extra Channel Plan ID, but keep setting in Channel Plan = 1 by using "explicit spacing and number" for EU domain. This interoperability is still the same situation, I explained above. If you take a look at 2 sniffers I attached above.

Hi,

I don't understand how what you're saying relates to what I'm seeing in Sysconfig. If I choose EU band, I can only choose channel plan ID 32, 34 or 36. Or did I misunderstand?

Cheers,

Marie H

Hi,

I mean the channel plan not channel plan ID in sysconfig.

With an EU domain, TI channel plan is set to 1 and this is one of the reasons the TI device cannot pair with other device while their channel plan is 0. My question is there any way to change the channel plan to 0.

However, with NA domain, TI channel plan is set to 0

Hi GP,

We have discovered that there is indeed an issue with our EU band channel configuration and this is why you are seeing IOP issues.

Unfortunately there is no way for you adjust the relevant settings since they are set in a library.

Cheers,

Marie H