Hi, Nimish, On Sep 24, 2013, at 9:02 AM, Nimish Sane wrote:
> I was under the impression that you are required to save model files as .slx, > because that is how it now stores model files by default. However, it does > give an option to save them as .mdl files in a drop-down list. So, .slx > format is indeed recommended, but not required. I am using .mdl for now for > easy integration with CASPER related development. Thanks for verifying that the .mdl file is still supported. I don't know of any specific problems saving in .slx format, but I don't want to find out either. One feature of the .mdl file format is that it is text based so it is possible (for the brave and/or foolish) to edit it with a text editor. The .slx format is actually a zip file containing a multiple files. > I did upgrade my mlib_devel to use the latest commit in casper-astro > repository based on Andrew Marten's suggestion on another thread. I followed > the procedure you have described. That seems to have worked fine. I am > attaching a log here. There are several warnings before it updates the old > blocks with new versions. I believe these are safe to ignore. Could you > please confirm? I haven't seen warnings like that before, but they are from the pre-updated blocks so I think they are fine to ignore. > I am able to update the diagram successfully. That's great! You should probably go through and re-verify the functionality of the updated model, either in simulation or in hardware, because it's possible that the latencies (or or other aspects) of some blocks have changed since the previous version of mlib_devel that you were using. Dave
