Has the bandpass filter function changed recently?

Question

Rosie 2013-7-30

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/83552-has-the-bandpass-filter-function-changed-recently

I am using the Bandpass filter function as shown below:

    d = fdesign.bandpass('N,F3dB1,F3dB2',Order,F3dB1,F3dB2,Fs);
    d1 = design(d,'butter');
where I commonly specify N as 4, F3dB1 as 5 and F3dB2 as 450 and Fs as 2000. 
I have used this many times up to yesterday and it worked fine. Today I am getting an error message as shown below:

"Error using fdesign.bandpass/set The name 'SpecificationType' is not an accessible property for an instance of class 'bandpass'."

I don't know whether there has been a sudden change in the input specifications, but even if I try and run one of the examples from the help file I get the same message. I will be very grateful to see if anyone else has come across this or if anyone can suggest why it's suddenly changed! Thanks, Rosie

0 个评论
显示 -2更早的评论隐藏 -2更早的评论

请先登录，再进行评论。

请先登录，再回答此问题。

Answer 1

Wayne King 2013-7-30

0
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/83552-has-the-bandpass-filter-function-changed-recently#answer_93125

在 MATLAB Online 中打开

Hi, the following code should work:

    Order = 4;
    F3dB1 = 5;
    F3dB2 = 450;
    Fs = 2000;
    d = fdesign.bandpass('N,F3dB1,F3dB2',Order,F3dB1,F3dB2,Fs);
    d1 = design(d,'butter');

The only thing I can think of is that you have some file that is actually shadowing the actual UDD class file

Can you try the following:

dbstop in toolbox\signal\signal\@fdesign\@bandpass\bandpass.m

and then

d = fdesign.bandpass('N,F3dB1,F3dB2',Order,F3dB1,F3dB2,Fs);

to see if the debugger takes you to the correct file, should be:

toolbox\signal\signal\@fdesign\@bandpass\bandpass.m

0 个评论
显示 -2更早的评论隐藏 -2更早的评论

请先登录，再进行评论。

Answer 2

Rosie 2013-7-30

0
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/83552-has-the-bandpass-filter-function-changed-recently#answer_93127

Thanks for your answer, I think it must have been something along those lines. Fortunately, closing down Matlab and re-opening it has fixed the issue, for now at least.