01-30-2024 02:10 AM
I am getting this error whenever i am playing with VI in labview software.
01-30-2024 03:22 AM
Hi hemanth,
@hemanthsurya99 wrote:
I am getting this error whenever i am playing with VI in labview software.
So the error is in the way you "play" or in your VI.
We cannot comment any of both options because of missing information...
01-30-2024 03:26 AM
yes whenever i am playing vi then i got this error. pls let me know what kind of info you need to solve this.
01-30-2024 03:58 AM
How to identify which is causing this error to pop up.
01-30-2024 08:22 AM
Please post your code so that we can know what might be wrong.
01-30-2024 10:51 PM
its huge code that too confidential. can you predict where I'm going wrong need some inputs so that i will check it out.
01-31-2024 01:22 AM
@hemanthsurya99 wrote:
its huge code that too confidential. can you predict where I'm going wrong need some inputs so that i will check it out.
You are asking us to do something similar than to diagnose what defect your car has when it’s beeping.
Beeping where? Is a dashboard light blinking? Or is it the tires screeching when you go fast around a corner? Does it beep as soon as you start the engine or rather when you do something specific?
You realize that LabVIEW can execute your program in single step mode and you can then go into the subVIs and see which function is exactly generating that error?
02-06-2024 10:09 PM
Issue solved by myself. In my RTL design the reference clock is not connected internally becoz of which labview is throwing error. Issue solved.
02-14-2024 04:38 AM
Can anyone help me in this regard?
My top file is written in Verilog code. How can i make labview software to support verilog hdl?
Thanks.
02-14-2024 05:35 AM
@hemanthsurya99 wrote:
Can anyone help me in this regard?
My top file is written in Verilog code. How can i make labview software to support verilog hdl?
Thanks.
I cannot find a good reference but Verilog must be wrapped in VHDL to be called. In other words, the top level cannot be Verilog.