05-30-2020 04:09 AM - edited 05-30-2020 04:10 AM
As mentioned error 7777 is a custom error. Someone (you, a colleague or a downloaded Vi) wrote VIs and decided to generate this error based on some error condition in the code. Aside from using a very random code (just hack four times on the keyboard somewhere) he also didn’t think about adding some context to the string portion of the error cluster.
While it COULD be possible that this error is caused by another program trying to open the communication resource (such as a serial port) that your program tries to use, killing random processes to see if it solves the problem is a bit like removing part for part from your car engine because it makes a funny sound until the troubling sound stops. Hardly effective and neither conclusive.
You’ll have to run this in the LabVIEW IDE and step through the code to see where this error is occurring. A first step is to use Find inLabVIEW and look for this 7777 error code in the program. Chances are that there are a bunch of locations as the developer used this code as a generic “something went wrong” indication. But it’s very likely limited to one specific driver component in your program so you have a better idea in which part of your program you will need to set breakpoints and step through your code with code highlighting enabled.
06-05-2020 06:28 AM
So a co-worker and I messed around with and got it to work now, Thanks for your guys responses.