LabVIEW Real-Time Idea Exchange

About LabVIEW Real-Time Idea Exchange

Have a LabVIEW Real-Time Idea?

  1. Does your idea apply to LabVIEW in general? Get the best feedback by posting it on the original LabVIEW Idea Exchange.
  2. Browse by label or search in the LabVIEW Real-Time Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  3. If your idea has not been submitted click New Idea to submit a product idea to the LabVIEW Real-Time Idea Exchange. Be sure to submit a separate post for each idea.
  4. Watch as the community gives your idea kudos and adds their input.
  5. As NI R&D considers the idea, they will change the idea status.
  6. Give kudos to other ideas that you would like to see in a future version of LabVIEW Real-Time!
Showing results for 
Search instead for 
Did you mean: 

Allow RT Scan Engine Fault Events to optionally include string data

I understand that the FE vi's needed to be optimized for speed so that they could be put inline without disturbing RT timing.  But it would be nice to be able to send a string description

with the fault so that it would show up in the DSM.  An example would be a fault due to trying to send an invalid remote message.  It would be nice if the invalid message string could be logged with the fault event.

I think making it optional would still preserve the determinism when needed.

  • Real-Time Execution & Performance
3 Comments
Member ScotSalmon
Member
Would it be okay if the string was a fixed (or at least known maximum) length?
Active Participant viScience
Active Participant
Sure that would be great, just so long as we can pass a reasonable description of the event.
Member jkurtw
Member

Just FYI, you can achieve similar functionality today by adding a custom error code file to the following directory:

C:\Program Files\National Instruments\Shared\Errors\English

 

In that text file you would define the text for your custom error codes. That text file then needs to reside in the above directory on the machine that has the system manager launched.