ni/niveristand-aim-milStd1553-custom-device

Issues

• Time Conversion Ignores Milliseconds

  #109 opened a year ago by KHsu2
  2

• How To Set Execution Time of Messages Within Minor Frame

  #107 opened a year ago by KHsu2
  2

• Scripting API for Ballard and AIM create naming conflict when used in the same project

  #101 opened 2 years ago by fmussi
  0

• Modify XSD to enable XML Serialization

  #103 opened 2 years ago by fmussi
  0

• Importing empty frames creates empty clusters of data that are compiled and passed around the custom device

  #62 opened 2 years ago by papowerNI
  0

• Example Parameters file specifies a buffer ID offset, which is confusing

  #90 opened 2 years ago by Karl-G1
  0

• Allow advanced users to specify which Buffer and Header ID range to use

  #59 opened 2 years ago by Karl-G1
  1

• Implement Terminal state control channels and status channels

  #60 opened 2 years ago by Karl-G1
  1

• Implement Logging capability

  #65 opened 2 years ago by Karl-G1
  1

• Minor Frame transmission is set to 0.001 milliseconds instead of configured value

  #76 opened 2 years ago by papowerNI
  0

• Tests have hard coded hardware parameters, but would be better if they were part of a configuration file

  #66 opened 2 years ago by papowerNI
  1

• Scripting example parameters file does not import subaddress information

  #25 opened 2 years ago by buckd
  1

• Coupling mode logic in the Hardware API looks wrong

  #56 opened 2 years ago by Karl-G1
  0

• Using multiple BIUs on the same PXIe module doesn't work

  #50 opened 2 years ago by Karl-G1
  1