Prev: inputdlg box
Next: Network size (using newff)
From: Rajasekar on 29 Nov 2006 03:54 Hi Nox, dimensions in the sense? i couldn't get to ur point... the problem lies with the link between state-space block and demux block.. i have a doubt that,this due to single link between state-space and demux.. but the block contain 2 values (x and y)........... i think this is the place where my problem lies.. any possible solutions to overcome? regards rajasekar nox wrote: > > > ok I found the model. > > what's the dimension of the state space output y ?
From: Rajasekar on 29 Nov 2006 04:28 Hi Nox, I understood ur point. but when i goes to format menu->port and signal displays->signal dimensions it goes to simulink debugger window ,not an dimension window as mentioned by u... why the dimension window is not coming ? suggest me some solutions...... regards raja nox wrote: > > > the problem is the following : > > I think the configuration of your state space block isn't good. > What > are your parameters for this block (A B C D) ? > the output y dimension must be at least 3 (vector with at least 3 > coordinates), because in your demux, you're trying to separate your > signal in 3. > Here the input of the demux is a vector with only 1 or 2 > coordinates, > so of course you can't separate it in 3 different parts, and it > generates an error. > > So take a look at your dimensions by doing the following : > > in your model, go in the "Format" menu > > then choose "Port/Signal Displays" and then put the "Signal > Dimension" to on. > > You'll see the dimensions on your model, and you'll see that the > input of the demux is inferior to 3, which is not correct.
From: rajasekar on 29 Nov 2006 05:01 Hi Nox, The Values for C variable,what i used is given below C=[eye(9)]; but this variable are exist in matlab work space.. regards rajasekar nox wrote: > > > you must have a window telling you the same error message as > previously. > But we don't care. > The important point is that dimensions of your signal now appear on > your model (on the links before and after each block). > > Could you please tell me the value of the C matrix in your state > space block ? (double clic on the block)
From: rajasekar on 29 Nov 2006 05:22 Hi Nox, one more thing i forget to tell in the last message, the values i got like ?(1) input side of state-space block and as well as in the output side of the state-space block and only ? in the input side of demux block.. regards rajasekar nox wrote: > > > so your output is a 9 dimension vector... > > we must be sure of this. Let's check... > > if the "Signal Dimension" setting didn't work, you can connect a > "to > workspace" block (in "Sinks") on the output of the state-space > block > (instead of the demux), and remove all blocks on the right of it > (demux, gain, scope,to workspace). > > Then run your model. > > The output of your state-space is now in your workspace with the > default name 'simout' I think. > > So try a > size(simout) in your prompt to check the dimension of the signal. > > What's the result ?
From: Rajasekar on 29 Nov 2006 05:39
Hi Nox, I tried as u said, i removed all the blocks from my model and i replace it with the simout block after the state-space block, as u said the variable "vi" not exist in the work space in matlab.but the values after the mux before state-space block is 3.... and the errors i got are listed below... 1.Invalid dimensions encountered while propagating dimensions from output port 1 of 'pwmchk/Mux' to input port 1 of 'pwmchk/State-Space'. During propagation, we are attempting to unify the dimensions of the multiplexed signal with dimensions {1,1,1} to obtain the dimensions [-1] 2.Error in port widths or dimensions. Invalid dimension has been specified for output port 1 of 'pwmchk/Mux' 3.Error in port widths or dimensions. Invalid dimension has been specified for input port 1 of 'pwmchk/State-Space' nox wrote: > > > rajasekar wrote: >> >> >> Hi Nox, >> >> one more thing i forget to tell in the last message, >> >> the values i got like ?(1) input side of state-space block and as >> well as in the output side of the state-space >> block >> >> and only ? in the input side of demux block.. >> >> regards >> rajasekar >> > > ok ! the the dimensions display worked well... > > So as I said, simulink think that the input of the demux is a one > dimension vector...of course you can't separate a one-dimension > vector in three with the demux. > > Now we need to find why this state-space outputs a one-dimension > vector instead of a nine-dimension one. > > The input of the state-space model doesn't seem right already... > > You have a "To Workspace" on the input...Use it to check the value > of > Vi. > > What do you find ? > > PS : maybe it'll be faster if you send me the model by email |