I'm currently trying to run a .NET assembly and perform a change in a particular mode in a control system. When I run the program on Labview the code get's stuck at the first invoke node and won't move on no matter how long I wait. I have attached a piture showing where it get's stuck for a reference. Does anyone know why it's getting stuck and how I can overcome it?
Please tell me you don't actually expect someone to fix your problems when the whole VI picture that you posted is blurred out. Is it April Fool's Day already?
We don't know which constructor you called, which methods you are calling, nothing...except that you are running this on an internal network, as evidenced by the 192.168.?????? ip address. Why would you even blur out the IP address? Every computer behind a Linksys or Netgear router has a similar ip address scheme. No one is going to hack your machine by knowing your internal ip address. Relax and do yourself a favor by doing us a favor and sharing the information we need to help you solve your problem.
See attached, unblurred.
I'm not worried about getting hacked, but about getting in trouble with my company. I'm new to this industry so I'm not aware of what I can share and not share.
Well, with that invoke node having no parameters passed to it at all, it's likely that whatever it's trying to do is causing it to freeze because of the code inside the DLL that you're calling and has nothing to do with LabVIEW specifically.
Do you have access to any documentation or source code that would reveal what that call is supposed to do?
Best guess on what it does by the function name is that it's trying to get access to a thread running in parallel, so it could be that it's waiting for another process to signal and it's a problem with that other process.
Thanks for the reply Kyle,
Those are great suggestions. I agree on your comment about it getting stuck because it's waiting for another process before continuing to the next step of the labview code. I just got home from work so I won't be able to view the source code until Monday morning but once I do I will get back to you with what I find.