LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

converting LabVIEW 8.5 vers 2012

Hi,


my mission is the transferring a programme written by another person.

the old computer has

a version of system exploitation XP(32 bits) and

LabVIEW 8.5 and card PCI 6024E and

NI-Daq traditionnel


the new computer has

a version of system Windows 7(64 bits) and

LabVIEW 2012 and card USB 6009 and

NI-DAQmx version 9.7.0.f.0

 

What can I do to make my program work in the new pc?

 

Helpppppppppppppppppppp please,

0 Kudos
Message 1 of 10
(3,259 Views)

could be worth posting to this board

 

http://forums.ni.com/t5/Version-Conversion/bd-p/VersionConversion

Please remember to accept any solutions and give kudos, Thanks


LV 8.6.1, LV2010,LV2011SP1, FPGA, Win7
0 Kudos
Message 2 of 10
(3,258 Views)

The simple part is converting the code itself. LV2012 will open the old code and save it in the new version. The hard part will be updating all the traditional DAQ calls to DAQmx. Depending on how well, or how poorly, the code was written, that part of the job could be huge.

 

My recommendation is to dig into the DAQmx examples and learn about how they work. Then go into the old code and try to rewrite ot using the new DAQmx techniques. I'm sorry I can't be more precise, but without an example of the code it's impossible to give more specific answers.

 

Mike... 


Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 3 of 10
(3,247 Views)

Hi,

 

you will find the code in attachment

 

Can you help me please?

 

Thanks,

0 Kudos
Message 4 of 10
(3,228 Views)

Two problems:

 

1. You need to get rid of the sequence structure. Assuming the operations can't be performed in parallel, the execution of the subVIs should be gated by the passing of error data from one to the next.

 

2. The subVIs are apparently where the daq code is, and you didn't send any of those.

 

Mike...

 


Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 5 of 10
(3,218 Views)

Hi,

 

thank you for having answered me quickly.

 

for a first probleme of sequence, I am new developer so it seems to me easy to use sequence

the second probleme, you find the vis are missing in attachment

 

thank you for your hlep

0 Kudos
Message 6 of 10
(3,212 Views)

Sequences are never a good idea, better to learn to not use them in the beginning.

 

More inportantly though, none of the VIs you posted use any DAQ. They all make calls to some custom DLL.

 

Mike...


Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 7 of 10
(3,204 Views)

Hi,

 

but how i can use this bll and how i can put Orbit_if.dll in my computer?

 

I try to put Orbit_if.dll in System 32 but he does not work, so i do not know how i use this dll

0 Kudos
Message 8 of 10
(3,199 Views)

can you tell me how i do not develop with sequence, any site?

0 Kudos
Message 9 of 10
(3,194 Views)

Each oone of those DLL calls can generate an error in the form of a numeric code that is in the "return" value. Typically a value of 0 means no error - but check the dll documentation.

 

  1. On each subVI place error in and error out clusters.
  2. On the block diagram place a case structure and wire the error in cluster to the case structure's selector node. When you do, the case in the structure will chaneg to "No Error" (green border) and "Error" (red border).
  3. In the Error case wire straight through the structure to the error out cluster.
  4. Place the existing DLL call in the No Error case.
  5. If the return value from the dll call is the non-error value (again, check the dll documentation) pass the input error cluster out to the error out cluster unmodified.
  6. If the return value indicates an error, create an error cluster where the return value is the Code value, the Status is a boolean true and the Source value is a string stating what the error code means (Also available in the dll documentation). Pass this error cluster to the error out.

Give that a try and post your results.

 

Mike...


Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 10 of 10
(3,188 Views)