solution for our query

[thakurshubh]

hello sir , please refer to this attachment n provide us a logical solution for  this..thanku

[GerdW]

Hi thakurshubh,

check the parameters of that subVI and determine the wrong parameter.

This process is called "debugging" - and is also mentioned in the LabVIEW help!

[thakurshubh]

sir i tried doing debugging but it is not working for me...it still showing some error due to which our stop button is not stoping the program.

can u  tell me the type of errors which might be possible in our case???

[GerdW]

Hi thakurshubh,

the error message names two possibe reasons. Either there is an invalid parameter - or it's a GPIB error in case you use GPIB functions…

[thakurshubh]

yes sir gpib errior is there but i m have tried my best but it is notr working.....can u tell the solution for this bcz this is the last error which my program has so its frustrating us...bcz we want our preogram to run ..........thnku

[Dennis_Knutson]

Can't tell a thing from just the front panel except you don't have a VISA Resource. You would not get a GPIB error if you're not using GPIB and the error comes from a serial initialize. Attach a snippet of the block diagram.

[GerdW]

Hi thakurshubh,

and please read this - it help's a lot to have readable questions…

[mikeporter]

What are the inputs to the property node mentioned? The message tells you which one.

Mike...

[Bob_Schor]

Who wrote the code?  I notice that you have not provided it to us (and please do not provide a picture of the code -- we need the actual VI so we can examine and test it), so I am assuming you did not write it, or it is otherwise proprietary.  If you cannot share it, go back and ask the person who wrote it for help.

Did you write it?  If so, are you learning LabVIEW and are you asking for help in this process?  It really helps us to know the context of the problem so that we can "teach" as well as "fix".

Bob Schor

[natasftw]

To be fair Bob, he also used a thread title that's completely useless.  His posts have been generally void of any information.  He's actively trying to make it impossible to help him.  It wouldn't be surprising if he wrote the code and just didn't post it because that fits his intent to be difficult to help to this point.

For future reference, "solution for our query" is absolutely meaningless.  That describes every thread ever posted.  Use a title that has some meaning.  Don't post a picture to explain a problem.  Use your words.  The more information you provide, the easier it is to determine what went wrong.  Your goal IS to find out what went wrong, correct?  Include your VI.  With errors that have different meanings depending on what caused them, it's helpful to look through the code to see what's happening.