|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: HELP!!!!!!!! with Labview Errors
As mentioned, please post more info, but my guess is that in Begin, some form of I/O based on the FPGA is no longer opening due to the latest modification. Without more of the error chain, it can't be narrowed down. I'm not really sure why the error is first showing up in the prep dashboard code except that it reads virtually everything in it's current form. If this is how the tea leaves dry out, focus on fixing the open error and all should work fine.
Greg McKaskle |
|
#2
|
||||
|
||||
|
Re: HELP!!!!!!!! with Labview Errors
Thanks for trying to help but it was all because our crio had image v28 not v30
|
|
#3
|
||||
|
||||
|
Re: HELP!!!!!!!! with Labview Errors
It's great that you posted the solution to the problem, as then you and other teams can be sure to add 'Check version of FPGA image' to their trouble-shooting check-list.
Last edited by Jon236 : 17-10-2011 at 13:25. |
|
#4
|
||||
|
||||
|
Re: HELP!!!!!!!! with Labview Errors
Sounds Like a good idea and if you have one of these trouble-shooting check-lists could you please post it here as we are a new veteran team but our rookies in the labview programing language and just lost our only programer(don't ask me why we only had one i have no idea but we were a very small team)
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|