09-12-2019 07:58 AM
The IT people here where I work need my laptop updated to Win 10. My 2009 version will no longer work. I have to vi's I use in teaching labs. They are broken. I neeed these to work for October. I have not programmed in Labview for maybe 5 yrs now. Can some one help me.
I have a license and a 2016 version the university purchased. We have 2009 up to 2018 or 2019 I think. Anyway I got away with using 2009 until they made me upgrade my laptop. I am an electronics/electrical eng - not a labview programmer.
Solved! Go to Solution.
09-12-2019 08:19 AM
Your VI's all open fine for me in 2019 without error.
You say they are broken, how are they broken? Broken run arrow? What does it say when you click on that broken run arrow.
If you provide information with details on the problem, we might be able to guide you to how to fix it.
09-12-2019 08:24 AM
I also opened them in LabVIEW 2016. I sent you a Private Message on the Forums suggesting (as a fellow academician) some things you might try ...
Bob Schor
09-12-2019 10:03 AM
Hey Ravens fan.
I uploaded the wrong vi's in my rush just before labs.
The muscle stim analysis and the emg_male analysis vi's have broken run arrows.
I attached the error window for the emg_male and the muscle stim analysis vi.
I got away with using these vi's for demo labs until I had to update to Windows 10.
09-12-2019 11:12 AM
09-12-2019 11:31 AM
I managed to reach out to Ned via a PM, and we've talked on the phone. He sent me his EMG Male Analysis routine, which also opens fine for me. He's in class (teaching) right now, but I expect he'll call me when he gets back, and we'll figure out what pieces he's missing so he can install them.
Bob Schor
09-12-2019 12:00 PM
I would start questioning the version of LabVIEW. Is it Basic, Full, or Professional?
It might use some functions that are only available in the Full version, but it is being opened in the Basic version. For example, the Amplitude and Levels.vi.
09-15-2019 12:37 PM
I uninstalled Labview. Reinstalled 2016 and everything works. Thank you for the help. Special shout out to the coding suggestions.