-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to load .raw data with spice list directive #5
Comments
I got the same error. Attached is an example file that comes with LTspiceXVII that can reproduce this error. C:\Program Files\LTspiceXVII\examples\Educational\FRA\Eg1.asc ".tran 0 {5/Freq+.1m} .1m" in Eg1.asc can save computation burden significently, but it cause the simulation data points (and also the matrix size) vary depends the variable {Freq} along each step. (line 531) "mat_size(2) / num_steps" is not compatible with this situation and causes the error. I would appreciate taking consider this situation. Thank you. YC Niu |
I also had this problem recently, but finally solved it perfectly. I guess the reason is because the length of the data is inconsistent, since LTSpice is a solver with variable step size. The solution is to use the software "ltsputil.exe" to interpolate the data in the raw file to achieve a consistent step size. For the new version of LTSpice, you also need to use "ltsputil17raw4.exe" to convert raw files. The above software can be easily found in google. Below is the code I use, just for reference: cd/d D:\Circuit_results\sweep_new\verify Note that they should run by CMD command, or use the batch file. |
One more important step is to keep raw uncompressed, the following command can be used in LTSpice. .opt plotwinsize=0 But this will greatly increase the raw file size. |
Hello,
I am able to load the .raw file when I run a basic .tran command. However, when I include a .step directive in the simulation I get the following error from MATLAB:
Any help would be greatley appreciated.
Thank You,
Ethan
The text was updated successfully, but these errors were encountered: