Archived: NI-FBUS 4.0.1 Known Issues

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.

Aperçu

This document has been archived and is no longer updated by National Instruments.

This document contains the NI-FBUS 4.0.1 known issues that were discovered before and since the release of NI-FBUS 4.0.1. Not every issue known to NI will appear on this list. It is intended to only show the severe and more common issues that can be encountered.

Fields

Each known issue includes these fields:

  • Issue ID - The issue ID from NI's deprecated bug reporting database (if applicable)
  • Issue Title
  • Problem Description
  • Workaround
  • Reported Version - the earliest version of NI-FBUS the issue was reported in
  • Resolved Version - version the issue was resolved or was no longer applicable
  • Version Added - the version of NI-FBUS the issue was added to the document (not reported date)

Contacting NI

Feel free to contact NI regarding this document or issues in the document. If you are contacting NI in regards to a specific issue, be sure to reference the ID number given in the document to the NI representative. The ID number contains the current issue ID number as well as the legacy ID number (use the current ID number when contacting National Instruments). You can contact us through any of the normal support channels including phone, email, or the discussion forums. Visit the NI Website to contact us. Also consider contacting us if you find a workaround for an issue that is not listed in the document so that we can add the workaround to the document.

Known Issues by Date

The following items are known issues in NI-FBUS 4.0.1 sorted by Date.

219594 — Only one USB-8486 is left in Configurator when the system with mulitple USB-8486 connected is recovered from hibernation (Windows Vista or above).
171893 — NI-FBUS 4.0.1 does not support dynamic display image feature in EDDL.
89744 — Communications Manager can not initialize the HSE/H1 linking device if one of the link IDs is equal to or greater than 0xF0FF.

 

Issue ID Known Issue
219594

Issue - Only one USB-8486 is left in Configurator when the system with mulitple USB-8486 connected is recovered from hibernation (Windows Vista or above)


Description - When the system with mulitple USB-8486 connected is recovered from hibernation, the log in Communications Manager shows that all the interfaces are reinitialized automatically. But when you use Take Online in Configurator, only one USB-8486 is left in the list. This issue only occurs on Windows Vista or above system.


Workaround - Restart Communications Manager and Configurator after the system is recovered from hibernation.

Reported Version - 4.0.1      Resolved Version - Unspecified

Version Added - 4.0.1

171893

Issue - NI-FBUS 4.0.1 does not support dynamic display image feature in EDDL


Description - The dynamic attribute of the image in EDDL is not supported. Configurator shows these images statically.


Workaround - N/A

Reported Version - 4.0      Resolved Version - Unspecified

Version Added - 4.0.1

89744

Issue - Communications Manager can not initialize the HSE/H1 linking device if one of the link IDs is equal to or greater than 0xF0FF


Description - If one of the link IDs on the HSE/H1 linking device is equal to or greater than 0xF0FF, Communications Manager can not start successfully. Error occurs when initializing the HSE/H1 linking device.


Workaround - Use the default ID. Do not set the ID to the value which is equal to or greater than 0xF0FF.

Reported Version - 3.2      Resolved Version - Unspecified

Version Added - 4.0.1

 

Document last updated on 7/6/2010

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).