LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Help Needed


@altenbach wrote:

On a side note, it took almost a day to get this thread going, possibly because of your generic and uninteresting subject line. Most will just skip it. 


Obligatory comment about the Unofficial Forum Guidelines, which mentions titles.  Also I found out about the thread because I get an email whenever someone mentions "TDMS" in a post.  I expect to get an email, about this post since I mentioned it again.

Message 11 of 13
(430 Views)

@GerdW wrote:

Hi Bimple,

 


@MrBimple wrote:

 Basically, the guy who wrote and maintained it is gone and left with no supporting documentation.


There are some options:...

  • Prepare a good offer for other freelancers to fix your problems...

Is WFH an option? My price is high but the cost is lower than unsupportable deliverables.


"Should be" isn't "Is" -Jay
Message 12 of 13
(427 Views)

Also note that there are some hardwired paths (Merge TDMS (SubVI).vi), meaning the program will only run on this exact computer with this exact HD arrangement containing this exact folder hierarchy and these exact files. 😮 While they generate an error if they don't exist, the caller discards the error (second picture) and you'll never know about it! Way too fragile!

 

If for example IT did some maintenance (Maybe one of the drives failed!) and moved drive letters around, things will fail without alerting the user. Can you see if these paths (There are a few more) are still valid using the windows file manager?

 

altenbach_0-1660314543951.png

 

 

Yes, the main VI is just plain horrible. I simply don't trust it. Event that subVI could have just used an array of strings as input instead of handfuls of variants that get converted back to string inside the subVI. Why??? That's just one big hairball with inputs on all sides! 😮

 

altenbach_0-1660315264127.png

 

 

0 Kudos
Message 13 of 13
(422 Views)