sydney Posted December 7, 2009 Report Share Posted December 7, 2009 I have a working project that is fairly large and tried to save to version 8.5 and got a memory mananger.cpp line 547 error. I also noticed that the subVIs seem to make the version transformation even though the main vi did not. I did install the f2 patch and then got the same results. About the most esoteric features that I am using in the program are the conditional code blocks and the diagram disable blocks. Any ideas? Quote Link to comment
Darren Posted December 7, 2009 Report Share Posted December 7, 2009 I think I've seen this issue posted on the NI Forums a few times, and I think it has to do with having an Event Structure in your 2009 diagram and attempting to save to 8.5. I think there are some workarounds posted. -D Quote Link to comment
Yair Posted December 7, 2009 Report Share Posted December 7, 2009 I believe the issue Darren is describing was supposed to have been fixed by the f2 patch, so presumably it's not that. When I have an error and I want to pinpoint the source, what I usually do is delete parts of the code until it stops happening or delete all of the code and then delete less and less until it starts happening. Which method you choose depends on all kinds of factors, but the basic concept is the same. I usually prefer at least deleting all the code first, to make sure the issue isn't with the VI itself. Quote Link to comment
asbo Posted December 7, 2009 Report Share Posted December 7, 2009 If you're able, you might also try saving to 8.6 as an intermediate step. I feel like I've done something like that previously, just not with LV2009. Quote Link to comment
huotom Posted December 10, 2009 Report Share Posted December 10, 2009 I believe the issue Darren is describing was supposed to have been fixed by the f2 patch, so presumably it's not that. When I have an error and I want to pinpoint the source, what I usually do is delete parts of the code until it stops happening or delete all of the code and then delete less and less until it starts happening. Which method you choose depends on all kinds of factors, but the basic concept is the same. I usually prefer at least deleting all the code first, to make sure the issue isn't with the VI itself. I think it has not been fixed by the f2 patch. May be f3 or fn is OK. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.