Some courses and learning paths on NI Learning Center may not appear on learner dashboards. Our team is actively investigating.

If you encounter access issues, please contact services@ni.com and include the learner’s name, email, service ID or EA number, and the list of required courses.

Home Support Documentation Bugs

Archived: NI Bluetooth 1.1 Toolkit Known Issues

Updated Sep 9, 2025

NI does not actively maintain this document.

This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.

Overview



NI Bluetooth Toolkit Known Issues

Each issue appears as a row in the table and includes the following fields:

  • Issue ID - The number in at the top of each of the cells in the first column. When you report an issue to NI, you may be given this ID, you can also find IDs posted by NI on the discussion forums or in Knowledge Base articles.  "N/A" indicates that there is no ID assigned to the issue.
  • Issue Title (in italics) - Describes the issue in one sentence or less.
  • Problem Description - A few sentences which describe the problem in further detail. The brief description given does not necessarily describe the problem in full detail, and it is expected that you may want more information on an issue. If you would like more information on an issue, contact NI and reference the ID number given in the document.
  • Workaround - Possible ways to work around the problem. The workarounds that appear in the document are not always tested by NI and are not guaranteed to resolve the issue. If a workaround refers you to the NI KnowledgeBase, visit www.ni.com/kb/ and enter the KnowledgeBase number in the search field to locate the specific document.
  • Reported Version - The earliest version of NI-RFSG in which the issue was reported. If you discover the issue appears in an earlier version of NI-RFSG than is reported in this field, report the discrepancy to NI to have the field updated.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).

Known Issues by Severity

365093—BER results may be incorrect if you do not restrict the number of unique packets
309253—Gaussian RBW filter type does not give expected results for DF2 measurements.
300396—DEVM measurements in loop back gradually degrade and fail as the payload length on generator is reduced from maximum to 1 (for all supported packet types)
299800—EV3 packet type is not supported for any modulation type
368856—DF1 and DF2 measurements for FEC-encoded packets are incorrect when the packet length offset field is not zero
369733—The toolkit cannot measure LE CFO and LE transmit power if you set the payload length less than the maximum payload length on the generator



IDKnown Issue
365093

While using the SFP or CVI, BER results may be incorrect if you do not restrict the number of unique packets


Workaround: Restrict the number of unique packets to a multiple of c*p, where c is the number of consecutive packets per impairment set, and p is the number of impairment sets.

Reported Version: 1.1  Resolved Version: N/A  Added: 10/31/2012
309253

Gaussian RBW filter type does not give expected results for DF2 measurements.

If you set the RBW filter type to Gaussian, the DF2 measurement values are low.

Workaround: None

Reported Version: 1.1  Resolved Version: N/A  Added: 10/31/2012
300396

DEVM measurements in loop back gradually degrade and fail as the payload length on generator is reduced from maximum to 1 (for all supported packet types)

DEVM measurements in loop back give an expected result only when generated for the maximum packet payload length. The measurements gradually degrade and fail as the packet length is decreased.

Workaround: None

Reported Version: 1.1  Resolved Version: N/A  Added: 10/31/2012
299800

EV3 packet type is not supported for any modulation type

The toolkit does not support the EV3 packet type for any modulation type.

Workaround: None

Reported Version: 1.1  Resolved Version: N/A  Added: 10/31/2012
368856

DF1 and DF2 measurements for FEC-encoded packets are incorrect when the packet length offset field is not zero

DF1 and DF2 measurements for DM1, DM3, and DM5 packets are incorrect when the packet length offset field is not zero.

Workaround: None

Reported Version: 1.1  Resolved Version: N/A  Added: 10/31/2012
369733

The toolkit cannot measure LE CFO and LE transmit power if you set the payload length less than the maximum payload length on the generator

The toolkit cannot measure LE CFO and LE transmit power if you set the payload length less than the maximum payload length on the generator.

Workaround: None

Reported Version: 1.1  Resolved Version: N/A  Added: 10/31/2012

Contacting NI

Contact NI regarding this document or issues in the document. If you contact NI in regards to a specific issue, reference the ID number given in the document. The ID number contains the current issue ID number as well as the legacy ID number (use the current ID number when contacting NI). You can contact us through any of the normal support channels including phone, email, or the discussion forums. Also contact us if you find a workaround for an issue that is not listed in the document.

Back to top

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).