Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


danren924 last won the day on January 17 2014

danren924 had the most liked content!

Community Reputation


About danren924

  • Rank
    LAVA groupie
  • Birthday 09/24/1958

Profile Information

  • Gender
  • Location

Contact Methods

LabVIEW Information

  • Version
    LabVIEW 2015
  • Since

Recent Profile Visitors

1,047 profile views
  1. I was able to establish communication between LabVIEW and the 1553 interface, after some help from the folks at AIT. The "No Hardware Found" error was caused by the drivers and DLLs. When the interface card was originally installed, the LabVIEW drivers were not on the system, and the new hardware wizard enabled the non-VISA drivers. AIT sent me a detailed document on the procedure for changing the drivers. This resulted in a change of the position of the AIT hardware in the Device Manager. Originally, the 1553 interface showed up under the AIT group in Device Manager. With the correct drivers
  2. I have an AIT MIL-STD-1553 PXI card, and I am trying to control it using LabVIEW. The card shows up in MAX, and a Test Panel is able to communicate with it, as shown in the attached images. Further, if I open a VISA session with the instrument, it seems to be okay. (I have only tried doing a VISA Open and VISA Close, resulting in no error. Since I don't know any other VISA commands to this instrument, and since it does not seem to speak SCPI, I have been limited to simply opening and closing the VISA session.) However, when I try to do a simple Initialize using the AIT LabVIEW vis, I get an er
  3. What reason do you feel will keep you from initializing the array? Do you know the array dimensions? Will the array be a constant size? If the array size will be changing, averaging arrays of different sizes becomes a much more complex issue.
  4. If you know the dimensions of your 2D array, that is if the size of the 2D array is constant, you can initialize the array using the Initialize Array function in the arrays palette, and feed that into your shift register. The default array is 1D, but you can make it 2D by simply adding a dimension input. Then feed your zero constant into the Element input and the resulting output will be a 2D arrayof zeroes with the dimension constants you wire to the dimension size inputs. It is generally good practice to initialize an array so that LabVIEW will allocate the space for it up front, eliminating
  5. While I have received no replies to my question, I have made some progress. The correct sequence of DLL calls has enabled me to exercise control of the processor through the Background Debug Mode (BDM) Port, using the Call Library Function Node in LabVIEW. I'll outine my progress, in case someone else out in the LabVIEW universe is trying this. The PE Micro DLL must first be loaded into memory, and remain in memory for subsequent calls, which requires dynamic loading of the DLL. Dynamically loading the DLL is accomplished by setting up the Call Library Function Node to specify the path to
  6. I have a PE Micro USB Multilink cable for interfacing to a Freescale MPC850 microcontroller. I have also purchased the UNITPPC software package from PE Micro, which includes the unitppcz.dll application extension. There are several routines within this dll that I have tried to call from LabVIEW using the Call Library Function Node, but I have had no luck exercising any control or reading any data back from the micro. The Multilink cable seems to work fine when I run the PE Micro executables. I want to incorporate the dll into a large LabVIEW test application that will exercise complete control
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.