AnsweredAssumed Answered

Upgrading to VEE9.32

Question asked by trailrider on Jun 4, 2015
Latest reply on Jun 9, 2015 by Mike

Like • Show 0 Likes0
Comment • 6

I am in the process of updating our test benches to new DAQ, GPIB, and VEE 9.32. I have everything installed, but VEE throws errors when trying to communicate to any instrument on the GPIB. When I try to create a panel it gives a timeout error. Nothing shows up on the IO Monitor. The Connection Expert is able to communicate with the equipment.

I have tried uninstall and reinstalling VEE and the same problem occurs. I have tried direct IO and still nothing.
Any ideas?

No one else has this question

Outcomes

6 Replies

WDrago Jun 6, 2015 1:15 PM
Mark Correct
Correct Answer
What version of VEE are you upgrading from?

To get your older programs to work you might have to check the "Enable Pre 8.0 Legacy I/O" box under File > Default Preferences.

-Bill
Like • Show 0 Likes0
Actions
- trailrider @ WDrago on Jun 8, 2015 6:19 AM
  Mark Correct
  Correct Answer
  I got the instruments talking. I had to enable legacy drivers. Now if I can get full control of the DAQ card I'm upgrading to. PCIE-6323. I get an error when send a number bigger than 32767 yet I'm using the WriteDigitalU32 function. Saying unable to convert to Int16??
  Like • Show 0 Likes0
  Actions
  - Mike @ trailrider on Jun 8, 2015 7:41 AM
    Mark Correct
    Correct Answer
    Hmm, tricky. There is a function asUInt16 in VEE, which I've used to convert to .NET types but not a UInt32. I would look up the .NET method System.Convert ( you need to add the mscor using Device -> Add .NET Assembly References... menu in VEE to be able to access the method ). Let us know how you get on with that.
    Like • Show 0 Likes0
    Actions
    - trailrider @ Mike on Jun 8, 2015 9:30 AM
      Mark Correct
      Correct Answer
      Have that issue fixed. Some how the input was set to Int16. Changed to any and now it is somewhat working. Has anyone tried communicating to a section of a port on a NI DAQ card? I have tried everything and still acts like it want to talk to the entire port even thought I have specified a range.
      
      Thanks,
      Like • Show 0 Likes0
      Actions
      - trailrider @ trailrider on Jun 8, 2015 12:57 PM
        Mark Correct
        Correct Answer
        Have it working. Not how I would want or think it should work, but working. I ended up writing each line separately. I think the setting the port to a range of lines does not work correctly or at least I'm unable to get it to work.
        Like • Show 0 Likes0
        Actions
        Mike @ trailrider on Jun 9, 2015 4:32 AM
        Mark Correct
        Correct Answer
        Thanks for the update - glad to hear you managed to make it work.
        
        For a part of the port the usual way to do that ( I don't know the NI API ) would be to read the whole port, set the bits you wish to change and then write the whole port back again. Maybe that would be a way to do that here.
        Like • Show 0 Likes0
        Actions

Upgrading to VEE9.32

Outcomes

Related Content

Recommended Content