• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 54 subscribers
  • Views 647 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: ETSI and FCC conformity

Slev1n
Genius 5680 points
Part Number: CC1310

Tool/software: TI-RTOS

Hey guys,

we are using the 15.4 Stack and sensor collector example as base. Currently, we are using the 863MHz ETSI standard, thus we are allowed to occupy this frequency band for 3.6s/hour/device. We are evaluating to send big data messages (up to 1000bytes). We fill an array and if this array is full we immediately send it. If the array is not full until the reporting interval is reached, it is still send, but is smaller.

I was wondering what happens if the 3.6s are reached?

And how is the chip verifying that his limit is not exceeded? Does it check the occupancy of the band of one device between lets say 4a.m. and 5a.m. or is it continuously checking the occupancy?

I hope you can help me understand how the chip/software works regarding this occupancy issue.

kind regards

Slev1n

  • 0
    TI__Genius 12415 points
    Hi Slev1n,

    our software protocol stacks only ensure that they are compliant with the protocol specification they are based on. Therefore certifications such as FCC, ETSI, and others are up to the developer writing the application to follow.

    This being said, neither the chip nor the stack can verify if your application is ETSI compliant. You need to make sure that your device is following the ETSI guidelines before you submit your device for ETSI certification.

    Also if you are only sending 1KB/hour/device then you shouldn't have a problem with meeting the requirements of 3.6s, but still you should make sure this is the case when you submit your devices for testing.
  • 0 in reply to Hector_r
    Genius 5680 points

    Thank you for the answer Hector.

    Than I will make sure, that the device will not exceed the 3.6s.

    Since we are planning to implement the OAD feature, is the basic OAD example provided by TI complying with the guidelines?

  • 0 in reply to Slev1n
    TI__Genius 12415 points
    No, the OAD feature does not follow this 3.6 second requirement. To comply with the 3.6s there are 2 things that you can modify in the OAD feature which are OAD_BLOCK_SIZE (defines the number of bytes of the new image that will be sent in 1 OAD block) and OAD_BLOCK_REQ_RATE (number of milliseconds that the sensor device will wait to request another block of OAD data )

    Also, note that the time that a device will occupy the frequency band also depends on the data rate that you are using
  • 0 in reply to Hector_r
    Genius 5680 points

    Ok, this issue will be easy to estimate if everything works finde, but if for example a collector is not acknowledging a message and the sensor retries 3 more times, I guess I have to take this into account, too. And also ACK messages will occupy the band, so one should estimate the payload over one hour very conservatively.

    In the case of OAD I guess the main sending part is done by the collector, so the collector will be an issue, too.

    But I can rely on the standard byte rate of 50kbps right? And 14dBm signal strength or below is allowed in both ETSI and FCC, right?

  • 0 in reply to Slev1n
    TI__Guru**** 317180 points
    Bitrate is not part of ETSI/ FCC but output power and power density is. Have you download the ETSI and FCC parts you want to comply with and read at least through the headlines to get an overview of what the device has to comply to?

    Our launchpads have all been ETSI qualified since this is required to sell them within EU.
  • 0 in reply to TER
    Genius 5680 points

    I know that the bitrate is not part of ETSI, but if I know that the bitrate is constantly as high as 50kbits than I can calculate the density from the amount of bytes I send. I read a little bit about the ETSI and FCC regulations. In ETSI mode we use the 863MHz band and I know that the density is 0.1% per hour = 3.6s and the maximum strength is 25mW = 14dBm ERP. For FCC i noticed that only the used frequency is important though regarding the power I didnt find the exact value for the 915MHz band but I assume that again, the basic settings allowed in config.c of sensor/collector example are in the allowed range.

    So if I know that I can rely on the transmission rate I can apply the correct settings for my data array transmissions and my OAD application.

  • 0 in reply to Slev1n
    TI__Guru**** 317180 points
    For FCC, the max power is dependent of if you are targeting 15.247 or 15.249.

    The bit rate will always be the rate of the selected phy (If you select 50 kbps, you will always have 50 kbps rate)